Updated black screen with mouse no sddm

Issues & Assistance KDE
1

I updated and then rebooted I can get to tty3 and can run startx sucessfully. However there is just a black screen with mouse on tty1 after reboot

inxi -Fxxxza

System: Kernel: 5.14.6-1-cacule x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-cacule
root=UUID=00b33177-335b-466d-8a5b-e5bad5669f19 rw rootflags=subvol=@ quiet splash
rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 3 dm: startx
Distro: Garuda Linux base: Arch Linux
Machine: Type: Laptop System: Micro-Star product: GL65 9SE v: REV:1.0 serial: Chassis: type: 10
serial:
Mobo: Micro-Star model: MS-16U5 v: REV:1.0 serial: UEFI: American Megatrends
v: E16U5IMS.101 date: 07/02/2019
Battery: ID-1: BAT1 charge: 23.3 Wh (60.2%) condition: 38.7/51.6 Wh (75.1%) volts: 11.1 min: 10.9
model: MSI BIF0_9 type: Li-ion serial: N/A status: Unknown
CPU: Info: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Kaby Lake note: check
family: 6 model-id: 9E (158) stepping: A (10) microcode: EA cache: L2: 12 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62469
Speed: 2930 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 2930 2: 4276 3: 2829 4: 4183
5: 4161 6: 4149 7: 4199 8: 4180 9: 4200 10: 4095 11: 4203 12: 4180
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
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 generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Micro-Star MSI driver: i915
v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Micro-Star MSI driver: nvidia
v: 470.74 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1f11 class-ID: 0300
Device-3: Chicony HD Webcam type: USB driver: uvcvideo bus-ID: 1-13:3 chip-ID: 04f2:b695
class-ID: 0e02
Display: server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: intel,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
Monitor-1: eDP1 res: 1920x1080 hz: 120 dpi: 143 size: 340x190mm (13.4x7.5") diag: 389mm (15.3")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 21.2.2 direct render: Yes
Audio: Device-1: Intel Cannon Lake PCH cAVS vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Sound Server-1: ALSA v: k5.14.6-1-cacule running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.37 running: yes
Network: Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel port: 5000 bus-ID: 00:14.3
chip-ID: 8086:a370 class-ID: 0280
IF: wlo1 state: up mac:
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
driver: r8169 v: kernel port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: down mac:
IF-ID-1: virbr0 state: down mac:
Bluetooth: Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb v: 0.8
bus-ID: 1-14:5 chip-ID: 8087:0aaa class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 2 state: down bt-service: enabled,running rfk-block:
hardware: no software: yes address:
Drives: Local Storage: total: 1.38 TiB used: 282.47 GiB (20.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN520 SDAPNUW-512G-1032
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD
serial: rev: 20140000 temp: 46.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10JPVX-60JC3T0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400
serial: rev: 1A01 scheme: GPT
Partition: ID-1: / raw-size: 73.24 GiB size: 73.24 GiB (100.00%) used: 46.43 GiB (63.4%) fs: btrfs
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 546 KiB (0.2%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 73.24 GiB size: 73.24 GiB (100.00%) used: 46.43 GiB (63.4%) fs: btrfs
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 73.24 GiB size: 73.24 GiB (100.00%) used: 46.43 GiB (63.4%) fs: btrfs
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 73.24 GiB size: 73.24 GiB (100.00%) used: 46.43 GiB (63.4%) fs: btrfs
dev: /dev/nvme0n1p2 maj-min: 259:2
Swap: Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.47 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors: System Temperatures: cpu: 59.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 398 Uptime: 4m wakeups: 1 Memory: 15.47 GiB used: 3.12 GiB (20.2%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1751 lib: 533
Shell: fish v: 3.3.1 running-in: konsole inxi: 3.3.06

-- Journal begins at Thu 2021-05-06 09:18:20 CST, ends at Mon 2021-09-27 17:22:27 CST. --
Sep 27 17:08:04 jeremy-gl659se kernel: x86/cpu: SGX disabled by BIOS.
Sep 27 17:08:04 jeremy-gl659se kernel: 
Sep 27 17:08:06 jeremy-gl659se kernel: Bluetooth: hci0: command 0xfc01 tx timeout
Sep 27 17:08:11 jeremy-gl659se nmbd[4291]: [2021/09/27 17:08:11.821077,  0] ../../source3/nmbd/nmbd.c:902(main)
Sep 27 17:08:11 jeremy-gl659se nmbd[4291]:   nmbd version 4.15.0 started.
Sep 27 17:08:11 jeremy-gl659se nmbd[4291]:   Copyright Andrew Tridgell and the Samba Team 1992-2021
Sep 27 17:08:11 jeremy-gl659se smbd[4293]: [2021/09/27 17:08:11.862869,  0] ../../source3/smbd/server.c:1738(main)
Sep 27 17:08:11 jeremy-gl659se smbd[4293]:   smbd version 4.15.0 started.
Sep 27 17:08:11 jeremy-gl659se smbd[4293]:   Copyright Andrew Tridgell and the Samba Team 1992-2021
Sep 27 17:08:15 jeremy-gl659se kernel: Bluetooth: hci0: FW download error recovery failed (-110)
Sep 27 17:08:30 jeremy-gl659se sddm-helper[776]: pam_systemd(sddm-greeter:session): Failed to release session: Access denied
Sep 27 17:08:34 jeremy-gl659se nmbd[4291]: [2021/09/27 17:08:34.845797,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Sep 27 17:08:34 jeremy-gl659se nmbd[4291]:   *****
Sep 27 17:08:34 jeremy-gl659se nmbd[4291]: 
Sep 27 17:08:34 jeremy-gl659se nmbd[4291]:   Samba name server JEREMY-GL659SE is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1
Sep 27 17:08:34 jeremy-gl659se nmbd[4291]: 
Sep 27 17:08:34 jeremy-gl659se nmbd[4291]:   *****
Sep 27 17:09:26 jeremy-gl659se kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=6948 end=6949) time 148 us, min 1066, max 1079, scanline start 1064, end 1082
Sep 27 17:12:10 jeremy-gl659se kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=16905 end=16906) time 273 us, min 1066, max 1079, scanline start 1061, end 1096
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.115626,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116141,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (3) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.241, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116257,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (4) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.241, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116340,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (5) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.241, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116420,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (6) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se 
nmbd[4291]: [2021/09/27 17:13:30.116498,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (7) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.243, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116574,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (8) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116650,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (9) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.243, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116737,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (10) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116813,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (11) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.243, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116905,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (12) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.116983,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (13) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.243, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.117058,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (14) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.117135,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (15) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]: [2021/09/27 17:13:30.117213,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (16) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:13:30 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:18:12 jeremy-gl659se kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=40774 end=40775) time 260 us, min 1066, max 1079, scanline start 1064, end 1099
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.400397,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.241, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.400708,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (3) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.400898,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (4) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.243, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401003,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (5) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.243, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401085,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (6) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.243, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401163,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (7) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.243, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401241,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (8) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.241, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401316,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (9) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.241, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401393,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (10) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401491,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (11) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.241, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401568,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (12) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401647,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (13) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401723,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (14) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401799,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (15) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]: [2021/09/27 17:18:32.401874,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   query_name_response: Multiple (16) responses received for a query on subnet 192.168.1.160 for name WORKGROUP<1d>.
Sep 27 17:18:32 jeremy-gl659se nmbd[4291]:   This response was from IP 192.168.1.242, reporting an IP address of 192.168.1.243.
Sep 27 17:22:13 jeremy-gl659se kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=51281 end=51282) time 305 us, min 1066, max 1079, scanline start 1047, end 1086
1 Like
2

Assuming you've already read Computer doesn’t boot, boots to a black screen, or stops at a message , what's the output of

dkms status

and have you tried booting a different (standard) kernel?

Does SDDM load at any point, or if you press a few keys?

3 Likes
3 
dkms status
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/nvidia/465.24.02/source/dkms.conf does not exist.

sudo dkms autoinstall
[sudo] password for jeremy:
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/nvidia/465.24.02/source/dkms.conf does not exist.

Funny because I am using nvidia v: 470.74
Also seems as though linux-lts is working fine but linux-calcule is not. Even on linux-lts I still have the same dkms error. sddm only give me a mouse pointer and a black screen that is all. I cannot login or use any keys to further my process.

4

It looks like the nvidia DKMS driver got broken at some point - I'm wondering whether it hasn't built for linux-calcule?

I'd clean out all nvidia-dkms-related packages, then clean out /var/lib/dkms/nvidia/, then reinstall nvidia-dkms. With any luck it will resolve whatever broke with 465.24.02.

1 Like
5

Could you elaborate on "clean out"? Is this the following commands you would use?

sudo pacman -R nvidia-dkms
sudo pacman -Rns $(pacman -Qqtd)
sudo rm -rf  /var/lib/dkms/nvidia
sudo pacman -Syu nvidia-dkms
1 Like
6

Thankyou for your assistance. I really appreciate all advice. I tried the above with no resolve, still in the same place. Still have the same dkms errors as well. not sure how to proceed.

Edit: After Rolling back to last known configuration that was working I still have the same dkms error.

1 Like
7

Hmm... I wonder if this is a DKMS bug...

What's the output of ls -l /var/lib/dkms/* ?

8

this is on the rollback

ls -l /var/lib/dkms/*
.rw-r--r-- 6 root 12 Sep 20:32  /var/lib/dkms/dkms_dbversion

/var/lib/dkms/nvidia:
drwxr-xr-x  - root 30 Apr 12:32  465.24.02
drwxr-xr-x  - root 16 Aug 14:22  470.57.02
drwxr-xr-x  - root 22 Sep 11:11  470.63.01
drwxr-xr-x  - root 22 Sep 11:11  470.74
lrwxrwxrwx 35 root 22 Apr 09:56  kernel-5.11.11-zen1-1-zen-x86_64 -> 465.24.02/5.11.11-zen1-1-zen/x86_64
lrwxrwxrwx 32 root 21 Jul 08:16  kernel-5.13.2-1-cacule-x86_64 -> 470.57.02/5.13.2-1-cacule/x86_64
lrwxrwxrwx 32 root 16 Aug 14:23  kernel-5.13.9-2-cacule-x86_64 -> 470.63.01/5.13.9-2-cacule/x86_64
lrwxrwxrwx 32 root  2 Sep 09:22  kernel-5.14.0-4-cacule-x86_64 -> 470.63.01/5.14.0-4-cacule/x86_64
lrwxrwxrwx 32 root  9 Sep 08:25  kernel-5.14.2-3-cacule-x86_64 -> 470.63.01/5.14.2-3-cacule/x86_64
lrwxrwxrwx 29 root 22 Sep 11:11  kernel-5.14.6-1-cacule-x86_64 -> 470.74/5.14.6-1-cacule/x86_64
drwxr-xr-x  - root 16 Aug 14:23  original_module
9

Remove the old files and links, then try dkms status again,

sudo rm -fr 465.24.02 470.57.02 470.63.01 kernel-5.11.11-zen1-1-zen-x86_64 kernel-5.13.2-1-cacule-x86_64 kernel-5.13.9-2-cacule-x86_64 kernel-5.14.0-4-cacule-x86_64 kernel-5.14.2-3-cacule-x86_64
dkms status
sudo dkms autoinstall

Let me know what, if any, output there is from the last two commands.

10 
╭─jeremy@jeremy in /var/lib/dkms/nvidia🔒
╰─λ sudo rm -fr 465.24.02 470.57.02 470.63.01 kernel-5.11.11-zen1-1-zen-x86_64 kernel-5.13.2-1-cacule-x86_64 kernel-5.13.9-2-cacule-x86_64 kernel-5.14.0-4-cacule-x86_64 kernel-5.14.2-3-cacule-x86_64

╭─jeremy@jeremy in /var/lib/dkms/nvidia🔒 took 45ms
╰─λ dkms status
nvidia/470.74, 5.14.6-1-cacule, x86_64: installed

╭─jeremy@jeremy in /var/lib/dkms/nvidia🔒 took 252ms
╰─λ sudo dkms autoinstall
11

OK, so the driver is installed and DKMS is working. :partying_face:

If you're still getting a black screen with linux-calcule but linux-lts (5.10) works then it might just be an issue with the calcule kernel, so next would be to try linux-zen to make sure it's not related to kernel 5.14.

1 Like
12

I then ran Sudo pacman -Syyu and rebooted.

dkms status
nvidia/470.74, 5.14.6-1-cacule, x86_64: installed

Still have no sddm just a black screen with mouse.

1 Like
13 
sudo pacman -Syu linux-lts linux-lts-headers linux-zen linux-zen-headers

Now I have a black screen and mouse when I reboot from all three linux kernels.

dkms status
nvidia/470.74, 5.10.69-1-lts, x86_64: installed
nvidia/470.74, 5.14.6-1-cacule, x86_64: installed
nvidia/470.74, 5.14.8-zen1-1-zen, x86_64: installed
14

I did have an error a few days ago that I solved. Maybe unrelated idk. Everything worked well afterwards

configuration file "/var/lib/sddm/.config/sddm-greaterrc" not writable.

I solved with

sudo chown sddm:sddm /var/lib/sddm/.config -R
15

I'm just thinking what else I recently did (5 or 6 days ago)...
I installed sddm-wayland-git and plasma-wayland-session however i do not have a rollback to a previous state as this was seemless and working well until this last update.

16

This is probably a ridiculous suggestion, I am a Linux noob tbh but can I suggest that if you're connecting from your graphics card to your monitor with anything other than HDMI (DisplayPort for example), that you try connect via just a HDMI cable instead after these problems present themselves and see if that helps at all.

I know, silly suggestion but simple enough to just rule out.

I'm only mentioning it as I've noticed recently that nvidia drivers have (for me anyway) sometimes defaulted to ONLY display via HDMI cable rather than what I usually only use, DisplayPort. Presenting a black screen via the Displayport, sometimes with the mouse pointer showing (weird!) yet when I connect a HDMI cable, there's the proper display (yet sometimes also locked up/frozen).

Just a suggestion. I've only had this problem myself with newer kernels and latest Nvidia drivers, along with possibly also only when using SDDM.

1 Like
17

Hmm. It’s possible this needs a rebuild against some newer library. I’d revert that back to the standard sddm package.

1 Like
18

I ran sudo pacman -Syyu --ignore egl-wayland and all is well...

19

As a quick heads up, sddm-wayland-git is going to be replaced by sddm-git as their PKGBUILDs are the same and a merge request has been filed at the AUR. I added proper replaces to sddm-git so all you have to do is pressing yes to the replace prompt when updating :slight_smile:

3 Likes
20

I updated and sddm-git replaced sddm-wayland-git automatically. However I still have the black screen and mouse.

EDIT: updated again with sudo pacman -Syyu --ignore egl-wayland. sddm is working great!
I found Ver 1.1.8-1 breaks plasma wayland. Sounds like this may be a nvidia problem.

EDIT2: Perhaps not able to resolve until October 11. When new Nvidia Drivers V495 will be available in beta.

2 Likes