Date: Sun, 16 Mar 2014 18:33:14 -0700 From: Rui Paulo <rpaulo@FreeBSD.org> To: Patrick Kelsey <kelsey@ieee.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Booting FreeBSD from eMMC on BeagleBone Black Message-ID: <E1283934-0065-4979-92AA-99D1056BFBD5@FreeBSD.org> In-Reply-To: <CAD44qMXrKbZqXT_Z1UL2LXuVON4Gb49m-GygW_6Y14Zz-egTFw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On 16 Mar 2014, at 14:59, Patrick Kelsey <kelsey@ieee.org> wrote: > - Improved disk probing support that will now by default find and use the > first suitable partition among the available storage devices. I think this introduced a bug where, if you have a non-responsive boot device, ubldr will stop and won't try network booting: ## Starting application at 0x01000054 ... Consoles: U-Boot console Compatible API signature found @1d800a8 Number of U-Boot devices: 2 FreeBSD/armv6 U-Boot loader, Revision 1.2 (rpaulo@zedfs.local, Fri Mar 14 22:35:47 PDT 2014) DRAM: 256MB Unknown device type '' <------------ this is new Found U-Boot device: disk Probing all storage devices... Checking unit=0 slice=0 partition=-1...disk0: read failed, error=1 Checking unit=1 slice=0 partition=-1... Checking unit=2 slice=0 partition=-1... Checking unit=3 slice=0 partition=-1... Checking unit=4 slice=0 partition=-1... Checking unit=5 slice=0 partition=-1... can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. loader> It stops here and doesn't try net0 booting. -- Rui Paulohelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1283934-0065-4979-92AA-99D1056BFBD5>