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

AngelBePro · 2024-02-26 18:11:15

So I recently discovered if my monitor is turned off, and I turn it on, there is no signal. First idea was to switch to a different tty, which does not work. But what does work is logging in blindly(I use sddm and kde). I just type my password as if I am receiving signal and that logs me in. But there is still an issue. Switching to a different tty other than the one I am currently using for kde still has no signal. My guess is that tty sessions created before turning on the monitor cannot detect it. Don't know what logs to supply so you tell me.

Last edited by AngelBePro (2024-03-08 11:03:26)

AngelBePro · 2024-02-26 18:19:28

Ok, here is the dmesg http://0x0.st/HRNV.txt and a journal http://0x0.st/HRNO.txt

seth · 2024-02-26 20:26:05

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

(The one you posted looks like the session journal which doesn't include any pre-login entries)

To be clear:

if my monitor is turned off, and I turn it on

There's no problem whatsoever when booting w/ an active ouptut?

Please also post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

AngelBePro · 2024-02-27 06:38:23

seth wrote:

(The one you posted looks like the session journal which doesn't include any pre-login entries)

Seems like I didn't run the command as sudo, here: http://0x0.st/HRc6.txt. Here is the xorg log too http://0x0.st/HRcU.txt

seth · 2024-02-27 08:44:38

[    11.999] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    11.999] (==) NVIDIA(0):     will be used as the requested mode.
[    11.999] (==) NVIDIA(0): 
[    11.999] (--) NVIDIA(0): No enabled display devices found; starting anyway because
[    11.999] (--) NVIDIA(0):     AllowEmptyInitialConfiguration is enabled
[    12.003] (II) NVIDIA(0): Validated MetaModes:
[    12.003] (II) NVIDIA(0):     "NULL"
[    12.003] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
[    12.003] (WW) NVIDIA(0): Unable to get display device for DPI computation.
[    12.003] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default

The output isn't only powerd off but disconnected (do you completely cut it from power? Is it a Tv? KVM?)

You want sth. like https://aur.archlinux.org/packages?O=0&K=x-on-resize though kscreen should™ be able to automagically activate your monitor when it appears.
Another problem is however that the DE might not really like running on a 0x0 sized server.

The nvidia driver has a

Option "ConnectedMonitor" "string"

option which will allow you to enforce a output to be considered available, https://download.nvidia.com/XFree86/Lin … nview.html
Then you'd configure a metamode/modeline for it, sth. along /etc/X11/xorg.conf.d/20-nvidia.conf

Section "Device"                                                                                                                
    Identifier "RTX 3070"
    Driver  "nvidia"
    Option "ConnectedMonitor" "DFP-4"
    Option  "MetaModes" "DFP-4: 2560x1440 +0+0"
EndSection

You can use nvidia-settings to generate a better metamode, but you don't want write a static Xorg server config (let alone using nvidia-settings, it produces a lot of cruft)
Ideally however you want the powered off output to show up as connected.

AngelBePro · 2024-02-27 11:58:27

seth wrote:

(do you completely cut it from power? Is it a Tv? KVM?)

I only use the menu from the monitor to power it off, not using KVM, nor a tv.
I also didn't specify that the monitor is powered off (with the menu not by power) before even booting into the OS itself.
Will try your solutions later and update on what happened.

Last edited by AngelBePro (2024-02-27 11:59:09)

AngelBePro · 2024-02-27 17:34:03

So

seth wrote:

Section "Device"                                                                                                                
    Identifier "RTX 3070"
    Driver  "nvidia"
    Option "ConnectedMonitor" "DFP-4"
    Option  "MetaModes" "DFP-4: 2560x1440 +0+0"
EndSection

Turns out that you had a mistake since my monitor was connected to DFP-5, but that doesn't fix it since now when I launch the computer without the monitor being on the power it on, There is still nothing. But it's worse than before since when I press the power off button once, the pc doesn't power off and i have to force shutdown it (by using the restart button or holding the power button). Also not able to blindly log in which probably indicates that I am not even reaching sddm. Here is a xorg log

[     8.479] (--) Log file renamed from "/var/log/Xorg.pid-633.log" to "/var/log/Xorg.0.log"
[     8.480] 
X.Org X Server 1.21.1.11
X Protocol Version 11, Revision 0
[     8.480] Current Operating System: Linux archlinux 6.7.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:31:48 +0000 x86_64
[     8.480] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7b447a03-5a42-441e-ac42-40eb2dbba923 rw splash loglevel=3 nvidia-drm.modeset=1
[     8.480]  
[     8.480] Current version of pixman: 0.43.2
[     8.480] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     8.480] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     8.480] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 27 19:16:35 2024
[     8.482] (==) Using config directory: "/etc/X11/xorg.conf.d"
[     8.482] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     8.483] (==) No Layout section.  Using the first Screen section.
[     8.483] (==) No screen section available. Using defaults.
[     8.483] (**) |-->Screen "Default Screen Section" (0)
[     8.483] (**) |   |-->Monitor "<default monitor>"
[     8.483] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[     8.483] (**) |   |-->Device "RTX 3070"
[     8.483] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[     8.483] (==) Automatically adding devices
[     8.483] (==) Automatically enabling devices
[     8.483] (==) Automatically adding GPU devices
[     8.483] (==) Automatically binding GPU devices
[     8.483] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     8.484] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[     8.484] 	Entry deleted from font path.
[     8.484] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[     8.484] 	Entry deleted from font path.
[     8.485] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF,
	/usr/share/fonts/100dpi,
	/usr/share/fonts/75dpi
[     8.485] (==) ModulePath set to "/usr/lib/xorg/modules"
[     8.485] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     8.485] (II) Module ABI versions:
[     8.485] 	X.Org ANSI C Emulation: 0.4
[     8.485] 	X.Org Video Driver: 25.2
[     8.485] 	X.Org XInput driver : 24.4
[     8.485] 	X.Org Server Extension : 10.0
[     8.485] (++) using VT number 2

[     8.485] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     8.486] (II) xfree86: Adding drm device (/dev/dri/card0)
[     8.486] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[     8.507] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[     8.508] (--) PCI:*(1@0:0:0) 10de:2484:1462:3903 rev 161, Mem @ 0x80000000/16777216, 0x4000000000/8589934592, 0x4200000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/131072
[     8.508] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[     8.508] (II) LoadModule: "glx"
[     8.510] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     8.517] (II) Module glx: vendor="X.Org Foundation"
[     8.517] 	compiled for 1.21.1.11, module version = 1.0.0
[     8.517] 	ABI class: X.Org Server Extension, version 10.0
[     8.517] (II) LoadModule: "nvidia"
[     8.517] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[     8.521] (II) Module nvidia: vendor="NVIDIA Corporation"
[     8.521] 	compiled for 1.6.99.901, module version = 1.0.0
[     8.521] 	Module class: X.Org Video Driver
[     8.522] (II) NVIDIA dlloader X Driver  545.29.06  Thu Nov 16 01:52:34 UTC 2023
[     8.522] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs

Also sorry for posting here, I can't post it as url currently.

Last edited by AngelBePro (2024-02-27 17:35:52)

seth · 2024-02-27 17:45:54

The log ends prematurely?
Simply copy the xorg log somewherem, move away the configlet, start X11 and check the old log.

AngelBePro · 2024-02-28 07:40:45

So im using this config http://0x0.st/HR2l.txt and this is a healthy boot withouth the screen being powered off at boot http://0x0.st/HR2k.txt, and the old log file is again ending prematurely, and I don't see a difference between the one I posted in my last post and this one but just in case here http://0x0.st/HR27.txt.

seth · 2024-02-28 09:35:22

So im using this config http://0x0.st/HR2l.txt

seth wrote:

you don't want write a static Xorg server config

…
Get rid of the static server config, the suggested configlet would not even have been applied.
You can make it and keep

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVIDIA GeForce RTX 3070"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "ConnectedMonitor" "DFP-5"
    Option         "nvidiaXineramaInfoOrder" "DFP-5"
    Option         "metamodes" "2560x1440 +0+0 {AllowGSYNCCompatible=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

AngelBePro · 2024-03-01 09:54:35

So I got rid of the static server http://0x0.st/HRdA.txt but the xorg log is still the same, and I used

journalctl -b -1

to get the journal of the previouse boot http://0x0.st/HRdK.txt. Hope I am not bumping the post I just didn't have time to post a update.

Last edited by AngelBePro (2024-03-01 10:02:01)

seth · 2024-03-01 10:18:19

[    22.611] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar  1 11:30:04 2024

The server then ran ~30 minutes and

[  1640.104] (II) Server terminated successfully (0). Closing log file.

Terminated cleanly.

The journal segment you posted runs 5 minutes from 11:22 - 11:27, it's not related to the xorg log.

The xorg config lacks

Option         "ConnectedMonitor" "DFP-5"

, kscreen therefore determines the output as not present and disables it.
It never picks up any event to enable it.

You're using kde-unstable?

AngelBePro · 2024-03-01 10:28:07

Well I added extra-staging to pacman.conf, using downgraded sddm to 1.20. I know it's a mess but I am waiting for things to get stable. Will see if

Option         "ConnectedMonitor" "DFP-5"

fixes something.

seth · 2024-03-01 10:31:03

I added extra-staging to pacman.conf

And you wonder why things don't work?
https://wiki.archlinux.org/title/Offici … positories

AngelBePro · 2024-03-01 10:54:54

seth wrote:

I added extra-staging to pacman.conf
And you wonder why things don't work?
https://wiki.archlinux.org/title/Offici … positories

I watched a YouTube tutorial, that's why. Should I use extra-testing?

seth · 2024-03-01 11:02:08

https://wiki.archlinux.org/title/Offici … positories
Testin repos are all or nothing.
You need core, extra and multilib testing and then kde-unstable.
If you want to use kde-unstable.

And you can start praying that your system isn't FUBAR at this point, but you'll likely have to -Syyuu yourself out of this and potentially re-install all packages

And inform the idiot on youtube to delete their videos.

AngelBePro · 2024-03-01 13:32:53

Ignore this since I accidentally typed -QnQ and not -Qnq

Last edited by AngelBePro (2024-03-01 13:45:29)

AngelBePro · 2024-03-04 17:53:51

Alright! After some dumb amount of shit I did I got everything running with plasma. But Back to the topic. It seems like the xorg config worked but I have one small problem, the resolution looks like 800x800. How do I define it?

seth · 2024-03-04 18:14:28

resolution looks like 800x800

??

xrandr -q

AngelBePro · 2024-03-04 18:28:18

The resolution fixes after login, but here

Screen 0: minimum 16 x 16, current 2560 x 1440, maximum 32767 x 32767
DP-3 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
   2560x1440    143.91*+
   1920x1440    143.90  
   1600x1200    143.89  
   1440x1080    143.80  
   1400x1050    143.89  
   1280x1024    143.79  
   1280x960     143.86  
   1152x864     143.92  
   1024x768     143.87  
   800x600      143.83  
   640x480      143.85  
   320x240      142.05  
   1920x1200    143.89  
   1680x1050    143.88  
   1440x900     143.86  
   1280x800     143.84  
   1152x720     143.77  
   960x600      143.72  
   928x580      143.50  
   800x500      143.68  
   768x480      143.69  
   720x480      143.85  
   640x400      143.37  
   320x200      141.40  
   2048x1152    143.88  
   1920x1080    143.88  
   1600x900     143.93  
   1368x768     143.77  
   1280x720     143.67  
   1024x576     143.91  
   864x486      143.63  
   720x400      143.88  
   640x350      143.57

seth · 2024-03-04 18:40:43

The resolution fixes after login

What does that mean?
Where exactly does the

resolution looks like 800x800

A linux console?
You can force the output enabled and a specific mode there, too:
https://wiki.archlinux.org/title/Kernel … cing_modes

AngelBePro · 2024-03-04 18:53:14

The resolution is not right at sddm, but when logging in the resolution resets to 2560x1440.

seth · 2024-03-04 21:43:01

That's odd.
When you do not login, but switch to another TTY and check "xrandr -q --display :0", what resolution is active at SDDM?
Do you run SDDM on wayland??

If all resolutions are listed, but SDDM picks the wrong™ one, you might be able to work around that in /usr/share/sddm/scripts/Xsetup, https://wiki.archlinux.org/title/Xrandr#Configuration

AngelBePro · 2024-03-05 09:06:28

Going into a different tty gets me again to no signal. But after switching back to the sddm tty (in this case tty2) the resolution fixes, but sddm renders in the old resolution and looks like a box at the top left corner of the screen, where as before that it scretches in the old resolution. I also figured out why sometimes the xorg config ends prematurely (I think), plymouth never starts and is stuck there. Here is the journalctl http://0x0.st/H7eN.txt from when it gets stuck, also would like to point out that plymouth doesn't start only when i get to grub with the monitor off and then turn it off before launching arch linux. Here is a journalctl with broken res http://0x0.st/H7eT.txt and the xorg log http://0x0.st/H7eA.txt.

seth · 2024-03-05 15:42:40

[    13.123] (WW) NVIDIA(0): No valid modes for "2560x1440+0+0{AllowGSYNCCompatible=On}";
[    13.123] (WW) NVIDIA(0):     removing.
[    13.123] (WW) NVIDIA(0): 
[    13.123] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
[    13.123] (WW) NVIDIA(0):     "nvidia-auto-select".
[    13.123] (WW) NVIDIA(0): 
[    13.129] (II) NVIDIA(0): Validated MetaModes:
[    13.129] (II) NVIDIA(0):     "DFP-5:nvidia-auto-select"
[    13.129] (II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
[    13.501] (WW) NVIDIA(0): DFP-5 does not have an EDID, or its EDID does not contain a
[    13.501] (WW) NVIDIA(0):     maximum image size; cannot compute DPI from DFP-5's EDID.
[    13.501] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
[    13.502] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory

You can either extract copy the edid to a file when the monitor is connected and inject that: https://wiki.archlinux.org/title/Kernel … s_and_EDID
Or disable nvidia's modevalidation

Option "ModeValidation" "DFP-5: AllowNonEdidModes"

will hopefully do (you can add that to the device section)

Arch Linux

#1 2024-02-26 18:11:15

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

#2 2024-02-26 18:19:28

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

#3 2024-02-26 20:26:05

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

#4 2024-02-27 06:38:23

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

#5 2024-02-27 08:44:38

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

#6 2024-02-27 11:58:27

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

#7 2024-02-27 17:34:03

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

#8 2024-02-27 17:45:54

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

#9 2024-02-28 07:40:45

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

#10 2024-02-28 09:35:22

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

#11 2024-03-01 09:54:35

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

#12 2024-03-01 10:18:19

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

#13 2024-03-01 10:28:07

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

#14 2024-03-01 10:31:03

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

#15 2024-03-01 10:54:54

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

#16 2024-03-01 11:02:08

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

#17 2024-03-01 13:32:53

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

#18 2024-03-04 17:53:51

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

#19 2024-03-04 18:14:28

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

#20 2024-03-04 18:28:18

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

#21 2024-03-04 18:40:43

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

#22 2024-03-04 18:53:14

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

#23 2024-03-04 21:43:01

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

#24 2024-03-05 09:06:28

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

#25 2024-03-05 15:42:40

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

Board footer