From: Greg KH <greg@kroah.com>
To: "Carlos Jiménez" <lordeath@linuxspain.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: UHCI-HCD && mosedev on 2.6.0-test11
Date: Tue, 16 Dec 2003 16:55:52 -0800 [thread overview]
Message-ID: <20031217005552.GA8753@kroah.com> (raw)
In-Reply-To: <1071621227.11193.69.camel@localhost>
On Wed, Dec 17, 2003 at 01:33:48AM +0100, Carlos Jiménez wrote:
> ok thanx I'll try it, and i'll notify you
>
> Excuse my english (I am from spain, and I not practice english too much
> :)
>
> On 2.6.0-alltest (not yet probed with bk) all usb devices works good
> (usb-storage with an aiptek cam, and usbfloppy).
>
> When I plug in that mouse, usbview shows it as an unrecognized device.
What does /proc/bus/usb/devices show with the mouse plugged in? Do you
have the usb hid driver loaded?
> The device does not work at all, cat /dev/input/mice , cat
> /dev/input/mouse0 and cat /dev/usbmouse shows anything when I move the
> usbmouse, (on 2.4.2x kernel device works good, and I was wathcing ascii
> characters, when I was moving it).
>
> Then, when I removed the device, or when i try to unload uhci-hcd (while
> device is plugged) kernel show that info, and all about usb goes down. I
> cant unload, load, anything about modules, and I have to use sync before
> poweroff to power off the system whithout breakin filesystems.
Yeah, there are still some races there. Hopefully the latest -bk tree
(or test11) will fix a lot of these.
thanks,
greg k-h
next prev parent reply other threads:[~2003-12-17 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 0:55 UHCI-HCD && mosedev on 2.6.0-test11 Carlos Jiménez
2003-12-16 17:46 ` Greg KH
2003-12-17 0:33 ` Carlos Jiménez
2003-12-17 0:55 ` Greg KH [this message]
2003-12-17 10:18 ` Carlos Jiménez
2003-12-19 12:13 ` Carlos Jiménez
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=20031217005552.GA8753@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lordeath@linuxspain.net \
/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