From: Meino Christian Cramer <mccramer@s.netic.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.62 fails to boot, Uncompressing... and then nothing
Date: Wed, 19 Feb 2003 13:19:09 +0100 (MET) [thread overview]
Message-ID: <20030219.131909.59461826.mccramer@s.netic.de> (raw)
In-Reply-To: <200302191052.47663.baldrick@wanadoo.fr>
From: Duncan Sands <baldrick@wanadoo.fr>
Subject: Re: 2.5.62 fails to boot, Uncompressing... and then nothing
Date: Wed, 19 Feb 2003 10:52:47 +0100
Message-ID: <200302191052.47663.baldrick@wanadoo.fr>
Hi,
yes, indeed, this was the problem!!! (by the way: HURRAY, IT BOOTS!)
It seems that loading an "old" config file from the 2.4.*-series
of linux kernels will WIPE OUT that config items since they are not
written back to disk anymore when saving kernel configuartions....
Another thing is that make menuconfig fails to write back
configurations as alternate files into directories owned by root
and set drwxr-xr-x....but it is able to write into the . directory,
even if it is set with drwxr-xr-x also...
But this is only a sideeffect.
Keep Hacking!
Meino
> This is becoming a FAQ! Did you enable the console in your .config?
>
> CONFIG_VT=y
> CONFIG_VT_CONSOLE=y
>
> Most likely you chose to compile the input system as a module, which
> caused the console options to be autohorribly deselected. Just say 'y'
> for the input subsystem, at which point the console options will reappear,
> letting you select them.
>
> I hope this helps,
>
> Duncan.
>
next prev parent reply other threads:[~2003-02-19 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 7:19 2.5.62 fails to boot, Uncompressing... and then nothing Alexander Koch
2003-02-19 7:32 ` William Lee Irwin III
2003-02-19 8:59 ` Meino Christian Cramer
2003-02-19 9:47 ` William Lee Irwin III
2003-02-19 9:52 ` Duncan Sands
2003-02-19 9:54 ` William Lee Irwin III
2003-02-19 12:19 ` Meino Christian Cramer [this message]
2003-02-19 12:31 ` Alex Riesen
2003-02-19 14:01 ` Meino Christian Cramer
2003-02-24 12:33 ` Floris Kraak
2003-02-19 21:57 ` Peter Chubb
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=20030219.131909.59461826.mccramer@s.netic.de \
--to=mccramer@s.netic.de \
--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