erubio0
(Emilio Rubio)
February 16, 2020, 6:18pm
22
Unfortunately, this bug is still alive. Here’s the workaround update for Silverblue 31:
chroot /mnt/sysimage/ostree/deploy/fedora/deploy/<deploy_id>.0 /bin/sh
mv /boot/efi/EFI/EFI/BOOT/* /boot/efi/EFI/BOOT/
mv /boot/efi/EFI/EFI/fedora /boot/efi/EFI/
rm -r /boot/efi/EFI/EFI
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
3 Likes
bam
(Andrey)
February 19, 2020, 11:48pm
23
This is a real pain. I’m not even able to do the workaround since my keyboard is bluetooth one and we have no bluetooth here in Anaconda!
So let’s please file this bug in the end if it wasn’t already. Anyone aware of the situation?
PS: also, the installer seem doesn’t allow to continue the installation, so not sure if workaround is enough…
1 Like
bam
(Andrey)
February 20, 2020, 12:34pm
24
Apparently, there are a lot of this bug reports already, starting from 2017, but the bug is still there:
https://bugzilla.redhat.com/show_bug.cgi?id=1483818
https://bugzilla.redhat.com/show_bug.cgi?id=1575957
1 Like
bam
(Andrey)
February 21, 2020, 2:25pm
25
Ok I found the issue and provided the fix:
https://github.com/rhinstaller/anaconda/pull/2329
Not sure why is should had to take 3 years if one is really care…
1 Like
msmafra
(Marcelo Dos Santos Mafra)
February 21, 2020, 6:54pm
26
Wow! Just that to solve an x-years problem?!
bam
(Andrey)
February 21, 2020, 6:57pm
27
Silly, yeah? Actually, I’m just going to test it
1 Like
msmafra
(Marcelo Dos Santos Mafra)
February 22, 2020, 1:02pm
28
Hello!
Did you test it with Fedora Silver Blue 31? Did you test dual boot with Windows?
bam
(Andrey)
February 22, 2020, 1:07pm
29
Hi, I’m testing right now. Still see the problem with the grub
error, but maybe it’s because I’m trying to reinstall Fedora to itself. Will see.
Anyway, the patch above is for sure necessary. Maybe it just not enough
1 Like
msmafra
(Marcelo Dos Santos Mafra)
February 22, 2020, 1:56pm
30
How are you testing it? Is it just changing an installation script?
Maybe I can test on my secondary machine.
bam
(Andrey)
February 22, 2020, 1:59pm
31
I’m testing on Virtualbox. Yes the file being patched is writable so anyone can try too.
But patch
util is absent
1 Like
bam
(Andrey)
February 22, 2020, 2:07pm
32
The grub error seems occurs only when grub.cfg was present somewhere in /EFI/… on ESP before. If it’s not the case - install should finish flawlessly with the patched script (and hopefully boot).
1 Like
msmafra
(Marcelo Dos Santos Mafra)
February 23, 2020, 3:45pm
33
Would it work with Systemd-Boot?
bam
(Andrey)
February 23, 2020, 7:45pm
34
I hope so. But grub supports BLS also, so not a real problem
1 Like
yajo
(Jairo Llopis)
February 27, 2020, 9:29am
35
Nope, I just installed normal Fedora. Too many problems with silverblue…
1 Like
jakfrost
(Stephen Snow)
February 27, 2020, 1:08pm
36
Bummer,
It is sort of the issue when using something new, not everything has come together for every use case equally. On the upside, you’re still a Fedora user!
1 Like
yajo
(Jairo Llopis)
March 2, 2020, 8:12am
37
Yes, I love fedora since years, and I love the Silverblue concept, but you know, it’s a workstation and I need things working…
I guess I’ll try again after one or 2 versions if it’s more stable.
1 Like
bam
(Andrey)
April 8, 2020, 1:12pm
38
Some updates.
Systemd-Boot works but you’ll have to tune it’s .conf files manually after every rpm-ostree upgrade. This is due OSTree doesn’t support Systemd-Boot yet, unfortunately.
So for now I came up with default Grub BLS solution, which works rather good also.
1 Like