I have a similar problem. Sometimes (not always), after a suspend-resume cycle,
the display of my Thinkpad T23 stays black. I can bring it back only by doing
'vbetool dpms on'. (Actually, I just hit the lid switch and the video comes
back -- and I have modified /etc/apci/lid.sh to do dpms off/dpms on with
vbetool, as xset dpms does not turn the backlight off.)
The video on this beast is S3 SuperSavage IX/C, and I have SAVE_VBE_STATE=true,
POST_VIDEO=true, USE_DPMS=true, DOUBLE_CONSOLE_SWITCH=false. The interesting bit
is USE_DPMS=true: /etc/acpi/resume.sh already does 'vbetool dpms on', and I
don't know why I sometimes have to repeat the procedure.
To complicate matters further, the inverter on my laptop was dying recently --
sometimes it did not come up after a suspend, sometimes it just went off during
normal work. I sent the laptop to IBM for repairs under warranty, and when I
got it back, the tech said "I replaced something that might have been causing
the problem, try to use the laptop now, and if the problem persists, bring it
back". Since I switched from Debian to Ubuntu right after that, I am not sure
if this problem is caused by the hardware, or the software.
I have a similar problem. Sometimes (not always), after a suspend-resume cycle,
the display of my Thinkpad T23 stays black. I can bring it back only by doing
'vbetool dpms on'. (Actually, I just hit the lid switch and the video comes
back -- and I have modified /etc/apci/lid.sh to do dpms off/dpms on with
vbetool, as xset dpms does not turn the backlight off.)
The video on this beast is S3 SuperSavage IX/C, and I have SAVE_VBE_ STATE=true, CONSOLE_ SWITCH= false. The interesting bit
POST_VIDEO=true, USE_DPMS=true, DOUBLE_
is USE_DPMS=true: /etc/acpi/resume.sh already does 'vbetool dpms on', and I
don't know why I sometimes have to repeat the procedure.
To complicate matters further, the inverter on my laptop was dying recently --
sometimes it did not come up after a suspend, sometimes it just went off during
normal work. I sent the laptop to IBM for repairs under warranty, and when I
got it back, the tech said "I replaced something that might have been causing
the problem, try to use the laptop now, and if the problem persists, bring it
back". Since I switched from Debian to Ubuntu right after that, I am not sure
if this problem is caused by the hardware, or the software.