Johan Nielsen writes:
Torsdag den 19. august 2004 10:16 skrev Per Jessen:
Ti Kan wrote:
Plausible explanation. However you should also look at the INITRD_MODULES= line in your /etc/sysconfig/kernel file. This specifies kernel modules that should be loaded early in the boot process, before
Ah yes, very true. I never use a stock SuSE kernel and almost never use an initrd, so it didn't occur to me to mention that.
Trying to summarize is this the issue/reason when ide-devices is "found" before SATA devices (ASUS P4C800E-Deluxe board).
SuSE's standard kernels have the IDE module linked statically into the kernel, so it stands to reason that the IDE drives are first found before any other disk controller driver modules are loaded. However I am pretty sure this behavior could be modified via boot parameters.
And what about the case with Promise ide-controllers they're also detected before drives on regular controllers (read controllers on the main board) ??
I don't know, how is the Promise IDE controller different than the one on the motherboard? If they use the same IDE kernel driver, then the kernel will "discover" each controller in some order, perhaps by the hardware slot. If your motherboard's PCI bus appears in a lower "slot" than the embedded IDE controller, that would explain it. Some BIOS setups might allow you to modify the order with which the slots are ordered. -Ti