After the last pamac
update, I’m getting some strange behaviour between pamac and polkit1 in KDE. Even with a wrong password, pamac can install/remove/update packages when executed via the terminal. GUI doesn’t allow it without a valid password being entered. All is well with it in /etc/passwd
polkitd:x:102:102:PolicyKit daemon:/:/sbin/nologin
rtkit:x:133:133:RealtimeKit:/proc:/sbin/nologin
pamac update
Preparing...
==== AUTHENTICATING FOR org.manjaro.pamac.commit ====
Authentication is required to install, update, or remove packages
Authenticating as: George (george)
Password:
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
==== AUTHENTICATION FAILED ====
Error: Authentication failed
Nothing to do.
Transaction successfully finished.
I just tried pamac upgrade used the wrong password and got the same message as you.I tried it again with the right password and it showed I needed updates.
My wired Ethernet isn’t working under 6.2.6-1.
I checked the output with lshw -C network and got an *-network UNCLAIMED for RTL8111/8168/8411.
dragan
March 16, 2023, 6:05pm
26
driver / module was not loaded (probably r8169
), you can try manually (# modprobe r8169
and watch journalctl
) but the question remains why it didn’t on startup.
Same controller / kernel here, all is fine.
1 Like
Found the issue! I missed an error on pamac stating “bad return status for module build on kernel: 6.2.6-1-MANJARO”. So I rebuild r8168-dkms and everything is back on track. Thanks, @dragan , for checking, it saved me some debugging.
I’m having trouble with linux510 5.10.175-1
. It hangs and won’t continue booting. 5.10.174-1 works fine.
Looks like it’s the same as here: [Testing Update] 2023-03-18 - Kernels, Thunderbird, Cinnamon, KDE-git, Python, Haskell - #3 by Oldhabbits
When update mkinitcpio:
“WARNING: Possibly missing firmware for module: ‘csiostor’”
I attempted a fix with mkinitcpio
35.1-3.
2 Likes
mkinitcpio
35.1-4 should do the trick.
3 Likes
Yochanan:
do the trick.
YES - it works -Thank You
1 Like
Zesko
March 23, 2023, 6:39pm
34
After upgrading from Kernel version 6.2.7-2
to 6.2.8-1
, I get the error message:
$ journalctl --no-pager -p 3 -b --output=cat
spl: version magic '6.2.7-2-MANJARO SMP preempt mod_unload ' should be '6.2.8-1-MANJARO SMP preempt mod_unload '
spl: version magic '6.2.7-2-MANJARO SMP preempt mod_unload ' should be '6.2.8-1-MANJARO SMP preempt mod_unload '
It looks like version magic of spl doesn’t match kernel version.
$ modinfo spl
filename: /lib/modules/6.2.8-1-MANJARO/extramodules/spl.ko.xz
version: 2.1.9-1
license: GPL
author: OpenZFS
description: Solaris Porting Layer
srcversion: 0248BCBBFA4DFB290E4D2F0
depends:
retpoline: Y
name: spl
vermagic: 6.2.7-2-MANJARO SMP preempt mod_unload
Solution:
Uninstall linux62-zfs
Install zfs-dkms
. The error messages are gone. (But the ZFS module is not loaded.)
Edit:
OpenZFS 2.1.9 is not compatible with Kernel 6.2.8, because building the zfs module failed, but it has no issue with Kernel 6.2.7.
Solution:
Switch back to Kernel 6.1 LTS, no error message in journalctl
The known issue:
opened 02:43AM - 23 Mar 23 UTC
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.
```
1 Like
NVIDIA 530.41.03 drivers will be available shortly.
Note that there is now compatibility for Linux kernels with Indirect Branch Tracking (IBT). The ibt=off
kernel parameter is no longer required.
Zesko
March 23, 2023, 7:39pm
36
VirtualBox still needs this kernel parameter when using Intel 11th CPU.
Why? More info, please?
Either way, that has nothing to do with the NVIDIA driver.
Zesko
March 23, 2023, 7:45pm
38
I tested VirutalBox on Intel11th CPU. If I removed this kernel parameter, then I still get the same issue as before:
For the past couple of months, I’ve been unable to launch VMs on my Manjaro host while running the 5.18 kernel. VirtualBox just hangs on “starting virtual machine.” I had no such problem on the 5.17, 5.16, or 5.15 kernels. Continuing to use 5.15 solves the issue, so this isn’t anything urgent, but I want to understand the problem.
Back in early June, it appeared that VirtualBox 6.1.34 was the problem, with a fix promised for VirtualBox 6.1.35+. So with the arrival of VirtualBox 6.1.36 in this l…
I got a problem with virtualbox starting a virtual machine.
I use Manjaro on two computers with the same versions (release 22.0.0, Sikaris, kernel linux 5.19.7-1) and the same installation procedure.
With one computer (HP Pavilion Laptop 14-dv1xxx), after a release of the virtualbox application, I’m unable to restart the virtual machine with the followig message, which don’t stop:
[image]
I need to kill both processes (VM and virtualbox) to reinitiate the system.
I tried to uninstall the…
VirtualBox machine can not start or freezes when using Linux Kernel 5.18 and Intel 11th or 12th Gen.
The error messages from Journalctl:
Jun 16 21:50:43 zesko kernel: traps: Missing ENDBR: 0xffffa48c478ab3c0
Jun 16 21:50:43 zesko kernel: kernel BUG at arch/x86/kernel/traps.c:252!
The known issue: FS#74891 : kernel bug (upon boot) after upgrade to 5.18.arch1-1
Solution:
For Grub:
Edit /etc/default/grub to add the Kernel parameter ibt=off
sudo update-grub
Reboot
Linux Kernel 5.17 has no i…
1 Like
Thanks for the info. I’ll mention that in the next update post (probably Testing Updates ). No need for a new Unstable Updates post probably until GNOME 44 is available.
Yochanan
Split this topic
March 24, 2023, 3:28pm
40
Zesko
March 25, 2023, 8:40pm
41
Zesko:
OpenZFS 2.1.9 is not compatible with Kernel 6.2.8, because building the zfs module failed, but it has no issue with Kernel 6.2.7.
Solution:
Switch back to Kernel 6.1 LTS, no error message in journalctl
The known issue:
Best solution for me:
I created a new KVM/QEMU to setup a small NAS with separate Kernel 6.1 LTS and ZFS that directly access my external physical disks as pass-through disks via PCI without virtual.
Host: Kernel 6.2 is now running on my PC without ZFS.
Guest: Kernel 6.1 LTS is running on my KVM with ZFS on the same PC.
Both communicate via a local NFS share (Speed ~31Gb/s). NFS preserves all file permissions , Samba does not.
They plan to have a proper fix for this in the 2.1.10 release, see this comment on that issue.
1 Like