USB keyboard and mouse deactivates after boot screen and before login

Syntaxeus · 2012-02-25 15:09:43

Hi guys!

After the last pacman upgrade (a couple of days ago) I'm not able to use my the USB keyboard and the Num Lock lamp is turned off together with the laser diode on my mouse, indicating that the USB connection is shut down.
The keyboard works fine in GRUB though.

I have checked dmsg and various logs in /var/log, but nothing brings me any closer to a solution.

I've also verified that I have usbinput in the HOOKS array in my mkinitcpio.conf file.

Any suggestions are very much appriciated!

Last edited by Syntaxeus (2012-02-25 15:15:18)

Gcool · 2012-02-26 09:03:27

Kernel 3.2.7-1 was released a few days ago, so could be that your issues started after upgrading to that one. Have you tried rolling back to a previous kernel version and see if this resolves the issue?

lilsirecho · 2012-02-27 01:44:35

Same problem occurs here. I have an idea it is related to the module-init-tools change to kmod which may require a mkinitcpio mod as well.

Why everyone is not affected means it is our upgrade with missing details in our use of the upgrade info.

Haven't spent time on the problem because I have a project requiring full attention.

Syntaxeus · 2012-03-04 13:11:46

I downgraded the kernel to 3.2.6-1 and mkinitcpio to 0.8.2.2, but the problem still remains.

Anyone else got an idea? This is getting really annoying.

lilsirecho · 2012-03-04 21:52:02

It may be udev and kmod that cause the problem.

Syntaxeus · 2012-03-05 18:56:47

I tried downgrade both kmod and udev, but the problem still remains.

I also notices that the Num Lock lamp (USB power) turn of as soon as the boot menu screen shows.

lilsirecho · 2012-03-06 05:45:55

Your problem may be different than mine since my USB power remains on. I am using usb keybd and mouse.

I reach Desktop in xfce4 but the keyboard and mouse(both lit) do not respond. It may be a problem with xfce4 in my case. All of the items on my Desktop are displayed but no action from the mouse or keybd.

It stopped working a few upgrades back and I have many items to check from those upgrades!

Am hoping to spend a day trying to fix this now that my project has reached a plateau.

I know it can be fixed cause it worked before an upgrade.

EDIT: I now suspect it is a USB problem caused by other usb devices connected during boot and/or other HDD devices as slaves/master.

Last edited by lilsirecho (2012-03-06 05:54:25)

lilsirecho · 2012-03-06 11:09:16

My problem responded to a workaround suggesting that it is caused by grub misconfigure.

I boot with grub 0.97 with hd0,0. If I change that to hd1,0 and use the HDD (hd1) to boot, the mouse and keybd are usable upon reaching Desktop.

Both systems are on the same kernel. The system which failed is on a compact flash device .

I will try to boot without the HDD backup using hd1,0 and see if that works.

This indicates some problem different than yours since my usb is always active.

lilsirecho · 2012-03-06 11:35:58

As expected, the CF card does not produce usable keybd nor mouse with the hd1,0 setting without the HDD backup.

Examining the error logs I find the following:

Feb 24 16:52:53 localhost kernel: [   18.470845] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.474827] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.478847] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71
Feb 24 16:52:53 localhost kernel: [   18.482827] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.486846] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.490827] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.494847] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71
Feb 24 16:52:53 localhost kernel: [   18.498827] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.502846] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.506703] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.510722] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71
Feb 24 16:52:53 localhost kernel: [   18.514702] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.518720] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.522708] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.526722] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71
Feb 24 16:52:53 localhost kernel: [   18.530702] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.534720] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.538708] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.542722] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71
Feb 24 16:52:53 localhost kernel: [   18.546702] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.550720] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.554708] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.558722] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71
Feb 24 16:52:53 localhost kernel: [   18.562702] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.566721] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.570708] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.574722] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71
Feb 24 16:52:53 localhost kernel: [   18.578702] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.582720] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.586708] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.590722] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71
Feb 24 16:52:53 localhost kernel: [   18.594702] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.598719] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.602708] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.606723] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71
Feb 24 16:52:53 localhost kernel: [   18.610702] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.614720] generic-usb 0003:06A3:8021.0002: can't reset device, 0000:00:1d.7-6.2/input0, status -71
Feb 24 16:52:53 localhost kernel: [   18.618708] usb 1-6: clear tt 1 (0040) error -71
Feb 24 16:52:53 localhost kernel: [   18.622722] generic-usb 0003:06A3:8021.0003: can't reset device, 0000:00:1d.7-6.2/input1, status -71

Thus, it may be the same problem area.......

The problem illustrated occured when the system did not work on Feb24.

lilsirecho · 2012-03-08 22:25:02

My arrangement in the CF card arch install is a two partition scheme. I have a 100mb partition for boot and the rest of a 16GB CF card for /root.

I intended to boot on the partition but the grub boot system did not permit it.

Therefore I run into the keybd and mouse problem when attempting to boot from MBR.

The solution (workaround ) that I am using allows the HDD MBR to be used to back-up the CF card system by employing (hd1,0) in the grub menu list.

I do not know if this info is helpful for your problem, Syntaxeus.

phekdra · 2012-03-09 06:17:33

I just had a similar problem this morning the first time booting using kernal 3.2.9, with the same 'can't reset device' error. I eventually managed to log in to the desktop by finding a PS2 adaptor for my keyboard and waiting several minutes as the computer chugged it's way slowly to the gdm screen. The keyboard worked, but curiously my ethernet adaptor took several attempts to persuade to make a connection.

Same problem on repeated reboots.

P

Syntaxeus · 2012-03-19 20:42:06

So I gave up on trying to fix this in my current system and when for a reinstall using the defaults when it comes to config files and packages.

But boy was I suprised (and frustrated) when I rebooted my newly installed system and the problem still remained!!

What on earth can be causing my USB devices to be deactivated during boot and is there any log I can look in to get a clue whats is causing this?

Also, the only way to access my system is through chroot.

Any type of help is very much appriciated.

schnorchelkatze · 2012-03-19 23:39:23

I got the same Problem here, but it occured two days ago.

My Keyboard works perfectly in GRUB and also when im booting into single-user-mode. Then i can use it normally but can only work in text mode. As soon as i go into graphical mode it does not work anymore and i cant even switch back.

I suspect udev or maybe something in the X configuration? I'm really just guessing...

If i get a solution in the German Forums i'll post it here as well.

BTW:
My Keyboard is an "Enermax Aurora Lite"

Lsusb says:
Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard

Maybe its something with some particular models or so?

Last edited by schnorchelkatze (2012-03-19 23:55:16)

kuri · 2012-03-20 17:22:15

schnorchelkatze wrote:

I got the same Problem here, but it occured two days ago.
My Keyboard works perfectly in GRUB and also when im booting into single-user-mode. Then i can use it normally but can only work in text mode. As soon as i go into graphical mode it does not work anymore and i cant even switch back.
I suspect udev or maybe something in the X configuration? I'm really just guessing...
If i get a solution in the German Forums i'll post it here as well.
BTW:
My Keyboard is an "Enermax Aurora Lite"
Lsusb says:
Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard
Maybe its something with some particular models or so?

Hello, i have the exact same keyboard with the exact same problem!
If i plug another keyboard, it works.

i have no idea what the problem is

schnorchelkatze · 2012-04-02 22:11:15

To "revive" this thread: Keyboard is still NOT working.

I tried to delete the xorg.conf and without it everything worked fine but not the keyboard.

Also i tried to change the

etc/X11/xorg.conf.d/10-evdev.conf

and set the Driver to "kbd" instead of "evdev" but that totally went wrong and i was not able to login since my keyboard wrote something like "777#°213" when i just hit one letter on it...

Since i already got a message if was able to fix the issue i'd really appreciate some help here.

What i know so far:

- Keyboard is "Enermax Aurora Lite"
- Keyboard works fine when in CLI, as soon as X starts the LEDs do not glow and the keyboard does not work

- Maybe only USB-Keyboards won't work. Since this is the only one i have with usb i cant tell but my alternative keyboards all have PS/2 and work normally.
- Maybe its a problem with some drivers / option in X since it works normally in CLI
- Maybe it's a problem with the model "Enermax Aurora (Lite)"

Any suggestions i might try or anything that could help? logs?

kuri · 2012-04-12 03:27:37

My other keyboard uses USB and works just fine while my aurora lite doesnt.

sigman · 2012-04-15 20:46:19

guys, the problem is caused by "udev" post 2012

220700 Nov 8 08:57 udev-175-1-i686.pkg.tar.xz <=== pre-year 2012 = OK
218008 Jan 21 13:00 udev-178-1-i686.pkg.tar.xz
218068 Jan 25 02:31 udev-179-1-i686.pkg.tar.xz
218112 Jan 29 13:32 udev-180-1-i686.pkg.tar.xz
217796 Feb 8 16:59 udev-181-2-i686.pkg.tar.xz
218100 Mar 15 04:33 udev-181-5-i686.pkg.tar.xz

please file a bug report under udev.
this is due to change on the way udev loads necessary hooks during boot time.

by downgrading udev to 175-1, you have to downgrade initscripts to "initscripts 2011.11.3-1"
as well.

UPDATE: unfortunately, you have to stay with "pacman 4.0.2-1", as of today the latest pacman
requires the latest udev version

Last edited by sigman (2012-04-15 20:49:19)

kuri · 2012-04-17 18:39:30

Hello sigman.

All this sucks. But still i dont understand why it doesnt work, as udev sees my keyboard, when i unplug/plug it : http://pastebin.archlinux.fr/438910

sigman · 2012-04-18 17:16:49

yeah all udev post 2012 versions work once booted, take note the problem is on the way "udev hooks" are generated during "mkinitcpio ..."
so it has something to do with init during *BOOT time only*, once booted udev behaves the way it is supposed to behave
detecting devices, so by unplugging-and-plugging your usb keyboard/mouse it is expected to work.

hence if you downgraded your udev pre 2012, you have to regenerate your init by
# mkinitcpio -p your-kernel-version-here
then reboot is required.

kuri wrote:

Hello sigman.
All this sucks. But still i dont understand why it doesnt work, as udev sees my keyboard, when i unplug/plug it : http://pastebin.archlinux.fr/438910

tjbp · 2012-04-26 00:54:42

I've also had this problem for months. Every USB device I have plugged in on boot has to be unplugged and plugged in again before they work (external hard drive, mouse, keyboard). I also noticed that Arch fails to stop udev when shutting down, but I don't know how that could be related.

I'm assuming this doesn't affect everyone or we'd have a fix - possibly a broken upgrade? Has anyone posted a bug or should I?

Arch Linux

#1 2012-02-25 15:09:43

USB keyboard and mouse deactivates after boot screen and before login

#2 2012-02-26 09:03:27

Re: USB keyboard and mouse deactivates after boot screen and before login

#3 2012-02-27 01:44:35

Re: USB keyboard and mouse deactivates after boot screen and before login

#4 2012-03-04 13:11:46

Re: USB keyboard and mouse deactivates after boot screen and before login

#5 2012-03-04 21:52:02

Re: USB keyboard and mouse deactivates after boot screen and before login

#6 2012-03-05 18:56:47

Re: USB keyboard and mouse deactivates after boot screen and before login

#7 2012-03-06 05:45:55

Re: USB keyboard and mouse deactivates after boot screen and before login

#8 2012-03-06 11:09:16

Re: USB keyboard and mouse deactivates after boot screen and before login

#9 2012-03-06 11:35:58

Re: USB keyboard and mouse deactivates after boot screen and before login

#10 2012-03-08 22:25:02

Re: USB keyboard and mouse deactivates after boot screen and before login

#11 2012-03-09 06:17:33

Re: USB keyboard and mouse deactivates after boot screen and before login

#12 2012-03-19 20:42:06

Re: USB keyboard and mouse deactivates after boot screen and before login

#13 2012-03-19 23:39:23

Re: USB keyboard and mouse deactivates after boot screen and before login

#14 2012-03-20 17:22:15

Re: USB keyboard and mouse deactivates after boot screen and before login

#15 2012-04-02 22:11:15

Re: USB keyboard and mouse deactivates after boot screen and before login

#16 2012-04-12 03:27:37

Re: USB keyboard and mouse deactivates after boot screen and before login

#17 2012-04-15 20:46:19

Re: USB keyboard and mouse deactivates after boot screen and before login

#18 2012-04-17 18:39:30

Re: USB keyboard and mouse deactivates after boot screen and before login

#19 2012-04-18 17:16:49

Re: USB keyboard and mouse deactivates after boot screen and before login

#20 2012-04-26 00:54:42

Re: USB keyboard and mouse deactivates after boot screen and before login

Board footer