> >> On Slackware I can boot using the sata.i kernel image. I'm not sure if
> >> you can do that on Fedora Core. Last time I checked, I couldn't even
> >> install Fedora Core from a usb cd-rom drive.
> > Woah, I just learned something. If I boot from a non sata kernel... I
> > puts my sata drive at /dev/hde. That's how windows seems to use it too
> > since it thinks its the 3rd drive. (I've got drives in /dev/hda and
> > /dev/hdd as well).
> Hmm. That explains something I've seen recently.
> Circumstances forced me to try Debian. When I did what I thought was the
> default with "sarge", I was given a 2.4 kernel. This crashed on SATA1
> drives until I told the BIOS to put them into IDE mode. That worked, and I
> saw "hd" drives.
> When I subsequently tried the 2.6 "sarge" (but didn't change the BIOS
> settings), the drives were recognized as "sd" drives (if I'm recalling
> correctly). I was able to successfully use a SATA setting in the BIOS, and
> they were still seen as "sd" drives.
Yep, emulation mode is how first generation SATA controllers got
off the ground, later kernels switch chip into 'native' SATA mode
and thus you have sda... Later chipsets don't have the emulation
mode, instead they offer RAID, sometimes a * little mess to
deal with --> JBOD --> Just a Bunch Of Disks --> Non-RAID operation
for SATA disks.
Whom computers would destroy, they must first drive mad.