Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Sep 2008 08:00:59 -0400
From:      Robert Noland <rnoland@FreeBSD.org>
To:        Tom Evans <tevans.uk@googlemail.com>
Cc:        freebsd-x11@freebsd.org
Subject:   Re: Regression in intel driver
Message-ID:  <1222171259.1732.9.camel@wombat.2hip.net>
In-Reply-To: <1222169294.2443.6.camel@localhost>
References:  <1222162224.2731.20.camel@localhost> <1222163559.2731.27.camel@localhost> <3a142e750809230352p3ad6d256w5794eaccc2c53b38@mail.gmail.com> <1222169294.2443.6.camel@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-eadfAg35AfNVD9B8vb1h
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2008-09-23 at 12:28 +0100, Tom Evans wrote:
> On Tue, 2008-09-23 at 12:52 +0200, Paul B. Mahol wrote:
> > On 9/23/08, Tom Evans <tevans.uk@googlemail.com> wrote:
> > > On Tue, 2008-09-23 at 10:30 +0100, Tom Evans wrote:
> > >> Hi all
> > >>
> > >> I've been using the intel xorg driver for quite some time now, and
> > >> recently upgraded Xorg server/drm/intel driver to the most current
> > >> available in ports. This has caused a significant performance regres=
sion
> > >> when running without direct rendering enabled, which is required wit=
h
> > >> this driver to achieve Virtual desktop with a dimension greater than
> > >> 2048 pixels. Xorg now chews through 30-35% CPU whilst tailing a log
> > >> file, where as before this used 3-4%. The effect is visibly noticeab=
le
> > >> (and doesn't just apply to fast moving text!)
> > >>
> > >> I have an HP laptop with a 1400x1050 LVDS panel, with a 1280x1024 TF=
T
> > >> attached to the VGA port. My preferred setup is:
> > >>
> > >> xrandr --output LVDS --mode 1400x1050 --output VGA --mode 1280x1024
> > >> --left-of LVDS
> > >>
> > >> What I am running now, the only way to get sane performance:
> > >>
> > >> xrandr --output LVDS --mode 1024x768 --output VGA --mode 1280x1024 -=
-above
> > >> LVDS
> > >>
> > >> I've tried reverting back to an older driver, but it seems that chan=
ges
> > >> to libdrm prevent that. I fear I may have to roll back drm, mesa,
> > >> xorg-server et al just to use a different driver version.
> > >>
> > >> Any tips?
> > >>
> > >> Cheers
> > >>
> > >> Tom
> > >
> > > I've just re-read this, and it isn't clear at all, my bad!
> > >
> > > First off, I forgot to mention what fbsd version I am using:
> > > FreeBSD zoot.mintel.co.uk 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #9: M=
on
> > > Sep 15 16:06:57 BST 2008
> > > root@zoot.mintel.co.uk:/data2/FreeBSD/RELENG_7/obj/data2/FreeBSD/RELE=
NG_7/src/sys/ZOOT
> > >  i386
> > >
> > > What I really need help with is, if I want to rollback to and use an
> > > earlier version of the intel driver, what other packages should I als=
o
> > > roll back? The compilation failure of xf86-video-intel-2.2.1_1 (and
> > > earlier versions) is:
> > >
> > >   In file included from i810_driver.c:88:
> > >   i830.h:74:20: error: xf86mm.h: No such file or directory
> > >
> > > Googling tells me that this is due to a libdrm change, so obviously t=
hat
> > > must be downgraded, which probably will require an earlier version of
> > > xorg-server as well. Any notable others that will need to be downgrad=
ed?
> > >
> >=20
> > It is known that new libdrm cause obsolete xf86-video-i810 to be
> > marked as broken port.
> >  For start just downgrade libdrm to 2.3.0 and try again.
> >=20
>=20
> I rolled back libdrm, xorg-server and xf86-video-intel back to
> 2008.07.23 (having ports as a CVS checkout is handy!), which helped a
> lot. There are still lots of slow downs due to indirect rendering that I
> would swear were not there before.
>=20
> This dual head limitation is really .. limiting .. I think the correct
> solution may be to ditch this hardware and get something with a bit more
> fancy hardware, probably nvidia. What graphics drivers do have good dual
> head support (eg: Direct rendering on both screens, full xrandr 1.2
> support)?=20

I'm still partial to Intel or Radeon...  We have, or are getting
documentation from both vendors.  I suspect the real issue that your are
running into is a limit on the maximum texture size, which doesn't
prevent drm from working.

robert.

> Cheers
>=20
> Tom

--=-eadfAg35AfNVD9B8vb1h
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEABECAAYFAkjY2nsACgkQM4TrQ4qfROMuUwCfZlN8+6uS29NCafO43Yusv1Zb
dEAAoIKtgAx3bUfDJhZOzDIxXchT0pCa
=MzA1
-----END PGP SIGNATURE-----

--=-eadfAg35AfNVD9B8vb1h--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1222171259.1732.9.camel>