Date: Wed, 28 Oct 2009 09:54:54 -0700 (PDT) From: RuiDC <ruidc@yahoo.com> To: freebsd-arm@freebsd.org Subject: Re: Can't boot Marvel Sheevaplug from USB Message-ID: <26098220.post@talk.nabble.com> In-Reply-To: <62E4AC76-198B-4C74-8318-E3399B4B35C7@gmail.com> References: <62E4AC76-198B-4C74-8318-E3399B4B35C7@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack Avenger wrote: > > See link: http://www.freebsd.org/cgi/query-pr.cgi?pr=138798 > I get the same problem as you, although the problem report you link to seems to show the device being detected after attempted root mount, which is different to your log and mine. I'm running 8-RC1 <code> usbus0: 480Mbps High Speed USB v2.0 Root mount waiting for: usbus0 ugen0.1: <Marvell> at usbus0 uhub0: <Marvell EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0 uhub0: 1 port with 1 removable, self powered Root mount waiting for: usbus0 ugen0.2: <TDKMedia> at usbus0 umass0: <TDKMedia Trans-It Drive, class 0/0, rev 2.00/1.10, addr 2> on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x0000 Root mount waiting for: usbus0 umass0:0:0:-1: Attached to scbus0 Trying to mount root from ufs:/dev/da0s2a ROOT MOUNT ERROR: If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove invalid mount options from /etc/fstab. Loader variables: vfs.root.mountfrom= vfs.root.mountfrom.options= Manual root filesystem specification: <fstype>:<device> Mount <device> using filesystem <fstype> eg. ufs:/dev/da0s1a eg. cd9660:/dev/acd0 This is equivalent to: mount -t cd9660 /dev/acd0 / ? List valid disk boot devices <empty line> Abort manual input mountroot> </code> -- View this message in context: http://www.nabble.com/Re%3A-Can%27t-boot-Marvel-Sheevaplug-from-USB-tp25977274p26098220.html Sent from the freebsd-arm mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26098220.post>