You are not logged in.
I switched to openrc, and this error comes up and stalls the boot process:
(copied manually, so it may have small errors)
waiting for uevents to be processed
error opening USB device 'descriptors' file
then my boot process is stalled untill ctrl+c is used to kill the stalled process. none of that shows up on /var/log/rc.log, which is a little odd.
Offline
Do you have any suspicious USB devices plugged in like a smartphone? I previously had problems with plugging my phone without switching it to USB mode and it caused boot freezes and errors.
Personal spot :: https://www.smirky.net/ :: Try not to get lost!
Offline
Do you have any suspicious USB devices plugged in like a smartphone? I previously had problems with plugging my phone without switching it to USB mode and it caused boot freezes and errors.
Nope, just a mouse. and the boot process sometimes continues on it's own.
Offline
What is the output of lsusb ?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
What is the output of lsusb ?
# lsusb
Bus 002 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 174f:147b Syntek
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 004: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0
Bus 005 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Offline
I think it's a bug of systemd , I found this information that may be helpful (The report refers to debian experimental which is also based in systemd, 6 December 2014):
https://www.mail-archive.com/debian-bug … 88218.html
Best Regards.
Offline
I think it's a bug of systemd , I found this information that may be helpful (The report refers to debian experimental which is also based in systemd, 6 December 2014):
I switched to openrc...
Offline
colegui wrote:I think it's a bug of systemd , I found this information that may be helpful (The report refers to debian experimental which is also based in systemd, 6 December 2014):
First post wrote:I switched to openrc...
Hello, sorry for the confusion, the message: "USB device error opening 'descriptors' file', also occurs randomly on my system:
root@archkde hector]# journalctl -b -7 | grep "error opening USB device"
dic 12 15:53:24 archkde systemd-udevd[181]: error opening USB device 'descriptors' file
dic 12 15:57:32 archkde systemd-udevd[181]: error opening USB device 'descriptors' file
I do not give importance to the error .. just like this other error:
cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"
Best Regards.
Offline
cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"
I too get this on shutdown on 3 arch installs.
Ancestoral Clan https://cirrus.freevar.com/mclean.html
Offline
You've a few things on the bus besides a wireless mouse
Bus 002 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 004: ID 174f:147b Syntek
Bus 005 Device 004: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0
A card reader, a Bluetooth controller, and a (I think) a camera.
Is there a card in the card reader? If so, try taking it out. If not, try putting one in
Does the card reader work? The Camera? The Bluetooth?
Check your logs for errors having to do with those.
BTW, my money is on that Syntek (camera?) thing. The details on the web of that device are sketchy at best.
Could you maybe post the full output of sudo lsusb -v
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
With OpenRC, eudev can be used as udev provider.
l0vot, you could downgrading eudev using following PKGBUILD and files:
http://sourceforge.net/projects/mefiles … .10.tar.gz
I tried downgrading on my system and it seems to be working, but I have yet to check if the USB descriptors error went away or not..
Last edited by aaditya (2014-12-14 12:23:25)
Offline
With OpenRC, eudev can be used as udev provider.
l0vot, you could downgrading eudev using following PKGBUILD and files:
http://sourceforge.net/projects/mefiles … .10.tar.gzI tried downgrading on my system and it seems to be working, but I have yet to check if the USB descriptors error went away or not..
The error is non-critical, and it doesn't stall the boot process anymore for some reason, it seems the more I use openrc the smoother the boot process goes, even if there are no updates, and I don't change anything. Sort of strange. in any case the problem is small enough now that it's not worth downgrading for.
Offline
I have arch with XBMC on raspberry and this is annoying to mount usb disks manually. How can i make this automatically?
I have the same error:
systemctl status systemd-udevd
* systemd-udevd.service - udev Kernel Device Manager
Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static; vendor preset: disabled)
Active: active (running) since Fri 2014-12-19 16:13:44 UTC; 8min ago
Docs: man:systemd-udevd.service(8)
man:udev(7)
Main PID: 299 (systemd-udevd)
CGroup: /system.slice/systemd-udevd.service
`-299 /usr/lib/systemd/systemd-udevd
Dec 19 16:13:44 alarmpi systemd[1]: Starting udev Kernel Device Manager...
Dec 19 16:13:44 alarmpi systemd-udevd[299]: starting version 218
Dec 19 16:13:44 alarmpi systemd[1]: Started udev Kernel Device Manager.
Dec 19 16:14:07 alarmpi systemd-udevd[299]: error opening USB device 'descriptors' file
Offline
skozco: you have hijacked a thread when a) you aren't even running Arch, b) you are using a completely different init system, and c) you clearly haven't bothered to read the thread: don't do it again.
Offline