From owner-freebsd-hardware@freebsd.org Thu Feb 15 08:13:04 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6D77F063E1; Thu, 15 Feb 2018 08:13:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 5190E6889E; Thu, 15 Feb 2018 08:13:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 2A57426009E; Thu, 15 Feb 2018 09:13:01 +0100 (CET) Subject: Re: Dell R630 unable to detect USB, can't boot To: Lee Brown , freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org References: <2dd2f1e1-dd3f-5e38-5873-81394633799b@selasky.org> <62462b68-2fb9-4e8a-c473-9c1ea9096f09@selasky.org> <78c5b059-ac39-8946-81f5-3e6ec75d6c39@selasky.org> <29e9db2f-800d-acbc-1aec-7b2170a571de@selasky.org> From: Hans Petter Selasky Message-ID: <882d40df-6082-bcca-a9ee-944aeca115a8@selasky.org> Date: Thu, 15 Feb 2018 09:10:04 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2018 08:13:04 -0000 On 02/15/18 06:24, Lee Brown wrote: > I do find it curious that the loader is able to work the USB hardware but > not the kernel. The loader is using the BIOS's USB code. Usually there is a handover from BIOS to OS, maybe that's where it's broken. --HPS