Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Feb 2019 20:14:49 -0700
From:      Ian Lepore <ian@freebsd.org>
To:        ticso@cicely.de
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: about netbooting on armv6 [was: Fwd: SDIO Patch D4761.diff Not Building For Me]
Message-ID:  <1797d7376b308236366305ad5ae18661b1d2a80c.camel@freebsd.org>
In-Reply-To: <20190301031213.GE23492@cicely7.cicely.de>
References:  <CABx9NuQuDVOZJt7%2B%2BK0cY%2B7oDLRkhrWmZ5WoNqFdTEMhZ0zQQQ@mail.gmail.com> <CABx9NuRXWEY%2BsBQN==q5YSaPU0f-o_pLQCpQOw1e32w=R0nPsg@mail.gmail.com> <CABx9NuSMK-X%2BvzTBH4bVsFLDFwWuF49t5JU7mzqVErDOMXGEzA@mail.gmail.com> <5432b449f37a481bc7099fbab25fbd2e@bakulin.de> <CABx9NuQKTFWUoTr2ufXANDo6C2AwLiYC7wd_5wSUg9J7M1Rofg@mail.gmail.com> <CABx9NuRTao6YhdzKPONwKgzfeAN80UmQ060QTf%2Buv18gkHogtg@mail.gmail.com> <CABx9NuSaWNX3qEwmGdpez-qf8GEjH4%2Bvd3y9tuR1ogZBDzsAng@mail.gmail.com> <a4a95b7a9617eea06212c50ec23bf5cc@bakulin.de> <CABx9NuQLbWjK8DfBLPDcRX9Bb1MY5Bk=TRDW_Fx63uP9orT2Og@mail.gmail.com> <1458751414.1091.47.camel@freebsd.org> <20190301031213.GE23492@cicely7.cicely.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2019-03-01 at 04:12 +0100, Bernd Walter wrote:
> On Wed, Mar 23, 2016 at 10:43:34AM -0600, Ian Lepore wrote:
> > 
> > The quick and easy config for netbooting armv6 these days is to set
> > a
> > few vars in your uboot env.  This assumes that you let uboot load
> > ubldr.bin from sdcard, and then have ubldr load the kernel and the
> > kernel will mount nfsroot.
> > 
> > If you have a dhcp server to provide an IP, this is all you need in
> > uboot env:
> > 
> >   loaderdev=net
> >   rootpath=<nfs server ip>:/<rootpath>
> > 
> > If you manually configure the ip, add these:
> > 
> >   ipaddr=<ip addr>
> >   netmask=255.etc.etc.etc
> 
> Ok - I'm lost with this.
> 
> I've setup a card for a Pi1-B with just the DOS partition on it.
> This is what I get:
> MMC:   mmc@7e300000: 1
> Loading Environment from FAT... In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   No ethernet found.
> starting USB...
> USB0:   scanning bus 0 for devices... 3 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0 
> MMC Device 0 not found
> no mmc device at slot 0
> switch to partitions #0, OK
> mmc1 is current device
> Scanning mmc 1:1...
> Found EFI removable media binary efi/boot/bootarm.efi
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> Scanning disk mmc@7e300000.blk...
> Found 2 disks
> FDT memrsv map 0: Failed to add to map
> 583472 bytes read in 56 ms (9.9 MiB/s)
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> FDT memrsv map 0: Failed to add to map
> ## Starting EFI application at 00080000 ...
> Consoles: EFI console  
> FreeBSD/arm EFI loader, Revision 1.1
> 
>    Command line arguments: l
>    EFI version: 2.70
>    EFI Firmware: Das U-Boot (rev 8216.2304)
>    Console: efi (0)
>    Load Path: /\efi\boot\bootarm.efi
>    Load Device: /VenHw(e61d73b9-a384-4acc-aeab-
> 82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x800,0x19000)
> Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-
> 82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x800,0x19000)
> Setting currdev to disk0p1:
> Failed to find bootable partition
> Startup error in /boot/lua/loader.lua: seconds
> LUA ERROR: cannot open /boot/lua/loader.lua: no such file or
> directory.
> 
> can't load 'kernel'
> 
> Type '?' for a list of commands, 'help' for more detailed help.
> OK  
> 
> So - ok it can't find its partition on the card.
> But how can I setup those variables?
> MMC:   mmc@7e300000: 1
> Loading Environment from FAT... In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   No ethernet found.
> starting USB...
> USB0:   scanning bus 0 for devices... 3 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0 
> U-Boot> loaderdev=net
> U-Boot> saveenv
> Saving Environment to FAT... Failed (1)
> 
> Same problem with saveenv not being functional on the original image
> as well,
> not just on mine.
> I've tried uEnv.txt, but it is just as it isn't there.
> 

All of what I said back then is valid only for ubldr.  EFI is a whole
'nother story.  I've never gotten netbooting to work with EFI.  So
mostly I just use old u-boot (from the 2015-2016 era) on all my boards.

-- Ian





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1797d7376b308236366305ad5ae18661b1d2a80c.camel>