|
|
#1 | |
|
Registered User
Join Date: Nov 2008
Posts: 7
|
Hi,
although giving me a performance boost for KDE4 , the new 180.* nvidia drivers are unusable to me. After a random time my WHOLE screen becomes corrupted, the picture flickers and i can no longer use the system, cant even forcefully restart X , i have to kill the whole system by force. This happend to me on a x86 and a amd64 installation on the same notebook. with the 177.* drivers i doesnt happen to me and i can use my notebook for hours without any problems. |
|
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Jun 2008
Posts: 51
|
same here (180.xx unusable).
maybe this has something to do with: http://www.nvnews.net/vbulletin/showthread.php?t=123729 (http://www.nvnews.net/vbulletin/show...74&postcount=8) iirc the problem is: Quote:
for me this also happens with 177.82 but only causes a temporary freeze (and no corruption) (also annoying). (bug report created with 177.82, can create one with 180.xx if needed) |
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Dec 2006
Posts: 72
|
i had randomly dead-freeze too (sometimes 3 freeze in 5 mn ! 30 per day i became completely silly), textures corruption, flickering display, hard reboot, nothing with the 177.xx serie...etc... but at the moment i've installed a flash-blocker in mozilla( firefox was always launch with mini 1 flash animation on a tab all the day ex deezer), no more freeze ! one per day max !!
and when i deactivate flash blocker for some flash site - 30 sec and freeze ! hope it can be so simple for you ! |
|
|
|
|
|
#4 | |
|
openSuSE11
Join Date: Aug 2005
Location: Europe, Slovenia, Koper
Posts: 515
|
I can confirm this too - 7600GT, display flickers, becomes corrupted and one time it went black and never recovered (applications were still working in bg).
Last edited by kriko; 05-31-11 at 01:34 PM. |
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Feb 2005
Posts: 84
|
nvidia driver 180.11
vga 8300 MGPU xorg-x11 server 1.5.3 xorg-x11-drv-evdev-2.1.0-1 WindowManager : compiz-0.7.8 GNOME Desktop 2.24.2 Code:
$ cat /var/log/Xorg.0.log [skip] Mouse? 1.0A" (type: MOUSE) (II) NVIDIA(0): Initialized GPU GART. (II) NVIDIA(0): Initialized GPU GART. (II) NVIDIA(0): Initialized GPU GART. [mi] EQ overflowing. The server is probably stuck in an infinite loop. Backtrace: 0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812bc5b] 1: /usr/bin/Xorg(mieqEnqueue+0x289) [0x810b379] 2: /usr/bin/Xorg(xf86PostMotionEventP+0xc2) [0x80d4262] 3: /usr/bin/Xorg(xf86PostMotionEvent+0x68) [0x80d43c8] 4: /usr/lib/xorg/modules/input//evdev_drv.so [0x4d54d05] 5: /usr/bin/Xorg [0x80bcdb7] 6: /usr/bin/Xorg [0x80ac91e] 7: [0x130400] 8: /usr/lib/xorg/modules/drivers//nvidia_drv.so(_nv001298X+0x3eb) [0x40ee11b] [mi] mieqEnequeue: out-of-order valuator event; dropping. [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] mieqEnequeue: out-of-order valuator event; dropping. [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] mieqEnequeue: out-of-order valuator event; dropping. [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] mieqEnequeue: out-of-order valuator event; dropping. [skip] Code:
$ dmesg [skip] NVRM: Xid (0002:00): 13, 0001 00000000 0000502d 0000060c 00000083 00000100 NVRM: Xid (0002:00): 13, 0001 00000000 0000502d 000008dc 00000000 00000100 NVRM: Xid (0002:00): 13, 0001 00000000 0000502d 000008dc 00000000 00000040 NVRM: Xid (0002:00): 13, 0003 00000000 00008397 00001b0c 1000f010 00000040 NVRM: Xid (0002:00): 13, 0003 00000000 00008397 00001310 00000000 00000040 NVRM: Xid (0002:00): 13, 0003 00000000 00008397 00001b0c 1000f010 00000040 NVRM: Xid (0002:00): 13, 0003 00000000 00008397 00001310 00000000 00000040 NVRM: Xid (0002:00): 13, 0003 00000000 00008397 00001b0c 1000f010 00000040 Last edited by sangu; 04-22-11 at 08:15 PM. |
|
|
|
|
|
#6 | |
|
Registered User
Join Date: Jun 2007
Location: Orléans (france)
Posts: 24
|
Hello,
I have the same problem on Ubuntu 8.10 64bits with a 8600M GT and the last beta drivers (180.11) |
|
|
|
|
|
|
#7 | |
|
Gentoo Linux addict
Join Date: Nov 2007
Location: Vienna, Austria; Germany; hello world :)
Posts: 202
|
Quote:
which nspluginwrapper, which flash version, which OS / architecture, kernel ... more details please, this should help the guys over at nvidia to (hopefully) reproduce and asap fix it ![]() @kriko: strangely it's all fine here with my 7600GT (from MSI), could you provide some steps to produce so I can see whether I can make it corrupt the screen, too ?
__________________
2.6.30-rc3-zen0+ w. compcache, reiser4 + ccreg40 (lzo-compression + checksumming) ![]() gcc version 4.4.0-pre9999 built 20090425 (prerelease) rev. 146764 (Gentoo SVN) gcc version 4.4.0 (Gentoo Hardened 4.4.0-r1, espf-0.2.1) Ubuntu Jaunty/9.04 x86_64 Dell XPS M1330 |
|
|
|
|
|
|
#8 |
|
Registered User
Join Date: Nov 2008
Posts: 7
|
|
|
|
|
|
|
#9 |
|
Registered User
Join Date: May 2004
Posts: 1
|
Yep, that's exactly what I see. No compiz, just stock Ubuntu 8.10 Gnome install. Usually happens when I'm running an application which is doing OpenGL calls, but also have seen this happening when just scrolling in Firefox 3 or even moving a terminal window on the desktop. Had this happen with stock nvidia-177 installed with ubuntu and now with 180.11 downloaded and installed from nvidia website.
The display will normally freeze for a few seconds, although the mouse still moves. Then the mouse also freezes for up to 30 seconds, with about a 1/2 to 1 second interval where it will update. I have not had any hard freezes on this; it usually recovers anywhere from 2 to 7 minutes later. |
|
|
|
|
|
#10 |
|
Registered User
Join Date: Dec 2008
Posts: 23
|
I have the same exact problem... X server locks up but mouse still moves, then it recovers after about 30 seconds... sometimes with screen corruption. Dmesg shows NVRM: Xid errors. For me, it only happens when using compositing or openGL. If I don't use those, everything works perfectly with no crashes or freezes. And the thing is, I can reboot to XP and play Crysis for hours with no issues. So it's almost certainly not a heat issue or a bad card. The same freezes occur when I switch out my 8800GT with my old 7800GT.
I have read several threads on this issue, and usually they end up telling you that if you get Xid errors, then your card is bad and you need a new one. But it seems like there are way too many people having this problem with the exact same symptoms. BTW, I even tried switching my motherboard because I thought my PCIE bus might have been bad, and it didn't help. The only thing that works for me is disabling compositing and avoiding openGL apps. I've tried all the suggested fixes and nothing works. I'm convinced this is a driver issue that nvidia needs to seriously look into. |
|
|
|
|
|
#11 |
|
Registered User
Join Date: Dec 2008
Posts: 23
|
Well, I seem to have found a workaround for my system. I have 2x2Gb memory modules which were installed in dual channel mode. When I removed one stick of memory, everything worked fine. So then I wanted to see if it was the actual amount of memory or just the fact that it was running in single channel with one stick. So I reinstalled the second module in a single channel configuration, and now everything works fine. No more freezes or Xid errors. Somehow, running 4gb of RAM in dual channel mode on a 32bit kernel was causing the problem. I'm happy that it works now, but I'm still not happy that I have to run single channel mode. I'm not sure if this is an nvidia problem or a kernel problem or an X server problem, but I really hope it gets fixed soon.
|
|
|
|
|
|
#12 |
|
Registered User
Join Date: Dec 2008
Posts: 23
|
I just updated my video card's bios to the latest version, and it didn't change anything. 4gb in single channel mode works flawlessly, with memory at stock 800mhz or overclocked to 1066mhz. But as soon as I move the memory to dual channel, even at stock speeds, I get Xid errors and freezes without a doubt.
What is it about a dual channel memory configuration that would cause this? Anyone else who is having this problem... try running your memory in single channel and let us know if that fixes it. |
|
|
|
![]() |
| Thread Tools | |
|
|