[Testing Update] 2023-03-11 - Kernels, Mesa 22.3.7, Phosh, LibreOffice 7.4.6

Announcements Testing Updates
,
1

Hello community,

Another testing branch update with some usual package updates for you.

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!
  • As you might have seen some of our team were able to attend FOSDEM 2023 and the conference proved to be incredibly productive for us. See our blog post for more.
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

image

Notable Package Updates:

  • Most of our Kernels got updated
  • Mesa is now at 22.3.7
  • Phosh got updated to 0.25.1. Also other parts of this mobile friendly UI got renewed.
  • With LibreOffice 7.4.6 more issues got solved
  • Usual KDE-git, Python and Haskell updates

Additional Info

Info about AUR packages

:warning: AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcement topics are off-topic and will be flagged, moved or removed without warning.

Info about GNOME 43

GNOME 43 is here! :partying_face:

New in Manjaro GNOME:

Lonely leftover orphan packages that have been removed from the Arch / Manjaro repositories:

  • adwaita-maia
  • dynamic-wallpaper-editor
  • firefox-gnome-theme-maia
  • gtkhash-nautilus
    (Not compatible with Nautilus 43)
  • manjaro-dynamic-wallpaper
  • manjaro-gdm-tweak
  • nautilus-terminal
    (Not compatible with Nautilus 43 & EOL)

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.277
  • linux54 5.4.236
  • linux510 5.10.174
  • linux515 5.15.102
  • linux61 6.1.19
  • linux62 6.2.6
  • linux515-rt 5.15.94_rt59
  • linux60-rt 6.0.5_rt14

Package Changes (Sat Mar 11 03:59:23 CET 2023 )

  • testing community x86_64: 433 new and 430 removed package(s)
  • testing core x86_64: 14 new and 13 removed package(s)
  • testing extra x86_64: 264 new and 268 removed package(s)
  • testing kde-unstable x86_64: 208 new and 208 removed package(s)
  • testing multilib x86_64: 9 new and 9 removed package(s)

A detailed 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)

0 voters

Check if your mirror has already synced:

5 Likes
2

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed

Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

:arrow_right: 2023-03-11

Possible kernel fs block code regression in 6.2.3 umounting usb drives

With kernel 6.2.3 when you simply plug in a usb external drive, mount it and umount it, then the journal has a kernel Oops. A bug report, that includes the journal output was submitted at. 217174 – Plugging in usb external drive, mount and umount causes kernel Oops Discussion can be found here: Re: Possible kernel fs block code regression in 6.2.3 umounting usb drives — Linux Stable Kernel Updates

kernel 5.15.99+ Black/empty screen during boot with i915 Intel gfx. No ways to do anything

Seems there is a regression introduced with 5.15.99 kernel update: [i915]drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_init+0xae/0x2d0 [i915] (#8284) · Issues · drm / i915 / kernel · GitLab. My thoughts here: [Testing Update] 2023-03-11 - Kernels, Mesa 22.3.7, Phosh, LibreOffice 7.4.6 - #31 by philm

2023-02-10

Switch to the base-devel meta package requires manual intervention

2023-02-12 - Robin Candau

On February 2nd, the base-devel package group has been replaced by a meta package of the same name.
If you installed the base-devel package group prior to this date, explicitly re-install it to get the new base-devel package installed on the system:

pacman -Syu base-devel

– Arch Linux - News: Switch to the base-devel meta package requires manual intervention

2023-01-17

Very slow shutdown when using KDE Plasma Wayland

The issue is sddm that can not be finished until the default timeout 90 sec.
The solution: Install sddm-git

The known bug reports:

PHP 8.2 update and introduction of legacy branch

2023-01-13 - Pierre Schmitz

The php packages have been updated to the latest version 8.2. In addition to this, a new set of php-legacy packages have been introduced. These will follow the oldest but still actively supported PHP branch. This enables users to install the latest version but also introduces the option to use third party applications that might rely on an older version. Both branches will be kept up to date following our rolling release model. php and php-legacy can be installed at the same time as the latter uses a -legacy suffix for its binaries and configuration files.

In addition to this, the php7 packages have been removed as they reached end of life. The imap extension will no longer be provided as it relies on the c-client library which has been abandoned for many years.

– Arch Linux - News: PHP 8.2 update and introduction of legacy branch

2023-01-04

Some games like Dota 2 are freezing

The issue is caused by update libx11 1.8.3-4
The solution: Upgrade to libx11 1.8.3-5

VLC crashes when playing a video file

It looks like there has been a regression introduced with the new version of libva (2.17.0), which is used by VLC media player. If you get the following error when executing vlc in a terminal:

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

you may try to change the Output option in Preferences > Video to VDPAU output instead of Automatic (or whatever value it had been set to before).

Downgrading the libva package from 2.17.0-1 to 2.16.0-1 may also work, but it is a more short-term workaround that should not be kept for too long, as sooner or later, the older package won’t be compatible with the other packages. Consider to do the solution above first.

2022-12-22

pacman-mirrors was temporarily renamed to manjaro-mirrors (the changes were reverted)

This was done to avoid confusion with an AUR / WSL package with the same name and avoid possible breakage. It should be a seamless transition.

Rename project (#183) · Issues · Applications / pacman-mirrors · GitLab

2022-12-19

KDE Wayland sometimes hangs with mesa 22.3.1 and AMD GPU

2022-12-16

dbus-x11 demoted to AUR

dbus-x11 was installed out of the box on some flavors of Manjaro as of a year ago, but is no longer needed. If you have it installed, please replace it with dbus using the following:

sudo pacman -Syu dbus
XFCE becomes unusable if libxfce4ui-nocsd is still installed

So far XFCE Classic project hasn’t updated yet to 4.18 series. We pushed 4.17.0 version of the package, but don’t know if that helps in that situation. It is recommended to install the regular libxfce4ui package to avoid issues and comment on this issue: libxfce4ui 4.18.0 released · Issue #15 · Xfce-Classic/libxfce4ui-nocsd · GitHub

2022-12-04

python-cairo 1.23.0-2 update requires manual intervention

The python-cairo package prior to version 1.23.0-2 was missing the compiled python module. This has been fixed in 1.23.0-2, so the upgrade will need to overwrite the untracked pyc file that was created. If you receive this error

python-cairo: /usr/lib/python3.10/site-packages/cairo/__pycache__/__init__.cpython-310.pyc exists in filesystem

when updating, use

pacman -Syu --overwrite /usr/lib/python3.10/site-packages/cairo/__pycache__/\*

to perform the upgrade.

2022-11-08

Pop Shell issues with Xorg session with Mutter 43.1 (fixed with mutter 43.1-1.0)

Gnome 43 (X11) GTK4 windows failed to render · Issue #1541 · pop-os/shell · GitHub

Window actors call update_stage_views() without allocation after non-interactive resize on X11 (#6054) · Issues · GNOME / gnome-shell · GitLab

2022-10-28

signature from "Manjaro Build Server <build_at_manjaro_dot_org>" is unknown trust

Seems our signing key for our Build Server had the 2022-10-28 as expire date set when generated. This is now fixed for chroot builds and fresh as also current existing installs via manjaro-keyring 20221028-4 Simply update your system to get that package, which got pushed to all our branches.

2022-10-27

Kernel 6.1-rc# might break backlight control on old/weird laptops

2022-10-18

Firefox 106.0 may have issues with screen sharing on GNOME with Wayland

2022-09-23

Nvidia 3060RTX cards may have issues with the 515.76 driver (fixed with 520.56.06)
Removing python2 from the repositories

2022-09-23 - Jelle van der Waa

Python 2 went end of life January 2020. Since then we have been actively cutting down the number of projects depending on python2 in our repositories, and we have finally been able to drop it from our distribution. If you still have python2 installed on your system consider removing it and any python2 package.

If you still require the python2 package you can keep it around, but please be aware that there will be no security updates. If you need a patched package please consult the AUR, or use an unofficial user repository.*

– Arch Linux - News: Removing python2 from the repositories

* Note: Unofficial user repositories are not supported

2022-08-27

Changes with Back In Time packages
  • backintime has been renamed to backintime-qt
  • backintime-cli has been renamed to backintime

After replacing backintime-cli with backintime, you will need to install backintime-qt manually if you want the Qt frontend installed again.

2022-08-23

electron12, electron13, electron14 & electron16 have been dropped to the AUR

Unsupported Electron packages have been dropped from the official repos to the AUR. They no longer receive security updates and nothing in the repos depend on them.

If you have AUR packages depending on those versions, install the binary version from the AUR to replace them; i.e., electron16-bin.

See FS#75490 - electron12, electron13, electron14, electron16 are unsupported and vulnerable packages

End of Support for 15.x.y and 16.x.y

Electron 15.x.y and 16.x.y has reached end-of-support. As per Electron’s new 8-week cadence, we were supporting the latest four versions of Electron until May 2022. With this Electron 19 release, we’ll return to supporting the latest three major versions, as well as the alpha, beta, and nightly releases.

Release electron v19.0.0 · electron/electron · GitHub

3

Continuing the discussion from [Testing Update] 2023-03-08 - Kernels, Wine, Systemd, KDE-Git, Python, Haskell:

I think I have seen these 17° thing since forever (I mean two years or something), now that I think about it, first time I saw it was in sensors output.

 omano  ~ $  sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +45.4 C  
Tccd1:        +43.0 C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8 C  (crit = +20.8 C)
temp2:        +16.8 C  (crit = +20.8 C)

gigabyte_wmi-virtual-0
Adapter: Virtual device
temp1:        +28.0 C  
temp2:        +45.0 C  
temp3:        +45.0 C  
temp4:        +15.0 C  
temp5:        +51.0 C  
temp6:        +57.0 C  

nvme-pci-0100
Adapter: PCI adapter
Composite:    +42.9 C  (low  =  -0.1 C, high = +86.8 C)
                       (crit = +89.8 C)
Sensor 1:     +42.9 C  (low  = -273.1 C, high = +65261.8 C)
4

Yes, my old AM4 motherboard has no issue and does not have the ACPI of PCT0 sensor. But my new motherboard has this PCT0.

The issue only affects thermal_zone1 in journalctl log.

You can see this thermal_zone1 is for PCTO in dmesg log.

Other ZT10 and UAD0 have no issue.

Maybe all current kernels don’t know about PCT0, this is why they forced my PC to shut down after waking up when PCTO is in critical condition (higher than 17°C after waking up from sleep?)

5

is it a gigabyte motherbaord ?
from mine

sensors
it8792-isa-0a60
Adapter: ISA adapter
in0:           1.78 V  (min =  +0.00 V, max =  +2.78 V)
in1:         676.00 mV (min =  +0.00 V, max =  +2.78 V)
in2:         992.00 mV (min =  +0.00 V, max =  +2.78 V)
+3.3V:         1.69 V  (min =  +0.00 V, max =  +2.78 V)
in4:           1.78 V  (min =  +0.00 V, max =  +2.78 V)
in5:           1.18 V  (min =  +0.00 V, max =  +2.78 V)
in6:           2.78 V  (min =  +0.00 V, max =  +2.78 V)  ALARM
3VSB:          1.68 V  (min =  +0.00 V, max =  +2.78 V)
Vbat:          1.56 V  
fan1:           0 RPM  (min =    0 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:         721 RPM  (min =    0 RPM)
temp1:        +38.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:        -55.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:        +35.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
intrusion0:  ALARM

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
temp2:        +16.8°C  (crit = +20.8°C)

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +47.6°C  
Tccd1:        +40.5°C
6

revert or apply patches
kernel 6.2
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.2.4

kernel 6.1
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.17

phoronix reveals the trouble

added ,
new versions kernels on all 5.x and 6.x series …
https://www.kernel.org/

8

After applying testing update 2023-03-11 my system seems to operate normally but it gets stuck on shutdown and reboot.
I get a lot of messages on the screen, only some of them i can find in the journal:

Mär 11 13:53:04 Peterputer kernel: #PF: supervisor read access in kernel mode
Mär 11 13:53:04 Peterputer kernel: #PF: error_code(0x0000) - not-present page
Mär 11 13:53:26 Peterputer kernel: NMI watchdog: Watchdog detected hard LOCKUP on cpu 6
Mär 11 13:53:26 Peterputer kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 6-...D } 6426 jiffies s: 693 root: 0x40/.
Mär 11 13:53:26 Peterputer kernel: rcu: blocking rcu_node structures (internal RCU debug):
Mär 11 13:53:33 Peterputer kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [khugepaged:122]
Mär 11 13:53:04 Peterputer systemd-coredump[7620]: Failed to connect to coredump service: Connection refused
Mär 11 13:53:04 Peterputer kernel: BUG: kernel NULL pointer dereference, address: 0000000000000028
Mär 11 13:53:04 Peterputer kernel: #PF: supervisor read access in kernel mode
Mär 11 13:53:04 Peterputer kernel: #PF: error_code(0x0000) - not-present page
Mär 11 13:53:26 Peterputer kernel: NMI watchdog: Watchdog detected hard LOCKUP on cpu 6
Mär 11 13:53:26 Peterputer kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 6-...D } 6426 jiffies s: 693 root: 0x40/.
Mär 11 13:53:26 Peterputer kernel: rcu: blocking rcu_node structures (internal RCU debug):
Mär 11 13:53:33 Peterputer kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [khugepaged:122]
Mär 11 13:53:04 Peterputer systemd-coredump[7620]: Failed to connect to coredump service: Connection refused
Mär 11 13:53:04 Peterputer kernel: BUG: kernel NULL pointer dereference, address: 0000000000000028
Mär 11 13:53:04 Peterputer kernel: #PF: supervisor read access in kernel mode
Mär 11 13:53:04 Peterputer kernel: #PF: error_code(0x0000) - not-present page
Mär 11 13:53:26 Peterputer kernel: NMI watchdog: Watchdog detected hard LOCKUP on cpu 6
Mär 11 13:53:26 Peterputer kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 6-...D } 6426 jiffies s: 693 root: 0x40/.
Mär 11 13:53:26 Peterputer kernel: rcu: blocking rcu_node structures (internal RCU debug):
Mär 11 13:53:33 Peterputer kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [khugepaged:122]

recovering system to a state just before update using timeshift resolves the problem.
my system specifications:

[peter@Peterputer ~]$ inxi -v7azy
System:
  Kernel: 6.2.3-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.2-x86_64
    root=UUID=fd6d419e-7fea-49a6-8d4e-5e3f2207d201 rw quiet
    udev.log_priority=3 iommu=pt vfio-pci.ids=10de:1380,10de:0fbc
    preempt=voluntary amd_pstate=passive
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel, cairo-dock
    wm: xfwm v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Manjaro Linux
    base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING B550M-PLUS v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 2423
    date: 08/10/2021
Battery:
  Message: No system battery data found. Is one present?
Memory:
  RAM: total: 27.21 GiB used: 2.72 GiB (10.0%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000C
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB
    desc: 1x16 MiB
  Speed (MHz): avg: 643 high: 4297 min/max: 400/5288 boost: enabled scaling:
    driver: amd-pstate governor: schedutil cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 4297 12: 400 13: 400 14: 400
    15: 400 16: 400 bogomips: 137655
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms extapic
    extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht
    hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni popcnt
    pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor
    svm svm_lock syscall tce topoext tsc tsc_scale umip v_spec_ctrl
    v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq wbnoinvd wdt
    xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: vfio-pci v: N/A
    alternate: nouveau non-free: 525.xx+ status: current (as of 2023-02)
    arch: Maxwell code: GMxxx process: TSMC 28nm built: 2014-19 pcie: gen: 1
    speed: 2.5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:1380 class-ID: 0300
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1 empty: DP-1
    bus-ID: 08:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 40.0 C
  Display: x11 server: X.Org v: 21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: BenQ G2420HDBL serial: <filter>
    built: 2010 res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2
    size: 477x268mm (18.78x10.55") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.7 renderer: AMD Radeon Graphics (renoir LLVM
    15.0.7 DRM 3.49 6.2.3-1-MANJARO) direct-render: Yes
Audio:
  Device-1: NVIDIA GM107 High Definition Audio [GeForce 940MX] driver: vfio-pci
    alternate: snd_hda_intel pcie: speed: Unknown lanes: 63 link-max: gen: 6
    speed: 64 GT/s bus-ID: 01:00.1 chip-ID: 10de:0fbc class-ID: 0403
  Device-2: AMD Renoir Radeon High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 08:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 08:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Sound API: ALSA v: k6.2.3-1-MANJARO running: yes
  Sound Interface: sndio v: N/A running: no
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.66 running: yes
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: bridge0 state: up speed: 1000 Mbps duplex: unknown mac: <filter>
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IP v6: <filter> scope: link
  IF-ID-2: virbr0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  WAN IP: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
    driver: btusb v: 0.8 bus-ID: 2-1.1:4 chip-ID: 0a12:0001 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.16 TiB used: 756.98 GiB (63.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 46.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1103 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Ultra USB 3.0
    size: 28.65 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-4: /dev/sdc maj-min: 8:32 type: USB model: USB 2.0 Flash Disk
    size: 1.89 GiB block-size: physical: 512 B logical: 512 B type: SSD
    serial: <filter> rev: 1100 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH10LS30 rev: 1.01
    dev-links: cdrom
  Features: speed: 40 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
  Optical-2: /dev/sr1 vendor: CDEmu model: CD-ROM rev: 1.0  dev-links: N/A
  Features: speed: 48 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 140.62 GiB size: 138.24 GiB (98.30%)
    used: 88.04 GiB (63.7%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
    label: Manjaro-Linux uuid: fd6d419e-7fea-49a6-8d4e-5e3f2207d201
  ID-2: /boot/efi raw-size: 200 MiB size: 196.9 MiB (98.45%)
    used: 150 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
    label: UEFI-NVME uuid: F80C-55AF
  ID-3: /home/<filter>/.mnt/Spiele_Lokales_usw raw-size: 790.69 GiB
    size: 777.22 GiB (98.30%) used: 622.88 GiB (80.1%) fs: ext4
    dev: /dev/nvme0n1p3 maj-min: 259:3 label: Spiele_Lokales
    uuid: 4b22c773-03e6-4020-93d1-5b4204bc9b8d
  ID-4: /home/<filter>/.mnt/Sys_Progs raw-size: 60 GiB size: 60 GiB (100.00%)
    used: 46.05 GiB (76.8%) fs: ntfs dev: /dev/sda3 maj-min: 8:3 label: Sys_Progs
    uuid: 01D590002CA52D80
  ID-5: /home/<filter>/.mnt/nfs/SV_Daten raw-size: N/A size: 104.21 GiB
    used: 26.36 GiB (25.3%) fs: nfs4 remote: 192.168.0.100:/SV-Daten
  ID-6: /home/<filter>/.mnt/nfs/Server raw-size: N/A size: 4.51 TiB
    used: 2.26 TiB (50.1%) fs: nfs4 remote: 192.168.0.100:/z_Server_komplett
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 3.4 GiB used: 0 KiB (0.0%) priority: 32767
    dev: /dev/zram0
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 300 MiB fs: vfat label: UEFI-SSD
    uuid: 0522-3A13
  ID-2: /dev/sda2 maj-min: 8:2 size: 29.7 GiB fs: ext4 label: Deb_Save
    uuid: ab6ca684-f85a-4eb6-a330-0e69e6b5f0d7
  ID-3: /dev/sda4 maj-min: 8:4 size: 95.92 GiB fs: ext4 label: Sys_Save
    uuid: dab078fe-fb8b-4f68-bab0-30d8a414aa75
  ID-4: /dev/sdb1 maj-min: 8:17 size: 28.62 GiB fs: exfat label: Ventoy
    uuid: 4072-A931
  ID-5: /dev/sdb2 maj-min: 8:18 size: 32 MiB fs: vfat label: VTOYEFI
    uuid: 440A-1007
  ID-6: /dev/sdc1 maj-min: 8:33 size: 1.89 GiB fs: vfat label: ASUS_MB
    uuid: 604A-4BF6
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 1-1:2 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    power: 500mA chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-6:3 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 16mA
    chip-ID: 0b05:1939 class-ID: 0300 serial: <filter>
  Hub-3: 1-7:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-8:5 info: Trust B.V. Optical Mouse type: Mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s
    power: 100mA chip-ID: 15d9:0a33 class-ID: 0301
  Hub-4: 2-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-5: 2-1:2 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    power: 100mA chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 2-1.1:4 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
    type: Bluetooth driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s
    power: 100mA chip-ID: 0a12:0001 class-ID: e001
  Device-2: 2-2:3 info: Silicon Motion - Taiwan (formerly Feiya ) Flash Drive
    type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 090c:1000 class-ID: 0806 serial: <filter>
  Hub-6: 3-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-7: 3-1:2 info: Genesys Logic hub ports: 4 rev: 3.0 speed: 5 Gb/s
    chip-ID: 05e3:0616 class-ID: 0900
  Hub-8: 4-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 4-1:2 info: Ortek IR receiver [VRC-1100 Vista MCE Remote Control]
    type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 1.5 Mb/s power: 100mA chip-ID: 05a4:9881 class-ID: 0300
  Device-2: 4-2:3 info: ThrustMaster T.Flight Stick X type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s power: 80mA
    chip-ID: 044f:b106 class-ID: 0300
  Hub-9: 5-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-10: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-11: 6-1:2 info: Genesys Logic Hub ports: 4 rev: 3.0 speed: 5 Gb/s
    chip-ID: 05e3:0612 class-ID: 0900
  Device-1: 6-1.4:3 info: SanDisk Ultra Flair type: Mass Storage
    driver: usb-storage interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 896mA
    chip-ID: 0781:5591 class-ID: 0806 serial: <filter>
Sensors:
  System Temperatures: cpu: 36.5 C mobo: 42.0 C gpu: amdgpu temp: 39.0 C
  Fan Speeds (RPM): fan-1: 0 fan-2: 323 fan-3: 0 fan-7: 0
Info:
  Processes: 368 Uptime: 23m wakeups: 0 Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
  pkgs: 2232 libs: 523 tools: pamac Shell: Bash v: 5.1.16
  running-in: xfce4-terminal inxi: 3.3.25
[peter@Peterputer ~]$
9

Cannot load firmware for Asus PCE-AC88 - Again!

Hi, kernel v6.2.3 does not like my Broadcom WiFi card, similar to the issue that I had in January - although this time it is has another cause…

Anyone has already stumbled upon that?
I’m going to ask in linux-wireless for help, but so far I couldn’t find any report there yet. I only saw this but still can’t say that it what I am experiencing…

10

it may come from Uefi motherboard

see version 2816

you need this ?

 preempt=voluntary
11

OK, the regression discussed on linux-wireless about broadcom actually prevents my raspis to connect…
I wonder if someone is reporting it on manjaro-arm…

12

I dont think so, this ASUS statement sounds like commercial blabla to me.
System is in use for about one and a half year now with manjaro testing and this problem is present since today (after current update) and can be resolved by rolling back to former state.
But anyway, the problem seems not to be kernel-related. Both installed kernels (6.2 and 6.1-lts) have this problem when trying to reboot or shutdown, both since current update.

preempt=voluntary was included by me a long time ago as one kernel-option to optimize performance for a virtual windows 10 installation with gpu-passthrough without problem, but i will try without this option.
After testing: does not solve anything

1 Like
13

more from from recent kernels

5 Likes
14

okay, that’s probably the bad guy, hopefully!

15

Just pushed 6.2.4-1 & 6.1.17-1.

6 Likes
16

I just swooped past the 6.2.3 and 6.1.17 release - just got 6.2.4 and 6.1.17 on unstable.

1 Like
17

for unstable version 6.2.5 & 6.1.19 ( all others series has been released )

18

The new point releases are building now. :wink:

6 Likes
19

G H for hotfix patch

4 Likes
20

Well, the wifi fix is coming … [pkg-upd] 6.2.5-1 (e66a84e7) · Commits · Packages / Core / linux62 · GitLab

3 Likes
22

Resolved by kernel update linux62 (6.2.3-1 → 6.2.4-1) and linux61 (6.1.16-1 → 6.1.17-1)
:smile_cat:

Thank you Yochanan for lightspeed reaction :+1: and stephane for finding the solution :+1: