From: Andrew Morton <akpm@digeo.com>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: possible partition corruption
Date: Fri, 7 Feb 2003 18:06:39 -0800 [thread overview]
Message-ID: <20030207180639.046eb256.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302071943500.844-100000@localhost.localdomain>
Thomas Molina <tmolina@cox.net> wrote:
>
> On Fri, 7 Feb 2003, Andrew Morton wrote:
>
> > I couldn't immediately see the reason for this. You have your whole input
> > layer configured as a module, perhaps that has upset things.
> >
> > I suggest that you work on the config settings and find out what it is that
> > is causing the tty layer to not come up.
>
> OK, Hold the phone Susan, and stamp IDIOT on my forehead. The erason for
> not getting any output on the console was that I had configured the kernel
> without support for virtual terminals or console on virtual terminals.
> Once I configured that correctly, things worked. Duh!
Yes, but you had CONFIG_VGA_CONSOLE=y.
> The thing I don't understand is why would not having that configured in
> give me the lost journal and an inability to boot and mount the root
> partition when I booted back into a "normal" kernel.
Don't know. It didn't do that when I tested it.
next prev parent reply other threads:[~2003-02-08 1:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0302061848360.851-200000@localhost.localdomain>
2003-02-07 19:59 ` Thomas Molina
2003-02-07 22:15 ` Andrew Morton
2003-02-07 23:54 ` Thomas Molina
2003-02-07 23:40 ` Andrew Morton
2003-02-08 1:48 ` Thomas Molina
2003-02-08 2:06 ` Andrew Morton [this message]
2003-02-06 20:20 Thomas Molina
2003-02-06 20:36 ` Andrew Morton
2003-02-06 21:05 ` Thomas Molina
2003-02-06 21:14 ` Andreas Dilger
2003-02-06 22:35 ` Thomas Molina
2003-02-06 21:23 ` Andrew Morton
2003-02-06 21:33 ` Thomas Molina
2003-02-06 21:40 ` Andrew Morton
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=20030207180639.046eb256.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.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
all inboxes | Powered by JetHome®