[Stable Update] 2023-12-01 - Kernels, NVIDIA, Thunderbird, Deepin, PipeWire 1.0, QEMU

A post was split to a new topic: Optimus-manager.startup=nvidia: command not found

After the update I saw the following.

==> ERROR: module not found: ā€˜nvme2ā€™
==> WARNING: errors were encountered during the build. The image may not be complete.

This also happens after manually running sudo mkinitcpio -P for all my kernels that I have installed (LTS 6.1 and LTS 6.6).

Do I miss something? It still boots fine thoughā€¦ for now ;).

The PGP signatures for the kernel packages, and even all packages, seem to be broken.

From Manjaro Settings, when trying to install the 6.6 kernel:

linux66-6.6.3-1-x86_64 downloading...
 linux66-nvidia-545.29.06-8-x86_64 downloading...
checking keyring...
checking package integrity...
:: File /var/cache/pacman/pkg/linux66-6.6.3-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
:: File /var/cache/pacman/pkg/linux66-nvidia-545.29.06-8-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: linux66: signature from "Manjaro Build Server <build@manjaro.org>" is unknown trust
Errors occurred, no packages were upgraded.
error: linux66-nvidia: signature from "Manjaro Build Server <build@manjaro.org>" is unknown trust
error: failed to commit transaction (invalid or corrupted package (PGP signature))

Trying to (re)install any package also causes errors regarding unknown trust. Trying to refresh or repopulate keys also doesnā€™t work:

āÆ sudo pacman-key --refresh-keys
gpg: error reading key: No public key
gpg: key F296BDE50368C6CE: "T.J. Townsend <blakkheim@archlinux.org>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
pub   ed25519 2022-08-08 [SC]
      54C1FD273361EA514A237793F296BDE50368C6CE
uid           [ unknown] T.J. Townsend <blakkheim@archlinux.org>
sub   ed25519 2022-09-04 [SA]
sub   cv25519 2022-08-08 [E]

gpg: key A6234074498E9CEE: "Christian Hesse <eworm@archlinux.org>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
pub   rsa2048 2011-08-12 [SC]
      02FD1C7A934E614545849F19A6234074498E9CEE
uid           [ unknown] Christian Hesse <eworm@archlinux.org>
sub   rsa2048 2011-08-12 [E]
sub   ed25519 2019-08-29 [S]
sub   cv25519 2019-08-29 [E]

gpg: error retrieving 'build@manjaro.org' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key 279E7CF5D8D56EC8: "Manjaro Build Server <build@manjaro.org>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

āÆ sudo pacman-key --populate archlinux manjaro
==> ERROR: There is no secret key available to sign with.
==> Use 'pacman-key --init' to generate a default secret key.

āÆ sudo pacman-key --init
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/FB16E095594E1F57FA036AD9357F6022944466E6.rev'
gpg: Done
==> Updating trust database...
gpg: public key of ultimately trusted key 9C6B0359C4037DD4 not found
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   2  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 2u
==> ERROR: Trust database could not be updated.

EDIT:
I found a solution in completely refreshing the keys, as is described here

1 Like

Bricked my whole setup yesterday evening.

Had to rollback a Timeshift backup, from before the last update. Everything was back in working order after the rollback.

Updating to Kernel 6.6 and latest nvidia driver 545, results in:

  • Cinnamon buggy, crashes, locks up, etcā€¦
  • No BLE, Wifi nor Ethernet
  • Even the reboot command in CLI mode using ctrl+alt+f2 getā€™s stuck.

Additional info and issues:

  • I updated my system to kernel 6.6 about two weeks ago. This resulted in my monitors not always turning on, when I woke my system from sleep. So I rolled back to kernel 6.1 about one week later.
  • Yesterday I got a kernel panic during boot, after updating the nvidia drivers without updating the kernel. (Had to use Live usb to recover with Timeshift).
  • Updating appstream 0.16.4-1 to 1.0.0-5, locks up pamac (graphical pacman alternative).
  • Updating libadwaita 1:1.4.0-1 to 1:1.4.0-2, results in the same issue as the appstream update.

Hope the info helps debugging the problem. Thought it could be my old GTX980, not playing well with the new drivers. But the last update causes no issues on my old Asus zenbook with an GT310M insideā€¦ My main system has a R9 5900X and GTX980 GPU + 64GB DDR4 and 3 nvme drivesā€¦

1 Like

Hello everybody. I encountered a Problem with Kernel 6.6.3-1 and nouveau drivers on:

Graphics:
  Device-1: NVIDIA GT218 [GeForce 210] vendor: Micro-Star MSI N210
    driver: nouveau v: kernel arch: Tesla pcie: speed: 2.5 GT/s lanes: 16 ports:
    active: VGA-1 empty: DVI-I-1,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:0a65
    class-ID: 0300 temp: 54.0 C
  Display: x11 server: X.Org v: 21.1.9 compositor: kwin_x11 driver: X:
    loaded: modesetting alternate: fbdev,vesa dri: nouveau gpu: nouveau
    display-ID: :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: VGA-1 model: Samsung S23B550 serial: H4MCB01752 res: 1920x1080
    hz: 60 dpi: 96 size: 510x287mm (20.08x11.3") diag: 585mm (23") modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 egl: 1.4
    drv: nouveau device: 1 drv: swrast gbm: egl: 1.4 drv: nouveau surfaceless:
    egl: 1.4 drv: nouveau x11: egl: 1.4 drv: nouveau inactive: wayland
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 23.1.9-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: NVA8 device-ID: 10de:0a65
  API: Vulkan Message: No Vulkan data available.
Error: unknown Command 0x0400040.

Screen remains black with Mousearrow and not blinking curser on top left. Rolling back to 6.1.64-1 solves this problem.

Machine:

System:
  Host: rich-pc Kernel: 6.1.64-1-MANJARO arch: x86_64 bits: 64 compiler: gcc
    v: 13.2.1 clocksource: tsc Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: P5Q v: Rev 1.xx
    serial: <superuser required> BIOS: American Megatrends v: 2209
    date: 03/11/2010

edited for readability

1 Like

One curiosity which seems related to this update (as Iā€™ve never seen it before). On a couple of occasions my keyboard has become almost completely unresponsive. Logging out of Plasma then back in again fixes it, presumably because that restarts X.
I can still switch to a TTY using . I assume that three finger salute is handled at a lower-level than the X server.

Actually the issue is very strange. I am on lenovo legion slim 5 with amd 7840hs + amd780m and nvidia 4060. When the bios is set to dynamic graphics the system do not see the AMD gpu, and amdgpu kernel module is not loaded and I am able to boot only using nomodeset. When I switch to discrete graphics the system boots without nomodeset and sees Nvidia and AMD gpu but it detects laptop screen as connected to DP-2 and have another None-1-2 display. I am on KDE plasma.

on the other hand if I boot my system with latest kde iso with linux65 on dynamics graphics, the live system detects both GPUs and properly detects the screen as edP-1 and have all resolution options and settings. when I try to boot live system on discrete graphics it does not boot.

This was a brand new installation that was running fine with. 6.1.62 and previous nvidia 535 driver. I am running with vide-hybrid-amd-nvidia-prime.

Now that there is a newer production branch Nvidia driverā€¦ do you guys plan on adding that to the stable repo, or are you going to be staying on the new feature branch until the production branch goes to a 545 version?

Both Arch and Manjaro update to the new feature branch (currently 545) unless thereā€™s a newer production branch release (currently 535). There were issues with the initial 545 release, so we packaged 535 temporarily until the 545 bugfix was released.

1 Like