From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 835E715800F for ; Mon, 6 Feb 2023 05:36:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DF15CE07D0; Mon, 6 Feb 2023 05:36:12 +0000 (UTC) Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 98CC2E077F for ; Mon, 6 Feb 2023 05:36:12 +0000 (UTC) Received: by mail-pf1-x42d.google.com with SMTP id t17so7595939pfj.0 for ; Sun, 05 Feb 2023 21:36:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=P5hZS7MoLU8IS16XekaIkS6S/fm/P+XLx2qrz4EJe6s=; b=LEGUtdjSnPUvGPn0tX3Rv+7HkGzYCwciZfxN0X5AExyCKeVG3waNnoOB7KRg+sMpmP ImV64gmZtxMvcj5Hw63NyaqaMZultTa5ml6u84DWhck1wIITnimZlPtWOJtVy88cpRRg WbhTeO96KOQH311YPdgzhhfJsz59y7lX3mHC4wXbz2a9XGltArPSWPMeKaRkdxmNaTwB Y1S9Qxn7mWG9GN7KPvuVYJ9GOZkNQjFn8mEE8MCKawIl1X4dP61G0g6347EF5tgosGgZ 7TepxvZiO2/gL3ntXNx9xNHDOklkhMg631rzY1KHyTyVZHKUID/d5Dqdlvgvw1eghTpi kO0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=P5hZS7MoLU8IS16XekaIkS6S/fm/P+XLx2qrz4EJe6s=; b=ZgyAhZVOFxVfWLB4xZCR5PRrS/rm43IT4yFFi7SbWlqw8MpVPZH7zkQimZCgU9JVE7 H8vTvW5twupfLS8VPishEnr8dxvrpi1kgP4ZP8OBPgC5mcjqPCJyUHWpllrF+M840+BD AUcE6zfSyd7Tthjo91NB5SZR0Sef6Z0A9lEj9nIJNi5Ah8Gg6PPyGau4mvGtAampCsHA 8lx3RiNYO9gctmvnP0iCSBtp9KHsD8i5l92igNN3TZr1NpYo7duIhN2SUxBxSV8lYiQ2 eGEiwlnhYSRRnI978IMebEr3yCK7wven92wei88whknFfyCqjAk9GwUpUUTTYuwKlJIu 8Npw== X-Gm-Message-State: AO0yUKWM1v1urmulxljsEYE+3LhRotSLTdh4C8AX6iIqjsOTpR9qPSG1 e/kJHSTlhpnaQrpQ2zFrEeuNj/INIO5ru5dbFOOt9nTYSJ8= X-Google-Smtp-Source: AK7set9YLUTujudIjLE6T47Mds/RV8h+MmwR3dzoOiUJxfiMnTVQPTW/mxMnUpwUmJoPyAOaPfZqdv0OrU1JC+hAxlA= X-Received: by 2002:a05:6a00:4293:b0:593:b07a:893 with SMTP id bx19-20020a056a00429300b00593b07a0893mr3747646pfb.31.1675661771214; Sun, 05 Feb 2023 21:36:11 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 From: Daniel Frey Date: Sun, 5 Feb 2023 21:36:00 -0800 Message-ID: Subject: [gentoo-user] Strange DPMS behaviour To: Gentoo User Mailing List Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: e948462b-aa57-43f4-87b6-09f7f1fec5f1 X-Archives-Hash: d05b781ede2e032f0651a4e13dea5a87 I've been having this strange problem with my dual monitor setup. While I've figured out the nightmare of auto-detect not working at all with dual monitors and the inability to use nvidia's configure tool combined with Plasma's monitor option to fix the problem I've switched to nouveau and at least it is consistent now and not messing up my windows and randomly disconnecting. However, I still have one problem which is getting annoying. DPMS does not work automatically like it should. It says for the monitors the capabilities are off. But then it enables it (but it doesn't - xset shows everything disabled - first two lines are monitors and the last one is a general message saying it's enabled.) $ grep -i dpms /var/log/Xorg.0.log [ 6.087] (II) modeset(0): DPMS capabilities: Off [ 6.156] (II) modeset(0): DPMS capabilities: Off [ 6.174] (==) modeset(0): DPMS enabled [ 6.174] (II) Initializing extension DPMS Now I can run xset dpms 300 450 600 and only then xset shows it as set: $ xset q Keyboard Control: auto repeat: on key click percent: 0 LED mask: 00000002 XKB indicators: 00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off 03: Compose: off 04: Kana: off 05: Sleep: off 06: Suspend: off 07: Mute: off 08: Misc: off 09: Mail: off 10: Charging: off 11: Shift Lock: off 12: Group 2: off 13: Mouse Keys: off auto repeat delay: 600 repeat rate: 25 auto repeating keys: 00ffffffdffffbbf fadfffefffedffff 9fffffffffffffff fff7ffffffffffff bell percent: 50 bell pitch: 400 bell duration: 100 Pointer Control: acceleration: 2/1 threshold: 4 Screen Saver: prefer blanking: yes allow exposures: yes timeout: 0 cycle: 600 Colors: default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff Font Path: /usr/share/fonts/misc,/usr/share/fonts/75dpi,built-ins DPMS (Display Power Management Signaling): Standby: 300 Suspend: 450 Off: 600 DPMS is Enabled Monitor is On However, while it does blank and turn off the screens it doesn't last. Maybe 10 seconds later the screens turn back on. I can force it with xset to turn the monitors off immediately but same results - after a short time the monitors turn back on. In the X logs there is this: [ 449.529] (WW) EDID timing clock 408.29 exceeds claimed max 75MHz, fixing which makes me wonder if the EDID data is bad on the one monitor (a Samsung monitor.) Does anyone know of a way to test this DPMS? I suppose I could try unplugging the Samsung monitor to see if the problem goes away? One thing that may make a difference is that the Samsung is HDMI and the other monitor (MSI) is DP. However, both of these monitors worked find on my old computer (it was really old, no UEFI support. Can anyone think of next steps? I'm running out of things to try... Dan