On 04/24/2017 05:28 AM, Felix Miata wrote:
Is there such a BIOS as can or will look to device HD1 aka sdb instead of HD0 aka sda when exists bootable (generic/legacy/Windows) code on HD0? If not, then the BIOS will never use it. Grub on sdb will only be used in such a case by chainloading from from elsewhere.
Most modern BIOS can swap physical devices HD0 and HD1 via function key at POST or via setup menu, but that's not the same thing, as the second physical device in such case is presented as if the first. The installer or updater won't know the BIOS has done any such thing.
This is on my HP8760w laptop. It has 2 hard drive bays (actually 3, the dvd drive can be removed and it will server as a 3rd bay). All are directly bootable via the bios. The problem is I have the original Win10 SSD in bay 1, and SuSE in bay 2. I boot direct to SuSE. With this setup, grub updated, via their fried os_prober, always overwrites the MBR on the Win10 drive instead of writing the bootloader to drive 2. This is frustrating as hell (and probably a large part of the reason that Arch only provides os_prober on the install media and does not install it in the OS) With the SuSE install on the 2nd drive, grub should only install as: grub-install --target=i386-pc /dev/sdb but instead in the install everywhere leap setup, it installs as grub-install --target=i386-pc /dev/sda (the win 10 drive) even specifying in /etc/default/grub_installdevice /dev/sdb1 /dev/sdb activate generic_mbr and explicitly specifying the UUID for the install filesystem in /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/disk/by-uuid/3cadab5b-13b4-4dce-84d3-05e2070f741c splash=silent quiet showopts" GRUB_DISABLE_OS_PROBER="true" I give up... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org