unresolved symbols with ati-drivers-3.11.1

Message

c0balt · Post by **c0balt** » Thu Aug 12, 2004 1:27 am

well, who got them?
with official portage ebuild or self-compiled 3.11.1 drivers i always get unresolved symbols errors when trying to start X

El_Presidente_Pufferfish · Thu Aug 12, 2004 2:25 am

post the error?

c0balt · Post by **c0balt** » Thu Aug 12, 2004 2:36 am

crap, i wouldnt have thought someone posted this fast oO
i cant kill X right now, in an hour or so ill be able to post the error message
sry

c0balt · Post by **c0balt** » Thu Aug 12, 2004 4:32 am

Code: Select all

Symbol firegl_CheckMagic from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol firegl_AGPAcquire from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol firegl_QueryHwCaps from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol firegl_AllocMemBufferFromTop from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol firegl_AllocCache from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol firegl_AllocCache from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol firegl_GetMemInfo from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol firegl_AllocMemBufferFromTop from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAAPixmapIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol fbWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAAPixmapIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol XAACheckTileReducibility from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
Symbol fbWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting

finally

darkless · Post by **darkless** » Thu Aug 12, 2004 7:06 am

Yup, seeing the exact same thing here, using ati-drivers-3.11.1 and latest xorg, both from Portage.

This thread indicates that we're not alone:
http://www.rage3d.com/board/showthread.php?p=1333086687