From: andyliebman@aol.com
To: linux-kernel@vger.kernel.org
Subject: Changes in SATA, IDE and ATAPI configuration
Date: Sat, 07 Jan 2006 11:34:39 -0500 [thread overview]
Message-ID: <8C7E1BF63B9F5F4-AC8-506C@FWM-M45.sysops.aol.com> (raw)
At the risk of getting flamed for asking a basic question here, could I
suggest that a kernel and/or driver developer provide a brief "how-to
acticle" somehere (like on the kernel.org site, or in the kernel
documentation) that explains the way things have changed from the early
2.6.x days to more recent kernels like 2.6.14 or 2.6.15 with respect to
configuring fundamental devices like IDE drives, SATA drives, and ATAPI
drives.
Personally, I have been struggling for about two weeks to move an image
of an IDE OS Drive that's running a 2.6.14 kernel over to a SATA drive.
Clearly, SATA + ATAPI is not the same as IDE + ATAPI. Apparently,
several factors MIGHT be causing my ATAPI CDROM not to show up when I
boot from the SATA drive:
-- BIOS settings for the ICH5 SATA controller on my Xeon motherboard
(Auto, SATA, PATA?)
-- Whether the CD is connected to the Primary or Secondary IDE channel
-- Use (or NOT) of "options libata atapi_enabled=1" in modprobe.conf
-- Order of loading modules
-- Use (or NOT) of the AHCI module. When making fresh installs onto
SATA drives, some distributions seem to load the AHCI module and some
don't, on exactly the same hardware with the same kernel.
Whatever it is, I haven't found the magic formula for making the
transfer from IDE to SATA work. And various "support personnel"
associated with my two favorite Linux distributions have similarly
failed to provide a solution. I am not the only one struggling with
these issues. Just seach on the Forum of ANY distribution and you will
find people having similar issues.
Things used to be so simple. But now, with improvements like SATA, UDEV
and libata, for some users who are upgrading things have gotten more
confusing than ever. A little basic info -- if you use A, you have to
use B. X has to load before Y -- etc. might go a long way to making
some happier Linux users. I feel as if I have made a valient effort to
find the answers myself. Linux shouldn't be THIS difficult.
Regards,
Andy Liebman
next reply other threads:[~2006-01-07 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 16:34 andyliebman [this message]
2006-01-07 19:14 ` 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=8C7E1BF63B9F5F4-AC8-506C@FWM-M45.sysops.aol.com \
--to=andyliebman@aol.com \
--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
all inboxes | Powered by JetHome®