From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 38751158083 for ; Sun, 8 Sep 2024 13:32:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 04321E2A2A; Sun, 8 Sep 2024 13:32:48 +0000 (UTC) Received: from crocodile.elm.relay.mailchannels.net (crocodile.elm.relay.mailchannels.net [23.83.212.45]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 90345E2A14 for ; Sun, 8 Sep 2024 13:32:47 +0000 (UTC) X-Sender-Id: thundermail|x-authsender|confabulate@kintzios.com Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 5379F840296 for ; Sun, 8 Sep 2024 13:32:46 +0000 (UTC) ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1725802365; a=rsa-sha256; cv=none; b=cgY00IxEIB41pEe67cuEdrroHahUA0eZMEJHXlYzP/CkSL+Q2AsUDhJJusEJ3f5wQHWf+W B0XlVr0D+QY8apdOXrxmqjMjQFDXMxPJhGRo4kR5J/E/67o639aRopW6oLmU4LB98v0sFL /JQ277adcSyqHN9Beyaz56tB1s9fdJmBFyJjWWTujCpb1yTw/Q5nJSsD5J18T60CGEadr8 U1BhW2Y09QICwAVawyJNls1OPkONbMHoDtH7I9nYdtbxkHa44X/NiSoPbZw4K+ed2D9QcH UlBjISvnpwXtGhO59SfKW58VGewm6gHU0u3fDvMjeX4xpjDHoFNMQ+fyIDiWuA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1725802365; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=LDv+d5NSjt91W2R0T7OdVJmAySBeYJjxmCUZkfLIj44=; b=u6AARa6rUfmg2Y8WgfVvA0ZTsZvmg5JSpflOwcPzC6kj4+55AKcaaXqFR2qGI+V7JL3qj1 SnkskAtzCSOBAG0kZ9kn+cY1M+CPuKGI5p07CjW5ox9FDqls++BpS9u4CBzZAyUAmt3EDd MHi6d8nTbo7qUGM4Cf1KUYyHNViQDSefxNkeDNFxg2IfGzlAVCayoN4A48m3uflE5rPiW9 ImdOupXk5CDheuoBQKdU2jWH2uWyCu1Z0uXYa8pZzph8Nl7dECl/q3QTnu82kjtWuS6qdb ChZnj7MJu7hKMLv42WQnDxDyZdpynG+fh7ZUTf8oWogSAVzEvNnOcAjoVksUHw== ARC-Authentication-Results: i=1; rspamd-77766c4bb8-d6ffv; auth=pass smtp.auth=thundermail smtp.mailfrom=confabulate@kintzios.com X-Sender-Id: thundermail|x-authsender|confabulate@kintzios.com X-MC-Relay: Neutral X-MailChannels-SenderId: thundermail|x-authsender|confabulate@kintzios.com X-MailChannels-Auth-Id: thundermail X-Interest-Squirrel: 295edc77287f6874_1725802365549_3257819305 X-MC-Loop-Signature: 1725802365549:1079878632 X-MC-Ingress-Time: 1725802365549 Received: from mailclean11.thundermail.uk (mailclean11.thundermail.uk [149.255.60.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.96.75.102 (trex/7.0.2); Sun, 08 Sep 2024 13:32:45 +0000 Received: from cloud238.thundercloud.uk (cloud238.thundercloud.uk [149.255.62.116]) by mailclean11.thundermail.uk (Postfix) with ESMTPS id 3A3B61E0003 for ; Sun, 8 Sep 2024 14:32:43 +0100 (BST) Authentication-Results: cloud238.thundercloud.uk; spf=pass (sender IP is 217.169.3.230) smtp.mailfrom=confabulate@kintzios.com smtp.helo=rogueboard.localnet Received-SPF: pass (cloud238.thundercloud.uk: connection is authenticated) From: Michael 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 Message-ID: <8424240.T7Z3S40VBb@rogueboard> In-Reply-To: References: <8c26be16-d033-ea3f-06e1-a9ce84cbbafb@gmail.com> <00018d86-ec80-433b-94d2-994b6fba43e1@youngman.org.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart10528877.nUPlyArG6x"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-PPP-Message-ID: <172580236190.233961.8751399231794549823@cloud238.thundercloud.uk> X-PPP-Vhost: kintzios.com X-Rspamd-Queue-Id: 3A3B61E0003 X-Rspamd-Server: mailclean11 X-Spamd-Result: default: False [-1.61 / 999.00]; SIGNED_PGP(-2.00)[]; MID_RHS_NOT_FQDN(0.50)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; ONCE_RECEIVED(0.10)[]; MX_GOOD(-0.01)[]; R_SPF_ALLOW(0.00)[+mx]; FUZZY_BLOCKED(0.00)[rspamd.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:34931, ipnet:149.255.60.0/22, country:GB]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; R_DKIM_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; NEURAL_HAM(-0.00)[-0.977]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DMARC_POLICY_ALLOW(0.00)[kintzios.com,none]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[gentoo-user@lists.gentoo.org]; HAS_REPLYTO(0.00)[confabulate@kintzios.com] X-Rspamd-Action: no action X-Archives-Salt: c7154546-eb4b-4d3e-9c03-0cda0dee061c X-Archives-Hash: f611fbdce276229b4fe909b09d48c7a7 --nextPart10528877.nUPlyArG6x Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Michael To: gentoo-user@lists.gentoo.org Reply-To: confabulate@kintzios.com Date: Sun, 08 Sep 2024 14:32:42 +0100 Message-ID: <8424240.T7Z3S40VBb@rogueboard> In-Reply-To: MIME-Version: 1.0 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.). --nextPart10528877.nUPlyArG6x Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmbdp3oACgkQseqq9sKV ZxndUg//YMTrLRERA9P4trbx28mADuPURSjhKrlP/A6YdzOgjQvCL8lLJON2EoXn XpGIvdWnW/OgfD798//DUkA5j8ewwx1n/1Me+izJCpUukP8DhYqhnL+vW9J4SbYk svGd1/stKjAx/zmoMdwe0qpQPXcs2pgt7/HBa4As18rEOzDvVqRxNzi4twHq8EqS OfISTrXKZlq91Y4UPdO4W7sCD+pJ+eyOX8VdMmtYMXLXo1t7lEDYKq+dwXfw7YaP ijl3XoDeyJHIEBrYILtGzjQCy2B8J+q3icAMfjktKBWIhcoSCYfwL+3X7pAgCV5o UXadaioI7yLFy60oW/TFCSH7czH/hE/9AsV4TYIFn+9ijok1qlKtXME3AUzYCzrh S4hIX+u75weuwQmN4eOGazik7JUZkIrJr7C2aiOjwd1bcGZ4M2j5uMBRW/gx3GTq f/ZWGso0eq8tAO5RrZmLsx5rR/5NOx+0+lwkWE0orNyWNFbM4x++6p7avXENgUS+ bk3q6fb0QUGegvxWsIN7HkzMrWTwcs5rJmPg0n+Bl+2SHDMXPb3wqdV8yLEkZQ7z asQnThg3tBlT7jXOSwqun/2t/mwLJrWqppITop2Qv39affADiFBtmWbQirr8LadO 7dHtwLh5GLNfg+PzpaNJ7u1R3L72HnBJd1M+xypHsDzZMEGExjE= =7r6n -----END PGP SIGNATURE----- --nextPart10528877.nUPlyArG6x--