From owner-freebsd-current@FreeBSD.ORG Sun Aug 22 17:13:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C06116A4CE for ; Sun, 22 Aug 2004 17:13:36 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D31BB43D41 for ; Sun, 22 Aug 2004 17:13:35 +0000 (GMT) (envelope-from apeiron@comcast.net) Received: from prophecy.velum (pcp08490587pcs.levtwn01.pa.comcast.net[68.83.169.224]) by comcast.net (rwcrmhc11) with SMTP id <2004082217133501300r7nhge> (Authid: apeiron@comcast.net); Sun, 22 Aug 2004 17:13:35 +0000 Date: Sun, 22 Aug 2004 13:13:32 -0400 From: Christopher Nehren To: FreeBSD CURRENT List Message-ID: <20040822171332.GA717@prophecy.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline X-Please-CC-Me: In List And Group Replies User-Agent: Mutt/1.5.6i Subject: uhid recently broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Aug 2004 17:13:36 -0000 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've been tracking -CURRENT for a few weeks now, and I noticed that sometime after RELENG_5 was branched that my Gravis USB joystick (which uses uhid(4)) was no longer being detected at boot, or at all.=20 FreeBSD 6.0-CURRENT #0: Thu Aug 19 15:48:13 EDT 2004 root@prophecy.dyndns.org:/usr/obj/usr/src/sys/PROPHECY This kernel doesn't detect uhid0. FreeBSD 5.2-CURRENT #0: Sun Aug 15 20:18:31 EDT 2004 root@prophecy.dyndns.org:/usr/obj/usr/src/sys/PROPHECY This one does. Here's the relevant lines from dmesg on the working kernel: ohci1: mem 0xcffff000-0xcfffffff irq 11 at device 1.3 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered uhid0: Gravis GamePad Pro USB, rev 1.00/2.00, addr 2, iclass 3/0 I'm fairly certain that it's not a problem with USB overall because my USB= =20 mouse functions as it always has. If I can provide any more information, I'= d be=20 delighted to do so. I've checked UPDATING and both sys/conf/NOTES and=20 sys/i386/conf/NOTES and none of the above mention anything specifically abo= ut=20 uhid. There's also been no uhid-specific commits for a while, and nothing t= o=20 USB overall which seems to be the culprit. Am I missing something obvious? --=20 I abhor a system designed for the "user", if that word is a coded pejorative meaning "stupid and unsophisticated". -- Ken Thompson - Unix is user friendly. However, it isn't idiot friendly. --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBKNQ8k/lo7zvzJioRAul0AJ4vETbLiuJTr5bpxX5JZ37eg485qwCeJ8S9 egLiBppvXVbDIehXcgv8Sm0= =UOx0 -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd--