Suspend2ram on T22 [SOLVED]

Kate Monster · Posted: Sun Feb 04, 2007 3:41 am Post subject: Suspend2ram on T22 [SOLVED]

I have an IBM Thinkpad T22 laptop, and I have had suspend2disk working on it for awhile on it, but suspend2ram still does not work at all. Regardless of the method by which I suspend (I have tried hibernate-ram, s2ram, and just plain 'echo mem>/sys/power/state'), the system will go to sleep just fine, but upon resume, the screen comes back on, but nothing shows up. If I have X running, I can ctrl+f7 into it just fine, but I cannot switchback to the console. If I don't have X running, then nothing shows up on the screen. Either way, the system will not shutdown properly by any means. Trying to shut it down, or reboot it causes the screen to go blank, and the system to stop responding. My question is, has anyone with a T22 gotten suspend2ram to work?

Kate Monster · Posted: Mon Feb 05, 2007 5:38 pm Post subject:

Bump

I don't know if this is relevant, but problems with my soundcard (Crystal Semiconductor CS4263...i think) force me to boot with pci=routeirq, and compile ALSA as a module. I've heard that problems with suspending/resuming are many times caused by driver issues.

Kate Monster · Posted: Mon Feb 05, 2007 9:19 pm Post subject:

OK, I think I've almost got it. I switched on debugging, and turned off framebuffer so i can get access to the console, and i see that dmesg says "pnp: device 00:07 cannot be activated\ pnp:device 00:08 cannot be activated" after suspending/resuming. lspci tells me that 00:07 is an ISA bridge, but i do not see a device 00:08 in lspci. Does anyone know how I could figure out what this device is?

Kate Monster · Posted: Tue Feb 06, 2007 3:09 am Post subject:

It works to an extent. Upon resume, console glitches up and shows up as a bunch of vertical lines, but it responds to commands, and the suspend LED has stopped flashing like it was doing before. I'm not sure which one of these did it, but I'll list them all out...

1) Upgraded kernel from 2.6.16-r5 to 2.6.19-r1
2) Removed CPUFreq modules from kernel
3) Added "ec_intr=0" to kernel line in grub.conf

Kate Monster · Posted: Wed Feb 07, 2007 3:43 am Post subject:

After removing all traces of framebuffer from the kernel, the console is completely blank after resuming, but I can safely suspend2ram/resume from within X, and can switch between X and the tty without fscking my system. Works well enough for me, so I'll mark this as solved-ish.

If I was not clear in my previous posts, here is some advice/suggestions for others using a T22 (model 2647-8EU, though they are very similar for the most part) and who are having issues with suspend2ram:

1) Don't touch Savagefb with a ten foot pole.
2) I would advice against CPU frequency scaling. I havent had much luck with it, and havent put much effort into trying since google said it causes issues with suspend2 in the T22.
3) Try sticking "ec_intr=0" in your "kernel" line in GRUB (I do not know what this does, but it doesn't do any harm AFAICT)
4) Make sure you're using the latest kernel. You never know.

Thats as far as I got, if anyone gets it working with framebuffer, I would love to hear how.

Cheers,
Kevin

Kate Monster · Posted: Tue Jun 05, 2007 12:51 am Post subject:

Well, this is embarassing...After the 20,000th time of looking at the hibernate logs, my eyes finally come to rest on the message "ILLEGAL EXTENDED X86 OPCODE" which, after some more digging through the logs I found was coming from the command "vbetool vbestate save". After disabling Vbetool I now have fully working suspend-to-ram

no console issues, nothing...I'll post if I have other issues.