No image after NVIDIA update

System:
  Kernel: 6.9.3-nitrous+ arch: x86_64 bits: 64 compiler: clang v: 17.0.6
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-nitrous
    root=UUID=28737c36-a0e2-4c06-a15d-60f83ad584f9 rw rootflags=subvol=@
    quiet loglevel=3 ibt=off
    resume=/dev/disk/by-uuid/45bcf8fd-50cc-44d3-add4-8a3586b06983 lvm
    nvidia-drm.modeset=1 nvidia_drm.fbdev=1
    NVreg_PreserveVideoMemoryAllocations=1 apparmor=1 security=apparmor
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm4 v: 4.18.0
    with: xfce4-panel tools: light-locker avail: xautolock vt: 7 dm: LightDM
    v: 1.32.0 Distro: Arch Linux
Machine:
  Type: Desktop System: MSI product: MS-7922 v: 2.0
    serial: <superuser required>
  Mobo: MSI model: Z97S SLI Krait Edition (MS-7922) v: 2.0
    serial: <superuser required> uuid: <superuser required>
    UEFI: American Megatrends v: 10.4 date: 04/15/2015
Battery:
  Device-1: sony_controller_battery_a0:5a:5d:51:d7:87 model: N/A serial: N/A
    charge: N/A status: full
CPU:
  Info: model: Intel Core i5-4690K bits: 64 type: MCP arch: Haswell
    gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
    family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 895 high: 1183 min/max: 800/4000 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 800 2: 1183 3: 800
    4: 800 bogomips: 28011
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow 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: disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: ASUSTeK driver: nvidia
    v: 550.78 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current
    (as of 2024-04; EOL~2026-12-xx) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-2019 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-I-1
    bus-ID: 01:00.0 chip-ID: 10de:1401 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
    compositor: xfwm4 v: 4.18.0 driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
    s-diag: 583mm (22.95")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled
    model: LG (GoldStar) M227WDP serial: <filter> built: 2009 res: 1920x1080
    hz: 60 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
    diag: 551mm (21.7") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 960/PCIe/SSE2
    memory: 1.95 GiB
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: Intel 9 Series Family HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
    class-ID: 0403
  Device-2: NVIDIA GM206 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0fba class-ID: 0403
  API: ALSA v: k6.9.3-nitrous+ status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.7 status: active with: 1: pipewire-media-session
    status: active 2: pw-jack type: plugin tools: pw-cat,pw-cli
  Server-3: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl,pavucontrol
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A
    mac: <filter>
  IF-ID-2: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-5:2
    chip-ID: 0a12:0001 class-ID: e001
  Report: bt-adapter note: tool can't run ID: hci0 rfk-id: 0 state: down
    bt-service: disabled rfk-block: hardware: no software: yes address: N/A
Drives:
  Local Storage: total: 2.04 TiB used: 1.79 TiB (87.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: WALRAM model: 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: V0523B0 temp: 47.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 model: 240GB size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 0E scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD10JPCX-24UE4T0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 1A01 scheme: GPT
Partition:
  ID-1: / raw-size: 39.28 GiB size: 39.28 GiB (100.00%)
    used: 32.01 GiB (81.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 151 MiB size: 148.6 MiB (98.44%)
    used: 10.1 MiB (6.8%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 876.07 GiB size: 876.07 GiB (100.00%)
    used: 809.6 GiB (92.4%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
  ID-4: /var/log raw-size: 39.28 GiB size: 39.28 GiB (100.00%)
    used: 32.01 GiB (81.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 39.28 GiB size: 39.28 GiB (100.00%)
    used: 32.01 GiB (81.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: zram size: 8 GiB used: 7.3 GiB (91.2%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 16.02 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p4 maj-min: 259:4
Sensors:
  System Temperatures: cpu: 60.5 C mobo: 35.0 C gpu: nvidia temp: 54 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 1011 fan-3: 0 fan-4: 1666 fan-5: 0
    gpu: nvidia fan: 26%
Info:
  Memory: total: 16 GiB available: 15.55 GiB used: 13.02 GiB (83.7%)
  Processes: 323 Power: uptime: 5h 0m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.16 GiB services: upowerd,xfce4-power-manager
    Init: systemd v: 255 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1607 libs: 438 tools: pamac,paru Compilers:
    clang: 17.0.6 gcc: 14.1.1 Shell: fish v: 3.7.1 running-in: xfce4-terminal
    inxi: 3.3.34

Updating nvidia driver to 550.90.07-1 gives black screen with cursor blinking next reboot.
I’ve try updating to beta (nvidia-beta-dkms 555.52.04-1) and same result after reboot
Last know working version it’s 550.78-1

Do you get the same result if you install and use a different kernel?

4 Likes

Yes, with linux-hardened 6.9.3.hardened1-1
Updating doesn’t appear any kind of error, appears all successful (but I know how it’s nvidia with open-source)

What logs are needed?
In /var/log/.boot.log I have
[e[0;32m OK e[0m] Set up automount e[0;1;39mArbitrary Executable File Formats File System Automount Pointe[0m.

     Expecting device e[0;1;39m/dev/disk/by-uuid/28737c36-a0e2-4c06-a15d-60f83ad584f9e[0m...


     Expecting device e[0;1;39m/dev/disk/by-uuid/45bcf8fd-50cc-44d3-add4-8a3586b06983e[0m...


     Expecting device e[0;1;39m/dev/disk/by-uuid/504c295f-edd1-443d-957b-081351ab4913e[0m...


     Expecting device e[0;1;39m/dev/disk/by-uuid/75f488a3-d525-45cd-b70d-fee007dd185ae[0m...


     Expecting device e[0;1;39m/dev/disk/by-uuid/927a6b8a-7b57-465e-8b31-d7bd6a06e188e[0m...


     Expecting device e[0;1;39m/dev/disk/by-uuid/F1A5-EA6Ae[0m...


     Expecting device e[0;1;39m/dev/disk/by-uuid/a8dd36a6-0a10-420f-87b3-172ba0caa9c0e[0m...


     Expecting device e[0;1;39m/dev/disk/by-uuid/d291b139-fca9-465a-8277-70a7c7181052e[0m...


     Expecting device e[0;1;39m/dev/zram0e[0m...
[e[0;32m  OK  e[0m] Listening on e[0;1;39mD-Bus System Message Bus Sockete[0m.


[e[0;1;31mFAILEDe[0m] Failed to listen on e[0;1;39mGnuPG network certificate management daemon for /etc/pacman.d/gnupge[0m.


See 'systemctl status [email protected]' for details.


[e[0;1;31mFAILEDe[0m] Failed to listen on e[0;1;39mGnuPG cryptographic agent and passphrase cache (access for web browsers) for /etc/pacman.d/gnupge[0m.


See 'systemctl status [email protected]' for details.


[e[0;1;31mFAILEDe[0m] Failed to listen on e[0;1;39mGnuPG cryptographic agent and passphrase cache (restricted) for /etc/pacman.d/gnupge[0m.


See 'systemctl status [email protected]' for details.


[e[0;1;31mFAILEDe[0m] Failed to listen on e[0;1;39mGnuPG cryptographic agent (ssh-agent emulation) for /etc/pacman.d/gnupge[0m.


See 'systemctl status [email protected]' for details.


[e[0;1;31mFAILEDe[0m] Failed to listen on e[0;1;39mGnuPG cryptographic agent and passphrase cache for /etc/pacman.d/gnupge[0m.


See 'systemctl status [email protected]' for details.


[e[0;1;31mFAILEDe[0m] Failed to listen on e[0;1;39mGnuPG public key management service for /etc/pacman.d/gnupge[0m.


See 'systemctl status [email protected]' for details.
/log> systemctl status [email protected]
â—Ź [email protected] - GnuPG network certificate management daemon for /etc/pacman.d/gnu>
     Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
     Active: active (listening) since Mon 2024-06-10 15:20:56 BST; 7h ago
   Triggers: â—Ź [email protected]
       Docs: man:dirmngr(8)
     Listen: /etc/pacman.d/gnupg/S.dirmngr (Stream)
     CGroup: /system.slice/system-dirmngr.slice/[email protected]
/log> systemctl status [email protected]
â—Ź [email protected] - GnuPG cryptographic agent and passphrase cache for /etc/pacman.>
     Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
     Active: active (listening) since Mon 2024-06-10 15:20:56 BST; 7h ago
   Triggers: â—Ź [email protected]
       Docs: man:gpg-agent(1)
     Listen: /etc/pacman.d/gnupg/S.gpg-agent (Stream)
     CGroup: /system.slice/system-gpg\x2dagent.slice/[email protected]
log> systemctl status [email protected]
â—Ź [email protected] - GnuPG public key management service for /etc/pacman.d/gnupg
     Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
     Active: active (listening) since Mon 2024-06-10 15:20:56 BST; 7h ago
   Triggers: â—Ź [email protected]
     Listen: /etc/pacman.d/gnupg/S.keyboxd (Stream)
     CGroup: /system.slice/system-keyboxd.slice/[email protected]
File: /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>                             <mount point>           <type>  <options>                                                                                                     <dump> <pass>
UUID=F1A5-EA6A                              /boot/efi               vfat    defaults,noatime,umask=0077,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,utf8,errors=remount-ro       0      2
UUID=a8dd36a6-0a10-420f-87b3-172ba0caa9c0   /home                   btrfs   subvol=/@home,defaults,noatime,space_cache=v2,ssd_spread,discard=async,compress=zstd                            0      1
UUID=28737c36-a0e2-4c06-a15d-60f83ad584f9   /                       btrfs   subvol=/@,defaults,noatime,space_cache=v2,ssd_spread,discard=async,compress=zstd                                0      1
UUID=28737c36-a0e2-4c06-a15d-60f83ad584f9   /root                   btrfs   subvol=/@root,defaults,noatime,space_cache=v2,ssd_spread,discard=async,compress=zstd                            0      1
UUID=28737c36-a0e2-4c06-a15d-60f83ad584f9   /srv                    btrfs   subvol=/@srv,defaults,noatime,space_cache=v2,ssd_spread,discard=async,compress=zstd                             0      0
UUID=28737c36-a0e2-4c06-a15d-60f83ad584f9   /var/cache              btrfs   subvol=/@cache,defaults,noatime,space_cache=v2,ssd_spread,discard=async,compress=zstd                           0      0
UUID=28737c36-a0e2-4c06-a15d-60f83ad584f9   /var/log                btrfs   subvol=/@log,defaults,noatime,space_cache=v2,ssd_spread,discard=async,compress=zstd                             0      0
UUID=28737c36-a0e2-4c06-a15d-60f83ad584f9   /var/tmp                btrfs   subvol=/@tmp,defaults,noatime,space_cache=v2,ssd_spread,discard=async,compress=zstd                             0      0
tmpfs                                       /tmp                    tmpfs   defaults,noatime,mode=1777                                                                                      0      0
UUID=45bcf8fd-50cc-44d3-add4-8a3586b06983   none            swap    defaults,noatime,mode=1777,nofail                                                                               0      0
UUID=504c295f-edd1-443d-957b-081351ab4913   /media/hard/Bitcoin     btrfs   defaults,noatime,space_cache=v2,ssd_spread,discard=async,compress-force=zstd:1,nofail                   0      2
UUID=d291b139-fca9-465a-8277-70a7c7181052   /media/hard/Downloads   btrfs   defaults,noatime,space_cache=v2,ssd_spread,discard=async,compress-force=zstd:1,nofail                   0      2
UUID=927a6b8a-7b57-465e-8b31-d7bd6a06e188   /media/hard/Monero      xfs     defaults,noatime,discard,nofail                                                                     0      2
UUID=75f488a3-d525-45cd-b70d-fee007dd185a   /media/hard/1TB_WD      ext4    defaults,noatime,nofail                                                                                 0      2

Install the LTS kernel and headers, and see if you have a different result booting with that.

3 Likes

Same thing happened.
Even in CRLT+ALT+F2 doesn’t boot, x11 error.
Uninstalling the driver keeps not booting, only using snapshot rollback before pre-update, with snapshot pre-update also doesn’t boot :thinking:

What does the error exactly say? Take a picture of the screen if you don’t have any way to copy/paste the message.

xinit: giving up
xinit: unable to connect to X server: connection refused
xinit: server error
cat/home/hard/.local/share/xorg/Xorg.0.log
Open ACPI failed (/var/run/acpid.socket) (no such file or directory)
NVIDIA: Failed to initialize the NVIDIA kernel mode
(EE) No screens found

Linux-Nitrous
Linux-Hardened
LTS

Comparing same file with 2 nvidia driver versions, it crashs here:

 (==)Using system config directory "/usr/share/X11/xorg.conf.d"
 (==) ServerLayout "Layout0"

2nd LINE DOESN’T APPEAR IN NEW DRIVER VERSION

My screen is LG M227WDP

Delete this thread, it’s working

The essence of a forum is to share information to make it available to others.
Even when nothing special was done to fix a problem, perhaps it was a trivial configuration error, or the problem was self-resolved with an update, it is good to document it.
Others may have the same problem and need the same “solution”.

3 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.