closed, sorry initially I did not see how to close the MR but just found it.
The Everest 60 does not initialise properly when connected to some USB ports. In the faulty case changing modes is possible but changing colors isn't. The fix is to send the command 0x03 0x46 0x23 0xea to the device. This resets (or maybe reinitialises) the device, after which changing the colors also works when the Everest 60 is connected to such a USB port.
This supersedes !3206 (comment 3089001415)
The Everest 60 does not initialise properly when connected to some USB ports. In the faulty case changing modes is possible but changing colors isn't. The fix is to send the command 0x03 0x46 0x23 0xea to the device. This resets (or maybe reinitialises) the device, after which changing the colors also works when the Everest 60 is connected to such a USB port.
Frans Meulenbroeks (6859c23d) at 17 Feb 11:03
Mountain Everest 60: fix initialisation
Hi Chris,
Yes, I can change that. Actually I even considered that but I was not sure if the device was already opened and initialized, hence I took this solution. I will create a new merge request as I cannot updat ethis one due to master being a protected branch
See !3207 (merged)
This fixes #5469
The Everest 60 does not initialise properly when connected to some USB ports. In the faulty case changing modes is possible but changing colors isn't. The fix is to send the command 0x03 0x46 0x23 0xea to the device. This resets (or maybe reinitialises) the device, after which changing the colors also works when the Everest 60 is connected to such a USB port.
Frans Meulenbroeks (8d7a3822) at 17 Feb 10:05
Mountain Everest 60: fix initialisation
Frans Meulenbroeks (8f331090) at 17 Feb 09:46
Added support to RTX 5070Ti MSI Vanguard 16G
... and 6 more commits
I feel that this issue can be closed. Code has been merged, see !3155 (merged) ALso on a local build everything seems to work with my Everest 60 (but as I do not have a numpad, I could not verify that part)
Update: I did some digging in the scripts/build-udev-rules.sh script I looked at the file list and I see in CollermasterCOntrolelr three subdirs that match *RGBController in the name. This might be causing that I see three generated CoolerMaster sections.
Amd for MOuntain I see ./Controllers/MountainKeyboardController/RGBController_Mountain60Keyboard.cpp ./Controllers/MountainKeyboardController/RGBController_MountainKeyboard.cpp
Two sections are generated but both are for the regular keyboard not for the 60:
#---------------------------------------------------------------#
#---------------------------------------------------------------# SUBSYSTEMS=="usb|hidraw", ATTRS{idVendor}=="3282", ATTRS{idProduct}=="0001", TAG+="uaccess", TAG+="Mountain_Everest" #---------------------------------------------------------------#
#---------------------------------------------------------------# SUBSYSTEMS=="usb|hidraw", ATTRS{idVendor}=="3282", ATTRS{idProduct}=="0001", TAG+="uaccess", TAG+="Mountain_Everest"
The ansi version of the 60 kdb has PID 0x0005 whereas the ISO version has PID 0x0006
Frans Meulenbroeks (a2f29911) at 08 Feb 15:22
feat: support MSI GeForce RTX 4060 GAMING X NV Edition 8G
... and 772 more commits
Frans Meulenbroeks (3e08ddcd) at 27 Oct 13:12
small fixup to bold
Frans Meulenbroeks (3e380d6a) at 27 Oct 12:57
Add end-of-project to the README
Frans Meulenbroeks (5511298d) at 27 Oct 12:56
Add end-of-project to the README
This is not the name of the file
I'm not too versed in python but if it is possible it is probably good to factor out this code in a separate py file as it appears a number of times