From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Dave Jones <davej@redhat.com>, Jason <dravet@hotmail.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vgacon: Workaround for resize bug in some chipsets
Date: Sun, 13 Nov 2005 22:33:18 +0800 [thread overview]
Message-ID: <43774EAE.90004@gmail.com> (raw)
In-Reply-To: <20051113110618.GD4117@implementation>
Samuel Thibault wrote:
> Antonino A. Daplas, le Sun 13 Nov 2005 06:20:53 +0800, a écrit :
>> "I updated to the development kernel and now during boot only the top of the
>> text is visable. For example the monitor screen the is the lines and I can
>> only see text in the asterik area.
>> ---------------------
>> | **************** |
>> | * * |
>> | * * |
>> | **************** |
>> | |
>> | |
>> | |
>> ---------------------
>
> Are you missing some left and right part too? What are the dimensions of
> the text screen at bootup? What bootloader are you using? (It could be a
> bug in the boot up text screen dimension discovery).
It was just the height. All numbers (done with printk's) look okay from
bootup. He gets 80 and 25 for ORIG_VIDEO_NUM_COLS and ORIG_VIDEO_NUM_LINES
respectively.
>
>> I have a Silicon Graphics 1600sw LCD panel with a Number Nine Revolution 4
>> video card."
>
> Does vgacon.c properly discovers that it is a VGA board?
Yes.
>
>> This bug seems to be a glitch in the VGA core of this chipset. Resizing
>> the screen triggers the mentioned bug.
>
> Do vga-only games (like old DOS-mode games) work with it?
>
>> The workaround is to make vgacon avoid calling vgacon_doresize() if the
>> display parameters did not change.
>
> I.e. never call it, actually.
>
>> A definitive fix will need to be provided by someone who knows and has the
>> hardware.
>
> I'm not sure it is hardware-specific. Maybe you have a combination of
> vga bios/bootloader/vga=ask/... that prevents vgacon.c from properly
> discovering the dimensions of the text screen.
His console worked before linux-2.6.14-rc2.
Tony
next prev parent reply other threads:[~2005-11-13 14:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 22:20 [PATCH] vgacon: Workaround for resize bug in some chipsets Antonino A. Daplas
2005-11-13 10:23 ` Martin Mares
2005-11-13 11:06 ` Samuel Thibault
2005-11-13 14:33 ` Antonino A. Daplas [this message]
2005-11-13 22:25 ` Samuel Thibault
2005-11-13 23:37 ` Antonino A. Daplas
[not found] <58c2Z-8jG-23@gated-at.bofh.it>
2005-11-13 19:41 ` Bodo Eggert
2005-11-13 22:11 ` Antonino A. Daplas
2005-11-13 22:26 ` Mika Penttilä
2005-11-13 23:35 ` Antonino A. Daplas
2005-11-14 3:32 ` H. Peter Anvin
2005-11-13 22:24 ` Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
2005-11-14 3:46 Jason Dravet
[not found] <58DvZ-6en-1@gated-at.bofh.it>
2005-11-14 9:24 ` Bodo Eggert
2005-11-14 15:27 ` Jason Dravet
2005-11-14 16:32 ` Bodo Eggert
2005-11-16 0:05 ` Samuel Thibault
2005-11-16 1:50 ` Jason Dravet
2005-11-16 2:25 ` Samuel Thibault
2005-11-16 17:58 Jason Dravet
2005-11-16 23:52 ` Samuel Thibault
2005-11-17 1:37 ` Jason Dravet
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=43774EAE.90004@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=dravet@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.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.