Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Compatible Coolers

AlphaGeek
2012-06-14
2014-03-30
  • AlphaGeek
    AlphaGeek
    2012-06-14

    Post other ASETEK Branded Cooling systems that are known to work here.

     
  • AlphaGeek
    AlphaGeek
    2012-06-14

    AMD FX-8150 Black Edition CPU Water Cooler - reported working by Omega_Weapon
    ASETEK Branded Cooler for AMD FX-8150 Black Edition.

     

    • Anonymous
      2014-03-14

      It works, Kind of. I am getting no "fan rpm" info back, in a status request.
      Software reads out pump rpm, and coolant temp, but fan rpm is always zero.

       
      • AlphaGeek
        AlphaGeek
        2014-03-14

        Can you please include the Operating system used, type of cooler [the usb ID, by lsusb] and the manufacturer?

        Are the fans plugged into the cooler, and not the mainboard headers?

        Thanks!

         

        • Anonymous
          2014-03-14

          Fan(s) are plugged into headers on asetek.

          OS version is Fedora 20
          Linux amd8core-localdomain 3.13.6-200.fc20.x86_64 #1 SMP Fri Mar 7 17:02:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

          Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 007 Device 003: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB
          Bus 007 Device 002: ID 2433:b111
          Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
          Bus 013 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
          Bus 012 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
          Bus 012 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
          Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
          Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 005 Device 003: ID 045e:0084 Microsoft Corp. Basic Optical Mouse
          Bus 005 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
          Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
          Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
          Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
          Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

          And one other silly detail. It will fork into background from from
          terminal. If I setup a SysV init script or systemd Script or try to
          use the udev run rule, It refuses to run. Sigh.

          Systemd Script as below

          [Unit]
          Description=Start kuhler cooler control, if configured
          ConditionFileNotEmpty=/etc/kuhler_thresholds

          [Service]
          EnvironmentFile=/etc/sysconfig/kuhlerd
          Type=simple
          PIDFile=/var/run/kuhlerd.pid
          ExecStart=/var/local/kuhlerd

          [Install]
          WantedBy=multi-user.target

           

        • Anonymous
          2014-03-16

          Fans are plugged into the cooler.

          Linux amd8core-localdomain 3.13.6-200.fc20.x86_64 #1 SMP Fri Mar 7 17:02:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

          Cooler is OEM AMD 8150 water kit

          Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 007 Device 002: ID 2433:b111
          Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
          Bus 015 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
          Bus 014 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
          Bus 014 Device 002: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB
          Bus 014 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 013 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
          Bus 012 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
          Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 005 Device 003: ID 045e:0084 Microsoft Corp. Basic Optical Mouse
          Bus 005 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
          Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
          Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
          Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
          Bus 010 Device 002: ID 2109:3431
          Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
          Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
          Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

           

        • Anonymous
          2014-03-29

          Turned out had two major problems. 1st on-board fan headers insufficient current. Had to use power adapter to main power supply. Now fan rpm info
          working, with better speed control. Kuhlerd would work from command line,
          but udev rules did not. Would start but never fork into background. SystemD
          same problem, finally resorted to SysV init script. That worked. This id fedora 20.

           
          • AlphaGeek
            AlphaGeek
            2014-03-30

            Thanks for the reports! Sorry for not responding. I figured it might be a current supply / connection issue based on the report. try going back to 0.5 for udev rules support, I may have inadvertently broken something in 0.6+.

            As for systemD, because I don't supply/use a PID file, it might break the scripts. I normally put it into /etc/rc.local, or SysV init script. There also might be an issue in the forking code.

            For the record, I run both a 2433:b111, and 2433:b200 [Antec 920 v1/v4], and do most of my testing under Linux Mint, 64bit , MATE edition.

            Thanks for taking the time to update and post!

             
  • Cyril Lavier
    Cyril Lavier
    2013-08-09

    Hello.

    Thanks for this tool, I've been searching it since I bought my NZXT Kraken X60 (id : 2433:b200).

    It's working, but there is an issue when setting it to silent, it actually sets to "custom" (the setting I see when I reboot under windows and use the NZXT tool).

    Since its support is in beta stages, I would like to help you in any manner.

    Thanks.

     
    Last edit: Cyril Lavier 2013-08-09
    • AlphaGeek
      AlphaGeek
      2013-08-10

      Thanks for reporting compatibility!

      The NZXT tool does not query what the status was previously, so I think it will reset to what the last default was, altough I am not 100% certain. You will also most likely see this issue if you try and change the LED colors in the Linux driver, and then reboot into windows.

      Try changing the LED colors as well as the mode. I should think the windows software will reset the LED colors as well, since the NZXT/Kuhler software does not have any way of getting the current mode from the Kuhler hardware.

      Hope this helps. Let me know if you have any other questions/issues.

       

  • Anonymous
    2014-03-18

    My NZXT Kraken x40 with lsusb address 2433:b200 works perfectly fine, but extreme mode doesn't seem to effect my Fan RPM probably due to improper connection with my fan headers.But i notice that with the built in w83627ehf fan driver if I enable PWM and spit out 255 I get better speeds, so I'll rewire my fans, try to disable native driver and do many tests to see what works best.

     


Anonymous


Cancel   Add attachments