[SOLVED]No signal to monitor when turning it on after booting

AngelBePro · 2024-03-05 19:24:20

Sorry to ask, but after going through the steps in the wiki link you sent, my edid is still not detected. Im probably doing something wrong so here is the initcpio http://0x0.st/H7fy.txt and the grub config http://0x0.st/H7fv.txt. The edid file as you can see from the initcpio is in /usr/lib/firmware/edid/edid.bin.

seth · 2024-03-05 19:31:43

The kernel will not use the DFP syntax, the actually relevant output shows up in /sys/class/drm (Sorry, should have warned you)

However nvidia also supports an Xorg option for this (and you don't need the edid before X11 starts, I guess)

Option "CustomEDID" "DFP-5:/usr/lib/firmware/edid/edid.bin"

AngelBePro · 2024-03-05 20:11:18

Ok idk what is up now but there is no signal until I switch between ttys. Also only the tty where sddm is running is sending signal after switching. Hope you will be able to help me fix this soon because this post is already long enough, journalctl: http://0x0.st/H7f5.txt xorg log: http://0x0.st/H7fR.txt.

seth · 2024-03-05 20:43:27

Mar 05 21:56:51 archlinux kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 05 21:56:51 archlinux kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership

Do you have nvidia_drm.fbdev=1 enabled in any way shape or form?
If not, try - the behavior of the 550xx drivers is inconclusive (there've been reports that it's still buggy and other that it's actually required)

The X11 server accepts the output and add the proper metamode - this should be fine (and I guess so is your SDDM output once it shows up?)

AngelBePro · 2024-03-05 20:55:51

nvidia_drm.fbdev=1 fixed the "Failed to grab modeset ownership" error. About SDDM - it does render in the right resolution but i have to switch to a different tty and every other tty than the the one SDDM is running has no signal.

seth · 2024-03-06 08:12:05

But fbdev didn't do anything about the actual framebuffer situation at hand?
Try to supply the EDID via drm.edid_firmware - the correct output name is the one in /sys/class/drm where you got the edid from itfp.

Edit: ie. sth. like HDMI-0

Last edited by seth (2024-03-06 08:12:29)

AngelBePro · 2024-03-08 11:03:04

I stopped dealing with this issue as I migrated to wayland, marking as solved.

seth · 2024-03-08 14:08:39

Fwwi, I'm not sure that migrating to wayland would do anything about a failed output handshake; you might be fine because the output has actually always worked and you just needed sth. like https://aur.archlinux.org/packages?O=0&K=x-on-resize started in the right context (SDDM?)

Oh, well…

Arch Linux

#26 2024-03-05 19:24:20

Re: [SOLVED]No signal to monitor when turning it on after booting

#27 2024-03-05 19:31:43

Re: [SOLVED]No signal to monitor when turning it on after booting

#28 2024-03-05 20:11:18

Re: [SOLVED]No signal to monitor when turning it on after booting

#29 2024-03-05 20:43:27

Re: [SOLVED]No signal to monitor when turning it on after booting

#30 2024-03-05 20:55:51

Re: [SOLVED]No signal to monitor when turning it on after booting

#31 2024-03-06 08:12:05

Re: [SOLVED]No signal to monitor when turning it on after booting

#32 2024-03-08 11:03:04

Re: [SOLVED]No signal to monitor when turning it on after booting

#33 2024-03-08 14:08:39

Re: [SOLVED]No signal to monitor when turning it on after booting

Board footer