From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: James Simmons <jsimmons@infradead.org>
Cc: Gerhard Mack <gmack@innerfire.net>, Robert Love <rml@tech9.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.71 - random console corruption
Date: Wed, 18 Jun 2003 21:08:00 +0100 [thread overview]
Message-ID: <200306182108.05364@gjs> (raw)
In-Reply-To: <Pine.LNX.4.44.0306182127170.24449-100000@phoenix.infradead.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 18 of June 2003 21:28, James Simmons wrote:
> > Config attached.
>
> You have way to many fbdev drivers turned on. Also the console drivers are
> messed up. Slect one Fbdev driver and framebuffer console or just use
> vgacon.
Shouldn't those drivers detect if they are or not the ones, and if none of
them is - leave vgacon , if one of them does the job it should set vgacon off
and use fb ?
What if i will have to decide about configuration for distribution ? where
everyone nowdays want to boot with logo/fb and so on ?
- --
Grzegorz Jaskiewicz
K4 Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+8Malqu082fCQYIgRAjMSAJ4uCzn4EH4pgXstsRSnVBlZiZObggCdEYI8
vCupyDNBt9J9DvSYpE4pxoA=
=vnmZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-18 20:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 0:59 Linux 2.5.71 - random console corruption Gerhard Mack
2003-06-16 21:27 ` James Simmons
2003-06-16 21:31 ` Robert Love
2003-06-16 23:34 ` James Simmons
2003-06-16 23:40 ` Robert Love
2003-06-17 20:50 ` James Simmons
2003-06-18 1:50 ` Gerhard Mack
2003-06-18 11:56 ` Grzegorz Jaskiewicz
2003-06-18 16:38 ` James Simmons
2003-06-18 16:20 ` Grzegorz Jaskiewicz
2003-06-18 20:28 ` James Simmons
2003-06-18 20:08 ` Grzegorz Jaskiewicz [this message]
2003-06-18 16:55 ` Gerhard Mack
2003-06-19 20:43 ` Bill Davidsen
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=200306182108.05364@gjs \
--to=gj@pointblue.com.pl \
--cc=gmack@innerfire.net \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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