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 0CAA61581FB for ; Mon, 26 Aug 2024 10:40:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2256CE2A85; Mon, 26 Aug 2024 10:40:47 +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 7AE8BE2A34 for ; Mon, 26 Aug 2024 10:40:45 +0000 (UTC) Received: (qmail 87574 invoked by uid 3782); 26 Aug 2024 12:40:44 +0200 Received: from muc.de (p4fe156b1.dip0.t-ipconnect.de [79.225.86.177]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Mon, 26 Aug 2024 12:40:43 +0200 Received: (qmail 3210 invoked by uid 1000); 26 Aug 2024 10:40:43 -0000 Date: Mon, 26 Aug 2024 10:40:43 +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: <40afec53-5902-f2f4-1abd-71b0ffb71677@gmail.com> <3336008.aeNJFYEL58@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: <3336008.aeNJFYEL58@rogueboard> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Archives-Salt: ff334d8d-e57f-4955-9b21-54aff85af3dd X-Archives-Hash: 1d564c8ce89a3616db37502752e48694 Hello, Michael. On Sun, Aug 25, 2024 at 22:04:05 +0100, Michael wrote: > On Sunday, 25 August 2024 20:37:37 BST Dale wrote: > > Alan Mackenzie wrote: [ .... ] > > > I'm convinced this isn't a problem in Linux. It's something having got > > > wedged in the motherboard's firmware, seeing as how the blank strip > > > appears even when going into the BIOS. > The plot thickens! If the resolution in the BIOS menu is also wrong and > offset, it sounds like an MSI bug of sorts - "Try disabling CSM" in your UEFI > settings: > https://forums.tomshardware.com/threads/low-resolution-boot-uefi-bios.3530375/ > https://superuser.com/questions/1209012/uefi-and-therefore-linux-console-isnt-displayed-at-native-resolution > I have no idea why CSM affects the video resolution of the firmware, but it > may have to do with how much space is available on the NOR flash chip where > the UEFI firmware is stored. Enabling CSM may be eating up some/more > resources, leaving less to initialise and run the graphics capability of the > MoBo. :-/ The CSM setting actually can't be enabled on my MB for some reason. I tried, but it wouldn't go. Worth a try, but it hasn't gone anywhere. > > > I suspect I'm going to have to reinitialise the CMOS ram, which I > > > really don't want to do, though Michael doesn't think that's the > > > problem. We'll see. > I wasn't aware this display issue is present *before* the OS has even loaded. > This is not a linux issue and the linux driver itself does not seem able to > correct it. > OK, in the first instance disable the CMS in the UEFI settings and reboot. > Some boards do not lose some of their cached settings when you simply > shutdown. Remove the power cable, depress and hold the power button for 10-20 > seconds. Any capacitors will discharge. Reconnect the power and boot > normally. That didn't help either, I'm afraid. I've had a reply from MSI's support. It's along the lines of "buy new cables, don't use an adapter, and don't use a KVM box". In other words, not at all useful. I'm trying to work out whether it's worth trying to supply MSI with the extra information about the excess numbers of pixels being multiples of 16 in both the horizontal and vertical directions. I suspect I'll just get the runaround from them, no matter what. Or, I could go back to the shop that built the machine. Maybe I should try it connected directly to an HDMI monitor. > If the above gymnastics do not fix it, then you'll have to try resetting the > MoBo. Make a note of any changed settings and check the CSM option is left > disabled. I think this is what I will try next. I don't know which of the settings has been changed, so I'll need to make a note of practically every setting. Most of them are still defaults. > > Ahhhhh. If it does it in the BIOS, it's either a monitor or video card, > > or mobo if video is built in, problem. > On modern APUs video graphics chips are integrated within the CPU die itself > as separate graphics cores. It seems such a graphic core is supplying 2112x1116@60Hz, rather than the correct 1920x1080@60Hz. Hopefully the fault is in the firmware, not in the graphics unit. ;-( [ .... ] > Let's hope this is an MSI/CSM specific issue rather than a hardware fault. Given MSI support's attitude, it's looking like my machine is going back to the shop that made it, unless resetting the CMOS RAM does the job. That's the thing to try out next. -- Alan Mackenzie (Nuremberg, Germany).