[lkml]   [2006]   [Mar]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Good news --- jump from 2.6.13-rc3 to 2.6.16 (almost) ok (swsusp, input)

> I finally tried to install 2.6.16 on my portable PC, jumping directly from
> 2.6.13-rc3, and there are good news. The most critical thing, namely swsusp,
> did work ok and seems faster than before. A little problem is that when
> starting the suspend, no messages are printed (the screen goes blank and
> after a bit the machine poweroff). But then resume is ok . The same goes for
> -ck1, which has a really nice feeling.

See FAQ:

Q: How do I make suspend more verbose?

A: If you want to see any non-error kernel messages on the virtual
terminal the kernel switches to during suspend, you have to set the
kernel console loglevel to at least 4 (KERN_WARNING), for example by

# save the old loglevel
read LOGLEVEL DUMMY < /proc/sys/kernel/printk
# set the loglevel so we see the progress bar.
# if the level is higher than needed, we leave it alone.
if [ $LOGLEVEL -lt 5 ]; then
echo 5 > /proc/sys/kernel/printk

read IMG_SZ < /sys/power/image_size
echo -n disk > /sys/power/state
# the logic here is:
# if image_size > 0 (without kernel support, IMG_SZ will be
# then try again with image_size set to zero.
if [ $IMG_SZ -ne 0 ]; then # try again with minimal image size
echo 0 > /sys/power/image_size
echo -n disk > /sys/power/state

# restore previous loglevel
echo $LOGLEVEL > /proc/sys/kernel/printk
exit $RET

Picture of sleeping (Linux) penguin wanted...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-03-29 00:22    [W:0.030 / U:2.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site