GeForce4 - X Windows using 99% CPU

[aalto]

I've managed to get the nvidia driver (version: 1.0-4349) successfully installed and working with my GeForce4 MX440SE card on my AMD Athlon/K7SEM motherboard (256MB RAM/30GB HDD). When I boot Redhat 8.0 it successfully starts the GDM login (X Windows), where I can login and use X Windows for about two to three minutes. After that X Windows locks up and is using all the available CPU. When I strace the process, it seems to be hung on this loop:

--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])

I've check though all the files in /proc/driver/nvidia and everything looks fine. Additionally my XF86Config looks fine, as you can see:

# XFree86 4 configuration created by pyxf86config

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

Section "Files"
# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.

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"
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/mouse"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

#Section "InputDevice"
## If the normal CorePointer mouse is not a USB mouse then
## this input device can be used in AlwaysCore mode to let you
## also use USB mice at the same time.
# 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 "Samsung SyncMaster 15GLe"
DisplaySize 270 200
HorizSync 30.0 - 50.0
# VertRefresh 50.0 - 120.0
VertRefresh 60
ModeLine "1400x1050" 129.0 1400 1464 1656 1960 1050 1051 1054 1100 +hsync +vsync
ModeLine "1400x1050" 151.0 1400 1464 1656 1960 1050 1051 1054 1100 +hsync +vsync
ModeLine "1400x1050" 162.0 1400 1464 1656 1960 1050 1051 1054 1100 +hsync +vsync
ModeLine "1400x1050" 184.0 1400 1464 1656 1960 1050 1051 1054 1100 +hsync +vsync
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
# Driver "vesa"
Driver "nvidia"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce 4 (generic)"
BusID "PCI:1:0:0"

Option "MvAGP" "2"
Option "ConnectedMonitor" "TV"
Option "TVStandard" "NTSC-M"
# Screen 0
EndSection

#Section "Device"
# Identifier "Videocard1"
# Driver "nvidia"
# VendorName "Videocard vendor"
# BoardName "NVIDIA GeForce 4 (generic)"
# Screen 1
#EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Modes "800x600"
EndSubSection
SubSection "Display"
Depth 16
Modes "800x600" "640x480"
EndSubSection
EndSection

#Section "Screen"
# Identifier "Screen1"
# Device "Videocard1"
# Monitor "Monitor0"
# DefaultDepth 16
# SubSection "Display"
# Modes "800x600"
# EndSubSection
# SubSection "Display"
# Depth 16
# Modes "800x600" "640x480"
# EndSubSection
#EndSection

Section "DRI"
Group 0
Mode 0666
EndSection

...I've also played with the "MvAGP" device options, trying numbers 0-2, but to no avail.

If anyone could give me any help or hints, it would be greatly appreciated.

thanks in advance!

alex

[LordMorgul]

The option for AGP selection is correctly:

Option "NvAGP" "n" # n: 0-2

I think this should have given you an unknown option error in the log file at /var/log but perhaps not.


(ramble from coder who doesn't backtrace...)
The cpu problem I cannot really offer advice on, only to wonder what windowing system you are using, and perhaps what the 'Alarm clock' refers to? Are you perhaps running a buggy dock app?

[BigFish7]

my friend had the same problem with geforce3 (he had a vir)
just format and it should be fine (it fixed the problem, with his pc)

P.S. he had winXP so i might be wrong...

[aalto]

Thanks - That was exactly the problem. Now that I've fixed this typo everything works perfectly.

Thanks again!