Monitor frequently not detected.

seth · 2023-03-05 15:58:46

[    12.724] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar  3 21:01:47 2023

That's an older log?

TimSousa · 2023-03-05 17:05:02

That's weird. I got it from /var/log/Xorg.0.log
Is there some other place to get it from?

seth · 2023-03-05 17:21:27

https://wiki.archlinux.org/title/Xorg#General - it depends on how X11 is started.

TimSousa · 2023-03-05 20:01:07

here's my xorg log:
https://0x0.st/Hzln.txt

the output of xrandr -q
https://0x0.st/Hz65.txt

seth · 2023-03-05 21:14:42

Both nvidia outputs are there, DP-1-1 actually w/ 240Hz (w/o the extra modeline), the Enable flags are picked up but ignored.
The easiest solution is probably to configure the outputs w/ xrandr in your xinitrc, if the DP-1-1 output keeps up being only randomly present, try https://wiki.archlinux.org/title/Kernel … _KMS_start for the nvidia and i915 modules, https://wiki.archlinux.org/title/Kernel … _KMS_start

TimSousa · 2023-03-06 03:26:36

Can you guide me through the process?
sorry for the inconvenience

seth · 2023-03-06 08:14:16

What process?
Adding the modules to the initramfs? That's explained in the wiki.
Using "xrandr --output DP-1-1 --auto"? If you need specifics you can't infer from "xrandr --help", you'll need to explain how you want the outputs to be arranged (absolute or relative position, refresh rate, …)

TimSousa · 2023-03-06 19:20:45

Here's my .xinitrc file:
http://0x0.st/HznU.sh

I tried adding the xrandr commands before and after starting qtile and for some reason they still aren't being picked up.

I also tried this configuration:
http://0x0.st/Hz5b.sh

The monitors do turn on now, but my main monitor (DP-1-1) isn't the primary (eDP-1 is) and HDMI-1-0 either mirrors eDP-1 or is just a black screen (still turned on)

I also tried

$ cvt 1920 1080

# 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
Modeline "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync

$ xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync

$ xrandr --addmode HDMI-1-0 1920x1080_60.00

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  65
  Current serial number in output stream:  66

Last edited by TimSousa (2023-03-06 20:05:33)

seth · 2023-03-06 20:50:05

…
setxkbmap -layout pt

xrandr --newmode "1920x1080_239.76" 594.270  1920 1952 1984 2040  1080 1137 1145 1215  +HSync -VSync
xrandr --addmode DP-1-1 1920x1080_239.76
xrandr --output DP-1-1 --primary --mode 1920x1080_239.76 --left-of eDP-1
xrandr --output HDMI-1-0 --auto --right-of DP-1-1 

exec /usr/bin/qtile start

I also tried

Why?

TimSousa · 2023-03-06 21:57:24

Probably out of desperation to be honest.. I thought that there could be an issue with the mode - maybe it wasn't being saved? so I decided I'd just create it on the go
Anyways, that didn't work.. any ideas on how to proceed?

seth · 2023-03-06 22:34:41

that didn't work..

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

What's the resulting output of "xrandr -q"?

TimSousa · 2023-03-06 23:22:20

sorry, you're totally right.
here's the output of xrandr -q when setting and adding the newmode on the .xinitrc
https://0x0.st/Hz78.txt

and the xorg log:
https://0x0.st/Hz7c.txt

with this config, eDP-1worked as the primary, DP-1-1 as the second monitor, and HDMI-1-0 would either be a black screen or mirror eDP-1

the output of xrandr -q with this .xinitrc file:
http://0x0.st/Hz7A.txt

and the xorg log:
http://0x0.st/Hz7A.txt

with this config, though. only eDP-1 would turn on.

seth · 2023-03-07 07:28:16

here's the output of xrandr -q when setting and adding the newmode on the .xinitrc

eDP-1 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080    240.00*+  60.01    59.97    59.96    59.93    60.00
HDMI-1-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 531mm x 299mm
   1920x1080     60.00*+  59.99    59.94    50.00 
DP-1-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 540mm x 300mm
   1920x1080     60.00 + 239.76   144.00   119.98   119.93    99.90    84.88    59.94    50.00  
   1920x1080_239.76 239.76*

All outputs are there, active and use the desired modes.
The only "problem" is that eDP-1 and HDMI-1-0 originate at the same location which fits the xrandr calls.

xrandr --output DP-1-1 --left-of eDP-1 --primary
xrandr --output HDMI-1-0 --left-of DP-1-1

Sounds like you'd like

HDMI-1-0 | DP-1-1 | eDP-1
?

…
setxkbmap -layout pt

xrandr --newmode "1920x1080_239.76" 594.270  1920 1952 1984 2040  1080 1137 1145 1215  +HSync -VSync
xrandr --addmode DP-1-1 1920x1080_239.76
xrandr --output DP-1-1 --primary --mode 1920x1080_239.76 --left-of eDP-1
xrandr --output HDMI-1-0 --auto --left-of DP-1-1 

nitrogen --restore &
picom &

exec /usr/bin/qtile start

You also want to arrange the outputs before running picom to no cause a race condition (likely cause of randomly black output)

TimSousa · 2023-03-07 20:10:31

That worked! All monitors turn on and are in the right place! Thanks man!

DP-1-1 still only turns on some of the time though — will be checking those modules you mentioned

But there's still an issue..
I'm having some framerate issues as seen in this slow-motion video

Any idea what could be causing the issue?
Should I start a new thread for that issue in particular?

seth · 2023-03-07 20:38:03

What exactly is the "frame-rate" issue here? The cursor trail?
How slow-mo is this? (What makes you sure it's not an artifact of the recording?)

Is the issue that the cursor seems to be rendered at 60Hz even on the 240Hz outputs?
It's (by default) rendered by the driver directly into the framebuffer.
Idk whether the nvidia blob caps that or aligns it to (whatever, primary?) output - is it visible w/ the naked eye?
Does it also happen w/ only one (240Hz) output?

TimSousa · 2023-03-25 15:36:56

I added the modules to my mkinitcpio, but the monitor is still only randomly present.
For some reason my xorg logs aren't being updated.
Here's the one from /var/log
And the one from .local/share/xorg
my .xinitrc file, in case it's useful:
0x0.st/HoSl.sh

seth · 2023-03-25 20:02:33

What's the output of "xrandr -q" when the monitor is not present?

TimSousa · 2023-03-26 16:32:10

when the monitor isn't present it's shown as disconnected by xrandr
https://0x0.st/H-HZ.txt
I usually need to quit qtile/x many times until it finally is detected.

Last edited by TimSousa (2023-03-26 16:33:03)

seth · 2023-03-26 19:17:56

So I guess https://0x0.st/HoSE.txt is not such affected Xorg run?
Also while both, HDMI-1-0 and DP-1-1 are attached to the nvidia GPU, only HDMI-1-0 shows up, but DP-1-1 doesn't (so it's not about the "Nvidia drivers not kicking in")

I usually need to quit qtile/x many times until it finally is detected.

Depending on how frequent this is, can you at all trigger the undetected output when you only boot the multi-user.target, get a cup of coffee - or otherwise wait 5 minutes - and only start X11 then?

TimSousa · 2023-03-28 17:42:52

I'm not sure this is exactly what you asked (I'm pretty new to this), but I used systemctl set-default multi-user.target
and removed the lines that started x on my .bash_profile

unfortunately, though, the monitor still didn't turn off after a reboot, login, waiting 10 minutes and running startx

the log file, though, did update, so here it is along with the output of xrandr -q (monitor's still not detected)

seth wrote:

(so it's not about the "Nvidia drivers not kicking in")

yep, that issue's resolved! should've updated the title.

seth · 2023-03-28 19:56:58

still didn't turn off after a reboot

Typo??

Is the troublesome monitor connected w/ an adapter?
As mitigation, you could try to dump its edid when it shows up and synthetically add it, https://wiki.archlinux.org/title/Kernel … s_and_EDID

Arch Linux

#26 2023-03-05 15:58:46

Re: Monitor frequently not detected.

#27 2023-03-05 17:05:02

Re: Monitor frequently not detected.

#28 2023-03-05 17:21:27

Re: Monitor frequently not detected.

#29 2023-03-05 20:01:07

Re: Monitor frequently not detected.

#30 2023-03-05 21:14:42

Re: Monitor frequently not detected.

#31 2023-03-06 03:26:36

Re: Monitor frequently not detected.

#32 2023-03-06 08:14:16

Re: Monitor frequently not detected.

#33 2023-03-06 19:20:45

Re: Monitor frequently not detected.

#34 2023-03-06 20:50:05

Re: Monitor frequently not detected.

#35 2023-03-06 21:57:24

Re: Monitor frequently not detected.

#36 2023-03-06 22:34:41

Re: Monitor frequently not detected.

#37 2023-03-06 23:22:20

Re: Monitor frequently not detected.

#38 2023-03-07 07:28:16

Re: Monitor frequently not detected.

#39 2023-03-07 20:10:31

Re: Monitor frequently not detected.

#40 2023-03-07 20:38:03

Re: Monitor frequently not detected.

#41 2023-03-25 15:36:56

Re: Monitor frequently not detected.

#42 2023-03-25 20:02:33

Re: Monitor frequently not detected.

#43 2023-03-26 16:32:10

Re: Monitor frequently not detected.

#44 2023-03-26 19:17:56

Re: Monitor frequently not detected.

#45 2023-03-28 17:42:52

Re: Monitor frequently not detected.

#46 2023-03-28 19:56:58

Re: Monitor frequently not detected.

Board footer