The updated ucode requires a new AGESA version, hence, a BIOS update is required.
You can always blacklist the amd-ucode package.
Future amd-code updates will require the newer BIOS too.
EDIT: That is a common issue and it does not depend on Manjaro. It was reported on gentoo forums for the firs time and it affects all linux versions which include the updated microcode.
It’s up to you to keep your hardware firmware up to date.
error: no se pudo realizar la operación (archivos en conflicto)
konsole: /etc/xdg/konsolerc existe en el sistema de archivos
Ocurrieron errores, por lo que no se actualizarán los paquetes
zfs completly broken under kernel linux61, linux515 and linux510.
I managed to regain disk acces via a usb boot key and chroot into the installation. It seems mkinitcpio is in trouble too. All initramfs builds fail with ERROR: Hook ‘zfs’ cannot be found".
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'default'
-> -k /boot/vmlinuz-6.1-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.1-x86_64.img --microcode /boot/amd-ucode.img --microcode /boot/intel-ucode.img
==> Starting build: '6.1.25-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
==> ERROR: Hook 'zfs' cannot be found
==> ERROR: Hook 'zfsencryptssh' cannot be found
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.1-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'fallback'
The worst offender of this is Lutris (even with Kvantum Manager) no longer accepting the Materia theme and just flash banging you with a white default, except it being set to dark everywhere else.
This is on KDE Manjaro 6.2 with latest nvidia drivers on X11.
Seems we have to recheck Qt5 updates and ZFS support on this one …
I had created some new install medias, which can be tested. If the Plasma Edition is broken due to a missing qt5 rebuild we might get to know why faster …
Thanks philm, that was a quick one. For the time being i downgraded to 2.1.10 and could boot my 5.15 kernel. By now the mirrors don’t offer the 2.11-1.1 to me. A little more patience to be happy again.
Some mirrors were out-of-sync, despite the update being released yesterday already. So just rebuilt my mirror pool , and then it went well and good.
Used Mumuh to update and that’s how I found out I have out-of-sync mirrors. So, it seems it works well! I’ll just leave this here for whatever the reason might be:
Small non-blocking issue : I use Xfce with a dark theme, when I launch Calibre (Qt app) the dark theme is not applied at first launch. I must quit and restart to have dark theme.
Also when opening a window on Calibre (e.g : parameters), some part on GUI receive suddendly light theme (like line/column headers in books list) which is inconsistent.
The issue is non-blocking tough, since I just relaunch Calibre to apply dark themes.
I tried to set up a hotspot with WPA3 Personal on an Intel Laptop (WI-FI 6 AX200 Intel) using the KDE network manager.
It works, but the hotspot has no encryption at all. Changing that to WPA3 Pers in KDE’s network connection setup it refused to start the hotspot (it gave up after 20 sec).
In dmesg I have following entry:
“…wlan0: deauthenticating from 48:c0:93:82:8a:63 by local choice (Reason: 3=DEAUTH_LEAVING)”
Is that a configuration issue on my side or does someone has an other idea (I checked on Google, not finding a good advice).
After update, when I lock the screen on KDE Plasma (X11), I get this message:
The screen locker is broken and unlocking is not possible anymore. In order to unlock it, switch to a virtual terminal (e.g. Ctrl+Alt+F2), log in to your account and execute the command:
loginctl unlock-session 2
Then log out of the virtual session by pressing Ctrl+D, and switch
back to the running session (Ctrl+Alt+F1). Should you have forgotten the instructions, you can get back to this screen by pressing CTRL+ALT+F2