[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0708061832400.13469@fbirervta.pbzchgretzou.qr>
Date: Mon, 6 Aug 2007 18:34:17 +0200 (CEST)
From: Jan Engelhardt <jengelh@...putergmbh.de>
To: Jeff Chua <jeff.chua.linux@...il.com>
cc: "Antonino A. Daplas" <adaplas@...il.com>,
"H. Peter Anvin" <hpa@...or.com>,
lkml <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Linux 2.6.23-rc2
On Aug 7 2007 00:06, Jeff Chua wrote:
>On 8/6/07, Jan Engelhardt <jengelh@...putergmbh.de> wrote:
>
>> > ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
>> That looks pretty much like all-one-bits (ÿ = 255).
>> What about vcsa1 (use hexdump -C)?
>
># hexdump -C /dev/vcsa1
>00000000 19 50 00 18 ff ff ff ff ff ff ff ff ff ff ff ff |.P..............|
>00000010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
>*
>00000fa0 ff ff ff ff |....|
>00000fa4
>
>Yep, it's all one's.
If no s2ram was involved at all, and vcs and vcsa output was as you
describe, then your display whould actually show white blinking ÿs on a
gray background. :>
>And once "s2ram" (without parameter) is executed, there's no way to
>restore back the console in text-mode even using "s2ram --force
>--acpi_sleep 1 --vbe_mode" until a "suspend-to-disk" or a reboot.
>
>"s2ram --force --acpi_sleep 1 --vbe_mode" will only work on
>non-messed-up-console.
Jan
--
Powered by blists - more mailing lists