From owner-freebsd-arm@FreeBSD.ORG Mon Feb 7 15:38:38 2011 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25219106567A for ; Mon, 7 Feb 2011 15:38:38 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from thalia-smout.broadpark.no (thalia-smout.broadpark.no [80.202.8.21]) by mx1.freebsd.org (Postfix) with ESMTP id D0C108FC08 for ; Mon, 7 Feb 2011 15:38:37 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from terra-smin.broadpark.no ([80.202.8.13]) by thalia-smout.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with ESMTP id <0LG9009IZ7GCCF80@thalia-smout.broadpark.no> for freebsd-arm@FreeBSD.org; Mon, 07 Feb 2011 16:38:36 +0100 (CET) Received: from kg-v2.kg4.no ([84.48.120.77]) by terra-smin.broadpark.no (Sun Java(tm) System Messaging Server 7u3-15.01 64bit (built Feb 12 2010)) with SMTP id <0LG90081O7GBUQ21@terra-smin.broadpark.no> for freebsd-arm@FreeBSD.org; Mon, 07 Feb 2011 16:38:35 +0100 (CET) Date: Mon, 07 Feb 2011 16:38:35 +0100 From: Torfinn Ingolfsen To: freebsd-arm@FreeBSD.org Message-id: <20110207163835.41be5884.torfinn.ingolfsen@broadpark.no> In-reply-to: <201102062331.01760.hselasky@c2i.net> References: <20110206181659.869861bf.torfinn.ingolfsen@broadpark.no> <201102061955.38635.freebsd-arm@dino.sk> <20110206231720.e113a196.torfinn.ingolfsen@broadpark.no> <201102062331.01760.hselasky@c2i.net> X-Mailer: Sylpheed 3.0.3 (GTK+ 2.22.1; amd64-portbld-freebsd8.1) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Cc: Subject: Re: FreeBSD on a DockStar - doesn't mount root X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Feb 2011 15:38:38 -0000 Hello, On Sun, 06 Feb 2011 23:31:01 +0100 Hans Petter Selasky wrote: > On Sunday 06 February 2011 23:17:20 Torfinn Ingolfsen wrote: > > On Sun, 06 Feb 2011 19:55:37 +0100 > > > > Milan Obuch wrote: > > > Did you try typing several dots to test whether some more time to mount > > > root device helps? I would try it, sometimes it helps... Just some more > > > time for background tasks (one dot means one second, It I am not > > > mistaken). > > > > I'm not really sure how it is suposed to be, I tried > > .....ufs:/dev/ufs/kirkwoodroot > > > > and that didn't have any effect. > > Maybe you need to set the scsi delay sysctl, to give the drive more time to > probe. Search the mailing lists :-) Thanks to Milan I now know how to perform the "dot trick" - thanks! :-) It seems to my mountroot prompt is a bit different, it doesn't mention '.' as a "command" for the prompt, and it says it is trying to mount from it: mountroot> ? List of GEOM managed disk devices: Loader variables: vfs.root.mountfrom= vfs.root.mountfrom.options= Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a eg. cd9660:/dev/acd0 This is equivalent to: mount -t cd9660 /dev/acd0 / ? List valid disk boot devices Abort manual input mountroot> . Trying to mount root from . Loader variables: vfs.root.mountfrom= vfs.root.mountfrom.options= Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a eg. cd9660:/dev/acd0 This is equivalent to: mount -t cd9660 /dev/acd0 / ? List valid disk boot devices Abort manual input mountroot> ? List of GEOM managed disk devices: Loader variables: vfs.root.mountfrom= vfs.root.mountfrom.options= Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a eg. cd9660:/dev/acd0 This is equivalent to: mount -t cd9660 /dev/acd0 / ? List valid disk boot devices Abort manual input mountroot> Unfortunately, it doesn't help. I have tried waiting ten minutes - still no devices to boot from. So it seems like this isn't a "delay" type problem. -- Torfinn