----- Original Message -----
From: "John"
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. 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. My impression though is that my initial problems were entirely down to grub getting data that caused numerical errors. Subsequent problems being caused by intel not reseting the discs once the raid was removed, and suse getting it's knickers in a twist. ------------ 2.4 kernels had the ability for a while to to make use of the fake-raid hooks in the bios to boot (the way FreeBSD still does, and Windows.) That is exactly the purpose and the definition of fake-raid, to provide just enough ability to get started without actually doing any raid work in the bios or firmware. That support was dropped in 2.6 Doesn't make sense? Agrevates you? Welcome to Linux. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org