From owner-freebsd-current@FreeBSD.ORG Mon Oct 24 03:43:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 652F816A41F for ; Mon, 24 Oct 2005 03:43:32 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-157-21-180.jan.bellsouth.net [70.157.21.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED83D43D45 for ; Mon, 24 Oct 2005 03:43:31 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: by mortis.over-yonder.net (Postfix, from userid 100) id D4F7320F56; Sun, 23 Oct 2005 22:43:29 -0500 (CDT) Date: Sun, 23 Oct 2005 22:43:29 -0500 From: "Matthew D. Fuller" To: freebsd-current@freebsd.org Message-ID: <20051024034329.GV66908@over-yonder.net> References: <20051023044115.7050216A421@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051023044115.7050216A421@hub.freebsd.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Subject: Re: The case of the missing USB controllers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 24 Oct 2005 03:43:32 -0000 On Sun, Oct 23, 2005 at 04:41:15AM +0000 I heard the voice of Bill Paul, and lo! it spake thus: > > The machine has several USB controllers and FreeBSD likes them just > fine -- _when_ it actually manages to detect and attach the > controllers correctly. Unfortunately, it very often doesn't. Interestingly enough, I have a machine that also doesn't get along with its USB, but my situation is completely different. Mine seems to be interrupt routing issues. And not even the fun ACPI-related interrupt routing issues that everyone else seems to enjoy... This is an Intel PR440FX board (dual PPro). It's got onboard USB, and I've got a mouse plugged into it, which I'd really like to use: uhci0: port 0xff80-0xff9f irq 9 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered [...] ums0: Kensington Kensington USB/PS2 Wheel Mouse, rev 1.10/1.00, addr 2, iclass 3 /1 ums0: 3 buttons and Z dir. The downside is that it doesn't work. The mouse detects just fine there (as long as it's plugged in on boot; hotplug fails totally), but the USB controller never takes a single interrupt, so of course the mouse just sits there looking pretty. I only ever used the USB once, to test a USB keyboard a couple years back, and it worked all right then. I thought it might be a problem with that USB controller anyway, so I bought an Adaptec USB2 card. But that doesn't even probe or power up or anything. My only hint at that from dmesg is: pcib0: unable to route slot 7 INTD , so presumably it just won't talk to that PCI slot at all. I know it used to, because I had a NIC in that slot that I used years ago. I know it would still probe the NIC in that slot up until I took it out of the kernel config (de0; I took it out when mpsafenet became the default since it wasn't mpsafe). I messed around with PnP settings in the BIOS, but to no avail. And that's my only available slot... Unfortunately, this is my workstation, so I can't really spend a lot of time sitting around rebooting it either :| -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.