public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
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: Sun, 25 Aug 2024 14:37:37 -0500	[thread overview]
Message-ID: <40afec53-5902-f2f4-1abd-71b0ffb71677@gmail.com> (raw)
In-Reply-To: <ZsuCA7SNbp3tkN7A@ACM>

Alan Mackenzie wrote:
> Hello, Dale
>
> On Sun, Aug 25, 2024 at 13:28:14 -0500, Dale wrote:
>> Alan Mackenzie wrote:
>>> Somehow I don't think that will work (which doesn't mean I won't try it).
>>> There is something in the motherboard which is throwing off the desired
>>> resolution by those extra 192 horizontal pixels, even in the BIOS.
>> Do you have x11-apps/xrandr installed?  If you do, see what this says. 
> I didn't, but I do now.  After trying (and failing) to run it on the
> console, I tried in X-Windows (the display of which is miserably
> unstable at the moment).
>
>> xrandr --listmonitors
>
>> This is mine:
>
>> root@Gentoo-1 / # xrandr --listmonitors
>> Monitors: 3
>>  0: +*DP-2 1920/698x1080/393+0+1080  DP-2
>>  1: +DP-1 1920/698x1080/393+0+0  DP-1
>>  2: +DP-7 1920/1150x1080/650+1920+1080  DP-7
>> root@Gentoo-1 / #
> That's one tremendous monitor you've got on DP-7.  :-)
>
> I've got just the one monitor.  I got back:
>
> 0: +*HDMI-A-0 1920/521x1080/293+0+0  HDMI-A-0

If I read that and my thinking is right, that is what it should be.  I
don't completely understand everything that output is saying.  But, I
technically have three monitors.  I have two in front of me that have
different displays.  Those are DP2 and DP-2.  The third, DP-7, is my TV
that I watch.  It goes to a splitter which goes to a TV in my bedroom
and one in the living room.  I can cook, clean etc while watching TV. 
DP-7 is to the right of DP-2 which may be why it shows something larger. 

Some of this monitor stuff is a bit confusing. 


>> DP-2 is my primary display and if you have only one monitor, should be
>> the only line for you but might be DP-1 instead.  Micheal might can
>> explain this better, or even more correctly, but I think the important
>> part for this is where mine says +0+.  I think, just think, if yours
>> says something like +192+ instead of 0, that might be a clue.  If it
>> says 0 as it should, then this may be the wrong track to look down. 
>> What I'm wondering, is the monitor set to show a blank, or black,
>> section on that side for some reason.  This could very well not be the
>> case tho.  If it shows correctly like mine does, then ignore this and
>> know that isn't causing the problem at least. 
> No, I've got the +0+, too.
>
>> This is a odd problem.  I don't think I ever saw this even during the
>> old CRT days.  o_O
> 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.  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.
>
>> Dale
>> :-)  :-) 
>

Ahhhhh.  If it does it in the BIOS, it's either a monitor or video card,
or mobo if video is built in, problem.  If a monitor isn't right in the
BIOS screen, odds are it won't be when booted either.  Can you install a
video card and test?  If it works, mobo has a video driver problem.  If
not, could be monitor or cables or something. 

At least we know one thing it isn't.  ;-) 

Dale

:-)  :-) 


  reply	other threads:[~2024-08-25 19:37 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 [this message]
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=40afec53-5902-f2f4-1abd-71b0ffb71677@gmail.com \
    --to=rdalek1967@gmail.com \
    --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