Norman Diamond wrote: > There's next to nothing that I can do about it. > If the BIOS sets the Intel chip to present an ATA > interface then the IDE drivers take control early in > the boot process. If the BIOS sets the Intel chip to > present a SATA interface then LIBATA takes control > early in the boot process. > > I'm considering constructing a boot menu where the > default command line has hda=noprobe hdb=noprobe > hdc=noprobe hdd=noprobe, and an alternate boot option > omits those. Even if this will be reliable enough, it > won't be easy to explain to customers (if you don't > believe that then read some tech support stories). I think that at some point the IDE drivers were updated to be less aggressive about taking control of anything that looked like an IDE controller, but I'm not certain. These kind of problems are kind of inevitable when you configure two drivers that will attach to the same device, it's hard to control which one will attach. (It's especially bad if two drivers will attach to different parts of the same controller, which is the combined mode fiasco we had for a while.) Newer distributions like Fedora are generally setting CONFIG_IDE=n entirely and avoid the problem. > >> Realistically, although some people still work on >> it, testing coverage of the old IDE drivers is not >> that great these days, since most distributions no >> longer use it. > > Even Knoppix 6.0.1, whose kernel isn't too antique > yet, assigned /dev/hda and /dev/hdc on my Dell D820 > with ICH7M. > > -------------------------------------- > Power up the Internet with Yahoo! Toolbar. > http://pr.mail.yahoo.co.jp/toolbar/ -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
