mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Molina <tmolina@cablespeed.com>
To: Norman Diamond <ndiamond@wta.att.ne.jp>
Cc: dan@eglifamily.dnsalias.net, linux-kernel@vger.kernel.org
Subject: Re: Blank Screen in 2.6.0
Date: Mon, 29 Dec 2003 17:44:46 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0312291741530.5409@localhost.localdomain> (raw)
In-Reply-To: <007101c3cdbc$046a58d0$2fee4ca5@DIAMONDLX60>

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.  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've got 
framebuffer support as a module.

  reply	other threads:[~2003-12-29 22:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29  3:28 Norman Diamond
2003-12-29 22:44 ` Thomas Molina [this message]
2003-12-30  2:14   ` Norman Diamond
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=Pine.LNX.4.58.0312291741530.5409@localhost.localdomain \
    --to=tmolina@cablespeed.com \
    --cc=dan@eglifamily.dnsalias.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndiamond@wta.att.ne.jp \
    /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

all inboxes | Powered by JetHome®