From: Sascha Hauer <s.hauer@pengutronix.de>
To: Vivien Didelot <vivien.didelot@gmail.com>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>, barebox@lists.infradead.org
Subject: Re: [PATCH] defaultenv-2: trigger DHCP before booting 'net'
Date: Mon, 21 Jan 2019 09:35:55 +0100 [thread overview]
Message-ID: <20190121083555.mmsrjpw5at4kv7y2@pengutronix.de> (raw)
In-Reply-To: <20190119005018.31502-1-vivien.didelot@gmail.com>
On Fri, Jan 18, 2019 at 07:50:18PM -0500, Vivien Didelot wrote:
> Some variables may be set from DHCP requests, as shown below:
>
> barebox@ZII VF610 Development Board, Rev C:/ echo $global.hostname
> dev-rev-c
> barebox@ZII VF610 Development Board, Rev C:/ echo $global.net.server
> 0.0.0.0
> barebox@ZII VF610 Development Board, Rev C:/ dhcp
> eth0: 100Mbps full duplex link detected
> T T T eth0: DHCP client bound to address 192.168.203.31
> barebox@ZII VF610 Development Board, Rev C:/ echo $global.hostname
> zii-dev-rev-c-1
> barebox@ZII VF610 Development Board, Rev C:/ echo $global.net.server
> 192.168.203.1
> barebox@ZII VF610 Development Board, Rev C:/
>
> These variables are used by the boot/net script, so it is necessary
> to trigger DHCP before we set the TFTP file paths, otherwise booting
> from net will fail like below and will need to be triggered twice:
>
> running /env/bin/init...
>
> Hit m for menu or any key to stop autoboot: 1
> booting 'net'
> eth0: 100Mbps full duplex link detected
> T T T eth0: DHCP client bound to address 192.168.203.31
> WARNING: eth1: No MAC address set. Using random address 8a:ee:18:f5:98:e7
> T T T T T T T T T T T T T T T T T T T T could not open /mnt/tftp/none-linux-dev-rev-c: No such file or directory
> ERROR: Booting 'net' failed: No such file or directory
> boot: No such file or directory
>
> type exit to get to the menu
> barebox@ZII VF610 Development Board, Rev C:/ boot
> booting 'net'
>
> Loading ARM Linux zImage '/mnt/tftp/none-linux-zii-dev-rev-c-1'
> Loaded initrd unknown '/mnt/tftp/none-initramfs-zii-dev-rev-c-1'
> initrd is at 0x82509000-0x835593ff
> Loading devicetree from '/mnt/tftp/none-oftree-zii-dev-rev-c-1'
> commandline: console=ttyLP0,115200n8 ip=dhcp
> Ucompressing Linux... done, booting the kernel.
>
> To fix this, bring the interfaces up before setting up tftpboot.
>
> Signed-off-by: Vivien Didelot <vivien.didelot@gmail.com>
> ---
> defaultenv/defaultenv-2-base/boot/net | 3 +++
> 1 file changed, 3 insertions(+)
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-01-21 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 0:50 Vivien Didelot
2019-01-21 8:35 ` Sascha Hauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190121083555.mmsrjpw5at4kv7y2@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=vivien.didelot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox