S3 test

DISCUSSION Shaohua Li 4 participants 4 messages Jul 12, 2005 – Jul 15, 2005 2 messages not in the archive ACPI

Share & tools

Shaohua Li

author

2005-07-12 09:22 UTC #0 lore raw

Hi,
Somebody in the list suggested we could test S3 with a kernel which doesn't touch any device. Considering there are many broken drivers (especially hard disk driver in some systems), this sounds like a good method to narrow down S3 bugs. For those who want to try it, you can make a kernel without any driver support, and make attached file as your initrd, and see if S3 works. The attached initramfs doesn't touch any device and just does something like below:

echo 'mem' >/sys/power/state
echo xxxxxxxx
while true; do done

Thanks,
Shaohua

A message that is not in the archive (sent off-list or not yet received): 1121160149.20699.6.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org

Pavel Machek

2005-07-12 13:08 UTC #2 lore raw

Hi!

Quoted 11 lines

Somebody in the list suggested we could test S3 with a kernel which doesn't touch any device. Considering there are many broken drivers (especially hard disk driver in some systems), this sounds like a good method to narrow down S3 bugs. For those who want to try it, you can make a kernel without any driver support, and make attached file as your initrd, and see if S3 works. The attached initramfs doesn't touch any device and just does something like below:
echo 'mem' >/sys/power/state
echo xxxxxxxx
while true; do done

Unfortunately, video is the device least likely to work after resume :-(. But users can hit numlock or something to see if machine is still alive.

Signature · 9 lines

64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

Frank

2005-07-15 13:36 UTC #3 lore raw

In reply to a message not in the archive

Hi Shaohua,

thanks for your efforts on getting S3 to work.

Is there anybody on this list, who has tried this initramfs yet and can give a short list of the steps involved? I have never before built a kernel for use with initram, but I would like to test it on my S3-broken laptop.

Thanks,
Frank

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

A message that is not in the archive (sent off-list or not yet received): 200507151536.21857.hugelmopf-S0/[email protected]

Bernd Schubert

2005-07-15 14:29 UTC #5 lore raw

Hello Frank,

Quoted 1 line

Is there anybody on this list, who has tried this initramfs yet and can give

Quoted 2 lines

short list of the steps involved? I have never before built a kernel for use with initram, but I would like to test it on my S3-broken laptop.

I'm planning to do it over the weekend (there was just too much to do over the week). So far I have never used an initramfs myself, but I'm rather experienced with initrd's. I guess you only need to specify a line 'initrd = /path_to_initramfs/initramfs' in lilo, so something similar to this:

# a rescue image that calls a shell in the initrd
image=/boot/linux-2.6.9-tc5
        label=2.6.9_rescue
        read-only
        initrd=/boot/initrd-lvm-2.6.-amd64-lvm2_32_shell.gz

Recent kernels seem to first check if its an initramfs or initrd and I hope they will do the proper thing themselves. I'm not sure if the kernel needs ramdisk support, but I guess it needs it.

Better DON'T do it globally for all kernels, you might have problems to boot a normal kernel again ;-)

About grub I don't know how to use/configure it.

Hope it helps,
Bernd