[hardy] Blank screen when starting the system after shutdown

I just want to add that this is in Ubuntu Fiesty Fawn 7.04

try ones from konsole:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install xserver-xorg-video-intel

set "Driver" in xorg.conf to "intel"

then restart system or restart xserver

pet

Ok I have updated my driver from xserver-xorg-video-i810 to xserver-xorg-video-intel and I think my problem is solved(but I will try for 1 or 2 days just to make sure) and the biggest change was the resolution and that is now I have 1152x864 resolution(I like to work in as high resolution as possible) instead of just 1024x768 resolution which I was getting in i810 driver.

But now the login screen is coming in 800x600 resolution and then when I login the resolution will change to 1152x864 resolution. In i810 driver the resolution was 1024x768 for both the login screen and the desktop.

Please attach your xorg.conf.

Thanks for letting us know the original problem has been solved. Sorry to hear the resolution didn't get detected correctly, however we would need additional files (/var/log/Xorg.0.log and /etc/X11/xorg.conf) to troubleshoot that. Since it's been half a year since your last response, I'm assuming you've sorted out a solution, but if not please feel free to re-open this bug with the requested information.

I have this problem on latest hardy.
To reproduce : restart the system and be sure no console mode switch occurs during boot until kdm starts. You have a blank screen then.
Only switching in console mode then back to graphic mode makes the correct screen appear.
It seems to be a graphic display initialisation problem.

I have a laptop with the same xorg driver but cannot reproduce there since just before X starts there is a brief switch to console mode due to a couple of console messages showing.

dpkg -l xserver-xorg-video-intel*|grep ii
ii xserver-xorg-video-intel 2:2.2.1-1ubuntu12 X.Org X server -- Intel i8xx, i9xx display driver
ii xserver-xorg-video-intel-dbg 2:2.2.1-1ubuntu12 X.Org X server -- Intel i8xx, i9xx display driver

ii xserver-xorg 1:7.3+10ubuntu8 the X.Org X server
ii xserver-xorg-core 2:1.4.1~git20080131-1ubuntu7 Xorg X server - core server
ii xserver-xorg-core-dbg 2:1.4.1~git20080131-1ubuntu7

kernel 2.6.24-16-generic

Okay, can you please get a full backtrace after this happens? For directions on getting backtraces, see http://wiki.ubuntu.com/X/Backtracing

Well what do you want me to backtrace exactly ?
X is not crashed or freezed. It is only the display that is not showing anything.
Reproducing it several times I have this morning for example a completly red screen.

If I switch to console mode then to X, KDM will be displayed correctly.
It seems to be a problem when switching from bootsplash to X. And it seems random so maybe time dependent.

The bt when X is in this state is the following :
(gdb) bt full
#0 0xb7f69410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7db184d in select () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x081b2275 in WaitForSomething (pClientsReady=0xbfaf56d0) at ../../os/WaitFor.c:236
        i = <value optimized out>
        waittime = {tv_sec = 0, tv_usec = 288000}
        wt = (struct timeval *) 0xbfaf5690
        timeout = <value optimized out>
        clientsReadable = {fds_bits = {0 <repeats 32 times>}}
        clientsWritable = {fds_bits = {138251984, 136421032, -1079028280, 134814362, 136163204,
    138227056, -1079028280, 135624344, 138251984, 138235008, -1079028264, 136163204, 136163204, 0,
    -1079028232, 135625376, 138227056, -1079028240, -1079028200, 135595231, 136340232, 136630248, 0,
    136163204, 64, 138143360, -1079028152, 135639632, 138227056, 64, -1079028168, 4096}}
        curclient = <value optimized out>
        selecterr = 0
        nready = <value optimized out>
        devicesReadable = {fds_bits = {138234856, 0, -1079028440, 136022337, 138234856, 136163204,
    -1079028408, 135452948, 138234856, -1209872396, -1209867936, 138251984, -1079028360, -1210772240,
    -1209867936, 138251984, 138234856, 4194537, 138234872, 138251976, 136163204, 138234872,
    -1079028344, 136163204, 138251984, 138227056, -1079028344, 136022337, 138251984, 136163204,
    -1079028312, 135452948}}
        now = 166232
        someReady = 0
#3 0x0808d69d in Dispatch () at ../../dix/dispatch.c:425
        result = <value optimized out>
        client = (ClientPtr) 0x837d470
        nready = -1
        start_tick = 0
#4 0x0807471b in main (argc=8, argv=0xbfaf5c04, envp=0x0) at ../../dix/main.c:452
        i = 1
        error = 136163204
        xauthfile = <value optimized out>
        alwaysCheckForInput = {0, 1}
(gdb)

Hmm, then in that case the next thing to try would be to force the pipe-A enablement:

  Section "Device"
    ...
    Option "ForceEnablePipeA" "true"
  EndSection

If that makes it work, then please paste in the output of `lspci -vvnn | grep -A1 "VGA compat"`, and give the laptop model name and number

Re-closing bug. The original report has long since been fixed. Pascal, if you are still interested in troubleshooting your issue and can reproduce it on latest Intrepid, please file a NEW bug so we can look into it.