Hello, on some forums somebody told me that the windows drivers for antec v4 are different from the others. Are thoselinux drivers compatible wiith the version 4 of this cooler?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi! from what I can find on the net, the differences on the V4 are a split-flow radiator, and a higher pressure pump. the USB VID/PID might have changed, but hopefully the command-set remains the same.
If you have one, can you do a lsusb and grab the VID/PID?
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-03-24
I want to buy one... But i want to be sure if i can use it on linux or not...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-03-27
if the vid/pid is different, could i use these drivers too ? i have to change something?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If the VID/PID is differnt, you can change the VID/PID in the source code. It's a one line change. This does not guarantee that the driver will work though, since the commands used for control may be different.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-03-28
I just received a report that the VID/PID is different.
Original : 0x2433:0xb111
New V4: 0x2433:0xb200
The V4 also has different windows drivers, but this may be simply due to the PID change.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I accidentally posted this question to reviews. Sorry. Anyway. The Antec kuhler 920 is an OEM product from Asetek inc. I have the AMD version that comes with the FX-8150 processor. It is for all intents and purposes the exact same product except for the pump cover. Do you have any idea if your driver will work with the AMD version of this cooler?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-04-06
There is a confirmed report of this working. As long as it works with ChillControl software [by ASETEK], it SHOULD work with this driver.
the VID/PID may need to be modified though. A one line change in the header.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I actually checked that via lsusb it's the same device numbers as the Antec pre V4.
The problem I face now is that I'm running a 2.6.37 kernel (64 bit system) and the software compiles with no warnings yet the daemon exits with an exception error in the libusb library. Updated libusb to current version and still get the same thing.
Running Slackware 13.37. Been using Linux going on 12 years though I'm no programmer. 32bit/64bit compatibility problem??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running on Linux MINT v14, with 64 bit. It's running a much more recent kernel, the 3.5 series or so. I was a slackware fan for a long time before moving to Debian based distros.
Can you try the following?
-run the daemon in debug mode: ./kuhlerd -d
try running as sudo " sudo ./kuhlerd -d"
look for more detailed error logs in /var/log/messages or /var/log/syslog [look for kuhlerd].
The other thing you can try, is load the usbmon package, and capture some debug info for me , so I can try and help.
Can you post the errors you are getting?
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Problem solved. It's a hardware and or Linux kernel USB issue with the USB ports. I have a front panel with 4 usb ports they can be 1.1 or 2.0 ports as they are just wires to the ports with no intervening circuit components between the motherboard plug and the port plug. I unplugged ports 1 and 2 to install the AMD cooler and left ports 3 and 4 intact.
Seems Linux does not like this at all for some strange reason. Kuhlerd was exiting with a usblib device busy error. After I unplugged ports 3 and 4 it runs just fine. Windows 7 has no problem with the having ports 3 and 4 and the AMD cooler plugged in what so ever, go figure.
So call it a success. The AMD cooler can be accessed with your kuhler driver just perfectly with kernel 2.6.37 under Slackware 13.37. 64 bit.
Last edit: spjames 2013-04-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'll add that kernel/OS/Cooler combination to the list of known working combinations. Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-11-30
Thanks for trouble and effort to create this driver/application.
Compiled and successfully created binary on Ubuntu 12.04 x64 (kernel 3.2.0-56)
kuhler_ctl can access (read info) and change parameters (fan and colours) (so I assume all is ok here)
Added the /etc/udev/ rules as described in your install file.
Also created group kuhler and assigned my user as member.
Q1:
When I run as normal user or sudo kuhlerd or kuhlerd -d I get message:
Kuhlerd : usb_claim_interface error -6
Not sure where to start tracing problem. Any suggestions.
Q2:
Also it is not 100% clear where the kuhler_thresholds file comes into play.
When I run different modes under 100% CPU load I get following results
In mode 0 turning slow for silent mode
In mode 1 turning slow
In mode 2 full blast mode
Q3:
Also how does the thresholds interact with parameters -s -f and can they work against each other due to conflicting temperature settings?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi! Thanks for helping by providing your OS and CPU combo! I hope these answers help:
Q1:
kuhlerd is automatically run by the udev rules at each boot, there should be no need to run it, as normal user or root.
Q2: kuhler_thresholds only comes into play if you have a "V4" kuhler. Can you please send the output of lsusb? the V4 is identified by 2433:b200, while all other versions report 2433:b111.
Q3: kuhler thresholds does not interact with the -s and -f parameters. These parameters are only used for the V1-V3 kuhlers, while the kuhler_thresholds file is only used by the newer V4 kuhlers.
Please let me know if you have any other questions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-12-02
Ok,
Q1: Hickup sorted. Misinterpreted the "to run on bootup" line in your install file.
Q2: Looks like i have the 2433:b111 so no need to worry about thresholds then.
Q3: Makes sense based on Q2, thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Glad I could help clear things up! I'll modify the documentation to make it a bit clearer.
remember to set start and full temps for custom mode if you use that, I generally set mine to about 36 45 or something like that..you can always use the "-l" parameter to find out if your fans are ramping up, and of course you can hear the noise :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am currently running a Antec 920 with windows 8.1 and am wanting to switch over to Linux (Fedora Workstation 22) for my main system, so I'll be dual booting. I've tried my best to read through everything I can find on this particular matter, but nobody has stated whether or not this will work on Fedora. I ask because of the different file formats the different linux distros use. I have not been on Linux in a long time and am dying to come back to it. So if it is a matter of me just needing to compile the source code on my machine and it should work, then just let me know please. I am a Java programmer, so I'm not afraid to get my hands dirty at all.
I know this is an old thread and has not had any new posts in a while, so I hope somebody is still paying attention and can help me out with this. I don't want to get into Linux and try to work it all out and have my processor end up getting toasted. I'm not running anything crazy at the moment, just an AMD FX-4100 but will be upgrading to a 8 or 9 series later this year, so it will definitely be needed to cool my system down then. I appreciate any and all help I can get. Thank you!
Bryce
I can also be reached at bryce.yarbrough at gmail dot com if that's more convenient for anyone.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The driver is pertty generic, it's a source-only package so it should
work with most Linux distro's, I even have one confirmed report of OS X
working.
Just untar it, and try running "make", you may need "libusb-dev" or some
version of that library. The "rpm" command should be able to install it.
The Kuhler hardware is pretty fail-safe, the pumps and fans are always
running even if the driver is not installed, so there is little danger
of toasting a system.
If you need help, let me know , I will see what I can do. Most of my
testing was done on Ubuntu/Mint.
If you do get it working, please let us know, and I'll add it to the
supported OS/CPU list.
Also, do you have a V1 or V4 Kuhler?
the USB id's will help. In linux please do "lsusb"
2433:b111 is the V1-V3, while 2433:b200 is the V4 Kuhler.
On 15-08-05 09:37 PM, Bryce Yarbrough wrote:
Post above is mine, forgot to login.
Hi There,
I am currently running a Antec 920 with windows 8.1 and am wanting to switch over to Linux (Fedora Workstation 22) for my main system, so I'll be dual booting. I've tried my best to read through everything I can find on this particular matter, but nobody has stated whether or not this will work on Fedora. I ask because of the different file formats the different linux distros use. I have not been on Linux in a long time and am dying to come back to it. So if it is a matter of me just needing to compile the source code on my machine and it should work, then just let me know please. I am a Java programmer, so I'm not afraid to get my hands dirty at all.
I know this is an old thread and has not had any new posts in a while, so I hope somebody is still paying attention and can help me out with this. I don't want to get into Linux and try to work it all out and have my processor end up getting toasted. I'm not running anything crazy at the moment, just an AMD FX-4100 but will be upgrading to a 8 or 9 series later this year, so it will definitely be needed to cool my system down then. I appreciate any and all help I can get. Thank you!
Bryce
I can also be reached at bryce.yarbrough at gmail dot com if that's more convenient for anyone.
Hello, on some forums somebody told me that the windows drivers for antec v4 are different from the others. Are thoselinux drivers compatible wiith the version 4 of this cooler?
Hi! from what I can find on the net, the differences on the V4 are a split-flow radiator, and a higher pressure pump. the USB VID/PID might have changed, but hopefully the command-set remains the same.
If you have one, can you do a lsusb and grab the VID/PID?
Thanks!
I want to buy one... But i want to be sure if i can use it on linux or not...
if the vid/pid is different, could i use these drivers too ? i have to change something?
If the VID/PID is differnt, you can change the VID/PID in the source code. It's a one line change. This does not guarantee that the driver will work though, since the commands used for control may be different.
I just received a report that the VID/PID is different.
Original : 0x2433:0xb111
New V4: 0x2433:0xb200
The V4 also has different windows drivers, but this may be simply due to the PID change.
I accidentally posted this question to reviews. Sorry. Anyway. The Antec kuhler 920 is an OEM product from Asetek inc. I have the AMD version that comes with the FX-8150 processor. It is for all intents and purposes the exact same product except for the pump cover. Do you have any idea if your driver will work with the AMD version of this cooler?
There is a confirmed report of this working. As long as it works with ChillControl software [by ASETEK], it SHOULD work with this driver.
the VID/PID may need to be modified though. A one line change in the header.
I actually checked that via lsusb it's the same device numbers as the Antec pre V4.
The problem I face now is that I'm running a 2.6.37 kernel (64 bit system) and the software compiles with no warnings yet the daemon exits with an exception error in the libusb library. Updated libusb to current version and still get the same thing.
Running Slackware 13.37. Been using Linux going on 12 years though I'm no programmer. 32bit/64bit compatibility problem??
I'm running on Linux MINT v14, with 64 bit. It's running a much more recent kernel, the 3.5 series or so. I was a slackware fan for a long time before moving to Debian based distros.
Can you try the following?
-run the daemon in debug mode: ./kuhlerd -d
try running as sudo " sudo ./kuhlerd -d"
look for more detailed error logs in /var/log/messages or /var/log/syslog [look for kuhlerd].
The other thing you can try, is load the usbmon package, and capture some debug info for me , so I can try and help.
Can you post the errors you are getting?
Thanks!
Problem solved. It's a hardware and or Linux kernel USB issue with the USB ports. I have a front panel with 4 usb ports they can be 1.1 or 2.0 ports as they are just wires to the ports with no intervening circuit components between the motherboard plug and the port plug. I unplugged ports 1 and 2 to install the AMD cooler and left ports 3 and 4 intact.
Seems Linux does not like this at all for some strange reason. Kuhlerd was exiting with a usblib device busy error. After I unplugged ports 3 and 4 it runs just fine. Windows 7 has no problem with the having ports 3 and 4 and the AMD cooler plugged in what so ever, go figure.
So call it a success. The AMD cooler can be accessed with your kuhler driver just perfectly with kernel 2.6.37 under Slackware 13.37. 64 bit.
Last edit: spjames 2013-04-07
Great! Glad to hear it works!
I'll add that kernel/OS/Cooler combination to the list of known working combinations. Thanks!
Thanks for trouble and effort to create this driver/application.
Compiled and successfully created binary on Ubuntu 12.04 x64 (kernel 3.2.0-56)
kuhler_ctl can access (read info) and change parameters (fan and colours) (so I assume all is ok here)
Added the /etc/udev/ rules as described in your install file.
Also created group kuhler and assigned my user as member.
Q1:
When I run as normal user or sudo kuhlerd or kuhlerd -d I get message:
Kuhlerd : usb_claim_interface error -6
Not sure where to start tracing problem. Any suggestions.
Q2:
Also it is not 100% clear where the kuhler_thresholds file comes into play.
When I run different modes under 100% CPU load I get following results
In mode 0 turning slow for silent mode
In mode 1 turning slow
In mode 2 full blast mode
Q3:
Also how does the thresholds interact with parameters -s -f and can they work against each other due to conflicting temperature settings?
Hi! Thanks for helping by providing your OS and CPU combo! I hope these answers help:
Q1:
kuhlerd is automatically run by the udev rules at each boot, there should be no need to run it, as normal user or root.
Q2: kuhler_thresholds only comes into play if you have a "V4" kuhler. Can you please send the output of lsusb? the V4 is identified by 2433:b200, while all other versions report 2433:b111.
Q3: kuhler thresholds does not interact with the -s and -f parameters. These parameters are only used for the V1-V3 kuhlers, while the kuhler_thresholds file is only used by the newer V4 kuhlers.
Please let me know if you have any other questions.
Ok,
Q1: Hickup sorted. Misinterpreted the "to run on bootup" line in your install file.
Q2: Looks like i have the 2433:b111 so no need to worry about thresholds then.
Q3: Makes sense based on Q2, thanks.
Glad I could help clear things up! I'll modify the documentation to make it a bit clearer.
remember to set start and full temps for custom mode if you use that, I generally set mine to about 36 45 or something like that..you can always use the "-l" parameter to find out if your fans are ramping up, and of course you can hear the noise :)
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi There,
I am currently running a Antec 920 with windows 8.1 and am wanting to switch over to Linux (Fedora Workstation 22) for my main system, so I'll be dual booting. I've tried my best to read through everything I can find on this particular matter, but nobody has stated whether or not this will work on Fedora. I ask because of the different file formats the different linux distros use. I have not been on Linux in a long time and am dying to come back to it. So if it is a matter of me just needing to compile the source code on my machine and it should work, then just let me know please. I am a Java programmer, so I'm not afraid to get my hands dirty at all.
I know this is an old thread and has not had any new posts in a while, so I hope somebody is still paying attention and can help me out with this. I don't want to get into Linux and try to work it all out and have my processor end up getting toasted. I'm not running anything crazy at the moment, just an AMD FX-4100 but will be upgrading to a 8 or 9 series later this year, so it will definitely be needed to cool my system down then. I appreciate any and all help I can get. Thank you!
Bryce
I can also be reached at bryce.yarbrough at gmail dot com if that's more convenient for anyone.
Post above is mine, forgot to login.
Hi!
The driver is pertty generic, it's a source-only package so it should
work with most Linux distro's, I even have one confirmed report of OS X
working.
Just untar it, and try running "make", you may need "libusb-dev" or some
version of that library. The "rpm" command should be able to install it.
The Kuhler hardware is pretty fail-safe, the pumps and fans are always
running even if the driver is not installed, so there is little danger
of toasting a system.
If you need help, let me know , I will see what I can do. Most of my
testing was done on Ubuntu/Mint.
If you do get it working, please let us know, and I'll add it to the
supported OS/CPU list.
Also, do you have a V1 or V4 Kuhler?
the USB id's will help. In linux please do "lsusb"
2433:b111 is the V1-V3, while 2433:b200 is the V4 Kuhler.
On 15-08-05 09:37 PM, Bryce Yarbrough wrote:
Hi There,
I am currently running a Antec 920 with windows 8.1 and am wanting to switch over to Linux (Fedora Workstation 22) for my main system, so I'll be dual booting. I've tried my best to read through everything I can find on this particular matter, but nobody has stated whether or not this will work on Fedora. I ask because of the different file formats the different linux distros use. I have not been on Linux in a long time and am dying to come back to it. So if it is a matter of me just needing to compile the source code on my machine and it should work, then just let me know please. I am a Java programmer, so I'm not afraid to get my hands dirty at all.
I know this is an old thread and has not had any new posts in a while, so I hope somebody is still paying attention and can help me out with this. I don't want to get into Linux and try to work it all out and have my processor end up getting toasted. I'm not running anything crazy at the moment, just an AMD FX-4100 but will be upgrading to a 8 or 9 series later this year, so it will definitely be needed to cool my system down then. I appreciate any and all help I can get. Thank you!
Bryce
I can also be reached at bryce.yarbrough at gmail dot com if that's more convenient for anyone.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
For the record, this driver appears to work with the Corsair H100i V2 simply by changing the V4 VID to 0x1b1c and the V4 PID to 0x0c09
thanks for compatibility report. I will add to supported list!