blob: 7263800410c7660999235e984fe8cef6b372b229 (
plain)
1
2
3
4
5
6
|
<div dir="ltr"><div><div><div><div>I remember when PATA (IDE) drivers were statically compiled into the kernel, then we went to modular IDE which I liked because modprobe ordering could be controlled. (When dealing with parity RAID, its nice to have logical drive enumeration because SATA ports don't have UUID labels.)<br>
<br>But now it seems we've come full circle:<br><br>[root@localhost ~]# grep SATA_AHCI /boot/config-3.8.1-desktop-1.mga3<br>CONFIG_SATA_AHCI=y<br>CONFIG_SATA_AHCI_PLATFORM=y<br><br></div>Is there a compelling reason to do this (other than AHCI is popular)?<br>
<br></div>I'm putting together a home-brewed a file server using an old motherboard plus a couple of add-in SATA controllers. With the Mageia stock kernel, the enumeration looks like:<br><br></div><div>sda = RAID disk 08 (ahci)<br>
</div><div>sdb = RAID disk 09 (ahci)</div><div>sdc = RAID disk 10 (ahci)</div><div>sdd = RAID disk 11 (ahci)<br><div>sde = Mageia OS (sata_nv) (1st port on mobo)<br></div><div>sdf = RAID disk 01 (sata_nv)</div><div>sdg = RAID disk 02 (sata_nv)</div>
<div>sdh = RAID disk 03 (sata_nv)</div></div><div>sdi = RAID disk 04 (sata_sil)</div><div>sdj = RAID disk 05 (sata_sil)</div><div>sdk = RAID disk 06 (sata_sil)</div><div>sdl = RAID disk 07 (sata_sil)</div><br><div></div>Of course its no problem to re-compile the kernel with AHCI as a module so I can modprobe it last. Just wondering why AHCI is now the exception to modular sata...?<br>
<br></div>Thanks -- RJ<br><br></div>
|
