public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Matthew Wilcox <willy@debian.org>
Cc: jsimmons@transvirtual.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.26 broken on headless boxes
Date: Thu, 18 Jul 2002 23:42:18 +0200	[thread overview]
Message-ID: <B48C1CD735C@vcnet.vc.cvut.cz> (raw)

On 18 Jul 02 at 22:18, Matthew Wilcox wrote:
> On Thu, Jul 18, 2002 at 11:04:54PM +0200, Petr Vandrovec wrote:
> > You have enabled CONFIG_VT without CONFIG_VGA_CONSOLE and 
> > CONFIG_DUMMY_CONSOLE. It is illegal configuration.
> 
> Huh.  So CONFIG_VT_CONSOLE is not enough any more?  I really do think
> this should be documented in Config.help.

CONFIG_VT_CONSOLE works other way around. If you set CONFIG_VT_CONSOLE,
/dev/console can be displayed on your VTs (on your screen).

CONFIG_VGA_CONSOLE/CONFIG_DUMMY_CONSOLE determines whether your VT can
be created at all - maybe _CONSOLE suffix is misleading - without
having at least one displaying device virtual terminals cannot be build.
I always thought that CONFIG_DUMMY_CONSOLE cannot be unset, but
apparently it can...

And BTW, when such configuration worked for you last time? It does not
look to me like that it should ever work.

> > To fix oopses, either enable 'Framebuffer devices' under 'Console
> > drivers' section (you do not have to enable any fbdev driver, just
> > check this option...), or disable CONFIG_VT. See arch/*/kernel/setup.c
> > for explanation, no code in VT subsystem kernel expects conswitchp == NULL,
> > but couple of architectures leaves sometime conswitchp uninitialized.
> 
> well, this is on x86 ...
                                                    Petr Vandrovec
                                                    vandrove@vc.cvut.cz
                                                    

             reply	other threads:[~2002-07-18 21:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18 21:42 Petr Vandrovec [this message]
2002-07-18 21:45 ` 2.5.26 broken on headless boxes Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2002-07-18 22:16 Petr Vandrovec
2002-07-18 22:20 ` Arnaldo Carvalho de Melo
2002-07-18 23:01 ` James Simmons
2002-07-18 21:04 Petr Vandrovec
2002-07-18 21:18 ` Matthew Wilcox
     [not found] <20020717165538.D13352@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
2002-07-18 12:45 ` Andi Kleen
2002-07-18 23:07   ` James Simmons
2002-07-19  9:45     ` Andi Kleen
2002-07-17 15:55 Matthew Wilcox
2002-07-18  1:06 ` William Lee Irwin III
2002-07-18  9:48   ` Re[3]: " Tobias Rittweiler
2002-07-18 10:46     ` William Lee Irwin III
2002-07-18 12:29       ` Re[2]: " Tobias Rittweiler
2002-07-18 20:17         ` William Lee Irwin III
2002-07-18 13:29   ` Matthew Wilcox
2002-07-18 20:18     ` William Lee Irwin III
2002-07-18 20:32       ` Matthew Wilcox
2002-07-18 20:37         ` William Lee Irwin III

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=B48C1CD735C@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@debian.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