On 11 May 2026 at 12:07, Robert Moskowitz via users wrote:
Date sent: Mon, 11 May 2026 12:07:59 -0400
Subject: Re: External mouse not working
To: Community support for Fedora users
<[email protected]>,
Marco Moock <[email protected]>
Send reply to: Community support for Fedora users
<[email protected]>
From: Robert Moskowitz via users
<[email protected]>
Copies to: Robert Moskowitz <[email protected]>
>
>
> On 5/11/26 11:37 AM, Marco Moock wrote:
> > Am 11.05.26 um 17:05 schrieb Robert Moskowitz via users:
> >> When I get home, I will try other meese, but what might I look for in
> >> errors indicating why the mouse is not working?
> >
> > Check if it is being detected in lsusb.
> > Also check dmesg for any errors.
>
> I just plugged the mouse in again. This notebook ONLY has usb-3 ports:
>
> # lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
> Bus 001 Device 003: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated
> Camera
> Bus 001 Device 032: ID 138a:0017 Validity Sensors, Inc. VFS 5011
> fingerprint sensor
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>
> And:
>
> [64398.333361] usb 1-1: new full-speed USB device number 33 using xhci_hcd
> [64398.446694] usb 1-1: device descriptor read/64, error -71
> [64398.662845] usb 1-1: device descriptor read/64, error -71
> [64398.878573] usb 1-1: new full-speed USB device number 34 using xhci_hcd
> [64398.991409] usb 1-1: device descriptor read/64, error -71
> [64399.207847] usb 1-1: device descriptor read/64, error -71
> [64399.310000] usb usb1-port1: attempt power cycle
> [64399.688594] usb 1-1: new full-speed USB device number 35 using xhci_hcd
> [64399.689041] usb 1-1: Device not responding to setup address.
> [64399.894181] usb 1-1: Device not responding to setup address.
> [64400.101340] usb 1-1: device not accepting address 35, error -71
> [64400.101516] usb 1-1: WARN: invalid context state for evaluate context
> command.
> [64400.213566] usb 1-1: new full-speed USB device number 36 using xhci_hcd
> [64400.213937] usb 1-1: Device not responding to setup address.
> [64400.421937] usb 1-1: Device not responding to setup address.
> [64400.629377] usb 1-1: device not accepting address 36, error -71
> [64400.629695] usb 1-1: WARN: invalid context state for evaluate context
> command.
> [64400.630048] usb usb1-port1: unable to enumerate USB device
>
> Any advise?
>
Found this on google.com AI
Technical Fixes (Linux)
If the hardware seems fine, try these software-level solutions:
Restart the xHCI Controller: You can force the USB controller to
re-initialize without rebooting the entire system by unbinding and
rebinding the driver:
bash
# Replace '0000:04:00.0' with your device ID from dmesg
echo -n "0000:04:00.0" | sudo tee
/sys/bus/pci/drivers/xhci_hcd/unbind
echo -n "0000:04:00.0" | sudo tee
/sys/bus/pci/drivers/xhci_hcd/bind
Use code with caution.
Adjust Initialization Scheme: Some older or non-standard devices
respond better to an alternate initialization sequence.
Create or edit /etc/modprobe.d/usbcore.conf and add:
options usbcore old_scheme_first=y
Disable USB Autosuspend: Power management settings can
sometimes cut power to a device before it fully enumerates. You
can test this by adding usbcore.autosuspend=-1 to your GRUB boot
parameters.
Does the mouse use aaa batteries, or does it have a rechargable
battery. Have a mouse that has a lithium battery, and has a usb-c
port that you have to plug it into to charge it.
Also, if uses a usb transmitter on computer end, might have to
select frequency on the actual mouse. Have one on windows 11
machine, and mouse has to be set to the 3rd frequency to work.
On 71 error it shows this info.
The error -71 is a "Protocol Error" (specifically -EPROTO), which
typically means the host controller (xHCI) and the device aren't
speaking the same language properly or the signal is being
corrupted.
Since your device was already failing the setup address (error 36),
the switch to error -71 often points toward hardware-level signal
degradation or a power issue rather than just a software timeout.
Common Causes & Fixes
EMI and Cable Quality: Error -71 is frequently caused by
electromagnetic interference. Use a shorter, high-quality, or
shielded USB cable.
Power Hunger: The device might be attempting to draw more
power than the port can provide during initialization.
Fix: Plug the device into a powered USB hub if possible.
USB 3.0 (xHCI) Incompatibility: Some full-speed (USB 1.1/2.0)
devices struggle with the aggressive power management or
handshake of USB 3.0/3.1 ports.
Fix: Try a dedicated USB 2.0 port (usually black, not blue) or
toggle XHCI Hand-off in your BIOS settings.
Kernel Bugs/Drivers: In some cases, the linux kernel version you
are running might have issues with specific xHCI implementations
>
> --
> _______________________________________________
> users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
> Do not reply to spam, report it:
> https://forge.fedoraproject.org/infra/tickets/issues/new
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:[email protected]
mailto:[email protected]
mailto:[email protected]
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
