New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add support for Kraken 240 #624
Comments
You didn't list the USB product ID, so I'll guess that it's |
Does this help I did a lsusb |
Going to +1 this thread, looks like on windows the Kraken 240 presents itself like this
I'd be super down to test on windows and I can provide any additional information you might need @aleksamagicka |
Support for that Kraken in liquidctl has been merged in October. Please retry with the Git version for the time being. |
Will do, thank you for the info. I'll report back if it was successful. |
@lanceofwhichwedream can you report back whether you got it working successfully or not? I need to buy a water cooler, and this cooler costs $30 less than kraken x53, so if its successful, I could be getting a better product with more features (lcd) and $30 cheaper 😅 |
I can confirm it works on fb697e0 (latest master as of yesterday, linux, NixOS 23.11) ...however, after overnight using the python library to control pump and fan speed I get a "device has no langid" error like this previously reported bug: #618 . It's a bit different as it was working (so permissions are fine) but then it stops. (context: new motherboard/cooler for my fan control script -- it works in the same way, the only difference being I control the fan via the kraken now too every 0.5s. The X53 was reliable) dmesg is littered with USB errors. Replugging the internal USB connection gets things back working: Perhaps this is a Kraken firmware bug? I don't run windows so I've never updated its firmware. |
It crashed again overnight, more than 12 hours after re-plugging it. Nothing in The LCD on the Kraken is also stuck -- the default live temperature is stuck on 34c no matter how much I load it. Traceback:
|
I've booted into a copy of windows and started NZXT CAM, which immediately updated the firmware (with no warning ha). Well, nope. It lasted only a few minutes this time. Note also in windows I had to replug the device to get CAM to recognise it. Perhaps I have a dud? |
From what you're describing, it seems plausible to me (but I've never had this happen to concur). Maybe check that the cables are snug? Perhaps the connector isn't soldered correctly or is otherwise damaged, and the firmware disconnects after failed packets. I'm guessing that other devices on internal USB work fine? |
I actually spoke to soon -- I forgot the sudo (or udev rules) when I checked it before going to sleep 🤦 It's been running for 15h after the firmware update without a problem. I'll report back tomorrow, if it's still working then the firmware update may have fixed it. Otherwise yes indeed the internal USB is fine with other devices and the cables seem ok. Thanks for the reply |
OK it's been nearly 24h, I can confidently say the firmware update fixed the problem. I've made a PR to update the readme. |
just to add to this, my kraken 240 doesnt display anything when doing liquid list, and the pip version shows this error ValueError: The device has no langid (permission issue, no string descriptors supported or device error) |
Have you tried updating the firmware using NZXT Cam? Also, I presume you're using udev rules or sudo. |
Yeah I figured out that sudoing would let me run the script successfully |
Device type
AIO liquid cooler, Kraken 240 (no rgb version)
Product page
https://nzxt.com/product/kraken-240
First-party software
NZXT CAM
What monitoring functionality does the device support?
temperatures, fan/pump speeds or duty cycles
What configuration functionality does the device support?
fan/pump speeds or duty cycles, lighting of embedded LEDs, lighting of accessories like RGB fans or LED strips
Physical connection
No response
Connection protocol
No response
Additional information about the device
No response
Can you help with implementing or testing the changes needed for liquidctl to support this device?
testing changes on Linux
The text was updated successfully, but these errors were encountered: