From: Kurt Wall <kwallinator@gmail.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Console Goes Blank When Booting 2.6.15-rc5
Date: Wed, 14 Dec 2005 20:27:00 -0500 [thread overview]
Message-ID: <200512142027.00829.kwallinator@gmail.com> (raw)
In-Reply-To: <439FBDC5.5060609@gmail.com>
On Wednesday 14 December 2005 01:37 am, Antonino A. Daplas wrote:
> Kurt Wall wrote:
> > As Jesper Juhl has reported, if I boot 2.6.15-rc5 with vga=normal,
> > everything is fine. If I boot using my preferred size (vga=794),
> > the console goes blank. Because I'm a touch typist, I can login and
> > start X and everything is copacetic, but as soon as I leave X, I'm
> > back to the blank screen. From X, if I flip over to a VC, the VC
> > display is garbled and has artifacts from the X display.
> >
> > This worked fine with 2.6.14.3, and I didn't change the console,
> > framebuffer, or vesa options between the two kernels. Not sure how
> > to proceed, but I sure would like my high res console screens back.
>
> Can you recheck your .config and make sure that
> CONFIG_FRAMEBUFFER_CONSOLE=y
Oops. It was defined as a module. Compiling it statically gave me
the console back. Interestingly, I still lose the first 102 lines
of console output. After the all-important boot logo displays, I see
nothing until this line:
"Console: switching to colour frame buffer device 160x64"
It's all there in the ring buffer, of course. Thanks, Antonino.
Kurt
--
The mosquito is the state bird of New Jersey.
-- Andy Warhol
next prev parent reply other threads:[~2005-12-15 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 3:47 Console Goes Blank When Booting 2.6.15-rc5 Kurt Wall
2005-12-14 6:37 ` Antonino A. Daplas
2005-12-15 1:27 ` Kurt Wall [this message]
2005-12-15 7:43 ` Antonino A. Daplas
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=200512142027.00829.kwallinator@gmail.com \
--to=kwallinator@gmail.com \
--cc=adaplas@gmail.com \
--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.