From owner-freebsd-questions@FreeBSD.ORG Mon Jul 17 20:48:19 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E34F416A4DF for ; Mon, 17 Jul 2006 20:48:18 +0000 (UTC) (envelope-from richd@RichDPhoto.com) Received: from ceres.aros.net (ceres.aros.net [66.219.192.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C5CA43D81 for ; Mon, 17 Jul 2006 20:48:18 +0000 (GMT) (envelope-from richd@RichDPhoto.com) Received: from [192.168.1.101] (c-24-63-252-34.hsd1.nh.comcast.net [24.63.252.34]) (authenticated bits=0) by ceres.aros.net (8.13.3/8.13.3) with ESMTP id k6HKmEPe096283; Mon, 17 Jul 2006 14:48:15 -0600 (MDT) (envelope-from richd@RichDPhoto.com) Message-ID: <44BBF78A.3030107@RichDPhoto.com> Date: Mon, 17 Jul 2006 16:48:10 -0400 From: Rich Demanowski User-Agent: Thunderbird 1.5 (X11/20060714) MIME-Version: 1.0 To: Micah References: <44BA216E.3020701@RichDPhoto.com> <44BA73FA.2090504@ywave.com> <44BB6CC6.8090507@RichDPhoto.com> <44BBE9C8.204@ywave.com> In-Reply-To: <44BBE9C8.204@ywave.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on ceres.aros.net X-Virus-Status: Clean Cc: freebsd-questions@freebsd.org Subject: Re: USB and 6.1-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2006 20:48:19 -0000 Micah wrote: > Rich Demanowski wrote: >> Micah wrote: >>> Rich Demanowski wrote: >>>> scbus, da, pass, ohci, uhci, ehci, usb, udbp, ugen, uhid, ukbd, >>>> ulpt, umass, ums, ural, urio and uscanner are all enabled in the >>>> running kernel's /usr/src/sys/i386/conf config file. usbd is not >>>> running. When I try to start usbd I get the following: >>>> No USB host controllers found. >>>> >>>> There are no usb* devices listed in /dev. >>>> >>>> in dmesg I get the following with regard to ohci0 and ehci0: >>>> ohci0: mem 0xfe02f000-0xfe02ffff >>>> at device 11.0 on pci0 >>>> pcib0: unable to route slot 11 INTA >>>> ohci0: Could not allocate irq >>>> device_attach: ohci0 attach returned 6 >>>> ehci0: mem >>>> 0xfe02e000-0xfe02e0ff at device 1 1.1 on pci0 >>>> pcib0: unable to route slot 11 INTB >>>> ehci0: Could not allocate irq >>>> device_attach: ehci0 attach returned 6 >>>> >>>> >>>> When I plug the drive into any of the USB ports on the system, >>>> nothing happens in dmesg or /var/log/messages. camcontrol devlist >>>> lists no devices. >>>> >>>> I'm a bit confused as to why my USB keyboard and mouse function, >>>> but my thumb drive will not. >>> >>> It's likely that your BIOS has "legacy" support enabled in which >>> case, as far as FreeBSD is concerned, you actually have a regular >>> keyboard and mouse. That would explain why the mouse and keyboard >>> work while other USB items do not. From the messages you gave, it's >>> clear that FreeBSB is unable to connect to the USB controller. >>> Disabling legacy support in the BIOS may help. Otherwise check your >>> BIOS for other USB related settings and try changing those. >>> >> Indeed, legacy support is enabled (actually "auto" was the setting in >> the BIOS). When I disable it, the keyboard and mouse cease >> functioning, as well. That was the only setting I could find in the >> BIOS related to USB. >> >> I suppose that means the on-board USB controller is one not supported >> by existing drivers? Or at least ones not listed in the GENERIC >> config on which I based my kernel (all I added was the ath drivers >> for my wireless)? I don't know which chipset it is, but my guess is, >> since the on-board video and LAN is an nVidia chipset, that the USB >> controller probably is, as well. > > Based on the error messages I think it's still worth trying some > different settings. FeeeBSD seems to recognize the controller but it > is unable to allocate the right resources to it. Check your BIOS for a > "PnP OS" setting and toggle it. Also, try booting with ACPI disabled > (or enabled) from the FreeBSD boot menu. IIRC, ACPI can have a hand in > routing resources. > > HTH, > Micah ACPI is turned off. The install disc wouldn't even boot at all with it turned on. I'll try the Plug-and-play OS setting. It's currently "on".