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] [Fixed] New machine: Contents of display are offset around 2 inches from the left hand side.
Date: Wed, 28 Aug 2024 10:25:20 -0500	[thread overview]
Message-ID: <cb866844-759c-6fdf-2902-cb0f24535f77@gmail.com> (raw)
In-Reply-To: <Zs86-YrNXjwa12rj@ACM>

Alan Mackenzie wrote:
> Hello, everybody.
>
> On Tue, Aug 27, 2024 at 20:50:01 +0000, Alan Mackenzie wrote:
>> On Tue, Aug 27, 2024 at 19:36:49 +0100, Michael wrote:
>>> On Tuesday, 27 August 2024 17:05:26 BST Alan Mackenzie wrote:
>>>> 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:
> [ .... ]
>
>>>> 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.
> Well, I now have that new HDMI->DVI adapter, and my video now works!
> Both the console and X Windows (running XFCE) work fully.  There must
> have been a dodgy connection in my old adapter, possibly in a timing
> twisted pair, or something like that.
>
> As always, after solving such a problem, one wonders why it took so long
> to fix.  I was convinced it was something in the motherboard's firmware,
> and it took an actual demonstration of it working on an HDMI monitor to
> persuade me otherwise.
>
> Anyhow, now to finish setting the machine up, in particular getting an
> email server installed and configured.
>
> Many thanks to the people who helped me diagnose the problem,
> particularly Michael and Dale.
>
> [ .... ]
>
>> -- 
>> Alan Mackenzie (Nuremberg, Germany).
>


Very welcome.  You may have noticed that HUGE thread where Micheal and I
were banging at a monitor on my new rig.  Turns out, bad cable, adapter
or both.  New monitor, two new monitors later actually, and I still had
one monitor winking at me.  New cable with no adapter fixed that.  I
might add, second monitor still has the adapter and works just fine. 

I also had a hard drive once that was spitting out some sort of error. 
Turned out, cable wasn't making a good connection.  Unplug, re-plug and
carry on.  I might add, after recent move of all my hard drives to a new
case, some drives are having that error again.  I detect new cables in
their future.  May unplug and re-plug as a test tho, just in case. 

This is why I try to have extra cables hanging around in a box
somewhere.  It seems cables tend to have issues.  I think part of it is
the cheap way they make them.  I have several XTar VC4 battery
chargers.  The power cables to those things is always giving me fits. 
It's hard to find a quality cable that doesn't cost a arm and a leg. 

Glad you got it going.  :-D

Dale

:-)  :-) 


  reply	other threads:[~2024-08-28 15:25 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
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 [this message]
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=cb866844-759c-6fdf-2902-cb0f24535f77@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