From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=DATE_IN_PAST_12_24 autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 14007 invoked from network); 25 Apr 2021 10:17:15 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 25 Apr 2021 10:17:15 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 1ess; Sun Apr 25 06:04:21 -0400 2021 Message-ID: <050993C291A0D8B0008D9A4DAE2DA4DA@felloff.net> Date: Sat, 24 Apr 2021 18:07:11 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: <30C99A62E19B58AC69D833F029414A13@smtp.pobox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: module property GPU locator Subject: Re: [9front] aux/vga -p intermittent edid reporting Reply-To: 9front@9front.org Precedence: bulk > But back to the main issue: is edid supposed to be consistently > reported, or is this expected? no, this is not expected. this hints at some issue with the i2c controller code that is supposed to read the edid over the aux channel. the fix would be to fix that code so it read edid consistently. on some intel cards, the i2c stuff doesnt work at all. in this case, you can copy the monitor information into vgadb and tell it to use that info directly, skipping the i2c part. -- cinap