From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Date: Sun, 8 Sep 2024 21:19:51 +0100 [thread overview]
Message-ID: <5163114a-7037-4dd6-8946-11a1acd8d1da@youngman.org.uk> (raw)
In-Reply-To: <2198427.irdbgypaU6@rogueboard>
On 08/09/2024 10:15, Michael wrote:
> The placement of DIMMs depends on the MoBo, its manual would show in which
> slot should DIMM modules be added and the (maximum) size of each stick the
> MoBo can cope with. Normally OEMs provide a list of tested memory brands and
> models for their MoBos (QVL) and it is recommended to buy something on the
> list, rather than improvise.
Both old and new mobos are, iirc, 4 x 32GB, and they just swapped the
RAM over. But again iirc, the new mobo they supplied had two colours of
ram slots, something like "black, red, black, red". To me that's obvious
- both sticks in one colour! So - and I guess it was an apprentice who
didn't know what he was doing - just shoved the ram in the first two slots.
Two major blunders from a shop - a brand new mobo won't boot - the FIRST
suspect is an out-of-date bios. And then the second blunder - don't
check the ram is in the right slots. That's one shop I certainly won't
visit again.
(The only reason I asked a shop to fix it was because I didn't have an
old chip so couldn't boot the board to upgrade the bios to work with the
chip I had ...)
Cheers,
Wol
next prev parent reply other threads:[~2024-09-08 20:20 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 23:28 [gentoo-user] Package compile failures with "internal compiler error: Segmentation fault" Dale
2024-09-04 0:12 ` [gentoo-user] " Grant Edwards
2024-09-04 0:39 ` Dale
2024-09-04 4:16 ` corbin bird
2024-09-06 20:15 ` Dale
2024-09-06 23:17 ` Michael
2024-09-07 3:02 ` Dale
2024-09-07 22:12 ` Wols Lists
2024-09-08 1:59 ` Dale
2024-09-08 13:32 ` Michael
2024-09-08 9:15 ` Michael
2024-09-08 20:19 ` Wol [this message]
2024-09-04 7:53 ` Raffaele Belardi
2024-09-04 4:26 ` [gentoo-user] " Eli Schwartz
2024-09-04 10:48 ` [gentoo-user] " Dale
2024-09-04 11:05 ` Frank Steinmetzger
2024-09-04 11:21 ` Dale
2024-09-04 15:57 ` Peter Humphrey
2024-09-04 19:09 ` Grant Edwards
2024-09-04 21:08 ` Frank Steinmetzger
2024-09-04 21:22 ` Grant Edwards
2024-09-04 21:53 ` Dale
2024-09-04 22:07 ` Grant Edwards
2024-09-04 22:14 ` Dale
2024-09-04 22:38 ` Michael
2024-09-05 0:11 ` Dale
2024-09-05 8:05 ` Michael
2024-09-05 8:36 ` Dale
2024-09-05 8:42 ` Michael
2024-09-05 10:53 ` Dale
2024-09-05 11:08 ` Michael
2024-09-05 11:30 ` Dale
2024-09-05 18:55 ` Frank Steinmetzger
2024-09-05 22:06 ` Michael
2024-09-06 0:43 ` Dale
2024-09-06 12:21 ` Michael
2024-09-06 21:41 ` Frank Steinmetzger
2024-09-07 9:37 ` Michael
2024-09-07 16:28 ` Frank Steinmetzger
2024-09-07 17:08 ` Mark Knecht
2024-09-14 19:46 ` Dale
2024-09-15 22:29 ` Frank Steinmetzger
2024-09-16 10:24 ` Dale
2024-09-07 22:48 ` Wols Lists
2024-09-08 9:37 ` Michael
2024-09-05 9:08 ` Frank Steinmetzger
2024-09-05 9:36 ` Michael
2024-09-05 10:01 ` Frank Steinmetzger
2024-09-05 10:59 ` Dale
2024-09-04 14:21 ` Grant Edwards
2024-09-04 11:37 ` Dale
2024-09-04 14:23 ` Grant Edwards
2024-09-04 15:58 ` Peter Humphrey
2024-09-04 19:28 ` Dale
2024-09-25 20:41 ` 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=5163114a-7037-4dd6-8946-11a1acd8d1da@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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