When starting up my computer this screen automatically pops up and after 3 seconds of inactivity it automatically boots into the firmware interface and there is no other option. Yesterday it was working fine and booted into arch after 3 seconds of not pressing any keys like it normally does but today when I tried to turn my computer on this new error occured.. please send help!! Is there anyway to fix this issue from inside the firmware interface itself??
#ONLY OPTION IS REBOOTING INTO FIRMWARE INTERFACE
611 messages · Page 1 of 1 (latest)
It keeps booting into it and i cant get it to stop
This is my boot configuration inside the firmware interface if that helps
Can you chroot into it?
Its dell
Not sure how to do that i will look it up
Arch Wiki: Chroot
Here you go
you will need an installer usb
Cant find that option?
change the boot mode to something other than uefi only
is your pixel rooted?
Pixel?
Fuck
Uefi only..
Would enabling secure boot help?
@dusky yoke
the phone
no
No
So is my only option to chroot??
Fuck
It was working fine..b4.
well, then you need either an OTG adapter or a friend with a PC, and a usb drive
Dont i only need a usb drive to chroot?
Oh u need to download arch onto it
Ah
it would be twice as easy if your phone was rooted since most rooted android phones can be directly booted from
Wait ill check maybe it is?
Idk how to tell
Ill google it
if you did not root it, it most likely isn't
Damn
Ok so only option is chroot then?
How big of a usb do i need to buy
8 gigs will be enough
Ok ill get the usb stick but i might need ur guys help with chrooting like obviously ill follow the guide but..
afcours
The Arch ISO is ~900MB so 2GB should be good (to leave some extra for formatting shenanigans)
If you want to boot graphical ISOs later on, do 8GB. An 8GB one should do all but the most bloated ISOs.
95%
Will i lose my past files and have a fresh install of arch
Or itll boot into my old arch which is on the drive right?
No
The point of chrooting in this case is to not have to reinstall fully
network boot exists too.(but that's only possible once you get an efi/grub shell)
does add a boot option give you a file picker that you can use to browse your efi directory?
One sec ill check
How do i get an efi grub shell
Usually grub itself shows and option and sometimes aborts to it.
No
This is what browse for file gives
Your issue is simple. Systemd-boot cannot find your boot partition. So chroot and reinstall it
You need secure boot disabled to run arch
How come it found before??
i'm just wondering if there's a way without them buy a new usb.
Its k i bought it alr
Idk. But this is a simple issue. Bootloader can't find boot partition.
Reinstall it
there's a grub bug when the installed grub is a different version and the grub-mkconfig is a different version
.aw systemd-boot
Arch Wiki: Systemd-boot
They use systemd-boot
Not grub
Grub ≠ systemd-boot
So they have to reinstall systemd-boot from chroot then reconfigure it
Wiki tells how
Also lsblk to see if you still have your partitions there
.aw lsblk
Arch Wiki: Lsblk
When making the arch USB, use ventoy for best results
.aw ventoy
Arch Wiki: Ventoy
Which partitions? My arch one that shld be on my comps hard drive?
So flash using ventoy
Got it
All of it
Refer to the wiki on how to install your bootloader
Cuz I use grub
So systemed boot is a whole diff process right?
I didnt manually install arch b4 tho.. i used a script so
This is gonna be a bit confusing i think
Idk how you installed Arch but you choose systemd-boot as your bootloader
.s archbased
Users of unofficial install scripts and Arch-based distributions may not make support posts using the arch tag. This comes from the Arch Code of Conduct. By installing the system in a way that you do not have control over, you do not know how your system is set up or if a script silently broke something. This can cause huge issues with support, especially if people don't know you used a script.
If you need support with your system, use the other distros tag.
I used an officiall install script?
@fleet solstice how'd you know it was systemd-boot?
archinstall?
Ya i think
Because that's how systemd-boot looks by default
Ya its that not grub
You're using systemd-boot
Archinstall script offers you grub and systemd-boot
You can choose
I chose boot
Arch Wiki: Chroot
Ok i copied arch into the usb and formatted the disk using ventoy
Now ill boot into the usb
@fleet solstice
I just do normal mode right?
Cus its not grub
It made a loud beep and now its booting into uefi
I want to mount the root first right?
Sda2 being the root
@fleet solstice
.aw chroot
Arch Wiki: Chroot
I ran the lsblk thing to check my partitions
Find the right drive that contains your system
lsblk -f helps
Ya i swear its sda2?
Idk how to tell exaxtly cus sda1 is ventoy
It's not. NVMe one is your drive
/dev/nvme0n1
Partitions under it are your ESP and your root
Then mount and chroot
So run this command then mount?
I thot u could just mount first
That's a device
mount /dev/nvme0n1p2 /mnt mount /dev/nvme0n1p1 /mnt/boot
Unless you used /boot/EFI as mounting point
Then chroot
.aw chroot
Arch Wiki: Chroot
How am i meant to know if i used boot efi as a mounting point?
yeah so you mounted it /mnt/boot
actually you can change that now if you want. idk what would be a reason to though.
Ill leave it
maybe if you store loads of backups for fallbacks then...
okay
Just mount it
Then chroot
arch-chroot /mnt
From there reinstall systemd-boot
.aw systemd-boot
Arch Wiki: Systemd-boot
I can install just using the efi boot manager right
So just the first command
Bootctl install?
Srry for being annoying i just wanna make sure im doing it right
So im double checking
@fleet solstice
I did ur other steps of mounting and chroot
Ya in saying to reinstall
I use the first command from the wiki he linked
The efi boot manager one right?
Im just double checking
Small tip: if i where you I would get ventoy and get the archiso,fedora (or any other linux distro you like that installs a graphical system imidatly) and system rescue cd.
But im 99.9 percent sure thats the only one so
Probably but I'm not sure since I use grub2
That's the chroot environment
Now reinstall systemd-boot
Ya im saying to do that
.aw systemd-boot
Arch Wiki: Systemd-boot
I run the first command from the wiki
U linked right
Thats the only one saying to install
Ya
Idk if you need to regenerate the boot config but wiki tells how to
Now can i just reboot into it
Then exit chroot
Then umount -a and run poweroff
Remove the usb and try to boot
Alternatively you could switch to grub if it fails
.aw grub
Arch Wiki: Grub
Run poweroff as in just use the power off button??
Refind better
Exit chroot, unmount everything then run poweroff command
.aw refind
Arch Wiki: Refind
Save preferences for #tech-general
They only want to boot
And refind makes it easy to do that
Just lem em use what they want
It wont let me unmount
Run poweroff command
It should unmount the rest for you
Then remove the USB and try to boot
Arch Wiki: Grub
if you use multiple oses,
grub + os-prober is nice.
@fleet solstice help em installing grub. If it fails, do refind
Only use arch
It says in the wiki
To boot from a disk using UEFI, an EFI system partition is required.
Does this apply for me
As im booting from usb disk?
@fleet solstice
Yeah
Judging by your laptop, you're currently using uefi
Yup
So i needa create a partition..
Why
You already have the partitions
Btw check if you still have your kernels installed on chroot
Where's your partition layout again?
pacman -Qs linux on chroot should tell
@fleet solstice this
So tldr, check if you still have the kernels and install a bootloader
You have Vanilla kernel
pacman -Qs linux kernel
I see
So the thing is ... Installing s bootloader
Just that
So try with grub
Is that an issue?
Also os-prober unless its being pulled as a dependency
Im not dual booting
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub
Then this?
After the 1st command
yeah that looks fine
Oh wait
Specify the nvme drive too
Not the partition btw
1st command worked fine
Huh
Where in the command do i do that
So nvme0n1
Its the last argument
yeah
So after =grub?
Yes
I just write the drive name no space nothing else?
Yes
what does that do?
I don't remember doing it
What does what
Specifying the driver name?
.
Uhh
This is so long to type out..
The target?
*drive
yeah
I have efi ya
they have UEFI
It doesn't matter
Cool
(on a UEFI system)
Then stay quiet
You're doing it wrong this whole time then
Hm
Ill j type it? Will there be harm?
No
nah,
it'll be ignored, it's no use
Yeah erase the nvme part
add a space, if you're still doing it
I j mounted root and and boot and then chrooted
Ok
Thats just the name of the entry thats going to be put in the nvram
the whole command 
Aka boot menu
You may tell em how to use refind if they can't do grub
Wait
Its just a minor mistake
What matters is to have a bootloader
use spaces between directives @quick kernel
before/after every --somedirectives=somevalue
Do i need to specify the drive name in the moubt command??
Bro why didn't you put spaces between arguments
O
haish
this is what you have to do
Damn do i redo the first command then
But it still worked?
just press the up key
no just the grub install one.
You've been using spaces in between commands and it's directives before right?
I put space between slashes ya
press it multiple times to go back in your zsh history
but you didn't here
Ya ill try to fix it one sec
Where are you mounting your esp right now?
I havent done that
But i alr ran the first grub install command so
Idk what to do
You haven't mounted the esp 💀
Ya can i still do it after the first grub install command or no?
Have i fucked up
Do i just restart chroot
no
first make sure that nothing is mounted at /boot
by looking at mount or df -h... I find the latter more readable.
then do rm -r /boot/*
chroot first
You can't install grub if there's nothing to install it to
Mount it first
And then install grub
I think they should delete whatever they grub-installed to /boot/*
if anything installed that is...
grub install will install to a directory if it exists I don't think it can discern a mountpoint from a normal directory.
(after chrooting that is)
Hmm you mounted your esp at /boot
How do i do this what delete command to run
Oops
So ill chroot and have to unmount
Kk
Remount the esp?
Yes
To get into chroot im confused cus u mount the root then boot
So idk where the esp comes in
The nvmep1 is supposed to be esp
ls -di /
btw this shows 2 if you're not chrooted.
as a quick check.
Its alr mounted
?
I alr mounted this stuff
Before i entered chroot
Thats why im lost
I ran these steps
@true blade
I can still unmount while inside the /mnt/boot/efi right??
nme
Mb
smh
yes
I go into this directory then run the mount command?
No
Do i chroot first ?
Just stay there in ~
Ok
no
/mnt/boot/efi
It doesnt work
I added the efi at the end
Add --mkdir after mount
Good
Yeah I think
Chroot and then run the grub-install thingy
How do i delete it?
Without the /dev/nvme thingy
with rm
Do i delete the efiboutmgr as well?
Its not working
Or just the grub install?
Command
goto /boot
cd boot
Don't write random things if you don't know it
then ls -lrta
Just cd to /boot and delete the things grub related
there's nothing there
he just created that dir earlier
oh okay, I'm not up to speed.
I mean you already installed that
Yes
You NEED to put spaces between arguments
otherwise the shell will treat it as one command
I tried to follow this
@fleet solstice
Lol when ur done with mobile league
Ofc
Remove the nvme thing from the last
Yup
Yay
directory
I have that?
Oh how come the installation worked then
It must've installed it in the default location or the current directory
Fixed
Do ls /boot
Do ls /boot/efi
very old phones present themselves as mass storage
Looks good.
But grubs not done installing is it?
What abt this
"Remember to #Generate the main configuration file after finalizing the configuration"
@fleet solstice @fleet solstice what would this have done?
Theres other stuff in the wiki so im lost
I changed it now...but oops
Too late?
Do pacman -Syu
Errors
Rip
No it's okay, you might need to delete some stuff to undo what that command did. I don't know what it does by default.
Connect to the internet using nmcli or nmtui or something
The root unchrooted shell of the archiso you can use iwtcl,
If nmcli in the chroot doesn't work.
We're doing this so you can generate the kernel executables.(updating does this too), since your /boot is empty and doesn't have those.
So shld i try nmtui?
And iwtcl?
Instead?
No. I think you can generate the kernel image by pacman -S linux, no need to update
Download this ya?
So i get the kernel img
check if it generated those images in
ls /boot
then follow
It did
yes it did.
yeah
yep. reboot
And take out usb and retry booting?
Then what
Wym
Do i take out usb then hold power off button
poweroff, take out usb, press power button
Ok
reboot doesnt unload some info from firmware, causes issues sometimes
lets go
Wait so now it will always just automatically use grub bootloader?
so i think it should work fine unless grub breaks with an update again lol
i think installing grub-hook (aur) might be smart
i did it and have never had an issue, even with the breaking change made to grub
Hmm
What breaking change made to grub?
To install grub when chrooted:
Pacman -s grub efibootmgr
grub-Install /dev/you're drive name (iirc nvme0n1)
grub-mkconfig -o /boot/grub/grub.cfg
Exit
Remove your usb
Umount -a (will unmount all drives that aren't bussy)
Reboot
what page is this?
endeavouros reddit sticky
https://www.reddit.com/r/EndeavourOS/comments/wygfds/full_transparency_on_the_grub_issue/
\
lol ofc i am not everyone, but its a good idea to update grub configs after grub update and a grub hook does that for you so you dont have to remember
me too.
[Trigger]
Operation = Install
Operation = Upgrade
Operation = Remove
Type = File
Target = usr/lib/modules/*/vmlinuz
[Action]
Description = Updating GRUB Config
Depends = grub
When = PostTransaction
Exec = /usr/bin/grub-mkconfig -o /boot/grub/grub.cfg
at /usr/share/libalpm/hooks/grub.hook, owned by root with permissions 0644
this is what the aur package does
Nice 
... solved
#9742 📣 If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.
- You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
- You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".
Your title should be like so: https://cdn.discordapp.com/attachments/503224329191030787/1039841700417384498/image.png
Thank you
@quick kernel is your issue solved?
yes
