From owner-freebsd-usb@FreeBSD.ORG Tue Nov 4 16:45:30 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFFFCF65 for ; Tue, 4 Nov 2014 16:45:30 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B2A0CC9A for ; Tue, 4 Nov 2014 16:45:30 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 8EBF31FE022; Tue, 4 Nov 2014 17:45:28 +0100 (CET) Message-ID: <545902B4.8030001@selasky.org> Date: Tue, 04 Nov 2014 17:45:40 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Steven Hartland , "freebsd-usb@freebsd.org" Subject: Re: ehci breaking Supermicro IPMI keyboard on uhci? References: <5458184E.5020801@multiplay.co.uk> <54587E9B.50709@selasky.org> <54590195.7090600@multiplay.co.uk> In-Reply-To: <54590195.7090600@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 16:45:31 -0000 On 11/04/14 17:40, Steven Hartland wrote: > On 04/11/2014 07:22, Hans Petter Selasky wrote: >> On 11/04/14 01:05, Steven Hartland wrote: >>> Had the problem where the Supermicro IPMI keyboard wouldn't work on some >>> machines for a while, tonight I finally had time to play with all the >>> options to see if anything would make it work. >>> >>> Turns out adding the following to loader.conf does fixes the issue: >>> hint.ehci.0.disabled="1" >>> >>> So the question is why would this help? >>> >>> Surely disabling one controller shouldn't make devices attached to >>> another work? >>> >> >> Hi, >> >> The USB device is failing to enumerate. Are you sure there is no XHCI >> controller on this device? > I did try removing xhci from my kernel config, but that had no effect, > only when I disabled the ehci controller did it correctly enumerate the > devices attached to the uhci controller. > > Attached is the outuput from pciconf -l -v in case that helps. If > there's anything else I can provide which will help just let me know. > > For reference I'm currently testing 10.1-RC4 on this box. > > Regards > Steve Maybe you can check the PCI IDs with Linux EHCI driver, if your hardware requires some special quirks? --HPS