From owner-freebsd-x11@FreeBSD.ORG Sun Apr 9 05:12:10 2006 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4713C16A401 for ; Sun, 9 Apr 2006 05:12:10 +0000 (UTC) (envelope-from eric@anholt.net) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAEAC43D45 for ; Sun, 9 Apr 2006 05:12:09 +0000 (GMT) (envelope-from eric@anholt.net) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.4/8.13.1) with ESMTP id k395C8oE068103; Sat, 8 Apr 2006 22:12:08 -0700 (PDT) (envelope-from eric@anholt.net) Received: (from anholt@localhost) by leguin.anholt.net (8.13.4/8.13.1/Submit) id k395C7e2068102; Sat, 8 Apr 2006 22:12:07 -0700 (PDT) (envelope-from eric@anholt.net) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eric@anholt.net using -f From: Eric Anholt To: Fred Cox In-Reply-To: <20060409030741.61164.qmail@web31802.mail.mud.yahoo.com> References: <20060409030741.61164.qmail@web31802.mail.mud.yahoo.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-wUbvL4jgOto/cN7b8n/y" Date: Sat, 08 Apr 2006 22:12:06 -0700 Message-Id: <1144559526.7017.103.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Cc: freebsd-x11@freebsd.org, Jason Morgan Subject: Re: X troubles (possibly radeon related) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 05:12:10 -0000 --=-wUbvL4jgOto/cN7b8n/y Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2006-04-08 at 20:07 -0700, Fred Cox wrote: > --- Eric Anholt wrote: >=20 > > On Sat, 2006-04-08 at 12:58 -0700, Fred Cox wrote: > > > Several people have reported problems with X.org > > 6.9 > > > and Radeon X300, which were "solved" by going back > > to > > > 6.8.2. This includes total machine lockup with > > the > > > default vga driver as well as various ati and > > radeon > > > drivers. > > >=20 > > > Unfortunately, there doesn't seem to be any > > visible > > > action on the problem. I get no response when I > > email > > > the Xorg maintainer. > > >=20 > > > I don't think they want to believe they've broken > > > something. They want to blame the drivers. > >=20 > > I did respond to your email. I don't have any > > response from you. >=20 > I found this message in Yahoo's (overly agressive) > bulk folder, but nothing else from you. Could you > resend? If you use an email service that throws away good mail, you should get a better service, not ask people to resend mail. :P > > message gave a > > line with "vga0" from > > dmesg that's irrelevant to X's behavior, making me > > suspect that you were > > still using the radeon driver in X, not vga as you > > claimed. >=20 > I never told FreeBSD to use the Radeon driver, and > since it doesn't mention radeon in dmesg, I assumed > that was what's going on. >=20 > For people who aren't as deeply steeped in the code, > can you tell us how to tell which driver is being > used? /var/log/Xorg.0.log is X's equivalent of dmesg /etc/X11/xorg.conf is where you configure what drivers to use, if you do. > > The radeon > > driver in 6.9 (as with 6.8.2, 6.8.1, 6.8.0, 6.7.0, > > XFree86 4.4, etc.) > > had major issues. The major issues have changed > > from release to > > release, as fixes were applied for some chipset that > > broke another. > > It's really actually hard to get this memory mapping > > stuff right for > > ATI. It's quite possible that benh has fixed them > > now in the latest > > releases of the ATI driver -- he's studied the > > problems more in-depth > > than anyone before, so the latest radeon driver is > > probably good when > > combined with a good DRM and good DRI drivers. >=20 > Are these required for simple 2D X interactions, such > as fluxbox and Firefox would use? They are not required, but enabling 3D acceleration (which is the default) places a dependency on the DRM for 2D drawing, which changes code paths significantly. > > We > > have none of these in > > FreeBSD currently. > >=20 >=20 > Is there any plan to get this stuff fixed? Sure, we intend to bring in the latest greatest upstream bits. Is there a schedule? Of course not. --=20 Eric Anholt anholt@FreeBSD.org eric@anholt.net eric.anholt@intel.com --=-wUbvL4jgOto/cN7b8n/y Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBEOJemHUdvYGzw6vcRAj41AJ9ZXy2UQqVsIyJyhZS+HIyUkAUcLwCeOs6m rm0IIoySux3vYPNWfWOB+6s= =5Tp3 -----END PGP SIGNATURE----- --=-wUbvL4jgOto/cN7b8n/y--