Grub update in the testing repo

:sweat_smile:

:yawning_face:
It will probably be another boring update.

2 Likes

Iā€™m sure there will be issues because users donā€™t pay any attention to the output in pacman when updating.

After the grub package is upgraded the new grub package has to be installed and the grub update command run.

sudo grub-install
sudo grub-mkconfig -o /boot/grub/grub.cfg

Edit: I updated it already from the testing repo and ran the commands. No issues!

[ricklinux@rick-ms7c37 ~]$ pacman -Qi grub
Name            : grub
Version         : 2:2.12rc1-2
Description     : GNU GRand Unified Bootloader (2)
Architecture    : x86_64
URL             : https://www.gnu.org/software/grub/
Licenses        : GPL3
Groups          : None
Provides        : grub-common  grub-bios  grub-emu  grub-efi-x86_64
Depends On      : sh  xz  gettext  device-mapper
Optional Deps   : freetype2: For grub-mkfont usage [installed]
                  fuse3: For grub-mount usage [installed]
                  dosfstools: For grub-mkrescue FAT FS and EFI support [installed]
                  lzop: For grub-mkrescue LZO support
                  efibootmgr: For grub-install EFI support [installed]
                  libisoburn: Provides xorriso for generating grub rescue iso using grub-mkrescue
                  os-prober: To detect other OSes when generating grub.cfg in BIOS systems [installed]
                  mtools: For grub-mkrescue FAT FS support [installed]
Required By     : None
Optional For    : None
Conflicts With  : grub-common  grub-bios  grub-emu  grub-efi-x86_64  grub-legacy
Replaces        : grub-common  grub-bios  grub-emu  grub-efi-x86_64
Installed Size  : 33.42 MiB
Packager        : Tobias Powalowski <tpowa@archlinux.org>
Build Date      : Tue 03 Oct 2023 04:08:12 PM
Install Date    : Tue 03 Oct 2023 11:34:15 PM
Install Reason  : Explicitly installed
Install Script  : Yes
Validated By    : Signature
5 Likes

One thing Iā€™ve made a habit of doing when I update or even install something is to read the output and see if anything extra needs to be done or if there are any optional dependencies Iā€™ve forgotten about that I may need.

1 Like

of course I donā€™t pay attentionā€¦ canā€™t we hook this into pacman somehow? if itā€™s needed anyway?

You should always pay attention. Itā€™s your computer to manage.

1 Like

The update is useless if you donā€™t install it afterwords and run the grub update command to create the configuration. Otherwise you are still using the same grub version that it was prior to the downloaded updated package.

1 Like

then why does it break after update without these commands, if the same version remains installed?

isnā€™t the point of a computer to automatize operations, especially necessary and repeating stuff?

Sorry Iā€™m just really confused by this whole grub thing. All I know I had a few problems before, I was not paying attention and did an update and it broke the grub. I had to run these commands from a live environment. It happened a few times. Obviously this is an issue, because there were multiple threads about this update problem. Iā€™m just asking if thereā€™s a solution that runs these commands automatically, sometimes I just donā€™t pay enough attention to stuff and Iā€™m not alone.

Generally not Endeavour/Arch based stuff, no.

Itā€™s your computer to do as you want, and to know. Thatā€™s why you have this:

https://wiki.archlinux.org/title/Installation_guide

If you want a computer to automate, and do everything for you completely, simply and without needing to bother you. Check out PopOS, Ubuntu, Zorin, and very notably Windows and MacOS.

1 Like

Well I guess I should be thankful that I donā€™t have to run mkinitcpio manually tooā€¦
I guess thereā€™s no explanation for why canā€™t these grub commands be hooked into pacman.

In case thereā€™s a manual intervention required. But, I suppose you can make a hook if you wanted to.

Also, we use dracut now not mkinicpio, so unless you have an older install, itā€™s likely not likely to work.

How do I know when itā€™s required? From what I read it should be run after every grub update to make sure it wonā€™t fail to boot. If itā€™s advised, why canā€™t it just be automatic after every new grub version?

https://aur.archlinux.org/packages/grub-hook

So I found this, sounds better than reading update outputs. I survived two years without reading outputs, if we donā€™t count the grub issues.

edit: the above link is for kernel updates, so not good
I found this, looks like what I need Grub Hook to grub-install and grub-mkconfig?

Someone said you can even uninstall the package, and stay with the installed version. I did something similar, I just put it in ignorePkg a few months ago.

Cool. It looks like youā€™ve found your fix then!

Looks like they put out another new version of grub.

==> yay
[sudo] password for ricklinux: 
:: Synchronizing package databases...
 endeavouros                            26.7 KiB   215 KiB/s 00:00 [------------------------------------] 100%
 core                                  127.2 KiB   719 KiB/s 00:00 [------------------------------------] 100%
 extra                                   8.2 MiB  23.7 MiB/s 00:00 [------------------------------------] 100%
 multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
:: 4 packages to upgrade/install.
4  endeavouros/eos-update-notifier  23-14       -> 23-15
3  core/grub                        2:2.12rc1-2 -> 2:2.12rc1-3
2  core/hwdata                      0.374-1     -> 0.375-1
1  core/openssh                     9.4p1-4     -> 9.5p1-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems
==> 
1 Like

I am really glad my thread could be of value.
But it wouldnā€™t have been without the support I got here from our friends.
To be honest, I didnā€™t even know the word ā€œhookā€ other than that related to fishing! But I learened it here.

2 Likes

I do care whatā€™s being installed, especially being extra careful with a GRUB issue.
I saw that it created some new configurations & a file, so, with an live iso handy & ready for a chroot, I just rebooted immediately after updating. Hopefully, GRUB appeared with all its previous glory.
*** Talking about a non UEFI oldidh DELL Latitude laptop

Exactly why I love this forum, Iā€™ve learnt more from here than most other sources I used to go to

1 Like