core 174.4 KiB 167 KiB/s 00:01 [###################################################################] 100%
extra 1905.0 KiB 1790 KiB/s 00:01 [###################################################################] 100%
community 6.7 MiB 5.16 MiB/s 00:01 [###################################################################] 100%
multilib 177.1 KiB 873 KiB/s 00:00 [###################################################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing nvidia-utils (495.44-1) breaks dependency 'nvidia-utils=495.29.05' required by linux513-nvidia
:: installing nvidia-utils (495.44-1) breaks dependency 'nvidia-utils=495.29.05' required by linux514-nvidia
@oberon is current working on the extramodules for 495 driver series. We had some low staffing this week due to some vacations and other things going on. For sure the modules may be online in some hours …
Has anyone been able to get Plasma 5.23.2 desktop to be GPU accelerated with Nvidia in the Wayland session? Whenever I log in to Plasma Wayland with Nvidia 495.44 installed, Plasma renders with llvmpipe, X works as intended. Reverting to 47x fixes Wayland (uses my GTX 1060 instead of llvmpipe)
Tried different kernels, made sure my modesetting config was correct, checked package versions for stuff such as xwayland and egl-wayland, all up to date.
Usually I’m a patient soul; but this GBM support has me drooling, lol
Seems we’re waiting for an egl-wayland and Qt update for this to work properly, so for now we have to use EGLStreams for just a little bit longer. Solution in link.
Some urgent info for all “Unstablers”:
The latest series of updates will make your system unbootable if you’re using LVM and udev-based initramfs. Here is what I’m looking at right now:
Building image from preset: /etc/mkinitcpio.d/linux514.preset: 'default'
-> -k /boot/vmlinuz-5.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.14-x86_64.img
==> Starting build: 5.14.14-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [keyboard]
-> Running build hook: [consolefont]
-> Running build hook: [autodetect]
-> Running build hook: [plymouth]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [plymouth-tpm2-totp]
-> Running build hook: [tpm2]
-> Running build hook: [plymouth-encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [lvm2]
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/install/lvm2: line 33: add_udev_rule: command not found
-> Running build hook: [resume]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-5.14-x86_64.img
==> Image generation successful
This was udev-based initramfs.
Now let’s move to systemd-based:
==> Building image from preset: /etc/mkinitcpio.d/linux514.preset: 'systemd'
-> -k /boot/vmlinuz-5.14-x86_64 -c /etc/mkinitcpio.systemd.conf -g /boot/initramfs-5.14-x86_64-systemd.img
==> Starting build: 5.14.14-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [keyboard]
-> Running build hook: [sd-vconsole]
-> Running build hook: [autodetect]
-> Running build hook: [sd-plymouth]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [sd-plymouth-tpm2-totp]
-> Running build hook: [sd-encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [lvm2]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-5.14-x86_64-systemd.img
==> Image generation successful
Seems OK with systemd hook. Will reboot now and see, but I already can tell that udev-based initramfs’ images I have now are slightly smaller than systemd-based ones, which is the opposite of what it used to be on my machine.
Hilariously both have “Image generation successful” report at the end
PS: the last batch of updates I’m talking about contained these packages:
python-pexpect (4.8.0-3 -> 4.8.0-4)
python-ptyprocess (0.7.0-1 -> 0.7.0-2)
python-cachetools (4.2.3-1 -> 4.2.4-1)
openexr (3.1.2-1 -> 3.1.3-1)
lvm2 (2.03.13-1 -> 2.03.14-1)
cryptsetup (2.4.1-1 -> 2.4.1-3)
device-mapper (2.03.13-1 -> 2.03.14-1)
EDIT:
Yep, as expected, system is unbootable with udev initramfs, but works fine with systemd-based one.
There’s a command add_udev_rule
in updated lvm2
hook, but /usr/lib/initcpio/functions
has no such command:
Got the same `command not found` while update
$ pamac update
Preparing...
Synchronizing package databases...
Refreshing core.db...
Refreshing extra.db...
Refreshing community.db...
Refreshing chaotic-aur.db...
Resolving dependencies...
Checking inter-conflicts...
To upgrade (4):
device-mapper 2.03.14-1 (2.03.13-1) core 300.3 kB
cryptsetup 2.4.1-3 (2.4.1-1) core 601.7 kB
lvm2 2.03.14-1 (2.03.13-1) core 1.6 MB
openexr 3.1.3-1 (3.1.2-1) extra 1.2 MB
Total download size: 3.7 MB
Total installed size: 103.1 kB
Apply transaction ? [y/N] y
Download of openexr (3.1.3-1) started
Download of device-mapper (2.03.14-1) started
Download of device-mapper (2.03.14-1) finished
Download of cryptsetup (2.4.1-3) started
Download of openexr (3.1.3-1) finished
Download of cryptsetup (2.4.1-3) finished
Download of lvm2 (2.03.14-1) started
Download of lvm2 (2.03.14-1) finished
Checking keyring... [4/4]
Checking integrity... [4/4]
Loading packages files... [4/4]
Checking file conflicts... [4/4]
Checking available disk space... [4/4]
Upgrading device-mapper (2.03.13-1 -> 2.03.14-1)... [1/4]
Upgrading cryptsetup (2.4.1-1 -> 2.4.1-3)... [2/4]
Upgrading lvm2 (2.03.13-1 -> 2.03.14-1)... [3/4]
Upgrading openexr (3.1.2-1 -> 3.1.3-1)... [4/4]
Running post-transaction hooks...
Reloading system manager configuration... [1/5]
Reloading device manager configuration... [2/5]
Arming ConditionNeedsUpdate... [3/5]
Updating linux initcpios... [4/5]
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
Refreshing PackageKit... [5/5]
A restart is required for the changes to take effect.
Transaction successfully finished.
$
I saw this too late and I rebooted my machine, now I can’t recover.
I am sorry but does anyone know a good way to recover?
Chroot to your system from live OS and downgrade lvm2 and cryptsetup packages.
@alven do not reboot
To avoid such issues and feel a bit pro (only a lil bit though) you guys can use a cool trick to generate both udev- and systemd-based initrds when updating kernels, cryptsetup and other stuff that triggers initrds’ rebuild:
- Do
cp /etc/mkinitcpio.conf /etc/mkinitcpio.systemd.conf
- Open
/etc/mkinitcpio.systemd.conf
with some editor - Find
HOOKS
section - Make it look like this:
HOOKS=(base systemd keyboard sd-vconsole autodetect sd-plymouth modconf block sd-plymouth-tpm2-totp sd-encrypt lvm2 filesystems)
instead of this:HOOKS=(base udev keyboard consolefont autodetect plymouth modconf block plymouth-tpm2-totp tpm2 plymouth-encrypt lvm2 resume filesystems)
Basically just do as Arch Wiki suggests. I’m writing “like” because the above reflects my set of hooks, yours may be very different. You need a general understanding what you’re doing that’s why I mentioned Arch Wiki as a reference. - After saving that file, navigate to
/etc/mkinitcpio.d
and open any preset there, say, linux515.preset. - Modify the line
PRESETS=('default' 'fallback')
toPRESETS=('default' 'systemd')
- Add there the following:
systemd_config="/etc/mkinitcpio.systemd.conf"
systemd_image="/boot/initramfs-5.15-x86_64-systemd.img"
#systemd_options=""
Done! Now every time you initiate mkinitcpio manually or by pacman hook (during installing updates) mkinitcpio will build 2 initrds for linux 5.15: udev-based and systemd-based. If something goes bad and you won’t be able to boot all you need to do is to select 5.15 entry in Grub menu, press E, modify initramfs path from initramfs-5.15-x86_64.img
to initramfs-5.15-x86_64-systemd.img
and press Ctrl + X to boot.
Of course there are other obstacles if you are using encryption for example, but you got the general idea I guess. Edit Grub’s cmdline too, if needed. Or you can go further and add a respective entry to Grub / systemd-boot menu if you want. That’s another story though.
I downgraded but I am still seeing add_udev_rule issues
in initcpio functions.
Huh?
Summary
┬─[openm@reiwa:~]─[01:01:24]
╰─>$ sudo downgrade lvm2
Available packages (core):
- 1) lvm2 2.02.183 2 remote
...
- 20) lvm2 2.03.12 1 remote
- 21) lvm2 2.03.13 1 remote
+ 22) lvm2 2.03.14 1 remote
+ 23) lvm2 2.03.14 1 /var/cache/pacman/pkg
select a package by number: 21
:: Retrieving packages...
lvm2-2.03.13-1-x... 1530.7 KiB 846 KiB/s 00:02 [#########################] 100%
loading packages...
warning: downgrading package lvm2 (2.03.14-1 => 2.03.13-1)
resolving dependencies...
looking for conflicting packages...
Packages (1) lvm2-2.03.13-1
Total Installed Size: 6.17 MiB
Net Upgrade Size: -0.07 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#########################] 100%
(1/1) checking package integrity [#########################] 100%
(1/1) loading package files [#########################] 100%
(1/1) checking for file conflicts [#########################] 100%
(1/1) checking available disk space [#########################] 100%
:: Processing package changes...
(1/1) downgrading lvm2 [#########################] 100%
:: Running post-transaction hooks...
(1/6) Reloading system manager configuration...
(2/6) Reloading device manager configuration...
(3/6) Arming ConditionNeedsUpdate...
(4/6) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: 5.10.75-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [keyboard]
-> Running build hook: [consolefont]
-> Running build hook: [autodetect]
-> Running build hook: [plymouth]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [plymouth-tpm2-totp]
-> Running build hook: [tpm2]
-> Running build hook: [plymouth-encrypt]
-> Running build hook: [lvm2]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-5.10-x86_64.img
==> Image generation successful
...
As you can see, issue “got fixed” right upon installing (downgrading to) the previous version of lvm2. So I guess you’re doing it wrong.
You’d better quit Unstable branch if you can’t downgrade or else one day you gonna bork your install irrevocably.
UPD: Ah I’m sorry too, I see now how your set up is done. No plymouth-encrypt
hook I suppose but encrypt
instead…
if you are downgrading dont you have to downgrade “device-mapper” as well.
I am sorry I was not very clear, I was able to downgrade cleanly using my cache the issue was since i use encryption I needed to downgrade cryptsetup too, thanks for your help!
Ah, that’s interesting. So you did it from chrooted system, right? I have encryption too but I haven’t downgraded cryptsetup as well. Lvm2 was enough to make its hook work with Manjaro’s mkinitcpio.
OK then, glad it worked for you
Yes, that’s how I did it, downgraded to lvm2 first and then again cryptsetup, now I can boot cleanly.
This seems to the commit that added add_udev_rule to encrypt hooks upgpkg: cryptsetup 2.4.1-2: update mkinitcpio hooks · archlinux/svntogit-packages@57b7f78 · GitHub
No it’s another tool. Found it finally:
In brief, we need an update to systemd, @philm @oberon @Yochanan (aah, somebody help! [Eminem screams in background ])
Btw I hope you guys have read my PM, it’s only a beginning, soon mkinitcpio update will bring a lot of more headache or this sort.
Looks like the error was fixed
$ pamac update
Preparing...
Synchronizing package databases...
Refreshing core.db...
Refreshing extra.db...
Refreshing community.db...
Refreshing multilib.db...
Refreshing chaotic-aur.db...
Resolving dependencies...
Checking inter-conflicts...
To upgrade (11):
systemd-libs 249.5-3 (249.5-2) core 804.8 kB
device-mapper 2.03.14-1 (2.03.13-1) core
cryptsetup 2.4.1-3 (2.4.1-1) core
gsettings-desktop-schemas 41.0-1 (40.0-3) extra 681.3 kB
libxnvctrl 495.44-1 (470.82.00-1) extra 97.3 kB
lvm2 2.03.14-1 (2.03.13-1) core
mhwd-nvidia 495.44-1 (470.82.00-1) core 19.8 kB
openexr 3.1.3-1 (3.1.2-1) extra
systemd 249.5-3 (249.5-2) core 9.0 MB
opencv 4.5.4-4 (4.5.4-1) extra 27.3 MB
systemd-sysvcompat 249.5-3 (249.5-2) core 6.4 kB
Total download size: 37.9 MB
Total installed size: 215.7 kB
Apply transaction ? [y/N] y
Download of libxnvctrl (495.44-1) started
Download of libxnvctrl (495.44-1) finished
Download of gsettings-desktop-schemas (41.0-1) started
Download of mhwd-nvidia (495.44-1) started
Download of mhwd-nvidia (495.44-1) finished
Download of opencv (4.5.4-4) started
Download of gsettings-desktop-schemas (41.0-1) finished
Download of systemd-sysvcompat (249.5-3) started
Download of systemd-sysvcompat (249.5-3) finished
Download of systemd (249.5-3) started
Download of systemd (249.5-3) finished
Download of systemd-libs (249.5-3) started
Download of systemd-libs (249.5-3) finished
Download of opencv (4.5.4-4) finished
Checking keyring... [11/11]
Checking integrity... [11/11]
Loading packages files... [11/11]
Checking file conflicts... [11/11]
Checking available disk space... [11/11]
Upgrading systemd-libs (249.5-2 -> 249.5-3)... [1/11]
Upgrading device-mapper (2.03.13-1 -> 2.03.14-1)... [2/11]
Upgrading cryptsetup (2.4.1-1 -> 2.4.1-3)... [3/11]
Upgrading gsettings-desktop-schemas (40.0-3 -> 41.0-1)... [4/11]
Upgrading libxnvctrl (470.82.00-1 -> 495.44-1)... [5/11]
Upgrading lvm2 (2.03.13-1 -> 2.03.14-1)... [6/11]
Upgrading mhwd-nvidia (470.82.00-1 -> 495.44-1)... [7/11]
Upgrading openexr (3.1.2-1 -> 3.1.3-1)... [8/11]
Upgrading systemd (249.5-2 -> 249.5-3)... [9/11]
Upgrading opencv (4.5.4-1 -> 4.5.4-4)... [10/11]
Upgrading systemd-sysvcompat (249.5-2 -> 249.5-3)... [11/11]
Running post-transaction hooks...
Creating system user accounts... [1/12]
Updating journal message catalog... [2/12]
Reloading system manager configuration... [3/12]
Updating udev hardware database... [4/12]
Applying kernel sysctl settings... [5/12]
Creating temporary files... [6/12]
Reloading device manager configuration... [7/12]
Arming ConditionNeedsUpdate... [8/12]
Updating linux initcpios... [9/12]
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
Refreshing PackageKit... [10/12]
Reloading system bus configuration... [11/12]
Compiling GSettings XML schema files... [12/12]
A restart is required for the changes to take effect.
Transaction successfully finished.
$
$ pamac update --force-refresh
Preparing...
Synchronizing package databases...
Refreshing core.db...
Refreshing extra.db...
Refreshing community.db...
Refreshing multilib.db...
Refreshing chaotic-aur.db...
Refreshing core.files...
Refreshing extra.files...
Refreshing community.files...
Refreshing multilib.files...
Refreshing chaotic-aur.files...
Nothing to do.
Transaction successfully finished.
$
If I will not edit this post to mention that it is fixed in 10 minutes, than I started to search my LiveCD boot media.
EDIT
PC reboot went well as ordinary. It was fixed. Thanks to all!
$ mhwd-kernel -li
Currently running: 5.15.0-1-MANJARO (linux515)
The following kernels are installed in your system:
* linux515
$
Yep, that was the issue and you can blame it on me, I suppose. I synced with Arch before updating our systemd
overlay. Such as life (sometimes) in the unstable branch.
We are on unstable
. sometimes it is unstable, but mostly stable.
I am happy that somebody posted the problem when met it and it was solved fast.
TY!
No worries, no blaming. We’re here to monitor such issues. Our watch is not over yet!