[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program, not the pilot))



Hans wrote:
Am Dienstag, 19. September 2006 02:28 schrieb Russ Cook:
Russ Cook wrote:
Hans-J. Ullrich wrote:
Am Sonntag, 17. September 2006 19:27 schrieb Russ Cook:
Flightgear crashes on startup on my system.  I'm running
2.6.16-2-amd64-k8-smp generic kernel.  My system:

An Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual

core cpu, with 4 MB of Corsair TwinX ram sticks.  I have an older
GeForce4 MX 420 graphics board with 64 MB ram.  I have updated my bios
to version 1303.
I'm running Debian unstable, with latest version of Flightgear and
all required packages.  I'm NOT running nvidia drivers because
they cause my system to hang.  I'm also running the VESA driver,
for the same reason.  I've attached the error message that Flightgear
generates on startup.  Is this error indicative of the video driver I'm
using?

Thanks for any help.

Regards,
  Russ
Hi Russ,

as far as I know flightgear needs rendering software, just opengl.
At start it looks in its configfile, and tries to set the settings
and initialising the scenery.
IMO you MUST have an opengl-driver working ! Otherwise it will crash.
Why does the nvidia-driver not work ? It should, if you use the
Debian packages and compile the nvidia-kernel-module on your own,
and, additionally install the package nvidia-glx.

Good luck !

Hans
Hans,
 Today I upgraded to 2.6.17-2-amd64, used the debian Nvidia packages,
compiled nvidia-kernel-module, and installed nvidia-glx.  I made the
appropriate changes to xorg.conf (attached), added nvidia to
/etc/modules,
and restarted my xserver.  As soon as I log in to gdm, the system
locks up.
I have to use ssh from another linux box to restart kill gdm.  If I
try to
log in as an invalid user, it checks password, rejects the login, and
gives
a new login prompt without locking up.  As soon as I successfully login,
the system locks up.
 I have reverted back to the vesa driver (again).  If anyone can help me
troubleshoot this problem, I'll be happy to reload the nvidia driver and
run whatever tests you can walk me through.  I'd really like to be able
to use the nvidia driver, for the performance boost it's supposed to
provide.  It also seems necessary in order to run Flightgear.

Thanks for any help.

   Russ
------------------------------------------------------------------------

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool,
using # values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual
page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades
*only* # if it has not been modified since the last upgrade of the
xserver-xorg # package.
#
# If you have edited this file but would like it to be automatically
updated # again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
	FontPath	"/usr/share/fonts/X11/misc"
	FontPath	"/usr/X11R6/lib/X11/fonts/misc"
	FontPath	"/usr/share/fonts/X11/cyrillic"
	FontPath	"/usr/X11R6/lib/X11/fonts/cyrillic"
	FontPath	"/usr/share/fonts/X11/100dpi/:unscaled"
	FontPath	"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
	FontPath	"/usr/share/fonts/X11/75dpi/:unscaled"
	FontPath	"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
	FontPath	"/usr/share/fonts/X11/Type1"
	FontPath	"/usr/X11R6/lib/X11/fonts/Type1"
	FontPath	"/usr/share/fonts/X11/100dpi"
	FontPath	"/usr/X11R6/lib/X11/fonts/100dpi"
	FontPath	"/usr/share/fonts/X11/75dpi"
	FontPath	"/usr/X11R6/lib/X11/fonts/75dpi"
	# path to defoma fonts
	FontPath	"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
	Load	"i2c"
	Load	"bitmap"
	Load	"ddc"
# "dri" module disabled for proprietary Nvidia driver
#	Load	"dri"
	Load	"extmod"
	Load	"freetype"
	Load	"glx"
	Load	"int10"
	Load	"type1"
	Load	"vbe"
EndSection

Section "InputDevice"
	Identifier	"Generic Keyboard"
	Driver		"kbd"
	Option		"CoreKeyboard"
	Option		"XkbRules"	"xorg"
	Option		"XkbModel"	"pc104"
	Option		"XkbLayout"	"us"
EndSection

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"mouse"
	Option		"CorePointer"
	Option		"Device"		"/dev/input/mice"
	Option		"Protocol"		"ExplorerPS/2"
	Option		"Emulate3Buttons"	"true"
EndSection

Section "Device"
	Identifier	"NVIDIA Corporation NV17 [GeForce4 MX 420]"
#	Driver "vesa" disabled
	Driver		"vesa"
#	Driver "Nvidia" enabled
	Driver		"nvidia"
	BusID		"PCI:4:7:0"
EndSection

Section "Monitor"
	Identifier	"S/T 77E/76E"
	Option		"DPMS"
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Device		"NVIDIA Corporation NV17 [GeForce4 MX 420]"
	Monitor		"S/T 77E/76E"
	DefaultDepth	24
	SubSection "Display"
		Depth		1
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		4
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		8
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		15
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		16
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		24
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
EndSection

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

Section "DRI"
	Mode	0666
EndSection
I see from the xorg.conf file I attached that I tried to enable both the
vesa driver and the nvidia driver.  I corrected that, loading only the
nvidia driver.  The results were the same.

Hi Russ,

this looks strange for me. I suppose, you did use the original Debian packages and not the one from the Nvidia homepage. Those will not work.

The other thing is, you could comment the line >> Load "glx" << out, so that you will start withe the "nvidia" driver, but will not have acceleration. Another way is to use the driver "nv", which is the framebuffer driver for nvidia-cards.

O.k., if the "nvidia" driver works (which I suppose), then reactivate Load "glx". Take a look in /var/log/Xorg.log, there yxou may find some more information.

After building and installing the nvidia-kernel-module , reinstall the package "nvidia-glx" again, as there have to be set some symlinks and rights.

Pay attention, that all users, which shall use acceleration are in the group "video". By default they are not in Debian ! It is one of the most errors.

Hint: Just move "gdm" out of the way from /etc/init.d/ so it will no more start after reboot. O.k., if you have done this and got a shell after reboot, you can easily test with the command "startx" as root. Now you an see, what happens.

If everything works fine, move gdm back to /etc/init.d/

If everything works, and ist starts fine, you can test acceleration with "glxgears -printfps" in a shell of a KDE or similar. You should have about 900-1300 FPS for your card.

As far as I know, acceleration needs some additionally Debian-packages, mesa-glx as I remember, and some more. Debian should know this.

O.k., what can I tell more ? I think, you should test it for now, if it wil not work, just write me again.
Good luck !!

Hans

OK, I have done the following:
1) disable glx and run nvidia driver - still crashes
2) load nv driver - crashes, but not immediately upon login - alsaconf always causes a crash
3) disable glx and load nv driver - same results
4) give up and run vesa driver - solid - no crashes - can't run flightgear
5) have previously run both Knoppix and Ubuntu live CDs - both crash

Since the card works with vesa driver, just no glx and hardware accel,
I have to assume my computer board and memory are OK.  I have run
memtest extensively.

I have always intended to purchase a better graphics board once I get
the system running will.  I'd like to solve this problem first.

Any further suggestions gratefully accepted.

Regards,
 Russ



Reply to: