Updated Grub Package

General system Kernel, boot, graphics & hardware
21

Is this disaster with grub the only reason why the EOS developers turned to systemd-boot?

1 Like
22

No

23

and …?

24

Some of the advantages of systemd-boot have been mentioned in this article if you would like to learn more about it:

https://discovery.endeavouros.com/installation/systemd-boot/

2 Likes
25

One thing i find with systemd-boot is the resolution isn’t as easy to set as it is in grub when it’s booting before the desktop.

Edit: I find it easier to set in grub and it works the way i want to see it. :man_shrugging:

Not saying I don’t like systemd-boot. Just don’t have much experience with it.

2 Likes
26

In loader.conf you can specify a console-mode line, which can be set to any of these values:

0
Standard UEFI 80x25 mode

1
80x50 mode, not supported by all devices

2
the first non-standard mode provided by the device firmware, if any

auto
Pick a suitable mode automatically using heuristics

max
Pick the highest-numbered available mode

keep
Keep the mode selected by firmware

I believe keep is the default, but if that looks a bit low-res you could try setting it to max like so:

...
console-mode max
...
27

Yes i know you can do this but it doesn’t match what you can set using grub. I use 1920x1080 which is the same resolution as my monitor on grub.

Edit: At least i don’t know how to get it to set 1920x1080

28

That works, thanks @BluishHumility. I would use systemd-boot, but I like the access to snapper snapshots and as far as I know there is still no way to do it with systemd-boot. I do know systemd-boot does make multi-distro installs a lot easier and less of a headache. I can now use my portable usb-arch install and it wont mess up my laptop which uses systemd.

29

grub-install --no-nvram as mentioned by @dalto might cover most cases.

But there may be other cases where additional parameters would be needed.

One that comes to my mind, if I am not mistaken, is when the user have ESP mounted at /efi or /boot and not at /boot/efi which I believe to be the default path for grub-install. In those cases--efi-directory= will be needed. Ex: efi-directory=/efi

Also, some implementations of UEFI:s won’t read the default path to the bootloader file grubx86.efi and use the fallback path to /esp/EFI/BOOT/BOOTX86.efi (esp being ESP’s mount point). In this case --removable needs to be passed to grub-install.

There might be other cases as well I am not aware of.

If I am mistaken on any part of the above, I would appreciate correction from you @all.

2 Likes
30

I’m one of the cases where it doesn’t work grub-install --no-vram

[ehudd@endeavour ~]$ LANG=C grub-install --no-nvram
Installing for x86_64-efi platform.
grub-install: warning: disk does not exist, so falling back to partition device /dev/sdb1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/sdb1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/sdb1.
grub-install: error: disk `hostdisk//dev/sdb1' not found.
31

Since this was not meant to be a help but sort of a #important-notifications thread (and marked as solved on top of that :thinking:), I would suggest you to open a new thread for your grub-install issue to get adequate assistance.

32

Tip : You can look back at the installation commands :

sudo cat /var/log/endeavour-install.log | grep grub
33

The other issue is i wonder if some users are installed with Bios. What does the command do in that case if using --no-vram? Does it just ignore that anyway?

34

If you are installed with BIOS you shouldn’t use the command identified as “for UEFI” :wink:

1 Like
35

I understand that. I just wondered if users reading here understand that and if they used the command on a Bios install what happens?

Edit: Does the command grub-install work on Bios also?

36

Oh! Sorry. I’ll do that.

1 Like
37

No idea. It will either return an error or succeed. However, it shouldn’t hurt anything.

Yes but I am haven’t tested what specific flags you need to update an existing grub install.

1 Like
38

Wasn’t it only the UEFI systems hit by the Grub issue back then when it started?

So, is it then recommended for Legacy systems to do a grub-install when Grub package is updated?

39

Yes, but that was because that specific change was related to UEFI

I would think so. If you don’t run grub-install, you are only getting part of the update. The core image won’t be updated. Relatively speaking, the risk is probably lower than with UEFI but I would still consider doing it.

1 Like
40

For Bios/Legacy installations:
The target= part can be skipped, so it is just sudo grub-install /<drivename> evermore, as it seems to me, who is on “Legacy/Bios-” installations all the time. :wink:

It is not only my machines getting old, but me too. :v:

1 Like