[gentoo-user] nvidia-driver crashes X
Hi! I'm experiencing some strange problems on one of my machines. Everytime I open the KDE Control Center and on random occasions in Firefox (sometimes after doing nothing for several minutes, just having it open in the background and switching back to it or when starting certain java scripts) the X-Server does no longer react. I can move the cursor but that's it. All I can do is open a remote shell. Top shows me that X is at 97-99% cpu usage and the only way to kill it is with kill -kill I've noticed the following in dmesg: NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode That's the situation after two crashes within a few minutes (I tried to open the Control Center). I'm using an NVidia Geforce2 MX with nvidia-drivers-1.0.7185. I'll attach the whole dmesg and lshw output as well as my xorg.conf. Thanks in advance! Florian Philipp By the way: Should I compress attachments? KMail offers automatic zip-compression. Section ServerLayout Identifier Layout0 Screen 0 Screen0 0 0 InputDeviceKeyboard0 CoreKeyboard InputDeviceMouse0 CorePointer EndSection Section Files EndSection Section Module Load freetype Load extmod Load glx Load dri Load dbe Load record Load xtrap Load type1 EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol Auto Option Device /dev/input/mice EndSection Section InputDevice Identifier Keyboard0 Driver kbd Option XkbModel logiitc Option XkbLayout de EndSection Section Monitor Identifier Monitor0 ### Comment all HorizSync and VertRefresh values to use DDC: HorizSync31.5 - 48.5 VertRefresh 50.0 - 70.0 Modeline 1280x768 80.1 1280 1344 1480 1680 768 770 786 795 EndSection Section Device Identifier Card0 Driver nvidia Option NVAgp 3 Option RenderAccel true Option AllowGLXWithComposite true Option TripleBuffer true Option DPMS TRUE Option NoLogo true VideoRam32768 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 Modes1280x768 EndSubSection EndSection Section DRI Group0 Mode 0666 EndSection 0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 (Bootup-CPU) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Nosave address range: 0009f000 - 000a Nosave address range: 000a - 000cc000 Nosave address range: 000cc000 - 000d6000 Nosave address range: 000d6000 - 000f Nosave address range: 000f - 0010 Allocating PCI resources starting at 7000 (gap: 6000:9ec0) Built 1 zonelists. Total pages: 386736 Kernel command line: Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) time.c: Detected 2000.104 MHz processor. Console: colour VGA+ 80x25
Re: [gentoo-user] nvidia-driver crashes X
On Montag, 13. August 2007, Florian Philipp wrote: Hi! I'm experiencing some strange problems on one of my machines. Everytime I open the KDE Control Center and on random occasions in Firefox (sometimes after doing nothing for several minutes, just having it open in the background and switching back to it or when starting certain java scripts) the X-Server does no longer react. I can move the cursor but that's it. All I can do is open a remote shell. Top shows me that X is at 97-99% cpu usage and the only way to kill it is with kill -kill I've noticed the following in dmesg: NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode That's the situation after two crashes within a few minutes (I tried to open the Control Center). I'm using an NVidia Geforce2 MX with nvidia-drivers-1.0.7185. I'll attach the whole dmesg and lshw output as well as my xorg.conf. Thanks in advance! Florian Philipp By the way: Should I compress attachments? KMail offers automatic zip-compression. first, update you bios. Pull out the card, dust the case, put the card back, retry. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] nvidia-driver crashes X
Am Montag 13 August 2007 15:14:18 schrieb Volker Armin Hemmann: On Montag, 13. August 2007, Florian Philipp wrote: Hi! I'm experiencing some strange problems on one of my machines. Everytime I open the KDE Control Center and on random occasions in Firefox (sometimes after doing nothing for several minutes, just having it open in the background and switching back to it or when starting certain java scripts) the X-Server does no longer react. I can move the cursor but that's it. All I can do is open a remote shell. Top shows me that X is at 97-99% cpu usage and the only way to kill it is with kill -kill I've noticed the following in dmesg: NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode That's the situation after two crashes within a few minutes (I tried to open the Control Center). I'm using an NVidia Geforce2 MX with nvidia-drivers-1.0.7185. I'll attach the whole dmesg and lshw output as well as my xorg.conf. Thanks in advance! Florian Philipp By the way: Should I compress attachments? KMail offers automatic zip-compression. first, update you bios. Pull out the card, dust the case, put the card back, retry. Bios is updated to the last stable release. The latest beta (for almost 2 years now) crashes badly. The system was build less than two months ago and should not contain much dust. Anyway, it's got no fan at all but I've taken care of possible heat problems. I'll check the bios settings, maybe permanently limiting it to AGP2x helps. I've forgotten to mention that the card works flawlessly with the nv driver. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] nvidia-driver crashes X
On Montag, 13. August 2007, Florian Philipp wrote: Am Montag 13 August 2007 15:14:18 schrieb Volker Armin Hemmann: On Montag, 13. August 2007, Florian Philipp wrote: Hi! I'm experiencing some strange problems on one of my machines. Everytime I open the KDE Control Center and on random occasions in Firefox (sometimes after doing nothing for several minutes, just having it open in the background and switching back to it or when starting certain java scripts) the X-Server does no longer react. I can move the cursor but that's it. All I can do is open a remote shell. Top shows me that X is at 97-99% cpu usage and the only way to kill it is with kill -kill I've noticed the following in dmesg: NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode That's the situation after two crashes within a few minutes (I tried to open the Control Center). I'm using an NVidia Geforce2 MX with nvidia-drivers-1.0.7185. I'll attach the whole dmesg and lshw output as well as my xorg.conf. Thanks in advance! Florian Philipp By the way: Should I compress attachments? KMail offers automatic zip-compression. first, update you bios. Pull out the card, dust the case, put the card back, retry. Bios is updated to the last stable release. The latest beta (for almost 2 years now) crashes badly. The system was build less than two months ago and should not contain much dust. Anyway, it's got no fan at all but I've taken care of possible heat problems. I'll check the bios settings, maybe permanently limiting it to AGP2x helps. I've forgotten to mention that the card works flawlessly with the nv driver. yeah, because nv does not really stress the card and bus. Such signaling or power problems are masked away. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] nvidia-driver crashes X
Am Montag 13 August 2007 16:06:50 schrieb Volker Armin Hemmann: On Montag, 13. August 2007, Florian Philipp wrote: Am Montag 13 August 2007 15:14:18 schrieb Volker Armin Hemmann: On Montag, 13. August 2007, Florian Philipp wrote: Hi! I'm experiencing some strange problems on one of my machines. Everytime I open the KDE Control Center and on random occasions in Firefox (sometimes after doing nothing for several minutes, just having it open in the background and switching back to it or when starting certain java scripts) the X-Server does no longer react. I can move the cursor but that's it. All I can do is open a remote shell. Top shows me that X is at 97-99% cpu usage and the only way to kill it is with kill -kill I've noticed the following in dmesg: NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode That's the situation after two crashes within a few minutes (I tried to open the Control Center). I'm using an NVidia Geforce2 MX with nvidia-drivers-1.0.7185. I'll attach the whole dmesg and lshw output as well as my xorg.conf. Thanks in advance! Florian Philipp By the way: Should I compress attachments? KMail offers automatic zip-compression. first, update you bios. Pull out the card, dust the case, put the card back, retry. Bios is updated to the last stable release. The latest beta (for almost 2 years now) crashes badly. The system was build less than two months ago and should not contain much dust. Anyway, it's got no fan at all but I've taken care of possible heat problems. I'll check the bios settings, maybe permanently limiting it to AGP2x helps. I've forgotten to mention that the card works flawlessly with the nv driver. yeah, because nv does not really stress the card and bus. Such signaling or power problems are masked away. I still suspect a driver issue because I never had any problems on Windows. Anyway, if it makes you happy, I'll check it for connection problems as soon as possible (maybe tomorrow). But hardware problems can't explain why I can use it for office, watching DVDs, GoogleEarth and such like for hours while starting KDE's Control Panel crashes it immediately every time I try it. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] nvidia-driver crashes X
On Montag, 13. August 2007, Florian Philipp wrote: Am Montag 13 August 2007 16:06:50 schrieb Volker Armin Hemmann: On Montag, 13. August 2007, Florian Philipp wrote: Am Montag 13 August 2007 15:14:18 schrieb Volker Armin Hemmann: On Montag, 13. August 2007, Florian Philipp wrote: Hi! I'm experiencing some strange problems on one of my machines. Everytime I open the KDE Control Center and on random occasions in Firefox (sometimes after doing nothing for several minutes, just having it open in the background and switching back to it or when starting certain java scripts) the X-Server does no longer react. I can move the cursor but that's it. All I can do is open a remote shell. Top shows me that X is at 97-99% cpu usage and the only way to kill it is with kill -kill I've noticed the following in dmesg: NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode NVRM: Xid: 13, 02005600 0056 0c28 00230291 0080 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 x1 agpgart: Device is in legacy mode, falling back to 2.x agpgart: Putting AGP V2 device at :00:00.0 into 4x mode agpgart: Putting AGP V2 device at :01:00.0 into 4x mode That's the situation after two crashes within a few minutes (I tried to open the Control Center). I'm using an NVidia Geforce2 MX with nvidia-drivers-1.0.7185. I'll attach the whole dmesg and lshw output as well as my xorg.conf. Thanks in advance! Florian Philipp By the way: Should I compress attachments? KMail offers automatic zip-compression. first, update you bios. Pull out the card, dust the case, put the card back, retry. Bios is updated to the last stable release. The latest beta (for almost 2 years now) crashes badly. The system was build less than two months ago and should not contain much dust. Anyway, it's got no fan at all but I've taken care of possible heat problems. I'll check the bios settings, maybe permanently limiting it to AGP2x helps. I've forgotten to mention that the card works flawlessly with the nv driver. yeah, because nv does not really stress the card and bus. Such signaling or power problems are masked away. I still suspect a driver issue because I never had any problems on Windows. Anyway, if it makes you happy, I'll check it for connection problems as soon as possible (maybe tomorrow). But hardware problems can't explain why I can use it for office, watching DVDs, GoogleEarth and such like for hours while starting KDE's Control Panel crashes it immediately every time I try it. because of the Xid. From the part in your mail it looks like you get your first one as soon as X starts. And after a Xid the gpu is in a highly unstable condition. You can post your problem in the nvnews-forum. Maybe you'll find some help there. -- [EMAIL PROTECTED] mailing list
