From: "H. Peter Anvin" <hpa@zytor.com>
To: Rasmus Andersen <rasmus@avlebavle.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LILO fatal error after going from 2.6.22 to 2.6.24.2
Date: Tue, 19 Feb 2008 09:22:27 -0800 [thread overview]
Message-ID: <47BB1053.60409@zytor.com> (raw)
In-Reply-To: <20080219070201.GA7353@avlebavle.dk>
Rasmus Andersen wrote:
> Hello,
>
> I have just upgraded from 2.6.22 to 2.6.24.2 and after booting into the
> new kernel and seeing that everything went right, I wanted to make the
> new kernel the default boot kernel. But running LILO I got
>
> Fatal: Linux experimental device 0x04x needs to be defined.
> Check 'man lilo.conf' under 'disk=' and 'max-partitions='
>
> (Full output from lilo -v 5 below). Apart from setting 2.6.24.2 as
> default this is the same lilo config as 2.6.22 was able to write fine.
> Can anyone tell me what I (or the kernel) am/is doing wrong?
>
You have at least one file on a device mapper device (possibly an LVM
module), and LILO doesn't understand it.
-hpa
next prev parent reply other threads:[~2008-02-19 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 7:02 LILO fatal error after going from 2.6.22 to 2.6.24.2 Rasmus Andersen
2008-02-19 17:22 ` H. Peter Anvin [this message]
2008-02-19 19:55 ` Rasmus Andersen
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=47BB1053.60409@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rasmus@avlebavle.dk \
/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.