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
Here it is without kernel parameters (click):
[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
ALL_config="/etc/mkinitcpio.conf"
#ALL_kver="/boot/e27534f9c24b4615a2f8f13f8f11954f/5.17.1-3-MANJARO/linux"
ALL_kver="/boot/vmlinuz-5.17-x86_64"
PRESETS=(default fallback)
#default_image="/boot/e27534f9c24b4615a2f8f13f8f11954f/5.17.1-3-MANJARO/initrd"
default_image="/boot/initramfs-5.17-x86_64.img"
#fallback_image="/boot/e27534f9c24b4615a2f8f13f8f11954f/5.17.1-3-MANJARO/initrd-fallback"
fallback_image="/boot/initramfs-5.17-x86_64-fallback.img"
fallback_options="-S autodetect"
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.
4月 16 09:48:19 Sulaco gnome-shell[1192]: DING: @/home/rico/.local/share/gnome-shell/extensions/ding@rastersoft.com/ding.js:176:9
4月 16 09:48:19 Sulaco gnome-shell[1192]: DING: _emitChangedSignal/this._signalTimerID<@/home/rico/.local/share/gnome-shell/extensions/ding@rastersoft.com/dbusUtils.js:273>
4月 16 09:48:19 Sulaco gnome-shell[1192]: DING: _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
4月 16 09:48:19 Sulaco gnome-shell[1192]: DING: ProxyManager/<@/home/rico/.local/share/gnome-shell/extensions/ding@rastersoft.com/dbusUtils.js:85:26
4月 16 09:48:19 Sulaco gnome-shell[1192]: DING: makeNewProxy@/home/rico/.local/share/gnome-shell/extensions/ding@rastersoft.com/dbusUtils.js:127:85
4月 16 09:48:19 Sulaco gnome-shell[1192]: DING: _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17
4月 16 09:48:19 Sulaco gnome-shell[1192]: DING: _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25
4月 16 09:48:19 Sulaco gnome-shell[1192]: DING: Error creating proxy, "Nautilus-Sushi" is needed for Desktop Icons: Error calling StartServiceByName for org.gnome.Nautilus>
4月 16 09:48:19 Sulaco dbus-daemon[1161]: [session uid=1000 pid=1161] Activated service 'org.gnome.NautilusPreviewer' failed: Process org.gnome.NautilusPreviewer exited wi>
4月 16 09:48:19 Sulaco org.gnome.Nauti[48587]: Script /usr/lib/org.gnome.NautilusPreviewer threw an exception
4月 16 09:48:19 Sulaco org.gnome.Nauti[48587]: JS ERROR: SyntaxError: expected property name, got '{' @ resource:///org/gnome/NautilusPreviewer/js/viewers/html.js:63
4月 16 09:48:19 Sulaco dbus-daemon[1161]: [session uid=1000 pid=1161] Activating service name='org.gnome.NautilusPreviewer' requested by ':1.93' (uid=1000 pid=1770 comm="g>
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:
Assertion ((src_linesize) >= 0 ? (src_linesize) : (-(src_linesize))) >= bytewidth failed at libavutil/imgutils.c:350
Abandon (core dumped)
Never had this before, and I if revert my system with a Timeshift snapshot, it’s working again.
Anyone has an idea how to solve this?
I have a python error with two apps, Quod Libet and Rapid Photo Downloader, that prevents them starting.
Both apps are installed from ‘Official Repositories’ according to Pamac.
Error is:
ERROR:../pygobject/gi/gimodule.c:1826:_wrap_pyg_hook_up_vfunc_implementation: assertion failed: (G_TYPE_IS_CLASSED (implementor_gtype))
Bail out! ERROR:../pygobject/gi/gimodule.c:1826:_wrap_pyg_hook_up_vfunc_implementation: assertion failed: (G_TYPE_IS_CLASSED (implementor_gtype))
Core dump from Quod Libet is in this bug report.
Been through the Python rebuild instructions…doesn’t seem to be an issue there.
python-gobject is at 3.42.0-3
Nice I don’t need setting up anything on my UEFI. Prime X570-Pro has CPPC set to auto.
But I wait until next LTS Kernel then some features are stable enough.
2 Likes
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
I am running kernel 5.17.1-3-MANJARO
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.
Thanks for your help!
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.
sudo pacman -U https://archive.archlinux.org/packages/s/sushi/sushi-41.2-1-x86_64.pkg.tar.zst
2 Likes
This option does not exist anymore. I think it in some earlier version while the driver was still in development.
This one does the trick for Zen2 based CPU’s.
Zen3 should not need this.
2 Likes
I seem to have a similar issue. In my case the system logs get filled with messages about CTRL-EVENT-BEACON-LOSS when the connection starts to break down, like this:
Apr 16 17:42:25 computer wpa_supplicant[547]: wlp6s0: CTRL-EVENT-BEACON-LOSS
Apr 16 17:42:26 computer wpa_supplicant[547]: wlp6s0: CTRL-EVENT-BEACON-LOSS
Apr 16 17:42:27 computer wpa_supplicant[547]: wlp6s0: CTRL-EVENT-BEACON-LOSS
Apr 16 17:42:28 computer wpa_supplicant[547]: wlp6s0: CTRL-EVENT-BEACON-LOSS
No network traffic while these messages are appearing. Sometimes it would recover from it on its own, I have no idea how or why, but other times it would be stuck repeating this non-stop until I reconnected it using the applet.
This happened on kernel 5.16.18-1, now I randomly booted an older kernel that happened to be 5.10.109-1 and it does not seem to have the issue.
TV (tested DBV-C + Kaffeine) with Si2168 (like in USB stick Hauppauge WinTV SoloHD) doesn’t work with kernel V5.17.3.
Kernel V5.16 no problem
si2157 7-0060: Can’t continue without a firmware.
Looks like an known regression:
https://bbs.archlinux.org/viewtopic.php?id=275502
Hello,
Thank you for the update. The update ran all fine only after my first reboot, the primary and secondary monitor had the wrong resolution. Did a second reboot and the monitors are fine.
The only real issue is that there is no Wifi available anymore because it says that it is hard blocked.
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
From inxi -nz
Network:
Device-1: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS ]
driver: ath11k_pci
IF: wlp4s0 state: down mac: <filter>
What I tried is to do an rfkill unblock all but this has no effect. Then I rebooted to check my BIOS but WiFi is enabled there. This is a Dell XPS 9700 and it has no physical kill switch.
So I went back to the 5.16 kernel and Wifi works just fine there, so I believe it is something in the 5.17 kernel.
Running this 5.17 kernel:
Linux 5.17.1-3-MANJARO x86_64
From the kernel log when I filter on ath11 all I get is this:
16-04-2022 18:32 ath11k_pci 0000 4:00.0: BAR 0: assigned [mem 0xd2100000-0xd21fffff 64bit]
16-04-2022 18:32 ath11k_pci 0000 4:00.0: enabling device (0000 -> 0002)
16-04-2022 18:32 ath11k_pci 0000 4:00.0: MSI vectors: 32
16-04-2022 18:32 ath11k_pci 0000 4:00.0: qca6390 hw2.0
16-04-2022 18:32 ath11k_pci 0000 4:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0xffffffff
16-04-2022 18:32 ath11k_pci 0000 4:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id
16-04-2022 18:32 ath11k_pci 0000 4:00.0 wlp4s0: renamed from wlan0
For now I will use the 5.16 kernel when I need Wifi.
Excellent, thank you! Sushi works & DING errors stopped.
I could not manage without these two. 