when booting with gentoo or smp kernel, VIA SATA is initialised and drives detected as hde etc. proc knows they are there, but /dev does not see hde or ide/host2. booting with the emachines kernel (on a desktop box based on MSI K8T Neo FSI2R) gives a functioning /dev/hde
Umm... 2004.2 isn't released yet... also... this is probably a dupe... either that, or you need to check and make sure your devices aren't /dev/sda, etc. *** This bug has been marked as a duplicate of 52717 ***
Apparently, this isn't a DUPE... REOPENING
Workaround is to modprobe ide-disk after the boot for != emachines kernel, tested on my asus k8v-se, but this gets compatibility (slow) mode disk afaik. And it also shows up as /dev/hde.
Hopefully, this will be fixed in the near future, since the kernel developers have decided it a good idea to load the SATA interface before IDE in the newer (-bk) kernels. This problem will go away in the future, but for now, one must use Gustavo's workaround.
via SATA has a few problems, but they are not insurmountable. I just finished installing SATA on an ASUS A7V600. 1. When choosing SCSI drivers only select the one that you need. In this my case VIA SATA support. Other drivers lockout the VIA driver. 3. Compile it into the kernel. 3. While installing from the LiveCD 2004.2 the nomenclature for the SATA drives is /dev/sda1, /dev/sda2/, and /dev/sda3. Upon reboot, however, the naming convention changes to /dev/hde1, /dev/hde2 and /dev/hde3. Your fstab must be updated accordingly. The grub config thus became (in my case) title=gentoo-2.6.7 root(hd0,2) kernel /gentoo-2.6.7 root=/dev/hde3 My fstab /dev/hde1 /boot ext3 noauto,noatime 1 1 /dev/hde2 none swap sw 0 0 /dev/hde3 / reiserfs noatime 0 0 /dev/hda1 /mnt/cdrom iso9660 noauto,ro 0 0 Machine hardware is an ASUS A7V600, Adaptec 2940, HP SureStore DAT Drive, ATI Radeon 7000 R70. Two Western Digital WD800JD-00HKA0 setup as a RAID-1 Mirror set via the VIA controller. Hope this helps Curtis Maurand
Curtis, your kernel is not configured correctly to use the sata_via driver if your drives are showing up as hde#. Anyway, that's OT from this bug and is a configuration issue on your part Closing this bug as LATER, as I've noted the issue in the amd64 technotes (amd64.gentoo.org/technotes.xml) in the Errata section. The issue this bug is about will be fixed for 2004.3.
*** Bug 60820 has been marked as a duplicate of this bug. ***
