From: Joshua Kwan <joshk@triplehelix.org>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [REPRODUCABLE BUGS] Linux 2.5.66
Date: Wed, 26 Mar 2003 18:27:32 -0800 [thread overview]
Message-ID: <20030327022732.GA2867@triplehelix.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0303270019050.25001-100000@phoenix.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
While we're on the framebuffer bug train, James, do you know of
this bug with radeonfb:
My 2.5 kernel boots. Some initial boot text with ACPI and such is
scrolled on the screen, this is before radeonfb has taken over and
switched the screen size. But this is usually instant.
Right after the switch there is a lot of random characters in
varying colors at the top of the screen below the penguin. The
first legible boot message I see is this:
"Console: switching to colour framebuffer device 128x48"
(not verbatim)
The junk quickly scrolls off into the sunset and has no adverse
effects on the following boot messages.
It does not help to tell lilo to use 1024x768x16 by default.
(vga=791)
This is a minor bug, but the same thing works fine in the 2.4
radeonfb.
Regards
Josh
--
New PGP public key: 0x27AFC3EE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-03-27 2:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 23:26 Linux 2.5.66 Linus Torvalds
2003-03-24 23:35 ` Larry McVoy
2003-03-25 0:14 ` Florin Iucha
2003-03-25 8:05 ` Rolf Eike Beer
2003-03-25 8:29 ` Marco Roeland
2003-03-25 0:16 ` Jeremy Brown
2003-03-25 0:22 ` Udo A. Steinberg
2003-03-25 0:30 ` Greg KH
2003-03-25 1:18 ` Udo A. Steinberg
2003-03-25 1:47 ` Greg KH
2003-03-25 4:18 ` CaT
2003-03-25 4:34 ` Greg KH
2003-03-25 5:56 ` CaT
2003-03-25 6:51 ` Greg KH
2003-03-25 7:22 ` CaT
2003-03-25 7:27 ` Greg KH
2003-03-25 0:53 ` John Cherry
2003-03-25 1:55 ` [REPRODUCABLE BUGS] " Toplica Tanaskovic
2003-03-25 3:19 ` James Simmons
2003-03-25 9:51 ` Toplica Tanaskovic
2003-03-26 20:24 ` James Simmons
2003-03-26 23:49 ` Torrey Hoffman
2003-03-27 0:20 ` James Simmons
2003-03-27 2:27 ` Joshua Kwan [this message]
2003-04-02 22:16 ` James Simmons
2003-04-03 1:02 ` Joshua Kwan
2003-04-03 3:59 ` James Simmons
2003-03-27 16:05 ` Toplica Tanaskovic
2003-03-26 2:53 ` Paweł Gołaszewski
2003-03-26 3:33 ` James Simmons
2003-03-26 11:00 ` [2.5 patch] fix sound/oss/mad16.c compile Adrian Bunk
2003-03-26 11:26 ` 2.5.66: compile problem with snd-ice1724 Adrian Bunk
2003-03-26 12:45 ` [2.5 patch] fix ipmi_devintf.c compilation Adrian Bunk
2003-03-26 14:36 ` Corey Minyard
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=20030327022732.GA2867@triplehelix.org \
--to=joshk@triplehelix.org \
--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