From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Date: Wed, 4 Sep 2024 16:53:27 -0500 [thread overview]
Message-ID: <031346ad-5c83-aea5-6ba1-6656094e5540@gmail.com> (raw)
In-Reply-To: <vbaj20$101u$1@ciao.gmane.io>
Grant Edwards wrote:
> On 2024-09-04, Frank Steinmetzger <Warp_7@gmx.de> wrote:
>> Am Wed, Sep 04, 2024 at 07:09:43PM -0000 schrieb Grant Edwards:
>>> […]
>>> I plugged them in alongside the recently purchased pair. Wouldn't
>>> work. Either pair of SIMMs worked fine by themselves, but the only way
>>> I could get both pairs to work together was to drop the clock speed
>>> down to about a third the speed they were supposed to support.
>> Indeed that was my first thought when Dale mentioned getting another
>> pair. I don’t know if it’s true for all Ryzen chips, but if you use
>> four sticks, they may not work at the maximum speed advertised by
>> AMD (not counting in overlcocking). If you kept the settings to Auto
>> you shouldn’t get problems, but RAM may work slower then.
> Yea, I thought auto should work, but it didn't. I had to manually
> lower the RAM clock speed to get all four to work at the same
> time. The BIOS screens were a bit mind-boggling (very high on
> graphics, dazzle, and flash -- very low on usability). So it's
> possible I didn't really have auto mode correctly enabled.
>
>> OTOH, since you don’t do hard-core gaming or scientific
>> number-crunching, it is unlikely you will notice a difference in
>> your every-day computing.
> In my case I compared an "emerge" that took several minutes, and it
> took significantly longer with the lower RAM clock speed. I decided I
> was better off with fewer GB of faster RAM.
>
>
At one point, I looked for a set of four sticks of the memory. I
couldn't find any. They only come in sets of two. I read somewhere
that the mobo expects each pair to be matched. Thing is, things
change. My mobo may work different or something or they figured out
some better coding. The downside, my mobo is a somewhat older tech.
Given the number of components on each stick, it's pretty amazing they
work at all. I recall our conversation about the number of transistors
on a CPU. I suspect memory is right up there with it. 32GBs on a stick
is a lot. I think they have larger sticks too. That means even more.
Also, mine puts on a fancy light show. It has LEDs that change colors.
Annoying at times. Needs a off switch. LOL
My emerge -e world is still chugging along. Not a single failure yet.
I started Qbittorrent and it complained about files. I did run fsck on
the file system tho and it did fix a few things, like it always does.
It always finds something to improve on. I told QB to force a recheck,
within minutes, it was off to the races again. It appears to be fixing
any bad files. Sort of neat that it can do that.
Dale
:-) :-)
P. S. With my TV not connected, my monitor situation went weird. I
guess when I get the new rig back to normal, it will work like it did
before.
next prev parent reply other threads:[~2024-09-04 21:53 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
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 [this message]
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=031346ad-5c83-aea5-6ba1-6656094e5540@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