From: Pavel Machek <pavel@ucw.cz>
To: Romano Giannetti <romanol@upcomillas.es>, linux-kernel@vger.kernel.org
Subject: Re: Good news --- jump from 2.6.13-rc3 to 2.6.16 (almost) ok (swsusp, input)
Date: Wed, 29 Mar 2006 00:19:56 +0200 [thread overview]
Message-ID: <20060328221956.GA5760@elf.ucw.cz> (raw)
In-Reply-To: <20060327120706.GA838@pern.dea.icai.upcomillas.es>
Hi!
> 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
doing
# 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
fi
IMG_SZ=0
read IMG_SZ < /sys/power/image_size
echo -n disk > /sys/power/state
RET=$?
#
# the logic here is:
# if image_size > 0 (without kernel support, IMG_SZ will be
zero),
# 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
RET=$?
fi
# restore previous loglevel
echo $LOGLEVEL > /proc/sys/kernel/printk
exit $RET
--
Picture of sleeping (Linux) penguin wanted...
prev parent reply other threads:[~2006-03-28 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 12:07 Romano Giannetti
2006-03-28 22:19 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060328221956.GA5760@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=romanol@upcomillas.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®