philm
8 January 2024 05:43
1
Hello community,
What is great to start 2024? With a new update to our testing branch. This time we think the blocker packages systemd , mesa and plymouth should work just fine. Let us know if you still see some regressions.
Recent News:
Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate !
Previous News
Finding information easier about Manjaro
Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: New Manjaro search engine is available | Blog
Notable Package Updates:
Some Kernels got updated
this also include the final release of 6.7 - We updated Mesa to 23.3.2
Systemd got renewed to 255.2
read the news to see what this series provides on new features!
Plymouth is updated to 24.004.60 Phosh got updated to 0.35.0 AMDVLK is now at 2023.Q4.3 Qt5 is at 5.15.12
please report back if we forgot some rebuilds
Updates to Gnome , Cinnamon and Deepin
Usual KDE-git , Haskell and Python updates
Info about AUR packages
Arch User Repository ) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements
For help with AUR packages, please create a new topic in AUR
Get our latest daily developer images now from Github: Plasma , GNOME , XFCE . You can get the latest stable releases of Manjaro from CDN77 .
Our current supported kernels
linux419 4.19.303
linux54 5.4.265
linux510 5.10.206
linux515 5.15.146
linux61 6.1.71
linux65 6.5.13 [EOL]
linux66 6.6.10
linux67 6.7.0
linux61-rt 6.1.66_rt19
linux65-rt 6.5.2_rt8
linux66-rt 6.6.7_rt18
Package Changes (Mon Jan 8 06:08:58 CET 2024)
testing core x86_64: 25 new and 24 removed package(s)
testing extra x86_64: 1456 new and 1449 removed package(s)
testing kde-unstable x86_64: 257 new and 253 removed package(s)
testing multilib x86_64: 15 new and 15 removed package(s)
A list of all package changes can be found here
No issue, everything went smoothly
Yes there was an issue. I was able to resolve it myself.(Please post your solution)
Yes i am currently experiencing an issue due to the update. (Please post about it)
Check if your mirror has already synced:
2 Likes
philm
8 January 2024 05:44
2
This is a wiki post; please edit as necessary. RSS feed
Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!
Plymouth changes
WARNING : The plymouth-encrypt and sd-plymouth hooks no longer exist in the package. You should replace them with encrypt and plymouth hooks in your mkinitcpio.conf. The lxdm-plymouth.service, lightdm-plymouth.service and sddm-plymouth.service systemd service files no longer exist in the package. You should enable lxdm.service, lightdm.service or sddm.service instead.
Nvidia 545 drivers might have issues
If you are having no issues with the 545 series, there is nothing to do. If you are, you can downgrade to the 535 series with pamac update --enable-downgrade or sudo pacman -Syuu.
So far we know about these issues the Nvidia 545 driver series has:
If you experience similar or new issues please run sudo usr/bin/nvidia-bug-report.sh and post either in an already given post or create a new one, including your generated nvidia-bug-report.log.gz for Nvidia to fix the issue: Linux - NVIDIA Developer Forums
Changes in JDK / JRE 21 packages may require manual intervention
2023-11-02 - Frederik Schwan
We are introducing a change in JDK/JRE packages of our distro. This is triggered from the way a JRE is build in modern versions of Java (>9). We are introducing this change in Java 21.
To sum it up instead of having JDK and JRE packages coexist in the same system we will be making them conflict. The JDK variant package includes the runtime environment to execute Java applications so if one needs compilation and runtime of Java they need only the JDK package in the future. If, on the other hand, they need just runtime of Java then JRE (or jre-headless) will work.
This will (potentially) require a manual user action during upgrade:
If you have both JDK and JRE installed you can manually install the JDK with pacman -Sy jdk-openjdk && pacman -Su and this removes the JRE related packages.
If you have both JRE and JRE-headless you will need to choose one of them and install it manually since they would conflict each other now.
If you only have one of the JDK/JRE/JRE-headless pacman should resolve dependencies normally and no action is needed.
At the moment this is only valid for the upcoming JDK 21 release.
– Arch Linux - News: Incoming changes in JDK / JRE 21 packages may require manual intervention
Mechanical HDDs may not spin-down properly on shutdown
There might be a regression introduced with 6.6.0-rc4 which got also backported to 6.1.59 and 6.5.8 Kernels. There is a discussion with the author of the offending patch ongoing here .
ZFS package changes
ZFS extramodules; i.e., linuxXX-zfs, have been dropped from the repos. There have been recent difficulties building them and no one on the Manjaro Team uses ZFS.
Please install zfs-dkms instead. You will to need to manually remove the old 2.1.13 extramodule package(s) first to install the new 2.2.0 packages; i.e., with linux61:
sudo pacman -R linux61-zfs && sudo pacman -Syu zfs-dkms
Restarting gnome-shell using Alt+F2 and entering R, causes a crash
FS#79884 : [gnome-shell] Restarting gnome-shell using Alt+F2 and entering R, causes a crash
GNOME Extensions that target older GNOME versions will not work in GNOME 45
It is recommended to remove all third-party extensions before updating, then install the compatible versions after updating and rebooting. All Most extensions in the Manjaro repos are already updated.
glibc-locales update requires manual intervention
If you had the old glibc-locales package from the extra repo installed, the update to the new core package will need manual intervention:
sudo pacman -Syu glibc-locales --overwrite /usr/lib/locale/\*/\*
Previous testing threads:
1 Like
Hello! Don’t know, why, but I experience the booting problem after the latest update with kernels 6.6.10-1 and 6.7.0. The boot time is too long, sometimes it takes the PC forever to reboot, it just hangs. I have to cold-reboot it.
Confirmed. Restart/reboot the system does not work. Just seeing black screen forever. Switch PC OFF then ON - works.
1 Like
mpv throws an error about not finding libplacebo after updating:mpv: error while loading shared libraries: libplacebo.so.264: cannot open shared object file: No such file or directory
Sounds like you’re in an unsupported partial upgrade state. Make sure your mirrors are up to date. You should have libplacebo 6.338.1-1 and mpv 1:0.37.0-1.
may be add warning about Btrfs :
What warning?wiki post yourself as you probably already know.
I have had same error after 24.01.02 stabel update on Jan. 3rd. But now is is fixed for stable update.
rechecked UEFI , ok for SVM
MrKiu
9 January 2024 07:56
10
I have same kind of issue. Somehow sddm does not start correctly and screen stays black forever. If I do cold reboot, system boots correctly.
Boot log from sddm start :
janv. 09 08:31:51 pc-veranda sddm[705]: Adding new display...
janv. 09 08:31:51 pc-veranda sddm[705]: Loaded empty theme configuration
janv. 09 08:31:51 pc-veranda sddm[705]: Xauthority path: "/run/sddm/xauth_MrbriC"
janv. 09 08:31:51 pc-veranda sddm[705]: Using VT 2
janv. 09 08:31:51 pc-veranda sddm[705]: Display server starting...
janv. 09 08:31:51 pc-veranda sddm[705]: Writing cookie to "/run/sddm/xauth_MrbriC"
janv. 09 08:31:51 pc-veranda sddm[705]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_MrbriC -noreset -displayfd 16
janv. 09 08:31:51 pc-veranda kernel: [drm] DSC precompute is not needed.
janv. 09 08:31:52 pc-veranda NetworkManager[646]: <info> [1704785512.3342] device (enp8s0): carrier: link connected
janv. 09 08:31:52 pc-veranda NetworkManager[646]: <info> [1704785512.3343] device (enp8s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-sta>
janv. 09 08:31:52 pc-veranda NetworkManager[646]: <info> [1704785512.3349] policy: auto-activating connection 'Wired connection 2' (3eb983b5-cfe1-3dbc-ab00-d857b6ba59a0)
janv. 09 08:31:52 pc-veranda NetworkManager[646]: <info> [1704785512.3351] device (enp8s0): Activation: starting connection 'Wired connection 2' (3eb983b5-cfe1-3dbc-ab00-d857>
janv. 09 08:31:52 pc-veranda NetworkManager[646]: <info> [1704785512.3351] device (enp8s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
janv. 09 08:31:52 pc-veranda NetworkManager[646]: <info> [1704785512.3352] manager: NetworkManager state is now CONNECTING
janv. 09 08:31:52 pc-veranda kernel: e1000e 0000:08:00.0 enp8s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
janv. 09 08:31:52 pc-veranda NetworkManager[646]: <info> [1704785512.4051] device (enp8s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
janv. 09 08:31:52 pc-veranda NetworkManager[646]: <info> [1704785512.4058] device (enp8s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
janv. 09 08:31:52 pc-veranda NetworkManager[646]: <info> [1704785512.4064] dhcp4 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
janv. 09 08:31:52 pc-veranda avahi-daemon[597]: Joining mDNS multicast group on interface enp8s0.IPv6 with address fe80::90dc:2eeb:74cb:85e6.
janv. 09 08:31:52 pc-veranda avahi-daemon[597]: New relevant interface enp8s0.IPv6 for mDNS.
janv. 09 08:31:52 pc-veranda avahi-daemon[597]: Registering new address record for fe80::90dc:2eeb:74cb:85e6 on enp8s0.*.
janv. 09 08:31:53 pc-veranda ModemManager[678]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:00.0/0000:04:>
janv. 09 08:31:53 pc-veranda ModemManager[678]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:07.0/0000:08:>
janv. 09 08:31:53 pc-veranda systemd[1]: systemd-rfkill.service: Deactivated successfully.
janv. 09 08:31:55 pc-veranda NetworkManager[646]: <info> [1704785515.6047] device (enp8s0): carrier: link connected
janv. 09 08:31:55 pc-veranda kernel: e1000e 0000:08:00.0 enp8s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
janv. 09 08:31:56 pc-veranda NetworkManager[646]: <info> [1704785516.8693] dhcp4 (enp8s0): state changed new lease, address=192.168.1.33
janv. 09 08:31:56 pc-veranda NetworkManager[646]: <info> [1704785516.8696] policy: set 'Wired connection 2' (enp8s0) as default for IPv4 routing and DNS
janv. 09 08:31:56 pc-veranda dbus-daemon[599]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested >
janv. 09 08:31:56 pc-veranda dbus-daemon[599]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.serv>
janv. 09 08:31:56 pc-veranda avahi-daemon[597]: Joining mDNS multicast group on interface enp8s0.IPv4 with address 192.168.1.33.
janv. 09 08:31:56 pc-veranda avahi-daemon[597]: New relevant interface enp8s0.IPv4 for mDNS.
janv. 09 08:31:56 pc-veranda avahi-daemon[597]: Registering new address record for 192.168.1.33 on enp8s0.IPv4.
janv. 09 08:31:56 pc-veranda NetworkManager[646]: <info> [1704785516.8817] device (enp8s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
janv. 09 08:31:56 pc-veranda NetworkManager[646]: <info> [1704785516.8829] device (enp8s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
janv. 09 08:31:56 pc-veranda NetworkManager[646]: <info> [1704785516.8830] device (enp8s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
janv. 09 08:31:56 pc-veranda NetworkManager[646]: <info> [1704785516.8833] manager: NetworkManager state is now CONNECTED_SITE
janv. 09 08:31:56 pc-veranda NetworkManager[646]: <info> [1704785516.8834] device (enp8s0): Activation: successful, device activated.
janv. 09 08:31:56 pc-veranda NetworkManager[646]: <info> [1704785516.8837] manager: startup complete
janv. 09 08:31:56 pc-veranda systemd[1]: Finished Network Manager Wait Online.
janv. 09 08:31:56 pc-veranda systemd[1]: Reached target Network is Online.
janv. 09 08:31:56 pc-veranda systemd[1]: Starting Notify NFS peers of a restart...
janv. 09 08:31:56 pc-veranda systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
janv. 09 08:31:56 pc-veranda sm-notify[750]: Version 2.6.4 starting
janv. 09 08:31:56 pc-veranda systemd[1]: Starting pkgfile database update...
janv. 09 08:31:56 pc-veranda NetworkManager[646]: <info> [1704785516.9519] manager: NetworkManager state is now CONNECTED_GLOBAL
janv. 09 08:31:56 pc-veranda rpc.statd[754]: Version 2.6.4 starting
janv. 09 08:31:56 pc-veranda rpc.statd[754]: Flags: TI-RPC
janv. 09 08:31:56 pc-veranda systemd[1]: Started Notify NFS peers of a restart.
janv. 09 08:31:56 pc-veranda systemd[1]: Started NFS status monitor for NFSv2/3 locking..
janv. 09 08:31:56 pc-veranda systemd[1]: Starting Automounts filesystems on demand...
janv. 09 08:31:56 pc-veranda (utomount)[760]: autofs.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
janv. 09 08:31:56 pc-veranda systemd[1]: tmp-autoUQSId0.mount: Deactivated successfully.
janv. 09 08:31:56 pc-veranda systemd[1]: Started Automounts filesystems on demand.
janv. 09 08:31:56 pc-veranda systemd[1]: Started Command Scheduler.
janv. 09 08:31:56 pc-veranda systemd[1]: Reached target Multi-User System.
janv. 09 08:31:56 pc-veranda systemd[1]: Reached target Graphical Interface.
janv. 09 08:31:56 pc-veranda crond[773]: (CRON) STARTUP (1.7.0)
janv. 09 08:31:56 pc-veranda crond[773]: (CRON) INFO (Syslog will be used instead of sendmail.)
janv. 09 08:31:56 pc-veranda crond[773]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 72% if used.)
janv. 09 08:31:56 pc-veranda crond[773]: (CRON) INFO (running with inotify support)
janv. 09 08:31:57 pc-veranda systemd[1]: pkgfile-update.service: Deactivated successfully.
janv. 09 08:31:57 pc-veranda systemd[1]: Finished pkgfile database update.
janv. 09 08:31:57 pc-veranda systemd[1]: Startup finished in 7.862s (firmware) + 5.283s (loader) + 2.398s (kernel) + 11.718s (userspace) = 27.263s.
janv. 09 08:31:57 pc-veranda NetworkManager[646]: <info> [1704785517.9490] policy: set 'Wired connection 2' (enp8s0) as default for IPv6 routing and DNS
janv. 09 08:31:57 pc-veranda avahi-daemon[597]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address fe80::90dc:2eeb:74cb:85e6.
janv. 09 08:31:57 pc-veranda avahi-daemon[597]: Joining mDNS multicast group on interface enp8s0.IPv6 with address 2a01:e0a:28d:5a10:854c:c340:ab27:bca1.
janv. 09 08:31:57 pc-veranda avahi-daemon[597]: Registering new address record for 2a01:e0a:28d:5a10:854c:c340:ab27:bca1 on enp8s0.*.
janv. 09 08:31:57 pc-veranda NetworkManager[646]: <info> [1704785517.9628] dhcp6 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
janv. 09 08:31:57 pc-veranda avahi-daemon[597]: Withdrawing address record for fe80::90dc:2eeb:74cb:85e6 on enp8s0.
janv. 09 08:31:57 pc-veranda NetworkManager[646]: <info> [1704785517.9689] dhcp6 (enp8s0): state changed new lease
janv. 09 08:31:57 pc-veranda systemd[1]: tmp-autotzULFm.mount: Deactivated successfully.
janv. 09 08:31:59 pc-veranda systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
janv. 09 08:32:19 pc-veranda systemd[1]: systemd-hostnamed.service: Deactivated successfully.
2 Likes
Hi. Black screen too after this update.
janv. 09 09:45:48 steph-aspirea315510p kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.UBTC], AE_ALREADY_EXISTS (20230628/dswload2-326)
janv. 09 09:45:48 steph-aspirea315510p kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
janv. 09 09:45:48 steph-aspirea315510p systemd-udevd[260]: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:57 Unknown group 'uaccess', ignoring.
janv. 09 09:45:49 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: timeout waiting for FW reset ACK (inta_hw=0x0)
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 6
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 77.f92b5fed.0 so-a0-jf-b0-77.ucode
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000084 | NMI_INTERRUPT_UNKNOWN
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00A002F0 | trm_hw_status0
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x004D2A06 | branchlink2
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x004C92BE | interruptlink1
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x004C92BE | interruptlink2
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00011F5A | data1
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x01000000 | data2
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | data3
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | beacon time
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0001B415 | tsf low
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | time gp1
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00026789 | time gp2
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0000004D | uCode version major
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0xF92B5FED | uCode version minor
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000370 | hw version
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00480002 | board version
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x802EFF00 | hcmd
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00020000 | isr0
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr1
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x58F00002 | isr2
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00C0000C | isr3
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr4
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | last cmd Id
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00011F5A | wait_event
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | timestamp
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000028 | flow_handler
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | ADVANCED_SYSASSERT
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink2
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink1
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac data1
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac data2
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac data3
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac major
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac minor
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | frame pointer
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | stack pointer
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | last host cmd
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: IML/ROM dump:
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00004F71 | IML/ROM data1
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: Fseq Registers:
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x80330000 | FSEQ_TOP_INIT_VERSION
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00010009 | FSEQ_CNVIO_INIT_VERSION
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0xFFB23B89 | FSEQ_TOP_CONTENT_VERSION
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x01300202 | FSEQ_CNVR_ID
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00010009 | FSEQ_PREV_CNVIO_INIT_VERSION
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00330000 | FSEQ_WIFI_FSEQ_VERSION
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00330000 | FSEQ_BT_FSEQ_VERSION
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000118 | FSEQ_CLASS_TP_VERSION
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: UMAC CURRENT PC: 0x8047e450
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: LMAC1 CURRENT PC: 0xd0
janv. 09 09:45:50 steph-aspirea315510p (udev-worker)[291]: hiddev0: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:57 Only network interfaces can be renamed, ignoring NAME="usb/%k".
janv. 09 09:45:50 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: timeout waiting for FW reset ACK (inta_hw=0x0)
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 6
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 77.f92b5fed.0 so-a0-jf-b0-77.ucode
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000084 | NMI_INTERRUPT_UNKNOWN
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x000002F0 | trm_hw_status0
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x004D2A06 | branchlink2
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x004C92BE | interruptlink1
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x004C92BE | interruptlink2
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00011F5A | data1
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x01000000 | data2
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | data3
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | beacon time
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00025C2A | tsf low
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | time gp1
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0003106E | time gp2
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0000004D | uCode version major
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0xF92B5FED | uCode version minor
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000370 | hw version
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00480002 | board version
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x807DFF00 | hcmd
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00020000 | isr0
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr1
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x48F04002 | isr2
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00C3000C | isr3
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr4
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00230148 | last cmd Id
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00011F5A | wait_event
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000018 | lmpm_pmg_sel
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | timestamp
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00002048 | flow_handler
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | ADVANCED_SYSASSERT
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink2
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink1
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac data1
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac data2
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac data3
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac major
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac minor
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | frame pointer
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | stack pointer
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | last host cmd
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: IML/ROM dump:
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00004FA3 | IML/ROM data1
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: Fseq Registers:
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x80330000 | FSEQ_TOP_INIT_VERSION
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00010009 | FSEQ_CNVIO_INIT_VERSION
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0xFFB23B89 | FSEQ_TOP_CONTENT_VERSION
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x01300202 | FSEQ_CNVR_ID
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00010009 | FSEQ_PREV_CNVIO_INIT_VERSION
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00330000 | FSEQ_WIFI_FSEQ_VERSION
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00330000 | FSEQ_BT_FSEQ_VERSION
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: 0x00000118 | FSEQ_CLASS_TP_VERSION
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: UMAC CURRENT PC: 0x8047e450
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: LMAC1 CURRENT PC: 0xd0
janv. 09 09:45:51 steph-aspirea315510p kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
janv. 09 09:45:54 steph-aspirea315510p kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
janv. 09 09:46:24 steph-aspirea315510p systemd-coredump[1159]: Process 1060 (light-locker) of user 1000 dumped core.
Stack trace of thread 1060:
#0 0x00007f7acd82c83c n/a (libc.so.6 + 0x8e83c)
#1 0x00007f7acd7dc668 raise (libc.so.6 + 0x3e668)
#2 0x00007f7acd7c44b8 abort (libc.so.6 + 0x264b8)
#3 0x00007f7ace9f9044 n/a (libdbus-1.so.3 + 0xe044)
#4 0x00007f7acea208eb _dbus_warn_check_failed (libdbus-1.so.3 + 0x358eb)
#5 0x00007f7acea0f530 dbus_message_iter_append_basic (libdbus-1.so.3 + 0x24530)
#6 0x00007f7acea10996 dbus_message_append_args_valist (libdbus-1.so.3 + 0x25996)
#7 0x00007f7acea10bde dbus_message_append_args (libdbus-1.so.3 + 0x25bde)
#8 0x000055ccdfe8d4de n/a (light-locker + 0xb4de)
#9 0x00007f7ace9c811b g_type_create_instance (libgobject-2.0.so.0 + 0x3f11b)
#10 0x00007f7ace9add91 n/a (libgobject-2.0.so.0 + 0x24d91)
#11 0x00007f7ace9af387 g_object_new_with_properties (libgobject-2.0.so.0 + 0x26387)
#12 0x00007f7ace9b02ca g_object_new (libgobject-2.0.so.0 + 0x272ca)
#13 0x000055ccdfe8f010 n/a (light-locker + 0xd010)
#14 0x00007f7ace9c811b g_type_create_instance (libgobject-2.0.so.0 + 0x3f11b)
#15 0x00007f7ace9add91 n/a (libgobject-2.0.so.0 + 0x24d91)
#16 0x00007f7ace9af387 g_object_new_with_properties (libgobject-2.0.so.0 + 0x26387)
#17 0x00007f7ace9b02ca g_object_new (libgobject-2.0.so.0 + 0x272ca)
#18 0x000055ccdfe88372 n/a (light-locker + 0x6372)
#19 0x00007f7acd7c5cd0 n/a (libc.so.6 + 0x27cd0)
#20 0x00007f7acd7c5d8a __libc_start_main (libc.so.6 + 0x27d8a)
#21 0x000055ccdfe88be5 n/a (light-locker + 0x6be5)
Stack trace of thread 1079:
#0 0x00007f7acd8ac73d syscall (libc.so.6 + 0x10e73d)
#1 0x00007f7ace8f02f7 g_cond_wait (libglib-2.0.so.0 + 0xb32f7)
#2 0x00007f7ace8621b4 n/a (libglib-2.0.so.0 + 0x251b4)
#3 0x00007f7ace8caa8e n/a (libglib-2.0.so.0 + 0x8da8e)
#4 0x00007f7ace8c8a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5 0x00007f7acd82a9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007f7acd8ae7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 1084:
#0 0x00007f7acd8a0f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f7ace8f52b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007f7ace897b97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
#3 0x00007f7acdb8619c n/a (libgio-2.0.so.0 + 0x11219c)
#4 0x00007f7ace8c8a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5 0x00007f7acd82a9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007f7acd8ae7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 1080:
#0 0x00007f7acd8a0f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f7ace8f52b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007f7ace895162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x00007f7ace8951b2 n/a (libglib-2.0.so.0 + 0x581b2)
#4 0x00007f7ace8c8a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5 0x00007f7acd82a9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007f7acd8ae7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 1081:
#0 0x00007f7acd8a0f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f7ace8f52b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007f7ace895162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x00007f7acea7afde n/a (libdconfsettings.so + 0x5fde)
#4 0x00007f7ace8c8a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5 0x00007f7acd82a9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007f7acd8ae7cc n/a (libc.so.6 + 0x1107cc)
ELF object binary architecture: AMD x86-64
2 Likes
VT995
9 January 2024 13:56
13
Also getting black screen after this update. No amount of waiting or rebooting fixed the GUI. OS was running in the background as confirmed from timeshift running sync after boot, but no graphics. Had to rollback to pre-update through live image to get my PC working again.
1 Like
Hi Everybody,
First of all, I wish You my best wishes for 2024 and most of all, good health!
With this update, I modify my mkinitcpio.conf and remove the kms hook. I place plymouth hoot just after systemd or for those using base and udev after them.
That way, boot time is faster and no more flickering screen swith caused by kms hook.
I hope it help You!
Wish You well
1 Like
Hi Everybody,
After this update I am not able to boot Manjaro anymore. The display shows the following message:
mount: /openswap_keymount: no valid filesystem type specified.
/init: line 22: cryptsetup: not found
umount: can't umount openswap_keymount: Invalid argument
ERROR: resume: hibernation device "/dev/mapper/luks-...UUID1" not found
ERROR: device "/dev/mapper/luks-...UUID2" not found. Skipping fsck.
mount: /new_root: no valid filesystem type specified.
ERROR: Failed to mount "/dev/mapper/luks-...UUID2" on real root
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
Remarks: …UUID1 and …UUID2 are placeholders.
I can mount my LUKS encrypted drives in a live session and access all my files. But I don’t know how to fix this by myself.
Update: I rolled back to the stable branch and I am able to boot my system again.
1 Like
Alex24
9 January 2024 15:23
16
And yes, that good old glitch with NO WiFi is back! Wi-Fi does not start.
philm
9 January 2024 15:31
17
Check your /var/log/pacman.log to see what acutally got updated. Does it still work normally with 6.1.x kernels?
What changes are those and what warnings are needed to be noted?
Well, we need to know more about your system. Mesa in combination with Plymouth might create issues. Here we have updated both.
Posting me-too responses might not help. There are known issues with Intel and Nvidia based GPUs and Mesa 23.3.x series. That is why I decided to downgrade Mesa to 23.1.9 again. sudo pacman -Syuu will adjust that.
You to. let me know what hardware you have GPU wise.
kms might be the issue with mesa , plymouth and systemd compared on some Intel and Nvidia GPUs. However also AMD graphic cards might have issues. We had kms not enabled for a long time due to some known issues. More info about KMS here: Kernel mode setting - ArchWiki
2 Likes
Alex24
9 January 2024 15:51
18
Rolled back finally. Timeshift helped to solve all the problems. No more booting problems, and WiFi is back. I’d rather wait till the next update.
I managed to fixed it. For some reason the hook “plymouth-encrypt” does not exist anymore after the upgrade. I noticed that the hook “encrypt” exist. So I replaced plymouth-encrypt with encrypt.
In my case it appears to be plymouth that is causing the failure to boot. Editing grub linux line to remove “quiet” and add “3” resulted in the boot process halting at
:: running hook [plymouth]
I downgraded plymouth:
sudo pacman -U /var/cache/pacman/pkg/plymouth-22.02.122-15-x86_64.pkg.tar.zst
and then could boot normally even with the updated mesa. I have an AMD cpu and Nvidia gpu.
MrKiu
9 January 2024 18:34
21
Hi,
I have both AMD GPU and CPU, running on 6.7 kernel and mesa 23.3.2
I realize now that with updated plymouth, boot splashscreen was not displayed at all.
1 Like
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.
2024-01-08
Due to various issues including non working backlights on some machines, the NVIDIA 545 series feature branch drivers have been downgraded to the 535 series production branch drivers.