On Fri, 2016-04-01 at 12:21 -0600, Chris Murphy wrote:
On Thu, Mar 31, 2016 at 11:16 PM, Dave Howorth <dave@howorth.org.uk> wrote:
I'm disappointed that Acer haven't seen fit to reply to my query to them about editing the machine's boot menu. I may try installing rEFInd to get single stage multi-booting rather than chainloading.
Understand any legit firmware bug is going to have to find its way up to engineering, and there's usually a thick filtering layer between user and engineering. What I'd expect is, engineering will take weeks to months to get the code fixed, assuming it's a model they're actively supporting with firmware updates. And then support will ask you to update your firmware once they get informed from engineering and website folks that there's an update available.
What I'd probably do is take a cell phone screen shot of the boot manager menu showing only Windows; show the contents of tree -L 3 /boot/efi to show the ESP filesystem tree; show the contents of efibootmgr -v; and then point out that it's not conforming to UEFI spec section 3 regarding the Boot Manager. *shrug* from that spec all I see off hand is they have to honor boot order and next boot variables in NVRAM when there's a matching path to OSloader, but pretty much seems to leave them off the hook UI wise if their displayed boot list is incomplete. That's kinda silly...
I think you're right. I haven't read the spec but I've seen that view stated elsewhere. It sounds like something the firmware engineer would do between noon and 1pm, or possibly between 2pm and 3pm. https://www.happyassassin.net/2013/05/03/a-day-in-the-life-of-a-firmware-eng... Acer did come back to me now, with a classic 'support' answer: "This unit is been manufactured with Windows 10 operating system.There are no specific option in the BIOS to choose boot operating system and also Acer has not released any BIOS update with the firmware upgrade to enable users to choose boot operating system. "Windows 10 is set as the default boot operating system as the unit is manufactured with it." Fortunately the UEFI spec does apparently require them to actually boot what they're told by efibootmgr, even if they won't display it. But one oddity is that if I tell it to boot ONLY mint (-o 0002), it does it once and then boots only openSUSE whilst the boot order returns to 0001,0000,0002. (openSUSE, Win10, Mint) I haven't figured out what's going on there. rEFInd, here I come. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org