RPI2-Images

[Bernd Walter]

Just to get a recent FreeBSD on a Pi2 running, I've gone through a
few images with mixed results.

FreeBSD-11.0-RELEASE-arm-armv6-RPI2.img works fine.

FreeBSD-11.1-RC3-arm-armv6-RPI2.img shows this:
...
Mounting late filesystems:.
Configuring vt: blanktime.
Generating RSA host key.
2048 SHA256:ZPTJrJQQXL2z16vTJjZGRVT4KwflzxzYS4yWkbJ/Fgo root at rpi2 (RSA)
Generating ECDSA host key.
256 SHA256:GW8ubAvN0Qj8xUbPn8zlogndXpm13Du+A5U3lHwAtR8 root at rpi2 (ECDSA)
Generating ED25519 host key.
256 SHA256:rybupyofzcX+zlYaPFSp749fVjyyd3XrIquE0ogfr+8 root at rpi2 (ED25519)
Performing sanity check on sshd configuration.
Starting sshd.
Starting cron.
Starting background file system checks in 60 seconds.
[: =: unexpected operator
[: =: unexpected operator
mount: /dev/ufs/rootfs: Device busy

Fri Jul 14 14:57:48 
FreeBSD/arm (rpi2) (ttyu0)

login: 

Not sure what to think about the two '[: =: unexpected operator' messages,
but they only happened on the first boot and I can't see that anything
has failed.
FS was expanded to full SD size as well.
But since this is RC3 already, I think this should be investigated.

FreeBSD-12.0-CURRENT-arm-armv6-RPI2-20170710-r320869.img show this:
...
uhub1 on uhub0
uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2> on usbus0
uhub1: MTT enabled
GEOM_PART: ufs/rootfs was automatically resized.
  Use `gpart commit ufs/rootfs` to save changes or `gpart undo ufs/rootfs` to revert them.
mmcsd0s2 resized
growfs: /dev/ufs/rootfs: Operation not permitted
/etc/rc: WARNING: hostid: unable to figure out a UUID from DMI data, generating a new one
uhub1: 5 ports with 4 removable, self powered
ugen0.3: <vendor 0x0424 product 0xec00> at usbus0
smsc0 on uhub1
smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus0
smsc0: chip 0xec00, rev. 0002
miibus0: <MII bus> on smsc0
smscphy0: <SMC LAN8700 10/100 interface> PHY 1 on miibus0
smscphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ue0: <USB Ethernet> on smsc0
ue0: Ethernet address: b8:27:eb:07:20:c5
Setting hostuuid: dd0eedc4-65c4-11e7-bb07-b827eb0720c5.
Setting hostid: 0x7716eed6.
No suitable dump device was found.
Starting file system checks:
/dev/ufs/rootfs: NO WRITE ACCESS
/dev/ufs/rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Automatic file system check failed; help!
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Jul 10 23:09:45 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
Enter full pathname of shell or RETURN for /bin/sh: 

I remember seeing a discussion about write acces a few months ago, but
this is the most recent snapshot and I'd assumed it was fixed in the meantime.
Anyway - it's current after all, so no expectations.

-- 
B.Walter <bernd at bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.