Created attachment 299303 [details] Windows 10 Device Information kernel: usb 1-1.5: new high-speed USB device number 40 using ehci-pci kernel: usb 1-1.5: device descriptor read/64, error -71 kernel: usb 1-1.5: device descriptor read/64, error -71 kernel: usb 1-1.5: new high-speed USB device number 41 using ehci-pci kernel: usb 1-1.5: device descriptor read/64, error -71 kernel: usb 1-1.5: device descriptor read/64, error -71 kernel: usb 1-1-port5: attempt power cycle kernel: usb 1-1.5: new high-speed USB device number 42 using ehci-pci kernel: usb 1-1.5: device not accepting address 42, error -71 kernel: usb 1-1.5: new high-speed USB device number 43 using ehci-pci kernel: usb 1-1.5: device not accepting address 43, error -71 kernel: usb 1-1-port5: unable to enumerate USB device kernel: usb 1-1.5: new high-speed USB device number 44 using ehci-pci kernel: usb 1-1.5: device descriptor read/64, error -71 kernel: usb 1-1.5: device descriptor read/64, error -71 kernel: usb 1-1.5: new high-speed USB device number 45 using ehci-pci kernel: usb 1-1.5: device descriptor read/64, error -71 kernel: usb 1-1.5: device descriptor read/64, error -71 kernel: usb 1-1-port5: attempt power cycle kernel: usb 1-1.5: new high-speed USB device number 46 using ehci-pci kernel: usb 1-1.5: device not accepting address 46, error -71 kernel: usb 1-1.5: new high-speed USB device number 47 using ehci-pci kernel: usb 1-1.5: device not accepting address 47, error -71 kernel: usb 1-1-port5: unable to enumerate USB device
I am not aware of further device information. My hope was that only the device ID is missing somewhere? I am able to work-around this issue by specifying the driver details manually?
The most likely explanation is that the USB device, the cable, or the host controller hardware isn't working properly. Does the device work on other computers? Do other devices work when plugged into that USB port? You cannot work around the issue by specifying details manually.
@Alan Stern Same host controller, same port, same cable - both devices with mini-USB port. My mouse is working properly: kernel: usb 1-1.5: new full-speed USB device number 79 using ehci-pci kernel: usb 1-1.5: New USB device found, idVendor=25a7, idProduct=fa98, bcdDevice= 2.03 kernel: usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 kernel: usb 1-1.5: Product: 2.4G Dual Mode Mouse kernel: usb 1-1.5: Manufacturer: Compx kernel: input: Compx 2.4G Dual Mode Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/0003:25A7:FA98.0023/input/input74 kernel: hid-generic 0003:25A7:FA98.0023: input,hidraw6: USB HID v1.10 Mouse [Compx 2.4G Dual Mode Mouse] on usb-0000:00:1a.0-1.5/input0 kernel: input: Compx 2.4G Dual Mode Mouse Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.1/0003:25A7:FA98.0024/input/input75 kernel: input: Compx 2.4G Dual Mode Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.1/0003:25A7:FA98.0024/input/input76 kernel: input: Compx 2.4G Dual Mode Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.1/0003:25A7:FA98.0024/input/input77 kernel: hid-generic 0003:25A7:FA98.0024: input,hiddev100,hidraw7: USB HID v1.10 Keyboard [Compx 2.4G Dual Mode Mouse] on usb-0000:00:1a.0-1.5/input1 mtp-probe[214798]: checking bus 1, device 79: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5" mtp-probe[214798]: bus: 1, device: 79 was not an MTP device upowerd[843]: treating change event as add on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5 systemd-logind[471]: Watching system buttons on /dev/input/event27 (Compx 2.4G Dual Mode Mouse Keyboard) mtp-probe[214811]: checking bus 1, device 79: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5" mtp-probe[214811]: bus: 1, device: 79 was not an MTP device
I am able to force "full-speed" instead of "high-speed"? What is called "device number" here - it will be increased more often in case of failure? Just to avoid USB "index"/"name" conflicts?
(In reply to Stefan.Lauterwasser from comment #3) Both devices with micro-USB not mini-USB.
@Alan Stern You are right, it's working on an other port and with an other (shorter) cable. It's a non-USB 3.0 port also - port is not blue at least. I am so happy - thought I tried all ports already, sorry. :-/ kernel: usb 1-1.4: new high-speed USB device number 80 using ehci-pci kernel: usb 1-1.4: New USB device found, idVendor=054c, idProduct=0bdf, bcdDevice= 1.00 kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: usb 1-1.4: Product: WALKMAN kernel: usb 1-1.4: Manufacturer: Sony kernel: usb 1-1.4: SerialNumber: 10455F55708440 kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected kernel: scsi host8: usb-storage 1-1.4:1.0 mtp-probe[215847]: checking bus 1, device 80: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4" mtp-probe[215847]: bus: 1, device: 80 was not an MTP device mtp-probe[215848]: checking bus 1, device 80: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4" mtp-probe[215848]: bus: 1, device: 80 was not an MTP device kernel: scsi 8:0:0:0: Direct-Access SONY WALKMAN 1.00 PQ: 0 ANSI: 2 kernel: sd 8:0:0:0: Attached scsi generic sg2 type 0 kernel: sd 8:0:0:0: [sdc] 7032832 512-byte logical blocks: (3.60 GB/3.35 GiB) kernel: sd 8:0:0:0: [sdc] Write Protect is off kernel: sd 8:0:0:0: [sdc] Mode Sense: 0b 00 00 00 kernel: sd 8:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: sdc: sdc1 kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk udisksd[1208]: Mounted /dev/sdc1 at /run/media/<user>/WALKMAN on behalf of uid 1000
That makes no sense - it must be the cable now. Device now works on each port with other cable.