From owner-freebsd-arm@freebsd.org Wed May 20 03:56:44 2020 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 9D1122FDB22 for ; Wed, 20 May 2020 03:56:44 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-22.consmr.mail.gq1.yahoo.com (sonic310-22.consmr.mail.gq1.yahoo.com [98.137.69.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49Rf7v2586z4cBN for ; Wed, 20 May 2020 03:56:43 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: YAfqKtEVM1mEfdmlu.lN4D02zL84lBKpDpeW4b3m_iJWOefwxN4s1X64YtSRNFS tY57ujhpa2Jj9noj5JcPxnPHHnQRCEMG5sJoKcfD4hkwT9KUg2azrojinBqwtV.XGySAzkBz9Vtk xmPrKYenGbCvEseTQm3pN6u78VpSHX0kbx4iVKz0bWMdvmoLYt.xrMBd6Ju.XoqLPsKb.Shsrhji 9Y0LtHb6DFI5M_0JCLyZuFUv2xkxxh7nAWjNvt0DeKwZmX.usjJqNLFgxkkJDLOaq5BY8sNJ8iR4 Zhb_tB9DddMcQAYXuQZs7ml4pTCuwbr5D6hHpAxDOdVHPfe0dUgcn.uYibUBl6qm5pprHazgAaxx nS8bff3Yw47O8a2RRFQKJkMqsUK2z6eoDAtdrh.mLsxI.5fijLFYfwVv5GGCOE8OuFyBOvx8nU.n FlmrGu0EGAx8De_lvDJR_K6IKhLGdIA1IKyb2ELYyXN16O.Y5ogkMj9BCf3v7ae4GebRFZn1jHzq G_wqCRmXajTROjjqQVp9lNfTx8HhkLrNUC6lxqg_VPuOteelX5cza3tVEfvzb.4oBoUsOEkOkMSe AFn136_XmZ0ek.ZJ7v4rXz1GXEWVVmwNI0alybsytC0v2A8kG2_ZzB9mPcAt7ZAgMhNjQn6Jnnii HvUnNXgIHT93MnIgFIv42aJ4v8PnxmQCZFw.CabDvFmFNdq_kvsw45A5x0bXwwz07b3YuBBNH7VU 6fFm0uV2HrGx3f0dMR.mlhgcMx9YKQB9ijKbDKVb84Ab41YH7qC9mVbHFxLYUH4Qc4VrbNCUBdix .MyeD6KUUwbjsocSR1AULQY6JmBcyDaMs5B7BAi4ZmpLw4CmMaU.uVEHmR4OhzbN1BiVLc7SyRTK 5UP5d5vl1.v2B1HmPhUw8u.zzoZBkibdVDFnvF.3y7yMDRZJNSzVD.ecnbtSSiCRSKsSGT0QCo7Q TrSoPjsETlzgaypjqrneDBDnBgTvWq46IBE644eRiZLrahalyH5Iehjwl7P5kZzR_lXy12DgQP9h LePmO.T5XbIaFu9nSRy6e22XBim8tyMyxaiQYDBbW9wZLDj9shIdF_jATXuDFvSu3KL8Maz7bBkR F9GiAGvRNlTgmts0fg6ml58XzaZGAt4E294AxHFtr9Ur7P0EfgwXArrWkg9Fyemjy3RFWDrupdxa pdcVM5UXeozZJ7s6U5h6e5JIFXxs3ELaUYPeAs9npA61z5MTKouuUoNWsSpdlZCuAVFuJ.jt3PQ6 RUTjJmkquYBQA0AobwvHKZdsjcDE6nm5Mx8kIcWHgIp2pjKXyM6KU2U8HSEIqhGLpW07JIGQtfXY _HxnRS2QkjN8yw1xbUGaZC887MfACpk0ttQ8kj0_TZQq.HajVW1UjoGlhCI96BHzWz3hof6qEdI_ 5gEHvfiqifMhpF5Ltv.wf Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Wed, 20 May 2020 03:56:41 +0000 Received: by smtp411.mail.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID fb2f329a629bc4c2ed931a9f400eb7d6; Wed, 20 May 2020 03:56:38 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: rpi4 headless experience From: Mark Millard In-Reply-To: Date: Tue, 19 May 2020 20:56:37 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Dan Mack X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49Rf7v2586z4cBN X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.02 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.148:from]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; NEURAL_HAM_MEDIUM(-0.90)[-0.900]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.148:from]; NEURAL_HAM_SHORT(-0.62)[-0.617]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2020 03:56:44 -0000 On 2020-May-19, at 19:52, Dan Mack wrote: >=20 > Thanks for that info - this is my first foray into fbsd on arm so I = might be messing something up. As a test I swapped in an alpine linux = sdcard and booted the same rpi4-4 and this is what it reports for cpu = and memory. What the heck am I doing wrong? :-) >=20 > # alpine >=20 > Booting Linux on physical CPU 0x0000000000 [0x410fd083] > Linux version 5.4.12-0-rpi4 (buildozer@build-3-11-aarch64) version = 9.2.0 (Alpine 9.2.0)) #1-Alpine SMP PREEMPT Thu Jan 16 Machine model: = Raspberry Pi 4 Model B Rev 1.1 >=20 > pi4f:~# cat /proc/cpuinfo > processor : 0 > BogoMIPS : 108.00 > Features : fp asimd evtstrm crc32 cpuid > CPU implementer : 0x41 > CPU architecture: 8 > CPU variant : 0x0 > CPU part : 0xd08 > CPU revision : 3 >=20 > processor : 1 > BogoMIPS : 108.00 > Features : fp asimd evtstrm crc32 cpuid > CPU implementer : 0x41 > CPU architecture: 8 > CPU variant : 0x0 > CPU part : 0xd08 > CPU revision : 3 >=20 > processor : 2 > BogoMIPS : 108.00 > Features : fp asimd evtstrm crc32 cpuid > CPU implementer : 0x41 > CPU architecture: 8 > CPU variant : 0x0 > CPU part : 0xd08 > CPU revision : 3 >=20 > processor : 3 > BogoMIPS : 108.00 > Features : fp asimd evtstrm crc32 cpuid > CPU implementer : 0x41 > CPU architecture: 8 > CPU variant : 0x0 > CPU part : 0xd08 > CPU revision : 3 >=20 > Hardware : BCM2835 > Revision : c03111 > Serial : 100000002b2bb8fd > Model : Raspberry Pi 4 Model B Rev 1.1 >=20 > pi4f:~# cat /proc/meminfo > MemTotal: 3890684 kB > MemFree: 3739844 kB > >=20 > Since others are not seeing the memory discrepency, more investigation = is warranted on my end. >=20 > Take care. >=20 > Dan I just realized that your original message said: "Just tried the latest FreeBSD on RPI image on my rpi4-4GB system." There is no such image for the RPi4. Looking at: = https://lists.freebsd.org/pipermail/freebsd-snapshots/2020-May/000698.html= shows: o 13.0-CURRENT aarch64 GENERIC o 13.0-CURRENT aarch64 RPI3 o 13.0-CURRENT aarch64 PINE64 o 13.0-CURRENT aarch64 PINE64-LTS o 13.0-CURRENT aarch64 PINEBOOK o 13.0-CURRENT aarch64 ROCK64 o 13.0-CURRENT aarch64 ROCKPRO64 Treating an RPi4 as a RPi3 is not going to make everything work: it does not have the right variant of u-boot, for example. The following lists installed files from ports: sysutils/u-boot-rpi[34] sysutils/rpi-firmware The installations of the 2 prots only puts the files someplace so they (or some) can later be copied to the msdos file system involved. # ls -ldT /usr/local/share/u-boot/u-boot-rpi[34]/* -rw-r--r-- 1 root wheel 124 Apr 25 00:16:57 2020 = /usr/local/share/u-boot/u-boot-rpi3/README -rw-r--r-- 1 root wheel 37 Apr 25 00:16:55 2020 = /usr/local/share/u-boot/u-boot-rpi3/metadata -rw-r--r-- 1 root wheel 499824 Apr 25 00:16:54 2020 = /usr/local/share/u-boot/u-boot-rpi3/u-boot.bin -rw-r--r-- 1 root wheel 124 Apr 25 13:28:34 2020 = /usr/local/share/u-boot/u-boot-rpi4/README -rw-r--r-- 1 root wheel 37 Apr 25 13:28:34 2020 = /usr/local/share/u-boot/u-boot-rpi4/metadata -rw-r--r-- 1 root wheel 506360 Apr 25 13:28:34 2020 = /usr/local/share/u-boot/u-boot-rpi4/u-boot.bin If you replaced the u-boot.bin in the msdos file system with the rpi4 one the memory might well show correctly. There is also: # ls -ldT /usr/local/share/rpi-firmware/* . . . -rw-r--r-- 1 root wheel 89 Jan 30 13:26:19 2020 = /usr/local/share/rpi-firmware/config.txt -rw-r--r-- 1 root wheel 147 Jan 30 13:26:19 2020 = /usr/local/share/rpi-firmware/config_rpi3.txt -rw-r--r-- 1 root wheel 135 Jan 30 13:26:20 2020 = /usr/local/share/rpi-firmware/config_rpi4.txt -rw-r--r-- 1 root wheel 110 Jan 30 13:26:19 2020 = /usr/local/share/rpi-firmware/config_rpi_0_w.txt . . . where you would need to copy the config_rpi4.txt content to the config.txt in use on the msdos file system. There are other files for the RPi4 from the list as well. I've not checked a rpi3 snapshot do know if the snapshot has copies of RPi4 specific files: -rw-r--r-- 1 root wheel 5888 Jan 30 13:26:31 2020 = /usr/local/share/rpi-firmware/armstub8-gic.bin -rw-r--r-- 1 root wheel 40659 Nov 22 09:06:45 2019 = /usr/local/share/rpi-firmware/bcm2711-rpi-4-b.dtb -rw-r--r-- 1 root wheel 6193 Nov 22 09:06:45 2019 = /usr/local/share/rpi-firmware/fixup4.dat -rw-r--r-- 1 root wheel 3089 Nov 22 09:06:45 2019 = /usr/local/share/rpi-firmware/fixup4cd.dat -rw-r--r-- 1 root wheel 9181 Nov 22 09:06:45 2019 = /usr/local/share/rpi-firmware/fixup4db.dat -rw-r--r-- 1 root wheel 9183 Nov 22 09:06:45 2019 = /usr/local/share/rpi-firmware/fixup4x.dat -rw-r--r-- 1 root wheel 2775076 Nov 22 09:06:45 2019 = /usr/local/share/rpi-firmware/start4.elf -rw-r--r-- 1 root wheel 775872 Nov 22 09:06:45 2019 = /usr/local/share/rpi-firmware/start4cd.elf -rw-r--r-- 1 root wheel 4582664 Nov 22 09:06:45 2019 = /usr/local/share/rpi-firmware/start4db.elf -rw-r--r-- 1 root wheel 3536680 Nov 22 09:06:45 2019 = /usr/local/share/rpi-firmware/start4x.elf in the msdosfs file system. Note (where config.txt is a copy/variant of config_rpi4.txt by content): # more /boot/efi/config.txt=20 arm_control=3D0x200 arm_64bit=3D1 dtoverlay=3Ddisable-bt dtoverlay=3Dmmc device_tree_address=3D0x4000 kernel=3Du-boot.bin armstub=3Darmstub8-gic.bin So, without armstub8-gic.bin being present in the msdos file system, the RPi4 config.txt content would then specify a missing file. Similarly for u-boot.bin . =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)