From: Michael West <neovorbis@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Possible bug in USB or HID on asus mobo with via kt266 a chipset
Date: Thu, 18 Apr 2002 19:10:42 -0400 [thread overview]
Message-ID: <3CBF5272.3030203@comcast.net> (raw)
I recently changed motherboards on my linux box and one of my hid
controllers (a psx-usb converter) stopped functioning correctly. I was
running a 2.4.18 kernel on both boards, and with the new asus board,
apps reading from the /dev/input/js0 file seem to halt after the first
19 joystick messages are read. I tried reproducing the problem on other
kernel versions, and experienced the same problem with a smattering of
previous kernels. I'm using a hid mouse, as well as another hid
controller, and both work correctly. Not sure if its related or not,
but I also seem to have some apparent irq problems, as newly plugged in
usb devices (any) and by that I mean after the usb-uhci or uhci driver
is loaded, throw "USB device not accepting new address - * (error =
-110)" errors. The situation in 2.4.19-pre2 changed a bit by completely
breaking the psx-converter (joydev driver assigns no device) only on
usb-uhci. pre3 has the same origional problem, as well as 4 and 5.
Pre6 and Pre7 seem to completely break all usb hid devices. The irq
(or whatever) problems go away and devices are hotplugged fine, but no
hid devices are ever registered. Sorry for my infamiliarity with the
linux kernel source and terminology. Thanks in advance.
Michael
next reply other threads:[~2002-04-18 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 23:10 Michael West [this message]
2002-04-18 23:38 ` Possible bug in USB or HID on asus mobo with via kt266 a chipset Johannes Erdfelt
2002-04-19 1:31 ` Greg KH
2002-04-19 19:25 ` Michael West
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=3CBF5272.3030203@comcast.net \
--to=neovorbis@comcast.net \
--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