To: James Oakley <joakley@solutioninc.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc2-mm4 + alps locks input in X
References: <20040927192744.GA8947@luna.mooo.com>
	<200409271604.33993.joakley@solutioninc.com>
From: Peter Osterlund <petero2@telia.com>
Date: 27 Sep 2004 22:25:42 +0200
In-Reply-To: <200409271604.33993.joakley@solutioninc.com>
Message-ID: <m3wtyf792x.fsf@telia.com>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1102
Lines: 20

James Oakley <joakley@solutioninc.com> writes:

> On Monday 27 September 2004 4:27 pm, Micha Feigin wrote:
> > I tried both with mm4 with the already included alps patch and with
> > bk11 and bk13 with the patch manually applied. In both cases when
> > starting X with the alps driver input is completely dead in X, both
> > mouse and keyboard, including sysrq keys and num-lock/caps-lock.
> 
> I had this problem when I accidentally used the event device for my keyboard 
> instead of the touchpad. It didn't help that every alps XF86Config example 
> out there points to event1, which is my keyboard.
> 
> cat /proc/bus/input/devices to see which event device to use.

Or better yet, use the auto-dev feature, which should work if you have
a new enough X driver and kernel patch.

-- 
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/