Date: Thu, 2 Jul 2015 16:32:10 +0200 From: Hellmuth Michaelis <hm@hellmuth-michaelis.de> To: Andrew Gervase <andy.gervase@me.com> Cc: Glen Barber <gjb@FreeBSD.org>, freebsd-arm@freebsd.org Subject: Re: Once Booted from MMC, eMMC not found Message-ID: <6C705C95-D95D-4207-B23A-01CD0E583426@hellmuth-michaelis.de> In-Reply-To: <462071B7-1D51-45CC-B69C-E59EA36DA729@me.com> References: <1435812471361-6022231.post@n5.nabble.com> <20150702050306.GD45214@FreeBSD.org> <20150702050634.GE45214@FreeBSD.org> <462071B7-1D51-45CC-B69C-E59EA36DA729@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
it seems booting from eMMC is currently not possible, for a discussion = of possible causes have a look at the thread = https://lists.freebsd.org/pipermail/freebsd-arm/2015-March/010598.html hellmuth > Am 02.07.2015 um 13:35 schrieb Andrew Gervase <andy.gervase@me.com>: >=20 > Thank you for your reply, Glen: To me, the script is optional. All = it does is partition and newfs a slice on mmc1, and then copies = everything via tar from mmc0 to mmc1. =20 >=20 > My problem is, mmc1 doesn=E2=80=99t exist once the kernel loads. I = was wondering if there is a module that needs to be loaded or compiled = into the kernel to make sure the eMMC (mmc1) is recognized. =20 >=20 > Andy ideas? >=20 > =E2=80=94Andy >=20 >> On Jul 2, 2015, at 01:06, Glen Barber <gjb@FreeBSD.org> wrote: >>=20 >> On Thu, Jul 02, 2015 at 05:03:06AM +0000, Glen Barber wrote: >>> On Wed, Jul 01, 2015 at 09:47:51PM -0700, agervase wrote: >>>> I was finally able to get my Beaglebone Black to boot from FreeBSD >>>> 10.1-RELEASE, however the copy-to-emmc.sh script fails because mmc1 = is not >>>> found. I'd very much like my BBB to boot automatically, preferably = from the >>>> eMMC, however I'll take what I can! >>>>=20 >>>> Please forgive me in advance if this question has already been = addressed, as >>>> my searches have yielded nothing helpful thus far. >>>>=20 >>>> My greatest appreciation in advance, >>>=20 >>> Please wait until next week when several changes/fixes are committed = to >>> the stable/10 branch that can help with this. >>>=20 >>> Unless you do not have a particular reason to run 10-STABLE, you can = try >>> the 11-CURRENT snapshots. See the mailing list archives for >>> freebsd-snapshots@ for details. >>>=20 >>=20 >> Bah, actually I think what I suggested is orthogonal to your issue, >> since I just realized you mentioned a script I am unaware of. >>=20 >> Sorry for any confusion. >>=20 >> Glen >>=20 >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6C705C95-D95D-4207-B23A-01CD0E583426>