giganode

PN

Please try this: /usr/local/bin/cpsumon/cpsumoncli /dev/ttyUSB0 Please post your Diagnostics.

And that is correct. I again didn't read correctly. You need to use cpsumoncli for AXi series psu. Please try the following command in cli: cpsumoncli /dev/ttyUSB0 You may need to use this command first: chmod +x /usr/local/bin/cpsumon/cpsumoncli

Please check the output of corsairmi. Did you try go to settings page and set to default? Gesendet von iPhone mit Tapatalk

RMi and HXi series use corsairmi. At the moment, the following psus are implemented: 0x1c0a, /* RM650i 0x1c0b, /* RM750i 0x1c0c, /* RM850i 0x1c0d, /* RM1000i 0x1c04, /* HX650i 0x1c05, /* HX750i 0x1c06, /* HX850i 0x1c07, /* HX1000i 0x1c1e, /* HX1000i with USB-C 0x1c08, /* HX1200i */ If you want to go for the hx1500i, I can try to integrate it. But for that we need to buy it.

Okay, I will look into that

Is your cpsumoncli executable after boot? Please post the output of cpsumoncli /dev/ttyUSB0

May I ask why you have the following in your go file? : echo PATH=.:$PATH:/usr/local/sbin:/usr/local/bin >>/root/.bash_profile cp /boot/config/group /etc/group chmod 644 /etc/group cp /boot/bin/* /usr/local/bin chmod 755 /usr/local/bin/*

Hello Thank you for the provides details. Just for me to know.. which AXi PSU is it exactly? Please verify the following with lsusb -t again before you proceed: root@mccserverur01:/dev# lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 4: Dev 4, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M Run echo -n "2-4:1.0" > /sys/bus/usb/drivers/cp210x/bind now try cpsumoncli /dev/ttyUSB0 If psu still doesn't answer try echo -n "2-4:1.0" > /sys/bus/usb/drivers/cp210x/unbind echo -n "2-4:1.0" > /sys/bus/usb/drivers/cp210x/bind cpsumoncli /dev/ttyUSB0 Can you share your final output of cpsumoncli?

Please provide the Diagnostics.

for AXi PSU you need to use cpsumoncli. Try this in terminal: cpsumoncli /dev/ttyUSB0 Keep in mind that you may need to point to another device because of the other dongle.. or just simply unplug the wireless dongle for testing. Post the output pls

Hi, to me 1b1c:1b66 seems to be the following device: Corsair IRONCLAW RGB WIRELESS Gaming Dongle. Can you verify that you use that device this in your system?

You’re welcome [emoji6] Right now, only the 1000W version is added, but support for the other versions should be added quickly, after getting some information from the psu. For now there is still a double mention in the header of the widget. I still need to change that but for now it’s working

More and more people seem to have the new 1000 watts psu [emoji2] Just go ahead and install the released version and it should be working[emoji846]

No, that is not the reason.

Thank you. I want to know why you need to chmod the executable. Please provide the Diagnostics.

There is a 2nd user with the same behaviour. For research, please provide your Diagnostics.

Okay, so you will need a temporary fix until the changes are released. I will send it to you via pn in a few minutes [emoji846]

Exactly, RMx series doesn’t have a communication port. So there’s no way to extract the data.

I'm sorry I did not think about that new generation with usb-c connector. This version is actually not supported right now. I will try to add support later that day. For testing purposes I will contact you via pn then

Ah thats the new generation! I'm afraid, that might be the reason. Let me check something..

@mayberts try by unplugging the keyboard and mouse please. Then check function with corsairmi via cli. If this doesn’t help, try unplugging the PSUs usb cable, plug it back in and then try corsairmi again.

@mayberts I upgraded to rc7.. everything works like before for me. What happens if you remove every hid? Please remove Mouse and Keyboard, then test again. Also try unplugging the PSUs usb cable, then put it back in and try again.

Yes, because rc7 is higher 😅 I switched the branch and will apply the update to rc7 soon..

Okay. I updated to 6.12.0-rc6.13. For me it is working. If you don't mind please update in case the issue is already gone with this release.