> ubuntu failed to update the efi boot catlog to point to grub.
I checked on the Toshiba Satellite NB10-A-10N during my testing and after the installation was done when I ran `efibootmgr -v` the typical all lowercase "ubuntu" entry was in the output. When I restored the drive to the initial state and removed the entry to reinstall with secure boot enabled the result was the same on this machine: the catalog was updated. I think we can rule that out.
> 2) The machine's buggy firmware assumes that if the default loader exists, it
> should use that, no matter what the boot catalog says.
I haven't tested this scenario as far a can remember and I don't have access to such a machine currently.
Would it be a good idea to put this up to the top of the report and set a corresponding tag or status so that someone else with such hardware can provide the information?
> good going microsloth for violating the uefi spec already.
I'd rather put the blame on the manufacturers or who ever writes the firmware, but that wouldn't help solving the problem I guess. :)
Hello Phillip and everyone else,
> ubuntu failed to update the efi boot catlog to point to grub.
I checked on the Toshiba Satellite NB10-A-10N during my testing and after the installation was done when I ran `efibootmgr -v` the typical all lowercase "ubuntu" entry was in the output. When I restored the drive to the initial state and removed the entry to reinstall with secure boot enabled the result was the same on this machine: the catalog was updated. I think we can rule that out.
> 2) The machine's buggy firmware assumes that if the default loader exists, it
> should use that, no matter what the boot catalog says.
I haven't tested this scenario as far a can remember and I don't have access to such a machine currently.
Would it be a good idea to put this up to the top of the report and set a corresponding tag or status so that someone else with such hardware can provide the information?
> good going microsloth for violating the uefi spec already.
I'd rather put the blame on the manufacturers or who ever writes the firmware, but that wouldn't help solving the problem I guess. :)