It’s currently in the unstable branch.
[Stable Update] 2021-06-07 - Kernels, Perl, Haskell, Tesseract, Cutefish, KDE, Nvidia
-> Running build hook: [sd-encrypt] ==> ERROR: file not found: `' -> Running build hook: [lvm2]
this promises no good for my next boot…
I find it unnerving how fragile initramfs has been lately
And I am not the first one: Mkinitcpio error related to sd-encrypt: ==> ERROR: file not found: `'
Please see this thread:
Downgrading cryptsetup made this error disappear.
Yes, downgrading did indeed help. But I did that on my own accord as grub led me to a blank screen.
Which means I had to chroot, predictably.
How about we don’t release broken cryptsetup to stable next time, please?
Downgraded my poll vote…
A post was split to a new topic: Unknown key of DEB_Arch_Extra.db.sig
I would like to confirm that the nvidia display port issue doesn’t affect my system. Mine GPU is an RTX 2080 and monitor is a Samsung U28E590 4K monitor. Hope it helps.
Belows are the system details:
System: Kernel: 5.10.41-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 parameters: initrd=\amd-ucode.img initrd=\intel-ucode.img initrd=\initramfs-5.10-x86_64.img zfs=zroot/manjaro/root rw bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash Desktop: KDE Plasma 5.21.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux Machine: Type: Desktop System: Micro-Star product: MS-7C37 v: 3.0 serial: <filter> Mobo: Micro-Star model: X570-A PRO (MS-7C37) v: 3.0 serial: <filter> UEFI: American Megatrends LLC. v: H.D4 date: 04/09/2021 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter> charge: 55% (should be ignored) rechargeable: yes status: Discharging Device-2: hidpp_battery_1 model: Logitech Wireless Mouse serial: <filter> charge: 55% (should be ignored) rechargeable: yes status: Discharging CPU: Info: 8-Core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3 family: 19 (25) model-id: 21 (33) stepping: 0 microcode: A201009 cache: L2: 4 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 121647 Speed: 2879 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2879 2: 2878 3: 2879 4: 3599 5: 2876 6: 2877 7: 2872 8: 2880 9: 2873 10: 3593 11: 2879 12: 2879 13: 2879 14: 2879 15: 2870 16: 2877 Vulnerabilities: Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP: always-on, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA TU104 [GeForce RTX 2080] vendor: Gigabyte driver: nvidia v: 465.31 alternate: nouveau,nvidia_drm bus-ID: 2d:00.0 chip-ID: 10de:1e82 class-ID: 0300 Device-2: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-2:3 chip-ID: 046d:0843 class-ID: 0102 serial: <filter> Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: nvidia display-ID: :0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 159 s-size: 613x352mm (24.1x13.9") s-diag: 707mm (27.8") Monitor-1: DP-0 res: 3840x2160 hz: 60 dpi: 161 size: 607x345mm (23.9x13.6") diag: 698mm (27.5") OpenGL: renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2 v: 4.6.0 NVIDIA 465.31 direct render: Yes Audio: Device-1: NVIDIA TU104 HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 2d:00.1 chip-ID: 10de:10f8 class-ID: 0403 Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI X570-A PRO driver: snd_hda_intel v: kernel bus-ID: 2f:00.4 chip-ID: 1022:1487 class-ID: 0403 Device-3: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-2:3 chip-ID: 046d:0843 class-ID: 0102 serial: <filter> Sound Server-1: ALSA v: k5.10.41-1-MANJARO running: yes Sound Server-2: JACK v: 0.125.0 running: no Sound Server-3: PulseAudio v: 14.2 running: yes Sound Server-4: PipeWire v: 0.3.28 running: yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel port: d000 bus-ID: 27:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: enp39s0 state: down mac: <filter> Device-2: Edimax Edimax AC1750 USB type: USB driver: 8814au bus-ID: 1-1:2 chip-ID: 7392:a833 class-ID: 0000 serial: <filter> IF: wlp42s0f1u1 state: up mac: <filter> RAID: Supported mdraid levels: raid1 Device-1: md127 maj-min: 9:127 type: mdraid level: mirror status: active size: 513.9 MiB Info: report: 2/2 UU blocks: 526272 chunk-size: N/A super-blocks: 1.0 Components: Online: 0: nvme0n1p1 maj-min: 259:2 size: 514 MiB 1: nvme1n1p1 maj-min: 259:5 size: 514 MiB Device-2: zbigdata type: zfs status: ONLINE level: linear size: 1.81 TiB free: 1.09 TiB allocated: 739 GiB Components: Online: N/A Device-3: zhome type: zfs status: ONLINE level: linear size: 464 GiB free: 338 GiB allocated: 126 GiB Components: Online: N/A Device-4: zroot type: zfs status: ONLINE level: mirror size: 920 GiB free: 852 GiB allocated: 68.4 GiB Components: Online: N/A Drives: Local Storage: total: raw: 4.09 TiB usable: 7.25 TiB used: 932.64 GiB (12.6%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: Force MP600 size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: EGFM13.0 temp: 34.9 C scheme: GPT ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Corsair model: Force MP600 size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: EGFM13.0 temp: 31.9 C scheme: GPT ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 1B6Q scheme: GPT ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DX002-2DV164 size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC41 scheme: GPT Partition: ID-1: / raw-size: N/A size: 891.24 GiB used: 68.36 GiB (7.7%) fs: zfs logical: zroot/manjaro/root ID-2: /boot raw-size: 512.9 MiB size: 511.9 MiB (99.80%) used: 72.5 MiB (14.2%) fs: vfat dev: /dev/md127p1 maj-min: 259:8 ID-3: /home raw-size: N/A size: 449.48 GiB used: 125.56 GiB (27.9%) fs: zfs logical: zhome/manjaro/home Swap: Kernel: swappiness: 60 (default) cache-pressure: 100 (default) ID-1: swap-1 type: partition size: 10 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme1n1p2 maj-min: 259:6 ID-2: swap-2 type: partition size: 10 GiB used: 0 KiB (0.0%) priority: -3 dev: /dev/nvme0n1p2 maj-min: 259:3 Sensors: System Temperatures: cpu: 38.9 C mobo: 33.0 C gpu: nvidia temp: 38 C Fan Speeds (RPM): fan-1: 986 fan-2: 2360 fan-3: 721 fan-4: 504 fan-5: 0 fan-6: 0 fan-7: 1229 gpu: nvidia fan: 0% Info: Processes: 659 Uptime: 9h 02m wakeups: 76 Memory: 15.62 GiB used: 8.21 GiB (52.6%) Init: systemd v: 247 tool: systemctl Compilers: gcc: 11.1.0 alt: 10 clang: 11.1.0 Packages: pacman: 1538 lib: 373 Shell: Bash v: 5.1.8 running-in: yakuake inxi: 3.3.04
Basically I’m just holding off since the new nvidia driver was recklessly dumped into production when it was a known issue in upstream since 4/20/2021 with no current fix although nvidia has replicated it and “is working on it.” While the actual problem is nvidia’s until they fix the problem in their driver, a known bad driver should have NEVER EVER been pushed into production until the fix was posted. The new driver provides no necessary functionality at all and just breaks systems that use display port.
You can go the fix it yourself route and upgrade and then manually compile the older driver that actually works if you want but that is a terrible way for the manjaro team to address what was just sloppy handling of a the production branch. Basically it seems like there are those on the manjaro team that don’t like nvidia and would rather try to make their “statements about how bad nvidia is” rather than run a proper production branch.
Hi Cheker, I can see the same on my journalctl output. Do you know any solution?
Not really, no. Specially considering no noticeable consequence comes from this.
I’m going to give it a couple of weeks and see what happens after both the kernel and the vbox packages get updated a few times. If the error persists, I might try unloading the module and see if file/folder sharing still works after it. I’m not in a hurry either way because A) as I said, sharing still works and B) my hypervisor of choice in Linux is KVM, VBox is just there as a backup.
No nvidia issues here. GTX1070 connected via DP to 27" wqhd 144hz with freesync.
I have the same monitor and DP cable connected and a RTX 2060 SUPER,
May I ask if your monitor is DP connected?
Yes. It’s connected via DisplayPort.
Neither simply entering
IGNORE_CC_MISMATCH=1 on the command line nor adding it to
/etc/environment before executing the dkms to compile the nvidia kernel modules worked for me.
I got the same error 2 or 10 return codes because of GCC version mismatch.
The installation of the 5.10 kernel as suggested by @GokuSan ([Stable Update] 2021-06-07 - Kernels, Perl, Haskell, Tesseract, Cutefish, KDE, Nvidia - #81 by GokuSan) didn’t work either. Same problem: GCC version check failed
What worked for me:
gcc to the version, with which the kernel (in my case 5.4) had been compiled. Which was 10.2.x and had been upgraded to 11.1.x during the updates.
For the downgrade I used this here: Downgrading packages - Manjaro
The tricky bit with using
downgrade was: I had to specify both
gcc-libs at the same time, because
downgrade apparently isn’t able to handle the dependencies on its own:
downgrade gcc gcc-libs
downgrade gcc on its own did NOT work.
(I did not choose to add the packages to the ignore list so they should be included in the next updates I do.)
After the downgrade the dkms compile worked all fine like this:
dkms install --no-depmod -m nvidia -v 340.108 -k 5.4.123-1-MANJARO
Or you can try this which might be less hassle: [Stable Update] 2021-06-07 - Kernels, Perl, Haskell, Tesseract, Cutefish, KDE, Nvidia - #128 by eph
You might try this: [Stable Update] 2021-06-07 - Kernels, Perl, Haskell, Tesseract, Cutefish, KDE, Nvidia - #128 by eph
If the above doesn’t work for you, maybe try temporarily downgrading gcc like this: [Stable Update] 2021-06-07 - Kernels, Perl, Haskell, Tesseract, Cutefish, KDE, Nvidia - #128 by eph
Glad you solved it temporarily.
I already have both 5.4 and 5.10 working with gcc 11.1 and nvidia-340-xx. I made backup with timeshift in case something unexpected happens.
I hope the next update runs smooth.
This worked for me (dkms nvidia340xx, booted into linux510 built with gcc10) permanently without rebooting after the update borked linux54 and linux510 by building with gcc11.Using pamac:
- remove (broken) linux54&headers
- downgrade gcc&gcc-lib to 10
- reinstall linux54&headers (built with gcc10)
No dkms errors?
- reboot into linux54 (built with gcc10)
- remove (broken) linux510&headers
- reboot into linux54 (built with gcc10)
- remove the downgrade entry for gcc&gcc-lib and update to gcc11
- install linux510&headers
No dkms errors?
- reboot into linux510 (built with gcc11)
- remove linux54&headers (built with gcc10)
- reboot into linux510 (built with gcc11)
- install linux54&headers (built with gcc11)
No dkms errors?
You can again reboot into both kernels (built with gcc11)!
Thanks GokuSan and eph, great work.