From: Michael Tokarev <mjt@tls.msk.ru>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: Switching from (deprecated) IDE driver -> SATA (PATA support) (found solution (scratch that))
Date: Sun, 25 Jan 2009 16:15:16 +0300 [thread overview]
Message-ID: <497C65E4.2040302@msgid.tls.msk.ru> (raw)
In-Reply-To: <alpine.DEB.1.10.0901250808020.15073@p34.internal.lan>
Justin Piszcz wrote:
>
> On Sun, 25 Jan 2009, Justin Piszcz wrote:
>> On Sun, 25 Jan 2009, Justin Piszcz wrote:
>>> On Sun, 25 Jan 2009, Justin Piszcz wrote:
>>>> On Sun, 25 Jan 2009, Justin Piszcz wrote:
>>>>> On Sun, 25 Jan 2009, Justin Piszcz wrote:
Wow, that's quite some ping-pong!.. ;)
[]
> Hm, I may have spoke too fast:
>
> Added: (IDE ONLY), no SATA:
> image=/boot/2.6.26-6
> label=2.6.26-6
> read-only
> root=current
>
> p254:/boot# lilo
> Added 2.6.26-6 *
> Added 2.6.28-4
> p254:/boot#
>
> Set to current.
>
> p254:/boot# grep =current /etc/lilo.conf
> root=current
> root=current
> p254:/boot#
>
> The reason current may have worked before is because I manually booted with
> root=/dev/sdd2 (after I saw the error that it could not find root,302, etc)
>
> So I am booting the old kernel without the SATA drivers with root=current
> to see if it works..
>
> Nope, so I need to figure out how to get the UUID= option working in LILO.
There's no way without using initramfs. Lilo only records the unix device
number (like 8:1 for /dev/sda1) and passes it to kernel (replacing `current'
with that number). But for different kernels (IDE vs PATA drivers) the
number will be different. Lilo itself - when booting at least - can not
know which device it will be.
The only universal solution is to use smart initramfs that will populate
/dev/disk/by-label/ etc (using udev maybe).
Another solution is to explicitly specify root=/dev/sda1 or root=/dev/hda1
when using pata- or ide-enabled kernels, in lilo.conf.
/mjt
next prev parent reply other threads:[~2009-01-25 13:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 10:56 Switching from (deprecated) IDE driver -> SATA (PATA support) Justin Piszcz
2009-01-25 11:07 ` Alan Cox
2009-01-25 12:09 ` Justin Piszcz
2009-01-25 12:15 ` Justin Piszcz
2009-01-25 12:28 ` Justin Piszcz
2009-01-25 12:41 ` Justin Piszcz
2009-01-25 12:55 ` Switching from (deprecated) IDE driver -> SATA (PATA support) (found solution) Justin Piszcz
2009-01-25 13:08 ` Switching from (deprecated) IDE driver -> SATA (PATA support) (found solution (scratch that)) Justin Piszcz
2009-01-25 13:15 ` Michael Tokarev [this message]
2009-01-25 15:45 ` Switching from (deprecated) IDE driver -> SATA (PATA support) Eric Sandeen
[not found] ` <alpine.DEB.1.10.0901250726530.10805__44823.8515914001$1232890466$gmane$org@p34.internal.lan>
2009-01-25 21:13 ` Bill Davidsen
2009-01-25 21:14 ` Justin Piszcz
2009-01-29 23:44 ` Bill Davidsen
2009-01-26 22:02 ` Lennart Sorensen
2009-01-26 23:36 ` Sergei Shtylyov
2009-01-25 18:04 ` Mark Lord
2009-01-25 19:27 ` Bartlomiej Zolnierkiewicz
2009-01-25 21:13 ` Justin Piszcz
2009-01-25 21:39 ` Bartlomiej Zolnierkiewicz
2009-01-29 23:50 ` Bill Davidsen
2009-01-30 3:38 ` david
2009-01-30 10:21 ` Alan Cox
2009-01-30 10:11 ` Alan Cox
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=497C65E4.2040302@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).