You are not logged in.
Pages: 1
Hi,
for the last two days or so I've been unable to use any usb devices with my Arch (linux 3.7.7-1) machine.
As far as I can tell the usb devices are not detected at all - at least I get neither error messages during boot (journactl -b has nothing related as far as I can tell) nor any other errors I can find. udevadm monitor doesn't register anything when I plug/unpug in my usbkeyboard/mouse. The only message I do get is:
lsusb
unable to initialize libusb: -99
The keyboard works in grub2 and bios so I guess it is no hardware error? To be honest I'm completely at a loss as how to tackle this problem any help would be greatly appreciated!
iardis
journalctl -b -p5
-- Logs begin at Fri 2012-11-02 15:27:52 CET, end at Thu 2013-02-14 10:16:49 CET. --
Feb 14 09:37:04 barbosa kernel: Linux version 3.7.7-1-ARCH (nobody@foutrelis) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Feb 11 20:20:58 EET 2013
Feb 14 09:37:04 barbosa kernel: ACPI: RSDP 00000000000f00e0 00024 (v04 LENOVO)
Feb 14 09:37:04 barbosa kernel: ACPI: XSDT 00000000baffe120 00084 (v01 LENOVO TP-8Q 00001090 PTEC 00000002)
Feb 14 09:37:04 barbosa kernel: ACPI: FACP 00000000bafeb000 000F4 (v03 LENOVO TP-8Q 00001090 PTL 00000002)
Feb 14 09:37:04 barbosa kernel: ACPI: DSDT 00000000bafee000 0F7A3 (v02 LENOVO SNB-CPT 00000000 INTL 20061109)
Feb 14 09:37:04 barbosa kernel: ACPI: FACS 00000000baf3c000 00040
Feb 14 09:37:04 barbosa kernel: ACPI: ASF! 00000000bafed000 000A5 (v32 LENOVO TP-8Q 00001090 PTL 00000002)
Feb 14 09:37:04 barbosa kernel: ACPI: HPET 00000000bafea000 00038 (v01 LENOVO TP-8Q 00001090 PTL 00000002)
Feb 14 09:37:04 barbosa kernel: ACPI: APIC 00000000bafe9000 00098 (v01 LENOVO TP-8Q 00001090 PTL 00000002)
Feb 14 09:37:04 barbosa kernel: ACPI: MCFG 00000000bafe8000 0003C (v01 LENOVO TP-8Q 00001090 PTL 00000002)
Feb 14 09:37:04 barbosa kernel: ACPI: SLIC 00000000bafe7000 00176 (v01 LENOVO TP-8Q 00001090 PTEC 00000001)
Feb 14 09:37:04 barbosa kernel: ACPI: TCPA 00000000bafe6000 00032 (v02 PTL LENOVO 06040000 LNVO 00000001)
Feb 14 09:37:04 barbosa kernel: ACPI: SSDT 00000000bafe5000 006FC (v01 PmRef Cpu0Ist 00003000 INTL 20061109)
Feb 14 09:37:04 barbosa kernel: ACPI: SSDT 00000000bafe4000 00996 (v01 PmRef CpuPm 00003000 INTL 20061109)
Feb 14 09:37:04 barbosa kernel: ACPI: UEFI 00000000bafe3000 0003E (v01 LENOVO TP-8Q 00001090 PTL 00000002)
Feb 14 09:37:04 barbosa kernel: ACPI: UEFI 00000000bafe2000 00042 (v01 PTL COMBUF 00000001 PTL 00000001)
Feb 14 09:37:04 barbosa kernel: ACPI: UEFI 00000000bafe1000 002A6 (v01 LENOVO TP-8Q 00001090 PTL 00000002)
Feb 14 09:37:04 barbosa kernel: Zone ranges:
Feb 14 09:37:04 barbosa kernel: DMA [mem 0x00010000-0x00ffffff]
Feb 14 09:37:04 barbosa kernel: DMA32 [mem 0x01000000-0xffffffff]
Feb 14 09:37:04 barbosa kernel: Normal [mem 0x100000000-0x13fdfffff]
Feb 14 09:37:04 barbosa kernel: Movable zone start for each node
Feb 14 09:37:04 barbosa kernel: Early memory node ranges
Feb 14 09:37:04 barbosa kernel: node 0: [mem 0x00010000-0x0009cfff]
Feb 14 09:37:04 barbosa kernel: node 0: [mem 0x00100000-0xbac4afff]
Feb 14 09:37:04 barbosa kernel: node 0: [mem 0xbafff000-0xbaffffff]
Feb 14 09:37:04 barbosa kernel: node 0: [mem 0x100000000-0x13fdfffff]
Feb 14 09:37:04 barbosa kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 1005908
Feb 14 09:37:04 barbosa kernel: Policy zone: Normal
Feb 14 09:37:04 barbosa kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=f4b7c604-3a40-4693-bac1-7450ab7a55dc ro quiet ipv6.disable=1
Feb 14 09:37:04 barbosa kernel: __ex_table already sorted, skipping sort
Feb 14 09:37:04 barbosa kernel: [117B blob data]
Feb 14 09:37:04 barbosa kernel: mtrr: your CPUs had inconsistent variable MTRR settings
Feb 14 09:37:04 barbosa kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Feb 14 09:37:04 barbosa kernel: ACPI: SSDT 00000000baecf018 00835 (v01 PmRef Cpu0Cst 00003001 INTL 20061109)
Feb 14 09:37:04 barbosa kernel: ACPI: Dynamic OEM Table Load:
Feb 14 09:37:04 barbosa kernel: ACPI: SSDT (null) 00835 (v01 PmRef Cpu0Cst 00003001 INTL 20061109)
Feb 14 09:37:04 barbosa kernel: ACPI: SSDT 00000000baed0a98 00303 (v01 PmRef ApIst 00003000 INTL 20061109)
Feb 14 09:37:04 barbosa kernel: ACPI: Dynamic OEM Table Load:
Feb 14 09:37:04 barbosa kernel: ACPI: SSDT (null) 00303 (v01 PmRef ApIst 00003000 INTL 20061109)
Feb 14 09:37:04 barbosa kernel: ACPI: SSDT 00000000baeced98 00119 (v01 PmRef ApCst 00003000 INTL 20061109)
Feb 14 09:37:04 barbosa kernel: ACPI: Dynamic OEM Table Load:
Feb 14 09:37:04 barbosa kernel: ACPI: SSDT (null) 00119 (v01 PmRef ApCst 00003000 INTL 20061109)
Feb 14 09:37:04 barbosa kernel: type=2000 audit(1360831022.123:1): initialized
Feb 14 09:37:04 barbosa kernel: VFS: Disk quotas dquot_6.5.2
Feb 14 09:37:04 barbosa kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 14 09:37:04 barbosa kernel: Key type dns_resolver registered
Feb 14 09:37:04 barbosa kernel: SCSI subsystem initialized
Feb 14 09:37:04 barbosa kernel: scsi 0:0:0:0: Direct-Access ATA M4-CT064M4SSD2 0002 PQ: 0 ANSI: 5
Feb 14 09:37:04 barbosa kernel: sd 0:0:0:0: [sda] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
Feb 14 09:37:04 barbosa kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 14 09:37:04 barbosa kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 14 09:37:04 barbosa kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 14 09:37:04 barbosa kernel: ACPI Warning:
Feb 14 09:37:04 barbosa kernel: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1
Feb 14 09:37:04 barbosa kernel: (20120913/utaddress-251)
Feb 14 09:37:04 barbosa kernel: ACPI Warning:
Feb 14 09:37:04 barbosa kernel: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPIO 1
Feb 14 09:37:04 barbosa kernel: (20120913/utaddress-251)
Feb 14 09:37:04 barbosa kernel: ACPI Warning:
Feb 14 09:37:04 barbosa kernel: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1
Feb 14 09:37:04 barbosa kernel: (20120913/utaddress-251)
Feb 14 09:37:04 barbosa kernel: ACPI Warning:
Feb 14 09:37:04 barbosa kernel: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1
Feb 14 09:37:04 barbosa kernel: (20120913/utaddress-251)
Feb 14 09:37:04 barbosa kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Feb 14 09:37:04 barbosa kernel: rts_pstor: module is from the staging directory, the quality is unknown, you have been warned.
Feb 14 09:37:04 barbosa kernel: ACPI Warning: 0x000000000000efa0-0x000000000000efbf SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120913/utaddress-251)
Feb 14 09:37:05 barbosa ntpd[297]: ntpd 4.2.6p5@1.2349-o Tue Dec 18 22:48:42 UTC 2012 (1)
Feb 14 09:37:05 barbosa ntpd[300]: proto: precision = 0.130 usec
Feb 14 09:37:05 barbosa avahi-daemon[298]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Feb 14 09:37:06 barbosa kernel: scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S. 1.00 PQ: 0 ANSI: 0 CCS
Feb 14 09:37:06 barbosa kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
Feb 14 09:37:06 barbosa kernel: kvm: disabled by bios
Feb 14 09:37:06 barbosa kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
Feb 14 09:37:10 barbosa dhcpcd[945]: all: configured as a router, not a host
Feb 14 10:00:57 barbosa kernel: thinkpad_acpi: unknown possible thermal alarm or keyboard event received
Feb 14 10:00:57 barbosa kernel: thinkpad_acpi: temperatures (Celsius): 44 0 44 0 0 0 21 0
Feb 14 10:00:57 barbosa kernel: thinkpad_acpi: unhandled HKEY event 0x6040
Feb 14 10:00:57 barbosa kernel: thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-devel@lists.sourceforge.net
Feb 14 10:01:01 barbosa kernel: thinkpad_acpi: unknown possible thermal alarm or keyboard event received
Feb 14 10:01:01 barbosa kernel: thinkpad_acpi: temperatures (Celsius): 44 0 44 0 0 0 21 0
Feb 14 10:01:01 barbosa kernel: thinkpad_acpi: unhandled HKEY event 0x6040
Feb 14 10:01:01 barbosa kernel: thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-devel@lists.sourceforge.net
Last edited by iardis (2013-02-14 21:46:50)
Offline
Just to rule out the obvious - you have rebooted since the last kernel update?
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Hehe, yes I have.
I forgot to mention that I tried to downgrade the kernel, too. Didn't solve the problem, either.
My mkinitcpio.conf: (everything but hooks empty)
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
The only thing I did between "system worked" and "usb doesn't work" is a system update which changed the following packages:
gzip (1.5-2 -> 1.5-3)
perl (5.16.2-2 -> 5.16.2-3)
openssl (1.0.1.c-1 -> 1.0.1.d-1)
curl (7.28.1-1 -> 7.29.0-1)
dhcpcd (5.6.4-1 -> 5.6.4-2)
docbook-xsl (1.77.1-2 -> 1.78.0-1)
gtk-update-icon-cache (2.24.14-1 -> 2.24.15-1)
gtk2 (2.24.14-1 -> 2.24.15-1)
flashplugin (11.2.202.261-1 -> 11.2.202.262-1)
gimp (2.8.2-1 -> 2.8.4-1)
git (1.8.1.2-1 -> 1.8.1.3-1)
gnutls (3.1.7-1 -> 3.1.8-1)
vim-runtime (7.3.754-1 -> 7.3.798-1)
ruby (1.9.3_p374-1 -> 1.9.3_p385-1)
gvim (7.3.754-1 -> 7.3.798-1)
hwids (20121203-1 -> 20130209-1)
krb5 (1.11-2 -> 1.11-3)
libdrm (2.4.41-1 -> 2.4.42-1)
lib32-libdrm (2.4.41-1 -> 2.4.42-1)
lib32-libglapi (9.0.2-1 -> 9.0.2-4)
lib32-libgl (9.0.2-1 -> 9.0.2-4)
lib32-mesa (9.0.2-1 -> 9.0.2-4)
libevent (2.0.21-1 -> 2.0.21-2)
linux (3.7.5-1 -> 3.7.6-1)
lirc-utils (1:0.9.0-36 -> 1:0.9.0-37)
openssh (6.1p1-4 -> 6.1p1-5)
poppler (0.22.0-1 -> 0.22.1-1)
poppler-glib (0.22.0-1 -> 0.22.1-1)
seabios (1.7.1-1 -> 1.7.2-1)
v4l-utils (0.8.9-1 -> 0.9.3-1)
xterm (288-1 -> 289-1)
Offline
What happens in dmesg when you connect a usb drive?
Also can you look at
dmesg | grep -i hcd
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
dmesg | grep - i hcd gives no result - this implies that the usb-driver isn't loaded at all, doesn't it?
There is no event in dmesg when I plug/unplug my usb device.
Btw. thanks a lot for the help, skanky!
Offline
Yeah, the driver's not being loaded.
I don't know if there's a way to manually try and load it? If so that would probably get you some more info.
Sorry, I'm pretty much at the limit of my knowledge now....you could try reinstalling libusb and usbutils, etc. and redoing mkinitcpio just to make sure they're all sorted.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
It seems like I've solved the problem somewhat. I've added
MODULES="ehci_hcd"
to the /etc/mkinitcpio.conf. Now usb seems to be working again. The thing is: How can this happen? Shouldn't udev take care of the needed kernel modules (especially stuff like usb drivers) ?
Btw. thanks again shanky - your hints enabled me to fix the problem.
Offline
No problem, glad I was able to help.
That's an odd one. Yes, AFAIA, udev is supposed to load it.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Really weird. I even had the keyboard hook in my HOOKS. It still failed to load the ehci_hcd module. I tried this with two different keyboards - cherry and logitech. :-( If anyone could point me to a documentation how to open a bug for Archlinux I would volunteer to do so. ;-)
Best Regards,
Robin
Offline
OK. that was easy.. https://wiki.archlinux.org/index.php/Re … Guidelines
Offline
I opened a bug and got some insights - https://bugs.archlinux.org/task/34492
It seems like mkinitcpio only registers and generates modules for devices that are connected when the generation runs. If you want to generate for devices that are not connected at that point in time you need to explicitly specify them in your MODULES section.
Offline
Until the bug is resolved, maybe you should put this in the wiki.
Offline
Pages: 1