Bug 19232 – Loading of NVidia Driver on UT2003-Live-CD 20030405 fails with "unresolved symbols" on Athlon/1000 with GF3Ti200

• Product: Gentoo Release Media
• Status: RESOLVED CANTFIX

[Description Oliver Stetskamp 2003-04-13 06:44:54 UTC]

Hardware: Athlon1000 on Asus A7V, GF3Ti200 
Symptom: Loading of X-Driver fails with "unresolved symbols" 
 
--- cut from XFree86.0.log --- 
(II) NVIDIA(0): Clock range:  12.00 to 350.00 MHz 
Symbol fbWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/nvidia_drv.o 
 is unresolved! 
Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/nvidia_drv.o is 
unresolved! 
Symbol fbValidateGC from module /usr/X11R6/lib/modules/drivers/nvidia_drv.o is u 
nresolved! 
Symbol fbGCPrivateIndex from module /usr/X11R6/lib/modules/drivers/nvidia_drv.o 
is unresolved! 
Symbol fbCreateGC from module /usr/X11R6/lib/modules/drivers/nvidia_drv.o is unr 
esolved! 
Symbol fbCreateWindow from module /usr/X11R6/lib/modules/drivers/nvidia_drv.o is 
 unresolved! 
Symbol fbWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/nvidia_drv.o 
 is unresolved! 
Symbol fbWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/nvidia_drv.o 
 is unresolved! 
Symbol fbCloseScreen from module /usr/X11R6/lib/modules/drivers/nvidia_drv.o is 
unresolved! 
--- /cut from XFree86.0.log --- 
 
Additional info: Kernel module was properly loaded at that point of time 

Reproducible: Always
Steps to Reproduce:
1. Boot the CD on hardware stated above and wait

[Comment 1 Wouter 2003-05-01 17:19:15 UTC]

it also happens on a duron 700@940 on a asus a7v133 with a leadtek geforce2 mx64 aka 100/200

[Comment 2 Chris Slater 2003-05-20 20:47:11 UTC]

I also get a simmilar problem with the America's Army Live CD that was just released. I have an Athlon 1333 MHz with a GeForce4 Ti4800SE.

[Comment 3 Stephen Ogletree 2003-05-22 19:41:42 UTC]

Same problem happening here.
Athlon 1200
GeForce 2 GTS/Pro
Americas Army LiveCD 1.4_rc4 (aa-20030513.iso)

[Comment 4 Bob Johnson (RETIRED) 2003-05-22 20:15:58 UTC]

could you please try the livecd by typing  
nofb by itself at the prompt 
 
note: not "gentoo nofb" 

[Comment 5 Stephen Ogletree 2003-05-22 20:57:46 UTC]

nofb took the gui out of the boot process, but the unresolved symbols still killed the server with a "Caught signal 4.  Signal aborting"

The only other warning in the log is
NVIDIA(0): Failure reading EDID parameters for display device CRT-0
which I assume is because I use an LCD.

Also, the 1.4_rc1 UT Demo LiveCD worked fine on this exact same system (no hardware changes since then).

[Comment 6 Chris Slater 2003-05-23 00:58:02 UTC]

I also get a Signal 4 on the America's Army CD -- aa-20030515 Live CD. Same situation, and I can't even get a command line after the crash.

[Comment 7 Stephen Ogletree 2003-06-10 01:20:23 UTC]

Is there any additional information we can provide the developers so that this can get fixed?

[Comment 8 Chris Slater 2003-06-10 12:48:55 UTC]

I don't have any addtional infromation at this time other than I do not recieve any EDID errors because I use a CRT and not a flatpanel.

[Comment 9 Hal Canary 2003-07-22 20:42:47 UTC]

Created attachment 14895 [details]
/var/log/XFree86.0.log

Similar problem.  I have a gforce2mx.  I'll attach my /var/log/XFree86.0.log

[Comment 10 John Davis (zhen) (RETIRED) 2004-01-23 17:44:56 UTC]

looks like a prob with the nvidia drivers included on the livecd. I don't know if there are plans to rebuild this livecd, but livewire would be the one to talk to. closing since I am not sure if we still support these cds