So small issue in intel-graphics-compiler 1:1.0.10778-1 (or possibly intel-opencl-clang). Running an OpenCl Geekbench benchmark, for example, leads to an error for (only) the SFFT part of the benchmark. Below is the error message:
Same error is not present when using the AUR version of intel-graphics-compiler-bin 1:1.0.10840-1. The issue could also be with intel-opencl-clang since the AUR version also provides that.
I know Geekbench isn’t a true workload. I am just using it in this instance to see if everything runs.
I can report that I didn’t change UEFI nor add boot params, yet my system reports the amd-pstate driver successfully. Running kernel 5.17.1-3 on an AMD Ryzen 9.
i wouldnt reboot, it will probably break your system… try canceling/ killing the update, then logout, enter into TTY: Ctrl+Alt+F2 and run update again with: pamac update
[omano@omano-nvme ~]$ sudo cpupower frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 2.20 GHz - 4.21 GHz
available frequency steps: 3.60 GHz, 2.80 GHz, 2.20 GHz
available cpufreq governors: conservative ondemand userspace powersave performance schedutil
current policy: frequency should be within 2.20 GHz and 3.60 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: 3.60 GHz (asserted by call to hardware)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 2800MHz
Pstate-P2: 2200MHz
[omano@omano-nvme ~]$ sudo dmesg|grep -i pstate
[ 2.787330] amd_pstate: This processor supports shared memory solution, you can enable it with amd_pstate.shared_mem=1
Here it is with the kernel parameters (click):
[omano@omano-nvme ~]$ sudo cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 550 MHz - 4.21 GHz
available cpufreq governors: conservative ondemand userspace powersave performance schedutil
current policy: frequency should be within 550 MHz and 4.21 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.34 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3600MHz
Pstate-P1: 2800MHz
Pstate-P2: 2200MHz
[omano@omano-nvme ~]$ sudo dmesg|grep -i pstate
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.17-x86_64 root=UUID=6a81f472-9ea9-40f8-85f6-7925c4bbe742 ro quiet splash zswap_enabled=1 ipv6.disable=1 apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1 amd_pstate.enable=1 amd_pstate.shared_mem=1 nowatchdog delayacct
[ 0.030287] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.17-x86_64 root=UUID=6a81f472-9ea9-40f8-85f6-7925c4bbe742 ro quiet splash zswap_enabled=1 ipv6.disable=1 apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1 amd_pstate.enable=1 amd_pstate.shared_mem=1 nowatchdog delayacct
so it is definitely not automatic. Maybe in your specific case it is because it is a zen3 CPU and I have zen2, but if I recall correctly, it is not enabled by default until they sort the last quirks/bugs.
I had to manually edit the mkinitcpio preset in linux-517 for some reason. Is it because I use systemd-boot? Commented lines are the original ones with a weird path under boot, and right after them the fixes I had to make for initrd generation to work for 5.17-1
This update fixed my pipewire & bluetooth problems of stuttering, sudden disconnection etc.
I tried linux517, but it spammed my journal with “…unexpected event 0xff length…” warnings, so i turned back to 5.16.
Everything is ok here, thank you <3
This is also seems to have a knock-on effect with the extension Desktop Icons DING. ““Nautilus-Sushi” is needed for Desktop Icons”
error spam every second.
I’m using Shotcut video editor and since this update, some of the MP3 I was successfully using with it before for soundtrack are now crashing the program when I want to import them. Here is the error message:
There were no errors in the upgrade process, but after the upgrade, bluetooth rendered unusable. There are no devices visible and the settings panel advises me to switch on bluetooth. But it is already switched on. Ticking the button in the upper right does nothing.
systemctl claims that bluetooth is running fine (systemctl status bluetooth.service):
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2022-04-16 16:28:14 CEST; 25min ago
Docs: man:bluetoothd(8)
Main PID: 4099 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 77047)
Memory: 868.0K
CPU: 28ms
CGroup: /system.slice/bluetooth.service
└─4099 /usr/lib/bluetooth/bluetoothd
Apr 16 16:28:14 PC systemd[1]: Starting Bluetooth service...
Apr 16 16:28:14 PC bluetoothd[4099]: Bluetooth daemon 5.64
Apr 16 16:28:14 PC systemd[1]: Started Bluetooth service.
Apr 16 16:28:14 PC bluetoothd[4099]: Starting SDP server
Apr 16 16:28:14 PC bluetoothd[4099]: Bluetooth management interface 1.21 initialized
Ever since the update, my internet connection periodically stops working with the error “Temporary failure in name resolution”. I am connected over wifi and using kernel 5.15.32-1 LTS. Disabling and reenabling wifi temporarily resolves the issue.
As far as I know there’s no pattern to when it starts, websites just start loading very slowly and then stop altogether.
My connections are managed with the NetworkManager Applet.
after an update my wireplumber can’t start with Failed to open module /usr/lib/wireplumber-0.4/libwireplumber-module-device-activation: /usr/lib/wireplumber-0.4/libwireplumber-module-device-activation.so: No such file or directory
The update notes say mesa is updated to 21.3.8. Looking at the pending updates on my system, mesa packages do show new version as 21.3.8, except for the lib32-mesa package which shows it will update to 22.0.0. Usually all the mesa packages have a synchronised version number. OK to go ahead with update, or will this possibly cause trouble with Steam games?
Sadly it appears a simple downgrading of sushi and/or gjs won’t solve our problems. sushi still has the same issue in the 3.38 branch, and downgrading gjs might be a bit messy due to other things that depend on it. gjs 1.72.0 is currently in the unstable branch as well as sushi 41.2 which has the issue fixed.
That error spam is a bit excessive. Disabling the Desktop Icons extension might be the way to go for the time being to avoid that mess.
I’m all ears for other solutions. Funny how you don’t realize how important the simple things are in your daily flow until they muck up.
I've decided to go ahead and upgrade sushi to 41.2 and so far so good.
