Jump to content
Corsair Community

Discuss Link v4.7.0.77 here


Technobeard

Recommended Posts

  • Administrators

This will be the official discussion thread for Link v4.7.0.77.

 

If you'd like to report a bug, please respond to this thread in this format:

  1. Version of your Link software. NOTE: If you're not using v4.7.0.77, please install it and see if the bug has been fixed.
  2. What version of Windows you're using.
  3. Summary - One line / sentence explaining the issue
  4. Detailed description of the issue - This part can be as long as you want. It should be detailed enough so that we can clearly identify the issue and attempt to replicate it.
  5. Attach photos of the issue to the post that help #4.

 

05/16/2017 - Corsair Link Software Update Version v4.7.0.77

 

Changelog:

  • New CPUID SDK backend update for AMD Ryzen support
    • Ryzen support for CPU/MB information
    • Ryzen support for LED DRAM control (Both RGB and Single Color)

     

    [*]Added additional HD fan effects to Lighting Node PRO (Sequential, Marquee, Strobing/Blink, Visor)

    • Included in Firmware update for Lighting Node PRO

     

    [*]Added Rainbow effect for SP fans on Lighting Node PRO

    • Included in Firmware update for Lighting Node PRO

     

    [*]Addressed LED DRAM lighting control for 4-slot X99 systems

    [*]Addressed a specific instance with Lighting Node PRO and some HD Series fans being unresponsive after firmware update

    • Included in Firmware update for Lighting Node PRO

     

Link to comment
Share on other sites

  • Replies 106
  • Created
  • Last Reply

  1. With CL 4.7.0.77 the PCH/ICH SMBus interlocking is totally broken :mad:.
    1. Below you can see only five of the six DIMMs were reported and one of the names was misread.
    2. SIV also detected the ICH10 SMBus controller registers had been changed when it was holding the Global\Access_SMBUS.HTP.Method named mutex so needed to do retries.
    3. The issue is far more likely to happen on systems with have DIMMs with MTS as other utilities (AIDA64+HWiNFO+SIV) are likely to be reading the SMBus of a regular basis.
    4. I am at a loss as to why Corsair failed to find this issue before CL 4.7.0.77 was released :confused:.
    5. As I found the same issues with CPUZ + HWM I contacted the CPUID SDK developers and worked with them to fix the bugs :sunglasse.
    6. Corsair, you need to ask for the fixed CPUID SDK and should make it available as a download :idea:.
    7. I also just noticed there two DIMMs called Temp #1 which is somewhat inappropriate.
    8. After working with the CPUID SDK developers on Tue 20-Jun-2017 I tested a 1.1.6.7 cpuidsdk.dll and using this CL 4.7.0.77 finally reported my system as it should, well almost, staring from Core #2 is rather poor and shows the Corsair testing is :rofl:.
    9. Corsair would be wise to ensure the next CL4 release uses the 1.1.6.7 cpuidsdk.dll or later and I have made them aware of my view.

[*] CL 4.7.0.77 no longer lists my Motherboard and CPUs. Below are the [Home] tabs from CL 4.7.0.77 + CL 4.6.0.86 that clearly show this regression.

[*] The LNP 0.3.72 firmware update got stuck at 35%, see http://forum.corsair.com/forums/showthread.php?p=892389 for how I recovered from this.

[*] CL 4.7.0.77 also failed to display the CPUs and Disks on my Dell 490 when CL 4.6.0.86 did, see http://forum.corsair.com/forums/attachment.php?attachmentid=28260&d=1490084915.

[*] The memory title still also flashes between Hyundai Electronics and Qimonda.

[*] On my HP DL580 G5 CL 4.7.0.77 also failed to report the motherboard and CPUs, further none of the 32 x FB-DIMMs were reported when they used to be, yet another regression :(:. HWM reports them, so it can't be down to the CPUID SDK.

[*] No fix for http://forum.corsair.com/forums/showthread.php?p=854759 is rather poor and as I specified before to fix -ve X and fail to fix -ve Y is a major oversight! When I move the CL 4.7.0.77 window to screen 3 as soon as I release the mouse it jumps back to screen two :(:.

[*] Again rather the DRAM CL4 should display the RAM type, DDR4/DDR3/etc. and it's also silly to display 16.0 as the latency and the .0 should not be there except for DDR1. The number of channels and operating mode should also be displayed, Single/Dual/Triple/Quad and Dual Xeon system has 8 Memory Buffers/Channels.

[*] Yet again CL4 should display it's version number as I find many members fail to specify this or state "latest version" when posting.

[*] Yet again I further feel CL4 should use meaningful names rather than the Temp #1 form it currently uses, same for the fan names.

[*] Yet again reporting the same disk temperature twice is silly and causes confusion for some, see the 2nd #2 in http://forum.corsair.com/forums/showthread.php?p=890673

[*] Yet again can control the H110i + H110iGT pump speed using a Custom Curve be added to CL4?

How do I download new firmware into my CL Minis + H100i + H110iGT?

 

  1. http://forum.corsair.com/forums/showthread.php?p=904256 - I suspect the CL-9011110-WW will replace the CL Mini, does this mean the CL Mini firmware bugs will never be fixed?

Have any of the following firmware bugs been addressed some of which have now been outstanding since 20-Nov-2014? If not on what date are they scheduled to be addressed please?

 

  1. http://forum.corsair.com/forums/showthread.php?t=134621 - Commander Mini will not control fans based on temp sensors
  2. http://forum.corsair.com/forums/showthread.php?p=757703 - Commander Mini + H100i + H80i fan mode register is not returned correctly.
  3. http://forum.corsair.com/forums/showthread.php?t=137364 - Commander Mini + RGB LEDs - Blinking Issue.
  4. http://forum.corsair.com/forums/showthread.php?p=754023 - 10,000 RPM Fans #1 - Corsair suspect it's a firmware bug of 16-Jan-2015.
  5. http://forum.corsair.com/forums/showthread.php?p=709734 - H100i + H80i incorrect colour if you use zero, use 255,1,1 rather than 255,0,0.
  6. http://forum.corsair.com/forums/showthread.php?p=855427 - H100i + H80i you can't use 1,1,1 rather than 0,0,0 as this is not black.
  7. http://forum.corsair.com/forums/showthread.php?p=837226 - CLCC support for 0% PWM or 0 RPM to stop the fans.
  8. http://forum.corsair.com/forums/showthread.php?p=893630 - H110i + H110iGT Custom mode does not work for the pump.

Here is an itemised list of issues which Corsair failed to respond to or address in a timely manor.

  1. http://forum.corsair.com/forums/showthread.php?p=896054 - CL 4.6.0.86 issues.
  2. http://forum.corsair.com/forums/showthread.php?p=890711 - CL 4.5.0.55 issues
  3. http://forum.corsair.com/forums/showthread.php?p=871675 - CL 4.3.0.154 issues
  4. http://forum.corsair.com/forums/showthread.php?p=864149 - CL 4.2.4.25 issues
  5. http://forum.corsair.com/forums/showthread.php?p=851701 - CL 4.2.3.41 issues
  6. http://forum.corsair.com/forums/showthread.php?p=844974 - CL 4.2.2.27 issues - How do I change the TCP port
  7. http://forum.corsair.com/forums/showthread.php?p=841278 - CL 4.2.1.42 issues
  8. http://forum.corsair.com/forums/showthread.php?p=833499 - CL 4.2.0.162 issues
  9. http://forum.corsair.com/forums/showthread.php?p=833532 - CL asking for a reboot when it should not
  10. http://forum.corsair.com/forums/showthread.php?p=837724 - CL4 using a massive amount of TCP transfers
  11. http://forum.corsair.com/forums/showthread.php?p=833695 - Silly driver package name
  12. http://forum.corsair.com/forums/showthread.php?p=833699 - Issues with > 32 CPUs
  13. http://forum.corsair.com/forums/showthread.php?p=834459 - CL4 does not support CSMI RAID
  14. http://forum.corsair.com/forums/showthread.php?p=836506 - CL4 does not support EC Sensors
  15. http://forum.corsair.com/forums/showthread.php?p=837364 - No support for the original Commander.
  16. http://forum.corsair.com/forums/showthread.php?p=845182 - BSOD #1 caused by Corsair supplied AXi PSU/Asetek Cooler kernel mode driver
  17. http://forum.corsair.com/forums/showthread.php?p=898187 - BSOD #2 caused by Corsair supplied AXi PSU/Asetek Cooler kernel mode driver
  18. http://forum.corsair.com/forums/showthread.php?p=896126 - BSOD #3 caused by CL 4.6.0.86 (CPUID SDK) on W10 RS2 Build 15063.
  19. http://forum.corsair.com/forums/showthread.php?p=845092 - 10,000 RPM Fans #2 - no reply
  20. http://forum.corsair.com/forums/showthread.php?p=853869 - 10,000 RPM Fans #3 - no reply
  21. http://forum.corsair.com/forums/showthread.php?p=854759 - To fix -ve X and fail to fix -ve Y is silly
  22. http://forum.corsair.com/forums/showthread.php?p=839550 - H100iV2 and H100iGTX have different firmware
  23. http://forum.corsair.com/forums/showthread.php?p=850509 - CL4 causing high DPC latencies.
  24. http://forum.corsair.com/forums/showthread.php?p=864164 - CL4 causing high DPC latencies after Corsair claim to have fixed it.
  25. http://forum.corsair.com/forums/showthread.php?p=837228 - CLCC support for 0% PWM or 0 RPM to stop the fans.
  26. http://forum.corsair.com/forums/showthread.php?p=881930 - AMD GPU fan speed and temperature information not reported.
  27. http://forum.corsair.com/forums/showthread.php?p=896497 - previous releases can't be downloaded :(:.

Note that some of the entries itemise up to 52 issues and I expect I reported other issues I could add to the list.

 

I feel Corsair should be posting the following as only the latest release is available via the support downloads and some members wish to revert to old versions :idea:

attachment.php?attachmentid=28308&stc=1&d=1490295038

attachment.php?attachmentid=29081&stc=1&d=1495133836

attachment.php?attachmentid=29019&stc=1&d=1494965575attachment.php?attachmentid=29027&stc=1&d=1494974969

attachment.php?attachmentid=28259&d=1490083334

attachment.php?attachmentid=29029&stc=1&d=1494979782

attachment.php?attachmentid=29038&stc=1&d=1495034060

62846448_LNP0.3.72FirmwareUpdatestuck@35.png.4b1d7b38bb39fdc84818da3cc045d09a.png

REX.thumb.png.6bdb520deff21cfafa6ab54fafca58a8.png

RXD.thumb.png.933c308a4d4e9a6c0a30e773c9fba78c.png

REG.thumb.png.9eb45f2b5401bc50c364a5ece22e5558.png

Link to comment
Share on other sites

Just curious but by chance would this enable lighting control over the Vengeance LED non RGB memory or is it permanently stuck to slow flashing ?

 

EDIT

 

Nevermind, I may be slightly blind :p:

 

Ryzen support for LED DRAM control (Both RGB and Single Color)

Link to comment
Share on other sites

Still can't update my Lighting Node Pro without having to open my case, reset it and doing it manually.

 

It just forver gets stuck on:

Bootloader mode

Firmware flash: 0%

 

Really needs sorting.

 

http://i.imgur.com/ZwMLN2O.jpg

Link to comment
Share on other sites

Thanks for that. If they know there is a problem installing lnp firmware, why not just put the firmware in the download section with instructions for those who don't know how to use it? Seems odd to have to ask a forum member for this file rather than just download it using the corsair website.
Link to comment
Share on other sites

Fans 1,3,4 are my Corsair 750D case fans. Fan 2 is my CPU fan. Corsair still can't figure out their own hardware with their software. What does that tell you?

 

Ever since version 4.6.086 and this version I have Link showing duplicate fans 5,6,7,8. If Corsair is unwilling or unable to fix this, could they please include the fix for the H110i pump running at lower RPM until startup in the 4.5.055 version. Then I will have no pump worries and four fans reported as it should be.

Link to comment
Share on other sites

PERFECT!!!!! Thank you Corsair!!. just what the doctor ordered :).

 

1. All updated with out a hitch

2. All items present and correct in link

3. LOVING THE NEW LIGHTING MODES

4.Corsair Link FOR THE WIN!!!!!! well done guys

Link to comment
Share on other sites

I'm done with Corsair Link products. It takes me hours every time I want to update because something always breaks

 

I can't update my Lighting Node Pro. The new firmware got stuck on 73% for half an hour after which I decided to cancel it.

Now it won't update at all unless I completely restart my PC, after which it gets stucks before even reaching 50%.

 

This means every single time I want to update the Lighting Node Pro, I need to completely open my PC case, get my Lighting Node Pro from under my PSU shroud,

which requires me to remove my watercooling reservoir, which requires me to completely drain my waterloop.

 

So, in order to fix Corsair's software every time it updates I need to put in hours of work just to update it.

When I put together this build I did not expect that I had to be able to reach the Lighting Node Pro physically in order to update it, because why the hell would I?. Why is a simple firmware update so damn difficult?

 

I'm done with this. Next time this happens, I'm not just draining my waterloop but removing all Corsair Link hardware, taking it back to the store, and replacing it.

 

 

Edit: also no matter how annoying red-ray's posts may be to Corsair (and I know they are very annoying), from the perspective of users on this sub forum it seems he's putting in more work on Crosair's products than Corsair is, yet you're completely ignoring everything he says even though he makes very good points

Link to comment
Share on other sites

v4.7.0.77: mobo fans are OK, i see my DDR sticks, but i do not see AX860i (connected to H80i)

v4.6.0.86, v4.5.0.55, v4.3.0.154: mobo fans give wrong readings, DDR sticks are not detected, however AX860i is seen.

 

Why detecting DRAM masks power supply?

 

To do the testing between each test i cleaned Link files, reg and devices manually.

 

Thanks

Link to comment
Share on other sites

Came across this thread and registered to throw out my feedback.

 

CL has been a good experience, certainly better than some competing software I have used.

 

I have a custom water cooled set up with much of the hardware controlled by the Corsair Commander Mini.

 

The bad:

1. Have had a couple of system crashes during Windows startup after adding devices to the CCM.

2. PWM pump was not getting a proper PWM signal from #1 fan header on CCM. I could control it up to approximately 70% speed but it would not run any faster, even when set to maximum speed. A fan connected to this fan header has full speed control.

 

The good:

1. Custom fan speed curves on all of my connected fans.

2. Properly controls fans that are connected to an 8-way PWM hub.

3. Fan speed control based on temp sensors connected to CCM works perfectly.

4. LED lighting control works perfectly with none of the blinking that I have seen reported here.

 

Something I would like to see is the ability to type in the desired fan speeds and temperatures. It would ease the process of creating a custom fan curve.

Link to comment
Share on other sites

Why does version 4.7.0.77 require admin privileges to run now?

 

I am not surprised, but this not even mentioned in the release notes :mad:.

 

The reason this is needed is that the GUI now interacts directly with the CPUID SDK for some reason, when before it did not. Corsair why has this been changed?

 

I can tell this is so as both CorsairLink4 (the GUI) + CorsairLink4.Service have the locks open as below.

 

Looking the RT_MANIFEST this also now specifies "highestAvailable" rather than "asInvoker", see https://msdn.microsoft.com/en-us/library/bb384691.aspx

 

attachment.php?attachmentid=29016&d=1494962628

attachment.php?attachmentid=29055&stc=1&d=1495088886

RT_MANIFEST.png.f5a68da5c1dd286444f561cdbe119269.png

Link to comment
Share on other sites

Is admin privileges necessary? Why would they change this only now? I can see this being an annoyance for non admin users...

 

Because the GUI now uses the CPUID SDK it needs admin in order to be able to start the CPUID SDK driver (the cpuz143 service).

 

My guess is that Corsair did this to be able to report AMD GPUs, but this is just a hunch as the release notes don't mention this.

 

Assuming I am correct Corsair there is a far better solution, but I suspect the CL4 developers may not be aware of it. When the GUI starts the CPUID SDK it should only specify CPUIDSDK_CONFIG_USE_DISPLAY_API in the initialisation call and I suspect CPUIDSDK_CONFIG_USE_EVERYTHING is specified. That said I don't know if you need admin to call ATIADL. Note I have never used the CPUID SDK, but Franck gave me the cpuidsdk.h header file when I was helping investigate some locking issues and have a fair idea of what is possible.

 

I just ran SIV on this system without admin rights and it reported all 4 x GTX 980 so know does not need admin. It would be interesting to know what happens with AMD GPUs. As you can see below all the GPUs were reported, but the rest of the information is rather limited.

 

I just checked and you don't need admin for ATIADL either and that Corsair may have implemented a suboptimal solution :bigeyes:.

 

1380534527_SIV64XwithoutAdmin.thumb.png.1e35a3529deea4c792503c0eacbdde1f.png

RCA.thumb.png.ae840ecd227a968bb97a0c01c2bc6b37.png

Link to comment
Share on other sites

I have the exact same issue, except my Lighting Node Pro always gets stuck on 0%. I even left it on over night to see if it would update and it didn't.

 

I've tried everything from uninstalling Corsair Link, removing anti-virus software, even re-installing Windows and this damn thing refuses to update.

 

Like you, I have to pull my PC apart every time to manually update it - which in itself is an absolute pain in the ****.

 

I don't hold out much hope for it getting fixed anytime soon, which is a shame since when it's working I love it.

 

I'm done with Corsair Link products. It takes me hours every time I want to update because something always breaks

 

I can't update my Lighting Node Pro. The new firmware got stuck on 73% for half an hour after which I decided to cancel it.

Now it won't update at all unless I completely restart my PC, after which it gets stucks before even reaching 50%.

 

This means every single time I want to update the Lighting Node Pro, I need to completely open my PC case, get my Lighting Node Pro from under my PSU shroud,

which requires me to remove my watercooling reservoir, which requires me to completely drain my waterloop.

 

So, in order to fix Corsair's software every time it updates I need to put in hours of work just to update it.

When I put together this build I did not expect that I had to be able to reach the Lighting Node Pro physically in order to update it, because why the hell would I?. Why is a simple firmware update so damn difficult?

 

I'm done with this. Next time this happens, I'm not just draining my waterloop but removing all Corsair Link hardware, taking it back to the store, and replacing it.

 

 

Edit: also no matter how annoying red-ray's posts may be to Corsair (and I know they are very annoying), from the perspective of users on this sub forum it seems he's putting in more work on Crosair's products than Corsair is, yet you're completely ignoring everything he says even though he makes very good points

Link to comment
Share on other sites

Well, this is my first post on this forum and I have to say that I haven't been having a very positive experience with CORSAIR link. Corsair support hasn't been much help to me at all either and IF I had to do it all over again I'd stay as far away from CORSAIR LINK as possible. Alas, I've wasted hundreds of dollars on it now so for what it's worth I will attempt to include a couple of screen shots in this post. The new update removed so much that it now looks like I hardly own any Corsair hardware at all! To be clear, I'm running Corsair Airflow RAM cooling fans X 2, 128GB of Corsair Dominator RAM, Corsair Mini Commander, and the Corsair HX1000i PSU. Check out these screen shots and tell me what's missing.

 

 

 

 

 

FIRMWARE NOT APPLICABLE???? ARE YOU KIDDING ME??? I had to buy the mini commander just to get my lights on my fans to turn blue and what a 3 day nightmare that turned out to be! Because I live in Canada I had to wrestle the Commander from the hands of the Customs officers and pay the brokerage so that in the end I paid around $130.oo Canadian just to have blue lights on my Corsair RAM fans. Additionally, can anybody please tell me what this digital cable is all about? The COMMANDER has four ports to plug the digital stuff into. I plugged one cable into my PSU and that was it ... The grommet went straight into the PSU and I can't get it out unless I open the PSU (which will more than likely violate the warranty). So that's left dangling now. When did CORSAIR start manufacturing such cheap junk? The interface used to list all my fans. Those are gone now along with the scroll bar -- not that it made any difference considering the fan control actually controlled precious little properly in the first place. Folks, this thing just keeps on going from bad to worse and I can never get any straight answers from CORSAIR except ... BUY MORE... BUY MORE!!! Not in your life. FIX IT FIRST.

77264041_LINK001.thumb.png.f1a5a24f71e4518fe85a16206bf9e9b8.png

2015991956_LINKTWO.thumb.png.f265ec806b64d5c5479d8540128aaaba.png

354082848_LINK3.thumb.png.6271358f79ef2ee5f31fbb2ba5f9fb12.png

Link to comment
Share on other sites

Yay a new upgrade - almost wet myself when I saw my GPU show up finally. Just one small issue - my CPU cores are now number 2-7 which is a bit odd.

 

I have the same issue. Not big deal but numbering was fine in previous update.

Capture.thumb.JPG.6152fe513f3d8af5ee945f4a93428f6a.JPG

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...