| 1 |
If you find that the EDID is really bad for one of the monitors, you |
| 2 |
should be able to find a correct copy and make that one available to X, |
| 3 |
although I don't remember how since I haven't needed to do so in years. |
| 4 |
I believe it is a setting within/under Xorg.conf. |
| 5 |
|
| 6 |
Jack |
| 7 |
|
| 8 |
On 2/6/23 00:36, Daniel Frey wrote: |
| 9 |
> I've been having this strange problem with my dual monitor setup. |
| 10 |
> While I've figured out the nightmare of auto-detect not working at all |
| 11 |
> with dual monitors and the inability to use nvidia's configure tool |
| 12 |
> combined with Plasma's monitor option to fix the problem I've switched |
| 13 |
> to nouveau and at least it is consistent now and not messing up my |
| 14 |
> windows and randomly disconnecting. |
| 15 |
> |
| 16 |
> However, I still have one problem which is getting annoying. DPMS does |
| 17 |
> not work automatically like it should. It says for the monitors the |
| 18 |
> capabilities are off. But then it enables it (but it doesn't - xset |
| 19 |
> shows everything disabled - first two lines are monitors and the last |
| 20 |
> one is a general message saying it's enabled.) |
| 21 |
> |
| 22 |
> $ grep -i dpms /var/log/Xorg.0.log |
| 23 |
> [ 6.087] (II) modeset(0): DPMS capabilities: Off |
| 24 |
> [ 6.156] (II) modeset(0): DPMS capabilities: Off |
| 25 |
> [ 6.174] (==) modeset(0): DPMS enabled |
| 26 |
> [ 6.174] (II) Initializing extension DPMS |
| 27 |
> |
| 28 |
> Now I can run xset dpms 300 450 600 and only then xset shows it as set: |
| 29 |
> |
| 30 |
> $ xset q |
| 31 |
> Keyboard Control: |
| 32 |
> auto repeat: on key click percent: 0 LED mask: 00000002 |
| 33 |
> XKB indicators: |
| 34 |
> 00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off |
| 35 |
> 03: Compose: off 04: Kana: off 05: Sleep: off |
| 36 |
> 06: Suspend: off 07: Mute: off 08: Misc: off |
| 37 |
> 09: Mail: off 10: Charging: off 11: Shift Lock: off |
| 38 |
> 12: Group 2: off 13: Mouse Keys: off |
| 39 |
> auto repeat delay: 600 repeat rate: 25 |
| 40 |
> auto repeating keys: 00ffffffdffffbbf |
| 41 |
> fadfffefffedffff |
| 42 |
> 9fffffffffffffff |
| 43 |
> fff7ffffffffffff |
| 44 |
> bell percent: 50 bell pitch: 400 bell duration: 100 |
| 45 |
> Pointer Control: |
| 46 |
> acceleration: 2/1 threshold: 4 |
| 47 |
> Screen Saver: |
| 48 |
> prefer blanking: yes allow exposures: yes |
| 49 |
> timeout: 0 cycle: 600 |
| 50 |
> Colors: |
| 51 |
> default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff |
| 52 |
> Font Path: |
| 53 |
> /usr/share/fonts/misc,/usr/share/fonts/75dpi,built-ins |
| 54 |
> DPMS (Display Power Management Signaling): |
| 55 |
> Standby: 300 Suspend: 450 Off: 600 |
| 56 |
> DPMS is Enabled |
| 57 |
> Monitor is On |
| 58 |
> |
| 59 |
> However, while it does blank and turn off the screens it doesn't last. |
| 60 |
> Maybe 10 seconds later the screens turn back on. |
| 61 |
> |
| 62 |
> I can force it with xset to turn the monitors off immediately but same |
| 63 |
> results - after a short time the monitors turn back on. In the X logs |
| 64 |
> there is this: |
| 65 |
> |
| 66 |
> [ 449.529] (WW) EDID timing clock 408.29 exceeds claimed max 75MHz, fixing |
| 67 |
> |
| 68 |
> which makes me wonder if the EDID data is bad on the one monitor (a |
| 69 |
> Samsung monitor.) |
| 70 |
> |
| 71 |
> Does anyone know of a way to test this DPMS? I suppose I could try |
| 72 |
> unplugging the Samsung monitor to see if the problem goes away? One |
| 73 |
> thing that may make a difference is that the Samsung is HDMI and the |
| 74 |
> other monitor (MSI) is DP. |
| 75 |
> |
| 76 |
> However, both of these monitors worked find on my old computer (it was |
| 77 |
> really old, no UEFI support. |
| 78 |
> |
| 79 |
> Can anyone think of next steps? I'm running out of things to try... |
| 80 |
> |
| 81 |
> Dan |
| 82 |
> |
Archives