[opensuse-support] boot priority on (Intel) iMac
I installed 15.0 on a previously virgin HD, partitioning in advance, and directing openSUSE which partitions to use for what. Good so far. Then I installed Snow Leopard. It wrested boot away from 15.0, so I installed rEFInd on the OS X system partition. That worked as advertised with no fuss necessary, allowing selection among OS X, 15.0, shutdown, reboot, and more that I don't remember. Then I ran YaST2 bootloader to see what would happen. Sure enough, it: 1-usurped control from rEFInd, and 2-omitted OS X from among the Grub2 menu choices. I used efibootmgr to reset the order: # efibootmgr BootCurrent: 0000 BootOrder: 0000,0001 Boot0000* opensuse Boot0001* rEFInd Goot Manager Boot0080* Mac OS X BootFFFF* # efibootmgr -o 0001,0000 BootCurrent: 0000 BootOrder: 0001,0000 Boot0000* opensuse Boot0001* rEFInd Goot Manager Boot0080* Mac OS X BootFFFF* but Grub still shows up instead of rEFInd on reboot. There is no BIOS to change boot order on Mactel. What can be done to prevent openSUSE from stealing boot control from rEFInd? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 07/12/2018 11:09 PM, Felix Miata wrote:
but Grub still shows up instead of rEFInd on reboot.
Your specified boot order does not take? If that happens, it's a firmware limitation. You could probably create a grub2 boot entry that chains to refind.
There is no BIOS to change boot order on Mactel. What can be done to prevent openSUSE from stealing boot control from rEFInd?
In normal operation, openSUSE won't "steal" control. It only does that when booting is reinstalled. Making changes with Yast bootloader might do that. Otherwise, it will probably only happen when there's an update to "grub2-efi" or to "shim". That's perhaps once every 6 months for Leap, and around weekly for Tumbleweed. I should say for Tumbleweed, that it can go for many weeks without such an update, but then it might update several times over the next week. The "around weekly" is a guessed average. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Neil Rickert composed on 2018-07-12 23:59 (UTC-0500):
Felix Miata wrote:
but Grub still shows up instead of rEFInd on reboot.
Your specified boot order does not take? If that happens, it's a firmware limitation. You could probably create a grub2 boot entry that chains to refind.
I shutdown to do other things for a while, then started up using the option key. That brought up only a picture of the installed HD. I clicked it to proceed and the rEFInd menu came up with two openSUSEs, one for rEFInd to load the kernel/initrd direcly from /, and the other for loading it via EFI/opensuse/grub64.efi, plus the OS X entry, and a fourth "Boot Legacy OS from whole disk volume", which if selected eventually winds up showing "No bootable device - insert boot desk and press any key".
There is no BIOS to change boot order on Mactel. What can be done to prevent openSUSE from stealing boot control from rEFInd?
In normal operation, openSUSE won't "steal" control. It only does that when booting is reinstalled.
That's sounds like what I call stealing. zypper up, KDE updater, etc. shouldn't change booting except as minimally required when a new kernel is installed. Are you saying initial installation and yast2 bootloader alterations are the only times "reinstallation" occurs? Are the latter primarily or entirely calls to grub2-install?
Making changes with Yast bootloader might do that.
yast2 bootloader is what I did. I changed only the timeout value, because as you and Carlos and others have often communicated, it's easier than looking up how to reconfigure the mini-OS that is Grub2.
Otherwise, it will probably only happen when there's an update to "grub2-efi" or to "shim". That's perhaps once every 6 months for Leap, and around weekly for Tumbleweed. I should say for Tumbleweed, that it can go for many weeks without such an update, but then it might update several times over the next week. The "around weekly" is a guessed average.
What I'm doing here is trying to get a Mac ready to sell to someone interested in OS X + Linux on one Mac. I could get by fine knowing how the system works, but a mere mortal is going to wonder what happened and have no idea how to fix something like this when what he needs is to use it for some kind of work. Plus, this thing is famously slow to POST and get the first boot menu to appear. rEFInd looks like a menu Apple built, so I want it to be and stay first. Green/black mousetype Grub with all the dots and dashes in truncated menu entries in a little bitty portion of the center of the screen is more like Mac antithesis, not wanted, particularly since os-prober is inexplicably managing not to offer even one other OS selection. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 07/13/2018 01:47 AM, Felix Miata wrote:
That's sounds like what I call stealing. zypper up, KDE updater, etc. shouldn't change booting except as minimally required when a new kernel is installed. Are you saying initial installation and yast2 bootloader alterations are the only times "reinstallation" occurs? Are the latter primarily or entirely calls to grub2-install?
Reinstall uses "efibootmgr" to add a boot entry. And "efibootmgr" always puts the new entry first. That's what causes this "stealing". A reinstall of booting is the only thing I have seen that opensuse does to affect this. It is reinstalled via yast-bootloader, via a command line use of "grub2-install" or "shim-install". And it is reinstalled when any package in the chain has been updated. I've only seen that happen for updates to "grub2-efi" and updates to "shim". Back in the era of openSUSE 12.3, booting was reinstalled by running "mkinitrd". I complained about that, and they changed that. So currently, a kernel update does not reinstall booting -- it only updates the boot menu.
Plus, this thing is famously slow to POST and get the first boot menu to appear. rEFInd looks like a menu Apple built, so I want it to be and stay first.
I don't know of a way to make it stay first. On one of my computers (a Lenovo ThinkServer), it does stay first. That's because the firmware changes the boot order back on every boot. To make a permanent boot order change, I have to go into BIOS setup. But actually, I rather like that the order stays fixed. This change of boot order is an annoyance and a misfeature of UEFI, in my opinion. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (2)
-
Felix Miata
-
Neil Rickert