Nvidia HDMI "no signal" on TV

kiddogdad · October 26, 2022, 5:08pm

I recently tried connecting my 4k TV to my Nvidia GPU's HDMI port as a second monitor. My primary display is connected through display port. Here's what happens when I try this:

If the computer is already on when I connect, the TV displays "no signal", and my primary monitor goes black but still shows the cursor. Disconnecting the TV makes the primary display work properly again.
If the computer is off when I plug the TV in, the TV and monitor both successfully display the login screen. After logging in, the TV switches to "no signal" as KDE is launching. KDE launches and displays correctly on the primary display. System settings shows both displays, but nothing I do in System settings can get the TV to display again.
If I boot with both displays plugged in and then leave the computer on, eventually the primary display will go to sleep. (But not the full system. I've disabled automatic sleep on the computer, only the display goes to sleep.) When I attempt to wake it, the primary monitor shows a black screen with a cursor. Unplugging the TV makes the primary monitor work again.

System details below. Any assistance is appreciated. Thanks!

System:
Kernel: 5.15.74-1-lts arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=948dd271-131a-4b40-8086-7b390c7c9723 rw rootflags=subvol=@
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
lsm=landlock,lockdown,yama,apparmor,bpf ibt=off
Desktop: KDE Plasma v: 5.26.2 tk: Qt v: 5.15.6 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING X570-PRO (WI-FI) v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 4021
date: 08/10/2021
CPU:
Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3 gen: 4
level: v3 note: check built: 2021-22 process: TSMC n7 (7nm)
family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 4195 high: 4201 min/max: 2200/5279 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 4199 2: 4197
3: 4199 4: 4200 5: 4200 6: 4199 7: 4201 8: 4193 9: 4199 10: 4197 11: 4163
12: 4199 bogomips: 100805
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed 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: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3060] vendor: Micro-Star MSI
driver: nvidia v: 520.56.06 alternate: nouveau,nvidia_drm non-free: 515.xx+
status: current (as of 2022-10) arch: Ampere code: GAxxx process: TSMC n7
(7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0a:00.0 chip-ID: 10de:2487 class-ID: 0300
Device-2: Logitech HD Pro Webcam C920 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 5-2:3 chip-ID: 046d:082d
class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.4
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 3440x1440 s-dpi: 110 s-size: 794x332mm (31.26x13.07")
s-diag: 861mm (33.88")
Monitor-1: DP-4 pos: primary res: 3440x1440 hz: 60 dpi: 110
size: 797x334mm (31.38x13.15") diag: 864mm (34.02") modes: N/A
Monitor-2: HDMI-0 size-res: N/A modes: N/A
OpenGL: renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2 v: 4.6.0 NVIDIA
520.56.06 direct render: Yes
Audio:
Device-1: NVIDIA GA104 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 5-2:3 chip-ID: 046d:082d pcie:
class-ID: 0102 gen: 4 speed: 16 GT/s serial: <filter> lanes: 16
bus-ID: 0a:00.1 chip-ID: 10de:228b class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Logitech HD Pro Webcam C920 type: USB
driver: snd-usb-audio,uvcvideo
Sound API: ALSA v: k5.15.74-1-lts running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 06:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-4:3 chip-ID: 8087:0029 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 3.68 TiB used: 1.99 TiB (53.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: TeamGroup
model: T-FORCE TM8FP8001T size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: V9002s77 temp: 39.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: TeamGroup
model: T-FORCE TM8FP8001T size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: V9002s77 temp: 39.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: GPT
Partition:
ID-1: / raw-size: 953.57 GiB size: 953.57 GiB (100.00%) used: 303.75 GiB
(31.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 592 KiB
(0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 953.57 GiB size: 953.57 GiB (100.00%) used: 303.75
GiB (31.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 953.57 GiB size: 953.57 GiB (100.00%) used: 303.75
GiB (31.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 953.57 GiB size: 953.57 GiB (100.00%) used: 303.75
GiB (31.9%) 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: 31.26 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 44.5 C mobo: N/A gpu: nvidia temp: 38 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 364 Uptime: 1m wakeups: 0 Memory: 31.26 GiB used: 5.26 GiB
(16.8%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 2472 pm: pacman pkgs: 2466
libs: 567 tools: octopi,paru pm: flatpak pkgs: 6 Shell: fish v: 3.5.1
default: Bash v: 5.1.16 running-in: yakuake inxi: 3.3.22
Garuda (2.6.9-1):
System install date:     2022-01-09
Last full system update: 2022-10-26
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:

BluishHumility · October 26, 2022, 5:22pm

If your DE is using a resolution that is not supported by the TV, that could cause this. Your login screen might be using a lower resolution that your TV can handle.

Try lowering the resolution in your display settings to test.

kiddogdad · October 26, 2022, 10:25pm

Thanks for the reply! I tried changing the resolution on my primary monitor and then plugging the TV in. The TV was recognized in KDE's settings, but wasn't enabled. (This might be default behavior?) I checked, and it was recognizing that the TV has a different resolution than my monitor. I enabled the TV, and then it showed no signal, and I got the black screen on my main monitor. Turning off the TV made my monitor work again.

BluishHumility · October 26, 2022, 11:36pm

What resolution did you try? Try 1080p/60hz and 720p/60hz (those are very common TV resolutions).

kiddogdad · October 26, 2022, 11:56pm

I tried both of those, and neither worked. I should also point out that it's a 4K TV with a 3840x2160 maximum resolution, and that KDE settings is picking up that resolution and setting it by default.

BluishHumility · October 27, 2022, 2:04am

Try switching to Wayland and see if you have better luck.

After fully updating, run

sudo pacman -S plasma-wayland-session

Reboot, and switch the session on the login screen before you sign in.

kiddogdad · October 27, 2022, 1:00pm

Thanks for the suggestion. I tried that, and unfortunately the Wayland session couldn't load. It would attempt to load, then fall back to the login screen again.

BluishHumility · October 27, 2022, 7:26pm

My mistake, I believe you need to enable the nvidia-drm.modeset=1 kernel parameter as well–I forgot to mention that.

kiddogdad · October 30, 2022, 11:30am

Thanks for continuing to help! I added this kernel parameter using Garuda Boot Options and restarted the computer. Same behavior: On Wayland, tries to login, fails and falls back to login screen. On X11, login screen shows, "no signal" after KDE launches.

system · November 13, 2022, 11:30am

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