mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION 2.6.23] no vga console and no messages
Date: Sun, 17 Feb 2008 18:48:16 +0100	[thread overview]
Message-ID: <200802171848.16969.elendil@planet.nl> (raw)
In-Reply-To: <alpine.LNX.1.00.0802171134350.5496@iabervon.org>

On Sunday 17 February 2008, Daniel Barkalow wrote:
> On Sun, 17 Feb 2008, Frans Pop wrote:
> > Daniel Barkalow wrote:
> > > For some reason I can't see and don't know how to debug, in 2.6.23 on
> > > my server I don't get the vga console, but only get the dummy
> > > console.
> >
> > Please check if this bug report matches the issue you are seeing:
> > http://bugzilla.kernel.org/show_bug.cgi?id=9310
>
> I think mine might be different. I've got a vga parameter (vga=0x301),
> and mine disappears very early, before when you usually get "Console:
> colour VGA+ 80x25" (and I'm getting "Console: coloud dummy 80x25"
> instead). I've also got CONFIG_FB turned off entirely.

The main question is: do you have FRAMEBUFFER_CONSOLE_DETECT_PRIMARY enabled 
in you kernel config. If you do, I'd try disabling it.

> But if you've got any insight into how the console driver stuff works
> from troubleshooting your problem, I could use the hints...

Afraid not. Are you sure you have the correct framebuffer driver compiled 
into the kernel?

Please post your kernel config and the output of 'lspci -nn', so people can 
have a look.

  reply	other threads:[~2008-02-17 17:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17  2:56 Daniel Barkalow
2008-02-17  7:37 ` Frans Pop
2008-02-17 16:44   ` Daniel Barkalow
2008-02-17 17:48     ` Frans Pop [this message]
2008-02-17 18:00       ` Daniel Barkalow
2008-02-17 18:19         ` Daniel Barkalow

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=200802171848.16969.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=barkalow@iabervon.org \
    --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 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®