From owner-freebsd-arm@freebsd.org Tue Jul 3 20:29:08 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E7DA1023AF3 for ; Tue, 3 Jul 2018 20:29:08 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 2A8A296C65 for ; Tue, 3 Jul 2018 20:29:08 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1faRv1-000NeQ-2J; Tue, 03 Jul 2018 13:28:59 -0700 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w63KSvLZ090917; Tue, 3 Jul 2018 13:28:57 -0700 (PDT) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Tue, 3 Jul 2018 13:28:57 -0700 From: Oleksandr Tymoshenko To: Ronald Klop Cc: Stefan Parvu , freebsd-arm@freebsd.org Subject: Re: FreeBSD on latest RPI3+ Message-ID: <20180703202857.GA90907@bluezbox.com> References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> <1DAB1D3D-DEA3-4904-A290-0EDC4B25217A@kronometrix.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Ronald Klop (ronald-lists@klop.ws) wrote: > On Tue, 03 Jul 2018 20:57:04 +0200, Stefan Parvu > wrote: > > > > >> Yes, I have it running out of the box. Just install the RPI3 F [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 20:29:08 -0000 Ronald Klop (ronald-lists@klop.ws) wrote: > On Tue, 03 Jul 2018 20:57:04 +0200, Stefan Parvu > wrote: > > > > >> Yes, I have it running out of the box. Just install the RPI3 FreeBSD > >> 12/aarch64 snapshot [1][2]. > >> Since a couple of weeks ethernet is supported. WiFi and bluetooth are > >> not (yet) supported. > > > > Im experimenting with it already. Are you using this > > image:FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180628-r335760.img.xz > > and this should support the NIC ? > > > I installed an image of a few weeks ago so the one you mention has the > right driver also. The driver is named if_muge. > The system should load this driver automaticly at boot. > See 'kldstat' if it is loaded or not. > With 'ifconfig' it will show up as 'ue0'. > > What I find anoying is that the mac address of the ethernet changes every > time you boot. So I hardcoded this in /etc/rc.conf. > ifconfig_ue0="ether 12:34:56:78:90:ab DHCP" > > Instead of the number above I used one of the random values it used and I > happened to register in my dhcp server/router. I've just submitted a patch for review that addresses this problem: https://reviews.freebsd.org/D16117 -- gonzo