John wrote:
On Friday 09 May 2008 18:07:43 Per Jessen wrote:
Carlos E. R. wrote:
For software raid, the kernel and modules needed to access the raid have to be accesable before the system is running and the raid itself mounted.
Yes, they're in the initrd.
/Per Jessen, Zürich
I have a problem with that comment. Windoze for instance has no problem at all booting - I assume it uses the intel bios maybe at a reduced performance level. Maybe even the board bios itself. Suse 10.0 also had no problems at all with the same drives again with an intel on board soft raid. Also I don't see how windoze can have loaded the drivers before it has booted.
John, I don't know why you would have a problem with my comment - it's just a simple Linux fact. The Linux boot setup is probably a little different to that of Windows (I don't know how Windows does it). Typically the bootloader (lilo, grub et al.) will load the Linux kernel into core, then load the initial ramdisk as/into the root filesystem. Drivers that are needed very early in the process are put into the initrd and loaded from there - this goes for disk drivers, cpu support etc. Once access to the real root file system has been established, the initial root file system is swapped for the real one, and the init-sequence takes over.
The suse 10 install did point out that the current kernel didn't support the discs and that it might not work but it did. Sounds like the kernel people decided to ignore these boards even though there are a huge number on the planet.
Which boards exactly? You can't assume they were ignored by the kernel developers - chances are the board manufacturer ignored Linux instead. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org