[TynesideLUG] Fwd: Booting Bunsenlabs Linux on an Acer Chromebook 14
Will McElderry
will at mcelderry.com
Wed Dec 8 13:31:09 UTC 2021
Hi Ian (and all again)
I' ve just downloaded the Bunsenlabs installation media image, mounted
it and confirmed that it (at least) has various UEFI components, so will
boot on an UEFI enabled system to get the installer running.
Ian has been told by someone that Bunsenlabs doesn't support UEFI - so
maybe the installer is not be doing everything necessary to configure
the system from then on - if you want to try a manual fix, you could
possibly get shim on there:
https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot#shim
<https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot#shim>
I've just tried executing an unsigned bootloader with SecureBoot
enabled, and I get the response:
   Error reported: Access Denied
so if you find your bootloader and start it (as detailed below), then
get that response, that may indicate that you need to install shim to
work around the issue.
Will.
P.S. I've included my message below that I had intended to send to the
list in case others want to contribute too.
I've missed Ian's reply off because I don't know if Ian would be happy
for me to promote his emails from private to public (not that there's
anything in there I expect Ian would worry about!)
-------- Forwarded Message --------
Subject: Re: [TynesideLUG] Booting Bunsenlabs Linux on an Acer
Chromebook 14
Date: Wed, 8 Dec 2021 12:57:22 +0000
From: Will McElderry <will at mcelderry.com>
To: Ian Bruntlett <ian.bruntlett at gmail.com>
Hi Ian,
If it booted Windows it will likely be SecureBoot enabled (unless
someone's already disabled it to get Windows on there?)
Given you've booted it from the Bunsenlabs USB flash drive, it seems
likely that Bunsenlabs does support UEFI - and having looked it up
Bunsenlabs seems to be basically Debian, so again seems likely that it
can work with UEFI. While it probably can work with UEFI, I'd guess
there's something that means it isn't working with UEFI - either it's
not using the shim bootloader, or it's got something wrong with the
bootloader entry.
In terms of how to use the UEFI shell I used this for reference:
https://linuxhint.com/use-uefi-interactive-shell-and-its-common-commands/
<https://linuxhint.com/use-uefi-interactive-shell-and-its-common-commands/>
Quick start: it's DOS.
To change to the 'drive' then discover what's there type the following
at the prompt:
> fs0:
> ls
then 'cd' to the correct directory using a backslash if you want to
change multiple levels (e.g. 'EFI\grub')
> cd \EFI\grub
Start the application just by typing it's name.
Or perhaps a better answer:
https://askubuntu.com/questions/981267/how-to-install-ubuntu-using-the-efi-shell
<https://askubuntu.com/questions/981267/how-to-install-ubuntu-using-the-efi-shell>
Will.
More information about the Tyneside
mailing list