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) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2627F1581FB for ; Tue, 27 Aug 2024 16:05:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2857CE2AD0; Tue, 27 Aug 2024 16:05:31 +0000 (UTC) Received: from mail.muc.de (mail.muc.de [193.149.48.3]) (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 D8D8FE2AA9 for ; Tue, 27 Aug 2024 16:05:29 +0000 (UTC) Received: (qmail 1992 invoked by uid 3782); 27 Aug 2024 18:05:27 +0200 Received: from muc.de (p4fe15d34.dip0.t-ipconnect.de [79.225.93.52]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Tue, 27 Aug 2024 18:05:27 +0200 Received: (qmail 6236 invoked by uid 1000); 27 Aug 2024 16:05:26 -0000 Date: Tue, 27 Aug 2024 16:05:26 +0000 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] New machine: Contents of display are offset around 2 inches from the left hand side. Message-ID: References: <3336008.aeNJFYEL58@rogueboard> <2227968.NgBsaNRSFp@rogueboard> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Archives-Salt: 27f9e348-e099-4e84-a6e8-800271dc8fe6 X-Archives-Hash: 05467f66228b5f8776638885c78bcf27 Hello, everybody. On Mon, Aug 26, 2024 at 14:49:14 +0000, Alan Mackenzie wrote: > On Mon, Aug 26, 2024 at 12:54:20 +0100, Michael wrote: > > On Monday, 26 August 2024 11:40:43 BST Alan Mackenzie wrote: > > > On Sun, Aug 25, 2024 at 22:04:05 +0100, Michael wrote: > I'm beginning to think getting an MSI board was a mistake. I'm still thinking that. > > > Or, I could go back to the shop that built the machine. Maybe I > > > should try it connected directly to an HDMI monitor. OK, I'm just back from the shop. The technician there plugged the machine into an HDMI monitor, and it just worked. Before leaving, I assured him that I _would_ get the machine working, even if that might involve buying a new monitor. ;-( When I got back home again and plugged in the new machine, it was slightly different. It was still pumping out 2112x1116, but the 2" gap has become a 1" gap on both the left hand and the right hand sides. There's still a (smaller) gap at the top. I haven't yet tried booting into Linux. At least we now have an indication of something "analog" perhaps not being in order. I'm thinking that perhaps my HDMI->DVI adapter is broken. I should have bought a new one while I was at the shop, just to test. I did have trouble with Windows laptops when I plugged them in via this adapter a couple of years ago. Maybe I'll go back to the shop to get that new HDMI->DVI adapter tomorrow. There might still be errors in the MSI's BIOS firmware's handling of the EDID, I still think that. [ .... ] >> Another thing to try to confirm is if the EDID of the monitor is >> correct: >> Emerge sys-apps/edid-decode, then capture the EDID of the monitor >> with get- edid in a file and feed it to 'edid-decode -p'. It will >> parse the file and output a human readable output. Then you can see >> what the preferred resolution is as far as the monitor EDID content >> is concerned, or if it is indeed missing as you reported previously. After reading the fine manual page, I tried edid-decode -pc, the -c meaninguto check the correctness of the EDID. It output a warning and (attleastdone)efault - something about some indicated resolutions' verticallsyncptimetlying(outside the given bounds. The diagnostics look like this: Warnings: Block 1, CTA-861 Extension Block: Display Product Serial Number is set, so the Serial Number in the Base EDID should be 0. Add a Colorimetry Data Block with the sRGB colorimetry bit set to avoid interop issues. Failures: Block 1, CTA-861 Extension Block: Missing VCDB, needed for Set Selectable RGB Quantization to avoid interop issues. EDID: Base EDID: Some timings are out of range of the Monitor Ranges: Vertical Freq: 50.000 - 75.062 Hz (Monitor: 56.000 - 75.000 Hz) EDID conformity: FAIL [ .... ] > > The recurring flickering of the display after you've loaded your desktop shows > > the linux OS is trying to re-adjust the display. Usually this happens when > > the connection/power to the monitor is disrupted, which again points to a > > connector issue, or it can also happen if you specified in your GUI the wrong > > resolution/frequency. > Yes. I think the connectors are OK, but maybe we'll see how the machine > performs differently at the shop tomorrow. I've decided I'm definitely going to get a new HDMI->DVI adapter. -- Alan Mackenzie (Nuremberg, Germany).