public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: lnx-kern@soo.com
Cc: Kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: VGA text console display problem with kernel 2.6.23-rc5/6
Date: Sun, 23 Sep 2007 07:51:30 +0800	[thread overview]
Message-ID: <1190505090.11468.6.camel@daplas> (raw)
In-Reply-To: <46F21280.6040400@soo.com>

On Thu, 2007-09-20 at 02:26 -0400, ben soo wrote:
> Antonino A. Daplas wrote:
> > On Tue, 2007-09-18 at 03:26 -0400, ben soo wrote:
> >> i've 2 servers with old PCI VGA cards, one using X86_64 kernel 
> >> version 2.6.23-rc5 and one with i386 kernel version 2.6.23-rc6,
> >> both wired into the same CRT via a KVM switch.
> > 
> > Is this new? If yes, what's the version of the last working kernel?
> 
> Hi Antonio; i'm very sorry about the delay in answering: been 
> pretty ill.
> 

That's okay.

> i had upgraded all four servers here to 2.6.23-rc6 and found that 
> only one had this console problem.  It runs a very old S3 Virge
> PCI vidcard.
> 
> Tonight i upgraded it to 2.6.23-rc7 and the console is fine again, 
> but, just to be complete i include the requested info:
> 
>   > Can you post dmesg and output of stty -a?
> 
> stty -a
> 
> speed 38400 baud; rows 34; columns 80; line = 0;

Yes, you have an 80x34 screen (normal VGA is 80x25). I have received
several reports about this problem (if the kernel boots with an initial
screen which is not 80x25 and the init scripts attempts to set an 8x16
font, the user gets a display that does not fit the screen). Your
problem though is probably unrelated.

Tony



      reply	other threads:[~2007-09-22 23:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18  7:26 VGA text console display problem with kernel 2.6.23-rc5/6 ben soo
2007-09-18  8:44 ` Antonino A. Daplas
2007-09-20  6:26   ` ben soo
2007-09-22 23:51     ` 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=1190505090.11468.6.camel@daplas \
    --to=adaplas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnx-kern@soo.com \
    /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