Skip to content
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

H100i RGB PRO XT Lighting not responding to commands #149

Closed
DrymarchonShaun opened this issue Jul 6, 2020 · 5 comments
Closed

H100i RGB PRO XT Lighting not responding to commands #149

DrymarchonShaun opened this issue Jul 6, 2020 · 5 comments
Labels
bug Apparent bug in liquidctl

Comments

@DrymarchonShaun
Copy link

DrymarchonShaun commented Jul 6, 2020

Making new issue as requested, as stated previously, My H100i RGB PRO XT is initialized, the fan control works, but lighting does not respond to commands. logs from one for the commands I tried below. (it does not respond to any of the command variations in its help docs.)

shaun  ~  sudo liquidctl set led color off --debug
[DEBUG] liquidctl.cli: running liquidctl v1.3.3 (Arch Linux; liquidctl-git 1.3.3.r238.454cde3-1)
[DEBUG] liquidctl.driver.usb: searching HidapiBus (api=hid, drivers=[CommonSmartDeviceDriver, CoolitPlatinumDriver, CorsairHidPsuDriver, KrakenTwoDriver, KrakenX3Driver, KrakenZ3Driver, SeasonicEDriver, SmartDeviceDriver, SmartDeviceV2Driver])
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:172b
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:172b
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:172b
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:172b
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:150d
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:150d
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1726
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1726
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1726
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1726
[DEBUG] liquidctl.driver.usb: probing drivers for device 1b1c:0c20
[DEBUG] liquidctl.driver.usb: instanced driver for Corsair H100i PRO XT (experimental)
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1610
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1610
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1610
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1610
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1610
[DEBUG] liquidctl.driver.usb: probing drivers for device 0b05:18a3
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1250
[DEBUG] liquidctl.driver.usb: searching PyUsbBus (drivers=[AsetekDriver, CommonAsetekDriver, CorsairAsetekDriver, LegacyAsetekDriver])
[DEBUG] liquidctl.driver.usb: probing drivers for device 1d6b:0003
[DEBUG] liquidctl.driver.usb: probing drivers for device 1d6b:0002
[DEBUG] liquidctl.driver.usb: probing drivers for device 1d6b:0003
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1250
[DEBUG] liquidctl.driver.usb: probing drivers for device 0b05:18a3
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1610
[DEBUG] liquidctl.driver.usb: probing drivers for device 1b1c:0c20
[DEBUG] liquidctl.driver.usb: probing drivers for device 05e3:0610
[DEBUG] liquidctl.driver.usb: probing drivers for device 8087:0aaa
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:1726
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:150d
[DEBUG] liquidctl.driver.usb: probing drivers for device 1038:172b
[DEBUG] liquidctl.driver.usb: probing drivers for device 1d6b:0002
[DEBUG] liquidctl.driver.usb: probing drivers for device 1d6b:0003
[DEBUG] liquidctl.driver.usb: probing drivers for device 1d6b:0002
[DEBUG] liquidctl.cli: device: Corsair H100i PRO XT (experimental)
[DEBUG] liquidctl.keyval: data in /var/run/liquidctl/1b1c_0c20/L2Rldi9oaWRyYXc0
[DEBUG] liquidctl.keyval: loaded sequence=4 (from /var/run/liquidctl/1b1c_0c20/L2Rldi9oaWRyYXc0/sequence)
[DEBUG] liquidctl.keyval: stored sequence=5 (in /var/run/liquidctl/1b1c_0c20/L2Rldi9oaWRyYXc0/sequence)
[DEBUG] liquidctl.driver.coolit_platinum: write 003f2c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ae
[DEBUG] liquidctl.driver.coolit_platinum: received ff281116000500df17000060e8036099030060e803609d0301bf0000bf3d090000000000000000000000000000000000000000000000000000000000000000fb
[DEBUG] liquidctl.keyval: stored sequence=6 (in /var/run/liquidctl/1b1c_0c20/L2Rldi9oaWRyYXc0/sequence)
[DEBUG] liquidctl.driver.coolit_platinum: write 003f3500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a5
[DEBUG] liquidctl.driver.coolit_platinum: received ff301116000600df17000060e8036099030060e803609d0301bf0000bf3d09000000000000000000000000000000000000000000000000000000000000000016
@jonasmalacofilho jonasmalacofilho added the bug Apparent bug in liquidctl label Jul 6, 2020
@jonasmalacofilho
Copy link
Member

jonasmalacofilho commented Jul 8, 2020

Thank you for opening this new issue.

I'll try to emulate a PRO XT to see what could be wrong/incomplete in the driver. But it may take me a few days to get to this...

In the meantime, if anyone can take a look at the USB traffic between iCue and a H100i/H115i PRO XT and attempt a fix, it would be very much appreciated!

By the way, fixing this will probably help #138 (H150i PRO XT support) too.

@audiohacked
Copy link

@jonasmalacofilho I'm currently out of town on a business trip, when I get home I'll do some testing.

@jonasmalacofilho jonasmalacofilho added the blocking Blocks a current release label Jul 13, 2020
jonasmalacofilho added a commit that referenced this issue Jul 25, 2020
This abstraction assumed each "component", meaning a fan or the pump
head, had the same number of LEDs.  It that held, the abstraction
provided a simple but convenient way to control each component
independently.

Unfortunately, the PRO XT devices made it obvious that the assumption
was incorrect: the pump head is very likely the same between Platinum
and PRO XT coolers, and it is now known to have 16 LEDs (on the PRO XT).

This makes the component abstraction a harder to (correctly) implement,
since the fans and the pump head have significantly different number of
LEDs.

Considering that it was also a very crude abstraction, a more direct
approach, where each component is identified by its name through
separate (pseudo) channels, is preferable to fixing the old one.

This will, however, require thorough testing, and is not something I am
ready to include (and thus stabilize) in 1.4.0.

For now, simply remove the broken abstraction and provide basic fully
independent or fully synchronized control over the LEDs.

Related: #149 ("H100i RGB PRO XT Lighting not responding to commands")
Related: #138 ("Add support for H150i PRO XT and H100i Platinum SE")
@jonasmalacofilho jonasmalacofilho removed the blocking Blocks a current release label Jul 25, 2020
jonasmalacofilho added a commit that referenced this issue Jul 25, 2020
Even with the potential fixed from commit c2200fa ("hydro_platinum:
Remove component abstraction in set_color"), this feature is not
sufficiently tested to be enabled by default on the impending 1.4.0
release.  Require `--unsafe pro_xt_lighting` (or equivalent when
directly calling the API) to enable.

Related: #149 ("H100i RGB PRO XT Lighting not responding to commands")
Related: #151 ("Tracking issue for release 1.4.0")
@MarshallAsch
Copy link
Member

@ShaunTheQuietGamer is this issue still presenting itself with the latest version of the project? And do you know what the current firmware version of the cooler is? There was another issue with #201 where somethings didn't work on an old firmware version. There has also been an additional message that has been added to the device to change the hardware lighting mode mentioned in #190

@jonasmalacofilho
Copy link
Member

Closing due to inactivity (and by now the driver has already changed quite a bit).

@MarshallAsch
Copy link
Member

@ShaunTheQuietGamer incase you are still having the issue you can add the --unsafe=pro_xt_lighting flag, without it the Pro XT devices cannot currently control the colors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Apparent bug in liquidctl
Projects
None yet
Development

No branches or pull requests

4 participants