USB Mouse disconnecting - Red Dragon Cobra M711

[daishishi]

Hello everyone,

I'm with a problem with a disconnecting mouse on Pop! OS 22.04 LTS. At random times the mouse turns off, the cursor won't move, the buttons don't respond, the mouse's LED turn off. Most of the times, the moment the mouse turns off, it will turn back on right after, but it happened sometimes of not turning back on. In the latter case I have to change the mouse of USB port, just removing and plugging back on the same USB port won't work.
The mouse is on a 'Motherboard USB Plug', and strangely when I tried using the mouse on a front USB plug (via those case cable) for a couple of hours the mouse didn't turn off (it could be that I didn't test long enough). Also, sometimes this weird behavior won't happen for a whole "PC use session", others times it will happen constantly.

It isn't the mouse, as I test it on my brother's notebook using Windows, and it didn't had any issue. Also, as I mentioned before at random sessions I don't have any trouble with it.
I don't know what log to look for, so here are some that made sense to me to collect:

System Information:

OS: Pop!_OS 22.04 LTS x86_64
Kernel: 6.17.4-76061704-generic
DE: GNOME 42.9
CPU: AMD Ryzen 5 2400G (8) @ 3.600GHz
GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series
Memory: 4903MiB / 21919MiB

grep "mouse" /var/log/syslog -> syslog_mouse.txt
dmesg | grep USB -> dmesg_USB.txt
journalctl -u systemd-udevd.service --since "2025-12-21" -> udev_log.txt

Somethings I already tried:

/sys/module/usbcore/parameters/autosuspend -> -1
sudo powertop -> Automatic Suspension Gaming Mouse = auto / Wake status for USB device 3-4 = Enable

Those didn't have any effect.
Thanks for any help.

 

[Trml]

That's very comprehensive log output!

Skimming the syslog it does look strange how frequently the mouse gets re-enumerated. It could be a wobbly connection. If your system has old (slow) ports e.g. USB2 even, try one of them. This simply to try another port, but the kernel may also use another driver mode.

Odd about the udev_log are those PoPOS mtp_probe's. MTP has to do with data transfer, not with HID (human input devices). You won't have that many devices as it probes, which probably is another sympton of the device getting dis-/reconnected.

You tried turning on autosuspend for the mouse. Did you also try disabling it? IMO you never want that setting for a mouse/keyboard, it should suspend when the system does and done.

I like powertop, great tool - but it's long I used it. You have to be careful since multiple settings can influence power control. To get to the bottom of the issue, I would remove any extra tweaking you have done with it. Simply let PoPOS defaults do the power handling and see if the mouse issue persists.

 

[bob466]

Some time ago I switched to a cordless mouse and I had a problem with it using Linux Mint...I kept forgetting to turn it off...bloody Linux.

 

[deb_user]

I would bet the rent money on a defective USB port.

 

[tpkusr]

Did you updated kernel recently? You can try little older kernel.

 

[daishishi]

Thanks for all the replies.

Some additional information:
The mouse is brand new, it is one and half month old, but I only used it some of the weekends I visit my parents. As it is in my second system, away from home.
I didn't tried to configure the mouse whatsoever, neither with something like the Piper application or using the windows app on a Windows System.
I lent the mouse to my brother this afternoon for a couple of days. He has a notebook with Windows and likes to play CS2, so if it is a hardware problem, I expect him to discover after 1-2 days. I will report back then.

To answer to maximum of questions I can:

It could be a wobbly connection

Yeah, that was my first/second hypothesis. However every time the problem appeared I tried to switch ports, and the problem persisted. The other hypothesis is the mouse itself, but if it is, then I don't think it is the cable. This because when I fiddle with the cable nothing happens (if the mouse it is on, messing with the cable won't turn it off, neither when it turns off fiddling with it turns back on). Maybe it is a problem with a chip or board of the mouse. :/

If your system has old (slow) ports e.g. USB2 even, try one of them

I think the front Ports are 2.0 (connector with black plastic), but I didn't check to see if they are routed to a native USB 2.0 header in the motherboard. I can do this later. I remember not having a issue with these ports, like I mentioned previously.
Currently the ports in the back of the case (the ones directly soldered in the motherboard) are USB 3.x, I think. The plastic inside the USB connector are dark blue or teal colored.

MTP has to do with data transfer, not with HID (human input devices).

Now that you mentioned I remember seeing the MTP acronym when plugging a android phone, maybe this is because it is a "gaming mouse" with an internal memory and different profiles.

You tried turning on autosuspend for the mouse. Did you also try disabling it?

No, I just dabble in the powertop app. I not comfortable using it as I don't know what it does. Maybe is better for me to reset everything and try safer and more 'traceable' options. So I will try to not mess with powertop and let Pop OS handle everything.

I would bet the rent money on a defective USB port.

I'm more keen on a defective mouse, because changing ports won't prevent the problem from occurring. I didn't had much time to test all possibilities, but I bet restarting the PC would wield different results. As sometimes (2-3 times) I didn't had any issue when using the PC (I always turn the PC off, never suspend or hibernate).

Did you updated kernel recently? You can try little older kernel.

I believe so, but not sure. Like I said above, the mouse is more than one month old, but I only use it in the weekends I come to my parents home. I don't remember if there was a kernel update after I started testing the mouse, however I think the problem it happened from the start.

-------

I will continue exploring the possibilities, the first one if it isn't a hardware problem. If it isn't, then I will try an USB 2.0 Port.
I really hope is more of a driver or kernel problem, so it can be fixed eventually. If it is a hardware problem, with the end of the year craziness, asking for the warranty will be such a headache.

Thanks everyone. I will keep you posted.