External Thunderbolt displays crash kernels >4.19

Hey there,

I was running 5.4.23-1 through 5.4.27-1 without issue on my Thinkpad X1 Extreme Gen2, using an external Thunderbolt 3 dock with two attached DP monitors. However, after upgrading to 5.4.28-1, connecting both monitors to the dock causes KDE to crash and kick me back out to SDDM. Repeated login attempts result in full system lockup.

I've tried 5.5 and 5.6, both with no luck. 5.4.26-RT worked for a bit but then resulted in other issues -- the only reliable kernel I've found it 4.19 but that one doesn't like my Intel AX200 WiFi driver. Thankfully, I can get around that issue for the time being by just using my dock's Ethernet connection.

I've also tried pulling the 5.4.27-1 kernel and header packages out of my pacman cache and installing them manually, but I get boot failure when selecting that kernel in Grub after installing them that way. Personally, finding a way to reliably roll back to 5.4.27-1 would be my preferred solution as all of my hardware worked fine with that release.

Any suggestions on this? Any help you can offer would be appreciated!

Cheers,
Theo

More info regarding your system would be nice:

Probably because you did not downgrade modules and/or drivers (nvidia user by the looks of your profile).
Were there error messages? Which ones exactly?

@freggel.doe thanks for the reply -- my apologies for not including enough information the first time.

As of this post, I've attempted fully uninstalling 5.4.28 via the Kernel manager and re-installing 5.4.27-1 from the pacman cache, including the headers and nvidia drivers. On that attempt, I was able to boot in but my external monitors were not detected at all. I'm also running optimus-manager to enable the nvidia-440xx driver on boot and am not currently using any switching methods with it.

On 5.4.28-1, I still get the issue where KDE crashes back out to SDDM after attempting to log in. Below are some dmesg and journalctl outputs (grepped and scrubbed for user/host details) from a login I had to TTY2 during one of those boot attempts. Using pastebin because of the forum post character limit, hope that's ok.

5.4.28-1 dmesg
5.4.28-1 journalctl | grep sddm
5.4.28-1 journalctl | grep kde

For stability's sake, I've moved to running 4.19.113 to get by, but as stated before my wireless card is completely undetected on this version. Below are some outputs from this boot -- everything runs fine except for the wireless card. I'd like to be able to move back to 5.4 but honestly if I can get my wireless card working on 4.19 I'm fine with that for the time being. As far as I an tell, it's seeing the card but failing to load any kernel drivers for it.

4.19.113-1 inxi -Fxxxza --no-host
System:    Kernel: 4.19.113-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19-x86_64 root=UUID=c650d837-89a7-4a22-9761-97b05f63f77c rw quiet apparmor=1 
           security=apparmor resume=UUID=408b2d48-d58b-4a0f-958c-6818740b0a4e udev.log_priority=3 
           Desktop: KDE Plasma 5.18.3 tk: Qt 5.14.1 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Laptop System: LENOVO product: 20QVCTO1WW v: ThinkPad X1 Extreme 2nd serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: LENOVO model: 20QVCTO1WW v: SDK0J40697 WIN serial: <filter> UEFI: LENOVO v: N2OET41W (1.28 ) date: 11/25/2019 
Battery:   ID-1: BAT0 charge: 77.3 Wh condition: 80.9/80.4 Wh (101%) volts: 17.2/15.4 model: SMP 01YU911 type: Li-poly 
           serial: <filter> status: Unknown cycles: 7 
CPU:       Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Kaby Lake family: 6 model-id: 9E (158) 
           stepping: A (10) microcode: CA L2 cache: 12.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62208 
           Speed: 1505 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 806 2: 832 3: 801 4: 890 5: 864 6: 809 7: 813 8: 854 
           9: 841 10: 811 11: 801 12: 801 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           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: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel UHD Graphics 630 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3e9b 
           Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Lenovo driver: nvidia v: 440.64 bus ID: 01:00.0 
           chip ID: 10de:1f91 
           Display: x11 server: X.Org 1.20.8 driver: modesetting,nvidia compositor: kwin_x11 
           resolution: 1920x1200~60Hz, 1920x1200~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1650 with Max-Q Design/PCIe/SSE2 v: 4.6.0 NVIDIA 440.64 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:a348 
           Device-2: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo bus ID: 3-2.3.3:20 
           chip ID: 046d:082d serial: <filter> 
           Device-3: Lenovo USB2.0 Hub type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-2.1.1.2:9 
           chip ID: 17ef:3083 serial: <filter> 
           Sound Server: ALSA v: k4.19.113-1-MANJARO 
Network:   Device-1: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: 3.2.6-k port: efa0 bus ID: 00:1f.6 
           chip ID: 8086:15bc 
           IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Intel Wi-Fi 6 AX200 driver: N/A port: 2000 bus ID: 52:00.0 chip ID: 8086:2723 
           Device-3: Lenovo USB3.1 Hub type: USB driver: cdc_ether bus ID: 4-2.1.2:5 chip ID: 17ef:3082 serial: <filter> 
           IF: enp9s0u2u1u2c2 state: up speed: N/A duplex: N/A mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 207.14 GiB (22.2%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB block size: physical: 512 B 
           logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2B2QEXE7 scheme: GPT 
           ID-2: /dev/nvme1n1 vendor: Samsung model: MZVLB256HBHQ-000L7 size: 238.47 GiB block size: physical: 512 B 
           logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 4M2QEXH7 scheme: GPT 
Partition: ID-1: / raw size: 897.10 GiB size: 882.02 GiB (98.32%) used: 207.14 GiB (23.5%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: swap-1 size: 34.12 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default) cache pressure: 100 (default) 
           dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 66.0 C mobo: N/A gpu: nvidia temp: 45 C 
           Fan Speeds (RPM): cpu: 2405 
Info:      Processes: 264 Uptime: 2h 12m Memory: 31.06 GiB used: 6.11 GiB (19.7%) Init: systemd v: 244 Compilers: gcc: 9.3.0 
           alt: 8 Shell: bash v: 5.0.16 running in: yakuake inxi: 3.0.37 
4.19.113-1 lspci -k
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
        Subsystem: Lenovo 8th Gen Core Processor Host Bridge/DRAM Registers
        Kernel driver in use: skl_uncore
lspci: Unable to load libkmod resources: error -12
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
        Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
        Subsystem: Lenovo UHD Graphics 630 (Mobile)
        Kernel driver in use: i915
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
        Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem
        Kernel driver in use: proc_thermal
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
        Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
        Subsystem: Lenovo Cannon Lake PCH Thermal Controller
        Kernel driver in use: intel_pch_thermal
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
        Subsystem: Lenovo Cannon Lake PCH USB 3.1 xHCI Host Controller
        Kernel driver in use: xhci_hcd
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
        Subsystem: Lenovo Cannon Lake PCH Shared SRAM
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10)
        Subsystem: Lenovo Cannon Lake PCH Serial IO I2C Controller
        Kernel driver in use: intel-lpss
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
        Subsystem: Lenovo Cannon Lake PCH HECI Controller
        Kernel driver in use: mei_me
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0)
        Kernel driver in use: pcieport
00:1b.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0)
        Kernel driver in use: pcieport
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0)
        Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)
        Kernel driver in use: pcieport
00:1d.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #15 (rev f0)
        Kernel driver in use: pcieport
00:1e.0 Communication controller: Intel Corporation Cannon Lake PCH Serial IO UART Host Controller (rev 10)
        Subsystem: Lenovo Cannon Lake PCH Serial IO UART Host Controller
        Kernel driver in use: intel-lpss
00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
        Subsystem: Lenovo Device 229f
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
        Subsystem: Lenovo Cannon Lake PCH cAVS
        Kernel driver in use: snd_hda_intel
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
        Subsystem: Lenovo Cannon Lake PCH SMBus Controller
        Kernel driver in use: i801_smbus
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
        Subsystem: Lenovo Cannon Lake PCH SPI Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
        Subsystem: Lenovo Ethernet Connection (7) I219-V
        Kernel driver in use: e1000e
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)
        Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q]
        Kernel driver in use: nvidia
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
        Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
        Kernel driver in use: nvme
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
        Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
        Kernel driver in use: nvme
04:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
        Kernel driver in use: pcieport
05:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
        Kernel driver in use: pcieport
05:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
        Kernel driver in use: pcieport
05:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
        Kernel driver in use: pcieport
05:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
        Kernel driver in use: pcieport
06:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] (rev 06)
        Subsystem: Lenovo JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018]
        Kernel driver in use: thunderbolt
07:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
        Kernel driver in use: pcieport
08:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
        Kernel driver in use: pcieport
08:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
        Kernel driver in use: pcieport
09:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge DD 2018] (rev 06)
        Subsystem: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge DD 2018]
        Kernel driver in use: xhci_hcd
52:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
        Subsystem: Intel Corporation Wi-Fi 6 AX200
53:00.0 SD Host controller: Genesys Logic, Inc Device 9755
        Subsystem: Lenovo Device 229f
        Kernel driver in use: sdhci-pci
4.19.113-1 Wireless interface commands
[user@host ~]$ iw dev
[user@host ~]$ cat /proc/net/wireless
Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
 face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
[user@host ~]$ ls /sys/class/ieee80211/
[user@host ~]$ 

Thanks again for your help -- hope this time the info is more helpful to you.

Cheers,
Theo

There are quite a few crashes and core dumps, but I can't make out why they are occuring.

Apr 05 16:06:16 **hostname** sddm[1472]: Authentication error: "Process crashed"
Apr 05 16:06:16 **hostname** sddm[1472]: Auth: sddm-helper crashed (exit code 15)
Apr 05 16:06:16 **hostname** sddm[1472]: Authentication error: "Process crashed"
Apr 05 16:06:16 **hostname** sddm[1472]: Auth: sddm-helper exited with 15

Apr 05 16:12:33 **hostname** systemd-coredump[1206]: Process 949 (sddm) of user 0 dumped core.
Apr 05 16:12:34 **hostname** systemd-coredump[1305]: Process 1299 (sddm) of user 0 dumped core.
Apr 05 16:12:34 **hostname** systemd-coredump[1327]: Process 1314 (sddm) of user 0 dumped core.
Apr 05 16:12:35 **hostname** systemd-coredump[1476]: Process 1470 (sddm) of user 0 dumped core.
Apr 05 16:12:36 **hostname** systemd-coredump[1542]: Process 1536 (sddm) of user 0 dumped core.
Apr 05 16:14:24 **hostname** systemd-coredump[1800]: Process 1794 (sddm) of user 0 dumped core.
Apr 05 16:14:24 **hostname** systemd-coredump[1812]: Process 1806 (sddm) of user 0 dumped core.
Apr 05 16:14:25 **hostname** systemd-coredump[1823]: Process 1817 (sddm) of user 0 dumped core.
Apr 05 16:14:25 **hostname** systemd-coredump[1834]: Process 1828 (sddm) of user 0 dumped core.
Apr 05 16:14:26 **hostname** systemd-coredump[1845]: Process 1839 (sddm) of user 0 dumped core.
Apr 05 16:37:13 **hostname** systemd-coredump[3033]: Process 2966 (org_kde_powerde) of user 1000 dumped core.
Apr 05 16:37:13 **hostname** systemd-coredump[3030]: Process 2889 (kdeconnectd) of user 1000 dumped core.
Apr 05 16:37:13 **hostname** systemd-coredump[3035]: Process 2973 (msm_kde_notifie) of user 1000 dumped core.
Apr 05 16:37:29 **hostname** systemd-coredump[3471]: Process 3413 (org_kde_powerde) of user 1000 dumped core.
Apr 05 16:37:29 **hostname** systemd-coredump[3469]: Process 3338 (kdeconnectd) of user 1000 dumped core.
Apr 05 16:37:29 **hostname** systemd-coredump[3468]: Process 3416 (msm_kde_notifie) of user 1000 dumped core.
Apr 05 19:53:21 **hostname** systemd-coredump[2118]: Process 1982 (org_kde_powerde) of user 1000 dumped core.
Apr 05 19:53:21 **hostname** systemd-coredump[2114]: Process 1973 (kded5) of user 1000 dumped core.
Apr 05 19:53:21 **hostname** systemd-coredump[2117]: Process 1989 (msm_kde_notifie) of user 1000 dumped core.
Apr 05 19:53:21 **hostname** systemd-coredump[2120]: Process 1942 (kdeconnectd) of user 1000 dumped core.

Perhaps this whole thing nvidia related? dmesg shows:

[   28.004974] [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
[   28.005057] [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
[   28.005272] BUG: scheduling while atomic: Xorg/1270/0x00000003
[   28.005273] Modules linked in: hid_generic snd_usb_audio usbhid snd_usbmidi_lib hid snd_rawmidi snd_seq_device cdc_ether usbnet mii cmac algif_hash algif_skcipher af_alg bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common nvidia_drm(POE) nvidia_modeset(POE) btusb videodev btrtl btbcm btintel mc bluetooth ecdh_generic nvidia(POE) ecc ipmi_devintf ipmi_msghandler joydev mousedev snd_sof_pci snd_sof_intel_byt snd_sof_intel_ipc snd_sof_xtensa_dsp snd_sof_intel_hda_common x86_pkg_temp_thermal intel_powerclamp snd_soc_hdac_hda coretemp snd_sof_intel_hda squashfs snd_sof kvm_intel iwlmvm snd_hda_codec_conexant snd_hda_codec_generic thunderbolt kvm snd_soc_skl mac80211 snd_soc_sst_ipc irqbypass snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi loop iTCO_wdt crct10dif_pclmul 8250_dw libarc4 mei_hdcp iTCO_vendor_support crc32_pclmul intel_rapl_msr i915 snd_soc_core wmi_bmof intel_wmi_thunderbolt ghash_clmulni_intel snd_compress ac97_bus iwlwifi
[   28.005295]  snd_pcm_dmaengine aesni_intel snd_hda_intel nls_iso8859_1 crypto_simd nls_cp437 i2c_algo_bit cryptd vfat glue_helper snd_intel_nhlt drm_kms_helper intel_cstate fat snd_hda_codec intel_uncore drm psmouse intel_rapl_perf input_leds pcspkr e1000e cfg80211 snd_hda_core intel_gtt snd_hwdep thinkpad_acpi agpgart snd_pcm i2c_i801 syscopyarea processor_thermal_device mei_me ucsi_acpi intel_lpss_pci sysfillrect typec_ucsi intel_rapl_common intel_lpss nvram sysimgblt mei snd_timer idma64 fb_sys_fops intel_soc_dts_iosf intel_pch_thermal typec wmi ledtrig_audio rfkill snd soundcore tpm_crb tpm_tis tpm_tis_core ac int3403_thermal int340x_thermal_zone tpm int3400_thermal evdev acpi_thermal_rel rng_core mac_hid vmw_vmci uinput sg scsi_mod crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 serio_raw atkbd libps2 sdhci_pci cqhci sdhci crc32c_intel xhci_pci mmc_core xhci_hcd i8042 serio battery
[   28.005316] Preemption disabled at:
[   28.005317] [<0000000000000000>] 0x0
[   28.005318] CPU: 2 PID: 1270 Comm: Xorg Tainted: P           OE     5.4.28-1-MANJARO #1
[   28.005319] Hardware name: LENOVO 20QVCTO1WW/20QVCTO1WW, BIOS N2OET41W (1.28 ) 11/25/2019
[   28.005319] Call Trace:
[   28.005324]  dump_stack+0x66/0x90
[   28.005326]  __schedule_bug.cold+0x8e/0x9b
[   28.005328]  __schedule+0x633/0x770
[   28.005330]  schedule+0x43/0xd0
[   28.005331]  schedule_timeout+0x231/0x310
[   28.005333]  wait_for_completion+0xa6/0x100
[   28.005334]  ? wake_up_q+0x60/0x60
[   28.005336]  do_coredump+0x406/0x1209
[   28.005347]  ? __ext4_journal_stop+0x37/0xa0 [ext4]
[   28.005350]  get_signal+0x4b9/0x8c0
[   28.005352]  do_signal+0x43/0x680
[   28.005355]  exit_to_usermode_loop+0x7f/0x100
[   28.005356]  prepare_exit_to_usermode+0x8e/0xb0
[   28.005357]  retint_user+0x8/0x8
[   28.005359] RIP: 0033:0x7fb0311d5b8d
[   28.005360] Code: 58 b8 ff ff ff ff 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 48 8b 57 20 48 3b 15 9d 74 00 00 48 8b 4f 28 0f 84 9b 00 00 00 <48> 89 15 8c 74 00 00 48 8d 15 55 75 00 00 48 89 0d 06 75 00 00 48
[   28.005360] RSP: 002b:00007ffcb38838f0 EFLAGS: 00013216
[   28.005361] RAX: 000055f2ef529040 RBX: 00007ffcb3883a30 RCX: 0000000000000000
[   28.005362] RDX: 0000000000000057 RSI: 0000000000000040 RDI: 00007ffcb38839a0
[   28.005362] RBP: 0000000000000057 R08: 000000000000000b R09: 000055f2ef529000
[   28.005363] R10: 00000000000003ff R11: 0000000000000000 R12: 00007fb03215e000
[   28.005363] R13: 0000000000000000 R14: 00007ffcb3883a30 R15: 00007fb03215f120

I'd try another nvidia driver as those are easy to install on Manjaro.

1 Like

@freggel.doe Thanks for looking through those! I'll reinstall 5.4.28-1 and then manually upgrade the nvidia driver that it automatically installs.

Pardon the silly question, but what's the normal method of manually upgrading a driver version for nvidia? The only drivers I have installed are either from the Hardware Configuration utility or the Kernel management utility, and both of those choose the nvidia version automatically.

The wiki mentions mwhd tool.

First take a look at what you have currently installed (on my system it's 418):

$ mhwd -li --pci
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
    video-nvidia-418xx            2019.10.25               false            PCI

To list all available drivers:

$ mhwd -la --pci
> All PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
...
    video-nvidia-430xx            2019.10.25               false            PCI
...
    video-nvidia-435xx            2019.10.25               false            PCI
...

Then remove the installed driver and install another:

$ sudo mhwd -r pci video-nvidia-418xx
$ sudo mhwd -i pci video-nvidia-435xx

As always when fiddling with these things: take a backup or snapshot so you can easily roll back any unwanted mishaps.

1 Like

Hey, that did it! I had forgotten that mhwd was a CLI utility in addition to being graphical. Your instructions were helpful, I'll keep those troubleshooting steps in mind if I run into another display issue. I'm running 435 on 5.4.28-1 now instead of 440 and there are no issues so far. Glad to have my WiFi card back again!

Thanks again for your patience and your help! Cheers!

Theo

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

Forum kindly sponsored by