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
Commander Pro -> Initialization is needed every ~15min (Proxmox Server) #611
Labels
bug
Apparent bug in liquidctl
Comments
Now it's the time while i didn't initialized and liquidctl lost somehow the status: If i run:
if i run:
So the sensors are working perfectly as expected, just liquidctl loses track somehow. Here is the debug of not working liquidctl, in case it's needed: liquidctl status --debug
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hi, first thank you a lot Jonas for this great tool.
It's working actually pretty flawless here, i have just one weird issue, that is actually not a big deal tbh.
Issue:
A quote from your Description about the Commander Pro:
"The device should be initialized every time it is powered on, including when the system resumes from suspending to memory."
-> Proxmox never sleeps here or anything, its always on and running 24/7
-> But i have to "initialize" liquidctl every 15-30 minutes, because if not, after some time status won't report anything else as the rail voltage.
-> I initialize liquidctl with "--direct-access" always (that leads to second question)
Issue:
-> I have to initialize liquidctl always with "--direct-access", or normally, but with unloading the kernel module "modprobe -r corsair_cpro" first.
-> Funny thing is, that your liquidctl loads itself its own module called "corsair-cpro", this module strangely works perfect.
-> If i don't unload the "corsair_cpro" module or if i don't use "--direct-access" to initialize, liquidctl won't see the fans or temperature sensors.
-> For me it looks clearly, like the "corsair_cpro" kernel module inside 6.2.16 is buggy/crappy ?
-> Couldn't you push some commits to upstream, to fix the kernel module?
Why is it all not so important:
-> Because the Corsair Commander Pro, operates by itself, means setting it once is enough. The commander pro will keep the settings during reboots, Powerloss, unplug/replug etc....
-> Once you set your desired settings for the fans etc, the commander will keep it forever, which is pretty amazing tbh.
Commands executed
I made a script, where i simply set my settings:
liquidctlsetspeed.sh
Output of all relevant commands with
--debug
flagliquidctl initialize --debug (without --direct access)
liquidctl status --debug
That are sadly debugs after --direct-access, means with working commander pro.
Once i did once initialize with --direct-access, the fullowing initialization without --direct-access works either.
But if needed i can send another debug, where i didn't initialized before with --direct-access, means a not working debug log.
Affected device
Corsair Commander Pro
Operating system and version
Proxmox 8.0.3 / Debian 12
Installation method
Proxmox ISO
Version of liquidctl
liquidctl v0.0.0-unknown (Linux-6.2.16-3-pve-x86_64-with-glibc2.36)
The text was updated successfully, but these errors were encountered: