You are not logged in.

#1 2011-10-26 11:50:24

sakisds
Member
From: Athens, Greece
Registered: 2011-10-03
Posts: 105

Udev gives errors about evdev at boot, no input

After the last udev update(174-1), I can no longer boot with my mouse plugged in. At boot, udev starts complaining about evdev like this:

Oct 24 20:04:17 localhost kernel: [   80.042194] evdev: no more free evdev devices
Oct 24 20:04:17 localhost kernel: [   80.092512] input: failed to attach handler evdev to device input1, error: -23

This continues until 'input1' is something around 'input3000' and then the rest of the boot process starts. At the end I get no X and no input at all (neither mouse nor keyboard).

However, if I unplug my mouse I can boot correctly and it works if plugged while in X. Downgrading the package fixes the problem too.

Any solutions? Thanks in advance.

Edit: This is not exactly working after all, If I just do the mouse tweak an 'udevd' uses around 30% of my CPU all the time, so the only real workaround for now is downgrading.

Last edited by sakisds (2011-10-26 15:48:53)

Offline

#2 2011-11-12 14:34:37

FrozenFox
Member
From: College Station, TX
Registered: 2008-03-23
Posts: 422
Website

Re: Udev gives errors about evdev at boot, no input

As this is the top google result for many arch-related queries of this bug, and this thread isn't *too* old, I figure I should respond to it. The issue seems to be fixed for me by udev 175-1. Perhaps you should try, sakisds.

Offline

#3 2011-11-13 01:54:13

tomegun
Developer
From: France
Registered: 2010-05-28
Posts: 661

Re: Udev gives errors about evdev at boot, no input

You are more likely to get a proper response / fix if you open a bug report (as this is clearly a bug). The only thing I'd suggest you do first though is to check if you can reproduce after you have
1) updated to the latest udev version
2) recreated your initramfs (mkinitcpio -p linux)
3) removed any custom udev rules (from /etc/udev/rules.d/)
4) uninstalled any unsupported packages that install udev rules
[5) if you don't want to do 3+4, then at least check that you don't have any rules in /etc/udev/rules.d/* or /lib/udev/rules.d/* that use the deprecated keys ID, SYSFS or BUS]

Offline

Board footer

Powered by FluxBB