From: "\"Andrey Borzenkov\" " <arvidjaar@mail.ru>
To: "\"Shawn Willden\" " <shawn-lkml@willden.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /dev/input/mice doesn't work in test9?
Date: Fri, 31 Oct 2003 11:03:43 +0300 [thread overview]
Message-ID: <E1AFUFz-0008jt-00.arvidjaar-mail-ru@f20.mail.ru> (raw)
> I'm sure I'm just missing something stupid, but google doesn't seem to turn
> up anything, so...
> I'm trying to use 2.6.0-test9 on a machine with a USB mouse. With 2.4, I
> have X configured to use /dev/input/mice (c 13 63) as my mouse pointer,
> and it works great. With test9, XFree86 fails to start because it can't
> open the mouse. The error is "xf86OpenSerial: Cannot open device /dev/
> input/mice No such device.".
> 'cat /dev/input/mice' also gives me "No such device".
> /dev/input/mouse0 (c 13 32) doesn't work either.
> I believe all of the relevant modules are loaded and the light on my
> optical mouse is lit, indicating that it has been powered by the usbmouse
> driver (as I understand it).
You are missing mousedev that is the driver that actually provides
/dev/input/mice. usbmouse (which is actually redundand with hid) speaks
with hardware and mousedev speaks with user :)
The whole input subsystem has changed between 2.4 and 2.6. Unfortunately,
input sysbsystem hotplugging is not currently implemented. Your best bet
is to forcibly load mousedev during boot. Alternatively look into hotplug
for usermap, it allows provide fake mapping for modules - you could add
mapping from UDB IDs of oyur mouse to mousedev. Loading it statically is
likely to be more simple.
regards
-andrey
next reply other threads:[~2003-10-31 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 8:03 "Andrey Borzenkov" [this message]
2003-10-31 14:27 ` /dev/input/mice doesn't work in test9? Shawn Willden
2003-11-01 20:56 ` DervishD
2003-11-02 10:12 ` Andrey Borzenkov
2003-11-02 12:08 ` DervishD
2003-11-02 17:45 ` Andrey Borzenkov
2003-11-02 20:37 ` DervishD
-- strict thread matches above, loose matches on Subject: below --
2003-10-30 18:32 Shawn Willden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1AFUFz-0008jt-00.arvidjaar-mail-ru@f20.mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn-lkml@willden.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).