Bazzite never configures a bootloader... (Failed to write bootloader)
As the title says, the installer NEVER configures a bootloader, im using ASUS Laptop ISO. Tried even doing the bootloader manually, but grub is fucked up and Systemd files are gone in the iso.
Solution:Jump to solution
so yea, the solution if anyone has it (on laptop) is updating the bios to a modern version (or reinstalling it if possible)
resetting the nvram too...
67 Replies
To add, i have all my disks formated (no dual boot)
what are you dualbooting with?
setting up the bootloader manually isn't that hard
it's just getting the installer to not touch the existing one
that's something i don't know how to do
all you really need is fedora's grub installed & a specific config file that will never really change
since fedora atomic doesn't directly touch the bootloadr
I said im not dualbooting, the disk is formated
Full Linux setup
I tried it, but always get files missing from the iso
Tried using systemd, files doesn't exist on the bazzite iso
yeah that confuses me
tried the same thing as you before got the same result
Tried using grub but get a .conf file missing error
Again, it looks like the iso is missing stuff
I tried using fedora workstation due to having access to DNF, but systemd doesn't get added to bios bootloader, and forcing it through ventoy just gives me enter to bios, no entries
Also, chroot doesn't work, getting always /bin/bash no such file or directory
hmm what about installing grub with fedora?
or are you having trouble even booting workstation
Nono, i can boot workstation fine! Its the only way to use stuff like DNF or even get some files
Im using live boot (usb)
hmm what did you try to chroot into?
On what i have installed
Again, i managed to install Bazzite, just getting the failed to write boot error, continued, and thats all
The only thing i have, is grub terminal
if you're up for it we can try something silly
bazzit's bash isn't in
/bin/bash physicallyI mean, i always can try
I didn't sleep trying to fix this lol
how familiar would you say are with Linux
you seem to be confortable with installing the bootloader
Three years already
Im just installing bazzite on my brother friends laptop asus vivobook)
good enough
you're probably used to it enough
Yea, isn't the first time i have serious bootloader problems
But not like this
It seems almost like a bug how the bootloader files are missing on bazzite
the installer doesn't have much to do with bazzite though
as far as i can tell it's just the fedora installer
which contains & can install bazzite
which boils down to 1 command
ever installed arch?
Yea
The idea of installing bazzite its because that friend never used Linux
Just wants better performance and gaming so, thats why im here
i guess then we shouldn't go with my silliest idea
i was thinking you get workstation running & use that as a jumping off point to manually install bazzite
i could help with that but it'd probably take a while
Maybe
Although i had the idea of
Instead of using ASUS iso, using the generic laptop iso
try that also
this sort of thing happens when there's already a fedora folder on the ESP
will do that and report back
been messing around with manual OSTree distro installation for a few days now
only really struggling to set up a user after installing
though i've been trying the old passwd command way
there's a different way though
there's this thing called systemd-homed
a systemd tool that manages home folders/users
in this setup everything relevant to the user is stored in the home folder itself
including the stuff that goes in /etc/passwd & /etc/shadow
it's in a
~/.identity fileBtw im rn about to install the laptop iso
which is cryptographically signed json
to transfer an user you just transfer the cryptographic keys & a file that gets mounted as the user's home on the new system
an AI summary told me this is very much supported on fedora atomic out of the box
couldn't find the official source of this at a glance
though it would make a lot of sense
since the atomic crew are all about keeping the system swappable
& thus the user data separate
& conveniently on fedora atomic the cryptographic keys go into the var folder
well they always go in var
but on fedora atomic var is specifically independent
Welll
Rip
Failed to write boot loader again
oh
logs are on another tty
Not even using laptop generic iso work lol
look at what the logs say
Something of a pcie error is spawning constantly
yeah the actual error probably passed by
though there are a few mor ttys
with stuff
there's also tmux
that has a few windows open
including logs
i think you can scroll in tmux
I pressed "No" and im looking from the installer logs
I see a LOT of $d errors
It tries something with some systemd configs and it says "Unknown modifiers d$"
there should be a very clear error about bootloader installation in there
OH
efibootmgr cannot remove boot entries
That is why
It tries to remove all leftovers entries
Gets an error and drops an "Could not delete variable. Invalid Argument"
And the installer shits itself
wel that's a pretty clear error
If you ask, I have secure boot disable
Its weird that efibootmgr cannot remove entries
not sure if you could work around it though
After that, it gives an internal error and "tries" to continue the installer (failing and just breaking itself more and more)
the firmware would need to cooperate there though
some don't
Im using an Asus Vivobook
on any other distro you could work around this in various ways
but fedora's installer sucks very much
at least the old Anaconda
Im going to check bios tho
or maybe if you're advanturous enough trying to update UEFI
maybe there's something in there
Im going to do that lol
It has a 2023 version
Yay the laptop didn't kaboom
Is still on the process tho
Now it finished
Lets go
that's not too old i'd expect them to fix basic issues
UEFI has been around for a while now
FINALLY
it installed perfectly
old bios had the nvram corrupted
oh
Solution
so yea, the solution if anyone has it (on laptop) is updating the bios to a modern version (or reinstalling it if possible)
resetting the nvram too
was just corrupted
yea
probably an old bug
there's usually a way to clear NVRAM if corruption is the issue
now
time too see if boots
yea it booted
nice
Steam Deck has a button combo to clear NVRAM
so did intel Macs
but updating was probably a good idea anyways
Ok now i have a weird thing
I log in, but the gnome screen is gray
Pressing the shutdown button worked tho
Well now i have weird issues
If i let the pc boot normally and let the plymouth screen (no pressing esc)
Everything freezes, and the caps lock key starts beeping
If i press ESC that doesn't happen (kernel panic?)
strange
try going back to the ASUS image
I cant lol
now that it can actually install properly
Everything freezes
Oh
Now after pressing esc
It happened
I think is a kernel panic
you can disable the splash screem alltogether i guess
yeah this doesn't look like a panic
but does look bad
It doesn't boot
It stuck there
caps lock led flashing
hmm how far can it boot i wonder
what of you make it stop at milti-user.target
It stops at "load/save os random seed"
After getting a fuck ton of ACPI Bios errors
yeah that seems like the firmware still being bugged
but nothing jumps out as that severe
Yep, rebooted it
Its ACPI error
Its a kernel panic
I will use now the generic iso
I think simply Bazzite doesn't work on Vivobooks
Used the generic one and still the same thing
Well, i think is something that should get fixed, rip but i tried
Will see with another distro now
Ty for the help tho