From: "Indan Zupancic" <indan@nul.nu>
To: "Jeff Chua" <jeff.chua.linux@gmail.com>
Cc: "Jan Engelhardt" <jengelh@computergmbh.de>,
"Antonino A. Daplas" <adaplas@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"lkml" <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: Linux 2.6.23-rc2
Date: Mon, 6 Aug 2007 18:46:12 +0200 (CEST) [thread overview]
Message-ID: <39839.81.207.0.53.1186418772.squirrel@secure.samage.net> (raw)
In-Reply-To: <b6a2187b0708060906k643a8a20jcb3ac33259993517@mail.gmail.com>
On Mon, August 6, 2007 18:06, Jeff Chua wrote:
> On 8/6/07, Jan Engelhardt <jengelh@computergmbh.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.
>
> 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.
Does executing unicode_start, unicode_stop fixes it?
Greetings,
Indan
next prev parent reply other threads:[~2007-08-06 16:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 12:11 Jeff Chua
2007-08-05 12:40 ` Antonino A. Daplas
2007-08-05 13:26 ` Jeff Chua
2007-08-05 16:47 ` Rafael J. Wysocki
2007-08-06 0:36 ` Jeff Chua
2007-08-06 11:26 ` Rafael J. Wysocki
2007-08-06 12:34 ` Jeff Chua
2007-08-06 16:40 ` H. Peter Anvin
2007-08-06 19:17 ` [Suspend-devel] " Rafael J. Wysocki
2007-08-06 15:40 ` Jan Engelhardt
2007-08-06 16:06 ` Jeff Chua
2007-08-06 16:34 ` Jan Engelhardt
2007-08-06 16:46 ` Indan Zupancic [this message]
2007-08-06 17:16 ` H. Peter Anvin
2007-08-06 17:32 ` Indan Zupancic
2007-08-06 17:33 ` H. Peter Anvin
2007-08-06 22:53 ` Jeff Chua
2007-08-06 22:54 ` H. Peter Anvin
2007-08-06 22:57 ` Jeff Chua
2007-08-06 23:00 ` H. Peter Anvin
2007-08-06 22:48 ` Jeff Chua
-- strict thread matches above, loose matches on Subject: below --
2007-08-06 23:20 Jeff Chua
2007-08-04 3:50 Linus Torvalds
2007-08-04 4:14 ` david
2007-08-04 5:13 ` Jeff Chua
2007-08-04 5:34 ` Jeff Chua
2007-08-04 13:52 ` Jeff Chua
2007-08-04 16:11 ` Linus Torvalds
2007-08-04 18:06 ` H. Peter Anvin
2007-08-04 21:02 ` Antonino A. Daplas
2007-08-05 2:37 ` Jeff Chua
2007-08-05 3:11 ` H. Peter Anvin
2007-08-05 11:52 ` Jeff Chua
2007-08-07 17:05 ` David Weinehall
2007-08-08 2:46 ` Jeff Chua
2007-08-05 2:29 ` Jeff Chua
2007-08-05 12:04 ` Jeff Chua
2007-08-04 10:30 ` Rafael J. Wysocki
2007-08-04 22:15 ` Rafael J. Wysocki
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=39839.81.207.0.53.1186418772.squirrel@secure.samage.net \
--to=indan@nul.nu \
--cc=adaplas@gmail.com \
--cc=hpa@zytor.com \
--cc=jeff.chua.linux@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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®