Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Thread Tools
Old 03-02-08, 03:42 PM   #1
Registered User
Join Date: May 2007
Posts: 13
Unhappy 169.12: X still can't be restarted in a resumed system

Version 169.12 still crashes my system if X gets restarted in a resumed system (which happens as soon as you log out from a GDM managed X session). The screen turns black and although there is still some hard disk activity, it isn't possible to log in via SSH anymore. Existing SSH sessions freeze immediately as well. That's why I can't provide a postmortem report log. There is no such issue with the open "nv" driver from X.org, so it's definitely triggered by the commercial driver.

I've attached two bug report logs. One which has been created after logging in (before a suspend) and one which has been made directly after awakening the machine.

In case you experience some form of deja vu: Yes, I wrote a quite similar bug report two months ago. Since I haven't got an answer, yet, I presume that either this bug is very hard to fix or nobody really cared What exactly can be done to support the debugging process of this issue?

Hardware: Dell Latitude D620, Quadro NVS 110M, Core 2 Duo T7200, i945PM, 2GB RAM (Dual Channel), latest BIOS (A09) is installed
Software: Ubuntu 8.04-alpha (i386 arch), stock kernel 2.6.24-11-generic, X.org server, prepackaged Nvidia driver (169.12)
Attached Files
File Type: gz nvidia-logs.tar.gz (52.4 KB, 96 views)
Tunix is offline   Reply With Quote
Old 03-26-08, 11:44 PM   #2
Registered User
Join Date: May 2007
Posts: 13
Lightbulb Re: 169.12: X still can't be restarted in a resumed system

It seems I have solved the problem, although the solution is rather odd. If the BIOS setup is locked by a password, restarting the X Server fails on a resumed system. If I remove the password, restarting X works. I found this out by accident. After reading through a backlight related device information file for HAL, I stumbled across a comment which recommends the removal of any BIOS passwords in order to make backlight brightness controllable by software. The reason is that the backlight of my Dell Latitude isn't controlled by ACPI but by SMBIOS which is somehow "protected" by these passwords. It looks like setting a password also has side effects on the suspend process of the video hardware. Placing voodoo dolls around my laptop couldn't be odder...
Tunix is offline   Reply With Quote

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
UEFI+Nvidia - NVRM: Your system is not currently configured to drive a VGA console... interzoneuk NVIDIA Linux 0 06-26-12 04:51 AM
PhysX System Software 9.12.0604 News Archived News Items 0 06-18-12 09:50 PM
Max Payne 3 system requirements updated, new PC screenshots released News Archived News Items 0 05-28-12 06:49 AM
Ars Technica system guide: Bargain Box April 2012 News Archived News Items 0 05-10-12 10:30 PM
Strange RedHat 7.3 issues with A7N266-C nforceuser NVIDIA Linux 8 09-27-02 03:16 PM

All times are GMT -5. The time now is 07:51 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2015, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.