ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #105276
[Bug 685727] Re: When i upgraded to 10.10 the screen on my laptop(Gateway nv79) went completely black and I could not see anything unless I held a flashlight to the screen to see. The only way I am able to fix this is issue is by doing a system test. But as soon as my laptop goes to sleep it goes back to the black screen. I could not find another fix because once I did the system testing for 10.10 it would not allow me to do the testing again to fix it.
I have the same problem upgrading from 10.04 to 10.10 on my Gateway
NV79. Booting with kernel 2.6.35-24 has this problem. Booting with
2.6.32.27 (the previous kernel for 10.04?) at least gets me back to a
working display.
Here's a description of when the issue occurs during booting:
At first, for a while, a single "_" appears in the upper left of display. Then a single line status message appears very briefly (less than 1 second) and it is difficult to recall what it says .. something about intel and 0.0.0.0.
Then when the display goes black with an audible sound of a switch
clicking .. same sound occurs during normal boot when it precedes the
display showing a full xserver service occuring. I suspect that either
the display chip has been turned off or (more likely) the display itself
has been turned off (or just the backlight?).
I cannot figure out any other settings that I can adjust. Please advise
a work-around or patch this quickly. Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/685727
Title:
When i upgraded to 10.10 the screen on my laptop(Gateway nv79) went
completely black and I could not see anything unless I held a
flashlight to the screen to see. The only way I am able to fix this is
issue is by doing a system test. But as soon as my laptop goes to
sleep it goes back to the black screen. I could not find another fix
because once I did the system testing for 10.10 it would not allow me
to do the testing again to fix it.
References