strange lockup with current nvidia-drivers and debian/woody

[parasew]

trying to get the nvidia drivers to run, totally locks up my system.

the "nv" drivers worked well, after using the new drivers ("nvidia") with the installer, nothing would work.
i had to "insmod nvidia" -- when doing a "startx" everything would start up correctly, but the mouse and the keyboard are not responding. remote ssh login is working, so i have to reboot the system remotely and try again...

any ideas what could be the problem?
btw, windowmanager is gnome 2.2 and launching just "X" doesn't change anything...

other specs:
celeron333 cpu
elsa gladiac 511pci
Model: GeForce2 MX/MX 400
IRQ: 5
Video BIOS: 03.11.01.30.86
Card Type: PCI

asus p2l97 mainboard
64mb ram
debian/woody testing
kernel 2.4.20

nvidia driver 1.0-4349 (self-compiled within the installer)






++++++++++++
here is my XF86config-4 file, the logfile is attached
+

### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# If you want your changes to this file preserved by dexconf, only make changes
# before the "### BEGIN DEBCONF SECTION" line above, and/or after the
# "### END DEBCONF SECTION" line below.
#
# To change things within the debconf section, run the command:
# dpkg-reconfigure xserver-xfree86
# as root. Also see "How do I add custom sections to a dexconf-generated
# XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz.

Section "Files"
FontPath "unix/:7100" # local font server
# if the local font server has problems, we can fall back on these
FontPath "/usr/lib/X11/fonts/misc"
FontPath "/usr/lib/X11/fonts/cyrillic"
FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/Type1"
FontPath "/usr/lib/X11/fonts/Speedo"
FontPath "/usr/lib/X11/fonts/100dpi"
FontPath "/usr/lib/X11/fonts/75dpi"
EndSection

Section "Module"
# Load "GLcore"
Load "bitmap"
Load "dbe"
Load "ddc"
# Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "record"
Load "speedo"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc104"
Option "XkbLayout" "de"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "PS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Generic Mouse"
Driver "mouse"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "Generic Video Card"
Driver "nvidia"
BusID "PCI:0:12:0"
VideoRam 32000
Option "UseFBDev" "true"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
HorizSync 30-57
VertRefresh 43-72
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Generic Video Card"
Monitor "Generic Monitor"
DefaultDepth 16
SubSection "Display"
Depth 1
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Generic Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection

### END DEBCONF SECTION

[bwkaz]

Does it help to get rid of some of those useless modules, or some of the useless settings in the Device section?

Stuff like int10, record, and vbe for modules, and the BusID, VideoRAM (which, BTW, the nVidia driver doesn't even acknowledge...), and UseFBDev for the device section.

You're also getting a "failed to verify AGP" message that might be part of it... I'm not sure what causes that, but it might be something bad. Have you tried disabling AGP completely, with Option "NvAgp" "0", since you don't need it?

You might also get rid of the InputDevice "Generic Mouse" line in the ServerLayout section. That's spitting a couple of errors to the log file too (though I don't think that's what's causing a lockup...).

[parasew]

thanks for your hints, i tried commenting out all the modules, even the font servers and stuff, commented out all the things like VideoRam and so on.
and even with the
Option "NvAgp" "0"
and just starting 'X' it's still crashing...

what did you mean by int10 and record?

can it be some kernel option from the linux kernel 2.4.20, that is causing problems?

see my kernel configuration here:
http://parasew.0rf.at/temp/eye-5ystem/dmesg.txt
http://parasew.0rf.at/temp/eye-5ystem/linux-kernel-config

[bwkaz]

By int10 and record, I was referring to the modules that you have loaded that are named "int10" and "record". Have you tried commenting those out? They're a little above the "vbe" module, which you also don't need.

Why is your kernel configured for SMP? It only sounds like you have one processor... there are also known issues with SMP kernels and DVI ports that cause lockups and stuff.

[parasew]

hmm...
i commented everything out and even recompiled the kernel with no SMP. but still the same problem. when i do 'insmod nvidia' i get the following screen-output, maybe the problem is located here somehere:


Using /lib/modules/2.4.20/kernel/drivers/video/nvidia.o
Warning: loading /lib/modules/2.4.20/kernel/drivers/video/nvidia.o will taint the kernel: non-GPL license - NVIDIA
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Module nvidia loaded, with warnings


or can it be that some other kernel stuff is conflicting?

[bwkaz]

I don't really know. The tainted message is harmless, unless you think you found a Linux kernel bug. Bugreports from a tainted kernel will be summarily dismissed from the mailing list; the developers can't see the source to the kernel module, so they don't have the slightest clue what it's doing that may or may not be the cause of the bug.

Click on your own link (from the warning message) to get a full explanation.

But no, I don't really have any other ideas...