Date: Tue, 30 Nov 2021 14:46:40 -0800 From: Mark Millard via freebsd-arm <freebsd-arm@freebsd.org> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-arm@freebsd.org Subject: Re: booting recent rpi current/14 snapshots Message-ID: <55EF15D1-4121-4F12-8167-353C52D3F72F@yahoo.com> In-Reply-To: <YaZkS/uDdA3/QxgY@cloud.zyxst.net> References: <YaZkS/uDdA3/QxgY@cloud.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Nov-30, at 09:50, tech-lists <tech-lists@zyxst.net> wrote: > Hello arm@ >=20 > Has anyone tried booting the recent current snapshots? >=20 > I've tried these ones. all written to good microsd cards, and sha256 = checked: >=20 > = https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/14.0/FreeBSD-14.0-CU= RRENT-arm64-aarch64-RPI-20211111-448bcd01dc5-250603.img.xz > = https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/14.0/FreeBSD-14.0-CU= RRENT-arm64-aarch64-RPI-20211118-4082b189d2c-250820.img.xz > = https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/14.0/FreeBSD-14.0-CU= RRENT-arm64-aarch64-RPI-20211125-3ede04c78c7-251054.img.xz >=20 > Get a rainbow screen and there it stops. >=20 > Anyone know of a working version? >=20 > What I'm trying to do is to run the installer and point it to a = connected usb3 > disk in order to facilitate usb3 boot-to-zfs. But I'm not even getting = as far as the installer. Looks like that last (20211125-3ede04c78c7 put on a microsd card) has: # mount -onoatime -tmsdosfs /dev/mmcsd1s1 /media # strings /media/start4.elf | grep VC_BUILD_ID_ VC_BUILD_ID_USER: dom VC_BUILD_ID_TIME: 12:10:40 VC_BUILD_ID_VARIANT: start VC_BUILD_ID_TIME: Feb 25 2021 VC_BUILD_ID_BRANCH: bcm2711_2 VC_BUILD_ID_HOSTNAME: buildbot VC_BUILD_ID_PLATFORM: raspberrypi_linux VC_BUILD_ID_VERSION: 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean) (I ignore armstub8-gic.bin here.) # strings /media/u-boot.bin | grep "U-Boot 2" U-Boot 2021.07 (Nov 25 2021 - 05:58:44 +0000) # more /media/config.txt [all] arm_64bit=3D1 dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don dtoverlay=3Dmmc dtoverlay=3Ddisable-bt device_tree_address=3D0x4000 kernel=3Du-boot.bin [pi4] hdmi_safe=3D1 armstub=3Darmstub8-gic.bin But I'm modifying it to: # more /media/config.txt [all] arm_64bit=3D1 dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don dtoverlay=3Dmmc dtoverlay=3Ddisable-bt device_tree_address=3D0x4000 kernel=3Du-boot.bin [pi4] #hdmi_safe=3D1 armstub=3Darmstub8-gic.bin # Local additions: [all] enable_uart=3D1 uart_2ndstage=3D1 dtdebug=3D1 disable_commandline_tags=3D1 disable_overscan=3D1 gpu_mem_1024=3D32 [pi4] over_voltage=3D6 arm_freq=3D2000 sdram_freq_min=3D3200 force_turbo=3D1 [all] Note the disabling of hdmi_safe=3D1 . The 8 GiByte RPi4B's eeprom also has debugging enabled. So with a monitor attached (unusual for me) and a serial console as well, it boots to the login prompt just fine, both on the serial console and the monitor. I logged in to both. # uname -apKU FreeBSD generic 14.0-CURRENT FreeBSD 14.0-CURRENT #0 = main-n251054-3ede04c78c7: Thu Nov 25 09:59:03 UTC 2021 = root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC = arm64 aarch64 1400042 1400042 For reference: EFI framebuffer information: addr, size 0x3e402000, 0x7e9000 dimensions 1920 x 1080 stride 1920 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 . . . VT(efifb): resolution 1920x1080 . . . fb0: <BCM2835 VT framebuffer driver> on simplebus0 fb0: keeping existing fb bpp of 32 fbd0 on fb0 WARNING: Device "fb" is Giant locked and may be deleted before FreeBSD = 14.0. VT: Replacing driver "efifb" with new "fb". fb0: 1920x1080(1920x1080@0,0) 32bpp fb0: fbswap: 1, pitch 7680, base 0x3e402000, screen_size 8355840 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55EF15D1-4121-4F12-8167-353C52D3F72F>