link in OP is working now - https://manjaro.myspreadshop.net/
I had an issue after rebooting, I was greeted with a “Cannot load kernel modules” message, I then switched to a TTY and ran
sudo pacman -Syyu and I had another update for all my kernels and headers and rebooting afterwards fixed the issue. I guess there was an issue that has been caught too late and new kernels got pushed shortly after.
Or not up-to-date mirrors
I refresh mirror list, and force the Global mirrors so no I don’t think so.
sudo pacman-mirrors --country Global sudo pacman -Syyu
Can’t give me outdated mirrors.
I got kernel updates initially too, so that tends to confirm my guess. No I got modules updates but I think the kernels were not pushed initially. That’s weird.
Maybe mirror wasn’t properly synced but pacman-mirror was seeing it as up to date so it’s weird.
It hasn’t been released yet. The release date is set to 2021-10-14. Then allow up to week or even more until it reaches Manjaro Testing.
Everything went fine.
Is it just me, or have mirrors been upgraded? The download speeds went sky-high. I have fiber-internet, but even with the best mirrors set, the download speeds were pretty limited. Today it was super quick, 1GB update downloaded in ca. 10s as if mirrors became much more efficient and the whole update processed in super speed. 1 minute and it was all over. Wow!
It depends on the mirror you have.
I got this error when applying this update.
error: failed to synchronize all databases (no servers configured for repository)
I don’t know exactly when the mirrors list got deleted, but it’s probably from the last update, because I don’t remember executing any elevated command between that update and this one. I just need to update the mirror, tho. There is no apparent changes to the URL from the newly downloaded mirrors list. But the fact that it got deleted is kinda weird. I hope it’s nothing to worry about.
OK found what I was looking at. “KDE Gear 21.08.2 will be released on October 7”.
3 posts were split to a new topic: Kde gear vs plasma release misunderstanding
inxi now gives an error when running
inxi -Fxx with 2 or more of the “x” flag. It stops after displaying Bluetooth information and gives the error:
Not an ARRAY reference at /usr/bin/inxi line 16007.
If I just use
inxi -F or
inxi -Fx, it works as expected.
inxi -Fazy gives the same error.
It doesn’t for me.
If I’m reading the source correctly it’s got something todo with hardware raid info parsing (which my machine doesn’t have).
Better open up a bug report upstream:
My system follows the stable branch, but I do like to peak here to see what’s on the horizon from time to time… and I recall
inxi updated for me on the 11th to v3.3.07.1-1.
I understand my total installed package list is not in step, but on the off chance this is related to the same
inxi version (unless another inxi version was released after the 11th)… I just wanted to share that I had no issues between the
inxi -Fxx command (v3.3.07.1-1) and my mdadm array.
$ inxi -Fxx System: Host: AM4-5600X-Linux Kernel: 5.14.10-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux base: Arch Linux Machine: Type: Desktop System: Micro-Star product: MS-7C35 v: 2.0 serial: <superuser required> Mobo: Micro-Star model: MEG X570 UNIFY (MS-7C35) v: 2.0 serial: <superuser required> UEFI: American Megatrends LLC. v: A.80 date: 01/22/2021 CPU: Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3 rev: 0 cache: L2: 3 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 88834 Speed: 4360 MHz min/max: 2200/3700 MHz boost: enabled Core speeds (MHz): 1: 4360 2: 2393 3: 3544 4: 2878 5: 2875 6: 2886 7: 2202 8: 2198 9: 3023 10: 2862 11: 2878 12: 2877 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: XFX Limited XFX Speedster MERC 319 driver: amdgpu v: kernel bus-ID: 2f:00.0 chip-ID: 1002:73bf Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: amdgpu,ati unloaded: modesetting,radeon alternate: fbdev,vesa resolution: 1: 2560x1440~144Hz 2: 2560x1440~144Hz s-dpi: 96 OpenGL: renderer: AMD Radeon RX 6800 XT (SIENNA_CICHLID DRM 3.42.0 5.14.10-1-MANJARO LLVM 12.0.1) v: 4.6 Mesa 21.2.3 direct render: Yes Audio: Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel v: kernel bus-ID: 2f:00.1 chip-ID: 1002:ab28 Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 31:00.4 chip-ID: 1022:1487 Device-3: Corsair CORSAIR VIRTUOSO SE USB Gaming Headset type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-4:3 chip-ID: 1b1c:0a3d Sound Server-1: ALSA v: k5.14.10-1-MANJARO running: yes Sound Server-2: sndio v: N/A running: no Sound Server-3: JACK v: 1.9.19 running: no Sound Server-4: PulseAudio v: 15.0 running: yes Sound Server-5: PipeWire v: 0.3.38 running: yes Network: Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel port: f000 bus-ID: 27:00.0 chip-ID: 10ec:8125 IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: 2c:f0:5d:ae:5e:89 Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:2 chip-ID: 8087:0029 Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends RAID: Device-1: md127 type: mdraid level: mirror status: active size: 7.28 TiB Info: report: 2/2 UU blocks: 7813893120 chunk-size: N/A super-blocks: 1.2 Components: Online: 0: sdb1 1: sdc1 Drives: Local Storage: total: 19.33 TiB used: 8.18 TiB (42.3%) ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T1X0E-00AFY0 size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 serial: ######### temp: 40.9 C ID-2: /dev/nvme1n1 vendor: Western Digital model: WDS100T3X0C-00SJG0 size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: ######### temp: 37.9 C ID-3: /dev/nvme2n1 vendor: Western Digital model: WDS100T1X0E-00AFY0 size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 serial: ######### temp: 40.9 C ID-4: /dev/nvme3n1 vendor: Western Digital model: WDS200T2B0C-00PXH0 size: 1.82 TiB speed: 31.6 Gb/s lanes: 4 serial: ######### temp: 31.9 C ID-5: /dev/sda vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s serial: ######### ID-6: /dev/sdb vendor: Western Digital model: WD80EFAX-68KNBN0 size: 7.28 TiB speed: 6.0 Gb/s serial: ######### ID-7: /dev/sdc vendor: Western Digital model: WD80EFAX-68KNBN0 size: 7.28 TiB speed: 6.0 Gb/s serial: ######### Partition: ID-1: / size: 915.53 GiB used: 417.03 GiB (45.6%) fs: ext4 dev: /dev/nvme2n1p2 ID-2: /boot/efi size: 299.4 MiB used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme2n1p1 Swap: ID-1: swap-1 type: file size: 38 GiB used: 5.8 MiB (0.0%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: 37.8 C mobo: N/A gpu: amdgpu temp: 46.0 C mem: 44.0 C Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 Info: Processes: 356 Uptime: 1d 14h 29m Memory: 31.27 GiB used: 6.88 GiB (22.0%) Init: systemd v: 249 Compilers: gcc: 11.1.0 Packages: pacman: 1404 Shell: Bash v: 5.1.8 running-in: konsole inxi: 3.3.07
I can’t reproduce it. Run
inxi --recommends and see if you’re missing an optional dependency.
This update appears to have introduced an issue regarding pci ports on my laptop.
Kernel 5.14, intel+nvidia hybrid, running optimus-manager + bbswitch switching. Nvidia module is unloaded, running only on intel graphics.
Anytime anything which requires hardware acceleration (mpv for example) is called, dmesg is spammed with
[ 504.252426] pcieport 0000:00:1c.0: Data Link Layer Link Active not set in 1000 msec [ 504.252637] pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 504.276581] pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 504.295276] pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible)
for a few seconds until system appears to “give up”. A hard-crash due to this has already occured during the playback of a long list of files.
PCI device 0000:00:1c.0 is, according to lspci, the Intel PCI bridge
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
This problem appears to go even further down, as any attempt to load the nvidia driver fails. Modprobe claims
modprobe: ERROR: could not insert 'nvidia': No such device
while journalctl logs
kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509 kernel: NVRM: This is a 64-bit BAR mapped above 4GB by the system NVRM: BIOS or the Linux kernel, but the PCI bridge NVRM: immediately upstream of this GPU does not define NVRM: a matching prefetchable memory window. kernel: NVRM: This may be due to a known Linux kernel bug. Please NVRM: see the README section on 64-bit BARs for additional NVRM: information. kernel: nvidia: probe of 0000:01:00.0 failed with error -1 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). kernel: NVRM: None of the NVIDIA devices were initialized. kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 509
Any attempt to load the nvidia driver, either via optimus-manager or directly fails. Critical failure in optimus-manager appears to be due to the same issue, with logs outputting
Command 'modprobe nvidia NVreg_UsePageAttributeTable=1' returned non-zero exit status 1.
again a modprobe nvidia related issue.
Despite modprobing nvidia always failing with the specific error
modprobe: INFO: Failed to insert module '/lib/modules/5.14.11-1-MANJARO/extramodules/nvidia.ko.gz': No such device
modinfo returns the expected information
filename: /lib/modules/5.14.11-1-MANJARO/extramodules/nvidia.ko.gz firmware: nvidia/470.74/gsp.bin alias: char-major-195-* version: 470.74 supported: external (etc)
As expected, Testing branch is once again left over. Testing of the package was done on Unstable and Stable-Staging, then pushed to Stable.
It’s been a recurring issue in the past months, updates are tested on Stable-Staging and not on Testing branch, then pushed to Stable, at some point Stable was more on par with Unstable branch than Testing. What are you doing guys, can you try to find out why this is regularly occurring and try to avoid that?
I want to stay on Testing branch but at some point if the update scheme makes no sense I’ll go back to Stable and forget about testing updates before they land to Stable…
I received an update today and:
error: failed to commit transaction (conflicting files) hwinfo: /sbin exists in filesystem (owned by filesystem) /usr/share/systemsettings/categories/manjaro-category.desktop exists in both 'manjaro-settings-manager-kcm' and 'manjaro-settings-manager-knotifier' Errors occurred, no packages were upgraded. -> error installing repo packages
What branch are you using?
hwinfo 21.77-1 was the only version that would cause that which was never in the testing branch. We pushed 21.77-1.2 to unstable before Arch finally updated to 21.77-2.
I agree. It seems like they are just testing the updates in the stable-staging branch and skipping the testing branch. Sometimes, stable branch even has newer packages than testing.