From: Jesper Juhl <jesper.juhl@gmail.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: vgacon regression
Date: Tue, 20 Dec 2005 21:03:33 +0100 [thread overview]
Message-ID: <9a8748490512201203s7fce043byfce95b11307008d5@mail.gmail.com> (raw)
Hi Antonino,
[starting a new thread and adding Linus to CC since this problem is
now also in his tree as well as Andrews]
The problem I observed in 2.6.15-rc5-mm2 with the (vgacon) console
getting corrupted after starting X is still present in 2.6.15-rc5-mm3
and is now also present in mainline (2.6.15-rc6-git1).
Latest kernel that I know of that is problem free is 2.6.15-rc5-git4.
The problem in a nutshell:
If I boot with vga=791 everything is fine with both mainline kernels
and -mm and
I don't see any of the problems noted below.
If I boot with vga=normal then I see these two problems :
1) Just after starts and switches resolution but before the login
manager is
displayed I briefly see a corrupted graphical image that is
sometimes what
looks like a garbled snapshot of the text-mode console and sometimes a
garbled version of the X login screen or a previous KDE desktop session.
2) If I switch back to a text mode console with ctrl+alt+f6 from
within X (or
even shut down X), then the text console is completely
garbled. It still has
the resolution it had at boot but it's displaying lots of
coloured (some of
them blinking) boxes and random characters all over, including
some bits
that look like partial boot-up messages (half a word here, two
words there,
with random bits inserted, etc) - in short, it's completely messed up.
The console stil remains functional in the sense that you can
log in blind and
run commands just fine, but no amount of "reset" or "clear"
will fix the
breakage.
Any advice as to what patches I can try to revert?
While I wait for a reply I'll test the mainline kernels between
2.6.15-rc5-git4 and 2.6.15-rc6-git1 to try and determine the first one
that breaks.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next reply other threads:[~2005-12-20 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 20:03 Jesper Juhl [this message]
2005-12-20 21:46 ` Antonino A. Daplas
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=9a8748490512201203s7fce043byfce95b11307008d5@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®