[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080213024329.GA6912@deepthought>
Date: Wed, 13 Feb 2008 02:43:29 +0000
From: Ken Moffat <zarniwhoop@...world.com>
To: Greg KH <greg@...ah.com>
Cc: bzolnier@...il.com, muli@...ibm.com, jdmason@...zu.us,
linux-ide@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz,
linux-kernel@...r.kernel.org, discuss@...-64.org
Subject: Re: "ide=reverse" do we still need this?
On Tue, Feb 12, 2008 at 04:15:07PM -0800, Greg KH wrote:
>
> I'm curious if we really still support the ide=reverse option? It's a
> config option that I don't think the distros still enable (SuSE does
> not). Is this still needed these days?
>
My "server" has a consumer-grade desktop amd64 mobo, with all that
implies about cheap hardware and strange/misleading bios options.
It also has an add-in dual IDE card with the main data on raid1.
It's set to ide=reverse, without that it doesn't boot (the add-ins
are IDE, system drive is SATA, so I guess it probably tries to boot
from the DVD - it's been a long time since it bit me and I don't
remember the full details.
That was how it was set for 2.6.18.6, and how it now boots from
2.6.22.18. I think at one time the order of the interfaces might
have been different. Certainly, I carry forward a fallback without
ide=reverse in lilo.conf, just in case the disks move on my next
kernel upgrade.
What a distro selects should cover most of that distro's users, but
that is not anywhere near providing 100% coverage for *all* the
hardware out there. Also, you can force your users to e.g. mount by
label. So far, that hasn't been forced on me, and I really hate
having to reboot that box :)
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists