From: Dave Jones <davej@codemonkey.org.uk>
To: Greg KH <greg@kroah.com>
Cc: jsimmons@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: vesa fb in -bk gives too many console lines
Date: Thu, 17 Apr 2003 13:27:49 +0100 [thread overview]
Message-ID: <20030417122748.GA20825@suse.de> (raw)
In-Reply-To: <20030417062546.GA3114@kroah.com>
On Wed, Apr 16, 2003 at 11:25:46PM -0700, Greg KH wrote:
> In the latest -bk tree, using the vesa fb driver, I get a window that is
> much too big for my screen. I'm using "vga=0x0305" as a command line
> option, which I've been using for years on this box, and when the fb
> code kicks in, it creates a screen that has more lines than are
> displayed on the monitor (text lines that is). I can see 48 lines, but
> it's acting like there are more that that present.
>
> Is this just an operator error, in that I need to provide a different
> command line option now for the size of the console screen?
I've seen this happen too, and a box that worked fine with vga=791
before now gets me a screen full of garbage. I think something got
broken somewhere along the lines.
> Here's the relevant portions of the boot messages:
<snip zillions of EDID junk>
> p.s. nice boot messages, I know now that the usb code will stop taking
> the heat for abusing the kernel log :)
That is in the 'taking the piss' category for voluminous output.
I hope its planned to be quitened down somewhat when we get closer to 2.6.
AIUI, there are userspace tools that dump all that info anyway for
interested parties.
Dave
prev parent reply other threads:[~2003-04-17 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 6:25 vesa fb in -bk gives too many console lines Greg KH
2003-04-17 12:27 ` Dave Jones [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=20030417122748.GA20825@suse.de \
--to=davej@codemonkey.org.uk \
--cc=greg@kroah.com \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.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