[Stable Update] 2022-04-15 - Kernels, Mesa, Nvidia, Budgie, PipeWire, LIbreOffice, KDE Frameworks, Wine

manjaro-mate-settings package is broken since a long time ago.

  1. Remove it without removing its dependencies.

  2. Remove its dependencies you have installed from AUR.

  3. Mark the rest of its dependencies as explicitly installed.

  4. Install mate-tweak package as usual.

1 Like

All went fine except for the fact that I faced an issue with the utility “solaar” (to set logitech hardware):

After the new update, I’m running into the following error message with ParaView:

/opt/paraview/bin/paraview: symbol lookup error: /opt/paraview/lib/libvtkfides.so.1: undefined symbol: _ZN6adios25ADIOS9DeclareIOENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE

I attempted to remove and reinstall (yay -R paraview && yay -S paraview), but the error still occurs. Note that even though I’m using yay above, paraview is not an AUR package.

This is with the i3 version of Manjaro (though I’ve installed qtile as my WM).

Is the AMD p-state driver enabled in this release (for 5.17) or is there additional configuration required to enable? Are there recommendations not to enable this yet?

I have this in my 5.17.1 booted kernel:

[strit@odin ~]$ zgrep PSTATE /proc/config.gz 
CONFIG_X86_INTEL_PSTATE=y
CONFIG_X86_AMD_PSTATE=y

So I guess, yes, it’s enabled.

2 Likes

It is enabled, but I’m pretty confident that for now, you need to add kernel parameters and configure your UEFI for it to replace acpi-cpufreq.

Kernel parameters to add: amd_pstate.enable=1 and amd_pstate.shared_mem=1 in some case
UEFI setting to enable: CPPC

See this post for source of info from last month [Testing Update] 2022-03-24 - Linux517, Nvidia, Palemoon (not) - #5 by stephane

The issue is fixed withmanjaro-mate-panel-layout 20220415-2.

Fixed with manjaro-mate-settings 20220415-1.

See above.

FYI, MATE packages in general are rarely maintained. This is true for Arch, Manjaro and the AUR.

The Arch packages were orphaned for quite some time, then a maintainer stepped up and updated some.

We currently have no dedicated maintainers for several of our community editions. I’m playing catch up a little and we build ISO’s occasionally to make sure things aren’t broken, that’s about it.

2 Likes

i updated intel-media-driver from 22.2.2-1 (manjaro package) to 22.2.2-2 from ala.
Now vaapi works with mpv and /usr/lib/dri/iHD_drv_video.so

sudo pacman -U https://archive.archlinux.org/packages/i/intel-media-driver/intel-media-driver-22.2.2-2-x86_64.pkg.tar.zst

3 Likes

Thanks! This worked for me too, now iHD works with vainfo.

I’m having font problem with FireFox on some site

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:

[ERROR: src/geekbench/workload/compute_workload.cpp(111)] workload 321 failed validation

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.

System specs:
Intel i5-6200U
Integrated Graphics (HD Graphics 520)
Thinkpad T460
Kernel 5.15.32-1

linux517 5.17.0 (still missing broadcom-wl, r8168 and rtl8723bu modules!)

It seems this problem has fixed since 5.17.1?

OK, I’ve pushed revision 2 for intel-media-driver now also to this branch.

4 Likes

I try to update with pamac update command, and have been stuck for several hours at [4/36] updating udev hardware database. Should I reboot now?

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>