From: Ed Tomlinson <edt@aei.ca>
To: Gabor MICSKO <gmicsko@szintezis.hu>
Cc: dan@eglifamily.dnsalias.net, linux-kernel@vger.kernel.org
Subject: Re: Blank Screen in 2.6.0
Date: Mon, 29 Dec 2003 10:02:21 -0500 [thread overview]
Message-ID: <200312291002.22262.edt@aei.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0312282303340.15994-100000@eglifamily.dnsalias.net>
On December 28, 2003 06:08 pm, dan@eglifamily.dnsalias.net wrote:
> On 28 Dec 2003, Gabor MICSKO wrote:
> > http://www.linux.org.uk/~davej/docs/post-halloween-2.6.txt
>
> I tried that.
>
>
> Known gotchas.
> ~~~~~~~~~~~~~~
> Certain known bugs are being reported over and over. Here are the
> workarounds.
> - Blank screen after decompressing kernel?
> Make sure your .config has
> CONFIG_INPUT=y
> CONFIG_VT=y
> CONFIG_VGA_CONSOLE=y
> CONFIG_VT_CONSOLE=y
> A lot of people have discovered that taking their .config from 2.4 and
> running make oldconfig to pick up new options leads to problems, notably
> with CONFIG_VT not being set.
>
> ok, so I grep'ed the .config
>
> [root@eglifamily kernel]# grep -wi config_input .config
> CONFIG_INPUT=y
> [root@eglifamily kernel]# grep -wi config_vt .config
> CONFIG_VT=y
> [root@eglifamily kernel]# grep -wi config_vga_console .config
> CONFIG_VGA_CONSOLE=y
> [root@eglifamily kernel]# grep -wi config_vt_console .config
> CONFIG_VT_CONSOLE=y
> [root@eglifamily kernel]#
>
> you can see that in the .config I attched:
> > > CONFIG_INPUT=y
> > > CONFIG_VT=y
> > > CONFIG_VT_CONSOLE=y
> > > CONFIG_VGA_CONSOLE=y
>
> Any other ideas?
I had problems getting 2.6.0 to work on a second box too. What seemed to solve
it here was defining the fonts:
CONFIG_PCI_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
Luck,
Ed Tomlinson
next prev parent reply other threads:[~2003-12-29 15:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 18:14 Blank Screen in 2.6.0 dan
2003-12-28 19:40 ` Gabor MICSKO
2003-12-28 23:08 ` dan
2003-12-29 15:02 ` Ed Tomlinson [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-12-29 3:28 Norman Diamond
2003-12-29 22:44 ` Thomas Molina
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
2003-12-29 14:49 Pacheco Jason NPRI
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=200312291002.22262.edt@aei.ca \
--to=edt@aei.ca \
--cc=dan@eglifamily.dnsalias.net \
--cc=gmicsko@szintezis.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.