# Reboot into firmware interface on boot **URL:** \ **Category:** Kernel, boot, graphics & hardware\ **Created:** [July 17, 2023, 1:38am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343 "2023-07-17T01:38:31Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [July 17, 2023, 1:38am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/1 "2023-07-17T01:38:31Z")
This is a very unexpected and inconvenient error for me. The computer worked fine yesterday, I updated like normal yesterday, unfortunately I don’t remember which packages were updated. Now I only get the option to reboot into firmware interface on systemd splash screen and the computer boots into bios after that. This is a problem, I am currently halfway through month long vacation in Vietnam, I do not have access to different computer, USB or anything of that kind. Only my phone. Is there anything I can do except reinstall EOS when I get back home? I do have USB with EOS iso on it at home. I haven’t been able to enable TTY or anything else during startup. ---
**Author:** ![samarium](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/samarium/32/78616_2.png) [@samarium](https://forum.endeavouros.com/u/samarium)\ **Post date:** [July 17, 2023, 2:17am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/2 "2023-07-17T02:17:05Z")
Can you download a USB thru the phone and use an app to write it to a USB you can find somewhere? Convince someone to loan you? Theoretically you could setup the phone so the phone USB port looked like a USB drive. Don’t know any software that would do that, but it is possible with a raspberry pi zero or any linux with USB OTG capability. So maybe there is a phone app that can do that? ---
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [July 17, 2023, 2:35am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/3 "2023-07-17T02:35:41Z")
I know no software on phone that can write iso to a USB. Going to change this to I don’t know about any software that I trust that can do this ---
**Author:** ![samarium](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/samarium/32/78616_2.png) [@samarium](https://forum.endeavouros.com/u/samarium)\ **Post date:** [July 17, 2023, 3:04am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/4 "2023-07-17T03:04:45Z")
I don’t know any either, I have heard that there are apps, and it is not something that is that difficult, but getting raw access to the USB might be interesting on andoid or iOS. Maybe someone else can write a USB for you? I’ve see various pages on recovering from grub / EFI boot issues, depends on grub or systemd-boot to some extent. You might have to enable EFI firmware shell so you can boot into that? Boot the EFI shell and navigate around the FS\*: and BLK\*: devices, using cd and ls, and try and find a .efi file to run. IIRC selecting a fs/blk device is just ‘fs0:’ or might be ‘cd fs0:’ /EFI/BOOT/BOOTX64.EFI /EFI/grub/grubx64.efi /EFI/systemd/systemd-bootx64.efi Won’t work if the upgrade killed your bootloader .EFI file of course, but it sounds like you aren’t getting that far. Might be worth visiting the BIOS and make sure you still have your boot device enabled. If the upgrade killed your grub or systemd-boot setup, that isn’t going to help much. No good telling you that you should have been more prepared, I’m sure you will be at least have a boot USB with you next time. Lots of options for redundancy, you just have to think it is worth the hassle. ---
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [July 17, 2023, 3:11am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/5 "2023-07-17T03:11:43Z")
Yeah, I will be better prepared next time. This is the first time the system crashes and it is not my fault. This distro has been stable for me for over a year so I was very confident that I didn’t need backup USB. I suspect that the bootloader is borked. I have no other selection than to reboot into firmware interface when I boot up. > **[New video by Ólafur Víðir Guðbjargarson](https://photos.app.goo.gl/fz33wLuqHSWoRuTb7)** Here is what happens. ---
**Author:** ![anthony93](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/anthony93/32/92169_2.png) [@anthony93](https://forum.endeavouros.com/u/anthony93)\ **Post date:** [July 17, 2023, 3:45am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/6 "2023-07-17T03:45:46Z")
> [@olividir](#): > > Now I only get the option to reboot into firmware interface on systemd splash screen and the computer boots into bios after that. Seems like your bootloader entries disappeared for some reason. You should boot into a live ISO, chroot, and run `reinstall-kernels`. This assumes that you have either `kernel-install-for-dracut` or `kernel-install-for-mkinitcpio` installed. [https://wiki.archlinux.org/title/chroot](https://wiki.archlinux.org/title/chroot) Here’s a quick guide on how to use `arch-chroot` if you need it. Basically, the key steps are: 1. Mount your root and esp partitions. 2. Run `arch-chroot ` ---
**Author:** ![samarium](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/samarium/32/78616_2.png) [@samarium](https://forum.endeavouros.com/u/samarium)\ **Post date:** [July 17, 2023, 3:53am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/7 "2023-07-17T03:53:46Z")
Linux Boot Loader is probably systemd-boot I didn’t see an EFI shell in the boot options. I you can find and enable it then you might be able to at least poke around and see what lives on your EFI partition? ---
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [July 17, 2023, 3:58am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/8 "2023-07-17T03:58:00Z")
I thought so, will have the option to do so in August. Sorry I can’t give more info. ---
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [July 17, 2023, 3:58am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/9 "2023-07-17T03:58:42Z")
The bootloader is borked, will fix this when I get home in August. ---
**Author:** ![samarium](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/samarium/32/78616_2.png) [@samarium](https://forum.endeavouros.com/u/samarium)\ **Post date:** [July 17, 2023, 4:02am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/10 "2023-07-17T04:02:00Z")
Found this: [https://f-droid.org/packages/eu.depau.etchdroid/](https://f-droid.org/packages/eu.depau.etchdroid/) EtchDroid, supposedly non root. Also found drivedroid to make your phone emulate a drive, but it requires root on the phone. If you don’t fix the laptop, maybe just enjoy the countryside : - ) ---
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [July 17, 2023, 4:15am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/11 "2023-07-17T04:15:40Z")
I’ll just do it in August when I get home, the least hassle in my opinion. ---
**Author:** ![manuel](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/manuel/32/396_2.png) [@manuel](https://forum.endeavouros.com/u/manuel)\ **Post date:** [July 17, 2023, 1:58pm UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/12 "2023-07-17T13:58:42Z")
For the record, it would be interesting to see which were the packages that you updated last. You can do this (before reinstalling 😉) after booting with the USB installer drive. So, if you have time to do so in August, please run this terminal command: ```auto tail -n200 /var/log/pacman.log | eos-sendlog ``` and show the returned address here. ---
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [July 18, 2023, 1:34am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/13 "2023-07-18T01:34:09Z")
After chrooting? But sure I’ll do that. Hoping that installing kernel and dracut through chroot again will solve my issue. ---
**Author:** ![manuel](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/manuel/32/396_2.png) [@manuel](https://forum.endeavouros.com/u/manuel)\ **Post date:** [July 18, 2023, 8:11pm UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/14 "2023-07-18T20:11:11Z")
> [@olividir](#): > > After chrooting? Yes. > [@olividir](#): > > Hoping that installing kernel and dracut through chroot again will solve my issue. Hope so too. 😃 ---
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [August 4, 2023, 9:21pm UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/15 "2023-08-04T21:21:05Z")
OK, just got home after over 24 hour travel from Vietnam, and I am having slight problem with chrooting. I am following this tutorial [https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/](https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/) and at `sudo cat /mnt/etc/fstab` command I get ```auto cat: /mnt/etc/fstab: No such file or directory ``` I have successfully mounted `/dev/nvme0n1p2`, at least I think I have. To @manuel ```auto tail -n200 /var/log/pacman.log | eos-sendlog tail: cannot open '/var/log/pacman.log' for reading: No such file or directory ``` And finally ```auto sudo mount /dev/sda1 /mnt/efi mount: /mnt/efi: mount point does not exist. dmesg(1) may have more information after failed mount system call. ``` Now, I am kind of WAY TOO TIRED to be working on this right now, having gone through 7 time zones in little over 24 hours and I am feeling quite jet-lagged. I’ll sign in tomorrow and see what is what. \*Whole terminal from when I started this, I might be chrooting wrong ```auto [liveuser@eos-2023.03.06 ~]$ sudo lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashf 4.0 0 100% /run/archiso/airootfs sda ├─sda1 exfat 1.0 Ventoy BC49-03DA │ └─ventoy iso9660 Joliet Ex EOS_202303 2023-03-06-14-54-40-00 0 100% /run/archiso/bootmnt └─sda2 vfat FAT16 VTOYEFI B228-8EFB nvme0n1 ├─nvme0n1p1 vfat FAT32 93A1-A3B1 └─nvme0n1p2 btrfs endeavouros e29ffbfa-0041-486b-8fed-f4bf7422e802 [liveuser@eos-2023.03.06 ~]$ sudo mount /dev/nvme0n1p2 /mnt [liveuser@eos-2023.03.06 ~]$ sudo cat /mnt/etc/fstab cat: /mnt/etc/fstab: No such file or directory [liveuser@eos-2023.03.06 ~]$ sudo cat /mnt/etc/fstab cat: /mnt/etc/fstab: No such file or directory [liveuser@eos-2023.03.06 ~]$ tail -n200 /var/log/pacman.log | eos-sendlog tail: cannot open '/var/log/pacman.log' for reading: No such file or directory [liveuser@eos-2023.03.06 ~]$ sudo mount /dev/sda1 /mnt/efi mount: /mnt/efi: mount point does not exist. dmesg(1) may have more information after failed mount system call. ``` ---
**Author:** ![manuel](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/manuel/32/396_2.png) [@manuel](https://forum.endeavouros.com/u/manuel)\ **Post date:** [August 5, 2023, 1:21am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/16 "2023-08-05T01:21:50Z")
> [@olividir](#): > > `sudo mount /dev/nvme0n1p2 /mnt` After this command you could try command ```auto ls -l /mnt ``` It should show the root (/) folder contents. If that looks OK, then you should arch-chroot to do other commands. ---
**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\ **Post date:** [August 5, 2023, 5:39am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/17 "2023-08-05T05:39:26Z")
> [@olividir](#): > > ```auto > nvme0n1 > ├─nvme0n1p1 vfat FAT32 93A1-A3B1 > └─nvme0n1p2 btrfs endeavouros e29ffbfa-0041-486b-8fed-f4bf7422e802 > > ``` You are using a Btrfs filesystem for your system partition. Before doing `arch-chroot /mnt` you would need to adapt your mount commands to to take account for the system’s subvolumes. > ##### BTRFS filesystem installs > > you need to know your subvol names and their associated mount points inside the system path. > > Per default EndeavourOS uses this scheme: > > `btrfsSubvolumes:- mountPoint: /subvolume: /@- mountPoint: /homesubvolume: /@home- mountPoint: /var/cachesubvolume: /@cache- mountPoint: /var/logsubvolume: /@log` > > _Not all subvolumes need to get mounted to use arch-chroot it needs mainly the / (@) if you only want to repair grub per example_ > > `sudo mount -o subvol=@ /dev/sdXn /mnt` > > `sudo mount -o subvol=@log /dev/sdXn /mnt/var/log` > > `sudo mount -o subvol=@cache /dev/sdXn /mnt/var/cache` > > `sudo mount -o subvol=@home /dev/sdXn /mnt/home` > > And your ESP needs to get mounted also … as it is not inside your BTRFS scheme and using its own fat32 partition: > > `sudo mount /dev/sdXn /mnt/efi` > > **where in all cases /dev/sdXn needs to be changed** according to what is used on your install as partition/device path and the mount path for the **ESP** needs to get changed according to your installed system in case. If it is **/efi** you need to mount on **/mnt/efi** if it is **/boot/efi** it would be **/mnt/boot/efi** … > > Now you will be able to arch-chroot into your **BTRFS** system, as you can see above under **Run arch-chroot to login to the installed system**. > > [https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/](https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/) ---
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [August 5, 2023, 6:41am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/18 "2023-08-05T06:41:04Z")
Good morning, unbelievable how much a sleep can do for you. @manuel and @pebcak I feel like I am getting mixed results when following your information here. ```auto [liveuser@eos-2023.03.06 ~]$ ls -l /mnt total 0 drwxr-xr-x 1 root root 128 May 11 13:12 @ drwxr-xr-x 1 root root 108 May 12 10:52 @cache drwxr-xr-x 1 root root 16 May 11 13:13 @home drwxr-xr-x 1 root root 262 Jul 15 09:53 @log [liveuser@eos-2023.03.06 ~]$ sudo mount -o subvol=@ /dev/nvme0n1p2 /mnt mount: /mnt: /dev/nvme0n1p2 already mounted on /mnt. dmesg(1) may have more information after failed mount system call. [liveuser@eos-2023.03.06 ~]$ sudo mount -o subvol=@log /dev/nvme0n1p2 /mnt/var/log mount: /mnt/var/log: mount point does not exist. dmesg(1) may have more information after failed mount system call. [liveuser@eos-2023.03.06 ~]$ sudo mount -o subvol=@cache /dev/nvme0n1p2 /mnt/var/cache mount: /mnt/var/cache: mount point does not exist. dmesg(1) may have more information after failed mount system call. [liveuser@eos-2023.03.06 ~]$ sudo mount -o subvol=@home /dev/nvme0n1p2 /mnt/home mount: /mnt/home: mount point does not exist. dmesg(1) may have more information after failed mount system call. [liveuser@eos-2023.03.06 ~]$ sudo mount /dev/nvme0n1p2 /mnt/efi mount: /mnt/efi: mount point does not exist. dmesg(1) may have more information after failed mount system call. ``` I find it hard to believe that `ls -l /mnt` shows me the mounting points but I can’t mount any of them. This is a standart BTRFS install. I am not getting why it won’t mount. ---
**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\ **Post date:** [August 5, 2023, 6:46am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/19 "2023-08-05T06:46:35Z")
Unmount whatever is mounted at /mnt first: `sudo umount -R /mnt` and start over following the instructions for Btrfs system. ---
**Author:** ![olividir](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/olividir/32/69217_2.png) [@olividir](https://forum.endeavouros.com/u/olividir)\ **Post date:** [August 5, 2023, 7:05am UTC](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343/20 "2023-08-05T07:05:17Z")
That seems also being giving me weird behaviour ```auto [liveuser@eos-2023.03.06 ~]$ sudo umount -R /mnt [liveuser@eos-2023.03.06 ~]$ sudo mount -o subvol=@log /dev/nvme0n1p2 /mnt/var/log mount: /mnt/var/log: mount point does not exist. dmesg(1) may have more information after failed mount system call. ``` I’ll try unmounting again. [Next page](https://forum.endeavouros.com/t/reboot-into-firmware-interface-on-boot/43343.md?page=2)