| View previous topic :: View next topic |
| Author |
Message |
m4rku5
n00b
Joined: 18 Apr 2006
Posts: 29
|
 Posted: Tue Apr 18, 2006 9:56 pm Post subject: gentoo AMD64 + nvidia + X error |
 |
|
Hi
im running Gentoo AMD64 on an Athlon 64 3000+ on a mobo with NForce4 chipset and a GeForce 6600 PCI-E
using latest stable nvidia-kernel and nvidia-glx 1.0-8756
with kernel 2.6.15-gentoo-r5
and latest stable xorg 6.8.2-r6
when running KDE for some time X freezes and uses 99% CPU
I've spent the last 4 hours on this forum and google searches but i didnt come up with any working solution to my problem.
Im looking forward to your suggestions - I'm goin to try n see if i can come up with some usefull syslog messages.
EDIT:
I've just started up X again and half the Konqueror window disappeared and i can only see the mouse moving but nothing else happens if i click the mouse buttons or hit and keys. CTRL+ALT+F1 etc doenst do anything too :/
I ssh'd in and got this off /var/log/messages:
this is from startup: | Code: | Apr 18 23:20:28 dorm Freeing unused kernel memory: 196k freed
Apr 18 23:20:28 dorm Adding 755044k swap on /dev/hda2. Priority:-1 extents:1 across:755044k
Apr 18 23:20:28 dorm nvidia: module license 'NVIDIA' taints kernel.
Apr 18 23:20:28 dorm ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 217
Apr 18 23:20:28 dorm PCI: Setting latency timer of device 0000:05:00.0 to 64
Apr 18 23:20:28 dorm NVRM: loading NVIDIA Linux x86_64 Kernel Module 1.0-8756 Wed Mar 29 15:12:41 PST 2006
Apr 18 23:20:29 dorm skge eth0: enabling interface |
and this is from the time of the problem
| Code: | | Apr 19 00:00:06 dorm NVRM: Xid (0005:00): 6, PE0000 0400 fff6f2e9 0000fd20 ffffffff 00010001 |
top shows me: | Code: | | 32434 root 25 0 52284 22m 4080 R 82.6 4.5 3:33.70 X |
EDIT2:
I've changes some kernel options and made sure my config matches this one: | Code: | Loadable Module Support --->
[*] Enable loadable module support
[*] Module unloading
Processor type and features --->
[*] MTRR (Memory Type Range Register) support
Device Drivers --->
Character Devices --->
< > /dev/agpgart (AGP Support)
[ ] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
Kernel Hacking --->
[ ] Kernel debugging |
I hope that fixes it - im recompiling and then re-emerging the nvidia-kernel |
|
| Back to top |
|
 |
luckyman
n00b
Joined: 19 Jan 2005
Posts: 15
Location: Nitra
|
| Posted: Wed Apr 19, 2006 12:30 am Post subject: |
|
|
| could you show us your xorg.conf? |
|
| Back to top |
|
|
m4rku5
n00b
Joined: 18 Apr 2006
Posts: 29
|
| Posted: Wed Apr 19, 2006 1:11 am Post subject: |
|
|
| Code: | # File generated by xorgconfig.
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# 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.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mouse0"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Option "ZAxisMapping" "4 5"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Belinea"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 30 - 64
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-80
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "nVidia GeForce 6600"
Driver "nvidia"
VideoRam 131072
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "nVidia GeForce 6600"
Monitor "Belinea"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection |
|
|
| Back to top |
|
|
luckyman
n00b
Joined: 19 Jan 2005
Posts: 15
Location: Nitra
|
| Posted: Thu Apr 20, 2006 10:47 am Post subject: |
|
|
Hi,
what if you use driver, is everything working well?
because I use radeon card I can't experiment on it with you, but
if the vesa driver works well
then:
have a look on the gentoo-wiki site > nvidia
check your use flags, emerge the world (if changes: -pv)
and search for the same card on this forum
thats all I can help you, good luck |
|
| Back to top |
|
|
energyman76b
Advocate
Joined: 26 Mar 2003
Posts: 2048
Location: Germany
|
| Posted: Thu Apr 20, 2006 11:33 am Post subject: |
|
|
Hi,
he has Xids - there is not much he can do.
Got to the nvidia forum.
Post to the Xid thread or open a new one, attach the output of nvidia-bug-report.sh.
A lot of Xids are caused by shitty card-bios or insufficient cooling.
_________________
Study finds stunning lack of racial, gender, and economic diversity among middle-class white males
I identify as a dirty penismensch. |
|
| Back to top |
|
|
brankob
Apprentice
Joined: 29 Apr 2004
Posts: 188
|
| Posted: Thu Apr 20, 2006 1:50 pm Post subject: |
|
|
Your xorg.conf seems to be fine, except for the fact that you have defined 2 graphic cards: your GF6600GT and ordinary VGA. SInce there is no screen with VGA card defined, it shouldn't be used, but nevertheless IIWY I would delete/comment out the lines:
| Quote: |
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
|
I think it would be also wise to check:
- RAM: use memtest and do extended set of tests
- your use flags and CFLAGS
- check compiler versaion with gcc-config -l
- "do revdep-rebuild" and see if there is something broken.
- reemerge QT and KDE
- check your hardware. Is vent on the graphic card working ? Is it firmly in the slot ? Is it faulty ? |
|
| Back to top |
|
|
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20067
|
| Posted: Thu Apr 20, 2006 3:25 pm Post subject: |
|
|
| m4rku5 wrote: | | Code: | Identifier "nVidia GeForce 6600"
Driver "nvidia" |
|
Instead of nvidia, try nv. It may at least get you running, if not how you'd like.
_________________
Quis separabit? Quo animo? |
|
| Back to top |
|
|
m4rku5
n00b
Joined: 18 Apr 2006
Posts: 29
|
| Posted: Sun Apr 23, 2006 6:44 pm Post subject: |
|
|
hey guys sry i couldnt reply for some time i had porblems with my ISP - anyways im back
i have some new info that is weird: when i startx with fluxbox as WM i dont get that lockup - so it seems to be something with KDE |
|
| Back to top |
|
|
m4rku5
n00b
Joined: 18 Apr 2006
Posts: 29
|
| Posted: Sun Apr 23, 2006 6:49 pm Post subject: |
|
|
| brankob wrote: |
I think it would be also wise to check:
- RAM: use memtest and do extended set of tests
- your use flags and CFLAGS
- check compiler versaion with gcc-config -l
- "do revdep-rebuild" and see if there is something broken.
- reemerge QT and KDE
- check your hardware. Is vent on the graphic card working ? Is it firmly in the slot ? Is it faulty ? |
1. my DFI NF4 Mainboard has memtest86 included and i had it running for several hours and it came up with no errors
2. could you tell me what (C)flags i should/shouldnt use?
3.4. / will do in a bit
5. will try that later - it might really be me KDE as other WMs dont cause this lockup
6. graphic card vent is working - its running smoothly under windows 2000 (on other HDD) |
|
| Back to top |
|
|
brankob
Apprentice
Joined: 29 Apr 2004
Posts: 188
|
| Posted: Sun Apr 23, 2006 6:57 pm Post subject: |
|
|
safest CFLAGS are "-march=opteron -O2 -pipe"
Everything else is a gamble. Might work perfectly for someone else, but cause problems for you.
Slight deviations are probably not detrimental, but some weird options might casue you grief.
Same with compiler version. 4.x is for a people who love to experiment...
Even thought ALMOST everything is working with new compilers, if there are problems, they usually crop up in KDE... |
|
| Back to top |
|
|
m4rku5
n00b
Joined: 18 Apr 2006
Posts: 29
|
| Posted: Sun Apr 23, 2006 7:08 pm Post subject: |
|
|
| Code: | dorm ~ # gcc-config -l
[1] x86_64-pc-linux-gnu-3.4.4 *
[2] x86_64-pc-linux-gnu-3.4.4-hardened
[3] x86_64-pc-linux-gnu-3.4.4-hardenednopie
[4] x86_64-pc-linux-gnu-3.4.4-hardenednopiessp
[5] x86_64-pc-linux-gnu-3.4.4-hardenednossp |
| Code: | CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j2"
USE="-gtk -gnome qt kde alsa" |
running revdep-rebuild -p atm ill post results in a bit
*edit* | Code: | | Dynamic linking on your system is consistent... All done. |
Btw: I still guess its something with KDE cause other WMs dont cause that lockup
so best thing to do is reemerge KDE ? |
|
| Back to top |
|
|
m4rku5
n00b
Joined: 18 Apr 2006
Posts: 29
|
| Posted: Mon Apr 24, 2006 7:15 pm Post subject: |
|
|
Well ive tried anything except remerging KDE now - BUT i had that lockup with another WM but opposite to KDE it doenst instandly lockup but only somtetimes - so im back to its a nvdia/X problem or something 
Btw what about that Xid: what does that mean ? |
|
| Back to top |
|
|
energyman76b
Advocate
Joined: 26 Mar 2003
Posts: 2048
Location: Germany
|
| Posted: Tue Apr 25, 2006 10:39 pm Post subject: |
|
|
Xid are GPU errors. Caused by driver problems or overheating or voltage fluctuations. Sometimes the cards bios is the culprit, but most of the time it is a temperature or voltage problem.
Please, pretty please, check your cooling. Have you cleaned the fans? Have you measured the temperatures, when the lockups occur? Do you have tried a different PSU?
_________________
Study finds stunning lack of racial, gender, and economic diversity among middle-class white males
I identify as a dirty penismensch. |
|
| Back to top |
|
|
m4rku5
n00b
Joined: 18 Apr 2006
Posts: 29
|
| Posted: Wed Apr 26, 2006 3:00 pm Post subject: |
|
|
The cooling is fine imo - its about 40-50°C (2D[linux - vesa driver] / Playing games[windows - nvidia driver])
I havent tried anohter PSU (I dont know if 3.27V 5.05V and 11.71V for 3.3V 5V and 12V are that bad) but I wanted to get a new PSU anyways.
And im going to post the nvidia bug log @ the nvidia linux forums later when i got some free time.
Btw - anyone thinking recompiling X/KDE might help (I dont think so atm since even other WMs cause X to use 99% CPU etc randomly - its just KDE doing that always with nvidia drivers) |
|
| Back to top |
|
|
m4rku5
n00b
Joined: 18 Apr 2006
Posts: 29
|
| Posted: Thu May 25, 2006 8:28 pm Post subject: |
|
|
hey guys i just tried new kernel and new nvidia drivers 8762 still the same problem :/
goin to post on the nvidia forums now maybe they can help |
|
| Back to top |
|
|
|
Gentoo on AMD64
