From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Date: Sun, 08 Sep 2024 14:32:42 +0100 [thread overview]
Message-ID: <8424240.T7Z3S40VBb@rogueboard> (raw)
In-Reply-To: <d6e54945-9b27-1892-83e8-550b4ec4768d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3263 bytes --]
On Sunday 8 September 2024 02:59:04 BST Dale wrote:
> Wols Lists wrote:
> > On 04/09/2024 01:39, Dale wrote:
> >> I've seen that before too. I'm hoping not. I may shutdown my rig,
> >> remove and reinstall the memory and then test it for a bit. May be a
> >> bad connection. It has worked well for the past couple months tho.
> >> Still, it is possible to either be a bad connection or just going bad.
> >
> > I've had *MOST* of my self-built systems force me to remove and
> > replace the ram several times before the system was happy.
> >
> > And when a shop "fixed" my computer for me (replacing a mobo that
> > wasn't broken - I told them I thought it needed a bios upgrade and I
> > was right!) they also messed up the ram. Memory is supposed to go in
> > in matched pairs. So what do they do? One stick in each pair of slots
> > - the thing ran like a sloth on tranquillisers! As soon as I realised
> > what they'd done and put both sticks in the same pair, it was MUCH
> > faster.
> >
> > Cheers,
> > Wol
>
> I noticed on the set I had to return, the serial numbers were in
> sequence. One was right after the other. I don't know if that makes
> them a matched set or if they run some test to match them.
Both. They run a test, if one fails in their hands as opposed to yours, they
pick up the next module and test that. So you typically end up with numbers
in a matched kit which are close enough.
> From my understanding tho, each 'bank' or pair has to be a matched set.
> I did finally find a set of four but it is a different brand. From what
> I read to tho, ASUS trains itself each time you boot up. It finds the
> best setting for each set of memory. It does say that it is usually set
> to a slower speed tho when all four are installed.
It depends if your MoBo comes with 'daisy chain' or 'T topology' RAM slot
configuration. Most consumer grade come with 'daisy chain' configuration and
ASUS may also have an "Optimem" function/feature as they call it.
With 'daisy chain' you should achieve higher max. frequency if you fit 2
matched DIMMs in the slots the manual suggests (typically B2 & A2), than if
you fit 4 DIMMs to achieve the same total RAM size.
With 'T topology' you'll achieve a lower frequency with 2 DIMMs, but a higher
frequency with 4 DIMMs at the same total RAM size, than you would with a
'daisy chain' MoBo.
The ASUS "Optimem" is some automagic run by the firmware of their 'daisy
chain' MoBos in terms of voltage and signal sequencing, to do the best job it
can when you have 4 DIMMs installed.
> Just have to wait
> and see I guess. Oh, when I boot the first couple times with new
> memory, it takes quite a bit longer on the BIOS boot screen. After a
> couple times, it doesn't seem to take so long. Not sure what, but it
> does something.
The memory controller on the CPU probes the memory module(s) by varying
voltage and latency until it achieves a reliable result. If you have enabled
DOCP as advised here and if provided in the BIOS also selected the RAM
frequency of the DIMMs you bought, then the probing ought to take less time:
https://www.asus.com/support/faq/1042256/
Unless ... there's something wrong with the system (power, faulty RAM modules,
buggy BIOS, etc.).
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-08 13:32 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 [this message]
2024-09-08 9:15 ` Michael
2024-09-08 20:19 ` Wol
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=8424240.T7Z3S40VBb@rogueboard \
--to=confabulate@kintzios.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