public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Thomas Molina" <tmolina@cablespeed.com>
Cc: <dan@eglifamily.dnsalias.net>, <linux-kernel@vger.kernel.org>
Subject: Re: Blank Screen in 2.6.0
Date: Tue, 30 Dec 2003 11:14:07 +0900	[thread overview]
Message-ID: <00d401c3ce7a$a302fd80$98ee4ca5@DIAMONDLX60> (raw)
In-Reply-To: Pine.LNX.4.58.0312291741530.5409@localhost.localdomain

Thomas Molina wrote:
> On Mon, 29 Dec 2003, Norman Diamond wrote:
> > Dan wrote:
> >
> > > Upgraded to the lastest module-init-tools, and disabled the
> > > frame buffer support in the kernel. So the only graphic option enabled is
> > > text mode selection. But when I boot I still get a blank screen!
> > > My lilo.conf contains a line: vga=773, which works beautifully under
> > > RedHat's stock 2.4.20-8.
> >
> > In my experience the vga= option worked with every 2.4 kernel in every
> > distro that I had used, continued working with 2.6 test* and 0 in Red Hat
> > 7.3, but blanked the screen with 2.6 test* and 0 in SuSE 8.1 and SuSE 8.2.
> > Haven't tried other configurations with 2.6.
> >
> > But now you're getting the same with a Red Hat distro, so it's looking
> > pretty random.
> >
> > The decision to release 2.6.0 with the same broken vga= option that was
> > reported many times in 2.6.0-test* makes me think that vga= is not intended
> > to work.
>
> Maybe it has something to do with RedHat 7.3.

Are you serious?  It really is true that vga= isn't supposed to work in
2.6.0, but there is something to do with RedHat 7.3 which caused vga= to
continue to work in 2.6.0 with that distro only?  Then why hasn't the vga=
parameter been removed entirely?

> I've used RH8, RH9, and  Fedora Core 1 and haven't had a problem with vga=
> in any of them during the 2.5/2.6 series, right up through the current one.

I forgot if Dan is using RH8 or RH9.  Whichever, you're getting different
results than he did, because his failed with one of these and yours works
with both.  At least my failures with SuSE are consistent.  I'd say the
overall inconsistency points to a bug in 2.6.0-test* and .0.  Especially
when no one seems to be reporting similar failures in the 2.4 series.


  reply	other threads:[~2003-12-30  2:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29  3:28 Blank Screen in 2.6.0 Norman Diamond
2003-12-29 22:44 ` Thomas Molina
2003-12-30  2:14   ` Norman Diamond [this message]
2003-12-30  2:46     ` Thomas Molina
2003-12-30  7:03       ` Wes Janzen
2004-01-05 23:46         ` James Simmons
2004-01-05 23:44     ` James Simmons
2003-12-30 21:03   ` Dan Egli
2004-01-05 23:34     ` James Simmons
2004-01-05 23:35       ` Dan Egli
  -- strict thread matches above, loose matches on Subject: below --
2003-12-29 14:49 Pacheco Jason NPRI
2003-12-28 18:14 dan
2003-12-28 19:40 ` Gabor MICSKO
2003-12-28 23:08   ` dan
2003-12-29 15:02     ` Ed Tomlinson
2003-12-29  7:45   ` Tomas Szepe
2003-12-29  6:22 ` Paul Misner
2003-12-29 15:13   ` Jesper Juhl
2004-01-06 23:02     ` James Simmons
2004-01-06 23:07       ` Jesper Juhl
2004-01-06 23:14         ` James Simmons
2004-01-07  0:39           ` Jesper Juhl
2004-01-07 17:44             ` James Simmons
2004-01-07 23:55               ` Jesper Juhl

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='00d401c3ce7a$a302fd80$98ee4ca5@DIAMONDLX60' \
    --to=ndiamond@wta.att.ne.jp \
    --cc=dan@eglifamily.dnsalias.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmolina@cablespeed.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