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: Fri, 23 Aug 2024 13:44:36 -0500 [thread overview]
Message-ID: <6edb62dc-0687-8a7f-2e95-a6b628d9dac0@gmail.com> (raw)
In-Reply-To: <25IEDS4F.JMIS3PQP.2Y54LNV6@VQTCSHWL.2DVUZ2NJ.H4SPCE3X>
Jack wrote:
> On 2024.08.23 12:21, Alan Mackenzie wrote:
>> I'm a bit fed up with all of this. It's a new machine, but the
>> motherboard, an MSI B650 Tomahawk Wifi, has been around a fair while and
>> bugs in its BIOS ought to have been fixed by now.
>
> Just because the latest available BIOS might have fixed a problem does
> not mean the physical mobo you bought actually has the latest BIOS
> installed. Have you checked, just to be compulsively certain?
>
> I say that because not too many years ago, I bought an MSI mobo and
> Ryzen CPU (from the same vendor) and I ended up having to buy (eBay)
> an older CPU just to boot the machine so I could update the BIOS to
> one which could handle the new CPU, because the installed BIOS was too
> old.
>
>
When I built my new rig, one of the first things I did after making sure
it wasn't bad out of the box, update the BIOS. Mine was like 2 or 3
versions behind. It booted and all but I did update anyway, just to
prevent weirdness later. Turns out I had enough weirdness with a old
monitor so I needed to rid myself of some for sure.
I might add, I had to do the same thing on my old system when I first
built it. I'm not sure on my very first rig. I think newer mobos will
update now even without a CPU. At least mine seems claims that anyway.
Dale
:-) :-)
next prev parent reply other threads:[~2024-08-23 18:44 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 [this message]
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=6edb62dc-0687-8a7f-2e95-a6b628d9dac0@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