Unable to enumerate usb device error 71

Проблема такая есть: на буке стоит Ubuntu 8.04 kernel 2.6.24-19. Вчера пробовал поставить модем он у меня winmodem, полазив по форуму нашел что нужны дрова от slamr-2.6.24-19-generic попробовал поставил - модем неопределился, пробовал скомпилить из slmodem-2.9.11-20080803, тоже ничего не вышло, перегрузился и у меня отвалилась мышка usb, родной тачпад работает.
  • Печать

Страницы: [1]   Вниз

Тема: USB ошибка 71  (Прочитано 6367 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
Берия

Проблема такая есть: на буке стоит Ubuntu 8.04 kernel 2.6.24-19. Вчера пробовал поставить модем он у меня winmodem, полазив по форуму нашел что нужны дрова от slamr-2.6.24-19-generic попробовал поставил — модем неопределился, пробовал скомпилить из slmodem-2.9.11-20080803, тоже ничего не вышло, перегрузился и у меня отвалилась мышка usb, родной тачпад работает. Сегодня поробывал другую мышу результат — неопределяется, собщения в логах:
Aug  5 15:43:35 linux kernel: [  234.251849] usb 3-2: new low speed USB device using uhci_hcd and address 2
Aug  5 15:43:35 linux kernel: [  234.371735] usb 3-2: device descriptor read/64, error -71
Aug  5 15:43:35 linux kernel: [  234.595506] usb 3-2: device descriptor read/64, error -71
Aug  5 15:43:35 linux kernel: [  234.811289] usb 3-2: new low speed USB device using uhci_hcd and address 3
Aug  5 15:43:36 linux kernel: [  234.931143] usb 3-2: device descriptor read/64, error -71
Aug  5 15:43:36 linux kernel: [  235.158922] usb 3-2: device descriptor read/64, error -71
Aug  5 15:43:36 linux kernel: [  235.374641] usb 3-2: new low speed USB device using uhci_hcd and address 4
Aug  5 15:43:36 linux kernel: [  235.782243] usb 3-2: device not accepting address 4, error -71
Aug  5 15:43:37 linux kernel: [  235.894127] usb 3-2: new low speed USB device using uhci_hcd and address 5
Aug  5 15:43:37 linux kernel: [  236.305725] usb 3-2: device not accepting address 5, error -71

гугл не дал информации по этому поводу, на форуме тоже не нашел ничего подобного.
причем попробывал web камеру подключилась пес проблем, а вот флешка не хочет подключаться, встроенный кард ридер все видет беспроблем!
Чем можно исправить данную ситуацию?(кроме переустановки :) )

Оффлайн
DALDON

Имею нечто подобное при загрузке настольного ПК. Но всё USB устройства работают без проблем — собственно увидил когда отключил сплеш заставку. Ну вот первое, что приходит в голову это удалить пакеты которые ставили? И потом гуглить снова на тему установки модема. И посмотреть куда раскидал пакет файлы/конфиги, всё удалить.

Оффлайн
Берия

Пробовал. Удалил все пакеты от модема — ошибка осталась.

Оффлайн
shagrat

Aug  5 15:43:35 linux kernel: [  234.371735] usb 3-2: device descriptor read/64, error -71

У меня таже проблема….. в lsusb видит все а никакие устройства работать не хотят, я думаю это система мою материнку принимать никак не хочет
Материнка: Acorp 7NFU400(U)
PS: Может есть у кого дрова на эту материнку???

almur

Аналогичная ошибка на этапе загрузки ядра иногда проскакивает! Никаких ошибок или глюков ЮСБ при работе нет и не было. Предлагаю просто не обращать внимания

  • Печать

Страницы: [1]   Вверх

Источник

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:

usb 1-6: new high speed USB device using ehci_hcd and address 4
usb 1-6: device not accepting address 4, error -71
hub 1-0:1.0: unable to enumerate USB device on port 6

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

    options usbcore autosuspend=-1

  3. Save the file
  4. Run «mkinitrd» (If you are sure that no USB device modules are loaded via the initrd, then you can skip this step)
  5. Reboot

 

Additional Information

This issue has been found to affect USB based printers, storage devices, keyboards and mice.

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.

  • Document ID:7002864
  • Creation Date:
    30-Mar-2009
  • Modified Date:16-Mar-2021
    • SUSE Linux Enterprise Desktop
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

Источник

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

xyphanajay
Member
Registered: 2018-05-22
Posts: 7

[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

seth
Member
Registered: 2012-09-03
Posts: 35,320

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

xyphanajay
Member
Registered: 2018-05-22
Posts: 7

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

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

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

xyphanajay wrote:

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

aur — dotfiles

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

seth
Member
Registered: 2012-09-03
Posts: 35,320

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

xyphanajay
Member
Registered: 2018-05-22
Posts: 7

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

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 18,304

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

For the stuck at boot: https://bbs.archlinux.org/viewtopic.php?id=236696

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.

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

seth
Member
Registered: 2012-09-03
Posts: 35,320

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

xyphanajay
Member
Registered: 2018-05-22
Posts: 7

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

seth wrote:

@xyphanajay, please paste your Xorg log

Xorg.0.log

[   178.168] (--) Log file renamed from "/var/log/Xorg.pid-20845.log" to "/var/log/Xorg.0.log"
[   178.169] 
X.Org X Server 1.20.0
X Protocol Version 11, Revision 0
[   178.169] Build Operating System: Linux Arch Linux
[   178.169] Current Operating System: Linux senpai 4.16.5-1-ARCH #1 SMP PREEMPT Thu Apr 26 16:53:40 UTC 2018 x86_64
[   178.169] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=0f6a9e7c-eb28-43ba-aa10-1028906abe20 rw quiet
[   178.169] Build Date: 16 May 2018  05:24:07PM
[   178.169]  
[   178.169] Current version of pixman: 0.34.0
[   178.169] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   178.169] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   178.169] (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 23 19:55:56 2018
[   178.169] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   178.169] (==) No Layout section.  Using the first Screen section.
[   178.169] (==) No screen section available. Using defaults.
[   178.169] (**) |-->Screen "Default Screen Section" (0)
[   178.169] (**) |   |-->Monitor "<default monitor>"
[   178.170] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   178.170] (==) Automatically adding devices
[   178.170] (==) Automatically enabling devices
[   178.170] (==) Automatically adding GPU devices
[   178.170] (==) Automatically binding GPU devices
[   178.170] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   178.170] (WW) The directory "/usr/share/fonts/misc" does not exist.
[   178.170] 	Entry deleted from font path.
[   178.170] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[   178.170] 	Entry deleted from font path.
[   178.170] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[   178.170] 	Entry deleted from font path.
[   178.170] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[   178.170] 	Entry deleted from font path.
[   178.170] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[   178.170] 	Entry deleted from font path.
[   178.170] (==) FontPath set to:
	/usr/share/fonts/TTF
[   178.170] (==) ModulePath set to "/usr/lib/xorg/modules"
[   178.170] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   178.170] (II) Module ABI versions:
[   178.170] 	X.Org ANSI C Emulation: 0.4
[   178.170] 	X.Org Video Driver: 24.0
[   178.170] 	X.Org XInput driver : 24.1
[   178.170] 	X.Org Server Extension : 10.0
[   178.170] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)
[   178.170] (++) using VT number 1

[   178.170] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[   178.173] (--) PCI:*(0@0:2:0) 8086:0a16:103c:2212 rev 11, Mem @ 0xb5000000/4194304, 0xc0000000/268435456, I/O @ 0x00006000/64, BIOS @ 0x????????/131072
[   178.173] (--) PCI: (9@0:0:0) 10de:1140:103c:2212 rev 161, Mem @ 0xb3000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00003000/128
[   178.173] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   178.173] (II) LoadModule: "glx"
[   178.174] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   178.175] (II) Module glx: vendor="X.Org Foundation"
[   178.176] 	compiled for 1.20.0, module version = 1.0.0
[   178.176] 	ABI class: X.Org Server Extension, version 10.0
[   178.176] (==) Matched intel as autoconfigured driver 0
[   178.176] (==) Matched modesetting as autoconfigured driver 1
[   178.176] (==) Matched fbdev as autoconfigured driver 2
[   178.176] (==) Matched vesa as autoconfigured driver 3
[   178.176] (==) Assigned the driver to the xf86ConfigLayout
[   178.176] (II) LoadModule: "intel"
[   178.176] (WW) Warning, couldn't open module intel
[   178.176] (EE) Failed to load module "intel" (module does not exist, 0)
[   178.176] (II) LoadModule: "modesetting"
[   178.176] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   178.177] (II) Module modesetting: vendor="X.Org Foundation"
[   178.177] 	compiled for 1.20.0, module version = 1.20.0
[   178.177] 	Module class: X.Org Video Driver
[   178.177] 	ABI class: X.Org Video Driver, version 24.0
[   178.177] (II) LoadModule: "fbdev"
[   178.177] (WW) Warning, couldn't open module fbdev
[   178.177] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   178.177] (II) LoadModule: "vesa"
[   178.177] (WW) Warning, couldn't open module vesa
[   178.177] (EE) Failed to load module "vesa" (module does not exist, 0)
[   178.177] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   178.177] (EE) open /dev/dri/card0: No such file or directory
[   178.177] (WW) Falling back to old probe method for modesetting
[   178.177] (EE) open /dev/dri/card0: No such file or directory
[   178.177] (EE) Screen 0 deleted because of no matching config section.
[   178.177] (II) UnloadModule: "modesetting"
[   178.177] (EE) Device(s) detected, but none match those in the config file.
[   178.177] (EE) 
Fatal server error:
[   178.177] (EE) no screens found(EE) 
[   178.178] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[   178.178] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   178.178] (EE) 
[   178.182] (EE) Server terminated with error (1). Closing log file.

Knowing is half the battle. DD!

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

seth
Member
Registered: 2012-09-03
Posts: 35,320

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

dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)
open /dev/dri/card0: No such file or directory

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

Check

uname -a
pacman -Qs linux
dmesg

#11 2018-05-23 19:26:31

xyphanajay
Member
Registered: 2018-05-22
Posts: 7

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.

Few warnings came on pacman — Qkk.
Screen flashes when I execute systemctl start sddm (on using kernel parameter — multi-user.target).
I don’t know where to see for drivers/hardware/xorg! I tried but unable to find it.
Also right now, I am unable to configure network as it’s not detectimg my wifi or ethernet adapter. ifconfig is showing loop back adapter — lo, only.

Last edited by xyphanajay (2018-05-23 19:29:01)

Knowing is half the battle. DD!

#12 2018-05-23 19:35:48

seth
Member
Registered: 2012-09-03
Posts: 35,320

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

Also right now, I am unable to configure network as it’s not detectimg my wifi or ethernet adapter.

With a 99.99% chance you’re not running the installed kernel, ie. you simply forgot to mount the /boot directory when updating.
See https://wiki.archlinux.org/index.php/Pa … an_upgrade on how to update the system offline, ensure to mount /boot of the installed system and re-install the kernel.

#13 2018-05-23 19:37:41

xyphanajay
Member
Registered: 2018-05-22
Posts: 7

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

seth wrote:

Check

uname -a
pacman -Qs linux
dmesg

uname — a
Linux senpai 4.16.5-1-Arch #1 SMP PREEMPT Thu Apr 26 16:53:40 UTC 2018 x86_64 GNU/LINUX

pacman — Qs linux
Nothing exceptional occured, showed installed packages.

dmesg
Few errors for usb, as expected.

Knowing is half the battle. DD!

#14 2018-05-23 19:40:06

seth
Member
Registered: 2012-09-03
Posts: 35,320

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

pacman — Qs linux
Nothing exceptional occured, showed installed packages.

That’s not the correct command and the idea is to compare the installed kernel w/ the running one.
Since however the most recent one is 4.16.10, there’s your problem. See comment #12.

#15 2018-05-24 06:24:30

xyphanajay
Member
Registered: 2018-05-22
Posts: 7

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

It worked. Thanks for you much meeded help.

Knowing is half the battle. DD!

Источник

3 / 3 / 0

Регистрация: 05.01.2015

Сообщений: 41

1

21.09.2022, 10:19. Показов 540. Ответов 2

Доброго времени суток!

Столкнулся с такой проблемой. На стеренький компьютер с материнской платой GF615M-P33 (MS-7597) поставил Ubuntu 20.04. Все работало просто замечательно (включение, выключение и сама работа) в течении недели. Однако после отключения питания из сети и последуещего включения компа через 4 дня, при загрузке стали выскакивать ошибки как в названии топика (фотку с экрана прилагаю). На просторах интернета ошибку 71 не нашел. Подозреваю что проблема в настройках биоса — т.к. компутер старенький батарейка быстро разряжается и при загрузке приходится нажимать кнопку с настройками биоса по умолчанию.

Подскажите, как исправить эту проблему?

P.S. После включения из 8 usb-портов работает только 1.

Миниатюры

usb1-1: device not accepting address, error - 71
 

__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь



0

Почетный модератор

11295 / 4264 / 437

Регистрация: 12.06.2008

Сообщений: 12,281

21.09.2022, 21:24

2

По какой-то причине USB-контроллеру приходит повреждённый пакет данных. Возможно, хаб сгорел. Правильно я понимаю, что все устройства 1-* выдают такую ошибку, а 2-* работают нормально? Если так, то, видимо, проблемы с хабом, который распаян на плате.



0

3 / 3 / 0

Регистрация: 05.01.2015

Сообщений: 41

22.09.2022, 13:53

 [ТС]

3

Humanoid,
спасибо что откликнулись! Работает только 1 порт. Все таки я думаю проблема в настройках биоса. Пото как это второй раз происходит. Где-то в середине лета я поставил ubuntu 20.04 на комп и до первого длительного отключения питания все работало нормально. Потом при включении стали появляться эти ошибки — тогда я не придавал этому большого значения так как я использовал единственный работающий порт — только мышка была подключена. В августе накатил обновление 22.04 и у меня отвалилось несколько нужных програм — эту проблему исправить не удалось и 2 недели назад заново установил 20.04. И опять же все работало хорошо до первого длительного отключения. Вот на просторах интернета наткнулся на похожую тему, там предложили такое решение:

Цитата
Сообщение от Isabele AA

This doesn’t work for me, but I’ll leave here the solution that I fund in:
«unix.stackexchange.com/questions/72625/why-is-usb-not-working-in-linux-when-it-works-in-uefi-bios»

I hope that this would help someone.

«It seems with newer Gigabyte mainboards (at least) there is a BIOS option called IOMMU Controller that is disabled by default and gives no clue or indication as to what it is for.

Enabling this setting and rebooting «magically» restores all my USB and networking problems in a 64-bit Linux OS (doesn’t matter which one).»

If this also doesn’t work, yu can try adding «iommu=soft» to the kernel command line.

Однако в моем биосе нет опции IOMMU.

Добавлено через 2 часа 23 минуты
Проблема решена! Дело было действительно в настройках биоса. Помогло отключение опции «USB Device Legacy Support» и все заработало).



0
Источник

I had Mint 19 and decided to do a fresh install for 20.1 (64 bit Cinnamon). In the installer, as I normally do, I chose “Something else”. I set up my partitions, choosing to format boot, var, root (/), home and home/alan (my personal partition). Other partitions on other drives were set up as well but none of those was set to format. Nothing different there – I have used this setup over many Mint versions. Once installation was complete I created a Timeshift snapshot., then installed numlockx (and activated it) and Gparted. Again nothing unusual there. Then, in Update manager, I selected the fastest mirror before installing the new version of Update Manager before installing all 50 updates plus the 10 additional changes.

At this point I rebooted and am presented with this error message:

Code: Select all

[	1.964030] usb 2-4: device read/64, error -71
[	2.212033] usb 2-4: device read/64, error -71
[	2.668041] usb 2-4: device read/64, error -71
[	2.940045] usb 2-4: device read/64, error -71
[	3.932089] usb 2-4: device not accepting address 5, error -71
[	4.404143] usb 2-4: device not accepting address 5, error -71
[	4.484175] usb usb2-port4: unable to enumerate usb device
You are in emergency mode. After logging in , type “journalctl -xb1” to view
system logs, “systemctl reboot” to reboot, systemctl default” or “exit”
to boot into default mode.
Press Enter for maintenance
(or press Control-D to continue):

I am writing this on a different machine so cannot shew the output of any commands. On the apparently defective machine if I look at the logs I do not know what I should look for, I am not sure what “”default mode” is; the implication is that it is somehow different from compatibility mode, and if I press “enter” to continue where would that take me. The options are for ‘those that know’ I am not one of that elite class of users.

That is where I am at at present. The message remains on the screen as I have done nothing. I am just hoping that someone might be able to drop a hint or two. Any (all sensible) suggestions please?. Should I cut my losses and do another installation? I do not know if I should try looking at the logs but if I did that I would not know what to look for.

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

Источник

  1. Error: unable to enumerate USB device on port 1

    Hi, I am having trouble with my WD my home external hdd. I have been using it on ubuntu for about a month, then all of a sudden it doesn’t work anymore as soon as I plug it in. When I plug it in, the hdd turns on, and dmesg will say this over and over, sometimes for 10 mins straight…

    [ 600.209066] usb 1-1: new high speed USB device using ehci_hcd and address 29
    [ 600.264462] hub 1-0:1.0: unable to enumerate USB device on port 1
    [ 600.453366] hub 1-0:1.0: unable to enumerate USB device on port 1
    [ 600.641350] hub 1-0:1.0: unable to enumerate USB device on port 1
    [ 600.828449] hub 1-0:1.0: unable to enumerate USB device on port 1
    [ 601.016974] hub 1-0:1.0: unable to enumerate USB device on port 1
    [ 601.277215] usb 3-1: new full speed USB device using uhci_hcd and address 2

    but eventually it will work and detect the hdd. I have tried multiple cords, and all of my ports, nothing works. I have also reinstalled ubuntu, and it does it when loading from ubuntu cd. But I have loaded up gentoo a few times from cd, and it has not done it. Does anyone know what is wrong?

  2. Re: Error: unable to enumerate USB device on port 1

  3. Re: Error: unable to enumerate USB device on port 1

    Hello brother,
    I have turned to Linux hoping it will solve my problem that my hard drive which is receiving a msg regarding my USB Hard Disk «This device cannot start. (Code 10)»

    I have chosen Ubuntu due to recoomendation by a frnd and his advocacy that Ubuntu has huge support and that he has not faced any prob whatsoever whne he used Ubuntu.

    I think the problem is because I reinstallled XP sp2, which in turn I did because the HD was running well on my Dell Laptop but its not working on my Desktop…

    Another prob is that scrolling on my desktop CRT monitor has suddenly become discrete after I reinstalled XP sp2…

    I cant change my Monitor’s refresh rate…Earlier I could change it from 60 Hz to 85Hz…

    DO U THINK UBUNTU WILL SOLVE THESE PROBLEMS FOR ME?

  4. Re: Error: unable to enumerate USB device on port 1

    @AcidRain0

    I am having this problem too with my external USB 2.0 hard drives on a new Dell T300.

    Dell product sheet for T300 claims all USB ports are 2.0, but only front ports are identified as 2.0 capable and the rear ports are identified as 1.1, which is untenable for any backup capabilities.

    lsusb:
    Bus 001 Device 004: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 «TetraHub»
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 003: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
    Bus 004 Device 002: ID 413c:3010 Dell Computer Corp. Optical Wheel Mouse
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

    I am running 9.10 and have tried slipping usb_storage into /etc/modules per a bug report I found on launchpad to no luck.

    I was actually able to get this device mounted at one time by plugging and replugging it, over and over. It’s not a solution by any means. I have also tried swapping cables and all, USB drive mounts fine on other platforms/machines.

    dmesg snipit:
    [ 28.820491] usb 1-7.2: new high speed USB device using ehci_hcd and address 9
    [ 28.900113] usb 1-7.2: device descriptor read/64, error -71
    [ 29.090119] usb 1-7.2: device descriptor read/64, error -71
    [ 29.280115] usb 1-7.2: new high speed USB device using ehci_hcd and address 10
    [ 29.360115] usb 1-7.2: device descriptor read/64, error -71
    [ 29.550114] usb 1-7.2: device descriptor read/64, error -71
    [ 29.741368] usb 1-7.2: new high speed USB device using ehci_hcd and address 11
    [ 30.160031] usb 1-7.2: device not accepting address 11, error -71
    [ 30.240120] usb 1-7.2: new high speed USB device using ehci_hcd and address 12
    [ 30.660021] usb 1-7.2: device not accepting address 12, error -71
    [ 30.660128] hub 1-7:1.0: unable to enumerate USB device on port 2

  5. Re: Error: unable to enumerate USB device on port 1

    Hi,
    Does anyone have already solved this bug?

  6. Re: Error: unable to enumerate USB device on port 1

    Anyone looked more into this I’m geeting the same error

  7. Re: Error: unable to enumerate USB device on port 1

    Have you tried external power, or at least using second usb port for power ??

    Linux Registered User #443947 Ubuntu Regestered User #12604

    Hakunamatata …… No worries !

  8. Re: Error: unable to enumerate USB device on port 1

    I have indeed, although I’m beginning to suspect there is a hardware faliure involved. The harddrive doesn’t work in windows XP or Windows 7 either.

  9. Re: Error: unable to enumerate USB device on port 1

    unable to enumerate USB device on port 1

    is the same error I’m getting on my front usb ports and I know it’s not a hardware issue since they worked fine earlier. I have 2 partitions, one is running Ubuntu 9.04 and the other is running Mint 8. Same problem on both sides.

  10. Re: Error: unable to enumerate USB device on port 1

    I have the same problem. Harddrive definitely works (tried it on my friend’s laptop running Windows XP). Tried different USB port, different USB cable all with the same problem. I have ntfs-3g installed, my other NTFS formatted harddrive works fine.

    # dmesg | tail
    [ 4088.476361] hub 1-0:1.0: unable to enumerate USB device on port 3
    [ 4088.664368] hub 1-0:1.0: unable to enumerate USB device on port 3
    [ 4088.852362] hub 1-0:1.0: unable to enumerate USB device on port 3
    [ 4089.040354] hub 1-0:1.0: unable to enumerate USB device on port 3

    can’t even try mounting it, doesn’t show up in fdisk -l

    Anyone find a solution? If I find something that works I’ll post it.

Источник

Понравилась статья? Поделить с друзьями:
  • Unable to enum cuda gpus unknown error
  • Unable to enter game generic bad file diablo 2 как исправить
  • Unable to enter game bad header diablo 2 как исправить
  • Unable to elevate error 1058
  • Unable to download video data http error 403 forbidden