From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: vgacon regression
Date: Wed, 21 Dec 2005 05:46:30 +0800 [thread overview]
Message-ID: <43A87BB6.4080401@gmail.com> (raw)
In-Reply-To: <9a8748490512201203s7fce043byfce95b11307008d5@mail.gmail.com>
Jesper Juhl wrote:
> Hi Antonino,
>
> 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.
More info. The vgacon is actually restored by X as vgacon does not
touch the hardware anymore (unless you resize the console with stty). So
any patch that affects X is a culprit. More specifically, the X driver
used was vesa, which means that the vgacon restoration would be done
using VBE state save and state restore function calls. With X, this would
involve lrmi (the same library used by vbetool).
I wasn't able to duplicate this problem, using Xorg vesa and vgacon 80x25.
Also, there are no changes to vgacon or to the console that I know of between
the versions he mentioned.
To Jesper,
>From your description, I would presume that the VGA fontmap was not
adequately restored. Can you try changing your system font using whatever
utility is available for your system, such as setfont? Choose any 8x16 font
in the consolefont directory (It's usually in /usr/share/kbd/consolefont)
Tony
PS: I'll be offline from the 22nd of December to early January 2006. I
_might_ be able to occasionally answer by e-mail.
prev parent reply other threads:[~2005-12-20 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 20:03 vgacon regression Jesper Juhl
2005-12-20 21:46 ` Antonino A. Daplas [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=43A87BB6.4080401@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.