On 2012-01-26 07:06, toes wrote:
> You keep going back to talking about a “BIOS drive”, why?
>
>
> please_try_again;2434104 Wrote:
>> > It’s not Grub. It’s a motherboard/BIOS issue.
> If, you, and I, understand the situation, then you seemingly have
> presented no foundation for claiming it’s the motherboard or BIOS.
>
> I can say that based on my experience working on BIOS source code,
> there don’t appear to be any BIOS problems with this machine.
> So, what exactly makes you think that it’s a “motherboard/BIOS” issue?
> Since I feel I’ve been quoted and responded to, out of context more
> than once, I wonder if the situation really is understood.
>
> The disk drives don’t just “float around” all over the place at a BIOS
> level, on this machine. The only time I’ve had any issues, is when I’ve
> installed an instance of openSUSE.
Booting is currently a bios issue. Grub1, lilo, grub2… (and windows) all
have to use bios calls to access the disks and load the kernel. So yes,
that a disk is hd0 or hd1 is at the mercy and control of the bios.
Only after the kernel is loaded we can look at IDs or labels inside the disks.
This situation changes with UEFI. But we have no support for that in
openSUSE and yast.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)