Administrators Technobeard Posted February 10, 2017 Administrators Share Posted February 10, 2017 This will be the official discussion thread for Link v4.5.0.55. If you'd like to report a bug, please respond to this thread in this format: Version of your Link software. NOTE: If you're not using v4.5.0.55, please install it and see if the bug has been fixed.What version of Windows you're using.Summary - One line / sentence explaining the issueDetailed 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.Attach photos of the issue to the post that help #4. 02/10/2017 - Corsair Link Software Update Version 4.5.0.55 Changelog: Added support for Lighting Node PROAdded new product support for the CORSAIR Lighting Node PROAdded Mimic color animation - display animation for selected lighting effect in the user interfaceFixed Vengeance LED modules when only one unit was controlled (Z170/Z270 motherboards only)Condensed DRAM layout to display modules with the same SPD in one section.Performance and stability improvements, minor bug fixes Link to comment Share on other sites More sharing options...
gilad215 Posted February 10, 2017 Share Posted February 10, 2017 [*]Performance and stability improvements, minor bug fixes ????? Are we worthy? http://www.corsair.com/en/support/downloads Link to comment Share on other sites More sharing options...
red-ray Posted February 10, 2017 Share Posted February 10, 2017 Fixed Vengeance LED modules when only one unit was controlled (Z170/Z270 motherboards only) Failing to support Kaby Lake is outrageous :mad:. Looking at my earlier post all it takes to fix this is a later CPUIDSDK.dll so one should be attached to the first post in this thread. It's also totally failing to report the 2 x Corsair Vengeance LED modules, is this the intended fix? :rofl: One HDD + my NVMe SSD are still not reported. They are JBOD and not members of a CSMI RAID array. Fixed in 1.1.5.5 cpuidsdk.dll. Most of this all down to the CPUIDSDK being ancient. It's the same as came with CL 4.3.0.154 and even I am lost for works as to how incompetent this is. NZXT ship a far later CPUIDSDK that supports Kaby Lake and so should Corsair :bigeyes:. CL4 should display it's version number as I find many members fail to specify this or state "latest version" when posting. Eight temperatures should be reported rather than three. Fixed in 1.1.5.5 cpuidsdk.dll. I further feel CL4 should use meaningful names rather than the Temp #1 form it currently uses, same for the fan names. VBAT is not ~2.0 volts and this needs to be fixed. Fixed in 1.1.5.5 cpuidsdk.dll. I suspected many of these issues would be trivial for a competent software engineer to fix and that I should prove this, see http://forum.corsair.com/forums/showthread.php?p=891269. 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 From the SIV screen shot you should see all correctly reported. SIV can also control both DIMM LEDs based on a temperature, when will CL4 be able to do this? SIV can control the H110i + H110iGT pump speed using a Custom Curve, when will CL4 be able to do this?The CPUID SDK that comes with CL CL 4.5.0.55 is ancient and as a result my DIMMs and NVMe Disks still don't get reported. Why was such an old CPUID SDK released? The interlocking semantics are still incorrect and given I reported this on 09-Aug-2016 why? I also e-mailed the product manager who did not even reply to my e-mail. I suspect it's a one line change and can be tested using SIV 5.12 or later. It might have been half fixed, but when I open Configure Fan then pressed [Apply] a few times [Link Test] reported @ 00:29:50.894 seq 40 5 = CreateFile( \\?\usb#vid_1b1c&pid_0c02#7289_1.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18} ) Access is denied. so I expect the CL4 locking semantics are still incorrect in some of the CL4 code. See http://forum.corsair.com/forums/showthread.php?p=892949 for the details. No fix for http://forum.corsair.com/forums/showthread.php?p=854759 is pathetic and as I specified before to fix -ve X and fail to fix -ve Y is incompetent! How do I download new firmware into my CL Minis + H100i + H110iGT? 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? http://forum.corsair.com/forums/showthread.php?t=134621 - Commander Mini will not control fans based on temp sensors http://forum.corsair.com/forums/showthread.php?p=757703 - Commander Mini + H100i + H80i fan mode register is not returned correctly. http://forum.corsair.com/forums/showthread.php?t=137364 - Commander Mini + RGB LEDs - Blinking Issue. 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. 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. 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. http://forum.corsair.com/forums/showthread.php?p=837226 - CLCC support for 0% PWM or 0 RPM to stop the fans. http://forum.corsair.com/forums/showthread.php?p=893630 - H110i + H110iGT Custom mode does not work for the pump. Some fixes appear to get promised, but then never seem to be released. This is a known issue with a fix coming. This was posted over 24 months ago on 02-Feb-2015 so I would have expected it to be fixed by now. On what date is the fix expected? On 03-Feb-2015 Corsair stated: I believe it requires a firmware update to be corrected. It should be in the next Corsair Link drop, or the one after. There have been at least 9 CL drops since then :(:. So just so you guys know, we're aware of this bug, but because of the issues we've seen with H100i/H80i and the current version of C-Link, this has been backburnered to get more pressing problems fixed. Posted on 03-Nov-2014, over 27 months ago. If you'd like to report a bug, please respond to this thread. I have done this for all the CL4 releases and Corsair have not responded to most of these posts. Why is this and why should I bother to report issues? Here is an itemised list of issues which Corsair failed to respond to or address in a timely manor. http://forum.corsair.com/forums/showthread.php?p=871675 - CL 4.3.0.154 issues http://forum.corsair.com/forums/showthread.php?p=864149 - CL 4.2.4.25 issues http://forum.corsair.com/forums/showthread.php?p=851701 - CL 4.2.3.41 issues http://forum.corsair.com/forums/showthread.php?p=844974 - CL 4.2.2.27 issues - How do I change the TCP port http://forum.corsair.com/forums/showthread.php?p=841278 - CL 4.2.1.42 issues http://forum.corsair.com/forums/showthread.php?p=833499 - CL 4.2.0.162 issues http://forum.corsair.com/forums/showthread.php?p=892949 - CL4 locking semantics only half fixed. http://forum.corsair.com/forums/showthread.php?p=833532 - CL asking for a reboot when it should not http://forum.corsair.com/forums/showthread.php?p=837724 - CL4 using a massive amount of TCP transfers http://forum.corsair.com/forums/showthread.php?p=833695 - Silly driver package name http://forum.corsair.com/forums/showthread.php?p=833699 - Issues with > 32 CPUs http://forum.corsair.com/forums/showthread.php?p=834459 - CL4 does not support CSMI RAID http://forum.corsair.com/forums/showthread.php?p=836506 - CL4 does not support EC Sensors http://forum.corsair.com/forums/showthread.php?p=836736 - NVMe Disks are not Reported http://forum.corsair.com/forums/showthread.php?p=837364 - No support for the original Commander. http://forum.corsair.com/forums/showthread.php?p=845182 - BSOD caused by Corsair supplied AXi PSU/Asetek Cooler kernel mode driver http://forum.corsair.com/forums/showthread.php?p=845092 - 10,000 RPM Fans #2 - no reply http://forum.corsair.com/forums/showthread.php?p=853869 - 10,000 RPM Fans #3 - no reply http://forum.corsair.com/forums/showthread.php?p=854759 - To fix -ve X and fail to fix -ve Y is incompetent http://forum.corsair.com/forums/showthread.php?p=839550 - H100iV2 and H100iGTX have different firmware http://forum.corsair.com/forums/showthread.php?p=850509 - CL4 causing high DPC latencies. http://forum.corsair.com/forums/showthread.php?p=864164 - CL4 causing high DPC latencies after Corsair claim to have fixed it. http://forum.corsair.com/forums/showthread.php?p=837228 - CLCC support for 0% PWM or 0 RPM to stop the fans. Note that some of the entries itemise up to 52 issues and I expect I reported other issues I could add to the list. Link to comment Share on other sites More sharing options...
red-ray Posted February 10, 2017 Share Posted February 10, 2017 Condensed DRAM layout to display modules with the same SPD in one section. Condensed DRAM layout is appropriate, but should be able to see the whole of BLT4G3D1869DT2TXRG in the title ;):. Only 7 of my 8 DIMMs are reported :mad:. Given we worked out what the issue was in August 2016 and fixed the CPUID SDK for a CL to be released 6 months later and not have the fix shows the CL4 team is incompetent. How did you decide on the ordering? Please can you explain why this is appropriate? I suspect the GPUs should also be condensed. The RM PSUs should be #1 and #2. As the DIMMs are associated with the CPUs DIMMs should be between the CPUs and GPUs. Link to comment Share on other sites More sharing options...
red-ray Posted February 10, 2017 Share Posted February 10, 2017 Condensed DRAM layout to display modules with the same SPD in one section. I was wondering what is meant to happen when the DIMMs have different SPD information so ran CL 4.5.0.55 on a system with different DIMMs and got as below. There are two screen shots as the name oscillates between the two different DIMM makers :eek: which I was not expecting. This this the intended behaviour? If not what should it be? If the flashing is intentional the release notes should specify this as it's rather unusual. I suspect this has not been tested at all. The ordering is again unexpected. Link to comment Share on other sites More sharing options...
red-ray Posted February 10, 2017 Share Posted February 10, 2017 Performance and stability improvements, minor bug fixes [*]Performance and stability improvements, minor bug fixes ????? You are wise to question if anything has been fixed as at least one trivial but important fix has either not been done or incorrectly done. The interlocking semantics are still incorrect. I expect the fix is to interpose the OpenFile() and AcquireLock() calls to adhere to the specification at the top of page 4 of the Corsair Link Lock Library documentation that is AcquireLock() should be done before the OpenFile(). The interlocking semantics are still incorrect and given I reported this on 09-Aug-2016 why? I also e-mailed the product manager who did not even reply to my e-mail. I suspect it's a one line change and can be tested using SIV 5.12 which typically reports the issue in < 2 seconds. Link to comment Share on other sites More sharing options...
hhh2260 Posted February 11, 2017 Share Posted February 11, 2017 1. Version of your Link software: 4.5.0.55 2. What version of Windows you're using: Win10 64bit 3. Summary - One line / sentence explaining the issue: Vengeance LED ram not working on Asus Z270E MOBO and 7700K I used the previous version. At least one lane of the ram can be controlled and it worked fine. Now I updated CL there is no LED option at all and neither of the ram LEDs work. Link to comment Share on other sites More sharing options...
fher Posted February 11, 2017 Share Posted February 11, 2017 1. Corsair Link v4.5.0.55 2. Windows 10 3. Corsair Link does not recognize Intel Kaby Lake 7700k Processor temperature 4. The software does not show the mother board, cores and RAM. I tried with diffferent versions, reinstallation and i got the same result. It seems that the library cpuidsdk.dll is outdated. 5. Link to comment Share on other sites More sharing options...
Marmite_II Posted February 11, 2017 Share Posted February 11, 2017 Hi Corsair Fans 1) Corsair Link v4.5.0.55 2) Win10 Pro 64bit 3) Corsair Link does not recognize Intel Kaby Lake 7700k Processor temperature 4) No Kaby Lake 7700k CPU support? 5) Z270 chipset I really don't know what link-software should show or not? Link to comment Share on other sites More sharing options...
red-ray Posted February 11, 2017 Share Posted February 11, 2017 4. The software does not show the mother board, cores and RAM. I tried with diffferent versions, reinstallation and i got the same result. It seems that the library cpuidsdk.dll is outdated. You should specify which motherboard, better still add your full PC specs to your profile as specified in http://forum.corsair.com/forums/showthread.php?t=77167 A later cpuidsdk.dll will fix the Kaby Lake reporting, but may not address the motherboard. I advise you to check what HWM reports and if needed work with the HWM/CPUIDSDK developers to get support for your motherboard added to HWM. This will mean an even later cpuidsdk.dll will be able to report your motherboard. Link to comment Share on other sites More sharing options...
red-ray Posted February 11, 2017 Share Posted February 11, 2017 I really don't know what link-software should show or not? Of course it should report the Kaby Lake core temperatures and as I showed in my earlier post it would if Corsair shipped a later CPUIDSDK with it. Link to comment Share on other sites More sharing options...
red-ray Posted February 11, 2017 Share Posted February 11, 2017 Vengeance LED ram not working on Asus Z270E MOBO and 7700K I used the previous version. At least one lane of the ram can be controlled and it worked fine. Now I updated CL there is no LED option at all and neither of the ram LEDs work. I get the same effect so it's useful to know it not just me that get's the issue. 2. It's also totally failing to report the 2 x Corsair Vengeance LED modules I am wondering if it's just the LED revision 0x03 DIMMs that aren't reported. Please will you run my SIV utility and post the [sPD] + [sMB Bus] panels so I can check? On my system with revision 0x03 LEDs I get as below. If anyone reading this has LED DIMMs that CL 4.5.0.55 does report please will you post the above two panels so I can try and deduce why. BTW You should add yourl PC specs to your profile Link to comment Share on other sites More sharing options...
PrEzi Posted February 11, 2017 Share Posted February 11, 2017 Wow... just WOW! I've given up on Corsair. I'll never buy or recommend a product from them again. Made a mistake once. Shame on me. Link to comment Share on other sites More sharing options...
BipolarBear Posted February 12, 2017 Share Posted February 12, 2017 I think Corsair Link as a device is becoming redundant anyway. Look at all the new motherboards: 6+ pwm fan headers, 1 or even 2 rgb headers, plus multiple temp sensors... my next upgrade CL will be coming out of my system and never going back in. Link to comment Share on other sites More sharing options...
fyew-jit-tiv Posted February 12, 2017 Share Posted February 12, 2017 Has commandline support been added to this revision? Link to comment Share on other sites More sharing options...
eeek Posted February 12, 2017 Share Posted February 12, 2017 I don't have a bug to report, but would it be possible in future releases to be able to move where items are? As an example, my hard drive aren't in any order that I know. Even if it mimicked how windows listed my drives, I would be happy. I'd be even happier if I could drag and drop them where I want. Attached is an example. I'd like to move my 950 to the top, the 840 next, and the Seagate to the bottom. I am aware of the configure tab, but I'd rather see it here. Link to comment Share on other sites More sharing options...
red-ray Posted February 12, 2017 Share Posted February 12, 2017 I don't have a bug to report, but would it be possible in future releases to be able to move where items are? I suspect this is the wrong solution and a better solution would be for CL4 to order the disks by drive letter and also display the drive letters. After pondering this I feel that NVMe disks should always be before the others so have just changed SIV 5.16 to do this. The order is now NVMe -> CSMI RAID -> SATA -> USB. I feel CL4 should do the same, but don't hold you breath, especially for CSMI RAID support to be added. Again displaying two temperatures is silly and only the highest one should be used. On the [home] tab this is not too confusing, but having 5 disk temperatures on [configure] when you only have 3 drives is. Link to comment Share on other sites More sharing options...
gilad215 Posted February 12, 2017 Share Posted February 12, 2017 Does anyone know of a way to control fan speeds without corsair link? this software is just too consuming. Link to comment Share on other sites More sharing options...
Alberello Posted February 12, 2017 Share Posted February 12, 2017 Does anyone know of a way to control fan speeds without corsair link? this software is just too consuming. Sure, you can do it from your BIOS or with the software from your motherboard manufacturer. Link to comment Share on other sites More sharing options...
red-ray Posted February 13, 2017 Share Posted February 13, 2017 Performance and stability improvements, minor bug fixes Looks like not all the stability issues have been addressed as CL 4.5.0.55 still crashes :(:. The system details are as per my PC specs. I sent off the crash details and look forward to Microsoft informing me there is a solution ;):. Link to comment Share on other sites More sharing options...
red-ray Posted February 13, 2017 Share Posted February 13, 2017 The CL 4.5.0.55 installer crashes on my Dell 7720 :rant2:. System specs: Dell 7720 Windows 7 x64 Ultimate V6.01 Build 7601 Service Pack 1 - fully updated Intel Core i7 Quad 3630QM (Ivy Bridge) 2.40GHz [E1] I was installing it so I could answer a post without needing to use my desktop. I thought it might work if I copied the files across, so I did and the GUI started OK, but nothing was reported. I then checked and the service had not been installed. Given this the GUI should have reported this as an error, but it totally failed to do this :(:. As it happens this also happened to a user, see http://forum.corsair.com/forums/showthread.php?p=891137. The GUI failing to report it can't communicate with the service is rather poor and should be fixed :!:. Link to comment Share on other sites More sharing options...
ToastWiz Posted February 13, 2017 Share Posted February 13, 2017 Fixed Vengeance LED modules when only one unit was controlled (Z170/Z270 motherboards only) Whilst this would be great, the DRAM section has completely disappeared from my application. Link to comment Share on other sites More sharing options...
izudeen Posted February 14, 2017 Share Posted February 14, 2017 Hi All, Its first time im posting here ; but here's an issue... i've 2 component ; H80iv2 & LED Vengeance ; I download this update because the official release version cant control my LED on Z270 Mobo ; However this version totally disabled/missing LED control... :eek: was totally suprised by this.... My system spec as below https://valid.x86.fr/wvmwdz Link to comment Share on other sites More sharing options...
CircuitWizardry Posted February 14, 2017 Share Posted February 14, 2017 I come back here every now and then to see what lack of progress Corsair is making on Link... They are making negative progress, new hardware is coming out, and they fail to support it, while letting the issues with the old stuff remain. I have become a walking dis-advertisement for Corsair. I've steered many customers away from their stuff at the stores, and even more friends. Lots of other good alternatives out there. Link to comment Share on other sites More sharing options...
izudeen Posted February 14, 2017 Share Posted February 14, 2017 im willing to give it benefit of a doubt that this "mistake" is only happened to me or my mobo problem... would appreciate the update on the proper fix Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.