Last active
February 25, 2025 04:47
-
-
Save fensoft/b27368b5588448bbe82eeb63c75edfac to your computer and use it in GitHub Desktop.
install ubuntu 22 64 bits on 32 bits EFI
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
copy https://github.com/hirotakaster/baytail-bootia32.efi/blob/master/bootia32.efi to /EFI/BOOT | |
after installing ubuntu: | |
sudo passwd ubuntu | |
sudo apt update | |
sudo apt install openssh-server | |
ssh to your computer, then: | |
sudo mount /dev/mmcblk1p2 /mnt | |
sudo mount --bind /dev /mnt/dev | |
sudo mount -t proc /proc /mnt/proc | |
sudo mount --bind /run /mnt/run | |
sudo mount --bind /sys /mnt/sys | |
sudo modprobe efivars | |
sudo chroot /mnt | |
in chroot: | |
mount -t devpts devpts /dev/pts | |
mkdir -p /boot/efi | |
mount /dev/mmcblk1p1 /boot/efi/ | |
apt update | |
apt-get remove --allow-remove-essential shim-signed | |
apt install grub-efi-ia32 grub-efi-ia32-bin | |
rm -rf /boot/efi/EFI/ubuntu | |
grub-install -v --target=i386-efi --efi-directory=/boot/efi | |
update-grub | |
exit | |
reboot |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks a lot! With some additions, these instructions allowed me to install KUbuntu 22.04 on an Acer Aspire Switch 10 E (32-bit uefi, 64-bit cpu).
I used some additional mounts according to this post:
Then, I ran
sudo modprobe efivarfs
instead ofsudo modprobe efivars
(not sure if it's a different module, or the snippet contains a typo)This made it possible for me to run this command in chroot, which I couldn't do with the mount commands provided in the snippet (you might need to
apt install efibootmgr
):sudo efibootmgr --create --disk /dev/mmcblk1 --part 1 --loader /EFI/BOOT/bootia32.efi --label "Ubuntu"
HOWEVER, I am not totally sure if I actually needed this! Because I still had no bootable device after these modifications.
What fixed it for me:
In my UEFI, I had to ENABLE secure boot, and manually add the 32-bit .efi file (in /EFI/ubuntu) as a file (give it a name), then push it to the top of the boot entries. No additional boot entry showed up after executing the
efibootmgr
command. If someone's trying this, you might want to try using the .efi file in /EFI/ubuntu instead of /EFI/BOOT when runningefibootmgr
, which might produce the same result as I got from manually adding this entry through the UEFI GUI.Some notes: