|
|
Post by shark5060 on Oct 27, 2018 21:24:18 GMT
Hey there,
just wanted a quick info if the RGB-Ness of the memory is supported by SIV.
I just want to narrow it down if it's an issue with my RAM or something else, since it isn't detected in iPOO or Link software, but SIV seems to be able to see the RAM, yet if I change the colors nothing happens.
|
|
|
|
Post by siv on Oct 28, 2018 8:08:09 GMT
Ideally you would have posted the SIV Initial Screen + SPD Summary + Link Status, as you have not I will have to guess what is happening and wonder if you have a Z390 motherboard.
I have CMR32GX4M4A2666C16 in my ASUS X299 Sage system which SIV supports, but I think the RGB PRO starts CMW and the control protocol is different, but I don't have any so so can't be sure and suspect SIV can't control your DIMM LEDs.
Please see spams://siv.boards.net/thread/14/running-same-time-corsair-iPOO
|
|
|
|
Post by shark5060 on Oct 28, 2018 12:23:19 GMT
Oh sorry.
Here are all the screens:
spams://public.shark5060.net/siv/siv_initial.PNG
spams://public.shark5060.net/siv/siv_link_status.PNG
spams://public.shark5060.net/siv/siv_spd_summary.PNG
spams://public.shark5060.net/siv/siv_cue_control.PNG
spams://public.shark5060.net/siv/siv_cl4_control.PNG
I have tried to disable the corsair service linked in your other thread, but that didn't help much either.
On the Status -> Link LED screen, whenever I change a color and press Apply it reverts back to the default one.
Part Number of the memory is: CMW32GX4M4C3000C15
|
|
|
|
Post by siv on Oct 28, 2018 12:49:52 GMT
Thank you and given your system has an X99 PCH and the DIMMs are connected via the CPU IMC SMBuses then I would have hoped CL4/iPOO would work, did either of them report the DIMM temperatures? I have done some more checking and it seems that the new RGB PRO (CMW) use a totally different LED control protocol to the RGB LED (CMR) DIMMs I have. I would need to update SIV to support them and to sensibly do this would need some in one of my systems. It's a shame you got RGB PRO (CMW) rather than RGB LED (CMR), could you exchange them as if you did SIV should be able to control them. I also noted that Link Status just reported DIMM 1 LEDs so SIV did not find any supported LED DIMMs. When supported DIMMs are found the name includes the SMBus address as in the attached. Out of interest does iPOO report your CLCC + AX860i? Attachments:
|
|
|
|
Post by shark5060 on Oct 28, 2018 12:58:03 GMT
iPOO doesn't report ANY devices.
Link 4 reports that AX860i is controlled by iPOO and reports DIMM Temperatures.
spams://public.shark5060.net/siv/siv_icue.PNG
spams://public.shark5060.net/siv/siv_link4.PNG
CLCC control via SIV still works though, as well as the AX860i
EDIT: After a bit of searching in the Corsair forums seems I am not alone with my problem (iPOO not detecting the DIMMs), so I opened a support ticket. Seems my Firmware on the DIMMs is not working correctly and has to be re-flashed.
|
|
|
|
Post by siv on Oct 28, 2018 13:22:49 GMT
- Thank you for the screen shots and CL4 only reported 3 of the 4 DIMM temperatures which is suboptimal, I wonder if TSOD is enabled, what does Menu->Hardware->Chipset->Chipset MCH report for the Intel Core i7 Integrated Memory Controller 0 Channel 0 Thermal Control.
- I have no idea as to why iPOO failed to report any DIMM temperatures and feel it should have.
- I wonder, does Menu->Tools->DIMM Status report any retries or failures.
- As I suspected iPOO does not support the CLCC, but might report the AX860i if it was USB connected.
- CL4 is dumb and should realise the AX860i is CLCC attached and therefor not supported by iPOO.
- I have no idea as to why CL4 did not report the CLCC and feel it should have.
I suspect in time I may add RGB PRO DIMM support to SIV, but currently have no plans to do this. Can you return the RGB PRO and get RGB LED DIMMs? |
|
|
|
Post by shark5060 on Oct 28, 2018 17:19:15 GMT
Thanks for your great help siv.
I might return them, even though I really like the look of the DIMMs =)
1. spams://public.shark5060.net/siv/siv_mch.PNG - also I just checked again, and Link now reported 4/4 temps. Strange.
2. It did actually display the correct DIMM incl. temperatues and everything on the FIRST boot. Never after it.
3. Yes, there are some Retries: spams://public.shark5060.net/siv/siv_dimm.PNG
4. Might, but I will not undo my cable management, since it works wonderfully in SIV =D
5. Agree.
6. Maybe because the Service is disabled?
EDIT: I will try running the memory on something like 2400 instead of 3000 and see if that makes a difference. Maybe some strange effects with the X99 Board.
EDIT2: okay, even with no overclocking present and the Memory running at 2166 speeds it makes no difference.
|
|
|
|
Post by siv on Oct 28, 2018 18:22:18 GMT
Thank you for the screen shots and now it makes more sense. From Chipset MCH we can see TSOD is active and from DIMM Status that SIV has done some retries.
Basically when TSOD is active then sometimes program SMBus transfers collide with the hardware TSOD SMBus reading and I suspect this is what happened when CL4 only reported 3 of the 4 DIMM temperatures. SIV has code to detect these collisions and recover them, it took me a while to figure out what was happening, but since I figured out the root cause all was been OK, see spam://forum.corsair.com/v3/showthread.php?t=159149
AFAIK iPOO + CL4 don't have code to deal with TSOD being enabled so unless you can disable TSOD (also called CLTT) in the BIOS they are likely to have issues reporting any DIMM temperatures and/or controlling the LEDs.
BTW You also need to ensure SPD Write is enabled in the BIOS to be able to control the DIMM LEDs.
Changing the DIMM speed should not affect DIMM SMBus access at all and I have never known it to.
|
|
|
|
Post by shark5060 on Oct 28, 2018 18:59:35 GMT
SPD Write is enabled, that was one of the first troubleshooting steps I tried.
I don't have any option for this setting in my BIOS. Sadly.
So it seems I either would have to switch my DIMMs or see if Corsair gets their shit together and produce some working software.
Thank you for your help.
|
|
|
|
Post by siv on Oct 29, 2018 18:21:20 GMT
After pondering I felt SIV should report that your DIMMs are Not Supported, please can you check that 5.35 Beta-12 says this on Link Status?
|
|
|
|
Post by shark5060 on Oct 29, 2018 20:07:00 GMT
Corsair CMW32GX4M4C3000C15 [Not Supported] (#0)
Corsair support was helpful as a moldy cheese ... as usual.
|
|
|
|
Post by siv on Oct 30, 2018 0:39:08 GMT
Corsair support was helpful as a moldy cheese ... as usual. Thank you checking and I am not at all surprised. After pondering the update of the DIMM RGB PRO firmware I guess this is done via the SMBus and if so then given that TSOD/CLTT is active I would not be at all surprised if the update fails. |
|
|
|
Post by shark5060 on Oct 30, 2018 15:58:33 GMT
I'll get a MSI Godlike Gaming from a friend for testing in a few weeks (he's upgrading). Let's see if I can reproduce the issues with that mainboard or if I can at least disable those settings in the BIOS there.
Should I keep you updated or is not neccessary, since you deemed the DIMM incompatible anyways?
|
|
|
|
Post by siv on Oct 30, 2018 17:38:40 GMT
Should I keep you updated or is not neccessary, since you deemed the DIMM incompatible anyways? I am unclear what you mean. The RGB PRO DIMMs should work in your ASUS X99-Deluxe and if I had a pair here I expect I could make SIV control them just as it does my RGB LED DIMMs. My concern is with CL4 + iPOO, given CL4 sometimes only reports 3 of the 4 DIMMs I suspect that it's SMBus I/O code goes wonky when TSOD/CLTT is enabled and this is likely to mean updating the firmware will fail as it's likely the hardware will do a TSOD/CLTT SMBus read half way through the firmware update. I don't know if the MSI Godlike Gaming will have TSOD/CLTT enabled, but I do know the ASUS X99-Deluxe II does not and feel it's down to the luck of the draw. |
|
|
|
Post by shark5060 on Dec 6, 2018 1:54:02 GMT
Well then.
I've installed my MSI X99A Godlike Gaming today and the memory works like a charm. Gets detected by iPOO and everything.
So it is totally a Mainboard fault here.
|
|
