From: Take Vos <Take.Vos@binary-magic.com>
To: Brad Hards <bhards@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: USB mouse does not apear in /dev/input
Date: Tue, 22 Oct 2002 13:28:35 +0200 [thread overview]
Message-ID: <200210221328.43413.Take.Vos@binary-magic.com> (raw)
In-Reply-To: <200210222121.04718.bhards@bigpond.net.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Brad
Sorry I think I forgot to press the "reply to all" button :-)
> On Tue, 22 Oct 2002 21:11, Take Vos wrote:
> > On Tuesday 22 October 2002 12:03, you wrote:
> > > On Tue, 22 Oct 2002 19:48, Take Vos wrote:
> > > > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
> > > > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> > > > P: Vendor=046d ProdID=c00c Rev= 6.20
> > > > S: Manufacturer=Logitech
> > > > S: Product=USB Mouse
> > > > C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
> > > > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=(none)
> > > > E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=10ms
> > > So it looks like you don't have a driver for the mouse loaded (should
> > > be hid).
> > Yes, I compared it with the 2.4.19 output, which has the Driver=hid
> > thing. I have enabled the HID (full HID) and HID input layer in the
> > kernel
> Looks OK.
> > > Can you check this in driverfs? (You used to be able to do this in
> > > /proc/bus/usb/drivers, but the maintainer knew better :-{)
> > /devices/bus/usb/drivers
> > total 0
> > drwxr-xr-x 2 root root 0 Oct 22 12:43 generic
> > drwxr-xr-x 2 root root 0 Oct 22 12:43 hid
> > drwxr-xr-x 2 root root 0 Oct 22 12:43 hub
> > drwxr-xr-x 2 root root 0 Oct 22 12:43 usb-storage
> > drwxr-xr-x 2 root root 0 Oct 22 12:43 usbfs
> > drwxr-xr-x 2 root root 0 Oct 22 12:43 usblp
> > drwxr-xr-x 2 root root 0 Oct 22 12:43 usbscanner
> >
> > The hid directory is empty, but so are the other, I don't know how
> > driverfs works yet.
> That is OK.
> > > Also, there is a problem with 2.5.43, in that the core driver model
> > > stuff got screwed up. That caused problem if you turned on the usb test
> > > framework driver, and some other issues. Here is a simple patch that
> > > David Brownell did:
> > Well, I have had USB testing driver off.
> May turn up other problems too. Did you try the patch?
Not yet, is it in the 2.5.44 sources, because I am now trying to install that.
Take
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9tTZmMMlizP1UqoURAqDiAJ9McfNNZWBE/UmZdzgnXxhfQYliwACfevCf
t802qfMW0XGc5JytDmrh3TM=
=pY6z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-10-22 11:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 8:46 Take Vos
2002-10-22 9:09 ` Brad Hards
2002-10-22 9:48 ` Take Vos
2002-10-22 10:03 ` Brad Hards
2002-10-22 16:47 ` Greg KH
2002-10-22 9:34 ` PROBLEM: PCMCIA cardmgr kill hangs kernel bert hubert
2002-10-22 9:51 ` Take Vos
2002-10-22 11:13 ` Take Vos
2002-10-22 12:15 ` Alan Cox
2002-10-22 12:20 ` Take Vos
[not found] ` <200210221311.19468.Take.Vos@binary-magic.com>
[not found] ` <200210222121.04718.bhards@bigpond.net.au>
2002-10-22 11:28 ` Take Vos [this message]
2002-10-22 12:23 ` PROBLEM: USB mouse does not apear in /dev/input (solved) Take Vos
2002-10-22 23:46 ` PROBLEM: PS/2 mouse wart does not work, while scratch pad does David Woodhouse
2002-10-23 8:42 ` Vojtech Pavlik
2002-11-09 21:50 ` Take Vos
2002-12-12 19:30 ` Take Vos
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=200210221328.43413.Take.Vos@binary-magic.com \
--to=take.vos@binary-magic.com \
--cc=bhards@bigpond.net.au \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome