From nobody Sun Jun 16 08:02:48 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4W259721Kbz5NWyQ for ; Sun, 16 Jun 2024 08:02:51 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4W25971D1kz4VB7; Sun, 16 Jun 2024 08:02:51 +0000 (UTC) (envelope-from decke@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1718524971; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4qDEoFLs1baiETZTahVRmSYn6H78Q/LOTn/VUJ2rniU=; b=NFftfy84bdF9ceiwoT4dSa70z+plLWUe1gvjr0w6N206+zd9XO8RYqquzoBL/b2OSasACK peWSV5XDx3/9BYGfHJ631YBrhi/rPwZGNpOphr4zpD+ReokQKXbWsRmt4aySyp5tBuiXVn tOw2YB5g1p781ZxTbDoleeL5GoSKhuHUH1QnA3EUqJ+a1KjM+7iM7HkjVMGqi6aDP3un/s fhSUms0ePOy9iMIfcbp8qSXbYpon1/KPhCCW1adAzQVZO6V1jTQH4VFmPcpMC68wUwD/3A Uk9A7xZRax4+s6+HCEZ83Sj/dJEq7SRR/X1Intdv7lc+CwsElf1snkN+AeEoNw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1718524971; a=rsa-sha256; cv=none; b=oPmHxmiGSFU1TP8P0Cg4mLOjPwPW172BV/JIS5ITSl2+/p+zOFVnXqOL837UBle4eFdcgQ NdiUZnlny/YjOCMEpYT50jmIM2osyaERljuUeUg78i7fK4K18b4OkGWbuLu+A/zxk1G+vw 2O/VZx1FW90aZXrH7Thh+w6OPgCr6BcTL2OJ4ZdJlKt2f6WY0+U/9q8UM79ZhNOsddTlcN kHQZFpSpepSF+5/02f7WGBuaJxXcRlOVm80neHsvd0HB5ppzSpaNvH/qYTVJECTFQ/up56 9qgSxf4r2pfFACIsLvXwwHKit5qEndZ09cLrVpKpMHw44ackS3ttzoJ+DoxsJQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1718524971; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4qDEoFLs1baiETZTahVRmSYn6H78Q/LOTn/VUJ2rniU=; b=hkYwZ+PpnvuM+mtPOyiaHu1tV6YBDJasqyVewGYWKMvB3bdIsSX5wLBaDD+yyfk2PgeaY9 vXOWO8Bi5YV4CFubI0+Fx5btGCmGNhxMLr+pvEAmWnDzBxXsrh02VIEn8FaFQqAKHWPXwH 8nXv2bfzmewzyj2rR+1OThhrp1bmuiVsUkH70UIqGfXxqEvV6KbI2xBk/3CcX90GzCnXg4 mgXTpVYe5K6O7D/vkDHrMIqI41pyyvLnEUOGZA4hz8/sDRmEv/9XIDDl/GzHE8WxNn4TbW vgN2cwVGdcoFFlDAtrX3L2EvjoKkIJlNzx/WMICufi/qyQgCSUlKt4pEgPrCbA== Received: from sender21-mail.zoho.eu (unknown [31.186.226.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: decke) by smtp.freebsd.org (Postfix) with ESMTPSA id 4W25965hkVz13GR; Sun, 16 Jun 2024 08:02:50 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from mail.zoho.eu by mx.zoho.eu with SMTP id 1718524968816648.1052185705413; Sun, 16 Jun 2024 10:02:48 +0200 (CEST) Date: Sun, 16 Jun 2024 10:02:48 +0200 From: Bernhard Froehlich To: "Nenhum_de_Nos" Cc: "freebsd-arm" Message-ID: <1902011ff6f.ee408da2133707.5064509573257891278@FreeBSD.org> In-Reply-To: <8efeb00d253639ca213d3009f38633e5.squirrel@10.1.7.91> References: <8efeb00d253639ca213d3009f38633e5.squirrel@10.1.7.91> Subject: Re: FreeBSD on Nanopi R4S(E) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Importance: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail ---- On Sat, 15 Jun 2024 00:11:14 +0200 Nenhum_de_Nos wrote ---=20 > Hello, >=20 > I amd trying to install FreeBSD 14.1 on this arm64 board and, despite > booting fine till the booting process needs to mount the root partition. > It just finds none. I am using sd card on it, but tried also having a co= py > on the USB stick. I finds none, and the boot process won't continue. >=20 > Have anyone done this? I know there are images for FreeBSD 13.x for it, > but I cannot find any clues so far on how to make it boot. >=20 > I am using the guide on > https://forums.freebsd.org/threads/nanopi-r4s-official-images-not-yet-av= ailable.91167/post-651057 Hi Matheus, i'm glad you asked for NanoPi R4S support but you are actually a bit late to the show. I worked on it in 2021 and well I hope it still works but ther= e has not been much interest in it actually. Since my backup R4S board broke (RAM chip defect) in 2022 I do not have a spare one around to play with but I still have some notes and one running in production=20 -- Bernhard Froehlich https://www.bluelife.at/ with OpenWRT :(. To build your own release image you can roughly follow the outdated instructions from the wiki: https://wiki.freebsd.org/arm/Build_image_using_release_building_infrastruct= ure it should be a bit more like: * make sure you have the 14.1-RELEASE sources checked out in /usr/src * make sure sysutils/u-boot-nanopi-r4s port is installed * copy NANOPI-R4S.conf from https://reviews.freebsd.org/D31134 to /usr/src/= release/arm64/ cd /usr/src/release sh release.sh -c arm64/NANOPI-R4S.conf Since in the forum thread you asked about PersonalBSD images I can only say that I personally do not trust any 3rd party images which I can't verify in any production environment. But I also tested his R4S images from 2021 and they were actually working fine in most regards. He always used a patched and outdated u-boot which can be a pain (but usually also newer u-boot can be pain) and applied his own sauce to some configs and stuff which might not be what you expect in some details. His u-boot sources can be found here: https://github.com/S199pWa1k9r/ports/tree/master/sysutils/u-boot-nanopi-r4s= -2020.07 Some notes from 2021 that might help you: * They use a special hack to store their MAC address (on older models) so your re0 interface might not have a MAC. This can be easily solved by like this: ifconfig re0 link 12:89:BB:YY:XX:AA * NanoPI R4S 1GB model might not work with official u-boot because only the 4GB model was upstreamed (might have changed in the meantime) * re0 device only visible when cable is connected at boot (make sure it is) -- Bernhard Fr=C3=B6hlich https://www.bluelife.at/