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 76AD415800F for ; Mon, 6 Feb 2023 16:03:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B357DE086C; Mon, 6 Feb 2023 16:03:09 +0000 (UTC) Received: from mail-qt1-f169.google.com (mail-qt1-f169.google.com [209.85.160.169]) (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 44257E077F for ; Mon, 6 Feb 2023 16:03:09 +0000 (UTC) Received: by mail-qt1-f169.google.com with SMTP id v17so13311081qto.3 for ; Mon, 06 Feb 2023 08:03:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:reply-to :content-language:references:to:subject:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=MUOFJTJ7ELS0esrfFo6GArOy9LXD2830bjfvf7wX0Oo=; b=4qu4y6ImvlTg323h1Q8guW+nmSR2MEodLw2p1M1eNvsQNy0eFYQkpuQdzW0CimfnML 7s8GOlIxTn25cZZnwnUVJWLNRpc7UVK7xt73oMlLv/Bq4CQnLB4oLJYeXq+DrtrQIYHl dXAXll1dWa+hNBMhRVVfEITiZP1jriCebdeiLsoQtY2TqXVMO6MYAkHo9QrS4BZY0VqX oqmiK6mP60adXFJY1UM/TOUvTtaF8Yz2jfJMnd8HakLTHVnoSHhC+Z0pguf+b3xNR/Tm IxGFC+/HAVHcrGuJ6d9d7QIEGb30/zcNkA+N6FSsrcRMjbHNJ5BCZtR4rb1aBvlz0t3w jO1w== X-Gm-Message-State: AO0yUKXWlj9VdeLSw186it+D36uADaEFrLLdIfAAQ7y4mToSee4fFyk4 iVlPJ+8Z1J0gvnzPOYy04ajZQJ2aT2oMhRWe X-Google-Smtp-Source: AK7set+qWwN3N0c/7+ET8B9nsT+VI/Std5YGLyjhqPcZwk1s9T4+8g4X8jCxXzvoj9Oz3DwoBOKaeg== X-Received: by 2002:a05:622a:17c4:b0:3b8:5199:f841 with SMTP id u4-20020a05622a17c400b003b85199f841mr37304376qtk.0.1675699388465; Mon, 06 Feb 2023 08:03:08 -0800 (PST) Received: from [192.168.1.18] (c-73-238-129-126.hsd1.ma.comcast.net. [73.238.129.126]) by smtp.gmail.com with ESMTPSA id b13-20020ac85bcd000000b003b68d445654sm7423366qtb.91.2023.02.06.08.03.07 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Feb 2023 08:03:07 -0800 (PST) Message-ID: <8922865a-08cc-5780-d76f-9bb726de4cf5@users.sourceforge.net> Date: Mon, 6 Feb 2023 11:00:47 -0500 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 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [gentoo-user] Strange DPMS behaviour To: gentoo-user@lists.gentoo.org References: Content-Language: en-US-large From: Jack In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: 6e2c39d4-b7d5-4964-82e6-88c5d8a4c020 X-Archives-Hash: cbcfae6a7c9c525a5585325b000beb37 If you find that the EDID is really bad for one of the monitors, you should be able to find a correct copy and make that one available to X, although I don't remember how since I haven't needed to do so in years.  I believe it is a setting within/under Xorg.conf. Jack On 2/6/23 00:36, Daniel Frey wrote: > 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 >