Date: Mon, 27 Dec 2021 23:27:09 -0500 From: roboman <roboman7811@gmail.com> To: petru garstea <peter.garshtja@ambient-md.com>, freebsd-arm@freebsd.org Subject: Re: FreeBSD13.0 on Pine ROCK64 Message-ID: <03aeb8fbc817d0370f999f70faa167674105940b.camel@gmail.com> In-Reply-To: <64ec1bf0-4eea-2499-f728-83f093e95027@ambient-md.com> References: <64ec1bf0-4eea-2499-f728-83f093e95027@ambient-md.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-jKzLovg2U01HuPe6g5ID
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Petru,
I have 4 Rock64 devices. I'm just using sdcards instead of
eMMC (FYI). I followed a similar path to yours below. I "burned" an
image for device #1. It didn't boot immediately. There is a lot of
online documentation on creating a serial console to view the boot
output; but they all require more than what I had available at my house
(custom USB cables, messing with wires, etc.). At the time, I was
accustomed to single board computers outputing to HDMI during boot but
came to realize from my research that the Rock64 devices do not output
to HDMI until/unless the kernel boots 3/4 of the way.
I followed some documentation to flash the U-boot code to the SPI
flash. U-boot appears to be similar to Linux "Grub" and the SPI is
similar to an old fashioned BIOS. After messing with it several times,
it worked on device#1. I flashed the SPI and the FreeBSD 13 boot image
worked fine. I used the same 'dd' command you did below. What you did
is correct.
Then I moved on to Rock64 device #2. On this device I tried
burning an SDCard just like the 1st device. Wouldn't boot.... no
surprise... I didn't "flash" the SPI yet; but I wanted to test it 1st.
I then proceeded to 'flash' the SPI with U-boot.... still didn't boot.
At this point I switched sdcards between working device #1 and device
#2. Still didn't work. I switched the sdcards back to their original
device and verified device #1 booted fine with either microSD card. I
assumed it MUST be that SPI, so I proceeded to "factory wipe" and
reload the FreeBSD-13 'friendly' U-boot code. no luck. I moved device
#2 to a troubleshooting bench of my basement which happened to have a
older 100 MB switch instead of a 1 GB switch. To my surprise, the
device started pinging on the network!!!!
Here's where I accidentally found something weird!!!
Turns-out, some (not all) of these Rock64s will not connect to
a 1 gig switch port. If I hard-code my primary switch port to 100 MB,
the Rock64 booted to the network no problem. If I switch the switch
port back to "auto" [10/100/1000], it won't connect.
I proceeded to "U-boot" flash the SPI of the other two devices
(3 &4) and create sdcards for all of them.
My result:
Device 1 works perfectly
Device 2 only works 100 MB
Device 3 only works 100 MB
Device 4 only works 100 MB
I reloaded devices 2-4 w/Armbian and they all work fine at 1 GB. It
appears to be a FreeBSD NIC driver-related issue. I posted details on
this forum and didn't get any solutions. I ended up moving to Armbian
for all 4 devices due to this problem being unresolved.
Recommend: Test on a 100 MB switch port and see if you are having the
same problem. If yes, see attached response I received from a fellow
FreeBSD-ARM member.
-Jeff
On Mon, 2021-12-27 at 22:40 -0500, petru garstea wrote:
> Greetings,
>
> Hope all is well.
>
> I burned on emmc drive a FBSD13 version for pine rock64 SOC however
> the
> system doesn't boot.
>
> The command I used
>
> dd if=FreeBSD-13.0-RELEASE-arm64-aarch64-ROCK64.img of=/dev/da0
> bs=1m
> conv=sync status=progress
>
> Then I validate the partition tables
>
> gpart show
> => 40 6291376 da0 GPT (29G) [CORRUPT]
> 40 32728 - free - (16M)
> 32768 102400 1 efi (50M)
> 135168 6156160 2 freebsd-ufs (2.9G)
> 6291328 88 - free - (44K)
>
>
> I tried to boot as is but no luck, then since the GPT is corrupted I
> ran
>
> gpt recover da0
>
> But the result is the same, the system doesnt boot.
>
>
> I tested an armbian image and that worked well.
>
>
> Please advise.
>
>
> Cheers,
>
> Petru
>
>
--=-jKzLovg2U01HuPe6g5ID
Content-Disposition: inline
Content-Description: Attached message - Re: Rock64 1Gb Ethernet not working,
100 MB okay
Content-Type: message/rfc822
Delivered-To: roboman7811@gmail.com
Received: by 2002:a17:907:7051:0:0:0:0 with SMTP id ws17csp667046ejb;
Fri, 22 Oct 2021 11:35:21 -0700 (PDT)
X-Google-Smtp-Source:
ABdhPJwcbI3Ic42inYXJjN4rtP5dEaNMHUNSdsdQWQ/yluG3Bk6xjckZsvpjWO69kRe4uV7mf7xw
X-Received: by 2002:a05:6402:5189:: with SMTP id
q9mr2186243edd.94.1634927720955; Fri, 22 Oct 2021 11:35:20 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1634927720; cv=none; d=google.com;
s=arc-20160816;
b=FakXfpWZwCGuLIJg/chu0Vd4H1uBnSsQiLuN+TU0MnME1Mg3tsXmZNFbyDkL47XSTu
K9xeFdmQ2x9a5zXZ+0almaOPqquIYxBH1ziaHFpKCJgaHlpKjHou5ONTC8nuFaAz6saj
S1VtjomWNfLtrb+IyItSMTAklsaZoi2U7i9ft+QIVAlbnP8jYgq2//q2lElIMxL0ma2H
4pXLlvSdoShREjDVoxNB2oz77Sg3qOhpWKyuO1YykXXnqaMchnTInzp1/dJgu9cRL6r0
D8XY2RMXSFXz4gTeh37WbwfsfgccynFsYHTZDYk91+LGLrCA35LfFhfTrtkrXZAmGEcI xnxg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
s=arc-20160816;
h=mime-version:references:in-reply-to:organization:message-id:date
:subject:cc:to:from; bh=GXsJ0FBF5vtep8YTGEHEX4cVYbFdSpSpWz6BdFGiIcE=;
b=jjs9rjjirdvfy1AnNhL+imQRi/sE+tB9T3yhXREDP9/+u2bJFpeMqqaylEuKFJpOGH
1PPwbJCCtr38xGsipKCCKjj414PVFU1M7z3/kQcRbUgyhl3nM0aYunJb32J69xetvmAX
A/BvWViGSUtEUySZGXVKxBCmQV81U+QxoiLodS7pWtCkke5RvJXL1snxaBky38616Kaq
gI5iYLGPGzXphN3Af2BiR34q4paDBCPOezPKi44ljWBjsJNENFQQ02oFROp49EbDVwzy
M3YDG1JVp7r7s/wfV+ylCVdRfbg29Wxiw4M2k82cmfE8/6UatF6kDn+GJmD9bAduMjNu uuEQ==
ARC-Authentication-Results: i=1; mx.google.com; spf=softfail (google.com:
domain of transitioning adridg@freebsd.org does not designate 194.109.24.25
as permitted sender) smtp.mailfrom=adridg@freebsd.org
Return-Path: <adridg@freebsd.org>
Received: from lb2-smtp-cloud8.xs4all.net (lb2-smtp-cloud8.xs4all.net.
[194.109.24.25]) by mx.google.com with ESMTPS id
r2si12365844eja.442.2021.10.22.11.35.20 for <roboman7811@gmail.com>
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Oct
2021 11:35:20 -0700 (PDT)
Received-SPF: softfail (google.com: domain of transitioning
adridg@freebsd.org does not designate 194.109.24.25 as permitted sender)
client-ip=194.109.24.25;
Authentication-Results: mx.google.com; spf=softfail (google.com: domain of
transitioning adridg@freebsd.org does not designate 194.109.24.25 as
permitted sender) smtp.mailfrom=adridg@freebsd.org
Received: from cust-d4a83f22 ([IPv6:fc0c:c11d:cecc:f58a:eaa1:c0:9d8f:c143])
by smtp-cloud8.xs4all.net with ESMTPA
id dzNtm2cFPFfMidzNvmR3wf; Fri, 22 Oct 2021 20:35:20 +0200
From: Adriaan de Groot <adridg@freebsd.org>
To: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Cc: roboman <roboman7811@gmail.com>
Subject: Re: Rock64 1Gb Ethernet not working, 100 MB okay
Date: Fri, 22 Oct 2021 20:35:17 +0200
Message-ID: <2902939.hHqAuc6tWs@beastie.bionicmutton.org>
Organization: FreeBSD
In-Reply-To: <cb4f03de58be061451b1ae69ed50983b687e603d.camel@gmail.com>
References: <cb4f03de58be061451b1ae69ed50983b687e603d.camel@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2302286.THHZn3L5Ee"; micalg="pgp-sha256"; protocol="application/pgp-signature"
X-CMAE-Envelope:
MS4xfOq+FXdWsbitWTtGWhv6S7Av/enM11J+UTcWqatC5w6qHjnwh6atOHg7lWyzmBclRZ8aDUalgeOulLFNmwIryPfBjX4lvXRYgaHHhOhUThP9PFMGQ9j+
VDCGI3WJlh2iPpftrZSDpvfMbn4CcN64vBGJHuhlB1+TMclVukebh3WieXnOlEHqnvkf/4YDlsvwdNDlPbjxrRxApTog7smptNR95nTzjSyrOjtY7Qc0TYkZ
w1V7U20FtdSwHtWLT5xHTo+ETjkoYALzbfVNkUSIaQ6qyIdq14bWqO1/VSyGgn1T
X-Evolution-Source: ec1a921a6e17257d5a4bd2aabc6110ded3dcfd40
--nextPart2302286.THHZn3L5Ee
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Adriaan de Groot <adridg@freebsd.org>
To: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Cc: roboman <roboman7811@gmail.com>
Subject: Re: Rock64 1Gb Ethernet not working, 100 MB okay
Date: Fri, 22 Oct 2021 20:35:17 +0200
Message-ID: <2902939.hHqAuc6tWs@beastie.bionicmutton.org>
Organization: FreeBSD
In-Reply-To: <cb4f03de58be061451b1ae69ed50983b687e603d.camel@gmail.com>
References: <cb4f03de58be061451b1ae69ed50983b687e603d.camel@gmail.com>
On Friday, 22 October 2021 08:22:21 CEST roboman wrote:
> One is running 13-Release at 1GB and is operating 100% stable @ 1Gb as
> a NFS server w/several active clients.
>
> Three fail to connect either via static or DHCP @ 1 Gb.
There was a lengthy thread "Rock64 flaky ethernet?" back in May on this list.
Yout can find blog-posts about it -- not necessarily FreeBSD-related though --
at places like
https://forum.pine64.org/showthread.php?tid=7545
https://sanisimov.com/2019/08/fixing-rock64-v2-gigabit-ethernet/
I was unsuccessful at finding the "right" timings to improve performance and
gave up on that particular board (not Rock64 overall, just the specific one on
my desk).
[ade]
--nextPart2302286.THHZn3L5Ee
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit
-----BEGIN PGP SIGNATURE-----
iQGzBAABCAAdFiEEhrjttu2OP5apuuy1z93JbxKxkVwFAmFzBGUACgkQz93JbxKx
kVwx2wv/cA6CBwDIQ6eMu6L1WE0onbkcMTcpHwaAolIiwbe0QSCIFglslB1IueO3
vyvMTHsvxWTBfJ5LH8gXUZXAurexaoidSMraFkPdxsB1wNZKCWoebO4EqWSHecdP
nfXetZ8be2hrJVPUbKWdDDYcqNTAb8WI0dVE8KrTRecctRvMAMl3eLb278bNprub
OSqnldnvr2/RJcExohJ1rSc+q6u/1XkTmyTK2xTZ/BYEMUKRmEjePbzKkD13910B
X7qQGMZpMn1xUFGC3ej+icbDHv76gfWHJmH03t53+ZSHragfDTo1lvFMw16aeBmc
C79rKEwIEvt1dp3ooUNrXr55cuzHlLoVFa+cRuHf6WzvDndBk7HKDQOeNoXdL1Jt
hcnc8ii0hPdxFXpwmJ76CF2cZGBWut53IuVOZpCP85W2ycNyrsgo5Ns54Vgk97iM
2ItnV084QSnJ9BVQCxuAr6x93Qkof19VULN6v0BGBImKqObRZuSorSOXGYZhPSDw
93Vz1f3C
=ESF4
-----END PGP SIGNATURE-----
--nextPart2302286.THHZn3L5Ee--
--=-jKzLovg2U01HuPe6g5ID--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?03aeb8fbc817d0370f999f70faa167674105940b.camel>