Unable to enumerate usb device linux

Какая-то проблема с USB.

Вот уже довольно продолжительное время система мне гадит в логи и консоль следующим сообщением:
Dec 11 08:13:41 s-main kernel: [127995.280050] hub 2-0:1.0: unable to enumerate USB device on port 4
Вообще-то она матюгалась и раньше, сообщением типа «over-current change on port такой-то», но это было относительно редко и рабочую консоль не затрагивало. Сейчас же, на новой убунте оно загаживает мне всю консоль так, что в ней невозможно работать.
Прошу помощи по устранению источника данной проблемы. Или подскажите хотя бы, как заблокировать вывод этого сообщения.

Судя по всему, это просто варнинг, и если USB работает, то это сообщение можно игнорировать.

Сейчас же, на новой убунте оно загаживает мне всю консоль так, что в ней невозможно работать.

Оно вообще на все консоли гадит? Что у тебя в настройках syslog’а?

>Судя по всему, это просто варнинг, и если USB работает, то это сообщение можно игнорировать.
Видимо, не просто. Один из портов на материнке не пашет как надо: мышка не загорается, мобилка пищит, зажигает лед, но не определяется.

Оно вообще на все консоли гадит?

Да, раз в секунду в активную консоль.

Что у тебя в настройках syslog’а?

Ты про /etc/logrotate.d/rsyslog или что-то другое?

Видимо, не просто. Один из портов на материнке не пашет как надо: мышка не загорается, мобилка пищит, зажигает лед, но не определяется.

А есть возможность проверить этот порт под другими операционными системами? Может он железно сломался.

Ты про /etc/logrotate.d/rsyslog или что-то другое?

Я хз как это в убунте выглядит. /etc/rsyslog.conf, /etc/rsyslog.d/ или как-то ещё. Смысл в том, что сообщения из журнала ядра в терминал (а так же в файлы /var/log или ещё куда-нибудь) перенаправляет syslog-демон. Существует несколько реализаций этого демона, в убунте вроде бы rsyslog.

Думаю, так и есть. Насчёт других операционок не знаю, но всякие разные линуксы на него тоже ругались, просто не так интенсивно.

Источник

Arch Linux

You are not logged in.

#1 2018-05-23 04:01:35

[Solved] usb usb2-port3: unable to enumerate USB device

Boot of OS stuck at

7.6435051 usb 2-3: device descriptor read/64, error -110
[ 7.876848] usb 2-3: device descriptor read/64, error -71
13.403401] usb 2-3: device descriptor read/64, error -110
23.8567271 usb 2-3: device descriptor read/64, error -110
25.020029] usb 2-3: device not accepting address 6, error -71
25.556693] usb 2-3: device not accepting address 7, error -71
25.557501] usb usb2-port3: unable to enumerate USB device

One of my usb port is not working in any os. I have Windows as dual boot. Last time I booted Windows and it updated something related to that port (which I am unable to rollback). After that when I booted back to arch, it stuck at enumerating that usb port.

Last edited by xyphanajay (2018-05-24 14:46:29)

Knowing is half the battle. DD!

#2 2018-05-23 06:29:43

Re: [Solved] usb usb2-port3: unable to enumerate USB device

First off all ensure to disable windows fastboot, https://www.tenforums.com/tutorials/418 … -10-a.html
If this is still an issue, ensure to isolate the usb stack, add «usbcore.nousb» as kernel parameter. The system should boot, albeit of course w/o any USB devices working (that can include keyboards even in notebooks)
You can then try «usbcore.old_scheme_first=1», but the single best solution to deal w/ a broken USB port (aside fixing it) would be to disable it in BIOS/UEFI (if possible)

#3 2018-05-23 07:22:11

Re: [Solved] usb usb2-port3: unable to enumerate USB device

I disabled fastboot mode. But nothing changed.

Then I add this parameter «usbcore.nousb» but an error pops up that can’t find command ‘usbcore.nousb’.

I checked my BIOS, there’s no option to disable any of my usb ports.

I am still stuck at the same page!

Edit: After adding kernel parameter «usbcore.nousb» that error didn’t appear but it didn’t booted, stuck at same place with no errors on screen.

Last edited by xyphanajay (2018-05-23 08:09:09)

Knowing is half the battle. DD!

#4 2018-05-23 07:36:32

Re: [Solved] usb usb2-port3: unable to enumerate USB device

Then I add this parameter «usbcore.nousb» but an error pops up that can’t find command ‘usbcore.nousb’.

It isn’t a command, it’s a Kernel Parameter.

No, it didn’t «fix» anything. It just shifted the brokeness one space to the right. — jasonwryan
Closing — for deletion; Banning — for muppetry. — jasonwryan

#5 2018-05-23 11:34:54

Re: [Solved] usb usb2-port3: unable to enumerate USB device

stuck at same place with no errors on screen

So the usb enumeration is most likely a red herring, try to boot into the multi-user.target or even the rescue.target, https://wiki.archlinux.org/index.php/Sy … _boot_into

#6 2018-05-23 14:39:01

Re: [Solved] usb usb2-port3: unable to enumerate USB device

I was able to switch btw ttyX, except tty1 which was stuck. Before trying multi-user.target, when I switch to other ttyX, tty1 stucm screen flashes continuously. So, I somehow logged in executed multi-user.target command. Next time when I booted, it reaches to tty1 login screen with usb error randomly appearing. I logged in and started sddm (systemctl start sddm) (I am using KDE Plasma). Screen started flashing again.

I think my GUI is causing this error, as the last thing that was checked successfully was Graphics.
So, I’ll try to install GUI or repair the existing one.

One more thing, on it’s last boot, I updated GUI using pacman -Syu which was interrupted few times due to slow network.

Last edited by xyphanajay (2018-05-23 17:07:12)

Knowing is half the battle. DD!

#7 2018-05-23 14:48:23

Re: [Solved] usb usb2-port3: unable to enumerate USB device

For the screen flashing, which drivers/hardware/xorg ddx are you using?

Regarding the update, if all of the packages successfully downloaded at some point and properly installed that should be relatively irrelevant, but you might still run e.g. a pacman -Qkk against the list of packages included in the last update.

Online

#8 2018-05-23 14:58:55

Re: [Solved] usb usb2-port3: unable to enumerate USB device

I’m not sure whether he really hits this in addition, but SDDM simply doesn’t start («surprise»).
@xyphanajay, please paste your Xorg log, see https://wiki.archlinux.org/index.php/Xorg#General for the location.
Also please notice that you can alter the targets at the bootloader commandline (rather than the bootloader config) just like the kernel parameters.

#9 2018-05-23 19:01:49

Re: [Solved] usb usb2-port3: unable to enumerate USB device

@xyphanajay, please paste your Xorg log

Knowing is half the battle. DD!

#10 2018-05-23 19:20:59

Re: [Solved] usb usb2-port3: unable to enumerate USB device

No DRM device and also no system bus, something went wrong w/ your update (at least this is broken beyond X11)

Источник

Ядро срёт в tty

dmesg|tail
[ 777.908038] hub 1-0:1.0: unable to enumerate USB device on port 7
[ 778.120042] hub 2-0:1.0: unable to enumerate USB device on port 7
[ 778.360042] hub 1-0:1.0: unable to enumerate USB device on port 7
[ 778.572035] hub 2-0:1.0: unable to enumerate USB device on port 7
[ 778.812040] hub 1-0:1.0: unable to enumerate USB device on port 7
[ 779.024039] hub 2-0:1.0: unable to enumerate USB device on port 7
[ 779.264042] hub 1-0:1.0: unable to enumerate USB device on port 7
[ 779.476039] hub 2-0:1.0: unable to enumerate USB device on port 7
[ 779.716041] hub 1-0:1.0: unable to enumerate USB device on port 7
[ 779.928033] hub 2-0:1.0: unable to enumerate USB device on port 7

MoBo: ASUS M2NPV-VM
CPU: AMD Athlon 64 3500+
GPU: Palit GeForce G210

вывод lsusb показывайте

Что в юсб воткнуто?

У тебя в черепе насрано.

lsusb -v

Bus 002 Device 002: ID 03f0:070c Hewlett-Packard
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x03f0 Hewlett-Packard
idProduct 0x070c
bcdDevice 2.10
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 2
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 2
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 50
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 3
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 116
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 255
cannot read device status, Operation not permitted (1)

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
can’t get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 2.06
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
can’t get hub descriptor: Operation not permitted
can’t get device qualifier: Operation not permitted
can’t get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)

Источник

SUSE Support

Here When You Need Us

USB devices not available; unable to enumerate device error

This document (7002864) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Desktop 11
SUSE Linux Enterprise Server 11

Situation

USB devices are not detected or avaible for use when plugged into the USB ports.

dmesg command output and messages in /var/log/messages shows output similar to:

Resolution

With the 2.6.27 kernel, a USB bug was introduced with the power-saving modules. Traditionally, the USB hub or controller would wake up when a new device was plugged in. However, with the 2.6.27 kernel, the USB does not wake up. Currently there is no upstream patch.

hot fix
Before implementing the permanent fix, it is suggested that you test it first. Unplug your USB device, and then run,
echo -1> /sys/module/usbcore/parameters/autosuspend
Plug your USB device in. If it is detected then continue on to the permenant fix.

permanent fix
The autosuspend setting can be set at the loading of the USB module. The control of device parameters can be found in /etc/modprobe.conf, /etc/modprobe.conf.local and /etc/modprobe.d.

1. Create a file in /etc/modprobe.d called usbcore
2. Populate the file with the following

Additional Information

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented «AS IS» WITHOUT WARRANTY OF ANY KIND.

Источник