nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   2.6.0-test5, minion.de patch, module loads fine, x fails? (http://www.nvnews.net/vbulletin/showthread.php?t=18226)

digital 09-17-03 09:14 PM

2.6.0-test5, minion.de patch, module loads fine, x fails?
 
I recently began using the 2.6.0-test5 kernel on my workstation. I followed the guide to patch and build the nvidia driver as describe using the minion.de patch. It loads fine but still X is failing.

(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.

But it's there? which is odd.

blackbox root # lsmod
Module Size Used by
nvidia 1702508 0
hid 23808 0
uhci_hcd 31624 0
usbcore 68768 2 hid,uhci_hcd
e100 60804 0

Anyone have any ideas what could be causing the problems? I would think if I had a kernel problem it wouldn't load or build fine, which it does.

Maybe my XF86Config is not setup right (works for previous driver version on 2.4.20)?

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
# FontPath "unix/:7100"
EndSection

Section "Module"
# Load "dbe"
# Load "extmod"
# Load "fbdevhw"
Load "glx"
# Load "record"
#Load "freetype"
#Load "type1"
#Load "dri"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "InputDevice"
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "FCT1905"
DisplaySize 390 290
HorizSync 30.0 - 80.0
VertRefresh 56.0 - 60.0
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "vesa"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce FX (generic)"
VideoRam 131072
Option "NvAgp" "3"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1600x1200" "1400x1050" "1280x1024" "1280x960" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

dpw2atox 09-18-03 12:57 AM

your drivers aren't set to use the nvidia driver. Change
Section "Device"
Identifier "Videocard0"
Driver "vesa"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce FX (generic)"
VideoRam 131072
Option "NvAgp" "3"
EndSection


where it says vesa...change to nvidia

digital 09-18-03 08:46 AM

Apologize, my line was reading:
Driver "nvidia"

but I changed it to vesa so I could get X started (albiet unaccelerated and low res) and post this.

My XF86Config has the line for nvidia not vesa and still fails.

Any other ideas?

zander 09-18-03 09:09 AM

Make sure the version of the kernel module matches the version of the XFree86 driver module; if this is the case, check the output of dmesg for error messages (after the failed attempt to start X).

andy-nforce2 09-18-03 09:28 AM

hmm.. this happened to me when I went from 2.6.0-test4 to 2.6.0-test5 - exactly the same message. I had just used the same nvidia.ko I'd made for test4 and forgot to regenerate it with the 2.6.0-test5 kernel headers.. I just recompiled it using the instructions from minion.de to and copied it across and depmod'd ... and then it worked fine. Same thing applied to nvnet also. I did not change anything in the XFree config.

I have test4 and test5 in parallel on my SN41G2.

Andy

digital 09-18-03 09:52 AM

dmesg output:
nvidia: module license 'NVIDIA' taints kernel.
1: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module 1.0-4496 Wed Jul 16 19:03:09 PDT 2003

i thought i'd make sure i was using the right kernel include so I rebuilt it, make SYSINCLUDE=/usr/src/linux/include (yes linux points to 2.6.0-test5). I reloaded it and tried to start x, same issue.

digital 09-18-03 10:10 AM

if it's relevant a little system info:

asus v9560 video suite (fx5600, 128mb, dual dvi)
865pe (MSI neo2-ls) motherboard
p4 2.4c (800mhz fsb, ht)
2x512mb kingston pc3500 running at 800mhz

gentoo linux (1.4, w/ latest everything)

trying 2.6.0-test5, i'm going to go an see if the latest drivers work with my other 2.4 based kernel.

andy-nforce2 09-18-03 10:43 AM

Well I'm not sure whats up, but for interest my nvidia module seems smaller than yours. I used the nvidia 4496 pkg0 run file as the source for patching with the 4496-2.6.diff file.

$ modinfo nvidia
license: NVIDIA
license: NVIDIA
vermagic: 2.6.0-test5 preempt K7 gcc-3.3

and :

$ lsmod
Module Size Used by
snd 50788 0
i810_audio 29460 2
md5 4224 1
ipv6 255552 10
apm 18028 2
af_packet 22024 0
sbp2 24968 1
raw1394 30092 0
ohci1394 35592 0
ieee1394 222508 3 sbp2,raw1394,ohci1394
nvnet 31232 0
autofs4 16128 0
nls_cp437 5888 1
nls_iso8859_1 4224 5
ac97_codec 19212 1 i810_audio
soundcore 9280 4 snd,i810_audio
nvidia 1701804 10
ohci_hcd 18688 0
usbcore 110172 3 ohci_hcd
rtc 12856 0

digital 09-18-03 10:50 AM

I finally got everything working. When I had been using the gentoo ebuilds they somehow hadn't emerge the latest nvidia-glx package (which was masked for some reason). I forced that to emerge and then the nvidia-kernel and everything is working now. I can only assume the older glx package was giving me problems.

My module is bigger than yours, weird, but now it's working.

blackbox root # modinfo nvidia
license: NVIDIA
license: NVIDIA
vermagic: 2.6.0-test5 SMP preempt PENTIUM4 gcc-3.2
depends:

For those who have problems on gentoo:
ACCEPT_KEYWORDS="~x86" emerge /usr/portage/media-video/nvidia-glx/ nvidia-glx-1.0.4496.ebuild

That will also pull the 4496 nvidia-kernel and patch automatically (gentoo rocks).

Thanks everyone for the help.

zander 09-18-03 02:53 PM

Any given (recent) version of the NVIDIA XFree86/GLX components requires a matching kernel module, different versions will abort initialization if a version mismatch is detected; this is why I suggested that you check the respective versions. The difference in module size is to be expected with different kernel configurations (SMP/UP, devfs, proc, ...)


All times are GMT -5. The time now is 12:04 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.