Reported by Alvaro Llamas on the Debian BTS 8 months ago, probably still applies since I didn't find any significant change in the server and in the driver. I am not sure which of them should be fixed though. I am assigning to newport for now since I am not aware of any other driver with this problem. Starting X using the newport driver (without XAA explicitly disabled) fails with: > /usr/bin/X11/X: symbol lookup error: > /usr/lib/xorg/modules/drivers/newport_drv.so: undefined symbol: XAACreateInfoRec > XIO: fatal IO error 131 (Connection reset by peer) on X server ":0.0" > after 0 requests (0 known processed) with 0 events remaining. People worked around the problem with Option "no_accel" (for instance http://www.mail-archive.com/debian-mips@lists.debian.org/msg06376.html) Brice
Looks like the driver simply doesn't load the xaa module before calling XAACreateInfoRec.
Created attachment 14555 [details] [review] proposed patch
(In reply to comment #1) > Looks like the driver simply doesn't load the xaa module before calling > XAACreateInfoRec. > It seems that xaa is only loaded if NoAccel is set to true. Brilliant :)
(In reply to comment #1) > Looks like the driver simply doesn't load the xaa module before calling > XAACreateInfoRec. > Fixed in git: commit 86b6bb11ffc4bce5886b5bc28b8df41af89f0925 Author: Julien Cristau <jcristau@debian.org> Date: Mon Feb 25 11:52:20 2008 +0100 Bug#11761: Fix xaa initialization Load the xaa module when NoAccel is unset, so it actually has a chance to work.
On Mon, Feb 25, 2008 at 02:55:32 -0800, bugzilla-daemon@freedesktop.org wrote: > It seems that xaa is only loaded if NoAccel is set to true. > Fixed in git: commit 86b6bb11ffc4bce5886b5bc28b8df41af89f0925 Author: Julien Cristau <jcristau@debian.org> Date: Mon Feb 25 11:52:20 2008 +0100 Bug#11761: Fix xaa initialization Load the xaa module when NoAccel is unset, so it actually has a chance to work.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.