severity 391279 important thanks Joel Fried wrote: > Package: fglrx-driver > Version: 8.28.8-2 > Severity: grave > Justification: renders package unusable
The bug is at most severity important, as it doesn't make the package completely unusable for everyone (it certainly works for me and for many other people). Please read http://www.debian.org/Bugs/Developer#severities for an explanation of bug severities. > (EE) AIGLX error: dlsym for __driCreateNewScreen_20050727 failed > (/usr/lib/dri/atiogl_a_dri.so: undefined symbol: > __driCreateNewScreen_20050727) > (EE) AIGLX: reverting to software rendering This was already reported and discussed, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390361 The error you're seeing doesn't affect direct rendering, so there must be some other problem. > fglrxinfo informs me that the fglrx driver is in fact not loaded by saying: > > display: :0.0 screen: 0 > OpenGL vendor string: Mesa project: www.mesa3d.org > OpenGL renderer string: Mesa GLX Indirect > OpenGL version string: 1.2 (1.5 Mesa 6.5.1) This does indeed indicate that direct rendering is disabled, but not that the driver is not loaded. >>From higher up in the Xorg.0.log, in case it is useful: > > [...] > (II) fglrx(0): Kernel Module Version Information: > (II) fglrx(0): Name: fglrx > (II) fglrx(0): Version: 8.28.8 > (II) fglrx(0): Date: Aug 17 2006 > (II) fglrx(0): Desc: ATI FireGL DRM kernel module > (II) fglrx(0): Kernel Module version matches driver. > (II) fglrx(0): Kernel Module Build Time Information: > (II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.8-2-686-smp > (II) fglrx(0): Build-Kernel MODVERSIONS: yes > (II) fglrx(0): Build-Kernel __SMP__: yes > (II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000 > > > So it is clear that the kernel module is properly built and recognized, it > simply will not load. [...] The kernel module *is* loaded, otherwise the X driver module wouldn't be able to access this information. The error lies somewhere else. > I will be happy to provide any more information that might be useful. A complete Xorg log might help. Please look for other clues that might indicate why direct rendering was not enabled even if the kernel module could be loaded. Keywords to look for are "drm", "dri" and "agp". -- Ciao, Flavio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
