From owner-freebsd-current@FreeBSD.ORG Tue Mar 24 07:42:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D88FA1065673 for ; Tue, 24 Mar 2009 07:42:49 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3068FC13 for ; Tue, 24 Mar 2009 07:42:48 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=j+k/Ze5hWUCaCztCgEjzDQ==:17 a=hzHASVDcAAAA:8 a=6I5d2MoRAAAA:8 a=Q8RHAWkl7CDnB8CKw8AA:9 a=Tfq0xeAGEqcHpN8_5kWXXS_WxgMA:4 a=LY0hPdMaydYA:10 a=vXa-fTo6yJYA:10 a=SV7veod9ZcQA:10 Received: from [81.191.55.181] (account mc467741@c2i.net HELO laptop) by mailfe08.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1213061847; Tue, 24 Mar 2009 08:42:47 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Tue, 24 Mar 2009 08:45:18 +0100 User-Agent: KMail/1.9.7 References: <200903231541.n2NFfP6f002755@monk.cnd.dundas.on.ca> <800e97aebad7e157c6b31466447501f7.squirrel@cygnus.homeunix.com> <3a142e750903240032s3e3dbb72pd12e984886fef908@mail.gmail.com> In-Reply-To: <3a142e750903240032s3e3dbb72pd12e984886fef908@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903240845.18610.hselasky@c2i.net> Cc: Nenhum_de_Nos Subject: Re: Booting from usb hard disk 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: Tue, 24 Mar 2009 07:42:50 -0000 On Tuesday 24 March 2009, Paul B. Mahol wrote: > On 3/24/09, Nenhum_de_Nos wrote: > > On Mon, March 23, 2009 20:46, Paul B. Mahol wrote: > >> On 3/23/09, Robert Noland wrote: > >>> On Mon, 2009-03-23 at 11:41 -0400, Douglas Berry wrote: > >>>> On Mon, 23 Mar 2009 05:36:15 CDT, Robert Noland wrote: > >>>> > So I have my i386 install on a usb hard disk, which I can only boot > >>>> > on one machine now. The one machine that I can make work has a bios > >>>> > option that reads "BIOS ehci handoff". This used to work with the > >>>> > old usb stack. The machines that it doesn't work on, boot the > >>>> > kernel, but fail to mount root, giving me the forbidding mountroot> > >>>> > prompt, which is immediately followed by the message saying that da0 > >>>> > is attached. da0 is however not listed in the available boot > >>>> > devices list. I tried playing around with the timeout in > >>>> > vfs_mount.c, but that didn't seem to have any impact. It has been > >>>> > suggested that this may be a "geom" timeout, but I don't know > >>>> > anything about the boot system really. > >>>> > >>>> I have been using tunefs(8) labeled partitions on my usb hard disk > >>>> under CURRENT. I changed the fstab entries to match the labels > >>>> (eg. assume mylabel is myroot, /dev/da0s1a becomes /dev/ufs/myroot) > >>>> It works well on most systems. On some systems, I see the symptom > >>>> you show, but I am saved by the labels showing up just after the > >>>> mountroot prompt. I am then able to type > >>>> > >>>> ufs:/dev/ufs/myroot > >>>> > >>>> and resume the boot. Maybe this helps you? > >>> > >>> Well, I haven't tried labeling the partitions, but ufs:/dev/da0s1a > >>> doesn't work from the rootmount> prompt. Even after da0 shows up. > >> > >> That is strange, I just recently have used one of usb sticks (256MB) to > >> fix > >> stupid sysinstall error. In my case da0 appeared after some delay but > >> usual da0s1a appeared after ? and I was able to mount root > >> partition multiple times. > >> I used usb via modules, on i386 revision r190297, with "boot -s" > >> (I hacked fbsd installation on stick because I didnt have time for fine > >> details ....) > >> > >> Could try just with uhci (but it will be too sloow) > > > > how can I make it use this module and not another ? (how to force) > > I doubt it will help but anyway ... > > Just ensure that you are using custom kernel without any of usb, ehci, > uhci, etc lines. And forcing uhci is simple, just dont kldload ehci > (or dont "load echi" from boot loader prompt) and load any other usb > modules you need. There is also a new sysctl to do this runtime: sysctl hw.usb2.ehci.no_hs=1 --HPS