|
|
#1 | |
|
Registered User
Join Date: Mar 2012
Posts: 4
|
Had major problems with 295.20-1 with suspend/shutdown/logout and even stopping gdm or the X server. After downgrading back to 290.10-1 suspend/resume work fine again.
I recently (26 Feb) upgraded from 290.10-1 to 295.20-1 on my laptop (HP 8440p with a NVS 3100M graphics system) using the packages for 295.20-1 from debian testing. My system is mostly debian stable, but with some packages from debian testing. On 27 Feb I stopped X, removed the module and then restarted X when I recalled that I had not done so immediately after the upgrade. Between the upgrade and loading the new module - the system was able to suspend and resume properly! Since then I have had multiple problems, all which seem related to the Nvidia 295.20-1 driver.
In all cases of the "crash" the laptop power would stay ON, the fan was pushing warm air out, and the system would not respond to keyboard at all. Network connections also failed or were dropped - even when the connection was live and working a few seconds before the change. The system would not respond to "ping" anymore either. After every crash and hard-reset, my /home partition was "unclean" and in quite a few cases there were messed up files (multiply claimed blocks, unused inodes, etc.) On the attempt to suspend - daemon.log shows that NetworkManager received the request to sleep, but kern.log did not get the messages "PM: Syncing filesystems ... done." or "PM: Preparing system for mem sleep" which show up as the suspend process is being done. I tried to "sleep 5; nvidia-bug-report.sh" in one remote session, and then run "/etc/init.d/gdm3 stop" to see if I could get debugging data while the "crash" was occuring. That was not successful. Instead, I could only attach a "nvidia-bug-report.log.gz" file which was generated after starting x from a remote console with "startx -- -logverbose 6" and before initiating a crash. Bottom line - at least on my machine the 295.20-1 driver makes a total mess of things on my machine. Ref: files on Debian BTS also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661822 Last edited by taniwallach; 03-01-12 at 12:03 PM. Reason: Added reference to bug report in Debian BTS |
|
|
|
|
|
|
#2 | |
|
NVIDIA Corporation
Join Date: Dec 2010
Posts: 259
|
Did you tried reinstalling nvidia driver after OS packages upgrade from ftp://download.nvidia.com/XFree86/Linux-x86_64/?
|
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Mar 2012
Posts: 4
|
Now I did - hope the time spend testing this helps.
NOTE: I uninstalled all the Debian NVIDIA packages (necessary to allow a manual nVidia driver install), then downloaded and installed 295.20 from NVIDIA site. (Needed "-e" for export mode to bypass the pre-install script which was causing a SIGTERM and failure to compile/install). Had the same hard freeze/crash problems as before (network/keyboard all dead) which forced a hard power cycle. Each reboot needed a fsck of /home which was not properly unmounted. I did not spend any time testing stability, just that the X server started and would crash the system when stopped. Try 1: Start "gdm3" (started up) and then stop it. Crashed system when I stopped gdm3. Try 2: I ran "startx -- -logverbose 6" and then "nvidia-bug-report.sh". This time the splinning icon of loading stuck and I still managed to run "nvidia-bug-report.sh". When I killed X - a system freeze. The bug report from this try is the small attached file called nvidia-bug-report-try2.log.gz. Try 3: I ran "startx -- -logverbose 6" and then "nvidia-bug-report.sh". This time the splinning icon of loading stuck and I still managed to run "nvidia-bug-report.sh". When I killed X - a system freeze. The bug report from this try is the larger attached file called nvidia-bug-report.log.gz. NOTE: switching to Virtual Terminals from X screen - does NOT work. Screen is just solid black. Once again I switched back to the Debian 290.10-1 packages, which work fine. |
|
|
|
|
|
#4 | |
|
Registered User
Join Date: Nov 2006
Posts: 5
|
I have exactly the save problem here on Fedora 16 with kernel 3.2.10-3.i686 on my old laptop with a 8400m GS card.
When I switch back to 290.10, this problem goes away. But this problem never shows up on my desktop computer with a GT520 graphics card. |
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Mar 2012
Posts: 4
|
Problems seem to be resolved in 295.59. There was still trouble with 295.40, but did not test 295.49 or 295.53.
Both suspend/restore and switch to VT and then back to X now work and don't hard-freeze my machine. Can be marked are resolved - in my opinion. Nathan |
|
|
|
|
|
#6 | |
|
NVIDIA Corporation
Join Date: Dec 2010
Posts: 259
|
I think VT switch console broken issue will resolve by passing kernel parameter vga=0
|
|
|
|
|
![]() |
| Thread Tools | |
|
|