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, 0000 02005600 00000056 00000c28 00230291 00000080 > > > > agpgart: Found an AGP 3.0 compliant device at 0000: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 0000:00:00.0 into 4x mode > > > > agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode > > > > agpgart: Found an AGP 3.0 compliant device at 0000: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 0000:00:00.0 into 4x mode > > > > agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode > > > > NVRM: Xid: 13, 0000 02005600 00000056 00000c28 00230291 00000080 > > > > agpgart: Found an AGP 3.0 compliant device at 0000: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 0000:00:00.0 into 4x mode > > > > agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode > > > > agpgart: Found an AGP 3.0 compliant device at 0000: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 0000:00:00.0 into 4x mode > > > > agpgart: Putting AGP V2 device at 0000: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.
