Re: Again: "AIGLX: Screen 0 is not dri capable"

[Florian Kulzer <florian.kulzer+debian@icfo.es>]

On Mon, May 28, 2007 at 11:00:54 +0200, Georg Heinrich wrote:
> Hello,
> 
> I have received some useful hints on how to post (thanks to Roger and
> Florian), that's why I give the information again:
> 
> ===============================================================
> 
> Hardware:
>     Apple PowerBook G4 12" (PowerBook 6,8) 1,5 GHz
>     NVidia GeForce FX Go5200
> 
> Linux:
>     debian 4.0 (etch)
> 
> ===============================================================
> 
> uname -a:
> 
> Linux gh-mob-lx 2.6.18-4-powerpc #1 Mon Mar 26 09:11:14 CEST 2007 ppc
> GNU/Linux
> 
> ===============================================================
> 
> lspci:
> 
> 0000:00:0b.0 Host bridge: Apple Computer Inc. UniNorth 2 AGP
> 0000:00:10.0 VGA compatible controller: nVidia Corporation NV34M [GeForce FX Go5200] (rev a1)

I think "NV34M" is simply the mobile version of the NV34 chipset, which
should be supported by the "nv" driver. (At least it is well supported
on i386; please note that I do not know powerpc at all.)

[...]

> ===============================================================
> 
> Xorg.0.log:
> 
> X Window System Version 7.1.1
> Release Date: 12 May 2006
> X Protocol Version 11, Revision 0, Release 7.1.1
> Build Operating System: UNKNOWN 
> Current Operating System: Linux gh-mob-lx 2.6.18-4-powerpc #1 Mon Mar 26
> 09:11:14 CEST 2007 ppc
> Build Date: 04 April 2007

[ snip: Nothing special, just a few font warnings (as you posted already
  earlier). The "nv" driver seems to load normally; GeForce FX Go5200 is
  mentioned explicitly as supported. ]

> Synaptics DeviceInit called
> SynapticsCtrl called.
> (II) Configured Mouse: ps2EnableDataReporting: succeeded
> Synaptics DeviceOn called
> (--) Synaptics Touchpad auto-dev sets device to /dev/input/event6
> (**) Option "Device" "/dev/input/event6"
> (--) Synaptics Touchpad touchpad found
> 
> Backtrace:
> 0: /usr/bin/X(xf86SigHandler+0x94) [0x1008eb98]
> 1: [0x100374]
> 2: [0x7fcac80c]
> 3: /usr/lib/xorg/modules/libxaa.so(XAAFillMono8x8PatternRectsScreenOrigin
> +0xdc) [0xf75301c]
> 4: /usr/lib/xorg/modules/libxaa.so(XAAPaintWindow+0x52c) [0xf761090]
> 5: /usr/bin/X [0x10138684]
> 6: /usr/bin/X(miWindowExposures+0x328) [0x100e057c]
> 7: /usr/bin/X [0x100a966c]
> 8: /usr/bin/X(MapWindow+0x3e4) [0x1002b6a8]
> 9: /usr/bin/X(InitRootWindow+0xfc) [0x1002b860]
> 10: /usr/bin/X(main+0x41c) [0x10025460]
> 11: /lib/tls/libc.so.6 [0xfc7e994]
> 12: /lib/tls/libc.so.6(__libc_start_main+0xb0) [0xfc7ead0]
> 
> Fatal server error:
> Caught signal 11.  Server aborting

It seems to me that the crash could be related to accelerated graphics
rendering (XAA = XFree86 Acceleration Architecture). You could try to
add

Option "NoAccel" "true"

in the "Device" section of your /etc/X11/xorg.conf. Maybe this will at
least allow you to start X.

Aside from that, the standard advice in this situation is to switch to
the "vesa" driver, but that one does not work for you either, right?

-- 
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |