[Stable Update] 2023-03-31 - Kernels, Plasma 5.27 LTS, Pamac, Phosh, Mesa, LibreOffice

sparcplug · 31 March 2023 16:17

Quick question concerning ZFS compatibility and linux 6.2.8.
Apparently backported bug fixes to linux 6.2.8 introduced incompatibility with zfs 2.1.9 as detailed in:

github.com/openzfs/zfs

6.2.8 kernel revert needed for zfs-2.1.9 dkms

opened 02:43AM - 23 Mar 23 UTC

closed 06:29PM - 27 Mar 23 UTC

comrade-meowski

Type: Defect

The latest stable kernel 6.2.8 causes zfs-2.1.9 & zfs-2.1.10-staging to fail dur…ing dkms installation of the zfs modules. The error given in the dkms make.log is: ``` ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_start_io_acct' ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_end_io_acct_remapped' ``` Building 6.2.8 with commit b477180587d81a4dd756361098bd534dfa6bb53d reverted allows zfs dkms to complete normally again. I have only tested with dkms but presumably this will more generally stop zfs building against 6.2.8 at all. This is the kernel commit: ``` commit b477180587d81a4dd756361098bd534dfa6bb53d Author: Yu Kuai <yukuai3@huawei.com> Date: Thu Feb 23 17:12:26 2023 +0800 block: count 'ios' and 'sectors' when io is done for bio-based device [ Upstream commit 5f27571382ca42daa3e3d40d1b252bf18c2b61d2 ] While using iostat for raid, I observed very strange 'await' occasionally, and turns out it's due to that 'ios' and 'sectors' is counted in bdev_start_io_acct(), while 'nsecs' is counted in bdev_end_io_acct(). I'm not sure why they are ccounted like that but I think this behaviour is obviously wrong because user will get wrong disk stats. Fix the problem by counting 'ios' and 'sectors' when io is done, like what rq-based device does. ```

It appears a patch was generated correcting the issue

github.com/archzfs/archzfs

zfs git branch (and also 2.1.9 release): include patch 3ace9de and 2e9c9b7

opened 08:55PM - 23 Mar 23 UTC

RAMChYLD

Kernel 6.2.8 backported some changes from kernel 6.3 which breaks ZFS. Speci…fically, the symbols bio_end_io_acct_remapped and bio_start_io_acct had been changed to GPL-only and breaks ZFS 2.1.9 and git. > ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_end_io_acct_remapped' > ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_start_io_acct' According to https://github.com/openzfs/zfs/issues/14658, the titular two patches should apply cleanly to 2.1.9 and fixes the issue on 6.2.8++ kernels. I did test it out the quick and dirty way (apply directly to /usr/src/zfs-git) and it works even if there were some warnings during building (dkms error 2 which appears to be nonfatal), so I can vouch for it. Edit: Also successfully applied the patches to 2.1.9 release now, so can vouch that it works on both.

This has been applied to linux modules extra as of approximately 8 hours ago on gitlab
zfs 2.1.9-10

Checking the package versions for linux6.2-zfs from extra lists 2.1.9-9 as the latestversion on all manjaro variants, stable, testing and unstable
https://packages.manjaro.org/?query=zfs

Is there any reason the latest extra module zfs version is not included in any manjaro variant?

Given that I’m depending on zfs and am currently using linux6.2, should I avoid this particular stable update as I’m not interested in reverting to linux6.1?
Or should I manually determine the means to checkout, build and apply the 2.1.9-10 zfs module myself?

myCatnip · 31 March 2023 16:39

Can’t change it from KDE config either.

I don’t get migraines from 144hz, just headaches, but they used to take 4-5hours to come on. I’ve been on 240+ for many years now and 144 is feeling instantly much worse than I recall, like everything is high speed-stop motion. It’s more a tingling in my head I’m noticing which is a sign I’ll get a headache soon. It’s only any form of strobe backlight / pwm under 1khz gives me migranes in 1-15mins, was just mentioning I don’t have that on because some people suggest checking that’s off. For some reason I was fine on 75hz CRT back in the day, and had to stick with CRT all through the 60hz LCD panel era because they gave me headaches in 1-2 hours.

Right now it’s sort of OK if nothing is moving on the screen, but the moment I move windows/mouse my head starts to feel weird.

I’m going to look up xrandr commands again now and hopefully fix this.

Yochanan · 31 March 2023 16:39

Now it has.

zfs-dkms 2.1.9-2 and linux62-zfs 2.1.9-11 will be coming along shortly.

Because it was failing to build previously.

sparcplug · 31 March 2023 16:44

Thanks for the quick response, cheers!

myCatnip · 31 March 2023 16:44

Tried:

cvt 1920 1080 280                                                            ✔ 
# 1920x1080 279.75 Hz (CVT) hsync: 358.36 kHz; pclk: 969.00 MHz
Modeline "1920x1080_280.00"  969.00  1920 2104 2312 2704  1080 1083 1088 1281 -hsync +vsync
    ~  sudo xrandr --newmode "1920x1080_280.00"  969.00  1920 2104 2312 2704  1080 1083 1088 1281 -hsync +vsync
[sudo] password: 
    ~  sudo xrandr --addmode DP-0 "1920x1080_280.00"                                      ✔ 
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  45
  Current serial number in output stream:  46

No clue what to do, need to take a break again, will try again in an hour or so.

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

purplemunchies · 31 March 2023 16:50

I ran into error messages after the update from Pamac.

Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
A restart is required for the changes to take effect.

Looking into /var/log/pacman.logs, the relevant parts shows the following:

2023-03-31T08:04:39-0400] [ALPM] transaction started
[2023-03-31T08:04:39-0400] [ALPM] upgraded archlinux-keyring (20230130-1 -> 20230320-1)
[2023-03-31T08:04:39-0400] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] ==> Updating trust database...
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-07
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] ==> Updating trust database...
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-07
[2023-03-31T08:04:43-0400] [ALPM] upgraded manjaro-keyring (20221028-4 -> 20230318-1)
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] ==> Appending keys from manjaro.gpg...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET]   -> Locally signed 2 keys.
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] ==> Disabling revoked keys in keyring...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET]   -> Disabled 8 keys.
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] ==> Updating trust database...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-07
[2023-03-31T08:04:44-0400] [ALPM] transaction completed

I’m running a relatively fresh install of Manjaro XFCE (stable branch) from earlier in March. All updates installed as they came in, and no AUR enabled. Running kernel 6.2.8-1.

I made a post about it in the Manjaro support forum before I found this page.

So far everything seems to run normally. I’ve opted not to try any fixes until I see if these error messages come up again.

I did though get caught by the “nvidia-settings” change of it not being installed by default in the updates. Installing it manually through Pamac caused no errors. Though this seems like poor planning in development. I do agree with Philm’s post in the link for that. This problem will confuse much newer users. It even took me a little to figure out since I’m new to the Manjaro distribution.

linub · 31 March 2023 16:57

is anyone else having an issue with nvidia-settings
like @Kobold and @stzer are having?

just checking before installing it.

Yochanan · 31 March 2023 16:59

Do you mean the flickering? That’s not related to nvidia-settings, it appears to be a driver issue. The driver package is nvidia-utils.

See FS#77975 - [nvidia] 530.41.03-1 high refresh rate problems

mafunzalo · 31 March 2023 17:01

For me this new kernel update to linux515 5.15.104 hung my laptop when it got to the “build hook [keyboard]” part of the build.

I was able to work around this by typing CTRL-ALT-F4 and then getting into the command line. Then I did pacman -Syu linux515 and it was able to rebuild the kernel properly. Everything worked fine after reboot.

Loacoon · 31 March 2023 17:08

Since the update, there is a few apps (identified for now are Firefox, Gimp and Viewnior) in which my mouse wheels first step doesn’t do anything when I rotate it in a direction. It’s quite bothering TBH…

linub · 31 March 2023 17:19

do you have a high refresh rate monitor?

Kobold · 31 March 2023 17:24

Yes, but i dont think my bug is related to the high refresh rate problem, that @Yochanan posted,
because i dont use Wayland as the people on that Arch Forum and my flashes temporary vanished when running 3D rendering (ingame) or watching videos with smplayer.

I edited my first posting already and added few links for more details.

yt87 · 31 March 2023 17:34

I have /home -> /mnt/sdb1/home. Update removed that link and created an empty directory /home. That prevented me from logging in.
So, my questions are:

Is that symlink a bad practice?
If so, mounting the second disk partition under /home is the proper way to go?

Otherwise, no problems so far.

pheiduck · 31 March 2023 17:36

I thought this update included the latest linux-firmware.
But is not the case, what a pity. Already in the Arch Linux Testing Repo:

https://archlinux.org/packages/testing/any/linux-firmware/

I have to be patient now.
This will bring the following firmware on board (qat_4xxx):

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_4xxx.bin

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_4xxx_mmp.bin

andreas85 · 31 March 2023 17:38

In these cases it is better to use a bind-mount instead of a symlink

This may apply to /home, /usr, /var and other essential directories
Please also follow this link (not the preview shown , but the expanded text):

varikonniemi · 31 March 2023 17:46

seems like a very weird place to crash as it is a pretty frequent and preserved codepath. Please check journal for errors and maybe post more info.

omar1 · 31 March 2023 17:53

There’s a problem that has been occuring for many months now, thought this update would fix it but didn’t. I’m on Manjaro Gnome. Everytime the Pamac software takes much time on a process, it it thinks that it crashed and it asks if I want to force close it or wait while in fact it didn’t crash, waiting for a few seconds/minutes fixes it and completes the process. It’s really annoying. Any fix for that? Thank you in advance.

deroberts1 · 31 March 2023 17:58

When I saw only 73% had no issues, I was sure I would have an update problem running KDE 5.24.7 LTS and the nouveau driver. But knock me over with a feather. NO PROBLEMS!

Frenchy · 31 March 2023 18:09

Had the same thoughts, although running Plasma 5.26.x, and, now, 5.27.x… All’s well.

iCEVooDoo · 31 March 2023 18:32

This is my first upgrade with mesa non-free included.
After I use the upgrade command, I receive this messages and I can’t continue.
Pleas a little advice on what can I do…

pamac upgrade --force-refresh                                                                                                   100 ✘  6s  
Preparing...
==== AUTHENTICATING FOR org.manjaro.pamac.commit ====
Authentication is required to install, update, or remove packages
Authenticating as: xxx
Password: 
==== AUTHENTICATION COMPLETE ====
Synchronizing package databases...
Refreshing mesa-nonfree.db...                                                                                                                             
Refreshing core.db...                                                                                                                                     
Refreshing extra.db...                                                                                                                                    
Refreshing community.db...                                                                                                                                
Refreshing multilib.db...                                                                                                                                 
Error: multilib.db: mesa-nonfree: signature from "Mesa Freeworld <info@manjaro.download>" is invalid                                                      
Refreshing mesa-nonfree.files...                                                                                                                          
Refreshing core.files...                                                                                                                                  
Refreshing extra.files...                                                                                                                                 
Refreshing community.files...                                                                                                                             
Refreshing multilib.files...                                                                                                                              
Error: multilib.files: mesa-nonfree: signature from "Mesa Freeworld <info@manjaro.download>" is invalid                                                   
Failed to synchronize databases
Warning: libva-mesa-driver: local (1:22.3.5-1) is newer than extra (23.0.1-1)
Warning: mesa: local (1:22.3.5-1) is newer than extra (23.0.1-1)
Warning: mesa-vdpau: local (1:22.3.5-1) is newer than extra (23.0.1-1)
Warning: opencl-mesa: local (1:22.3.5-1) is newer than extra (23.0.1-1)
Warning: vulkan-intel: local (1:22.3.5-1) is newer than extra (23.0.1-1)
Warning: vulkan-mesa-layers: local (1:22.3.5-1) is newer than extra (23.0.1-1)
Warning: vulkan-radeon: local (1:22.3.5-1) is newer than extra (23.0.1-1)
Warning: vulkan-swrast: local (1:22.3.5-1) is newer than extra (23.0.1-1)
Warning: vulkan-virtio: local (1:22.3.5-1) is newer than extra (23.0.1-1)
Error: Failed to prepare transaction: invalid or corrupted database