Groups | Search | Server Info | Login | Register
Groups > alt.comp.hardware.pc-homebuilt > #43928
| From | Paul <nospam@needed.invalid> |
|---|---|
| Newsgroups | alt.comp.hardware.pc-homebuilt |
| Subject | Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator |
| Date | 2025-05-06 03:37 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <vvce7q$2fger$1@dont-email.me> (permalink) |
| References | (17 earlier) <-x6dnVAvt9B1wjj6nZ2dnZfqn_ednZ2d@giganews.com> <vo444f$3cak0$1@dont-email.me> <uEGdneWBa8BOWFz6nZ2dnZfqnPudnZ2d@giganews.com> <vpslmi$3npna$1@dont-email.me> <_pKcnXl3vv53y4T1nZ2dnZfqnPWdnZ2d@giganews.com> |
On Mon, 5/5/2025 8:25 PM, bad sector wrote:
> On 2/28/25 10:45, Paul wrote:
>> On Fri, 2/28/2025 9:19 AM, bad sector wrote:
>>
>>> The saga continues..
>>>
>>> Couldn't get the 30-day refund at amazon because my sun's death preoccupied the family and I missed the deadline by 3 days. So it went back to the shop on RMA, after some weeks they advised that 'although it posted OK' they were sending me a new one. More weeks later I pulled on their chain and they replied _NIL-STOCK_ but that I could get a comparable board instead (some ROG gaming board): declined. I have a feeling that an upgrade version of the same board might become the replacement candidate (xY70e?).
>>>
>>
>> The time to do a build and test it, is pretty limited.
>>
>> It's one of the reasons I spent extra time "single sourcing"
>> builds in the past. So a complete kit of parts would
>> arrive on Day 0 and the testing could begin as soon
>> as I could find time to assemble it.
>>
>> It's a lot harder to be timely on stuff, if the sellers
>> are sending items "as they have them". Your effective
>> test window can be a lot shorter that way. But these
>> days, I guess that's unavoidable. Newegg.ca, I don't think they
>> single ship any more. They seem to operate in dribble mode.
>>
>> Paul
>
> Having just received the long-awaited edcc cards testing revealed that booting hangs on the DRAM (yellow) LED if either #3 or #4 ddr5 slot is occupied. I got identical cards as reported in my ECC thread but can only use them in slots #1 & #2 which is unaceptable. UP TO HERE with Asus sending me defective or returned scrap.
>
> Come to think of it... when a customer buys a new product and that product breaks in use but during the warranty period then repair service under warranty applies. HOWEVER if the product is defective on receipt, considering that what the customer had paid for was a NEW and defect-free product, the only acceptable remedy is ANOPTHER NEW (sealed) product and not a repaired one or a previously delivered to some other customer good or reopaired one!
>
A-Bus B-Bus
| |
A1 ------ ------ B1
| |
A2 ------ ------ B2 <=== fill the end of each bus first, A2 and B2 are to be filled first.
When laid out on the board, they are arranged as two buses, one after the other.
The first pair, have no common electrical signals with the second pair.
And as in the other diagram, A2 and B2 are to be filled first. The CPU
is the source of the "A" and "B" parts.
B -----------------+--+
| |
CPU A1 A2 B1 B2
| |
A --------+--+
But when they're drawn as buses, they look like the first drawing.
The A2 and B2 sticks, have programmable terminators. If the bus
impedance was 55 ohms or 35 ohms, it is up to the BIOS to set the
termination inside the memory chip to match that. Then, there are
no reflections off the end of the bus, and the signal quality is
undisturbed. When four sticks are present, and especially at high
speed, the "compromise" terminator settings (a percentage type
setting), the compromise is not sufficient for 5600 or 6400 speeds.
Apparently only lower bus speed choices settle in time with four sticks.
On older memory standards, the resistors were external, and right
after the A2 and B2 stick. The resistors were not programmable,
and if the engineer was wrong about the value, then "too bad".
Paul
Back to alt.comp.hardware.pc-homebuilt | Previous | Next — Previous in thread | Next in thread | Find similar
The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-30 11:36 -0500
Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-30 12:32 -0500
Re: The build is ON Paul <nospam@needed.invalid> - 2025-01-30 14:49 -0500
Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-30 17:21 -0500
Re: The build is ON John B Smith <crasso@nycap.rr.com> - 2025-01-31 15:41 -0500
Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-31 16:11 -0500
Re: The build is ON Paul <nospam@needed.invalid> - 2025-01-31 21:09 -0500
Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-01-31 23:32 -0500
Re: The build is ON Paul <nospam@needed.invalid> - 2025-02-01 05:31 -0500
Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-02-01 07:31 -0500
Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-02-01 08:39 -0500
Re: The build is ON Paul <nospam@needed.invalid> - 2025-02-01 12:52 -0500
Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-02-05 10:18 -0500
Re: The build is ON Paul <nospam@needed.invalid> - 2025-02-05 12:47 -0500
Re: The build is ON bad sector <forgetski@_INVALID.net> - 2025-02-06 08:49 -0500
Re: The build ..chatGPT scrapped the board and/or the CPU Paul <nospam@needed.invalid> - 2025-02-06 16:01 -0500
Re: The build ..chatGPT scrapped the board and/or the CPU bad sector <forgetski@_INVALID.net> - 2025-02-06 20:20 -0500
Re: The build ..chatGPT scrapped the board and/or the CPU Paul <nospam@needed.invalid> - 2025-02-07 00:02 -0500
Re: The build ..x870e ProArt-Creator in Limbo bad sector <forgetski@_INVALID.net> - 2025-02-28 09:19 -0500
Re: The build ..x870e ProArt-Creator in Limbo Paul <nospam@needed.invalid> - 2025-02-28 10:45 -0500
Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-04 07:41 -0500
Re: The build ..x870e ProArt-Creator, Scene-1, take N Paul <nospam@needed.invalid> - 2025-03-04 13:37 -0500
Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-21 12:49 -0400
Re: The build ..x870e ProArt-Creator, Scene-1, take N Paul <nospam@needed.invalid> - 2025-03-21 13:52 -0400
Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-21 14:39 -0400
Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-21 16:17 -0400
Re: The build ..x870e ProArt-Creator, Scene-1, take N Paul <nospam@needed.invalid> - 2025-03-21 23:18 -0400
Re: The build ..x870e ProArt-Creator, Scene-1, take N bad sector <forgetski@_INVALID.net> - 2025-03-22 07:52 -0400
Re: The build ..x870e ProArt-Creator, Scene-1, take N Paul <nospam@needed.invalid> - 2025-03-22 13:23 -0400
Re: The build ..x870e ProArt-Creator, Scene-1, take N John B. Smith <crasso@verizon.net> - 2025-03-23 09:09 -0400
The never-ending Asus FUBAR ___Re: The build ..x870e-Creator bad sector <forgetski@_INVALID.net> - 2025-05-05 20:25 -0400
Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator Paul <nospam@needed.invalid> - 2025-05-06 03:37 -0400
Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator bad sector <forgetski@_INVALID.net> - 2025-05-06 18:13 -0400
Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator Paul <nospam@needed.invalid> - 2025-05-06 19:17 -0400
Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator bad sector <forgetski@_INVALID.net> - 2025-05-10 09:46 -0400
Re: The never-ending Asus FUBAR ___Re: The build ..x870e-Creator Paul <nospam@needed.invalid> - 2025-05-10 13:58 -0400
csiph-web