i have VMware ESXi ARM Fling on raspberry pi4B 8gb , exist ther vmdk or ova for this device ?
Quote from: sharezone on November 23, 2021, 04:34:38 PM
i have VMware ESXi ARM Fling on raspberry pi4B 8gb , exist ther vmdk or ova for this device ?
I don't know if any exists, but you can to create your own image using the opnsense tools.
A good starting point would be here https://github.com/opnsense/tools
You will need some adjustments though, e.g. a slightly modified device config file for you RPi 4B,
adjust some build scripts and so on. I can already tell you that cross compiling the development version 22.1 (based on FreeBSD 13) works for me.
If you don't mind helping me out with some testing (just some basic stuff like stability, booting process, ...) I can provide an image. I won't be able to offer you any repo as I have no means to host one right now, but if the packages are not too large, I could upload them somewhere so that you can download and install them on demand.
PM me if you're interested so that we can talk about further details.
BR
I can provide space for repository and available for testing. have you then installed opnsense on arm fling pi4 8gb?
did you also manage to get openvmtools or vmware tools to work?
I remain at your disposal
Quote from: sharezone on November 30, 2021, 05:48:44 PM
I can provide space for repository and available for testing. have you then installed opnsense on arm fling pi4 8gb?
did you also manage to get openvmtools or vmware tools to work?
I remain at your disposal
In that case, let me setup the packages first (compiling takes a long time). I gave away my RPi 4 and currently own a RPi CM4.
Booting from an sd card works without issues. The image both for the RPi4 and RPi CM4 is essentially the same where the latter just requires an additional line in /etc/rc.conf to boot.
Afaik ESXi-Arm Fling doesn't work on the CM4 (or maybe it does? haven't seen it in the supported devices list). I could test it, but would take some time. Maybe it's easier if I just provide a vmdk image for the RPi4 and you can tell me whether it works or not on ESXi-Arm Fling. I can't say much about open-vm-tools. Technically speaking, it should work and it's also available as FreeBSD port. We won't know unless we try :)
I will let you know once I am done creating the image (should't take too long, I have everything ready more or less).
Can't give you a time for the ports though (might have to face compiling errors etc.). Will get there eventually :)
By the way, do you have any requirements for the image and swap size? The standard is 20G and 1G for swap.
For testing we can just go for smaller values I guess.
UPDATE:For starters I created a vmdk image for you. It boots up fine on my host (amd64) with qemu.
I turned off swap and the image size is 5 GB. Here is the link: https://we.tl/t-QawChIcscD
(Don't get surprised about the small archive size, it's just compressed)
sorry for the delay but my first baby was born.
i try you image but after uncompress i need execute vmkfstools -i sourcedisk.vmdk destdisck.vmk . after this i create a new virtual machine add the exting vmdk disk and now is up .
now how do i set the ip of the gui to access? ..
how can i set ip of interfaces so that i can assign ip and permit you access if you want on SSH
UPDATE
set ip on interface EM0 for internet access and execute pkg update and pkg install open-vm-tools
add on rc.conf the line vmware_guest_vmxnet_enable="YES"
see on vmware "VMware Tools Running, version:2147483647 (Guest Managed) " and the interface vmxnet is up
now i need set interface gui but
Congratulations! You and your family have all my blessings :)
I am glad to hear that the image works for you. As mentioned in my previous post, the image only contains the base and kernel. It was just to see whether it's gonna boot up on your device or not. Since it boots up, we can proceed with the next steps.
Did some research and found out that with open-vm-tools 11.3.0 they added support for arm64 (vmci is not working). You can read more about it here https://github.com/vmware/open-vm-tools/pull/474 and https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm-fling/
As you are not using a graphical desktop, I recommend you to use "open-vm-tools-nox11".
The reason why you don't have a GUI for opnsense is that I haven't built it. There is good news though. I finally managed to build the packages, but ran into some issues (as expected). Apparently some packages required to build the opnsense core depend on "go" where the latter is not build as per settings. I will try to build go and the remaining packages and eventually provide you a final vmdk image.
If you have time and want to get your hands dirty, you can have a look at this repo:
https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.7/latest/All/?C=N&O=A
Most of the packages are available here (my one is missing around 15 of them due to build errors).
thanks so much.
i will absolutely try to get my hands dirty, i like it.
So I await the defined image ok?
I use this thread to update my tests
I managed to solve the build issues. The GUI should be available now. Let me know if this image works for you. If it doesn't, I might have to add a few quirks (wouldn't take long). You can also use the packages as local repo (:
VMDK image: https://we.tl/t-yMPVbYgqnt
Packages: https://we.tl/t-X0K01nBY1V
so ..
- untar the file on datastore
execute on esxi sheel vmkfstool -i source.vmdk target.vmdk
create a new virtual machine
assign vmxnet3 interface
attached disk target.vmdk
start vm success
vm up and running
configure wan interface
enter on GUI with success
delete on /boot/loader.conf the entry hw.uart.console the reboot success
after tesh shutwn not boot show the message "EFI framebuffer information... "
i try to debug but not i understand where is the error
i see on tunable same key not supported see images
GREAAATTT function i removed the unsupported entry from gui and reboot and shutdown funtion .
Not function update . See the image for error
I am glad to hear it worked out in the end. It would be great if you tell me more about overall stability.
Well, updating is not possible which is why I provided you the packages archive. The image I created for you is from the development branch and arm64 is not "officially" supported by opnsense yet. In other words, an official opnsense repo for aarch64 does not exist. The provided image itself is experimental, so you can expect bugs, stability issues etc.
22.1 is scheduled for release in January, but I can't tell how soon official arm64 images will be available. Nevertheless, community builds for different arm devices will for sure be available either on the same day or shortly after.
The packages I uploaded are all up to date (I have compiled them yesterday). If you want to use a small repo to install packages, you can also create your own with the archive I provided you.
For more info and details, feel free to follow this thread:
https://forum.opnsense.org/index.php?topic=12186.0
EDIT: Yeah, I expected you to face these issues (that's my fault actually, I have commented out something inside the code which most likely caused it, but I can easily fix that).
you did a wonderful job. I will start the tests in these days since I have a few hours free. I'll do various tests and update the thread. I keep you informed
UPDATE:
you think is possible include on next build vmdk the opnvmtools
UPDATE TEST:
simple routing ok
routing vlan ok
dmz ok
ha ok
where is possible enable feature
That sounds like a plan! 8)
open-vm-tools-nox11 is actually available in the packages archive. I haven't tried to include certain packages in the image, but what I can do is to simply add these packages to a certain folder (/usr/ports/packages) within the image and create a local repo for you. You can then install the required packages on demand (even without internet access).
So for the next vmdk image, I will just adjust the quirks and add the repo :)
thank .. great
today i execute a revert snapshot and now i hve this problem. i prupose insert in next vmdk image check FS auomatically
Quote from: sharezone on December 05, 2021, 01:00:16 PM
thank .. great
today i execute a revert snapshot and now i hve this problem. i prupose insert in next vmdk image check FS auomatically
Unfortunately, I am not really sure about the cause of the issue. Looks like a limitation of running opnsense inside a virtual machine. I am no expert in this regards. Although, with the right configuration and hypervisor, you can almost reach bare metal performance – there is always some drawbacks (I could write a wiki article about it ;D ).
Your best bet would be taking snapshots through ESXi instead of opnsense and revert to an older snapshot through ESXi.
Regarding the next (most likely final) image. I am not adding any configuration in particular that would break the boot. Keep in mind that the opnsense initialization is also adding configs. Technically speaking you shouldn't have boot issues with a sane "loader.conf" and "rc.conf" – for a VM you most likely want to delete a few things in those manually. One in particular which you also figured out would be deleting the line with "hw.uart.console" or just setting it to hw.uart.console=""
As I a said in the previous post, I will add the packages folder to the image. You can adjust the the repo file manually (I will write down the instructions once I create the image). You can of course also add the official FreeBSD repo, but I won't take any responsibility for any dependency hell :)
UPDATE: Here is the final image: https://we.tl/t-6zrzXJYDkM
To add the local repo, edit the
/usr/local/etc/pkg/repos/OPNsense.conf file:
OPNsense: {
url: "file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
Perform a pkg update and you are set to go
@efetropy, I downloaded your vmdk image, converted it to qcow2 then I imported to my Raspberry Pi 4 with Proxmox and run it on my new VM, it stops on "Hit [Enter] to boot immediately, or any other key for command prompt". Any guess what could beeing happen ?
Quote from: quiOt on December 07, 2021, 01:40:03 PM
@efetropy, I downloaded your vmdk image, converted it to qcow2 then I imported to my Raspberry Pi 4 with Proxmox and run it on my new VM, it stops on "Hit [Enter] to boot immediately, or any other key for command prompt". Any guess what could beeing happen ?
Do you mean getting a black screen (no output) after you hit enter or does the VM completely crash? If it's a complete crash, let me create a qcow2 image for you directly and we can proceed from there. If there is simply not output I suspect something related to the vm configuration in proxmox. If you have a chance to share some logs, the proxmox vm config etc., I would appreciate it :)
What I did:
Downloaded: OPNsense-devel-202112061334-OpenSSL-vm-aarch64.vdmk.tar.xz
Uncompress with xz -d OPNsense-*-OpenSSL-*-aarch64*.*.xz
Extract vmdk file
Converted it to qcow2 with qemu-img convert -f vmdk -O qcow2 OPNsense-*-OpenSSL-vm-aarch64.vmdk OPNsense-out.qcow2
scp file to rpi proxmox server
Created a VM with OVMF bios
imported the qcow2 file to VM with qm importdisk <vm-id> OPNsense-out.qcow2 local
boot VM and lost console connection after this:
(https://i.ibb.co/MkrWD60/proxmox-opnsense-boot.png) (https://ibb.co/CKgN52G)
image hosting for website (https://imgbb.com/)
Now I'm trying to set it up with EXSi ARM fling but when I'm creating the vm file with vmkfstools -i OPNsense-devel-202112061334-OpenSSL-vm-aarch64.vmdk -d thin target.vmdk it prints "Disk is unrepairable.". Now im running vmkfstools -x check.
Edit: after running vmsfstools -x check i got:
Disk needs repair.
Disk is unrepairable.
Disk has scary/unexplainable errors
Edit2: with your previous vmdk ( from November ) i can start the VM.
It's my first time using proxmox/esxi server and opnsense, i will be thankfull if you can give some help offcourse ;)
Thanks!
you installed proxmox or esxi ARM fling ?
i think that this vmdk is corrupted because when i execute the command show this messages
[root@shrarm01:/vmfs/volumes/3679591e-7f04ccfd/Firewall/OPNsense] vmkfstools -i last_update.vmdk last_update_1.vmdk
DiskLib_Check() failed for source disk The file specified is not a virtual disk (15).
[root@shrarm01:/vmfs/volumes/3679591e-7f04ccfd/Firewall/OPNsense]
on the tree folder i see
GNUSparseFile.0
i suppose missing descriptor file or *-flat.vmdk file
Quote from: sharezone on December 10, 2021, 12:49:48 PM
you installed proxmox or esxi ARM fling ?
I tried both and i could only boot with esxi but didn't had network interfaces working even with manually configured interfaces.
Quote from: sharezone on December 10, 2021, 01:08:00 PM
i think that this vmdk is corrupted because when i execute the command show this messages
[root@shrarm01:/vmfs/volumes/3679591e-7f04ccfd/Firewall/OPNsense] vmkfstools -i last_update.vmdk last_update_1.vmdk
DiskLib_Check() failed for source disk The file specified is not a virtual disk (15).
[root@shrarm01:/vmfs/volumes/3679591e-7f04ccfd/Firewall/OPNsense]
on the tree folder i see
GNUSparseFile.0
i suppose missing descriptor file or *-flat.vmdk file
I reacreated the image: https://sendgb.com/5xMlT13Xcpq (VMDK, this time no other compression)
Quote from: quiOt on December 10, 2021, 05:38:28 PM
Quote from: sharezone on December 10, 2021, 12:49:48 PM
you installed proxmox or esxi ARM fling ?
I tried both and i could only boot with esxi but didn't had network interfaces working even with manually configured interfaces.
Which kind of network interface are you using?
this last image works without problem . i resubmit the test
i use vmxnet3 without problem
UPDATE
i have this entry on file
OPNsense: {
fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
url: "pkg+https://pkg.opnsense.org/${ABI}/22.1/latest",
signature_type: "fingerprints",
mirror_type: "srv",
priority: 11,
enabled: yes
}
i replace with
Code: [Select]
OPNsense: {
url: "file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
or add
Just replace it :-)
This repo
url: "pkg+https://pkg.opnsense.org/${ABI}/22.1/latest",
doesn't actually exist
i replaced
root@OPNsense:~ # cat /usr/local/etc/pkg/repos/OPNsense.conf
OPNsense: {
url: "file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
root@OPNsense:~ # pkg update
Updating OPNsense repository catalogue...
Fetching meta.conf: 100% 163 B 0.2kB/s 00:01
Fetching packagesite.txz: 100% 192 KiB 196.4kB/s 00:01
Processing entries: 100%
OPNsense repository update completed. 647 packages processed.
All repositories are up to date.
root@OPNsense:~ #
now why not see plugin ??
Quote from: sharezone on December 11, 2021, 02:07:56 PM
i replaced
root@OPNsense:~ # cat /usr/local/etc/pkg/repos/OPNsense.conf
OPNsense: {
url: "file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
root@OPNsense:~ # pkg update
Updating OPNsense repository catalogue...
Fetching meta.conf: 100% 163 B 0.2kB/s 00:01
Fetching packagesite.txz: 100% 192 KiB 196.4kB/s 00:01
Processing entries: 100%
OPNsense repository update completed. 647 packages processed.
All repositories are up to date.
root@OPNsense:~ #
now why not see plugin ??
I can see that the local repo is initialized. You should be able to install packages from the command line.
Why the plugins tab doesn't work in the GUI, is something I have no answer to. Can you see packages in the "packages" tab?
If yes, maybe I messed up something with the plugins (which I doubt). If the answer is no, maybe the core package does not support local repos in general. I haven't tested it, so can't tell. Someone else with experience might be able to help you better in that case.
There is one other thing you could try though. Just use a local webserver either within opnsense itself or since you are using ESXi, use a second VM (FreeBSD, Linux, or whatever you prefer). Make sure the webserver is reachable from opnsense. You already have the folder structure, so it should be easy. One you're set, just adjust the url of the repo config.
Btw., can you just change the url to
url: "pkg+file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest"and see if it works?
on firmware >> packages i see packet
Quote from: sharezone on December 13, 2021, 03:54:56 PM
on firmware >> packages i see packet
That's how it should be. Under packages you see the installed packages. That means no issues with the GUI.
Looks like the local repo is causing problems. As mentioned earlier, just try to setup a webserver and create your own repo.
Should work that way :-)
I have server web ,private and public , but i don't know configure the repository. Can you help me ?
Thanks
Quote from: sharezone on December 14, 2021, 04:31:07 AM
I have server web ,private and public , but i don't know configure the repository. Can you help me ?
Thanks
The local repo I created for you has the same folder structure as https://ftp.yrzr.tk/ and is available under /usr/ports/packages/
All you gotta do is serve these folders/files in your webserver. In the end the url would be something like
url: "https://[IP]/opnsense/FreeBSD:13:aarch64/21.7.6/latest"
where IP is your webserver
i configure web site repository on url https://opnsense.sharezone.cloud/ and change the file
/usr/local/etc/pkg/repos/OPNsense.conf
on
OPNsense: {
url: "https://opnsense.sharezone.cloud/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
but when i execute "pkg update" return error "Segmentation fault"
root@OPNsense:/usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest # pkg update
Updating OPNsense repository catalogue...
Fetching meta.conf: 100% 163 B 0.2kB/s 00:01
Fetching packagesite.txz: 100% 192 KiB 196.4kB/s 00:01
Child process pid=17426 terminated abnormally: Segmentation fault
where may be the problem
i try with
OPNsense: {
url: "pkg+https://opnsense.sharezone.cloud/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
but the problem is the same
i have another issue on file system but i think that the problem is on version esxi because
i read that problem is on version esxi arm with usb datastore.
i have
ESXi Version 7.0.0
Hypervisor VMware ESXi
Build 17230755
and on Build 19025766 (https://flings.vmware.com/esxi-arm-edition#changelog)
"Improve USB stability issues, especially with RTL8153-based USB NICs (a common chipset) and especially on Raspberry Pi and Tegra Xavier"
i try and update the thread
Did you by any chance update the pkg? Would be interesting to see which version you have. Just type "pkg -v" in the console. Maybe there is some sort of incompatibility (there were some recent changes). We can eventually debug and backtrace the problem. I have also hardcoded the ABI in the url, can you also try the following:
https://opnsense.sharezone.cloud/opnsense/${ABI}/21.7.6/latest"
Eventually relocate that folder (or remove it alltogether) from your local disk and reset pkg.
Regarding your USB problem. I guess you're trying to use a USB to Ethernet adapter with RTL8153 chip. What do you mean by filesystem issue? If you elaborate, maybe we can figure out something.
root@OPNsense:/var/log # pkg -v
1.16.3
root@OPNsense:/var/log # cat /usr/local/etc/pkg/repos/OPNsense.conf
OPNsense: {
url: "https://opnsense.sharezone.cloud/opnsense/${ABI}/21.7.6/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
same issue
root@OPNsense:/var/log # pkg update
Updating OPNsense repository catalogue...
Child process pid=9364 terminated abnormally: Segmentation fault
root@OPNsense:/var/log #
what do you mean "Eventually relocate that folder (or remove it alltogether) from your local disk and reset pkg.
"
delete all file and folder under /usr/ports/packages/
Indeed either delete the files or move the folder with its contents to some other place.
Did you also try pkg upgrade followed by pkg update? It's weird that you're getting a segmentation fault.
With the local repo, you didn't have this issue. It looks like the ports database is corrupted for whatever reason.
Did you try anything else before changing to the repo to your webserver?
i rename the folder opnsense under /usr/ports/packages on opnsenseold
execute
root@OPNsense:~ # pkg upgrade
Updating OPNsense repository catalogue...
Child process pid=68697 terminated abnormally: Segmentation fault
same issue .
I have not done any operation. I also tried to put back the original vmdk but same error.
i resubmint the original confiuration
OPNsense: {
url: "file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
but nothing .
i can't figure out where the problem is
Quote from: sharezone on December 17, 2021, 05:34:42 PM
i rename the folder opnsense under /usr/ports/packages on opnsenseold
execute
root@OPNsense:~ # pkg upgrade
Updating OPNsense repository catalogue...
Child process pid=68697 terminated abnormally: Segmentation fault
same issue .
I have not done any operation. I also tried to put back the original vmdk but same error.
i resubmint the original confiuration
OPNsense: {
url: "file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
signature_type: "NONE",
mirror_type: "NONE",
priority: 11,
enabled: yes
}
but nothing .
i can't figure out where the problem is
Can you change the mirror type to "srv" or "http" and try again?
nothing . i try both "srv" and "http" but same issue .
Bu if you try on your version with my public repository , funtion ?
Hello @efetropy,
Can you share the patches required to build opnsense 22.1 for a Raspberry Pi 4? I'd like to help with this.
I'm just getting started and have finally understood how to build it but missing the specific configuration for RPI4.
Quote from: efetropy on November 24, 2021, 07:03:43 AM
I don't know if any exists, but you can to create your own image using the opnsense tools.
A good starting point would be here https://github.com/opnsense/tools
You will need some adjustments though, e.g. a slightly modified device config file for you RPi 4B,
adjust some build scripts and so on. I can already tell you that cross compiling the development version 22.1 (based on FreeBSD 13) works for me.
Dear all,
Currently, I have a CM4 (with 4GB RAM and 8GB eMMC and no Wifi) and the DFRobot IoT Router Carrier Board (https://www.dfrobot.com/product-2242.html).
I am interested to compile an OPNsense build for this hardware but I am a little bit lost about it's potential compatibility.
Can someone confirm me that's this will be good or not?
Many thanks in advance!
Hi,
Thanks for the work you have done with arm64/UEFI!
I run pimox7 on pi4 adn I was hoping to test your image.
Is there an updated location or image? All links seem dead.
Thanks!
EDIT: an image for EXSI works great with pimox7, just a conversion away. It mainly need proper UEFI boot.
Sorry for the late reply!
Was busy with other stuff lately, had little to no time and to totally forgot to reply.
Quote from: yolocoffee on January 08, 2022, 12:20:11 PM
Hello @efetropy,
Can you share the patches required to build opnsense 22.1 for a Raspberry Pi 4? I'd like to help with this.
I'm just getting started and have finally understood how to build it but missing the specific configuration for RPI4.
Quote from: john_matrix on January 24, 2022, 04:44:38 PM
Dear all,
Currently, I have a CM4 (with 4GB RAM and 8GB eMMC and no Wifi) and the DFRobot IoT Router Carrier Board (https://www.dfrobot.com/product-2242.html).
I am interested to compile an OPNsense build for this hardware but I am a little bit lost about it's potential compatibility.
Can someone confirm me that's this will be good or not?
Many thanks in advance!
There is already an image built by @yrzr for the RPi which can be found here:
https://ftp.yrzr.tk/opnsense/FreeBSD%3A13%3Aaarch64/22.1/images/
A generic aarch64 vmdk image is also available (for e.g. for proxmox, esxi fling or whatever you're using).
The RPi 4B should work without problems (if not, just get some different boot files).
CM4 is a different case. It does work with the official I/O board albeit PCIe issues (see bugzilla).
Your carrier board states ETH2: PCI Express 1000BASE-T NIC (based on RTL8111). RTL8111 drivers are in fact available, but
it will be a hit or miss and you might not be able to the use the 2nd ethernet port due to the mentioned PCIe issues.
Furthermore, you have to figure out how to deal with the dtb file. Worst case scenario, you might have to make it compatible with freebsd.
Thank you! Downloading to test on my little proxmox.
Anyone had a similar boot problem?
Thanks!
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: 0xb82ff000
EFI version: 2.70
EFI Firmware: EDK II (rev 1.00)
Console: efi (0x20000000)
\
______ _____ _____
/ __ |/ ___ |/ __ |
| | | | |__/ | | | |___ ___ _ __ ___ ___
| | | | ___/| | | / __|/ _ \ '_ \/ __|/ _ \
| |__| | | | | | \__ \ __/ | | \__ \ __/
|_____/|_| |_| /__|___/\___|_| |_|___/\___|
/-----------------------------------------\ @@@@@@@@@@@@@@@@@@@@@@@@@@@@
| | @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
| 1. Boot Multi user [Enter] | @@@@@ @@@@@
| 2. Boot Single user | @@@@@ @@@@@
| 3. Escape to loader prompt | @@@@@@@@@@@ @@@@@@@@@@@
| Autoboot in 0 seconds. [Space] to pause | \\\\\ /////
| 5. Cons: Dual (Video primary) | )))))))))))) (((((((((((
Loading kernel... | ///// \\\\\
/boot/kernel/kernel text=0x2a8 text=0x924830 text=0x219e64 data=0x1b21c8 data=0x0+0x36a000 syms=[0x8+0x1312e0+0x8+0x156774]
Loading configured modules... (1 of 1) | @@@@@ @@@@@
/boot/kernel/if_enc.ko text=0x15ca text=0x934 data=0x750 syms=[0x8+0xca8+0x8+0xb71]
/boot/kernel/if_bridge.ko text=0x3677 text=0x7168 data=0xd38+0x8 syms=[0x8+0x1b90+0x8+0x15b5]
loading required module 'bridgestp' | @@@@@@@@@@@@@@@@@@@@@@@@@@@@
/boot/kernel/bridgestp.ko text=0x12e4 text=0x4acc data=0x2c8+0x28 syms=[0x8+0xb88+0x8+0x6e9]
/etc/hostid size=0x25nds. [Space] to pause
/boot/kernel/pf.ko text=0xe344 text=0x3dc7c data=0x59c0+0x39c syms=[0x8+0x5910+0x8+0x46ec]
/boot/kernel/pflog.ko text=0xf78 text=0x898 data=0x430 syms=[0x8+0x9f0+0x8+0x712]
/boot/kernel/if_gre.ko text=0x2736 text=0x4938 data=0x8c8+0x40 syms=[0x8+0x16f8+0x8+0xfaf]
/boot/kernel/if_lagg.ko text=0x3c93 text=0xa41c data=0xd08+0x8 syms=[0x8+0x1c80+0x8+0x15a6]
loading required module 'if_infiniband'
/boot/kernel/if_infiniband.ko text=0x1102 text=0x10fc data=0x300+0x8 syms=[0x8+0x8d0+0x8+0x59a]
/boot/entropy size=0x1000
/boot/kernel/carp.ko text=0x33ec text=0x6e54 data=0xc60+0x48 syms=[0x8+0x1980+0x8+0x1225]
/boot/kernel/pfsync.ko text=0x2f1c text=0x7b24 data=0xb30+0x8 syms=[0x8+0x1800+0x8+0x117d]
No valid device tree blob found!
WARNING! Trying to fire up the kernel, but no device tree blob found!
EFI framebuffer information:
addr, size 0x0, 0x0
dimensions 0 x 0
stride 0
masks 0x00000000, 0x00000000, 0x00000000, 0x00000000
Quote from: daemonix on February 13, 2022, 08:23:15 PM
Anyone had a similar boot problem?
Thanks!
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: 0xb82ff000
EFI version: 2.70
EFI Firmware: EDK II (rev 1.00)
Console: efi (0x20000000)
\
______ _____ _____
/ __ |/ ___ |/ __ |
| | | | |__/ | | | |___ ___ _ __ ___ ___
| | | | ___/| | | / __|/ _ \ '_ \/ __|/ _ \
| |__| | | | | | \__ \ __/ | | \__ \ __/
|_____/|_| |_| /__|___/\___|_| |_|___/\___|
/-----------------------------------------\ @@@@@@@@@@@@@@@@@@@@@@@@@@@@
| | @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
| 1. Boot Multi user [Enter] | @@@@@ @@@@@
| 2. Boot Single user | @@@@@ @@@@@
| 3. Escape to loader prompt | @@@@@@@@@@@ @@@@@@@@@@@
| Autoboot in 0 seconds. [Space] to pause | \\\\\ /////
| 5. Cons: Dual (Video primary) | )))))))))))) (((((((((((
Loading kernel... | ///// \\\\\
/boot/kernel/kernel text=0x2a8 text=0x924830 text=0x219e64 data=0x1b21c8 data=0x0+0x36a000 syms=[0x8+0x1312e0+0x8+0x156774]
Loading configured modules... (1 of 1) | @@@@@ @@@@@
/boot/kernel/if_enc.ko text=0x15ca text=0x934 data=0x750 syms=[0x8+0xca8+0x8+0xb71]
/boot/kernel/if_bridge.ko text=0x3677 text=0x7168 data=0xd38+0x8 syms=[0x8+0x1b90+0x8+0x15b5]
loading required module 'bridgestp' | @@@@@@@@@@@@@@@@@@@@@@@@@@@@
/boot/kernel/bridgestp.ko text=0x12e4 text=0x4acc data=0x2c8+0x28 syms=[0x8+0xb88+0x8+0x6e9]
/etc/hostid size=0x25nds. [Space] to pause
/boot/kernel/pf.ko text=0xe344 text=0x3dc7c data=0x59c0+0x39c syms=[0x8+0x5910+0x8+0x46ec]
/boot/kernel/pflog.ko text=0xf78 text=0x898 data=0x430 syms=[0x8+0x9f0+0x8+0x712]
/boot/kernel/if_gre.ko text=0x2736 text=0x4938 data=0x8c8+0x40 syms=[0x8+0x16f8+0x8+0xfaf]
/boot/kernel/if_lagg.ko text=0x3c93 text=0xa41c data=0xd08+0x8 syms=[0x8+0x1c80+0x8+0x15a6]
loading required module 'if_infiniband'
/boot/kernel/if_infiniband.ko text=0x1102 text=0x10fc data=0x300+0x8 syms=[0x8+0x8d0+0x8+0x59a]
/boot/entropy size=0x1000
/boot/kernel/carp.ko text=0x33ec text=0x6e54 data=0xc60+0x48 syms=[0x8+0x1980+0x8+0x1225]
/boot/kernel/pfsync.ko text=0x2f1c text=0x7b24 data=0xb30+0x8 syms=[0x8+0x1800+0x8+0x117d]
No valid device tree blob found!
WARNING! Trying to fire up the kernel, but no device tree blob found!
EFI framebuffer information:
addr, size 0x0, 0x0
dimensions 0 x 0
stride 0
masks 0x00000000, 0x00000000, 0x00000000, 0x00000000
Do you have hw.uart.console="" in loader.conf.local under /boot? If not create the file and add that line.
Quote from: efetropy on February 11, 2022, 12:18:21 PM
Sorry for the late reply!
Was busy with other stuff lately, had little to no time and to totally forgot to reply.
Quote from: yolocoffee on January 08, 2022, 12:20:11 PM
Hello @efetropy,
Can you share the patches required to build opnsense 22.1 for a Raspberry Pi 4? I'd like to help with this.
I'm just getting started and have finally understood how to build it but missing the specific configuration for RPI4.
Quote from: john_matrix on January 24, 2022, 04:44:38 PM
Dear all,
Currently, I have a CM4 (with 4GB RAM and 8GB eMMC and no Wifi) and the DFRobot IoT Router Carrier Board (https://www.dfrobot.com/product-2242.html).
I am interested to compile an OPNsense build for this hardware but I am a little bit lost about it's potential compatibility.
Can someone confirm me that's this will be good or not?
Many thanks in advance!
There is already an image built by @yrzr for the RPi which can be found here:
https://ftp.yrzr.tk/opnsense/FreeBSD%3A13%3Aaarch64/22.1/images/
A generic aarch64 vmdk image is also available (for e.g. for proxmox, esxi fling or whatever you're using).
The RPi 4B should work without problems (if not, just get some different boot files).
CM4 is a different case. It does work with the official I/O board albeit PCIe issues (see bugzilla).
Your carrier board states ETH2: PCI Express 1000BASE-T NIC (based on RTL8111). RTL8111 drivers are in fact available, but
it will be a hit or miss and you might not be able to the use the 2nd ethernet port due to the mentioned PCIe issues.
Furthermore, you have to figure out how to deal with the dtb file. Worst case scenario, you might have to make it compatible with freebsd.
I can confirm that the 22.1 image made by YRZR works with DFrobot carrier board with CM4 with 8GB Ram. Unfortunately the performance is only around 300Mb/s on 1Gb connection. Maybe some tuning needed to get better results. The cpu was only at 40% during downloads. Has anyone got better performance?
Quote from: efetropy on December 02, 2021, 04:00:13 PM
Did some research and found out that with open-vm-tools 11.3.0 they added support for arm64 (vmci is not working). You can read more about it here https://github.com/vmware/open-vm-tools/pull/474 and https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm-fling/
Hey, thanks for referencing my work! Hopefully it has helped you all out. :)
I've been running earlier builds of OPNsense under ESXi ARM Fling for probably at least a year now. I guess it is about time I update to these new builds you are all putting together! :D
I'll have to switch my 16-core ARM server back over from FreeBSD bare metal to running ESXi ARM Fling instead, and see what kind of bandwidth that thing can push with dual-10gbe NICs.
Hi all,
Interesting post, I'll give this a go when I have a little time next month. How's throughput on a pi4 8gb, above 500mb?
Thanks for your efforts.
Quote from: efetropy on February 15, 2022, 01:24:21 AM
Quote from: daemonix on February 13, 2022, 08:23:15 PM
Anyone had a similar boot problem?
Thanks!
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: 0xb82ff000
EFI version: 2.70
EFI Firmware: EDK II (rev 1.00)
Console: efi (0x20000000)
\
______ _____ _____
/ __ |/ ___ |/ __ |
| | | | |__/ | | | |___ ___ _ __ ___ ___
| | | | ___/| | | / __|/ _ \ '_ \/ __|/ _ \
| |__| | | | | | \__ \ __/ | | \__ \ __/
|_____/|_| |_| /__|___/\___|_| |_|___/\___|
/-----------------------------------------\ @@@@@@@@@@@@@@@@@@@@@@@@@@@@
| | @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
| 1. Boot Multi user [Enter] | @@@@@ @@@@@
| 2. Boot Single user | @@@@@ @@@@@
| 3. Escape to loader prompt | @@@@@@@@@@@ @@@@@@@@@@@
| Autoboot in 0 seconds. [Space] to pause | \\\\\ /////
| 5. Cons: Dual (Video primary) | )))))))))))) (((((((((((
Loading kernel... | ///// \\\\\
/boot/kernel/kernel text=0x2a8 text=0x924830 text=0x219e64 data=0x1b21c8 data=0x0+0x36a000 syms=[0x8+0x1312e0+0x8+0x156774]
Loading configured modules... (1 of 1) | @@@@@ @@@@@
/boot/kernel/if_enc.ko text=0x15ca text=0x934 data=0x750 syms=[0x8+0xca8+0x8+0xb71]
/boot/kernel/if_bridge.ko text=0x3677 text=0x7168 data=0xd38+0x8 syms=[0x8+0x1b90+0x8+0x15b5]
loading required module 'bridgestp' | @@@@@@@@@@@@@@@@@@@@@@@@@@@@
/boot/kernel/bridgestp.ko text=0x12e4 text=0x4acc data=0x2c8+0x28 syms=[0x8+0xb88+0x8+0x6e9]
/etc/hostid size=0x25nds. [Space] to pause
/boot/kernel/pf.ko text=0xe344 text=0x3dc7c data=0x59c0+0x39c syms=[0x8+0x5910+0x8+0x46ec]
/boot/kernel/pflog.ko text=0xf78 text=0x898 data=0x430 syms=[0x8+0x9f0+0x8+0x712]
/boot/kernel/if_gre.ko text=0x2736 text=0x4938 data=0x8c8+0x40 syms=[0x8+0x16f8+0x8+0xfaf]
/boot/kernel/if_lagg.ko text=0x3c93 text=0xa41c data=0xd08+0x8 syms=[0x8+0x1c80+0x8+0x15a6]
loading required module 'if_infiniband'
/boot/kernel/if_infiniband.ko text=0x1102 text=0x10fc data=0x300+0x8 syms=[0x8+0x8d0+0x8+0x59a]
/boot/entropy size=0x1000
/boot/kernel/carp.ko text=0x33ec text=0x6e54 data=0xc60+0x48 syms=[0x8+0x1980+0x8+0x1225]
/boot/kernel/pfsync.ko text=0x2f1c text=0x7b24 data=0xb30+0x8 syms=[0x8+0x1800+0x8+0x117d]
No valid device tree blob found!
WARNING! Trying to fire up the kernel, but no device tree blob found!
EFI framebuffer information:
addr, size 0x0, 0x0
dimensions 0 x 0
stride 0
masks 0x00000000, 0x00000000, 0x00000000, 0x00000000
Do you have hw.uart.console="" in loader.conf.local under /boot? If not create the file and add that line.
Whats the best way to mount the image? Im not sure how to edit loader.conf.local
Quote from: Joonas42 on February 17, 2022, 09:46:36 PM
I can confirm that the 22.1 image made by YRZR works with DFrobot carrier board with CM4 with 8GB Ram. Unfortunately the performance is only around 300Mb/s on 1Gb connection. Maybe some tuning needed to get better results. The cpu was only at 40% during downloads. Has anyone got better performance?
Thank you very much, I will take a look on this ;-)
Edit: testing cannot continue as I cannot boot on CM4 + DFRobot Mini router board :(
Quote from: efetropy on February 11, 2022, 12:18:21 PM
Sorry for the late reply!
Was busy with other stuff lately, had little to no time and to totally forgot to reply.
Quote from: yolocoffee on January 08, 2022, 12:20:11 PM
Hello @efetropy,
Can you share the patches required to build opnsense 22.1 for a Raspberry Pi 4? I'd like to help with this.
I'm just getting started and have finally understood how to build it but missing the specific configuration for RPI4.
Quote from: john_matrix on January 24, 2022, 04:44:38 PM
Dear all,
Currently, I have a CM4 (with 4GB RAM and 8GB eMMC and no Wifi) and the DFRobot IoT Router Carrier Board (https://www.dfrobot.com/product-2242.html).
I am interested to compile an OPNsense build for this hardware but I am a little bit lost about it's potential compatibility.
Can someone confirm me that's this will be good or not?
Many thanks in advance!
There is already an image built by @yrzr for the RPi which can be found here:
https://ftp.yrzr.tk/opnsense/FreeBSD%3A13%3Aaarch64/22.1/images/
A generic aarch64 vmdk image is also available (for e.g. for proxmox, esxi fling or whatever you're using).
The RPi 4B should work without problems (if not, just get some different boot files).
CM4 is a different case. It does work with the official I/O board albeit PCIe issues (see bugzilla).
Your carrier board states ETH2: PCI Express 1000BASE-T NIC (based on RTL8111). RTL8111 drivers are in fact available, but
it will be a hit or miss and you might not be able to the use the 2nd ethernet port due to the mentioned PCIe issues.
Furthermore, you have to figure out how to deal with the dtb file. Worst case scenario, you might have to make it compatible with freebsd.
Trying to get the 22.1.10 build working on my RPI4B 4GB but it does not book.
Can you advise how to get a working build for the RPI4?
Cheers