Petrol_Head Posted December 11, 2015 Share Posted December 11, 2015 I bought the M65 RGB a couple of days ago and have run into an issue right away: The CUE doesn't always recognize the mouse. The mouse works and the lights are on (with the factory default lighting scheme), but the polling rate is stuck at 125 Hz, no profiles are loaded and the device status is "Malfunction". Restarting CUE doesn't help, restarting the computer doesn't necessarily help, but unplugging and replugging seems to do the trick. Any ideas on how to fix this are welcome, as I'm not exactly keen on the idea of having to frequently unplug and replug the mouse. My CUE version is 1.13.36, my M65 firmware version is 1.19 and the bootloader version is 0.23. I have the mouse plugged in one of the USB 3.0 ports (Etron EJ188H) of my motherboard. I haven't installed ASRock's driver for Etron's USB 3.0, since the OS itself seems to have no issues with the mouse and I've heard Etron's drivers may in fact cause problems. So, at the moment I have the newest Windows drivers installed. Finally, here's the log from the latest incident: [2015-12-11T01:10:45]: Created new device object: M65 RGB; ready: 0 [2015-12-11T01:10:45]: Device profile (meta) for device vid=46d pid=c52b not found. [2015-12-11T01:10:45]: Device profile (meta) for device vid=46d pid=c52b not found. [2015-12-11T01:10:45]: Device profile (meta) for device vid=46d pid=c52b not found. [2015-12-11T01:10:45]: Attached to device object M65 RGB: b=1 a=0 [2015-12-11T01:10:45]: Initializing M65 RGB... [2015-12-11T01:10:45]: Device profile (meta) for device vid=46d pid=c52b not found. [2015-12-11T01:10:45]: Failed to open device: vid=1b1c pid=1b12 path=\\?\hid#vid_1b1c&pid_1b12&mi_01&col01#8&2e5d39bf&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2015-12-11T01:10:50]: Get device info failed.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 121. [2015-12-11T01:10:55]: Get device info failed.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 121. [2015-12-11T01:11:00]: Get device info failed.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 121. [2015-12-11T01:11:06]: Get device info failed.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 121. [2015-12-11T01:11:11]: Get device info failed.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 121. [2015-12-11T01:11:16]: Get device info failed.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 121. [2015-12-11T01:11:21]: Get device info failed.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 121. [2015-12-11T01:11:26]: Get device info failed.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 121. [2015-12-11T01:11:31]: Get device info failed.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 121. [2015-12-11T01:11:31]: Initializing M65 RGB: spent all tries on getDeviceInfo(). [2015-12-11T01:11:31]: Initializing M65 RGB: failed to read proto version. [2015-12-11T01:11:31]: Get device info failed. request timed out for M65 RGB [2015-12-11T01:11:31]: Initialized (st=0) M65 RGB. [2015-12-11T01:11:31]: Attached to device object M65 RGB: b=2 a=2 [2015-12-11T01:11:31]: Failed to open device: vid=1b1c pid=1b12 path=\\?\hid#vid_1b1c&pid_1b12&mi_00#8&1699ad7a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2015-12-11T01:11:31]: Device object failed to initialize, so it won't be registered with application susbystems. M65 RGB. [2015-12-11T01:11:35]: Firmware Download: Failed to parse firmware version. [2015-12-11T01:11:35]: Firmware Download: Failed to read firmware version. [2015-12-11T01:11:35]: Firmware Download: Some of required values are not set, aborting. [2015-12-11T01:11:36]: Get device info failed.Device : M65 RGB,Execution result = 0, result = 0, platform error code = 121. [2015-12-11T01:12:18]: Get device info failed. request timed out for M65 RGB [2015-12-11T01:12:23]: Get device info failed.Device : M65 RGB,Execution result = 0, result = 0, platform error code = 121. [2015-12-11T01:12:24]: Get device info failed. request timed out for M65 RGB [2015-12-11T01:12:29]: Get device info failed.Device : M65 RGB,Execution result = 0, result = 0, platform error code = 121. Link to comment Share on other sites More sharing options...
Toasted Posted December 13, 2015 Share Posted December 13, 2015 Install the latest drivers and see if it resolves the issue. Do you have any USB ports controlled by the AMD chipset? If so, try plugging the mouse into one of those and see whether its better. You can refer to your motherboard's user manual for that information. Link to comment Share on other sites More sharing options...
StealthDefender Posted December 13, 2015 Share Posted December 13, 2015 I have a simialar problem here. In my log i got thge same errors, but my mouse appears in cue. But after restart the lights won´t light up! This is about the 5 or 6th post i write about but no one semms to now an answer! Greetz Stealth Link to comment Share on other sites More sharing options...
Petrol_Head Posted December 13, 2015 Author Share Posted December 13, 2015 Install the latest drivers and see if it resolves the issue. I already have the latest drivers. Do you have any USB ports controlled by the AMD chipset? If so, try plugging the mouse into one of those and see whether its better. You can refer to your motherboard's user manual for that information. The manual doesn't explicitly specify what controls the USB 2.0 ports, but since the USB 2.0 headers aren't mentioned to be Etron's - unlike the USB 3.0 headers - it's probably reasonable to assume they're controlled by the AMD chipset. I'll see if using those helps, thanks. Btw, it's too early to tell for sure, but it seems that the problem occurs after I've booted to Linux and then boot back to Windows. After I've unplugged and replugged the mouse, it seems to keep on working as it should even after a reboot as long as I don't boot to Linux. In Linux the mouse functions as a generic mouse and since that's all I need in Linux, I haven't tried the unofficial Linux driver at all. Link to comment Share on other sites More sharing options...
Petrol_Head Posted December 16, 2015 Author Share Posted December 16, 2015 I've tried this only once, so this might just be a fluke, but I switched the mouse to a USB 2.0 port, booted to Linux, then to Windows and the mouse was found by the CUE. If this is not a fluke, then two questions arise: -Why would booting into Linux affect how well Etron's USB hub works in Windows? -What would cause the USB hub to work well enough for the mouse to work as a regular mouse in Windows, but not well enough for CUE to recognize it? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.