From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] New machine: Contents of display are offset around 2 inches from the left hand side.
Date: Thu, 22 Aug 2024 16:54:19 +0000 [thread overview]
Message-ID: <ZsdtO1eO5QyMBr1t@ACM> (raw)
Hello, Gentoo.
Thanks to everybody who helped me get my video going in the other thread.
I've now got a more puzzling problem: Every time I boot up my new
machine, the 1920x1080 pixel display is offset by around 2 inches from
the left hand side (and aroun 1 cm from the top). It still appears to be
1920x1080 pixels (more precisely, 240 columns x 67 lines of 16x8
characters), but it's not filling the screen.
The screen itself is attached to a KVM box, and it works just fine on the
old machine. So it's not the physical display which is at fault. It's
an around 10 year old Samsung digital monitor, not some ancient CRT, or
anything like that. It's interface is a DVI cable.
I seem to remember it filled the screen when it was new (on Monday).
Part of my efforts to make the video work (see other thread) involved
giving the kernel the drm.edid_firmware parameter. This parameter is
intended to compensate for the display/KVM box/whatever failing to supply
the correct EDID information to the PC. One of the settings I tried
involved the offsets from the left and top mentioned above. But somehow
they seem to have got stuck in the machine. It seems the BIOS has saved
the offsets in the CMOS or something. I don't know how to undo these
saved settings.
Would somebody please help me on this, too.
Thanks!
--
Alan Mackenzie (Nuremberg, Germany).
next reply other threads:[~2024-08-22 16:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 16:54 Alan Mackenzie [this message]
2024-08-22 21:44 ` [gentoo-user] New machine: Contents of display are offset around 2 inches from the left hand side 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
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=ZsdtO1eO5QyMBr1t@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