From: Alan Mackenzie <acm@muc.de>
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.
Date: Mon, 26 Aug 2024 10:40:43 +0000 [thread overview]
Message-ID: <Zsxbq6ZJIhJIIio_@ACM> (raw)
In-Reply-To: <3336008.aeNJFYEL58@rogueboard>
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).
next prev parent reply other threads:[~2024-08-26 10:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 16:54 [gentoo-user] New machine: Contents of display are offset around 2 inches from the left hand side Alan Mackenzie
2024-08-22 21:44 ` Michael
2024-08-23 16:21 ` Alan Mackenzie
2024-08-23 18:27 ` Dale
2024-08-24 10:08 ` Michael
2024-08-23 18:33 ` Jack
2024-08-23 18:44 ` Dale
2024-08-23 19:09 ` Alan Mackenzie
2024-08-24 9:44 ` Michael
2024-08-24 13:25 ` Alan Mackenzie
2024-08-24 15:40 ` Michael
2024-08-24 20:36 ` Alan Mackenzie
2024-08-25 12:33 ` Alan Mackenzie
2024-08-25 13:53 ` Dale
2024-08-25 16:02 ` Michael
2024-08-25 16:28 ` Dale
2024-08-25 15:31 ` Michael
2024-08-25 17:47 ` Alan Mackenzie
2024-08-25 18:28 ` Dale
2024-08-25 19:12 ` Alan Mackenzie
2024-08-25 19:37 ` Dale
2024-08-25 21:04 ` Michael
2024-08-26 9:36 ` Peter Humphrey
2024-08-26 10:40 ` Alan Mackenzie [this message]
2024-08-26 11:54 ` Michael
2024-08-26 14:49 ` Alan Mackenzie
2024-08-27 16:05 ` Alan Mackenzie
2024-08-27 18:36 ` Michael
2024-08-27 20:50 ` Alan Mackenzie
2024-08-28 14:58 ` [gentoo-user] [Fixed] " Alan Mackenzie
2024-08-28 15:25 ` Dale
2024-08-25 21:07 ` [gentoo-user] " Alan Mackenzie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zsxbq6ZJIhJIIio_@ACM \
--to=acm@muc.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox