Messages

I'd be more than happy to help test! I've got several RPI3 boards gathering dust.

If I get some spare time this week and/or next, I'll test on the RPI3.

Hi lattera,

the Attached Image ist the boot Screen and the Settings (German)
Secure Boot is of.

Thanks for helping! What are the specs for your hardware? I'm primarily curious about CPU make and model.

The ISO has been uploaded here: https://hardenedbsd.org/~shawn/opnsense/2019-03-26_hbsd_11-stable_disc1.iso

Can anyone interesting in running OPNsense 19.1 in a Hyper-V Gen2 instance please test?

I'll just leave this here. :)

Test ISO coming soon.

Can you post a screenshot of the panic?

When you're at the boot prompt (after selecting option 3), type this in:

set vm.pmap.pti="0"
boot

Oh, I posted this in the wrong thread, see below.

@bimmeldriver yes please, installer may hang but CTRL+C should work around it ok.

So this is the preliminary amd64 ISO for 19.1.4. It can be used in production and upgrades normally...

https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/OPNsense-19.1.4-OpenSSL-dvd-amd64.iso.bz2

All images, checksums and the announcement follow next week when we will have wrapped up testing image integrity for all other images (it takes about 2 days in total to do that).


Cheers,
Franco

First I want to say thanks for all the hard work put into this outstanding software!

I downloaded the ISO and burned it to a DVD.  When I boot from the DVD, it reboots over and over.  It does load the Kernel modules and then shows Booting.  The screen refreshes and looks like it is starting up and then that is when the computer restarts.  I even tried the Safe Mode and that didn't help.

The DVD Reader isn't that old while my Motherboard, Processor and RAM are.
Motherboard:  ASUS M4A785-M
Processor:  AMD Athlon II X2 245 Speed 2900Mhz
RAM: 8GB

The bios on the Motherboard is up to date.

Thanks,
Charles

I believe setting `vm.pmap.pti=0` at the boot prompt will solve your boot loop issue. Once your system is booted, you can set that permanently via the GUI or via manual edit of /boot/loader.conf.local

Oh, I posted this in the wrong thread, see below.

@bimmeldriver yes please, installer may hang but CTRL+C should work around it ok.

So this is the preliminary amd64 ISO for 19.1.4. It can be used in production and upgrades normally...

https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/OPNsense-19.1.4-OpenSSL-dvd-amd64.iso.bz2

All images, checksums and the announcement follow next week when we will have wrapped up testing image integrity for all other images (it takes about 2 days in total to do that).


Cheers,
Franco

Franco/Lattera,

I will dedicate a few VM's on my side to test upgrades and installs for 18.7 to 19.1 and 19.1 to 19.7 on the QEMU/KVM platform. Willing to help out as much as I can.

Let me know if the upgrade images are ready for 18.7 to 19.1.4 and I will test that also.

Not sure I have any "baremetal" equipment to use in testing except some old Dell's.

Thanks again.

-Waz

Thank you very much! Your offer of assistance really means a lot to me. I've got a busy weekend as my wife has planned a few special events. I'll likely get back to tracking down the kernel NX bug seen mostly on Hyper-V systems and some Dell systems on Tuesday of next week. Each time I build a new HardenedBSD 11-stable ISO, I will let you know for your own testing. All I need to know is if it boots to the installer, no need to actually perform the install. I can also upload a memstick image so you don't have to dust off dvd discs. ;)

The HardenedBSD team is looking at this. Thanks for the report!

Gotcha. Once I'm finished with the Hyper-V issues, I'll take a look at how opnsense's updater works and take the discussion private with some potential solutions for the team to discuss.

Franco,

Thanks for the clarification! Would you like me to file a feature request in github for teaching opnsense's updater how to display multiple changelogs?

I kinda wonder if it'd be best to show all changelogs from 19.1 to 19.1.4.

Here's why OPNsense switched from FreeBSD to HardenedBSD: https://github.com/HardenedBSD/hardenedBSD/wiki

Sorry, I meant to write: vm.pmap.pti=0

What happens when you set vm.pti=0?