OPNsense: {
fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
url: "http://neko.progr.am/pieSense/${ABI}/19.1/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
Minimum required build system:
64bit multicore processor, 4GB RAM and 25GB disk space.
Supported 32-bit ARM devices (arm:armv6):
1. Banana Pi (bpi)
2. Raspberry Pi2 (rpi2)
Supported 64-bit ARM devices (arm64:aarch64):
1. NanoPi NEO2 (nanopi-neo2)
2. Orange Pi PC2 (orangepi-pc2)
3. Raspberry Pi3 (rpi3)
Build steps:
# pkg install git
# cd /usr
# git clone https://github.com/opnsense/tools
# cd tools
# make update
# make xtools base kernel packages arm-3G DEVICE=(product-device)
# | Device | defconfig | dtb |
1 | ESPRESSObin | ?? | armada-3720-espressobin.dtb | armada-3720-community.dtb |
2 | MACCHIATObin | ?? | armada-8040-mcbin-single-shot.dtb | armada-8040-mcbin.dtb |
3 | Libre Computer Tritium H5 | libretech_all_h3_cc_h5_defconfig | sun50i-h5-libretech-all-h3-cc.dtb |
4 | Odroid XU3/4 | odroid-xu3_defconfig | exynos5422-odroidxu3.dtb |
6 | NanoPi R1 | nanopi_r1_defconfig | sun8i-h3-nanopi-r1.dtb |
Hi,
sounds very interesting!
Do you know, if your image would work for RPI3, too?
best regards
Dirk
I'd be more than happy to help test! I've got several RPI3 boards gathering dust.Thanks. If it doesn't work, I guess UBLDR_LOADADDR=0x200 on device/rpi3.conf is not correct.
If I get some spare time this week and/or next, I'll test on the RPI3.
Fun to see this old topic is still alive! I think I would also prefer raspi 3 as the "old" image in raspi 1 was vvvveerryyyy slow...Franco's code is already working fine to begin with, just a minor tweaking and it works well.
https://forum.opnsense.org/index.php?topic=6099.msg25545#msg25545
:-D
I think I would also prefer raspi 3 as the "old" image in raspi 1 was vvvveerryyyy slow...Me too! ;)
If espressobin supported by freebsd, it should work with opnsense, just need to add device config and compile.I think I would also prefer raspi 3 as the "old" image in raspi 1 was vvvveerryyyy slow...Me too! ;)
Also very interested of the performance on RPI3...
Of course a working image for Esspresso.bin would be nice!!! ;D ;D ;D
...still dreaming of ducktaping a raspi to my laptop as a firewall/wifi access while traveling. Powering raspi from laptop would be fun, but a small power bank would be acceptable, too :-DCurrenly using RPI2 to run suricata and unboundbl, works great with additional swap file. Still works better than using ipfire or openwrt. More to come with the plugins and update repo. I can see a future of opnsense with wide range of highend (multicore processor + 4GB and above of ram) arm SBC supported.
Currently I use a rather big old box with a wifi stick.
Is it this Aircard:Looks like same model, but different branding, I guess it's ISP branded air card and not generic one. If possible buy a generic unlocked usb modem and can connect using PPP effortlessly.
https://www.hackster.io/beame-io/how-to-use-an-off-the-shelf-4g-usb-module-with-raspberry-pi-c5c30f
...I only have a Telekom Speedstick LTE V (Huawei E3372s -153), any chance to get that working with the raspi 2? :-)
I only have a Telekom Speedstick LTE V (Huawei E3372s -153), any chance to get that working with the raspi 2? :-)
Most Huawei usb modem supported by open source distro, I guess freebsd already has a support for it. Just shove it into usb port and open Interface>WAN>IP Configuration Type>PPP and select the correct modem port.
Good news. I also have SBC, but still not supported by BSD.Looks like a great device with crypto support. Not sure if FreeBSD already have a supported device that has the same hardware. If they do, maybe can port it's uboot into Tritium.
It's a Libre Computer Tritium H5 2GB:
https://libre.computer/2019/02/07/linux-4-19-lts-images-for-tritium/ (https://libre.computer/2019/02/07/linux-4-19-lts-images-for-tritium/)
It only have support on Ubuntu, Debian and Armbian for now.
Can confirm this Huawei works, I created a PPP interface with cuaU0.1 and added Z as "init String" under Advanced Options, assigned it to WAN and works like a charm... Will test with the raspi soonish. :-)That's great. Huawei modem always have a good support from open source community. If you have RPI3, try test using that, would like to know how good it will performs.
I'd like to thank nekoprog for the work done with the ARM ports. Very useful and robust now. :)No problem, I'm glad to be able to contribute back. If I have any other SBC with 64bit arch, I will help with porting and testing.
Next step is actually the long-promised BPI image and then come 20.1 we'll have to see what we can do when i386 is being dropped from our supported list...
Cheers,
Franco
Good news. I also have SBC, but still not supported by BSD.Looks like a great device with crypto support. Not sure if FreeBSD already have a supported device that has the same hardware. If they do, maybe can port it's uboot into Tritium.
It's a Libre Computer Tritium H5 2GB:
https://libre.computer/2019/02/07/linux-4-19-lts-images-for-tritium/ (https://libre.computer/2019/02/07/linux-4-19-lts-images-for-tritium/)
It only have support on Ubuntu, Debian and Armbian for now.
PS: I have some raspi 3 here, but no image. ;-)My free hosting server wont allow upload more than 100MB, thus I grab some anon upload service for that image and no SHA256, sorry. Will try reupload using google drive this weekend. What is the model of your odroid? If I have some spare time, I will help with compiling RPI3 and odroid image.
Tried to download the raspi 2 image, but I'm trapped in "Wait 5 sec for download to start" and then nothing happenz... (allowed nearly all scripts for this page, except the Google stuff). Btw, do you have SHA256 for me to verify the download? :)
Many thanks in advance...
According to their wiki they have one supported:It will take some time to test and it may or may not working, but I do my best to try.
https://wiki.freebsd.org/FreeBSD/arm/Allwinner/H5 (https://wiki.freebsd.org/FreeBSD/arm/Allwinner/H5)
https://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=220 (https://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=220)
OPNsense: {
fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
url: "http://neko.progr.am/pieSense/${ABI}/19.1/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
These changes to file is not permanent, will have to edit again if error when checking for updates.
bunzip2: opnsense-openssl-arm-armv6-rpi2.img.xz is not a bzip2 file.
Many thanks, download working now (this time I had to allow Google scripts definitely ;-) )!From your error, looks like your tools don't support xz, try install xz first and extract it with xz -dkv *.xz. How to install xz varies among distros, you need to google that.
Will burn an SDcard and boot asap...
https://wiki.odroid.com/odroid-xu4/odroid-xu4
...but I had a look yesterday evening, apparently no FreeBSD support for this yet. NAS I will do with Ubuntu or Debian.
___
PS: My download gives
sha256sum opnsense-openssl-arm-armv6-rpi2.img.xz
048cf798130084379cfbbff0908cc84ed3c06b6d4ffc0191f8fbe55a477d5471 opnsense-openssl-arm-armv6-rpi2.img.xz
i.e. all lower case characters ;-)
___
PPS: Tried to expand the .xz, but with bunzip2 I getCode: [Select]bunzip2: opnsense-openssl-arm-armv6-rpi2.img.xz is not a bzip2 file.
and Ark (on linux) ends with file sizes much lower than the packed file. Did you use a Windows tool to compress?
tar -xf opnsense-openssl-arm-armv6-rpi2.img.xz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
Strange, xz is installed (xz 5.2.4), but I get:Maybe ;DCode: [Select]tar -xf opnsense-openssl-arm-armv6-rpi2.img.xz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
...never had such problems to burn a raspi image, am I too stupid? :-D
Maybe ;D
Anything necessary to use the whole SD-card?
Which setup do you use for suricata?
...and you figured out the correct boot options for raspi 3 if I understand the link to GIThub correctly? :-DFound the correct address for RPI3 from here (https://github.com/freebsd/crochet/blob/master/board/RaspberryPi3/setup.sh) and add Odroid XU3/XU4 configs too, lets hope Franco approve that PR, and I can test building image for Odroid XU4. ;D
I'd like to thank nekoprog for the work done with the ARM ports. Very useful and robust now. :)
Next step is actually the long-promised BPI image and then come 20.1 we'll have to see what we can do when i386 is being dropped from our supported list...
Cheers,
Franco
Hi, I'm currently compiling images for RPi2/3, Banana Pi and Orange Pi PC2 for OPNsense 19.1.6. Will let you know when the images are ready. :)I'd like to thank nekoprog for the work done with the ARM ports. Very useful and robust now. :)
Next step is actually the long-promised BPI image and then come 20.1 we'll have to see what we can do when i386 is being dropped from our supported list...
Cheers,
Franco
I have a Banana Pi board lying around here, if you are looking for someone to test the new image please let me know.
Regards,
Bobby Thomas
Ok, I managed to disable IDS in my default config.xml which I use for "standard starting setup" (users, unbound, etc.). Some observations:Hi, great that you found the solution, sorry I couldn't help, quite busy lately and got little time to check the forum. RPI3 image is compiling, will let you know when it's ready. RPI2 updates for 19.1.6 is online if you like to update. Just need to edit /usr/local/etc/pkg/repos/OPNsense.conf like I mentioned before.
- Via the HDMI console the output during boot stops at "smsc0: chip..." and after a LONG break you get the login prompt from opnsense. On the serial console you can monitor the whole boot process (starting services etc.) and in the end you get the login prompt as well.
- Without WAN attached I could not reach the GUI with Firefox (60.x ESR 32 bit), as the request to the https GUI timed out. With Konqueror I could reach the GUI and restore my default config.xml. But the Dashbord is significantly impaired in Konqueror (doing fine in FF, however, only with WAN interface up).
The throughput for a single host is nice (WAN is a 10/100 Mbit USB-RJ45), will have to try the config with UMTS-stick and wifi stick soon... :-)
Would be fun to see an image for Raspi 3 with the built-in wifi as WAN.
Hi, I'm currently compiling images for RPi2/3, Banana Pi and Orange Pi PC2 for OPNsense 19.1.6. Will let you know when the images are ready. :)I'd like to thank nekoprog for the work done with the ARM ports. Very useful and robust now. :)
Next step is actually the long-promised BPI image and then come 20.1 we'll have to see what we can do when i386 is being dropped from our supported list...
Cheers,
Franco
I have a Banana Pi board lying around here, if you are looking for someone to test the new image please let me know.
Regards,
Bobby ThomasOk, I managed to disable IDS in my default config.xml which I use for "standard starting setup" (users, unbound, etc.). Some observations:Hi, great that you found the solution, sorry I couldn't help, quite busy lately and got little time to check the forum. RPI3 image is compiling, will let you know when it's ready. RPI2 updates for 19.1.6 is online if you like to update. Just need to edit /usr/local/etc/pkg/repos/OPNsense.conf like I mentioned before.
- Via the HDMI console the output during boot stops at "smsc0: chip..." and after a LONG break you get the login prompt from opnsense. On the serial console you can monitor the whole boot process (starting services etc.) and in the end you get the login prompt as well.
- Without WAN attached I could not reach the GUI with Firefox (60.x ESR 32 bit), as the request to the https GUI timed out. With Konqueror I could reach the GUI and restore my default config.xml. But the Dashbord is significantly impaired in Konqueror (doing fine in FF, however, only with WAN interface up).
The throughput for a single host is nice (WAN is a 10/100 Mbit USB-RJ45), will have to try the config with UMTS-stick and wifi stick soon... :-)
Would be fun to see an image for Raspi 3 with the built-in wifi as WAN.
I see in the list the first version of NEO, which was build on 32bit H3 chip...NEO 2 is build on 64bit H5...I don’t have the device yet and I don’t have coding skills...could I contribute somehow just by buing it and testing your build?Don't buy it yet, because i don't have a working image for it at the moment.
OPNsense on NanoPI R1 works.Nice. Can you share your configs and make a pull request on tools.git so everyone with nanopi r1 can use it?
dd if=OPNsense-##.#.##-[Type]-[Architecture].img of=/dev/daX bs=16k
7 flashes: kernel.img not found
Downloaded raspi 3 image and checked SHA256 on .img (!, not .xz), was OK.Looks promising, want to experiment a little bit? Copy all these files (https://github.com/raspberrypi/firmware/tree/master/boot) into your microsd card, but do not overwrite existing files.
Burned image withCode: [Select]dd if=OPNsense-##.#.##-[Type]-[Architecture].img of=/dev/daX bs=16k
but on boot I get the infamous rainbow screen and green LED blinking seven times, which means:Code: [Select]7 flashes: kernel.img not found
https://elinux.org/R-Pi_Troubleshooting#Green_LED_blinks_in_a_specific_pattern
...tbc...
Hmm, I'm not a GIT-guy (and my local nerd is still sleeping...), how to download all this stuff? 8-)No worries. Try copying these files and boot. One fix at a time and remove older fix before trying other fix.
Have no BSD-machine here currently iirc, tried last fall last time, I guess... busy days... ;-)
OK, fix1 gives me a rainbow screen without green blinking...But it doesn't boot into OPNsense?
Rainbow screen is always "end of story" on raspi. Nothing going further...Thanks for the test. I'll take another look at it. Probably some minor kernel misconfiguration. as long as it boots, there will be a way to proceed.
Fix 1 removed, added the two kernel .img of fix 2 and it actually boots, but after
(secondary_start kernel) from [<00.....
next line is
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) ]---
mmc1 is current device
scanning mmc 1:1...
Device =: unknown device
"Waiting for Ethernet connection...
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-b8-27-....
I tried the config rename, but then I get :It digs deeper. Can you try booting it again with fix 1?Code: [Select]mmc1 is current device
scanning mmc 1:1...
Device =: unknown device
...and then it tries a PXE boot:Code: [Select]"Waiting for Ethernet connection...
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-b8-27-....
...and after some unsuccessful tries I end up with a U-boot prompt.
Regarding the link to fix:cmdline.txt was not included in freebsd rpi-firmware package. i think it's optional, because rpi2 also didn't have it. i'll take another look at it later.
I can open (on a linux machine) only the first partition of the (two) partitions visible on the SD-card, the one called "MSDOSBOOT" and on this partition I see no cmdline.txt
Booting with SHIFT pressed ends at the same error message, I think this works only on NOOBS?
Adding fix 1 (armstub8.bin) ends in rainbow screen. This is a deadend road. Tried again (with the two kernel images), same resultWant to try this fix? https://lists.freebsd.org/pipermail/freebsd-arm/2016-November/015094.html
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
root=/dev/mmcblk0p2
root=/dev/mmcblk0p6
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,6) ]---
OK, one last try:it's hard to debug without the device. i'll try using qemu. might take some time. thanks for the test.
https://lists.freebsd.org/pipermail/freebsd-arm/2016-November/015094.html
- Removed the cmdline.txt added previously
- Copied the uboot.bin and armstub8.bin to the card, config.txt was already correct and booted:
Rainbow screen...
Is it a secret where you are located on our planet?i'm a full-time psychic detective. ;D
sorry misunderstood your question, english is not my native language. i live in south-east asia. no worry, i have setup qemu in my machine, will give it a test soon.
for wishlist, i suggest arm boards with at least 1gb ram, and multicore cpu. lower than that we have to ignore it because it will not work. even with RPI2 specs, it's still considered too slow for advanced use.
current OPNsense uses freebsd 11.2. for now i stop experimenting with arm64 because freebsd simply don't have it working yet. but once OPNsense start using freebsd 12.0, i will help again if needed.
Could be done, will take some time to create new device config for orangepi-pc and test compile. :)for wishlist, i suggest arm boards with at least 1gb ram, and multicore cpu. lower than that we have to ignore it because it will not work. even with RPI2 specs, it's still considered too slow for advanced use.
Please add the two following as they fit to your suggestions (multicore cpu & 1gb of ram) and listed here: https://github.com/HardenedBSD/hardenedbsd-ports/blob/master/sysutils/Makefile
- orangepi-pc (h3 quad core, 1gb ram, http://linux-sunxi.org/Orange_Pi_PC)
- orangepi-pc2 (h5 quad core, arm64, 1gb ram, http://linux-sunxi.org/Orange_Pi_PC_2)current OPNsense uses freebsd 11.2. for now i stop experimenting with arm64 because freebsd simply don't have it working yet. but once OPNsense start using freebsd 12.0, i will help again if needed.
Could you consider creating a image for the orangepi-pc (as it's supported by freebsd 11.2 and isn't a arm64). I like to test the image and give report! :D (I would really like to do it myself but have insufficient infrastructure: metered slow internet and weak cpu)
I've taken delivery of a NanoPi R1, which image should I be using?Currenly we have a huge code changes for compiling arm device. Will have to check again if nanopi-r1 is supported on freebsd 11.2 or not.
I've had OpenWRT running on it after writing the image to an mmc, but not having any joy with Opnsense, I keep seeing checksum error.
I've taken delivery of a NanoPi R1, which image should I be using?
I've had OpenWRT running on it after writing the image to an mmc, but not having any joy with Opnsense, I keep seeing checksum error.
You can try https://people.freebsd.org/~ganbold/OPNsense-201903201231-OpenSSL-arm-armv7-nanopi-r1.img.xz (https://people.freebsd.org/~ganbold/OPNsense-201903201231-OpenSSL-arm-armv7-nanopi-r1.img.xz)
You can try https://people.freebsd.org/~ganbold/OPNsense-201903201231-OpenSSL-arm-armv7-nanopi-r1.img.xz
Not for me sadly, awg0 works fine as LAN or WAN, but ue0 does not work as either LAN or WAN, rather odd as I can see it when I netscan, and it has the correct address, but I cannot ping to it or ping from it to any client. If I reverse the assignments then LAN works but WAN doesn't. Any ideas?
And that fixed it... :)
Now just the wifi to sort out.
Long story short, the image for RPI-2 is here https://pkg.opnsense.org/FreeBSD:11:armv6/19.1/OPNsense-19.1-test-OpenSSL-arm-armv6-RPI2.img.bz2 and there might be an update before 19.7 but we have no plans to make 32-bit arm officially supported with rolling binary updates.
There's tools.git for everyone who wants to build a certain ARM device:
https://github.com/opnsense/tools#cross-building-for-other-architecures
Cheers,
Franco
There is no workable RPI3 support in HardenedBSD 11. We can add it when we are on HardenedBSD 12.
Cheers,
Franco
I'm waiting already a couple of years... one more... one less isn't that hard :P
But even with a usb network card the raspberry will still be the shitiest thing for networking (all 4 usb and the internal mac shared in one(!) physical usb hub). For i/o - specially for network this is probably the worst case design flaw. Even a $10 orange pi one with a allwinner h3 is kicking the raspberries away in terms of network throughput simply because the ethernet and usb port's are not shared. Sadly it looks like there is no future for the h3 boards with opnsense :(
check out nanopi-r1, RPI0,1,2,3 is not a really for router/firewall.
Good news!
https://cdn.shopify.com/s/files/1/1560/1473/files/Inside_Raspberry_Pi_4.pdf?2142
...but how long will it take till the support will reach BSD? :-(
I have ordered this one and I should expect it by this week or next. Since RPI 4 is here with better Specs (Cortex A72 ARM-V8, Gigabit Ethernet, LPDDR4, USB3, Wifi AC) this should be ideal to run OPNsense and FreeBSD. Can we expect some development for this board soon?
QuoteI have ordered this one and I should expect it by this week or next. Since RPI 4 is here with better Specs (Cortex A72 ARM-V8, Gigabit Ethernet, LPDDR4, USB3, Wifi AC) this should be ideal to run OPNsense and FreeBSD. Can we expect some development for this board soon?
Have a look at raspi 3, there is no working BSD-sense image yet, as the hardware is not really supported by the OS yet. Assume the same to happen for raspi 4...
Hi! Has there been any progress on the espressobin? I've got one I'd be happy to test with.espressobin is using aarch64, right now opnsense is using 11.2, not yet supported arm64 device, but rest assured you can hack your way if using freebsd12 and replace *.dtb to something like this armada-3720-espressobin.dtb | armada-3720-community.dtb
Thanks!
...
Wishlist (Needs uboot slave file in ports (https://github.com/HardenedBSD/hardenedbsd-ports/blob/master/sysutils/Makefile) to make it work)...
# Device defconfig dtb 1 ESPRESSObin ?? armada-3720-espressobin.dtb | armada-3720-community.dtb
Hello,
I am new to opnsense forum but not new to the software on x86.
I want to know how can I port opnsense to Armv7 and aarch64 boards? I have good knowledge in linux world but slowly moving to bsd too.
If there is any guide or documentation for porting freebsd or specifically opnsense then I would love to contribute.
Thanks
ARCH?= ${_ARCH}
ARCH?= arm:armv6
DEVICE?= A10
DEVICE?= CLEARFOG
.export MAKE_ARGS_DEV="
CROSS_BINUTILS_PREFIX=/usr/local/arm-gnueabi-freebsd11.2/bin
UBLDR_LOADADDR=0x900000
"
export PRODUCT_TARGET=arm
export PRODUCT_ARCH=armv6
export PRODUCT_WANTS="arm-gnueabi-binutils qemu-user-static u-boot-clearfog"
export ARM_FAT_SIZE="32m -b 1m"
export ARM_UBOOT_DIR="/usr/local/share/u-boot/u-boot-clearfog"
arm_install_uboot()
{
arm_unmount
dd if=${ARM_UBOOT_DIR}/u-boot-spl.kwb of=/dev/${DEV} bs=1k seek=8 conv=sync
arm_mount
cp ${ARM_UBOOT_DIR}/boot.scr ${STAGEDIR}/boot/msdos
cp -p ${STAGEDIR}/boot/ubldr.bin ${STAGEDIR}/boot/msdos
ln ${STAGEDIR}/boot/dtb/clearfog.dtb ${STAGEDIR}/boot/dtb/armada-388-clearfog.dtb
}
#pkg install git qemu-user-static arm-gnueabi-binutils u-boot-clearfog
/usr/tools #make base
===> usr.bin/clang/clang (all)
cc1_main.o: In function `cc1_main(llvm::ArrayRef<char const*>, char const*, void*)':
cc1_main.cpp:(.text._Z8cc1_mainN4llvm8ArrayRefIPKcEES2_Pv+0x45c): relocation truncated to fit: R_ARM_CALL against symbol `llvm::install_fatal_error_handler(void (*)(void*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool), void*)' defined in .text._ZN4llvm27install_fatal_error_handlerEPFvPvRKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbES0_ section in /usr/obj/arm.armv6/usr/src/lib/clang/libllvm/libllvm.a(ErrorHandling.o)
/usr/tools #make xtools
/usr/tools # make base
/usr/tools #make packages
/usr/tools #make base
.Hi,
I have a ClearFog Base which is based on an armv7 SOC, but it can run armv6. I've gotten FreeBSD 11.2, 12.0 and 12.1 to boot and run on it with both ethernet ports working properly.
I've followed nekoprog's instructions https://github.com/nekoprog/pieSense/blob/master/README.md (https://github.com/nekoprog/pieSense/blob/master/README.md) with appropriate modifications.
In the /usr/tools/Makefile the lineCode: [Select]ARCH?= ${_ARCH}
was replaced byCode: [Select]ARCH?= arm:armv6
and the lineCode: [Select]DEVICE?= A10
was replaced byCode: [Select]DEVICE?= CLEARFOG
.
The file /usr/tools/device/CLEARFOG.conf was created and modeled after BANANAPI.conf:Code: [Select]export MAKE_ARGS_DEV="
CROSS_BINUTILS_PREFIX=/usr/local/arm-gnueabi-freebsd11.2/bin
UBLDR_LOADADDR=0x900000
"
export PRODUCT_TARGET=arm
export PRODUCT_ARCH=armv6
export PRODUCT_WANTS="arm-gnueabi-binutils qemu-user-static u-boot-clearfog"
export ARM_FAT_SIZE="32m -b 1m"
export ARM_UBOOT_DIR="/usr/local/share/u-boot/u-boot-clearfog"
arm_install_uboot()
{
arm_unmount
dd if=${ARM_UBOOT_DIR}/u-boot-spl.kwb of=/dev/${DEV} bs=1k seek=8 conv=sync
arm_mount
cp ${ARM_UBOOT_DIR}/boot.scr ${STAGEDIR}/boot/msdos
cp -p ${STAGEDIR}/boot/ubldr.bin ${STAGEDIR}/boot/msdos
ln ${STAGEDIR}/boot/dtb/clearfog.dtb ${STAGEDIR}/boot/dtb/armada-388-clearfog.dtb
}Code: [Select]#pkg install git qemu-user-static arm-gnueabi-binutils u-boot-clearfog
was invoked and completed successfully.
WhenCode: [Select]/usr/tools #make base
is executed, the computer works for quite a while until the build fails with a relocation overflow. The first sign of trouble isCode: [Select]===> usr.bin/clang/clang (all)
cc1_main.o: In function `cc1_main(llvm::ArrayRef<char const*>, char const*, void*)':
cc1_main.cpp:(.text._Z8cc1_mainN4llvm8ArrayRefIPKcEES2_Pv+0x45c): relocation truncated to fit: R_ARM_CALL against symbol `llvm::install_fatal_error_handler(void (*)(void*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool), void*)' defined in .text._ZN4llvm27install_fatal_error_handlerEPFvPvRKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEEbES0_ section in /usr/obj/arm.armv6/usr/src/lib/clang/libllvm/libllvm.a(ErrorHandling.o)
This problem looks like the same issue reported and supposedly solved about 11 months ago https://github.com/opnsense/tools/issues/113 (https://github.com/opnsense/tools/issues/113)
RunningCode: [Select]/usr/tools #make xtools
beforeCode: [Select]/usr/tools # make base
doesn't solve the problem. And after building xtools, runningCode: [Select]/usr/tools #make packages
fails in the same place in the same way asCode: [Select]/usr/tools #make base
.
Was the fix that was implemented in tools last December propagated to the current version at https://github.com/opnsense/tools (https://github.com/opnsense/tools)?
make STEP DEVICE=CLEARFOG
This repo has been archived and only works on OPNsense 18.01 where building for arm is not yet supported.
Hi nekoprog,pieSense repo has been archived, it's not associated to OPNsense and I use it in the past to test for RPI2 build. Current OPNsense/tools (https://github.com/opnsense/tools) config for arm is more robust, just need to add kernel and device configs.
Thanks for the prompt reply. The version of the host FreeBSD was 12.0. I'm downloading 11.2 right now so it can be installed and used to cross build OPNsense for arm.QuoteThis repo has been archived and only works on OPNsense 18.01 where building for arm is not yet supported.
Could you elaborate on that? Where should tools be downloaded from to enable a successful build for armv6? From the console output, it looks like it was trying to build OPNsense 19.7.
dgktkr
Another question: Where does one specify KERNCONF for the kernel build of the target SOC, in my case: /usr/src/sys/arm/conf/ARMADA38X? For bananapi it seemed to be specified in older versions of BANANAPI.conf as KERNEL=ALLWINNER https://github.com/opnsense/src/blob/8d1a9170bd4d9d50ffeecc2c8366ec34b8ebdb02/release/arm/BANANAPI.conf#L6-L18 (https://github.com/opnsense/src/blob/8d1a9170bd4d9d50ffeecc2c8366ec34b8ebdb02/release/arm/BANANAPI.conf#L6-L18).Can you confirm the kernel type? This should be change at https://github.com/opnsense/tools/tree/master/config/19.7 and you need to create new kernel config file, use SMP-BANANAPI for example and rename it to SMP-CLEARFOG and change include ALLWINNER to include ARMADA38X maybe? And ident SMP-BANANAPI to ident SMP-CLEARFOG.
dgktkr
SYSTEM_COMPILER: Determined that CC=cc matches the source tree. Not bootstrapping a cross-compiler.
Hi,Just ignore it because we set the target arch on device config. If sets are listed here "ls /usr/local/opnsense/build/19.7/armv6/sets", then it's a success. Proceed with next make step.
When using FreeBSD 11.2 as the host, make base succeeds, but I'm wondering about the compiles. The build output to the console shows the messageCode: [Select]SYSTEM_COMPILER: Determined that CC=cc matches the source tree. Not bootstrapping a cross-compiler.
Is code being cross-compiled? If not, is there some environment variable that has to be set so that cross-compiling is done?
dgktkr
make -j4 packages DEVICE=CLEARFOG
errors out after many hours. If the command is repeated, it errors out in a few seconds. Taking out the -j4 option gets farther, but it runs into an error I've made (leaving out suricata as well as suricata-devel). I'll fix that and try again.make arm-3G DEVICE=CLEARFOG
ln: /usr/obj/usr/tools/config/19.7/OpenSSL:armv6/boot/dtb/clearfog.dtb: No such file or directory
Hi nekoprog,By default, "make" is running with how many CPUs you have from the output of "sysctl kern.smp.cpus".
Base and kernel for ClearFog have been built successfully thanks to your tips. The corresponding tgz files show up in /usr/local/opnsense/build/19.7/armv6/sets.
The packages buildCode: [Select]make -j4 packages DEVICE=CLEARFOG
errors out after many hours. If the command is repeated, it errors out in a few seconds. Taking out the -j4 option gets farther, but it runs into an error I've made (leaving out suricata as well as suricata-devel). I'll fix that and try again.
dgktkr
Hi,Need to look further into defconfig or into kernelconf, maybe the port is not loaded on boot. Got full log?
i think it better to discuss in this thread.
after some start problems, i got opnsense booting on the armada 385 SoC (Netgate SG3100).
But i am not able to type anything in the serial console, and their are no network ports discoverd :-(
any ideas?
Greets,
René
After the suggestions by nekoprog and franco were followed, the packages target was successfully built.You need to copy .dtb into kernel.tgz (look for /boot/dtb, create directory if not exist) in case FreeBSD does not include it during "make kernel". Do not copy into STAGEDIR (/usr/obj/usr/tools/config/19.7/OpenSSL:armv6), files will be replaces with base.tgz and kernel.tgz upon running "make arm".
Now the problem is when building the arm imageCode: [Select]make arm-3G DEVICE=CLEARFOG
the build errors out complainingCode: [Select]ln: /usr/obj/usr/tools/config/19.7/OpenSSL:armv6/boot/dtb/clearfog.dtb: No such file or directory
even though I put a valid clearfog.dtb there before the build. So where do I put a valid dtb file (or valid dts file if that's what is required) so that the build finds it?
dgktkr
Hi Nekoprog,Have you tried compiling with GENERIC kernel then copy all DTB into /boot/msdos/dtb?
i attached the output of the boot sequence.
It seems, that the kernel drivers for the Marvell switch and interfaces are missing.
i found them in the freebsd source, but dont know how to add them to the build procedure.
i used the default ARMADA-38X kernel config for my build, and put the prebuilt dtb files from the running pfsense image into my arm image. (still wondering this works ^^)
Kind regards,
René
(http://wiki.friendlyarm.com/wiki/images/f/fb/NanoPi_R1S-case1.jpg)
(http://wiki.friendlyarm.com/wiki/images/3/32/NanoPi_R1S-H5-layout.jpg)
(http://wiki.friendlyarm.com/wiki/images/6/6d/Matrix-USB2UART_nanopi_R1S-H3.jpg)
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1S-H5 (http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1S-H5)
Was there ever a opnsense device for less than $25 which does the job? This could be the first one! ;D
Hello, i have problem with running OPNsense on RPI2. Somehow, after installing img from opening post on SD card, RPI2 boots, but after loading kernel screen goes black and device is unresponsive, ETH not working too.These two are different problem entirely.
Last msg before black screen is something like:
Booting [/boot/kernel/kernel]...
/boot/dtb/bcm2836-rpi-2-b.dtb size=0x385e
Loaded DTB from file 'bcm2836-rpi-2-b.dtb'.
Kernel entry at 0x200180...
Kernel args: (null)
I tried 2 different SD cards (which both work normally on raspbian).
After that tried to compile myself but on FreeBSD 11.2 amd64 i get errors when # make base DEVICE=RPI2 so compiling is unsuccessful... Something about [clang], already removed VM so can't check. Any idea?
(http://wiki.friendlyarm.com/wiki/images/f/fb/NanoPi_R1S-case1.jpg)
(http://wiki.friendlyarm.com/wiki/images/3/32/NanoPi_R1S-H5-layout.jpg)
(http://wiki.friendlyarm.com/wiki/images/6/6d/Matrix-USB2UART_nanopi_R1S-H3.jpg)
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1S-H5 (http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1S-H5)
Was there ever a opnsense device for less than $25 which does the job? This could be the first one! ;D
I prefer at least 1GB of RAM to make it worth the time. Currently I'm working on NanoPi R1 device patch, let's hope FreeBSD accept it.
pfsense works on this device:
https://www.netgate.com/solutions/pfsense/sg-1100.html
As for OPNsense, you can try my image (it is not official one):
https://people.freebsd.org/~ganbold/OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz
It works for me on espressobin.
setenv fdt_name 'efi/boot/armada-3720-espressobin.dtb'
setenv image_name 'efi/boot/bootaa64.efi'
setenv bootmmc 'mmc dev 0; fatload mmc 0:1 $kernel_addr $image_name;fatload mmc 0:1 $fdt_addr $fdt_name; bootefi $kernel_addr $fdt_addr'
run bootmmc
setenv bootcmd 'mmc dev 0; fatload mmc 0:1 $kernel_addr $image_name;fatload mmc 0:1 $fdt_addr $fdt_name; bootefi $kernel_addr $fdt_addr'
Startup error in /boot/lua/loader.lua:
LUA ERROR: cannot open /boot/lua/loader.lua: invalid argument.
can't load 'kernel'
set currdev=disk0p2
boot
Long story short, the image for RPI-2 is here https://pkg.opnsense.org/FreeBSD:11:armv6/19.1/OPNsense-19.1-test-OpenSSL-arm-armv6-RPI2.img.bz2
(http://wiki.friendlyarm.com/wiki/images/f/fb/NanoPi_R1S-case1.jpg)
(http://wiki.friendlyarm.com/wiki/images/3/32/NanoPi_R1S-H5-layout.jpg)
(http://wiki.friendlyarm.com/wiki/images/6/6d/Matrix-USB2UART_nanopi_R1S-H3.jpg)
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1S-H5 (http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1S-H5)
Was there ever a opnsense device for less than $25 which does the job? This could be the first one! ;D
I prefer at least 1GB of RAM to make it worth the time. Currently I'm working on NanoPi R1 device patch, let's hope FreeBSD accept it.
Then you will like this one more
(https://www.cnx-software.com/wp-content/uploads/2020/01/NanoPi-R2S-Dual-Gigabit-Ethernet-SBC.jpg)
Same same but different. Not only 1GB of ram but also two times true(r)(c)(tm) gigabit Ethernet but and a rk3328 soc
Hi,
for those of you who managed to build an aarch64 image (e.g. for the NanoPi R1): Which FreeBSD version did you use for compiling and which OPNSense version (20.1 or 20.7) did you build? I tried to build 20.1 using FreeBSD 12.1 and failed.
(http://wiki.friendlyarm.com/wiki/images/f/fb/NanoPi_R1S-case1.jpg)
(http://wiki.friendlyarm.com/wiki/images/3/32/NanoPi_R1S-H5-layout.jpg)
(http://wiki.friendlyarm.com/wiki/images/6/6d/Matrix-USB2UART_nanopi_R1S-H3.jpg)
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1S-H5 (http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1S-H5)
looking forward to hear any news from your R2S board.
I really want to
Was there ever a opnsense device for less than $25 which does the job? This could be the first one! ;D
I prefer at least 1GB of RAM to make it worth the time. Currently I'm working on NanoPi R1 device patch, let's hope FreeBSD accept it.
Then you will like this one more
(https://www.cnx-software.com/wp-content/uploads/2020/01/NanoPi-R2S-Dual-Gigabit-Ethernet-SBC.jpg)
Same same but different. Not only 1GB of ram but also two times true(r)(c)(tm) gigabit Ethernet but and a rk3328 soc
I will have a NanoPi-R2S in few days. and try to install freebsd first. the try opensense.
"arm support has been postponed to the 30.7 release"
Can you advice how I can contribute?come join us at opnsense/tools (https://github.com/opnsense/tools) more help needed there on making a generic arm32 arm64 kernel config, but i will not do anything for now, will wait for 20.7 release
I have rpi3b+
Khadas edge-v - rk3399 - aarch64 already have freebsd image for it.
Bpi-R2 armvh7 freebsd support is wip.
Can you help with simple tutorial with steps? Will be very helpful to try.
Thanks for such a great tool.
"arm support has been postponed to the 30.7 release";D
:-X
...many things that were idealistic in the beginning have turned political over time... :-[it's hard to keep things working for arm 32bit, since they have too many architecture and different kernel modules. but we can have a generic build for arm64 later.
Can you advice how I can contribute?come join us at opnsense/tools (https://github.com/opnsense/tools) more help needed there on making a generic arm32 arm64 kernel config, but i will not do anything for now, will wait for 20.7 release
I have rpi3b+
Khadas edge-v - rk3399 - aarch64 already have freebsd image for it.
Bpi-R2 armvh7 freebsd support is wip.
Can you help with simple tutorial with steps? Will be very helpful to try.
Thanks for such a great tool."arm support has been postponed to the 30.7 release";D
:-X...many things that were idealistic in the beginning have turned political over time... :-[it's hard to keep things working for arm 32bit, since they have too many architecture and different kernel modules. but we can have a generic build for arm64 later.
currently i'm targetting this device http://www.banana-pi.org/r64.html
feel free to use my tools (https://github.com/nekoprog/tools) if you want to test 20.7 build using freebsd 12.1
come join us at opnsense/tools (https://github.com/opnsense/tools) more help needed there on making a generic arm32 arm64 kernel config, but i will not do anything for now, will wait for 20.7 release
Do you mean 30.7 ?
It is a git page. I will follow the work there.it's hard to keep things working for arm 32bit, since they have too many architecture and different kernel modules. but we can have a generic build for arm64 later.
currently i'm targetting this device http://www.banana-pi.org/r64.html
feel free to use my tools (https://github.com/nekoprog/tools) if you want to test 20.7 build using freebsd 12.1
if you have any problem, you can open issue at my repo, we will discuss it there
pfsense works on this device:
https://www.netgate.com/solutions/pfsense/sg-1100.html
As for OPNsense, you can try my image (it is not official one):
https://people.freebsd.org/~ganbold/OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz
It works for me on espressobin.
2020-06-22 15:40:24 (5.81 MB/s) - Connection closed at byte 20316160. Retrying.
--2020-06-22 15:40:24-- (try: 6) https://people.freebsd.org/~ganbold/OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz
Connecting to people.freebsd.org (people.freebsd.org)|96.47.72.75|:443... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 398789268 (380M), 378473108 (361M) remaining [application/octet-stream]
Saving to: ‘OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz.2’
OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz.2 15%[+++++++=============> ] 59.58M 12.6MB/s in 3.9s
2020-06-22 15:40:28 (10.2 MB/s) - Connection closed at byte 62472192. Retrying.
BTW: something seems to be preventing download of https://people.freebsd.org/~ganbold/OPNsense-201912171639-OpenSSL-arm-aarch64.img.xzI was getting the same error but with infinite retries it completed 35 minutes or so:
wget --tries=0 https://people.freebsd.org/\~ganbold/OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz
crw-rw-rw- 1 root wheel 18, 2 14 Jul 08:27 /dev/tty.SLAB_USBtoUART
crw-rw-rw- 1 root wheel 18, 5 14 Jul 08:27 /dev/cu.usbserial-0001
crw-rw-rw- 1 root wheel 18, 4 14 Jul 08:27 /dev/tty.usbserial-0001
screen /dev/tty.SLAB_USBtoUART 152000 8N1
���������m��������������R�������������ϓɖegr��γt�����������������������������������������������������������������������?���������������������������������������������������������������������������������������������������B��1���6���[���o�2��?����y�O����������������������������������������������������������������������������������������~�������������������������}�������������������_�ᾟ��������������Y�����������������y����������������������������
Can somebody smarter than me tell how to use serial console with NanoPi R2S?
I use macos Catalina and USB to TTL dongle (CP2102) from ebay. I installed drivers from https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers
and get following devices show up:Code: [Select]crw-rw-rw- 1 root wheel 18, 2 14 Jul 08:27 /dev/tty.SLAB_USBtoUART
crw-rw-rw- 1 root wheel 18, 5 14 Jul 08:27 /dev/cu.usbserial-0001
crw-rw-rw- 1 root wheel 18, 4 14 Jul 08:27 /dev/tty.usbserial-0001
When i try to connect to any of them with screen:Code: [Select]screen /dev/tty.SLAB_USBtoUART 152000 8N1
Gibberish shows up:Code: [Select]���������m��������������R�������������ϓɖegr��γt�����������������������������������������������������������������������?���������������������������������������������������������������������������������������������������B��1���6���[���o�2��?����y�O����������������������������������������������������������������������������������������~�������������������������}�������������������_�ᾟ��������������Y�����������������y����������������������������
Edit: turns out the USB to UART I have is CP2102 based which cannot do baud rates higher than 921600 and friendly elec's wiki talks about using 1500000 baud rate. Guess i need a different dongle.
@spikerguyHello,
I would like to contribute to porting to NanoPiR2S. I managed so far:
- Run Ganbold's freebsd image - 1 interface comes up - info posted above
- Run Armbian/FriendlyWrt
- Cross Compile various forks of Opnsense from github - so I have at this point cross compiling workflow working - wilmardo's looks promising but it fails when building image due to missing arm_install_uboot
- Got myself some other usb to uart dongles: one on PL2303HX, other on CP2104
- Reviewed various videos about u-boot on YT, i get the gist of it but got lost on details what is really required when porting. I have no idea what is uboot missing in here to get it running on R2S: https://github.com/opnsense/tools/compare/master...wilmardo:nanopi-r2s#diff-bd6443d009b4e5cb4bb4487c64127585
- I have looked at Armbian boot directory for some clues
- I have examined Armbian images with kpartx to get some ideas
I was thinking about either building upstream u-boot, or getting u-boot image from Armbian and sticking it all together. But still my understanding of u-boot is quite poor.
And then we have a problem with 1 ethernet coming up and the usb one being down.
If someone could point me in the right direction on the above, then maybe I can make some progress.
uname -a
FreeBSD generic 13.0-CURRENT FreeBSD 13.0-CURRENT #98 r357147:357497M: Fri Feb 7 14:30:10 +08 2020 tsgan@
beastie.mstride.com:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64
Nano pi have recently released a "proper" dual Ethernet ( one onboard RTL8211E and one via PCIe R8111H )
https://wiki.friendlyarm.com/wiki/index.php/NanoPi_R4S (https://wiki.friendlyarm.com/wiki/index.php/NanoPi_R4S)
Is it possible to port OPNsense to this??
OPNsense on NanoPI R4S
OPNsense: {
fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
url: "https://ftp.yrzr.tk/opnsense/${ABI}/21.1/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/build/21.1/aarch64/images/) for rpi3 (may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/build/21.1/aarch64/images/) for rpi3 (may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
dmesg
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 2013-2019 The HardenedBSD Project.
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.1-RELEASE-p13-HBSD #0 5a4151730(stable/21.1)-dirty: Fri Jan 8 01:33:30 UTC 2021
root@generic:/usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM arm64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
VT(efifb): resolution 656x416
HardenedBSD: initialize and check features (__HardenedBSD_version 1200059 __FreeBSD_version 1201000).
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
MAP 39f47000 mode 2 pages 1
MAP 39f4b000 mode 2 pages 3
MAP 39f4f000 mode 2 pages 4
MAP 3b360000 mode 2 pages 16
MAP 3f100000 mode 1 pages 1
000.000021 [4336] netmap_init netmap: loaded module
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
ofw_clkbus0: <OFW clocks bus> on ofwbus0
clk_fixed0: <Fixed clock> on ofw_clkbus0
clk_fixed1: <Fixed clock> on ofw_clkbus0
regfix0: <Fixed Regulator> on ofwbus0
regfix1: <Fixed Regulator> on ofwbus0
simple_mfd0: <Simple MFD (Multi-Functions Device)> on simplebus0
ofw_clkbus1: <OFW clocks bus> on simple_mfd0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
lintc0: <BCM2836 Interrupt Controller> mem 0x40000000-0x400000ff on simplebus0
intc0: <BCM2835 Interrupt Controller> mem 0x7e00b200-0x7e00b3ff irq 39 on simplebus0
gpio0: <BCM2708/2835 GPIO controller> mem 0x7e200000-0x7e2000b3 irq 7,8 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
generic_timer0: <ARMv7 Generic Timer> irq 1,2,3,4 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000
usb_nop_xceiv0: <USB NOP PHY> on ofwbus0
mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 6 on simplebus0
gpioc0: <GPIO controller> on gpio0
uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e2011ff irq 9 on simplebus0
uart0: console (115200,n,8,1)
spi0: <BCM2708/2835 SPI controller> mem 0x7e204000-0x7e2041ff irq 11 on simplebus0
spibus0: <OFW SPI bus> on spi0
spibus0: <unknown card> at cs 0 mode 0
spibus0: <unknown card> at cs 1 mode 0
iichb0: <BCM2708/2835 BSC controller> mem 0x7e804000-0x7e804fff irq 19 on simplebus0
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x7e980000-0x7e98ffff,0x7e006000-0x7e006fff irq 21,20
usbus0 on bcm283x_dwcotg0
bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007eff irq 23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38 on simpleb0
bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100113,0x7e00a000-0x7e00a023 on simplebus0
bcmrng0: <Broadcom BCM2835 RNG> mem 0x7e104000-0x7e10400f irq 40 on simplebus0
sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 48 on simplebus0
mmc0: <MMC/SD bus> on sdhci_bcm0
fb0: <BCM2835 VT framebuffer driver> on simplebus0
fbd0 on fb0
VT: Replacing driver "efifb" with new "fb".
fb0: 656x416(656x416@0,0) 24bpp
fb0: fbswap: 1, pitch 1968, base 0x3eb33000, screen_size 818688
pmu0: <Performance Monitoring Unit> irq 0 on ofwbus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
bcm2835_cpufreq0: <CPU Frequency Control> on cpu0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
gpioled0: <GPIO LEDs> on ofwbus0
gpioled0: <led0> failed to map pin
gpioled0: <led1> failed to map pin
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
usbus0: 480Mbps High Speed USB v2.0
iicbus0: <OFW I2C bus> on iichb0
iic0: <I2C generic I/O> on iicbus0
ugen0.1: <DWCOTG OTG Root HUB> at usbus0
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
mmcsd0: 16GB <SDHC SL16G 8.0 SN 682835FD MFG 04/2016 by 3 SD> at mmc0 50.0MHz/4bit/65535-block
bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF
uhub0: 1 port with 1 removable, self powered
Release APs...done
CPU 0: ARM Cortex-A53 r0p4 affinity: 0
Trying to mount root from ufs:/dev/ufs/OPNsense [rw]...
Instruction Set Attributes 0 = <CRC32>
Instruction Set Attributes 1 = <>
Processor Features 0 = <AdvSIMD,Float,EL3 32,EL2 32,EL1 32,EL0 32>
Processor Features 1 = <0>
Memory Model Features 0 = <4k Granule,64k Granule,S/NS Mem,MixedEndian,16bit ASID,1TB PA>
Memory Model Features 1 = <>
Memory Model Features 2 = <32b CCIDX,48b VA>
Debug Features 0 = <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v8>
Debug Features 1 = <0>
Auxiliary Features 0 = <0>
Auxiliary Features 1 = <0>
CPU 1: ARM Cortex-A53 r0p4 affinity: 1
CPU 2: ARM Cortex-A53 r0p4 affinity: 2
CPU 3: ARM Cortex-A53 r0p4 affinity: 3
Warning: no time-of-day clock registered, system time will not be set accurately
lo0: link state changed to UP
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
usbconfig
ugen0.1: <DWCOTG OTG Root HUB> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
*** OPNsense.localdomain: OPNsense 21.1_25 (aarch64/OpenSSL) ***
No network interfaces are assigned.
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option: 6
The system will reboot. Do you want to proceed? [y/N]: y
>>> Invoking stop script 'beep'
>>> Invoking stop script 'freebsd'
>>> Invoking stop script 'backup'
>>> Invoking backup script 'captiveportal'
>>> Invoking backup script 'dhcpleases'
>>> Invoking backup script 'duid'
>>> Invoking backup script 'netflow'
>>> Invoking backup script 'rrd'
>>> Invoking stop script 'config'
shutdown: [pid 9305]
Shutdown NOW!
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1
(Thu Jan 7 07:14:48 UTC 2021 root@releng1.nyi.freebsd.org)
Command line arguments: loader.efi
Image base: 0x39e16000
EFI version: 2.80
EFI Firmware: Das U-Boot (rev 8224.4096)
Console: comconsole (0)
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(2,0x01,0,0x10800,0x3ef800)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
[H[J[4;46H uKOS2qsmkfe38kEuXLimP+7XoBiuIt5k[5;46H BMHardenedBSDxfOL9QwvfA6yxGHkNMG[6;46H 2I7ADmw7Mp/P8Y4wjnBFDNKvNzdZa/uu[5
[25;0H[23;4HAutoboot in 2 seconds, hit [Enter] to boot or any other key to stop
[25;0H[23;4HAutoboot in 1 seconds, hit [Enter] to boot or any other key to stop
[25;0H[23;4HAutoboot in 0 seconds, hit [Enter] to boot or any other key to stop
[25;0HLoading kernel...
/boot/kernel/kernel text=0x9857d0 data=0x19b1f0+0x7a3084 syms=[0x8+0x142260+0x8+0x12dbac]
Loading configured modules...
/boot/kernel/pflog.ko text=0xfb0 text=0x830 data=0x10148 syms=[0x8+0x9f0+0x8+0x716]
loading required module 'pf'
/boot/kernel/pf.ko text=0x6061 text=0x2cb90 data=0x10490+0xfd38 syms=[0x8+0x4170+0x8+0x308c]
/boot/kernel/if_enc.ko text=0x1602 text=0x8d0 data=0x10168 syms=[0x8+0xc90+0x8+0xb66]
/boot/kernel/pfsync.ko text=0x2e14 text=0x6ad0 data=0x102e8+0xfd20 syms=[0x8+0x1758+0x8+0x10f0]
/boot/kernel/carp.ko text=0x34c0 text=0x63d0 data=0x10258+0xfdf0 syms=[0x8+0x1980+0x8+0x121f]
/boot/kernel/if_bridge.ko text=0x351e text=0x69a0 data=0x10428+0xfbe0 syms=[0x8+0x1a40+0x8+0x14a3]
loading required module 'bridgestp'
/boot/kernel/bridgestp.ko text=0xe44 text=0x402c data=0x170 data=0x158+0x28 syms=[0x8+0xb10+0x8+0x690]
/boot/kernel/if_tap.ko text=0x2613 text=0x2b90 data=0x10160+0xff18 syms=[0x8+0x1260+0x8+0xbc4]
/boot/kernel/if_lagg.ko text=0x35c0 text=0x7c30 data=0x10440+0xfbc8 syms=[0x8+0x1a70+0x8+0x1325]
/boot/kernel/if_gre.ko text=0x2458 text=0x4640 data=0x10228+0xfe18 syms=[0x8+0x1668+0x8+0xf17]
/boot/entropy size=0x1000
Using DTB provided by EFI at 0x7ef5000.
EFI framebuffer information:
addr, size 0x3eaf0000, 0x10a800
dimensions 656 x 416
stride 656
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1
(Thu Jan 7 07:14:48 UTC 2021 root@releng1.nyi.freebsd.org)
Command line arguments: loader.efi
Image base: 0x39e17000
EFI version: 2.80
EFI Firmware: Das U-Boot (rev 8224.4096)
Console: comconsole (0)
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x800,0)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x800,0x100)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x10800,0x3ef80)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
[0;37;40m[H[J[9;47H[muKOS2qsmkfe38kEuXLimP+7XoBiuIt5k[10;47HBM[36mHardened[34mBSD[mxfOL9Qwv5
[25;0H[23;4HAutoboot in 0 seconds, hit [Enter] to boot or any other key to stop
[25;0HLoading kernel...
/boot/kernel/kernel text=0x9857d0 data=0x19b1f0+0x7a3084 syms=[0x8+0x142260+0x8+0x12dbac]
Loading configured modules...
/boot/kernel/if_bridge.ko text=0x351e text=0x69a0 data=0x10428+0xfbe0 syms=[0x8+0x1a40+0x8+0]
loading required module 'bridgestp'
/boot/kernel/bridgestp.ko text=0xe44 text=0x402c data=0x170 data=0x158+0x28 syms=[0x8+0xb10+]
/boot/kernel/if_enc.ko text=0x1602 text=0x8d0 data=0x10168 syms=[0x8+0xc90+0x8+0xb66]
/boot/kernel/carp.ko text=0x34c0 text=0x63d0 data=0x10258+0xfdf0 syms=[0x8+0x1980+0x8+0x121f]
/boot/kernel/if_lagg.ko text=0x35c0 text=0x7c30 data=0x10440+0xfbc8 syms=[0x8+0x1a70+0x8+0x1]
/boot/kernel/pfsync.ko text=0x2e14 text=0x6ad0 data=0x102e8+0xfd20 syms=[0x8+0x1758+0x8+0x10]
loading required module 'pf'
/boot/kernel/pf.ko text=0x6061 text=0x2cb90 data=0x10490+0xfd38 syms=[0x8+0x4170+0x8+0x308c]
/boot/kernel/pflog.ko text=0xfb0 text=0x830 data=0x10148 syms=[0x8+0x9f0+0x8+0x716]
/boot/kernel/if_tap.ko text=0x2613 text=0x2b90 data=0x10160+0xff18 syms=[0x8+0x1260+0x8+0xbc]
/boot/entropy size=0x1000
/boot/kernel/if_gre.ko text=0x2458 text=0x4640 data=0x10228+0xfe18 syms=[0x8+0x1668+0x8+0xf1]
Using DTB provided by EFI at 0x7ef6000.
EFI framebuffer information:
addr, size 0x3e536000, 0x6baa80
dimensions 1680 x 1050
stride 1680
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 2013-2019 The HardenedBSD Project.
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.1-RELEASE-p13-HBSD #0 5a4151730(stable/21.1)-dirty: Fri Jan 8 01:33:30 UTC 2021
root@generic:/usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM arm64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
VT(efifb): resolution 1680x1050
HardenedBSD: initialize and check features (__HardenedBSD_version 1200059 __FreeBSD_version .
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
MAP 39f48000 mode 2 pages 1
MAP 39f4c000 mode 2 pages 3
MAP 39f50000 mode 2 pages 4
MAP 3b360000 mode 2 pages 16
MAP 3f100000 mode 1 pages 1
000.000021 [4336] netmap_init netmap: loaded module
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
ofw_clkbus0: <OFW clocks bus> on ofwbus0
clk_fixed0: <Fixed clock> on ofw_clkbus0
clk_fixed1: <Fixed clock> on ofw_clkbus0
regfix0: <Fixed Regulator> on ofwbus0
regfix1: <Fixed Regulator> on ofwbus0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
lintc0: <BCM2836 Interrupt Controller> mem 0x40000000-0x400000ff on simplebus0
intc0: <BCM2835 Interrupt Controller> mem 0x7e00b200-0x7e00b3ff irq 20 on simplebus0
gpio0: <BCM2708/2835 GPIO controller> mem 0x7e200000-0x7e2000b3 irq 23,24 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
generic_timer0: <ARMv7 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000
usb_nop_xceiv0: <USB NOP PHY> on ofwbus0
bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007eff irq 4,5,6,7,8,9,10,11,12,13,14,0
bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100027 on simplebus0
bcmrng0: <Broadcom BCM2835 RNG> mem 0x7e104000-0x7e10400f irq 21 on simplebus0
mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 22 on simplebus0
gpioc0: <GPIO controller> on gpio0
uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e201fff irq 25 on simplebus0
sdhost_bcm0: <Broadcom 2708 SDHOST controller> mem 0x7e202000-0x7e2020ff irq 26 on simplebus0
sdhost_bcm0-slot0: Hardware doesn't specify timeout clock frequency, setting BROKEN_TIMEOUT .
mmc0: <MMC/SD bus> on sdhost_bcm0
spi0: <BCM2708/2835 SPI controller> mem 0x7e204000-0x7e204fff irq 27 on simplebus0
spibus0: <OFW SPI bus> on spi0
spibus0: <unknown card> at cs 0 mode 0
spibus0: <unknown card> at cs 1 mode 0
uart1: <BCM2835 Mini-UART> mem 0x7e215040-0x7e21507f irq 33 on simpuart1: console (115200,n,)
iichb0: <BCM2708/2835 BSC controller> mem 0x7e804000-0x7e804fff irq 40 on simplebus0
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x7e980000-0x7e98ffff0
usbus0 on bcm283x_dwcotg0
sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 49 on simplebus0
mmc1: <MMC/SD bus> on sdhci_bcm0
fb0: <BCM2835 VT framebuffer driver> on simplebus0
fbd0 on fb0
VT: Replacing driver "efifb" with new "fb".
fb0: 1680x1050(1680x1050@0,0) 24bpp
fb0: fbswap: 1, pitch 5040, base 0x3e6e7000, screen_size 5322240
pmu0: <Performance Monitoring Unit> irq 53 on simplebus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
bcm2835_cpufreq0: <CPU Frequency Control> on cpu0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
gpioled0: <GPIO LEDs> on ofwbus0
gpioled0: <led0> failed to map pin
gpioled0: <led1> failed to map pin
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
usbus0: 480Mbps High Speed USB v2.0
ugen0.1: <DWCOTG OTG Root HUB> at usbus0
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
mmcsd0: 16GB <SDHC SL16G 8.0 SN 682835FD MFG 04/2016 by 3 SD> at mmc0 50.0MHz/4bit/65535-blok
iicbus0: <OFW I2C bus> on iichb0
iic0: <I2C generic I/O> on iicbus0
mmc1: No compatible cards found on bus
mbox0: mbox response error
bcm2835_cpufreq0: can't get max voltage
bcm2835_cpufreq0: ARM 600MHz, Core 400MHz, SDRAM 400MHz, Turbo OFF
mbox0: mbox response error
bcm2835_cpufreq0: can't set clock rate (id=3)
mbox0: mbox response error
bcm2835_cpufreq0: can't set clock rate (id=4)
uhub0: 1 port with 1 removable, self powered
ugen0.2: <vendor 0x0424 product 0x9514> at usbus0
uhub1 on uhub0
uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2> on usbus0
uhub1: MTT enabled
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:16:56:a8
ugen0.4: <ASIX Elec. Corp. AX88x72A> at usbus0
ugen0.5: <ASIX Elec. Corp. AX88x72A> at usbus0
ugen0.6: <vendor 0x1a40 USB 2.0 Hub> at usbus0
uhub2 on uhub1
uhub2: <vendor 0x1a40 USB 2.0 Hub, class 9/0, rev 2.00/1.11, addr 6> on usbus0
uhub2: 4 ports with 4 removable, self powered
ugen0.7: <vendor 0x046a product 0x0023> at usbus0
ukbd0 on uhub2
ukbd0: <vendor 0x046a product 0x0023, class 0/0, rev 2.00/2.20, addr 7> on usbus0
kbd1 at ukbd0
ugen0.8: <Primax Kensington Eagle Trackball> at usbus0
Release APs...done
CPU 0: ARM Cortex-A53 r0p4 affinity: 0
Trying to mount root from ufs:/dev/ufs/OPNsense [rw]...
Instruction Set Attributes 0 = <CRC32>
mountroot: waiting for device /dev/ufs/OPNsense...
Instruction Set Attributes 1 = <>
Processor Features 0 = <AdvSIMD,Float,EL3 32,EL2 32,EL1 32,EL0 32>
Processor Features 1 = <0>
Memory Model Features 0 = <4k Granule,64k Granule,S/NS Mem,MixedEndian,16bit ASID,1TB >
Memory Model Features 1 = <>
Memory Model Features 2 = <32b CCIDX,48b VA>
Debug Features 0 = <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v>
Debug Features 1 = <0>
Auxiliary Features 0 = <0>
Auxiliary Features 1 = <0>
CPU 1: ARM Cortex-A53 r0p4 affinity: 1
CPU 2: ARM Cortex-A53 r0p4 affinity: 2
CPU 3: ARM Cortex-A53 r0p4 affinity: 3
Mounting from ufs:/dev/ufs/OPNsense failed with error 19.
Loader variables:
vfs.root.mountfrom=ufs:/dev/ufs/OPNsense
vfs.root.mountfrom.options=rw
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:/dev/cd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot>
root@generic:~ # usbconfig
ugen0.1: <DWCOTG OTG Root HUB> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.2: <vendor 0x0424 product 0x9514> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE)
ugen0.3: <vendor 0x0424 product 0xec00> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ()
ugen0.4: <ASIX Elec. Corp. AX88x72A> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (250)
ugen0.5: <ASIX Elec. Corp. AX88x72A> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (250)
root@generic:~ #
Took the image by @yrzr and copied over from FreeBSD 12.1 ARM the /dtb as well as bcm2710-rpi-3-b.dtb, bcm2710-rpi-3-b-plus.dtb.
Now USB detected but won't mount OPPNsense...Code: [Select]Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1
(Thu Jan 7 07:14:48 UTC 2021 root@releng1.nyi.freebsd.org)
Command line arguments: loader.efi
Image base: 0x39e17000
EFI version: 2.80
EFI Firmware: Das U-Boot (rev 8224.4096)
Console: comconsole (0)
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x800,0)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x800,0x100)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x10800,0x3ef80)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
[0;37;40m[H[J[9;47H[muKOS2qsmkfe38kEuXLimP+7XoBiuIt5k[10;47HBM[36mHardened[34mBSD[mxfOL9Qwv5
[25;0H[23;4HAutoboot in 0 seconds, hit [Enter] to boot or any other key to stop
[25;0HLoading kernel...
/boot/kernel/kernel text=0x9857d0 data=0x19b1f0+0x7a3084 syms=[0x8+0x142260+0x8+0x12dbac]
Loading configured modules...
/boot/kernel/if_bridge.ko text=0x351e text=0x69a0 data=0x10428+0xfbe0 syms=[0x8+0x1a40+0x8+0]
loading required module 'bridgestp'
/boot/kernel/bridgestp.ko text=0xe44 text=0x402c data=0x170 data=0x158+0x28 syms=[0x8+0xb10+]
/boot/kernel/if_enc.ko text=0x1602 text=0x8d0 data=0x10168 syms=[0x8+0xc90+0x8+0xb66]
/boot/kernel/carp.ko text=0x34c0 text=0x63d0 data=0x10258+0xfdf0 syms=[0x8+0x1980+0x8+0x121f]
/boot/kernel/if_lagg.ko text=0x35c0 text=0x7c30 data=0x10440+0xfbc8 syms=[0x8+0x1a70+0x8+0x1]
/boot/kernel/pfsync.ko text=0x2e14 text=0x6ad0 data=0x102e8+0xfd20 syms=[0x8+0x1758+0x8+0x10]
loading required module 'pf'
/boot/kernel/pf.ko text=0x6061 text=0x2cb90 data=0x10490+0xfd38 syms=[0x8+0x4170+0x8+0x308c]
/boot/kernel/pflog.ko text=0xfb0 text=0x830 data=0x10148 syms=[0x8+0x9f0+0x8+0x716]
/boot/kernel/if_tap.ko text=0x2613 text=0x2b90 data=0x10160+0xff18 syms=[0x8+0x1260+0x8+0xbc]
/boot/entropy size=0x1000
/boot/kernel/if_gre.ko text=0x2458 text=0x4640 data=0x10228+0xfe18 syms=[0x8+0x1668+0x8+0xf1]
Using DTB provided by EFI at 0x7ef6000.
EFI framebuffer information:
addr, size 0x3e536000, 0x6baa80
dimensions 1680 x 1050
stride 1680
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 2013-2019 The HardenedBSD Project.
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.1-RELEASE-p13-HBSD #0 5a4151730(stable/21.1)-dirty: Fri Jan 8 01:33:30 UTC 2021
root@generic:/usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM arm64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
VT(efifb): resolution 1680x1050
HardenedBSD: initialize and check features (__HardenedBSD_version 1200059 __FreeBSD_version .
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
MAP 39f48000 mode 2 pages 1
MAP 39f4c000 mode 2 pages 3
MAP 39f50000 mode 2 pages 4
MAP 3b360000 mode 2 pages 16
MAP 3f100000 mode 1 pages 1
000.000021 [4336] netmap_init netmap: loaded module
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
ofw_clkbus0: <OFW clocks bus> on ofwbus0
clk_fixed0: <Fixed clock> on ofw_clkbus0
clk_fixed1: <Fixed clock> on ofw_clkbus0
regfix0: <Fixed Regulator> on ofwbus0
regfix1: <Fixed Regulator> on ofwbus0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
lintc0: <BCM2836 Interrupt Controller> mem 0x40000000-0x400000ff on simplebus0
intc0: <BCM2835 Interrupt Controller> mem 0x7e00b200-0x7e00b3ff irq 20 on simplebus0
gpio0: <BCM2708/2835 GPIO controller> mem 0x7e200000-0x7e2000b3 irq 23,24 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
generic_timer0: <ARMv7 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000
usb_nop_xceiv0: <USB NOP PHY> on ofwbus0
bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007eff irq 4,5,6,7,8,9,10,11,12,13,14,0
bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100027 on simplebus0
bcmrng0: <Broadcom BCM2835 RNG> mem 0x7e104000-0x7e10400f irq 21 on simplebus0
mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 22 on simplebus0
gpioc0: <GPIO controller> on gpio0
uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e201fff irq 25 on simplebus0
sdhost_bcm0: <Broadcom 2708 SDHOST controller> mem 0x7e202000-0x7e2020ff irq 26 on simplebus0
sdhost_bcm0-slot0: Hardware doesn't specify timeout clock frequency, setting BROKEN_TIMEOUT .
mmc0: <MMC/SD bus> on sdhost_bcm0
spi0: <BCM2708/2835 SPI controller> mem 0x7e204000-0x7e204fff irq 27 on simplebus0
spibus0: <OFW SPI bus> on spi0
spibus0: <unknown card> at cs 0 mode 0
spibus0: <unknown card> at cs 1 mode 0
uart1: <BCM2835 Mini-UART> mem 0x7e215040-0x7e21507f irq 33 on simpuart1: console (115200,n,)
iichb0: <BCM2708/2835 BSC controller> mem 0x7e804000-0x7e804fff irq 40 on simplebus0
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x7e980000-0x7e98ffff0
usbus0 on bcm283x_dwcotg0
sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 49 on simplebus0
mmc1: <MMC/SD bus> on sdhci_bcm0
fb0: <BCM2835 VT framebuffer driver> on simplebus0
fbd0 on fb0
VT: Replacing driver "efifb" with new "fb".
fb0: 1680x1050(1680x1050@0,0) 24bpp
fb0: fbswap: 1, pitch 5040, base 0x3e6e7000, screen_size 5322240
pmu0: <Performance Monitoring Unit> irq 53 on simplebus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
bcm2835_cpufreq0: <CPU Frequency Control> on cpu0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
gpioled0: <GPIO LEDs> on ofwbus0
gpioled0: <led0> failed to map pin
gpioled0: <led1> failed to map pin
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
usbus0: 480Mbps High Speed USB v2.0
ugen0.1: <DWCOTG OTG Root HUB> at usbus0
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
mmcsd0: 16GB <SDHC SL16G 8.0 SN 682835FD MFG 04/2016 by 3 SD> at mmc0 50.0MHz/4bit/65535-blok
iicbus0: <OFW I2C bus> on iichb0
iic0: <I2C generic I/O> on iicbus0
mmc1: No compatible cards found on bus
mbox0: mbox response error
bcm2835_cpufreq0: can't get max voltage
bcm2835_cpufreq0: ARM 600MHz, Core 400MHz, SDRAM 400MHz, Turbo OFF
mbox0: mbox response error
bcm2835_cpufreq0: can't set clock rate (id=3)
mbox0: mbox response error
bcm2835_cpufreq0: can't set clock rate (id=4)
uhub0: 1 port with 1 removable, self powered
ugen0.2: <vendor 0x0424 product 0x9514> at usbus0
uhub1 on uhub0
uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2> on usbus0
uhub1: MTT enabled
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:16:56:a8
ugen0.4: <ASIX Elec. Corp. AX88x72A> at usbus0
ugen0.5: <ASIX Elec. Corp. AX88x72A> at usbus0
ugen0.6: <vendor 0x1a40 USB 2.0 Hub> at usbus0
uhub2 on uhub1
uhub2: <vendor 0x1a40 USB 2.0 Hub, class 9/0, rev 2.00/1.11, addr 6> on usbus0
uhub2: 4 ports with 4 removable, self powered
ugen0.7: <vendor 0x046a product 0x0023> at usbus0
ukbd0 on uhub2
ukbd0: <vendor 0x046a product 0x0023, class 0/0, rev 2.00/2.20, addr 7> on usbus0
kbd1 at ukbd0
ugen0.8: <Primax Kensington Eagle Trackball> at usbus0
Release APs...done
CPU 0: ARM Cortex-A53 r0p4 affinity: 0
Trying to mount root from ufs:/dev/ufs/OPNsense [rw]...
Instruction Set Attributes 0 = <CRC32>
mountroot: waiting for device /dev/ufs/OPNsense...
Instruction Set Attributes 1 = <>
Processor Features 0 = <AdvSIMD,Float,EL3 32,EL2 32,EL1 32,EL0 32>
Processor Features 1 = <0>
Memory Model Features 0 = <4k Granule,64k Granule,S/NS Mem,MixedEndian,16bit ASID,1TB >
Memory Model Features 1 = <>
Memory Model Features 2 = <32b CCIDX,48b VA>
Debug Features 0 = <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v>
Debug Features 1 = <0>
Auxiliary Features 0 = <0>
Auxiliary Features 1 = <0>
CPU 1: ARM Cortex-A53 r0p4 affinity: 1
CPU 2: ARM Cortex-A53 r0p4 affinity: 2
CPU 3: ARM Cortex-A53 r0p4 affinity: 3
Mounting from ufs:/dev/ufs/OPNsense failed with error 19.
Loader variables:
vfs.root.mountfrom=ufs:/dev/ufs/OPNsense
vfs.root.mountfrom.options=rw
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:/dev/cd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot>
I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/build/21.1/aarch64/images/) for rpi3 (may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
Hi
Thanks for sharing.
I got lost in this thread about How to build RPi3 image. There's too many forks of codes. Which git/source or git/crochet you actually used to build your image pls ?
I'd like to reuse my RPi3, simply.
Update: my RPi 3b+ does not boot with your test-image and using config_rpi3.txt.
Gets stucked after:
CPU 3: ARM Cortex-A53 r0p4 affinity: 3
BTW: the screenshot shows Cortex-A72 , does that mean you successfully run in on RPi 4 too ?
BTW2: It seem there might be a progress soon:
https://github.com/opnsense/tools/pull/203
Thanks
T.
I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/build/21.1/aarch64/images/) for rpi3 (may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
Edited config.txt and opnsense up and running, but no Interfaces detected, not the built-in RJ45, not the wifi, not the USB2-RJ45. All hardware OK, as everything works as expected with opensuse Leap on the raspi 3b (not 3b+). I tried with raspi 3 config.txt, with 64bit version etc. and added uart=1 to have serial consol over GPIO.
Did anybody get this running?
PS: some infoCode: [Select]dmesg
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 2013-2019 The HardenedBSD Project.
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.1-RELEASE-p13-HBSD #0 5a4151730(stable/21.1)-dirty: Fri Jan 8 01:33:30 UTC 2021
root@generic:/usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM arm64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
VT(efifb): resolution 656x416
HardenedBSD: initialize and check features (__HardenedBSD_version 1200059 __FreeBSD_version 1201000).
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
MAP 39f47000 mode 2 pages 1
MAP 39f4b000 mode 2 pages 3
MAP 39f4f000 mode 2 pages 4
MAP 3b360000 mode 2 pages 16
MAP 3f100000 mode 1 pages 1
000.000021 [4336] netmap_init netmap: loaded module
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
ofw_clkbus0: <OFW clocks bus> on ofwbus0
clk_fixed0: <Fixed clock> on ofw_clkbus0
clk_fixed1: <Fixed clock> on ofw_clkbus0
regfix0: <Fixed Regulator> on ofwbus0
regfix1: <Fixed Regulator> on ofwbus0
simple_mfd0: <Simple MFD (Multi-Functions Device)> on simplebus0
ofw_clkbus1: <OFW clocks bus> on simple_mfd0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
lintc0: <BCM2836 Interrupt Controller> mem 0x40000000-0x400000ff on simplebus0
intc0: <BCM2835 Interrupt Controller> mem 0x7e00b200-0x7e00b3ff irq 39 on simplebus0
gpio0: <BCM2708/2835 GPIO controller> mem 0x7e200000-0x7e2000b3 irq 7,8 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
generic_timer0: <ARMv7 Generic Timer> irq 1,2,3,4 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000
usb_nop_xceiv0: <USB NOP PHY> on ofwbus0
mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 6 on simplebus0
gpioc0: <GPIO controller> on gpio0
uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e2011ff irq 9 on simplebus0
uart0: console (115200,n,8,1)
spi0: <BCM2708/2835 SPI controller> mem 0x7e204000-0x7e2041ff irq 11 on simplebus0
spibus0: <OFW SPI bus> on spi0
spibus0: <unknown card> at cs 0 mode 0
spibus0: <unknown card> at cs 1 mode 0
iichb0: <BCM2708/2835 BSC controller> mem 0x7e804000-0x7e804fff irq 19 on simplebus0
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x7e980000-0x7e98ffff,0x7e006000-0x7e006fff irq 21,20
usbus0 on bcm283x_dwcotg0
bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007eff irq 23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38 on simpleb0
bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100113,0x7e00a000-0x7e00a023 on simplebus0
bcmrng0: <Broadcom BCM2835 RNG> mem 0x7e104000-0x7e10400f irq 40 on simplebus0
sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 48 on simplebus0
mmc0: <MMC/SD bus> on sdhci_bcm0
fb0: <BCM2835 VT framebuffer driver> on simplebus0
fbd0 on fb0
VT: Replacing driver "efifb" with new "fb".
fb0: 656x416(656x416@0,0) 24bpp
fb0: fbswap: 1, pitch 1968, base 0x3eb33000, screen_size 818688
pmu0: <Performance Monitoring Unit> irq 0 on ofwbus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
bcm2835_cpufreq0: <CPU Frequency Control> on cpu0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
gpioled0: <GPIO LEDs> on ofwbus0
gpioled0: <led0> failed to map pin
gpioled0: <led1> failed to map pin
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
usbus0: 480Mbps High Speed USB v2.0
iicbus0: <OFW I2C bus> on iichb0
iic0: <I2C generic I/O> on iicbus0
ugen0.1: <DWCOTG OTG Root HUB> at usbus0
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
mmcsd0: 16GB <SDHC SL16G 8.0 SN 682835FD MFG 04/2016 by 3 SD> at mmc0 50.0MHz/4bit/65535-block
bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF
uhub0: 1 port with 1 removable, self powered
Release APs...done
CPU 0: ARM Cortex-A53 r0p4 affinity: 0
Trying to mount root from ufs:/dev/ufs/OPNsense [rw]...
Instruction Set Attributes 0 = <CRC32>
Instruction Set Attributes 1 = <>
Processor Features 0 = <AdvSIMD,Float,EL3 32,EL2 32,EL1 32,EL0 32>
Processor Features 1 = <0>
Memory Model Features 0 = <4k Granule,64k Granule,S/NS Mem,MixedEndian,16bit ASID,1TB PA>
Memory Model Features 1 = <>
Memory Model Features 2 = <32b CCIDX,48b VA>
Debug Features 0 = <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v8>
Debug Features 1 = <0>
Auxiliary Features 0 = <0>
Auxiliary Features 1 = <0>
CPU 1: ARM Cortex-A53 r0p4 affinity: 1
CPU 2: ARM Cortex-A53 r0p4 affinity: 2
CPU 3: ARM Cortex-A53 r0p4 affinity: 3
Warning: no time-of-day clock registered, system time will not be set accurately
lo0: link state changed to UP
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
andCode: [Select]usbconfig
ugen0.1: <DWCOTG OTG Root HUB> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
Fun fact: If you choose "reboot" the install never comes back (tried about 20 times), but stops before bootingCode: [Select]*** OPNsense.localdomain: OPNsense 21.1_25 (aarch64/OpenSSL) ***
No network interfaces are assigned.
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option: 6
The system will reboot. Do you want to proceed? [y/N]: y
>>> Invoking stop script 'beep'
>>> Invoking stop script 'freebsd'
>>> Invoking stop script 'backup'
>>> Invoking backup script 'captiveportal'
>>> Invoking backup script 'dhcpleases'
>>> Invoking backup script 'duid'
>>> Invoking backup script 'netflow'
>>> Invoking backup script 'rrd'
>>> Invoking stop script 'config'
shutdown: [pid 9305]
Shutdown NOW!
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1
(Thu Jan 7 07:14:48 UTC 2021 root@releng1.nyi.freebsd.org)
Command line arguments: loader.efi
Image base: 0x39e16000
EFI version: 2.80
EFI Firmware: Das U-Boot (rev 8224.4096)
Console: comconsole (0)
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(2,0x01,0,0x10800,0x3ef800)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
[H[J[4;46H uKOS2qsmkfe38kEuXLimP+7XoBiuIt5k[5;46H BMHardenedBSDxfOL9QwvfA6yxGHkNMG[6;46H 2I7ADmw7Mp/P8Y4wjnBFDNKvNzdZa/uu[5
[25;0H[23;4HAutoboot in 2 seconds, hit [Enter] to boot or any other key to stop
[25;0H[23;4HAutoboot in 1 seconds, hit [Enter] to boot or any other key to stop
[25;0H[23;4HAutoboot in 0 seconds, hit [Enter] to boot or any other key to stop
[25;0HLoading kernel...
/boot/kernel/kernel text=0x9857d0 data=0x19b1f0+0x7a3084 syms=[0x8+0x142260+0x8+0x12dbac]
Loading configured modules...
/boot/kernel/pflog.ko text=0xfb0 text=0x830 data=0x10148 syms=[0x8+0x9f0+0x8+0x716]
loading required module 'pf'
/boot/kernel/pf.ko text=0x6061 text=0x2cb90 data=0x10490+0xfd38 syms=[0x8+0x4170+0x8+0x308c]
/boot/kernel/if_enc.ko text=0x1602 text=0x8d0 data=0x10168 syms=[0x8+0xc90+0x8+0xb66]
/boot/kernel/pfsync.ko text=0x2e14 text=0x6ad0 data=0x102e8+0xfd20 syms=[0x8+0x1758+0x8+0x10f0]
/boot/kernel/carp.ko text=0x34c0 text=0x63d0 data=0x10258+0xfdf0 syms=[0x8+0x1980+0x8+0x121f]
/boot/kernel/if_bridge.ko text=0x351e text=0x69a0 data=0x10428+0xfbe0 syms=[0x8+0x1a40+0x8+0x14a3]
loading required module 'bridgestp'
/boot/kernel/bridgestp.ko text=0xe44 text=0x402c data=0x170 data=0x158+0x28 syms=[0x8+0xb10+0x8+0x690]
/boot/kernel/if_tap.ko text=0x2613 text=0x2b90 data=0x10160+0xff18 syms=[0x8+0x1260+0x8+0xbc4]
/boot/kernel/if_lagg.ko text=0x35c0 text=0x7c30 data=0x10440+0xfbc8 syms=[0x8+0x1a70+0x8+0x1325]
/boot/kernel/if_gre.ko text=0x2458 text=0x4640 data=0x10228+0xfe18 syms=[0x8+0x1668+0x8+0xf17]
/boot/entropy size=0x1000
Using DTB provided by EFI at 0x7ef5000.
EFI framebuffer information:
addr, size 0x3eaf0000, 0x10a800
dimensions 656 x 416
stride 656
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
kldxref -R /boot
cat >>/boot/loader.conf.local <<EOF
hw.uart.console=""
bcm283x_clkman_load="YES"
EOF
echo 'powerd_enable="YES"' >/etc/rc.conf.d/powerd
U-Boot 2020.10 (Feb 02 2021 - 23:40:41 +0000)
DRAM: 948 MiB
RPI 3 Model B (0xa02082)
MMC: mmc@7e300000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment
In: serial
Out: vidconsole
Err: vidconsole
Net: No ethernet found.
starting USB...
Bus usb@7e980000: USB DWC2
scanning bus usb@7e980000 for devices... 5 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
MMC Device 0 not found
no mmc device at slot 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found EFI removable media binary efi/boot/bootaa64.efi
- _ _ _ _ ____ _____ _____
| | | | | | | | _ \ / ____| __ \
| |__| | __ _ _ __ __| | ___ _ __ ___ __| | |_) | (___ | | | |
| __ |/ _` | '__/ _` |/ _ \ '_ \ / _ \/ _` | _ < \___ \| | | |uIt5k
| | | | (_| | | | (_| | __/ | | | __/ (_| | |_) |____) | |__| |HkNMG
|_| |_|\__,_|_| \__,_|\___|_| |_|\___|\__,_|____/|_____/|_____/ Za/uu
7jx0/j28DcHs1oTUiFxDezXj0+bYBAjk
M/WeI4vOFPUZQcUiqAhCItlLY/1/YsdU
???????????????????????????????????????????????????????????????????????? ?? bYCu3JOWsOA/Ctw0oVmHA+jY6Z8RJnsT ??
?? ?? NTm3YVdJVYQ+O2ltoSwHardenedBSDVD
?? 1. Boot Multi user [Enter] ?? vji9p89gQvsPgS9hh9ekUCw/0TnSeQ1W
?? 2. Boot Single user ?? NHcmBLfiNO7mU9D4rCxiSQfifcIZzC78
?? 3. Escape to loader prompt ?? uwaNYp+XGq+qEt7pQ+aX2nsJ2juBCGai
?? 4. Reboot ?? fTclPrFDFBNSqyrmOEI3Lrkn3eudPbJU
?? ?? NlHardenedBSDvCOXT59dcSRw9mB3bOl
?? Options: ?? gEcyCwdlh1xWKOu9qGWcmsAhOVReHec4\
?? 5. Kernel: default/kernel (1 of 1) ??
?? 6. Boot Options ??
?? ??
?? ??
?? ??
???????????????????????????????????????????????????????????????????????? ?? ??
Autoboot in 0 seconds, hit [Enter] to boot or any other key to stop
Loading kernel...
/boot/kernel/kernel text=0x97f010 data=0x19b1f0+0x7a3084 syms=[0x8+0x141c30+0x8+0x12dbaa]
Loading configured modules...
/boot/kernel/pflog.ko text=0xfb0 text=0x830 data=0x10148 syms=[0x8+0x9f0+0x8+0x716]
/boot/kernel/pfsync.ko text=0x2e14 text=0x6ad0 data=0x102e8+0xfd20 syms=[0x8+0x1758+0x8+0x10f0]
/boot/kernel/carp.ko text=0x34c0 text=0x63d0 data=0x10258+0xfdf0 syms=[0x8+0x1980+0x8+0x121f]
/boot/kernel/bcm283x_clkman.ko text=0xcf7 text=0x680 data=0x10150+0xfeb8 syms=[0x8+0x6d8+0x8+0x4f2]
/boot/kernel/pf.ko text=0x6061 text=0x2cb90 data=0x10490+0xfd38 syms=[0x8+0x4170+0x8+0x308c]
/boot/kernel/if_tap.ko text=0x2613 text=0x2b90 data=0x10160+0xff18 syms=[0x8+0x1260+0x8+0xbc4]
/boot/kernel/if_lagg.ko text=0x35c0 text=0x7c30 data=0x10440+0xfbc8 syms=[0x8+0x1a70+0x8+0x1325]
/boot/kernel/if_gre.ko text=0x2458 text=0x4640 data=0x10228+0xfe18 syms=[0x8+0x1668+0x8+0xf17]
/boot/kernel/if_bridge.ko text=0x351e text=0x69a0 data=0x10428+0xfbe0 syms=[0x8+0x1a40+0x8+0x14a3]
/boot/kernel/if_enc.ko text=0x1602 text=0x8d0 data=0x10168 syms=[0x8+0xc90+0x8+0xb66]
/boot/entropy size=0x1000
Using DTB provided by EFI at 0x7ef6000.
EFI framebuffer information:
addr, size 0x3e536000, 0x6baa80
dimensions 1680 x 1050
stride 1680
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 2013-2019 The HardenedBSD Project.
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.1-RELEASE-p13-HBSD #0 5a4151730(stable/21.1)-dirty: Mon Feb 22 22:06:31 HKT 2021
root@freebsd12:/usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM arm64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
VT(efifb): resolution 1680x1050
HardenedBSD: initialize and check features (__HardenedBSD_version 1200059 __FreeBSD_version 1201000).
KLD file if_bridge.ko is missing dependencies
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
MAP 39f48000 mode 2 pages 1
MAP 39f4c000 mode 2 pages 3
MAP 39f50000 mode 2 pages 4
MAP 3b360000 mode 2 pages 16
MAP 3f100000 mode 1 pages 1
000.000021 [4336] netmap_init netmap: loaded module
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
ofw_clkbus0: <OFW clocks bus> on ofwbus0
clk_fixed0: <Fixed clock> on ofw_clkbus0
clk_fixed1: <Fixed clock> on ofw_clkbus0
regfix0: <Fixed Regulator> on ofwbus0
regfix1: <Fixed Regulator> on ofwbus0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
lintc0: <BCM2836 Interrupt Controller> mem 0x40000000-0x400000ff on simplebus0
intc0: <BCM2835 Interrupt Controller> mem 0x7e00b200-0x7e00b3ff irq 20 on simplebus0
gpio0: <BCM2708/2835 GPIO controller> mem 0x7e200000-0x7e2000b3 irq 23,24 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
generic_timer0: <ARMv7 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000
usb_nop_xceiv0: <USB NOP PHY> on ofwbus0
bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007eff irq 4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,190
bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100027 on simplebus0
bcm2835_clkman0: <BCM283x Clock Manager> mem 0x7e101000-0x7e102fff on simplebus0
bcmrng0: <Broadcom BCM2835 RNG> mem 0x7e104000-0x7e10400f irq 21 on simplebus0
mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 22 on simplebus0
gpioc0: <GPIO controller> on gpio0
uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e201fff irq 25 on simplebus0
spi0: <BCM2708/2835 SPI controller> mem 0x7e204000-0x7e204fff irq 27 on simplebus0
spibus0: <OFW SPI bus> on spi0
spibus0: <unknown card> at cs 0 mode 0
spibus0: <unknown card> at cs 1 mode 0
uart1: <BCM2835 Mini-UART> mem 0x7e215040-0x7e21507f irq 33 on simpuart1: console (115200,n,8,1)
iichb0: <BCM2708/2835 BSC controller> mem 0x7e804000-0x7e804fff irq 40 on simplebus0
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x7e980000-0x7e98ffff,0x7e006000-0x0
usbus0 on bcm283x_dwcotg0
sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 49 on simplebus0
mmc0: <MMC/SD bus> on sdhci_bcm0
fb0: <BCM2835 VT framebuffer driver> on simplebus0
fbd0 on fb0
VT: Replacing driver "efifb" with new "fb".
fb0: 1680x1050(1680x1050@0,0) 24bpp
fb0: fbswap: 1, pitch 5040, base 0x3e6e7000, screen_size 5322240
pmu0: <Performance Monitoring Unit> irq 53 on simplebus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
bcm2835_cpufreq0: <CPU Frequency Control> on cpu0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
gpioled0: <GPIO LEDs> on ofwbus0
gpioled0: <led0> failed to map pin
gpioled0: <led1> failed to map pin
ZX??????7??T??????V5Z????PY??????TX????7??)y??I????????RR??Q????K??-????)yI????????X??@RR\??????I????x????????R??Y????????
Still no serial console, tried various config from GUI, serial first etc...
btw, no nano in packages? vi is still a pain :-D
Hmm, still no driver for the wifi module of the raspi 3b in BSD? Strange...
vm_fault pager read error, pid 1
Using DTB provided by EFI at 0x7ef0000.
EFI framebuffer information:
addr, size 0x3eac2000, 0x103000
dimensions 592 x 448
stride 592
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
arm_64bit=1
dtoverlay=disable-bt
dtoverlay=mmc
device_tree_address=0x4000
kernel=u-boot.bin
armstub=armstub8-gic.bin
hdmi_safe=1
enable_uart=1
uart_2ndstage=1
@chemlud Thanks for your great news.
I have figured out that the problem of boot failure after the second boot issue is caused by the `hw.uart.console` configuration in /boot/loader.conf. As it is auto-generated by opnsense, modification on /boot/loader.conf will be flushed. You can add `hw.uart.console=""` in /boot/loader.conf.local as a temporarily solution.I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/build/21.1/aarch64/images/) for rpi3 (may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
Edited config.txt and opnsense up and running, but no Interfaces detected, not the built-in RJ45, not the wifi, not the USB2-RJ45. All hardware OK, as everything works as expected with opensuse Leap on the raspi 3b (not 3b+). I tried with raspi 3 config.txt, with 64bit version etc. and added uart=1 to have serial consol over GPIO.
Did anybody get this running?
PS: some infoCode: [Select]dmesg
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 2013-2019 The HardenedBSD Project.
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.1-RELEASE-p13-HBSD #0 5a4151730(stable/21.1)-dirty: Fri Jan 8 01:33:30 UTC 2021
root@generic:/usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM arm64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
VT(efifb): resolution 656x416
HardenedBSD: initialize and check features (__HardenedBSD_version 1200059 __FreeBSD_version 1201000).
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
MAP 39f47000 mode 2 pages 1
MAP 39f4b000 mode 2 pages 3
MAP 39f4f000 mode 2 pages 4
MAP 3b360000 mode 2 pages 16
MAP 3f100000 mode 1 pages 1
000.000021 [4336] netmap_init netmap: loaded module
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
ofw_clkbus0: <OFW clocks bus> on ofwbus0
clk_fixed0: <Fixed clock> on ofw_clkbus0
clk_fixed1: <Fixed clock> on ofw_clkbus0
regfix0: <Fixed Regulator> on ofwbus0
regfix1: <Fixed Regulator> on ofwbus0
simple_mfd0: <Simple MFD (Multi-Functions Device)> on simplebus0
ofw_clkbus1: <OFW clocks bus> on simple_mfd0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
lintc0: <BCM2836 Interrupt Controller> mem 0x40000000-0x400000ff on simplebus0
intc0: <BCM2835 Interrupt Controller> mem 0x7e00b200-0x7e00b3ff irq 39 on simplebus0
gpio0: <BCM2708/2835 GPIO controller> mem 0x7e200000-0x7e2000b3 irq 7,8 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
generic_timer0: <ARMv7 Generic Timer> irq 1,2,3,4 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000
usb_nop_xceiv0: <USB NOP PHY> on ofwbus0
mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 6 on simplebus0
gpioc0: <GPIO controller> on gpio0
uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e2011ff irq 9 on simplebus0
uart0: console (115200,n,8,1)
spi0: <BCM2708/2835 SPI controller> mem 0x7e204000-0x7e2041ff irq 11 on simplebus0
spibus0: <OFW SPI bus> on spi0
spibus0: <unknown card> at cs 0 mode 0
spibus0: <unknown card> at cs 1 mode 0
iichb0: <BCM2708/2835 BSC controller> mem 0x7e804000-0x7e804fff irq 19 on simplebus0
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x7e980000-0x7e98ffff,0x7e006000-0x7e006fff irq 21,20
usbus0 on bcm283x_dwcotg0
bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007eff irq 23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38 on simpleb0
bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100113,0x7e00a000-0x7e00a023 on simplebus0
bcmrng0: <Broadcom BCM2835 RNG> mem 0x7e104000-0x7e10400f irq 40 on simplebus0
sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 48 on simplebus0
mmc0: <MMC/SD bus> on sdhci_bcm0
fb0: <BCM2835 VT framebuffer driver> on simplebus0
fbd0 on fb0
VT: Replacing driver "efifb" with new "fb".
fb0: 656x416(656x416@0,0) 24bpp
fb0: fbswap: 1, pitch 1968, base 0x3eb33000, screen_size 818688
pmu0: <Performance Monitoring Unit> irq 0 on ofwbus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
bcm2835_cpufreq0: <CPU Frequency Control> on cpu0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
gpioled0: <GPIO LEDs> on ofwbus0
gpioled0: <led0> failed to map pin
gpioled0: <led1> failed to map pin
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
usbus0: 480Mbps High Speed USB v2.0
iicbus0: <OFW I2C bus> on iichb0
iic0: <I2C generic I/O> on iicbus0
ugen0.1: <DWCOTG OTG Root HUB> at usbus0
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
mmcsd0: 16GB <SDHC SL16G 8.0 SN 682835FD MFG 04/2016 by 3 SD> at mmc0 50.0MHz/4bit/65535-block
bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF
uhub0: 1 port with 1 removable, self powered
Release APs...done
CPU 0: ARM Cortex-A53 r0p4 affinity: 0
Trying to mount root from ufs:/dev/ufs/OPNsense [rw]...
Instruction Set Attributes 0 = <CRC32>
Instruction Set Attributes 1 = <>
Processor Features 0 = <AdvSIMD,Float,EL3 32,EL2 32,EL1 32,EL0 32>
Processor Features 1 = <0>
Memory Model Features 0 = <4k Granule,64k Granule,S/NS Mem,MixedEndian,16bit ASID,1TB PA>
Memory Model Features 1 = <>
Memory Model Features 2 = <32b CCIDX,48b VA>
Debug Features 0 = <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v8>
Debug Features 1 = <0>
Auxiliary Features 0 = <0>
Auxiliary Features 1 = <0>
CPU 1: ARM Cortex-A53 r0p4 affinity: 1
CPU 2: ARM Cortex-A53 r0p4 affinity: 2
CPU 3: ARM Cortex-A53 r0p4 affinity: 3
Warning: no time-of-day clock registered, system time will not be set accurately
lo0: link state changed to UP
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
andCode: [Select]usbconfig
ugen0.1: <DWCOTG OTG Root HUB> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
Fun fact: If you choose "reboot" the install never comes back (tried about 20 times), but stops before bootingCode: [Select]*** OPNsense.localdomain: OPNsense 21.1_25 (aarch64/OpenSSL) ***
No network interfaces are assigned.
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option: 6
The system will reboot. Do you want to proceed? [y/N]: y
>>> Invoking stop script 'beep'
>>> Invoking stop script 'freebsd'
>>> Invoking stop script 'backup'
>>> Invoking backup script 'captiveportal'
>>> Invoking backup script 'dhcpleases'
>>> Invoking backup script 'duid'
>>> Invoking backup script 'netflow'
>>> Invoking backup script 'rrd'
>>> Invoking stop script 'config'
shutdown: [pid 9305]
Shutdown NOW!
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1
(Thu Jan 7 07:14:48 UTC 2021 root@releng1.nyi.freebsd.org)
Command line arguments: loader.efi
Image base: 0x39e16000
EFI version: 2.80
EFI Firmware: Das U-Boot (rev 8224.4096)
Console: comconsole (0)
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(2,0x01,0,0x10800,0x3ef800)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
[H[J[4;46H uKOS2qsmkfe38kEuXLimP+7XoBiuIt5k[5;46H BMHardenedBSDxfOL9QwvfA6yxGHkNMG[6;46H 2I7ADmw7Mp/P8Y4wjnBFDNKvNzdZa/uu[5
[25;0H[23;4HAutoboot in 2 seconds, hit [Enter] to boot or any other key to stop
[25;0H[23;4HAutoboot in 1 seconds, hit [Enter] to boot or any other key to stop
[25;0H[23;4HAutoboot in 0 seconds, hit [Enter] to boot or any other key to stop
[25;0HLoading kernel...
/boot/kernel/kernel text=0x9857d0 data=0x19b1f0+0x7a3084 syms=[0x8+0x142260+0x8+0x12dbac]
Loading configured modules...
/boot/kernel/pflog.ko text=0xfb0 text=0x830 data=0x10148 syms=[0x8+0x9f0+0x8+0x716]
loading required module 'pf'
/boot/kernel/pf.ko text=0x6061 text=0x2cb90 data=0x10490+0xfd38 syms=[0x8+0x4170+0x8+0x308c]
/boot/kernel/if_enc.ko text=0x1602 text=0x8d0 data=0x10168 syms=[0x8+0xc90+0x8+0xb66]
/boot/kernel/pfsync.ko text=0x2e14 text=0x6ad0 data=0x102e8+0xfd20 syms=[0x8+0x1758+0x8+0x10f0]
/boot/kernel/carp.ko text=0x34c0 text=0x63d0 data=0x10258+0xfdf0 syms=[0x8+0x1980+0x8+0x121f]
/boot/kernel/if_bridge.ko text=0x351e text=0x69a0 data=0x10428+0xfbe0 syms=[0x8+0x1a40+0x8+0x14a3]
loading required module 'bridgestp'
/boot/kernel/bridgestp.ko text=0xe44 text=0x402c data=0x170 data=0x158+0x28 syms=[0x8+0xb10+0x8+0x690]
/boot/kernel/if_tap.ko text=0x2613 text=0x2b90 data=0x10160+0xff18 syms=[0x8+0x1260+0x8+0xbc4]
/boot/kernel/if_lagg.ko text=0x35c0 text=0x7c30 data=0x10440+0xfbc8 syms=[0x8+0x1a70+0x8+0x1325]
/boot/kernel/if_gre.ko text=0x2458 text=0x4640 data=0x10228+0xfe18 syms=[0x8+0x1668+0x8+0xf17]
/boot/entropy size=0x1000
Using DTB provided by EFI at 0x7ef5000.
EFI framebuffer information:
addr, size 0x3eaf0000, 0x10a800
dimensions 656 x 416
stride 656
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
@yrzr
https://ftp.yrzr.tk/opnsense/build/21.1/aarch64/images/
latest image is a vm thingy (vmdk.lzo), how to make an .img out of this? ;-)
I just run it on ESXi. Works nice on a Pi4. Use vmkfstools -i image-in.vmdk -d thin image-out.vmdk to make esxi happy.
If you want to convert it to something else,qemu-img is helpful.
Unfortunately I do not have VMWare on my machine, only HyperV. I've tried to convert the vmdk to img (raw) using qemu-img, but it failed right at the beginning :(
qemu-img: error while writing sector 0: Input/output error
@korhojoa, if you could share your img file, that could help me a lot!
Thanks!
$ qemu-img -V
qemu-img version 5.2.0 (Debian 1:5.2+dfsg-6)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
$ qemu-img convert OPNsense-21.1.3-OpenSSL-vm-aarch64.vmdk -O raw OPNsense-21.1.3-OpenSSL-vm-aarch64.img
worked fine for me. Again, note: not running it on a Pi natively, but virtualized.lzop -d file.lzo
Hi yrzr,
I'm trying to deploy your image on RPI4 (Model B 4GB), but unfortunately it is not booting. It stops at point:Code: [Select]Using DTB provided by EFI at 0x7ef0000.
EFI framebuffer information:
addr, size 0x3eac2000, 0x103000
dimensions 592 x 448
stride 592
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
No other messages ... Can you or someone give me any info, what to check or how to continue?
I'm using the following config (connected through UART):Code: [Select]arm_64bit=1
dtoverlay=disable-bt
dtoverlay=mmc
device_tree_address=0x4000
kernel=u-boot.bin
armstub=armstub8-gic.bin
hdmi_safe=1
enable_uart=1
uart_2ndstage=1
I've also attached the whole boot log.
Thanks!@chemlud Thanks for your great news.
I have figured out that the problem of boot failure after the second boot issue is caused by the `hw.uart.console` configuration in /boot/loader.conf. As it is auto-generated by opnsense, modification on /boot/loader.conf will be flushed. You can add `hw.uart.console=""` in /boot/loader.conf.local as a temporarily solution.I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/build/21.1/aarch64/images/) for rpi3 (may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
Edited config.txt and opnsense up and running, but no Interfaces detected, not the built-in RJ45, not the wifi, not the USB2-RJ45. All hardware OK, as everything works as expected with opensuse Leap on the raspi 3b (not 3b+). I tried with raspi 3 config.txt, with 64bit version etc. and added uart=1 to have serial consol over GPIO.
Did anybody get this running?
PS: some infoCode: [Select]dmesg
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 2013-2019 The HardenedBSD Project.
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.1-RELEASE-p13-HBSD #0 5a4151730(stable/21.1)-dirty: Fri Jan 8 01:33:30 UTC 2021
root@generic:/usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM arm64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
VT(efifb): resolution 656x416
HardenedBSD: initialize and check features (__HardenedBSD_version 1200059 __FreeBSD_version 1201000).
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
MAP 39f47000 mode 2 pages 1
MAP 39f4b000 mode 2 pages 3
MAP 39f4f000 mode 2 pages 4
MAP 3b360000 mode 2 pages 16
MAP 3f100000 mode 1 pages 1
000.000021 [4336] netmap_init netmap: loaded module
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
ofw_clkbus0: <OFW clocks bus> on ofwbus0
clk_fixed0: <Fixed clock> on ofw_clkbus0
clk_fixed1: <Fixed clock> on ofw_clkbus0
regfix0: <Fixed Regulator> on ofwbus0
regfix1: <Fixed Regulator> on ofwbus0
simple_mfd0: <Simple MFD (Multi-Functions Device)> on simplebus0
ofw_clkbus1: <OFW clocks bus> on simple_mfd0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
lintc0: <BCM2836 Interrupt Controller> mem 0x40000000-0x400000ff on simplebus0
intc0: <BCM2835 Interrupt Controller> mem 0x7e00b200-0x7e00b3ff irq 39 on simplebus0
gpio0: <BCM2708/2835 GPIO controller> mem 0x7e200000-0x7e2000b3 irq 7,8 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
generic_timer0: <ARMv7 Generic Timer> irq 1,2,3,4 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000
usb_nop_xceiv0: <USB NOP PHY> on ofwbus0
mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 6 on simplebus0
gpioc0: <GPIO controller> on gpio0
uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e2011ff irq 9 on simplebus0
uart0: console (115200,n,8,1)
spi0: <BCM2708/2835 SPI controller> mem 0x7e204000-0x7e2041ff irq 11 on simplebus0
spibus0: <OFW SPI bus> on spi0
spibus0: <unknown card> at cs 0 mode 0
spibus0: <unknown card> at cs 1 mode 0
iichb0: <BCM2708/2835 BSC controller> mem 0x7e804000-0x7e804fff irq 19 on simplebus0
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x7e980000-0x7e98ffff,0x7e006000-0x7e006fff irq 21,20
usbus0 on bcm283x_dwcotg0
bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007eff irq 23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38 on simpleb0
bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100113,0x7e00a000-0x7e00a023 on simplebus0
bcmrng0: <Broadcom BCM2835 RNG> mem 0x7e104000-0x7e10400f irq 40 on simplebus0
sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 48 on simplebus0
mmc0: <MMC/SD bus> on sdhci_bcm0
fb0: <BCM2835 VT framebuffer driver> on simplebus0
fbd0 on fb0
VT: Replacing driver "efifb" with new "fb".
fb0: 656x416(656x416@0,0) 24bpp
fb0: fbswap: 1, pitch 1968, base 0x3eb33000, screen_size 818688
pmu0: <Performance Monitoring Unit> irq 0 on ofwbus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
bcm2835_cpufreq0: <CPU Frequency Control> on cpu0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
gpioled0: <GPIO LEDs> on ofwbus0
gpioled0: <led0> failed to map pin
gpioled0: <led1> failed to map pin
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
usbus0: 480Mbps High Speed USB v2.0
iicbus0: <OFW I2C bus> on iichb0
iic0: <I2C generic I/O> on iicbus0
ugen0.1: <DWCOTG OTG Root HUB> at usbus0
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
mmcsd0: 16GB <SDHC SL16G 8.0 SN 682835FD MFG 04/2016 by 3 SD> at mmc0 50.0MHz/4bit/65535-block
bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF
uhub0: 1 port with 1 removable, self powered
Release APs...done
CPU 0: ARM Cortex-A53 r0p4 affinity: 0
Trying to mount root from ufs:/dev/ufs/OPNsense [rw]...
Instruction Set Attributes 0 = <CRC32>
Instruction Set Attributes 1 = <>
Processor Features 0 = <AdvSIMD,Float,EL3 32,EL2 32,EL1 32,EL0 32>
Processor Features 1 = <0>
Memory Model Features 0 = <4k Granule,64k Granule,S/NS Mem,MixedEndian,16bit ASID,1TB PA>
Memory Model Features 1 = <>
Memory Model Features 2 = <32b CCIDX,48b VA>
Debug Features 0 = <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v8>
Debug Features 1 = <0>
Auxiliary Features 0 = <0>
Auxiliary Features 1 = <0>
CPU 1: ARM Cortex-A53 r0p4 affinity: 1
CPU 2: ARM Cortex-A53 r0p4 affinity: 2
CPU 3: ARM Cortex-A53 r0p4 affinity: 3
Warning: no time-of-day clock registered, system time will not be set accurately
lo0: link state changed to UP
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
andCode: [Select]usbconfig
ugen0.1: <DWCOTG OTG Root HUB> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
Fun fact: If you choose "reboot" the install never comes back (tried about 20 times), but stops before bootingCode: [Select]*** OPNsense.localdomain: OPNsense 21.1_25 (aarch64/OpenSSL) ***
No network interfaces are assigned.
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option: 6
The system will reboot. Do you want to proceed? [y/N]: y
>>> Invoking stop script 'beep'
>>> Invoking stop script 'freebsd'
>>> Invoking stop script 'backup'
>>> Invoking backup script 'captiveportal'
>>> Invoking backup script 'dhcpleases'
>>> Invoking backup script 'duid'
>>> Invoking backup script 'netflow'
>>> Invoking backup script 'rrd'
>>> Invoking stop script 'config'
shutdown: [pid 9305]
Shutdown NOW!
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1
(Thu Jan 7 07:14:48 UTC 2021 root@releng1.nyi.freebsd.org)
Command line arguments: loader.efi
Image base: 0x39e16000
EFI version: 2.80
EFI Firmware: Das U-Boot (rev 8224.4096)
Console: comconsole (0)
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(2,0x01,0,0x10800,0x3ef800)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
[H[J[4;46H uKOS2qsmkfe38kEuXLimP+7XoBiuIt5k[5;46H BMHardenedBSDxfOL9QwvfA6yxGHkNMG[6;46H 2I7ADmw7Mp/P8Y4wjnBFDNKvNzdZa/uu[5
[25;0H[23;4HAutoboot in 2 seconds, hit [Enter] to boot or any other key to stop
[25;0H[23;4HAutoboot in 1 seconds, hit [Enter] to boot or any other key to stop
[25;0H[23;4HAutoboot in 0 seconds, hit [Enter] to boot or any other key to stop
[25;0HLoading kernel...
/boot/kernel/kernel text=0x9857d0 data=0x19b1f0+0x7a3084 syms=[0x8+0x142260+0x8+0x12dbac]
Loading configured modules...
/boot/kernel/pflog.ko text=0xfb0 text=0x830 data=0x10148 syms=[0x8+0x9f0+0x8+0x716]
loading required module 'pf'
/boot/kernel/pf.ko text=0x6061 text=0x2cb90 data=0x10490+0xfd38 syms=[0x8+0x4170+0x8+0x308c]
/boot/kernel/if_enc.ko text=0x1602 text=0x8d0 data=0x10168 syms=[0x8+0xc90+0x8+0xb66]
/boot/kernel/pfsync.ko text=0x2e14 text=0x6ad0 data=0x102e8+0xfd20 syms=[0x8+0x1758+0x8+0x10f0]
/boot/kernel/carp.ko text=0x34c0 text=0x63d0 data=0x10258+0xfdf0 syms=[0x8+0x1980+0x8+0x121f]
/boot/kernel/if_bridge.ko text=0x351e text=0x69a0 data=0x10428+0xfbe0 syms=[0x8+0x1a40+0x8+0x14a3]
loading required module 'bridgestp'
/boot/kernel/bridgestp.ko text=0xe44 text=0x402c data=0x170 data=0x158+0x28 syms=[0x8+0xb10+0x8+0x690]
/boot/kernel/if_tap.ko text=0x2613 text=0x2b90 data=0x10160+0xff18 syms=[0x8+0x1260+0x8+0xbc4]
/boot/kernel/if_lagg.ko text=0x35c0 text=0x7c30 data=0x10440+0xfbc8 syms=[0x8+0x1a70+0x8+0x1325]
/boot/kernel/if_gre.ko text=0x2458 text=0x4640 data=0x10228+0xfe18 syms=[0x8+0x1668+0x8+0xf17]
/boot/entropy size=0x1000
Using DTB provided by EFI at 0x7ef5000.
EFI framebuffer information:
addr, size 0x3eaf0000, 0x10a800
dimensions 656 x 416
stride 656
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
@yrzr
https://ftp.yrzr.tk/opnsense/build/21.1/aarch64/images/
latest image is a vm thingy (vmdk.lzo), how to make an .img out of this? ;-)
I have updated the images. You can find them in https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.1/images/.@yrzr
https://ftp.yrzr.tk/opnsense/build/21.1/aarch64/images/
latest image is a vm thingy (vmdk.lzo), how to make an .img out of this? ;-)
Raspberry Pi Bootcode
Read File: config.txt, 171
Read File: start.elf, 2857060 (bytes)
Read File: fixup.dat, 6666 (bytes)
MESS:00:00:09.099525:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:09.103786:0: brfs: File read: 171 bytes
MESS:00:00:09.146340:0: HDMI:EDID error reading EDID block 0 attempt 0
MESS:00:00:09.152417:0: HDMI:EDID error reading EDID block 0 attempt 1
MESS:00:00:09.158661:0: HDMI:EDID error reading EDID block 0 attempt 2
MESS:00:00:09.164911:0: HDMI:EDID error reading EDID block 0 attempt 3
MESS:00:00:09.171161:0: HDMI:EDID error reading EDID block 0 attempt 4
MESS:00:00:09.177412:0: HDMI:EDID error reading EDID block 0 attempt 5
MESS:00:00:09.183661:0: HDMI:EDID error reading EDID block 0 attempt 6
MESS:00:00:09.189911:0: HDMI:EDID error reading EDID block 0 attempt 7
MESS:00:00:09.196162:0: HDMI:EDID error reading EDID block 0 attempt 8
MESS:00:00:09.202411:0: HDMI:EDID error reading EDID block 0 attempt 9
MESS:00:00:09.208424:0: HDMI:EDID giving up on reading EDID block 0
MESS:00:00:09.296678:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:09.300808:0: HDMI:Setting property pixel encoding to Default
MESS:00:00:09.306887:0: HDMI:Setting property pixel clock type to PAL
MESS:00:00:09.313050:0: HDMI:Setting property content type flag to No data
MESS:00:00:09.319647:0: HDMI:Setting property fuzzy format match to enabled
MESS:00:00:09.326423:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
MESS:00:00:09.529779:0: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined
MESS:00:00:09.537232:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
MESS:00:00:09.543495:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:09.551983:0: hdmi: HDMI:>>>>>>>>>>>>>Rx sensed, reading EDID<<<<<<<<<<<<<
MESS:00:00:09.559728:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
MESS:00:00:09.567461:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
MESS:00:00:09.574227:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
MESS:00:00:09.580997:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
MESS:00:00:09.587769:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
MESS:00:00:09.594540:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
MESS:00:00:09.601309:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
MESS:00:00:09.608080:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
MESS:00:00:09.614852:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
MESS:00:00:09.621623:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
MESS:00:00:09.628156:0: hdmi: HDMI:EDID giving up on reading EDID block 0
MESS:00:00:09.633671:0: hdmi: HDMI: No lookup table for resolution group 0
MESS:00:00:09.640256:0: hdmi: HDMI: hotplug attached with DVI support
MESS:00:00:09.646433:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:09.655467:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
MESS:00:00:09.663202:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
MESS:00:00:09.669974:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
MESS:00:00:09.676745:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
MESS:00:00:09.683514:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
MESS:00:00:09.690285:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
MESS:00:00:09.697057:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
MESS:00:00:09.703827:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
MESS:00:00:09.710599:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
MESS:00:00:09.717370:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
MESS:00:00:09.723904:0: hdmi: HDMI:EDID giving up on reading EDID block 0
MESS:00:00:09.729675:0: hdmi: HDMI: hotplug deassert
MESS:00:00:09.734090:0: hdmi: HDMI: HDMI is currently off
MESS:00:00:09.739211:0: hdmi: HDMI: changing mode to unplugged
MESS:00:00:09.744776:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:09.754204:0: *** Restart logging
MESS:00:00:09.757451:0: brfs: File read: 171 bytes
MESS:00:00:09.820882:0: Failed to open command line file 'cmdline.txt'
MESS:00:00:09.952018:0: brfs: File read: /mfs/sd/armstub8.bin
MESS:00:00:09.956065:0: Loading 'armstub8.bin' to 0x0 size 0x1700
MESS:00:00:09.961909:0: brfs: File read: 5888 bytes
MESS:00:00:10.161173:0: brfs: File read: /mfs/sd/u-boot.bin
MESS:00:00:10.165050:0: Loading 'u-boot.bin' to 0x80000 size 0x78b50
MESS:00:00:10.175460:0: No kernel trailer - assuming DT-capable
MESS:00:00:10.179702:0: brfs: File read: 494416 bytes
MESS:00:00:10.254058:0: brfs: File read: /mfs/sd/bcm2710-rpi-3-b.dtb
MESS:00:00:10.258712:0: Loading 'bcm2710-rpi-3-b.dtb' to 0xf8b50 size 0x62df
MESS:00:00:10.404699:0: brfs: File read: 25311 bytes
MESS:00:00:10.450208:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:10.454102:0: dtparam: audio=on
MESS:00:00:10.476678:0: dtparam: i2c_arm=on
MESS:00:00:10.495792:0: dtparam: spi=on
MESS:00:00:10.512405:0: brfs: File read: 171 bytes
MESS:00:00:10.847009:0: brfs: File read: /mfs/sd/overlays/mmc.dtbo
MESS:00:00:10.868936:0: Loaded overlay 'mmc'
MESS:00:00:10.919659:0: brfs: File read: 1099 bytes
MESS:00:00:11.397723:0: brfs: File read: /mfs/sd/overlays/pwm.dtbo
MESS:00:00:11.414949:0: Loaded overlay 'pwm'
MESS:00:00:11.452197:0: brfs: File read: 946 bytes
MESS:00:00:11.719752:0: brfs: File read: /mfs/sd/overlays/disable-bt.dtbo
MESS:00:00:11.743774:0: dterror: can't find symbol 'bt'
MESS:00:00:11.747305:0: Failed to resolve overlay 'disable-bt'
MESS:00:00:12.908149:0: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined
MESS:00:00:13.029436:0: Device tree loaded to 0x4000 (size 0x67aa)
MESS:00:00:13.035094:0: uart: Set PL011 baud rate to 103448.300000 Hz
MESS:00:00:13.041628:0: uart: Baud rate change done...
MESS:00:00:13.045056:0: uart: Baud rateMMC: mmc@7e300000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In: serial
Out: vidconsole
Err: vidconsole
Net: No ethernet found.
starting USB...
Bus usb@7e980000: scanning bus usb@7e980000 for devices... unable to get device descriptor (error=-110)
3 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
MMC Device 0 not found
no mmc device at slot 0
Card did not respond to voltage select!
Device 0: unknown device
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-b8-27-eb-16-56-a8
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-bcm283x-rpi
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-bcm283x
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Config file not found
U-Boot>
Raspberry Pi Bootcode
Read File: config.txt, 171
Read File: start.elf, 2857060 (bytes)
Read File: fixup.dat, 6666 (bytes)
MESS:00:00:01.056002:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:01.060264:0: brfs: File read: 171 bytes
MESS:00:00:01.074138:0: HDMI:EDID error reading EDID block 0 attempt 0
MESS:00:00:01.080209:0: HDMI:EDID error reading EDID block 0 attempt 1
MESS:00:00:01.086459:0: HDMI:EDID error reading EDID block 0 attempt 2
MESS:00:00:01.092709:0: HDMI:EDID error reading EDID block 0 attempt 3
MESS:00:00:01.098959:0: HDMI:EDID error reading EDID block 0 attempt 4
MESS:00:00:01.105209:0: HDMI:EDID error reading EDID block 0 attempt 5
MESS:00:00:01.111459:0: HDMI:EDID error reading EDID block 0 attempt 6
MESS:00:00:01.117709:0: HDMI:EDID error reading EDID block 0 attempt 7
MESS:00:00:01.123959:0: HDMI:EDID error reading EDID block 0 attempt 8
MESS:00:00:01.130209:0: HDMI:EDID error reading EDID block 0 attempt 9
MESS:00:00:01.136222:0: HDMI:EDID giving up on reading EDID block 0
MESS:00:00:01.156338:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:01.160469:0: HDMI:Setting property pixel encoding to Default
MESS:00:00:01.166548:0: HDMI:Setting property pixel clock type to PAL
MESS:00:00:01.172711:0: HDMI:Setting property content type flag to No data
MESS:00:00:01.179308:0: HDMI:Setting property fuzzy format match to enabled
MESS:00:00:01.407853:0: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined
MESS:00:00:01.415330:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:01.422845:0: hdmi: HDMI:>>>>>>>>>>>>>Rx sensed, reading EDID<<<<<<<<<<<<<
MESS:00:00:01.430591:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
MESS:00:00:01.438324:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
MESS:00:00:01.445089:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
MESS:00:00:01.451860:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
MESS:00:00:01.458632:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
MESS:00:00:01.465402:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
MESS:00:00:01.472172:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
MESS:00:00:01.478944:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
MESS:00:00:01.485714:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
MESS:00:00:01.492485:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
MESS:00:00:01.499019:0: hdmi: HDMI:EDID giving up on reading EDID block 0
MESS:00:00:01.504534:0: hdmi: HDMI: No lookup table for resolution group 0
MESS:00:00:01.511118:0: hdmi: HDMI: hotplug attached with DVI support
MESS:00:00:01.517297:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:01.526330:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
MESS:00:00:01.534065:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
MESS:00:00:01.540836:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
MESS:00:00:01.547606:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
MESS:00:00:01.554378:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
MESS:00:00:01.561148:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
MESS:00:00:01.567919:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
MESS:00:00:01.574690:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
MESS:00:00:01.581461:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
MESS:00:00:01.588232:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
MESS:00:00:01.594767:0: hdmi: HDMI:EDID giving up on reading EDID block 0
MESS:00:00:01.600286:0: hdmi: HDMI: hotplug deassert
MESS:00:00:01.604952:0: hdmi: HDMI: HDMI is currently off
MESS:00:00:01.610073:0: hdmi: HDMI: changing mode to unplugged
MESS:00:00:01.615639:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:01.625853:0: *** Restart logging
MESS:00:00:01.628343:0: brfs: File read: 171 bytes
MESS:00:00:01.634030:0: Failed to open command line file 'cmdline.txt'
MESS:00:00:01.643603:0: brfs: File read: /mfs/sd/armstub8.bin
MESS:00:00:01.647652:0: Loading 'armstub8.bin' to 0x0 size 0x1700
MESS:00:00:01.653495:0: brfs: File read: 5888 bytes
MESS:00:00:01.690171:0: brfs: File read: /mfs/sd/u-boot.bin
>> FreeBSD EFI boot block
Loader path: /boot/loader.efi
Initializing modules: ZFS UFS
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Probing 3 block devices.....* done
ZFS found no pools
UFS found 1 partition
command args: -S115200 -D
Consoles: EFI console
console comconsole is invalid!
Available consoles:
efi
FreeBSD/arm64 EFI loader, Revision 1.1
(Sun Mar 21 06:55:21 HKT 2021 root@freebsd12)
Command line arguments: loader.efi -S115200 -D
EFI version: 2.70
EFI Firmware: Das U-Boot (rev 8217.1792)
Console: efi comconsole (0x20000000)
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x01,0,0x10800,0x3b61800)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x01,0,0x10800,0x3b61800)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
console vidconsole is invalid!
console comconsole is invalid!
no valid consoles!
Available consoles:
efi
/boot/kernel/kernel text=0x97f068 data=0x19b1f0+0x7a3084 syms=[0x8+0x141c48+0x8+0x12dbbb]
/boot/entropy size=0x1000
/boot/kernel/carp.ko text=0x34c0 text=0x63d0 data=0x10258+0xfdf0 syms=[0x8+0x1980+0x8+0x121f]
/boot/kernel/if_bridge.ko text=0x351e text=0x69a0 data=0x10428+0xfbe0 syms=[0x8+0x1a40+0x8+0x14a3]
/boot/kernel/if_enc.ko text=0x1602 text=0x8d0 data=0x10168 syms=[0x8+0xc90+0x8+0xb66]
/boot/kernel/if_gre.ko text=0x2458 text=0x4640 data=0x10228+0xfe18 syms=[0x8+0x1668+0x8+0xf17]
/boot/kernel/if_lagg.ko text=0x35c0 text=0x7c30 data=0x10440+0xfbc8 syms=[0x8+0x1a70+0x8+0x1325]
/boot/kernel/if_tap.ko text=0x2613 text=0x2b90 data=0x10160+0xff18 syms=[0x8+0x1260+0x8+0xbc4]
/boot/kernel/pf.ko text=0x6061 text=0x2cb90 data=0x10490+0xfd38 syms=[0x8+0x4170+0x8+0x308c]
/boot/kernel/pflog.ko text=0xfb0 text=0x830 data=0x10148 syms=[0x8+0x9f0+0x8+0x716]
/boot/kernel/pfsync.ko text=0x2e14 text=0x6ad0 data=0x102e8+0xfd20 syms=[0x8+0x1758+0x8+0x10f0]
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by EFI at 0x7ef6000.
EFI framebuffer information:
addr, size 0x3eaf0000, 0x10a800
dimensions 656 x 416
stride 656
masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 2013-2019 The HardenedBSD Project.
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.1-RELEASE-p14-HBSD #0 e10a7efce(stable/21.1)-dirty: Sun Mar 21 08:00:57 HKT 2021
root@freebsd12:/usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM arm64
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
VT(efifb): resolution 656x416
HardenedBSD: initialize and check features (__HardenedBSD_version 1200059 __FreeBSD_version 1201000).
KLD file if_bridge.ko is missing dependencies
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
random: unblocking device.
random: entropy device external interface
MAP 39f4a000 mode 2 pages 1
MAP 39f4f000 mode 2 pages 1
MAP 3b350000 mode 2 pages 16
MAP 3f100000 mode 1 pages 1
000.000021 [4336] netmap_init netmap: loaded module
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
ofw_clkbus0: <OFW clocks bus> on ofwbus0
clk_fixed0: <Fixed clock> on ofw_clkbus0
clk_fixed1: <Fixed clock> on ofw_clkbus0
regfix0: <Fixed Regulator> on ofwbus0
regfix1: <Fixed Regulator> on ofwbus0
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
lintc0: <BCM2836 Interrupt Controller> mem 0x40000000-0x400000ff on simplebus0
intc0: <BCM2835 Interrupt Controller> mem 0x7e00b200-0x7e00b3ff irq 20 on simplebus0
gpio0: <BCM2708/2835 GPIO controller> mem 0x7e200000-0x7e2000b3 irq 23,24 on simplebus0
gpiobus0: <OFW GPIO bus> on gpio0
generic_timer0: <ARMv7 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000
usb_nop_xceiv0: <USB NOP PHY> on ofwbus0
bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007eff irq 4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19 on simplebus0
bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100027 on simplebus0
bcmrng0: <Broadcom BCM2835 RNG> mem 0x7e104000-0x7e10400f irq 21 on simplebus0
mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 22 on simplebus0
gpioc0: <GPIO controller> on gpio0
uart0: <PrimeCell UART (PL011)> mem 0x7e201000-0x7e201fff irq 25 on simplebus0
spi0: <BCM2708/2835 SPI controller> mem 0x7e204000-0x7e204fff irq 27 on simplebus0
spibus0: <OFW SPI bus> on spi0
spibus0: <unknown card> at cs 0 mode 0
spibus0: <unknown card> at cs 1 mode 0
uart1: <BCM2835 Mini-UART> mem 0x7e215040-0x7e21507f irq 33 on simplebus0
uart1: console (115200,n,8,1)
iichb0: <BCM2708/2835 BSC controller> mem 0x7e804000-0x7e804fff irq 40 on simplebus0
bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x7e980000-0x7e98ffff,0x7e006000-0x7e006fff irq 46,47 on simplebus0
usbus0 on bcm283x_dwcotg0
sdhci_bcm0: <Broadcom 2708 SDHCI controller> mem 0x7e300000-0x7e3000ff irq 49 on simplebus0
mmc0: <MMC/SD bus> on sdhci_bcm0
fb0: <BCM2835 VT framebuffer driver> on simplebus0
fbd0 on fb0
VT: Replacing driver "efifb" with new "fb".
fb0: 656x416(656x416@0,0) 24bpp
fb0: fbswap: 1, pitch 1968, base 0x3eb33000, screen_size 818688
pmu0: <Performance Monitoring Unit> irq 53 on simplebus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
bcm2835_cpufreq0: <CPU Frequency Control> on cpu0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
gpioled0: <GPIO LEDs> on ofwbus0
gpioled0: <led1> failed to map pin
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
usbus0: 480Mbps High Speed USB v2.0
iicbus0: <OFW I2C bus> on iichb0
iic0: <I2C generic I/O> on iicbus0
ugen0.1: <DWCOTG OTG Root HUB> at usbus0
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
mmcsd0: 32GB <SDHC SC32G 8.0 SN 9DC03993 MFG 10/2018 by 3 SD> at mmc0 50.0MHz/4bit/65535-block
bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF
mbox0: mbox response error
bcm2835_cpufreq0: can't set clock rate (id=4)
Release APs...done
CPU 0: ARM Cortex-A53 r0p4 affinity: 0
Trying to mount root from ufs:/dev/ufs/OPNsense [rw]...
Instruction Set Attributes 0 = <CRC32>
Instruction Set Attributes 1 = <>
Processor Features 0 = <AdvSIMD,Float,EL3 32,EL2 32,EL1 32,EL0 32>
Processor Features 1 = <0>
Memory Model Features 0 = <4k Granule,64k Granule,S/NS Mem,MixedEndian,16bit ASID,1TB PA>
Memory Model Features 1 = <>
Memory Model Features 2 = <32b CCIDX,48b VA>
Debug Features 0 = <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v8>
Debug Features 1 = <0>
Auxiliary Features 0 = <0>
Auxiliary Features 1 = <0>
CPU 1: ARM Cortex-A53 r0p4 affinity: 1
CPU 2: ARM Cortex-A53 r0p4 affinity: 2
CPU 3: ARM Cortex-A53 r0p4 affinity: 3
Warning: no time-of-day clock registered, system time will not be set accurately
uhub0: 1 port with 1 removable, self powered
Mounting filesystems...
tunefs: soft updates remains unchanged as enabled
tunefs: file system reloaded
camcontrol: cam_ugen0.2: <vendor 0x0424 product 0x2514> at usbus0
uhub1 on uhub0
uhub1: <vendor 0x0424 product 0x2514, class 9/0, rev 2.00/b.b3, addr 2> on usbus0
uhub1: MTT enabled
lookup_pass: CAMGETPASSTHRU ioctl failed
cam_lookup_pass: No such file or directory
cam_lookup_pass: either the pass driver isn't in your kernel
cam_lookup_pass: or mmcsd0 doesn't exist
** /dev/ufs/OPNsense
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 7101844 fuhub1: 4 ports with 3 removable, self powered
ree (220 frags, 887703 blocks, 0.0% fragmentation)
ugen0.3: <vendor 0x0424 product 0x2514> at usbus0
uhub2 on uhub1
uhub2: <vendor 0x0424 product 0x2514, class 9/0, rev 2.00/b.b3, addr 3> on usbus0
uhub2: MTT enabled
Setting hostuuid: 30303030-3030-3030-3139-663138353365.
Setting hostid: 0x56d89878.
Configurinuhub2: 3 ports with 2 removable, self powered
g vt: blanktime.
ugen0.4: <vendor 0x0424 product 0x7800> at usbus0
muge0 on uhub2
muge0: <vendor 0x0424 product 0x7800, rev 2.10/3.00, addr 4> on usbus0
muge0: Chip ID 0x7800 rev 0002
miibus0: <MII bus> on muge0
ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
ue0: <USB Ethernet> on muge0
ue0: Ethernet address: b8:27:eb:f1:85:3e
Setting up memory disks...done.
Configuring crash dump device: /dev/null
.ELF ldconfig path: /lib /usr/lib /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg /usr/local/lib/ipsec /usr/local/lib/perl5/5.32/mach/CORE
done.
>>> Invoking early script 'upgrade'
>>> Invoking early script 'configd'
Starting configd.
>>> Invoking early script 'templates'
Generating configuration: OK
>>> Invoking early script 'backup'
>>> Invoking backup script 'captiveportal'
>>> Invoking backup script 'dhcpleases'
>>> Invoking backup script 'duid'
>>> Invoking backup script 'netflow'
>>> Invoking backup script 'rrd'
>>> Invoking early script 'carp'
CARP event system: OK
Launching the init system...done.
Initializing...........done.
ue0: link state changed to UP
Starting device manager...done.
Configuring login behaviour...done.
Configuring looplo0: link state changed to UP
back interface...done.
Configuring kernel modules...done.
Setting up extended sysctls...done.
Setting timezone...done.
Writing firmware setting...done.
Writing trust files...done.
Setting hostname: opnsense.yrzr.tk
Generating /etc/hosts...done.
Configuring system logging...done.
Configuring loopback interface...done.
Creating wireless clone interfaces...donmuge0: Chip ID 0x7800 rev 0002
e.
Configuring WAN interface...done.
Creating IPsec VTI instances...done.
Generating /etc/resolv.conf...done.
Configuring firewall........done.
Starting PFLOG...done.
Configuring OpenSSH...done.
Starting web GUI...done.
Configuring CRON...done.
Setting up routes...done.
Generating /etc/hosts...done.
Starting Unbound DNS...done.
Setting up gateway monitors...done.
Configuring firewall........done.
Starting PFLOG...done.
Syncing OpenVPN settings...done.
Starting NTP service...deferred.
Starting Unbound DNS...done.
Generating RRD graphs...done.
Configuring system logging...done.
>>> Invoking start script 'newwanip'
Reconfiguring IPv4 on ue0: OK
Reconfiguring routes: OK
>>> Invoking start script 'freebsd'
Starting powerd.
>>> Invoking start script 'syslog-ng'
Stopping syslog_ng.
Waiting for PIDS: 31435.
Starting syslog_ng.
>>> Invoking start script 'wireguard'
Setting up routes...done.
Setting up gateway monitors...done.
Configuring firewall........done.
Starting PFLOG...done.
>>> Invoking start script 'carp'
>>> Invoking start script 'cron'
Starting Cron: OK
>>> Invoking start script 'beep'
Root file system: /dev/ufs/OPNsense
Fri Mar 26 20:11:52 HKT 2021
*** opnsense.yrzr.tk: OPNsense 21.1.3 (aarch64/OpenSSL) ***
As I wrote above, I can only boot from USB-stick (SD-slot broken), this works fine for the first boot, but after importing the config.xml via GUI the reboot fails completely:Code: [Select]Raspberry Pi Bootcode
Read File: config.txt, 171
Read File: start.elf, 2857060 (bytes)
Read File: fixup.dat, 6666 (bytes)
MESS:00:00:09.099525:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:09.103786:0: brfs: File read: 171 bytes
MESS:00:00:09.146340:0: HDMI:EDID error reading EDID block 0 attempt 0
MESS:00:00:09.152417:0: HDMI:EDID error reading EDID block 0 attempt 1
MESS:00:00:09.158661:0: HDMI:EDID error reading EDID block 0 attempt 2
MESS:00:00:09.164911:0: HDMI:EDID error reading EDID block 0 attempt 3
MESS:00:00:09.171161:0: HDMI:EDID error reading EDID block 0 attempt 4
MESS:00:00:09.177412:0: HDMI:EDID error reading EDID block 0 attempt 5
MESS:00:00:09.183661:0: HDMI:EDID error reading EDID block 0 attempt 6
MESS:00:00:09.189911:0: HDMI:EDID error reading EDID block 0 attempt 7
MESS:00:00:09.196162:0: HDMI:EDID error reading EDID block 0 attempt 8
MESS:00:00:09.202411:0: HDMI:EDID error reading EDID block 0 attempt 9
MESS:00:00:09.208424:0: HDMI:EDID giving up on reading EDID block 0
MESS:00:00:09.296678:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:09.300808:0: HDMI:Setting property pixel encoding to Default
MESS:00:00:09.306887:0: HDMI:Setting property pixel clock type to PAL
MESS:00:00:09.313050:0: HDMI:Setting property content type flag to No data
MESS:00:00:09.319647:0: HDMI:Setting property fuzzy format match to enabled
MESS:00:00:09.326423:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
MESS:00:00:09.529779:0: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined
MESS:00:00:09.537232:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
MESS:00:00:09.543495:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:09.551983:0: hdmi: HDMI:>>>>>>>>>>>>>Rx sensed, reading EDID<<<<<<<<<<<<<
MESS:00:00:09.559728:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
MESS:00:00:09.567461:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
MESS:00:00:09.574227:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
MESS:00:00:09.580997:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
MESS:00:00:09.587769:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
MESS:00:00:09.594540:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
MESS:00:00:09.601309:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
MESS:00:00:09.608080:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
MESS:00:00:09.614852:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
MESS:00:00:09.621623:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
MESS:00:00:09.628156:0: hdmi: HDMI:EDID giving up on reading EDID block 0
MESS:00:00:09.633671:0: hdmi: HDMI: No lookup table for resolution group 0
MESS:00:00:09.640256:0: hdmi: HDMI: hotplug attached with DVI support
MESS:00:00:09.646433:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:09.655467:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
MESS:00:00:09.663202:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
MESS:00:00:09.669974:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
MESS:00:00:09.676745:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
MESS:00:00:09.683514:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
MESS:00:00:09.690285:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
MESS:00:00:09.697057:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
MESS:00:00:09.703827:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
MESS:00:00:09.710599:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
MESS:00:00:09.717370:0: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
MESS:00:00:09.723904:0: hdmi: HDMI:EDID giving up on reading EDID block 0
MESS:00:00:09.729675:0: hdmi: HDMI: hotplug deassert
MESS:00:00:09.734090:0: hdmi: HDMI: HDMI is currently off
MESS:00:00:09.739211:0: hdmi: HDMI: changing mode to unplugged
MESS:00:00:09.744776:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:09.754204:0: *** Restart logging
MESS:00:00:09.757451:0: brfs: File read: 171 bytes
MESS:00:00:09.820882:0: Failed to open command line file 'cmdline.txt'
MESS:00:00:09.952018:0: brfs: File read: /mfs/sd/armstub8.bin
MESS:00:00:09.956065:0: Loading 'armstub8.bin' to 0x0 size 0x1700
MESS:00:00:09.961909:0: brfs: File read: 5888 bytes
MESS:00:00:10.161173:0: brfs: File read: /mfs/sd/u-boot.bin
MESS:00:00:10.165050:0: Loading 'u-boot.bin' to 0x80000 size 0x78b50
MESS:00:00:10.175460:0: No kernel trailer - assuming DT-capable
MESS:00:00:10.179702:0: brfs: File read: 494416 bytes
MESS:00:00:10.254058:0: brfs: File read: /mfs/sd/bcm2710-rpi-3-b.dtb
MESS:00:00:10.258712:0: Loading 'bcm2710-rpi-3-b.dtb' to 0xf8b50 size 0x62df
MESS:00:00:10.404699:0: brfs: File read: 25311 bytes
MESS:00:00:10.450208:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:10.454102:0: dtparam: audio=on
MESS:00:00:10.476678:0: dtparam: i2c_arm=on
MESS:00:00:10.495792:0: dtparam: spi=on
MESS:00:00:10.512405:0: brfs: File read: 171 bytes
MESS:00:00:10.847009:0: brfs: File read: /mfs/sd/overlays/mmc.dtbo
MESS:00:00:10.868936:0: Loaded overlay 'mmc'
MESS:00:00:10.919659:0: brfs: File read: 1099 bytes
MESS:00:00:11.397723:0: brfs: File read: /mfs/sd/overlays/pwm.dtbo
MESS:00:00:11.414949:0: Loaded overlay 'pwm'
MESS:00:00:11.452197:0: brfs: File read: 946 bytes
MESS:00:00:11.719752:0: brfs: File read: /mfs/sd/overlays/disable-bt.dtbo
MESS:00:00:11.743774:0: dterror: can't find symbol 'bt'
MESS:00:00:11.747305:0: Failed to resolve overlay 'disable-bt'
MESS:00:00:12.908149:0: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined
MESS:00:00:13.029436:0: Device tree loaded to 0x4000 (size 0x67aa)
MESS:00:00:13.035094:0: uart: Set PL011 baud rate to 103448.300000 Hz
MESS:00:00:13.041628:0: uart: Baud rate change done...
MESS:00:00:13.045056:0: uart: Baud rateMMC: mmc@7e300000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In: serial
Out: vidconsole
Err: vidconsole
Net: No ethernet found.
starting USB...
Bus usb@7e980000: scanning bus usb@7e980000 for devices... unable to get device descriptor (error=-110)
3 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
MMC Device 0 not found
no mmc device at slot 0
Card did not respond to voltage select!
Device 0: unknown device
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-b8-27-eb-16-56-a8
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-bcm283x-rpi
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-bcm283x
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Config file not found
U-Boot>
MESS:00:00:01.690171:0: brfs: File read: /mfs/sd/u-boot.bin
>> FreeBSD EFI boot block
Loader path: /boot/loader.efi
Initializing modules: ZFS UFS
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Probing 3 block devices.....* done
ZFS found no pools
UFS found 1 partition
command args: -S115200 -D
...
...
MESS:00:00:10.166426:0: Loading 'u-boot.bin' to 0x80000 size 0x78b50
MESS:00:00:10.176834:0: No kernel trailer - assuming DT-capable
MESS:00:00:10.181076:0: brfs: File read: 494416 bytes
MESS:00:00:10.242557:0: brfs: File read: /mfs/sd/bcm2710-rpi-3-b.dtb
MESS:00:00:10.247212:0: Loading 'bcm2710-rpi-3-b.dtb' to 0xf8b50 size 0x62df
MESS:00:00:10.393105:0: brfs: File read: 25311 bytes
MESS:00:00:10.438707:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:10.442600:0: dtparam: audio=on
MESS:00:00:10.465152:0: dtparam: i2c_arm=on
MESS:00:00:10.484265:0: dtparam: spi=on
MESS:00:00:10.500871:0: brfs: File read: 171 bytes
MESS:00:00:10.835383:0: brfs: File read: /mfs/sd/overlays/mmc.dtbo
MESS:00:00:10.857296:0: Loaded overlay 'mmc'
MESS:00:00:10.908017:0: brfs: File read: 1099 bytes
MESS:00:00:11.385221:0: brfs: File read: /mfs/sd/overlays/pwm.dtbo
MESS:00:00:11.402444:0: Loaded overlay 'pwm'
MESS:00:00:11.439702:0: brfs: File read: 946 bytes
MESS:00:00:11.707876:0: brfs: File read: /mfs/sd/overlays/disable-bt.dtbo
MESS:00:00:11.732142:0: dterror: can't find symbol 'bt'
MESS:00:00:11.735660:0: Failed to resolve overlay 'disable-bt'
MESS:00:00:12.883018:0: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined
MESS:00:00:13.004264:0: Device tree loaded to 0x4000 (size 0x67aa)
MESS:00:00:13.009938:0: uart: Set PL011 baud rate to 103448.300000 Hz
MESS:00:00:13.016456:0: uart: Baud rate change done...
MESS:00:00:13.019884:0: uart: Baud rateMMC: mmc@7e300000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In: serial
Out: vidconsole
Err: vidconsole
Net: No ethernet found.
starting USB...
Bus usb@7e980000: scanning bus usb@7e980000 for devices... unable to get device descriptor (error=-110)
3 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
MMC Device 0 not found
no mmc device at slot 0
Card did not respond to voltage select!
Device 0: unknown device
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-b8-27-eb-16-56-a8
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-bcm283x-rpi
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-bcm283x
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Config file not found
I have figured out that the problem of boot failure after the second boot issue is caused by the `hw.uart.console` configuration in /boot/loader.conf. As it is auto-generated by opnsense, modification on /boot/loader.conf will be flushed. You can add `hw.uart.console=""` in /boot/loader.conf.local as a temporarily solution.
No matter if I copy over the DTB etc. from FeeBSD for raspi 3 or not the second boot fails
Difference to your boot start afterCode: [Select]MESS:00:00:01.690171:0: brfs: File read: /mfs/sd/u-boot.bin
Your next linie isCode: [Select]>> FreeBSD EFI boot block
Loader path: /boot/loader.efi
Initializing modules: ZFS UFS
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x800,0x10000)
Probing 3 block devices.....* done
ZFS found no pools
UFS found 1 partition
command args: -S115200 -D
...
while my USB-stick takes a swing to a parallel universe not meant to be used for production:Code: [Select]...
MESS:00:00:10.166426:0: Loading 'u-boot.bin' to 0x80000 size 0x78b50
MESS:00:00:10.176834:0: No kernel trailer - assuming DT-capable
MESS:00:00:10.181076:0: brfs: File read: 494416 bytes
MESS:00:00:10.242557:0: brfs: File read: /mfs/sd/bcm2710-rpi-3-b.dtb
MESS:00:00:10.247212:0: Loading 'bcm2710-rpi-3-b.dtb' to 0xf8b50 size 0x62df
MESS:00:00:10.393105:0: brfs: File read: 25311 bytes
MESS:00:00:10.438707:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:10.442600:0: dtparam: audio=on
MESS:00:00:10.465152:0: dtparam: i2c_arm=on
MESS:00:00:10.484265:0: dtparam: spi=on
MESS:00:00:10.500871:0: brfs: File read: 171 bytes
MESS:00:00:10.835383:0: brfs: File read: /mfs/sd/overlays/mmc.dtbo
MESS:00:00:10.857296:0: Loaded overlay 'mmc'
MESS:00:00:10.908017:0: brfs: File read: 1099 bytes
MESS:00:00:11.385221:0: brfs: File read: /mfs/sd/overlays/pwm.dtbo
MESS:00:00:11.402444:0: Loaded overlay 'pwm'
MESS:00:00:11.439702:0: brfs: File read: 946 bytes
MESS:00:00:11.707876:0: brfs: File read: /mfs/sd/overlays/disable-bt.dtbo
MESS:00:00:11.732142:0: dterror: can't find symbol 'bt'
MESS:00:00:11.735660:0: Failed to resolve overlay 'disable-bt'
MESS:00:00:12.883018:0: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined
MESS:00:00:13.004264:0: Device tree loaded to 0x4000 (size 0x67aa)
MESS:00:00:13.009938:0: uart: Set PL011 baud rate to 103448.300000 Hz
MESS:00:00:13.016456:0: uart: Baud rate change done...
MESS:00:00:13.019884:0: uart: Baud rateMMC: mmc@7e300000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In: serial
Out: vidconsole
Err: vidconsole
Net: No ethernet found.
starting USB...
Bus usb@7e980000: scanning bus usb@7e980000 for devices... unable to get device descriptor (error=-110)
3 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
MMC Device 0 not found
no mmc device at slot 0
Card did not respond to voltage select!
Device 0: unknown device
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-b8-27-eb-16-56-a8
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-bcm283x-rpi
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-bcm283x
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Config file not found
I thought this fix is included now:Code: [Select]I have figured out that the problem of boot failure after the second boot issue is caused by the `hw.uart.console` configuration in /boot/loader.conf. As it is auto-generated by opnsense, modification on /boot/loader.conf will be flushed. You can add `hw.uart.console=""` in /boot/loader.conf.local as a temporarily solution.
Or do I still have to add the loader.conf.local?
Hi yrzr,
I found a good documentation on https://github.com/sreinhardt/armada-8040-images
i think with this item you can generate img
DDR version 1.16 20190528
ID:0x805 N
In
DDR4
333MHz
Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
ddrconfig:14
OUT
Boot1 Release Time: May 13 2019 17:34:36, version: 2.50
ChipType = 0x11, 248
mmc2:cmd1,20
emmc reinit
mmc2:cmd1,20
emmc reinit
mmc2:cmd1,20
SdmmcInit=2 1
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=3781MB
FwPartOffset=2000 , 0
StorageInit ok = 34120
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x337a9f0 signature is wrong
recovery gpt...
GPT part: 0, name: , start:0x800, size:0x762000
recovery gpt success!
no find partition:uboot.
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
hdr 000000000337a3b0 + 0x0:0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,
Load OK, addr=0x200000, size=0xab950
RunBL31 0x40000
INFO: Preloader serial: 2
NOTICE: BL31: v1.3(debug):403e0b816
NOTICE: BL31: Built : 14:13:08, Aug 11 2020
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2020.10-armbian (May 06 2021 - 18:04:51 +0000)
Model: FriendlyElec NanoPi R2S
DRAM: 1022 MiB
PMIC: RK8050 (on=0x40, off=0x01)
MMC: mmc@ff500000: 1
Loading Environment from MMC... MMC Device 0 not found
*** Warning - No MMC card found, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: FriendlyElec NanoPi R2S
Net: eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found EFI removable media binary efi/boot/bootaa64.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@ff500000.blk...
** Unrecognized filesystem type **
Found 3 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
393216 bytes read in 68 ms (5.5 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Booting /efi\boot\bootaa64.efi
>> FreeBSD EFI boot block
Loader path: /boot/loader.efi
Initializing modules: ZFS UFS
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x800,0x19000)
Probing 3 block devices...... done
ZFS found no pools
UFS found no partitions
Failed to load '/boot/loader.efi'
panic: No bootable partitions found!
## Application failed, r = 1
EFI LOAD FAILED: continuing...
MMC Device 0 not found
no mmc device at slot 0
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No working controllers found
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
There is a working image gor freebsd and opnsense for NanoPi R2S as since the rtl drivers were recently merged in freebsd.
https://personalbsd.org/images/OPNsense-21.1-OpenSSL-aarch64-NanoPi-R2S-20210612.img.xz.
Please donate to sergey for all his effort at personalbsd.org
Feel free to join telegram chat for opnsense on arm @personalbsd
Thanks.
There is a working image gor freebsd and opnsense for NanoPi R2S as since the rtl drivers were recently merged in freebsd.
https://personalbsd.org/images/OPNsense-21.1-OpenSSL-aarch64-NanoPi-R2S-20210612.img.xz.
Please donate to sergey for all his effort at personalbsd.org
Feel free to join telegram chat for opnsense on arm @personalbsd
Thanks.
I would like to try the image on R4S, @spikerguy Can you link to the telegram chat? I couldn't find it.
I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.1/images/) for rpi3(may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
------------
update on 2021-02-24
An updated image is now out, which works properly on rpi3b+ with the advice of @testo_cz.
Moreover, after the first boot, add `hw.uart.console=""` to /boot/loader.conf.local or the console will goes nowhere in the next boot.
Finally, you can use https://ftp.yrzr.tk/opnsense/ as the Repo to get almost all the plugins as if on amd64. Edit /usr/local/etc/pkg/repos/OPNsense.conf:Code: [Select]OPNsense: {
fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
url: "https://ftp.yrzr.tk/opnsense/${ABI}/21.1/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
------------
update on 2021-03-25
Thanks to @nekoprog's code and @testo_cz's advice, the RPI3 images now work fine with the serial console.
I have also made a rough introduction to the images on https://www.yrzr.tk/opnsense-images-for-aarch64.
FreeBSD 13.0-RELEASE #0 releng/13.0-n244733-ea31abc261f: Fri Apr 9 06:06:55 UTC 2021
root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64
FreeBSD clang version 11.0.1 (git@github.com:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe)
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mmcsd0: Error indicated: 1 Timeout
mountroot: waiting for device /dev/ufs/OPNsense...
Mounting from ufs:/dev/ufs/OPNsense failed with error 19.
Loader variables:
vfs.root.mountfrom=ufs:/dev/ufs/OPNsense
vfs.root.mountfrom.options=rw
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:/dev/cd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot>
I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.1/images/) for rpi3(may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
------------
update on 2021-02-24
An updated image is now out, which works properly on rpi3b+ with the advice of @testo_cz.
Moreover, after the first boot, add `hw.uart.console=""` to /boot/loader.conf.local or the console will goes nowhere in the next boot.
Finally, you can use https://ftp.yrzr.tk/opnsense/ as the Repo to get almost all the plugins as if on amd64. Edit /usr/local/etc/pkg/repos/OPNsense.conf:Code: [Select]OPNsense: {
fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
url: "https://ftp.yrzr.tk/opnsense/${ABI}/21.1/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
------------
update on 2021-03-25
Thanks to @nekoprog's code and @testo_cz's advice, the RPI3 images now work fine with the serial console.
I have also made a rough introduction to the images on https://www.yrzr.tk/opnsense-images-for-aarch64.
I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.1/images/) for rpi3(may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
------------
update on 2021-02-24
An updated image is now out, which works properly on rpi3b+ with the advice of @testo_cz.
Moreover, after the first boot, add `hw.uart.console=""` to /boot/loader.conf.local or the console will goes nowhere in the next boot.
Finally, you can use https://ftp.yrzr.tk/opnsense/ as the Repo to get almost all the plugins as if on amd64. Edit /usr/local/etc/pkg/repos/OPNsense.conf:Code: [Select]OPNsense: {
fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
url: "https://ftp.yrzr.tk/opnsense/${ABI}/21.1/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
------------
update on 2021-03-25
Thanks to @nekoprog's code and @testo_cz's advice, the RPI3 images now work fine with the serial console.
I have also made a rough introduction to the images on https://www.yrzr.tk/opnsense-images-for-aarch64.
Thanks @yrzr for this amazing work and for hosting the arm64 repo! I have opnsense 21.7 up and running happily on my rpi4 under ESXi.
Only thing I was wondering is if there is a reason the "os-vmware" plugin isn't available in your repo? It would be great to get vmware tools going too. I can have a go at compiling and installing vmwtools by hand, but it would be even better if this was possible through opnsense's ui.
Many thanks!
The plugin depends on open-vm-tools-nox11 (https://www.freshports.org/emulators/open-vm-tools-nox11/), currently not supported on aarch64.
However, there are patches out there that you can install on aarch64. See https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm-fling/.I have recently built a version 21.1 test image (https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.1/images/) for rpi3(may also work on rpi4).
Feel free to try it, and don't forget to modify config.txt before the first run ;).
------------
update on 2021-02-24
An updated image is now out, which works properly on rpi3b+ with the advice of @testo_cz.
Moreover, after the first boot, add `hw.uart.console=""` to /boot/loader.conf.local or the console will goes nowhere in the next boot.
Finally, you can use https://ftp.yrzr.tk/opnsense/ as the Repo to get almost all the plugins as if on amd64. Edit /usr/local/etc/pkg/repos/OPNsense.conf:Code: [Select]OPNsense: {
fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
url: "https://ftp.yrzr.tk/opnsense/${ABI}/21.1/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
------------
update on 2021-03-25
Thanks to @nekoprog's code and @testo_cz's advice, the RPI3 images now work fine with the serial console.
I have also made a rough introduction to the images on https://www.yrzr.tk/opnsense-images-for-aarch64.
Thanks @yrzr for this amazing work and for hosting the arm64 repo! I have opnsense 21.7 up and running happily on my rpi4 under ESXi.
Only thing I was wondering is if there is a reason the "os-vmware" plugin isn't available in your repo? It would be great to get vmware tools going too. I can have a go at compiling and installing vmwtools by hand, but it would be even better if this was possible through opnsense's ui.
Many thanks!
Can anyone build and share the R4S image from https://github.com/yrzr/opnsense-tools/tree/22.1/r4s?
To use opnsense on rpi you will need a usb to lan adaptor and not all devices are supported in freebsd .
Also performance will not be good with usb adaptor, hence many no one is working on it.
I'm trying to create a OPNSense VM on Proxmox with diry image from @yrzr without success. Anyone have tried it and successfully installed it ?
Hey @efetropy, I used this one - https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.1/images/dirty/ (https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.1/images/dirty/) but VM didn't boot
@efetropy ok. I would be grateful if you could send me the correct file or help me how I can do it.
it is feasible to port OPNsense to an ARM Cortex-A72 (Marvell® ARMADA® 7040)?
There is a OpenWrt SNAPSHOT (https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=mvebu%2Fcortexa72&id=globalscale_mochabin) available for the Globalscale MOCHAbin (I do have dev board).
Moreover I have Debian and Ubuntu image.
What would be the way to go to port it?
thank you
stefan
Hi,
Which image did you use?
Would you mind sharing?
Hi,
struggling for some days now to create a working x-build for a AMD64 host to a NanoPI R4S. Has someone this really working as I continue to run into error messages with the package build (base and kernel build seem to run fine).
I guess it's related to the cc target not being right because when I do a chroot in the build directory (make chroot DEVICE=R4S) and check the cc output I get the following
>>> chroot'ing into /usr/obj/usr/tools/config/22.1/OpenSSL:aarch64/...
root@freebsd-13-0-1:/ # cc --version
FreeBSD clang version 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
Target: x86_64-unknown-freebsd13.0
Thread model: posix
InstalledDir: /usr/bin
Where I would expect an aarch64 target. Not sure where this is going wrong.
Thnx for your support
pcib0: <Rockchip PCIe controller> mem 0xf8000000-0xf9ffffff,0xfd000000-0xfdffffff irq 6,7,8 on ofwbus0
pcib0: Cannot get 'pcie-phy-0' phy
device_attach: pcib0 attach returned 6
pcib0: <Rockchip PCIe controller> mem 0xf8000000-0xf9ffffff,0xfd000000-0xfdffffff irq 6,7,8 on ofwbus0
pci0: <PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 0.0 on pci0
pcib0: failed to reserve resource for pcib1
pcib1: failed to allocate initial memory window: 0-0xfffff
pci1: <PCI bus> on pcib1
pcib0: route pin 1 for device 0.0 to 78
pcib0: route pin 2 for device 0.0 to 79
pcib0: route pin 3 for device 0.0 to 80
pcib0: route pin 4 for device 0.0 to 81
Are you referring to the ROCKPro64 image? You can simply get the R4S image from https://ftp.yrzr.tk/opnsense/FreeBSD%3A13%3Aaarch64/22.1/images/
All you gotta do is write the bootloader files and you're set
https://personalbsd.org/?page_id=2
Makefile:43: *** missing separator. Stop.
Makefile:61: *** recipe commences before first target. Stop.
it is feasible to port OPNsense to an ARM Cortex-A72 (Marvell® ARMADA® 7040)?
There is a OpenWrt SNAPSHOT (https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=mvebu%2Fcortexa72&id=globalscale_mochabin) available for the Globalscale MOCHAbin (I do have dev board).
Moreover I have Debian and Ubuntu image.
What would be the way to go to port it?
thank you
stefan
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1
Command line arguments: loader.efi
Image base: 0xf0def000
EFI version: 2.80
EFI Firmware: Das U-Boot (rev 8225.1792)
Console: comconsole (0)
Load Path: /efi\boot\bootaa64.efi
Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x8000,0x10000)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x8000,0x10000)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x01,0,0x18000,0x5e8000)
Setting currdev to disk0p2:
ERROR: cannot open /boot/lua/loader.lua: no such file or directory.
OPNsense 22.7
Starting device manager...Fatal data abort:
x0: 0
x1: ffffa0000758a000
x2: 3
x3: ffff0000da33f650 ($d.10 + d8f61078)
x4: ffff0000da33f5d8 ($d.10 + d8f61000)
<snip>
pcie0: pcie@f8000000 {
<snip>
ranges = <0x83000000 0x0 0xfa000000 0x0 0xfa000000 0x0 0x1e00000
0x81000000 0x0 0xfbe00000 0x0 0xfbe00000 0x0 0x100000>;
<snip>
[snip]
EDIT: After another run, I managed to build the world and kernel successfully.Currently compiling packages – stay tuned for further updates.
Packages also compiled (and took quite a long time) and required a lot of space.
With some little changes, I managed to make an image. Booting worked on my CM4. I won't provide an image here as this was just to see whether compilation works or not
1 │ # Boot from SD/TF Card
2 │ sudo dd if=u-boot/idbloader.img of=/dev/sda conv=sync seek=64 status=progress
3 │ sudo dd if=u-boot/u-boot.itb of=/dev/sda conv=sync seek=16384 status=progress
4 │ sudo dd if=OPNsense-22.1.9-OpenSSL-aarch64-NanoPi-R4S-20220626.img of=/dev/sda conv=sync seek=32768 status=progress
Failed to initialize SPI flash at 0:0 (error
Hi all, excited to join in on the fun here!
I currently have 22.7 running from yrzr.tx on an R4S. I now see from a few posts above that this version is broken so I'll try 22.1.10 shortly. My hope is to replace my hp t730 for home use.
After enabling powerd and setting it to maximum cpu frequency scaling I am able to push around 400mbit in each direction through the unit in cursory iperf3 testing.
I have a Cisco T-Rex benchmarking setup and I plan to do more in depth testing - different packet sizes, number of flows, open states, etc.
When initially testing on openwrt I was able to pin irqs and receive queues for the two nics to the faster A72 cores which was a notable improvement.
Is this possible in opnsense/freebsd? I did a bit of googling and didn't find any definitive answers.
I also have two R4SE's (I dream of HA firewall at home) with 32gb of emmc onboard.
I have tried flashing a few different opnsense images using rkdevtool with no success yet (I didn't really expect it to justwork).
Anyone have any ideas on that? It seems the tool wants the image split into various partitions, but it does allow me to just flash the whole image starting at 0x0.
I haven't dived into the image build process but I'm sure I'll dig into that soon.
I have a 3v3 rs232 adapter on the way so I'll be able to get a console on these things soon.
Anyway, happy to test/help/etc!
I followed what I understood on https://yrzr.tk/opnsense-22-for-aarch64/
but can't get RPI4B system to boot. I don't have a serial adapter so unfortunately can't troubleshoot a lot.
Here is what I did:
Downloaded:
OPNsense-22.1.10-OpenSSL-arm-aarch64-RPI.img.xz
and
OPNsense-22.7.5-OpenSSL-arm-aarch64-RPI.img.xz
Used Raspberry Pi Imager to write the img to file. Renamed config_rpi4.txt to config.txt and deleted config_rpi3.txt . Put the newly flashed card into RPI4 and powered it up. It gets to the rainbow/multicolour splash screen and then nothing. This was the case for both img files, written with either Raspberry Pi Imager or Balena Etcher, unarchived first or provided as .xz to the imager. I tried this on two RPI4.
I tried booting the same card on RPI3B+ with config_rpi3.txt renamed to config.txt and it booted, showing the boot process. I set a static IP and then used config_rpi4.txt renamed to config.txt to boot rpi4. Got the rainbow screen but could still access the system. So there is something wrong with the video.
Is there something wrong with the default config_rpi4.txt? What could I try to get the console to show on hdmi output?
Thanks
I followed what I understood on https://yrzr.tk/opnsense-22-for-aarch64/
but can't get RPI4B system to boot. I don't have a serial adapter so unfortunately can't troubleshoot a lot.
Here is what I did:
Downloaded:
OPNsense-22.1.10-OpenSSL-arm-aarch64-RPI.img.xz
and
OPNsense-22.7.5-OpenSSL-arm-aarch64-RPI.img.xz
Used Raspberry Pi Imager to write the img to file. Renamed config_rpi4.txt to config.txt and deleted config_rpi3.txt . Put the newly flashed card into RPI4 and powered it up. It gets to the rainbow/multicolour splash screen and then nothing. This was the case for both img files, written with either Raspberry Pi Imager or Balena Etcher, unarchived first or provided as .xz to the imager. I tried this on two RPI4.
I tried booting the same card on RPI3B+ with config_rpi3.txt renamed to config.txt and it booted, showing the boot process. I set a static IP and then used config_rpi4.txt renamed to config.txt to boot rpi4. Got the rainbow screen but could still access the system. So there is something wrong with the video.
Is there something wrong with the default config_rpi4.txt? What could I try to get the console to show on hdmi output?
Thanks
I followed what I understood on https://yrzr.tk/opnsense-22-for-aarch64/
but can't get RPI4B system to boot. I don't have a serial adapter so unfortunately can't troubleshoot a lot.
Here is what I did:
Downloaded:
OPNsense-22.1.10-OpenSSL-arm-aarch64-RPI.img.xz
and
OPNsense-22.7.5-OpenSSL-arm-aarch64-RPI.img.xz
Used Raspberry Pi Imager to write the img to file. Renamed config_rpi4.txt to config.txt and deleted config_rpi3.txt . Put the newly flashed card into RPI4 and powered it up. It gets to the rainbow/multicolour splash screen and then nothing. This was the case for both img files, written with either Raspberry Pi Imager or Balena Etcher, unarchived first or provided as .xz to the imager. I tried this on two RPI4.
I tried booting the same card on RPI3B+ with config_rpi3.txt renamed to config.txt and it booted, showing the boot process. I set a static IP and then used config_rpi4.txt renamed to config.txt to boot rpi4. Got the rainbow screen but could still access the system. So there is something wrong with the video.
Is there something wrong with the default config_rpi4.txt? What could I try to get the console to show on hdmi output?
Thanks
Same here (raspberry pi 4 8GB). Tried extracting the xz file before running dd, according to the instructions in https://yrzr.tk/opnsense-22-for-aarch64/#41-writing-the-image, but to no avail.
I can't either get the image to work under qemu, it boots and after I configure the ethernet adapters it hangs completely.
Sadly there is no image for this board, I doubt anyone is working on this device support.
You can ask for help in BPI forum, or ask then to send samples to the team who can help bring up this device support on BSD, freebsd and opnsense.
Regards,
@tryingtotech See these threads for OPNsense on OCI A1 instances. You can download a suitable VM image from my GitHub (see signature).
https://forum.opnsense.org/index.php?topic=34795
https://forum.opnsense.org/index.php?topic=35828
https://forum.opnsense.org/index.php?topic=32546
@tryingtotech See these threads for OPNsense on OCI A1 instances. You can download a suitable VM image from my GitHub (see signature).
https://forum.opnsense.org/index.php?topic=34795
https://forum.opnsense.org/index.php?topic=35828
https://forum.opnsense.org/index.php?topic=32546
Did you enable the Standard.A1.Flex shape for the custom image after importing it?
You first have to add an IPv6 prefix to the VCN subnet, then you can add an IPv6 address to the VNIC of your instance.
Oracle has pretty decent documentation btw. ;)
Initially, you can't easily connect to the OPNsense Web UI using IPv4. That's because of Oracle's use of SNAT and OPNsense's HTTP_REFERER enforcement. Your best option is to access the Web UI via IPv6.
Hi guys,
I'm using opnsense on nanopi-r2s for a year, which is working just fine. The version I have is 22.7 from personalbsd.org. What I'm trying to do is to connect my UPS to the routes (USB cable), so the router would work as a NUT server. The issue is, that I cannot see the NUT plugin. I've tried the original package repo from personalbsd, now I tried yrzr.tk-s repo, but none of them contains this plugin.
I can remember, that in the earlier version (maybe in 19 or 20) it was present, as I played with it on other hardware (rockpi-e). There the connection was for some reason not working, so I stopped the work. Now I would like to try it on the this hardware.
Isn't this package supported? Or is there a way to grab it from somewhere for aarch64?
Thanks!