From owner-freebsd-arm@freebsd.org Mon Feb 8 01:25:21 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0C73C53F9FE for ; Mon, 8 Feb 2021 01:25:21 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from mx1.shrew.net (mx1.shrew.net [38.97.5.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DYpHM6N57z4RhL for ; Mon, 8 Feb 2021 01:25:19 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from mail.shrew.net (mail.shrew.prv [10.24.10.20]) by mx1.shrew.net (8.15.2/8.15.2) with ESMTP id 1181PCm6065314; Sun, 7 Feb 2021 19:25:12 -0600 (CST) (envelope-from mgrooms@shrew.net) Received: from [10.22.200.30] (unknown [136.49.68.36]) by mail.shrew.net (Postfix) with ESMTPSA id 0E773199F79; Sun, 7 Feb 2021 19:25:07 -0600 (CST) Subject: Re: rpi4 network boot To: =?UTF-8?Q?Klaus_K=c3=bcchemann?= , Torfinn Ingolfsen , Mike Karels , freebsd-arm@freebsd.org References: <3a1acba5-8662-55cb-c5c4-98ec7873f78f@shrew.net> <082BC0B9-2538-43D5-9D5E-C18B4DEE9ECB@googlemail.com> <2D8B4921-CCEB-4203-B616-C0C86612C1E5@googlemail.com> <24127be9-ff90-ad97-ada5-2c2175f34fd4@shrew.net> <20210207201956.f289206d5eb560c034fea7a4@getmail.no> <7DB4B9E5-2CA4-4AA3-B3EB-61A4807CFC9E@googlemail.com> From: Matthew Grooms Message-ID: Date: Sun, 7 Feb 2021 19:24:57 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <7DB4B9E5-2CA4-4AA3-B3EB-61A4807CFC9E@googlemail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx1.shrew.net [10.24.10.10]); Sun, 07 Feb 2021 19:25:13 -0600 (CST) X-Rspamd-Queue-Id: 4DYpHM6N57z4RhL X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mgrooms@shrew.net designates 38.97.5.131 as permitted sender) smtp.mailfrom=mgrooms@shrew.net X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[shrew.net]; RBL_DBL_DONT_QUERY_IPS(0.00)[38.97.5.131:from]; SPAMHAUS_ZRD(0.00)[38.97.5.131:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEMAIL_TO(0.00)[googlemail.com,getmail.no,karels.net,freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:174, ipnet:38.0.0.0/8, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm]; RECEIVED_SPAMHAUS_PBL(0.00)[136.49.68.36:received] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2021 01:25:21 -0000 On 2/7/2021 2:00 PM, Klaus Küchemann wrote: > Am 07.02.2021 um 20:19 schrieb Torfinn Ingolfsen > : >> I believe he is asking you to verify that the fstab file for the _client_ (aka the diskless machine your'e trying to boot) is correct. That file exists as >> ${NFSROOTDIR}/etc/fstab on the boot server. >> >> HTH >> -- >> Torfinn Ingolfsen >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org“ > Yes, the fstab-setup is important…... but then I realized Matthew`s boot environment : > He has u-boot sitting on the pxe-Server, whereas the eeprom was flashed for completely diskless netboot > as a requirement . > With that setup in fact we will end up in n infinite loop of an 'genet0: gen_intr2‘ -console-output, > regardless of fstab or whatever configuration elsewhere I tried. Thanks for testing and re-producing that. Corroborating test results were also posted by others in the FreeBSD forum thread I referenced earlier. > I have now refreshed the eeprom to it’s default(where diskless pxe-boot is disabled ) > And again successfully net-booted (14_current in this case) : > > https://dmesgd.nycbug.org/index.cgi?do=view&id=5917 > > Since netboot from u-boot on the uSD requiresdonly 1 command by hand (load net0:/boot/kernel/kernel > )(+ command :’boot’) and there’s no problem with the genet-driver I guess that > It’s an issue of the pxe-flashed eeprom where we don’t yet know exactly what happens. I have a slightly different take: The network device appears to work well initially when used by the eeprom and after the hand-off to u-boot. The FreeBSD genet driver generally works well unless the device is first used by eeprom/u-boot. I suspect that u-boot is performing some task that leaves the device in a state that is incompatible what FreeBSD expects and/or can work with. Perhaps there is a way to force some a full device reset of genet either before u-boot hands things off to FreeBSD or right after FreeBSD loads the genet driver? If so, maybe that would be worth trying, even as a hacky test, to see if it's the network device state that's wonky. > So for now I guess netboot from uSD is a painless and well working setup, > while to be honest: > I don’t remember exactly at the moment how I figured to get it to work after trials&errors :-) Ha Ha > But I’ll leave the uSD untouched or copy the folder to have a point for a tutorial or so if someone is interested in. Can that be done without human intervention? Perhaps with some sort of u-boot or EFI script that gets executed? If this method requires the user to enter a command to boot from the network, it's not an alternative to PXE. Thanks, -Matthew