I have two questions prior to executing this stable upgrade.
I’m an AMD user (CPU, GPU) and currently only linux-firmware-amdgpu 20260810-2 is installed. I’ve also removed the linux-firmware metapackage in the past. This means, I’m affected by the mentioned firmware changes in the ‘Known Issues’ section. The section doesn’t explicitly mention though when to install the other file (I guess linux-firmware-amd in my case). Do I get that right when I assume it’s meant to be installed right after the upgrade with sudo pacman -S linux-firmware-amd but before the reboot?
The second question is about the GRUB pacnew. My current situation is as follows:
install-grub and update-grub have been installed in the past.
My current GRUB_CMDLINE_LINUX_DEFAULT looks like this:
I have removed Plymouth in the past because I prefer to look at the boot messages during startup. Therefore I removed the ‘quiet’ parameter from GRUB and the ‘plymouth’ hook. I get that I can upgrade GRUB after rebooting but I’m not sure which parts to keep.
Since I’m using ‘systemd’ in the HOOKS, I’m pretty sure I have to replace udev.log_priority=3 with loglevel=3 rd.udev.log_level=3 as it has been suggested by @Marsa in post #42.
But what about the other kernel boot parameters? Do I have to remove any of them for the new GRUB to work or should they stay?
Do I get it right that install-grub won’t solve the .pacnew issue during the update but it requires manual intervention after the reboot with sudo update-grub after changing /etc/default/grub?
I’m asking to be on the safe side because I have a slight (admitted) paranoia about ending up with an unbootable system.
Just installing it is probably not enough. You’ll need to rebuild your initramfs and then update your boot loader again.
So before rebooting, you need to execute these two commands…
sudo mkinitcpio -P
sudo update-grub
That is correct.
They can stay.
You have to understand that all install-grub does is make sure that /boot/efi/EFI/boot/bootx64.efi and /boot/efi/EFI/manjaro/grubx64.efi are identical by copying the latter over the former.
This has nothing to do with update-grub, which is a script that in turn executes the following command…
grub-mkconfig -o /boot/grub/grub.cfg
The latter is where the configuration from your /etc/default/grub and the scripts in /etc/grub.d/ is being applied.
Just sharing a fix in case someone hits the same conflict.
Following the Known issues note, I ran pacman -S linux-firmware-amd and pacman refused with a conflict involving the old linux-firmware-meta I still had installed (sorry, I no longer have the exact message). Replacing it fixed it:
sudo pacman -Syu linux-firmware
I answered y when pacman asked to remove linux-firmware-meta; linux-firmware-amd, -amdgpu and -ti came in as dependencies. The meta package was already orphaned on my system (installed as a dependency, required by nothing).
The ‘Known issues’ section doesn’t mention that rebuilding the initramsfs is necessary. So thanks for the tip and deepening the understanding of install-grub and upgrade-grub.
Since I’m rebuilding the GRUB configuration after rebuilding the initramfs, I was asking myself if it would make sense to make the discussed .pacnew GRUB changes before that step to ‘kill two birds with one stone’ so to speak.
sudo pacman -Syu for the stable upgrade
pacman -S linux-firmware-amd
sudo mkinitcpio -P
Make the changes to /etc/default/grub/
sudo update-grub
sudo reboot now
Is there anything wrong with that or should GRUB only be modified after the reboot?
Normally a package is installed by only using sudo pacman -S <package> but, package(s) can also be installed while actually performing an update/sync sudo pacman -Syu <package>.
Make changes to /etc/default/grub
sudo mkinitcpio -P
sudo update-grub
sudo reboot now
Today i experience that Veracrypt tray menue refused to show up but instead has a strange request after this stable update, always when i right click on the tray icon this shows up:
xembedsniproxy is a component being provided by plasma-workspace. Veracrypt use an outdated protocol called XEmbed to embed their icons directly into the system tray panel. So, it should be totally safe to allow it.
If you install the flatpak-kcm package, you will then have a new Application Permissions section in Plasma’s System Settings where you can set and change the permissions for X11 applications. That should allow you to revoke previously allowed permissions (although I haven’t tested it myself).
flatpak-kcm is in the plasma group and part of the plasma-meta package. I was just looking at the KDE Plasma ISO profile to see what needed to be added / removed, in fact. I can include in the next ISO.
EDIT: I’ll also add flatseal for managing Flatpak permissions to the GNOME ISO.
Is it considered safe to keep rolling with non LTS kernels with stable repos? Isn’t now the latest kernel 7.2 basically EOL, but it’s the highest that is available on stable repos?
How would i go on switching to testing repos perhaps, because it’s rumored that the LTS will be 7.3 and i basically need the 7.4 on my system to get VRR?
Yes, 7.2 is EOL, but so far only in the Unstable branch. The reason why it’s still the newest non-LTS kernel in the Stable branch is that it had been since early September that there had been a Stable Update — in the announcement of which Philip stated that he was temporarily freezing Manjaro — and even the Testing branch was already getting a bit stale.
As such, the Team has taken matters into our own hands and pushed out a Stable Update and a Testing Update in short succession.