I've got an interesting problem when attempting to Suspend-to-RAM (S3) and virtual consoles. I swear, three days ago it was working and I didn't change anything (I don't think) at least that would change how this works (i.e. kernel, drivers, whatever)
With that said, here's my problem (and what I've tried): 1. If I initiate suspend-to-ram from a console itself, it suspends fine, resumes fine, but the screen is BLANK.I can type stuff, but for some reason when I reboot (i.e. typing reboot or Ctrl+Alt+Del, it freezes on some process and doesn't reboot -- I have to power cycle the computer by holding down the power button for 5 seconds). 2. If I initiate suspend-to-ram from X, it suspends fine, resumes fine and the X screen comes up. HOWEVER, if I then switch to a virtual console, it comes up blank. The same problem occurs when I reboot, however. 3. Suspend-to-disk works in both cases. And rebooting afterwards is also fine. To reiterate, I haven't changed anything that I believe to be low enough t cause problems with this... has anyone seen anything like it? I've tried things like adding acpi_sleep=s3_bios,s3_mode, etc to the kernel line in grub.conf, but that doesn't seem to be doing much. Attempting to blinding play with vbetool also doesn't do anything. Setting up the console in framebuffer mode also makes no difference. Any ideas? Thanks in advance. - Brian -- [EMAIL PROTECTED] mailing list
