From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together?
Date: Sat, 8 Jun 2024 12:46:05 -0500 [thread overview]
Message-ID: <fecdcf0e-c2e3-8461-9c79-8f312881f38a@gmail.com> (raw)
In-Reply-To: <4573508.LvFx2qVVIh@tp>
Frank Steinmetzger wrote:
> Am Samstag, 8. Juni 2024, 04:05:17 MESZ schrieb Dale:
>
>
>>> DisplayPort supports daisy-chaining. So if you do get another monitor some
>>> day, look for one that has this feature and you can drive two monitors
>>> with
>>> one port on the PC.
>> That's something I didn't know. I wondered why they had that when a
>> HDMI port is about the same size and can handle about the same
>> resolution. It has abilities HDMI doesn't. Neat. :-D
> Polemically speaking, HDMI is designed for the concerns of the MAFIA (Music
> and Film Industry of America) with stuff like DRM. DisplayPort is technically
> the better protocol, for example with more bandwidth and it is open. There was
> news recently that the HDMI forum would not allow AMD to implement HDMI 2.1 in
> its open source driver, which means no 4K 120 Hz for Linux users.
That sucks about HDMI. Next time I buy a video card, I need to get one
with display port outputs. It seems more Linux friendly. :-D
>> Sadly, the CPU I got is for processing only, no video support it says.
> So you got an F model?
I got the X model. It's supposed to be a wiiiittttttle bit faster. o_O
>
>>> But what I also just remembered: only the ×16 GPU slot and the primary M.2
>>> slots (which are often one gen faster than the other M.2 slots) are
>>> connected to the CPU via dedicated links. All other PCIe slots are behind
>>> the chipset. And that in turn is connected to the CPU via a PCIe 4.0×4
>>> link. This is probably the technical reason why there are so few boards
>>> with slots wider than ×4 – there is just no way to make use of them,
>>> because they all most go through that ×4 bottleneck to the CPU.
>>>
>>> ┌───┐ 5.0×4 ┌───┐ 4.0×4 ┌─────────┐ ┌───┐
>>> │M.2┝=======┥CPU┝━━━━━━━┥ Chipset ┝━━━┥M.2│
>>> └───┘ └─┰─┘ └─┰─────┰─┘ └───┘
>>>
>>> 5.0×16┃ ┃ ┃
>>>
>>> ┌─┸─┐ ┌────┸─┐ ┌─┸────┐
>>> │GPU│ │PCIe 1│ │PCIe 2│
>>> └───┘ └──────┘ └──────┘
>>> […]
>> Nice block diagram. You use software to make that?
> Yes, vim’s builtin digraph feature. O:-)
>
I was hoping so. Doing that by hand would take a LOT of time. I never
could figure out vim. I use nano on command line and Kwrite in a GUI.
Care to guess which I really prefer??? LOL
I got the little m.2 thing today. It's a lot smaller than I expected.
A whole lot smaller. It's fairly tiny actually. They look bigger in
pictures or on video. This reminds me of the discussion on the number
of transistors on a chip. I bet they packed tight in there. I bought a
heat sink that goes on each individual chip, one on controller, one on
data chip, two if it has two data chips. Anyway, it has only two chips
so I got extra heat sinks. LOL They fairly large since the mobo has
nothing on top of them. I got plenty of room. That said, anyone else
notice they make heat sinks for those things that have heat pipes and
itty bitty fans?? O_O It does make them run cool tho. :/ I like my
little heat sinks better. Pretty good size and no moving parts. They
come in a couple colors. Linky.
https://www.ebay.com/itm/254119864180
Oh, for those reading this. The data controller chip is a little
thinner than the data chip. I confirmed that on mine. If you don't use
a heatsink that has a thicker pad for that, it leaves a gap and the
controller chip doesn't make contact which means it runs hotter. As I
mentioned earlier, the controller seems to produce more heat so it needs
the heatsink more than the data chip. On videos, some people use a
additional pad to make up the difference on the controller chip. I
noticed on a couple heatsinks, they mention the difference and show they
use a pad that makes full contact on both chips. It looks like the
thermal pad is thicker and more squishy. One I saw looks like it is
just a little thicker on the controller end.
I guess Monday will be the big day, IF, big IF, they don't get hung up
in the local USPS sorting hub. That place is a little better now but
some packages still get hung up down there.
Dale
:-) :-)
next prev parent reply other threads:[~2024-06-08 17:46 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 5:38 [gentoo-user] Mobo, CPU, memory and a m.2 thingy. This work together? Dale
2024-06-02 7:54 ` Wols Lists
2024-06-02 13:27 ` Dale
2024-06-02 13:42 ` Peter Humphrey
2024-06-02 14:01 ` Dale
2024-06-02 14:03 ` Alan Mackenzie
2024-06-02 15:11 ` Dale
2024-06-02 15:51 ` Peter Humphrey
2024-06-02 17:54 ` Dale
2024-06-15 6:53 ` Dale
2024-06-15 9:53 ` Michael
2024-06-15 11:01 ` Dale
2024-06-15 12:29 ` Michael
2024-06-15 21:41 ` Dale
2024-06-15 23:07 ` Mark Knecht
2024-06-16 1:34 ` William Kenworthy
2024-06-16 4:55 ` Dale
2024-06-16 8:40 ` Michael
2024-06-16 8:54 ` Michael
2024-06-16 13:35 ` Dale
2024-06-16 14:19 ` Peter Humphrey
2024-06-16 16:14 ` Dale
2024-06-16 23:28 ` Wols Lists
2024-06-17 0:40 ` Dale
2024-06-16 15:47 ` Rich Freeman
2024-06-16 16:30 ` Dale
2024-06-17 9:37 ` Dale
2024-06-16 12:59 ` Frank Steinmetzger
2024-06-16 14:44 ` Mark Knecht
2024-06-16 16:19 ` Dale
2024-06-15 11:18 ` Peter Humphrey
2024-06-15 12:01 ` Dale
2024-06-15 15:28 ` Peter Humphrey
2024-06-15 16:55 ` Michael
2024-06-15 19:19 ` Peter Humphrey
2024-06-02 14:03 ` Rich Freeman
2024-06-02 19:41 ` Wols Lists
2024-06-03 23:57 ` Frank Steinmetzger
2024-06-03 3:21 ` Dale
2024-06-03 7:42 ` Alan Grimes
2024-06-03 9:12 ` Dale
2024-06-03 9:31 ` Rich Freeman
2024-06-03 11:06 ` Dale
2024-06-03 11:29 ` Rich Freeman
2024-06-03 15:17 ` Dale
2024-06-03 16:22 ` Rich Freeman
2024-06-03 19:28 ` Dale
2024-06-04 6:44 ` Dale
2024-06-04 9:49 ` Rich Freeman
2024-06-04 11:56 ` Dale
2024-06-04 13:15 ` Rich Freeman
2024-06-04 18:34 ` Dale
2024-06-04 18:58 ` Rich Freeman
2024-06-04 20:09 ` Dale
2024-06-04 19:05 ` Mark Knecht
2024-06-04 20:27 ` Dale
2024-06-04 20:37 ` Mark Knecht
2024-06-04 21:03 ` Dale
2024-06-04 21:24 ` Mark Knecht
2024-06-04 21:36 ` Mark Knecht
2024-06-04 22:11 ` Dale
2024-06-04 22:26 ` Mark Knecht
2024-06-04 22:58 ` Dale
2024-06-04 22:49 ` Wol
2024-06-05 0:22 ` Dale
2024-06-06 21:12 ` Frank Steinmetzger
2024-06-08 2:05 ` Dale
2024-06-08 9:39 ` Frank Steinmetzger
2024-06-08 13:40 ` Meowie Gamer
2024-06-09 21:41 ` Frank Steinmetzger
2024-06-09 22:24 ` Meowie Gamer
2024-06-08 17:46 ` Dale [this message]
2024-06-08 20:48 ` Michael
2024-06-08 22:41 ` Dale
2024-06-09 9:07 ` Michael
2024-06-09 10:06 ` Dale
2024-06-09 15:05 ` Frank Steinmetzger
2024-06-09 22:13 ` Dale
2024-06-09 22:49 ` Michael
2024-06-09 23:11 ` Dale
2024-06-10 0:29 ` Rich Freeman
2024-06-10 4:26 ` Dale
2024-06-10 9:17 ` Michael
2024-06-10 10:03 ` Dale
2024-06-10 13:37 ` William Kenworthy
2024-06-11 0:04 ` Frank Steinmetzger
2024-06-11 3:46 ` Dale
2024-06-04 10:19 ` Dale
2024-06-04 11:32 ` Rich Freeman
2024-06-04 12:03 ` Dale
2024-06-04 13:19 ` Rich Freeman
2024-06-03 10:02 ` byte.size226
2024-06-03 11:18 ` Dale
2024-06-03 11:07 ` [gentoo-user] " MasterP
2024-06-03 11:40 ` Wols Lists
2024-06-03 15:34 ` Dale
2024-06-04 7:59 ` Wols Lists
2024-06-03 23:45 ` [gentoo-user] " Frank Steinmetzger
2024-06-05 22:46 ` Mark Knecht
2024-06-06 3:54 ` Dale
2024-06-06 11:08 ` Michael
2024-06-06 16:36 ` Dale
2024-06-15 5:00 ` Dale
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=fecdcf0e-c2e3-8461-9c79-8f312881f38a@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