PC Engines apu2 experiences

Qinn

@dem Thanks for the quick reply, I understand that.
What I would like to know is how you get to the Virtual pfSense from here as the virtual pfsense machine is not running and access the checkpoint you made?

Btw I am using VM workstation!

dem

@qinn Sorry I wasn't clear: I put the installer image into the virtual optical drive of the same virtual pfSense instance that I checkpointed, so the installer has access to the same virtual disk and can locate the checkpointed zroot pool.

Edited to add: My goal was to simulate booting an apu2 from the memstick image in order to rewind a checkpoint, but I don't have a spare apu2 to test with. If I actually ran pfSense in a virtual machine I would use virtual machine snapshots before any upgrade.

VAMike

@qinn I never would have guessed this was somehow specific to the apu2

dem

@vamike It's not, but @vollans rolled back an upgrade of his apu2 using ZFS and that sparked interest in using ZFS to recover from a failed upgrade.

VAMike

@dem so he should start another thread so that people actually interested in apu2 experiences can find those without digging through unrelated zfs support questions

Vollans

@vamike I agreed it wasn't relevant here 2 days ago, and stopped responding.

sikita

Why pfsense 2.5 shows "AES-NI CPU Crypto: No" when in 2.4.x there was YES on APU2? Also on 2.5 there is in other line: Hardware crypto AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS

bigsy

@sikita said in PC Engines apu2 experiences:

Why pfsense 2.5 shows "AES-NI CPU Crypto: No" when in 2.4.x there was YES on APU2?

Anything to do with this problem? If so, it appears to be fixed in 2.5.1.

sikita

@bigsy Ok, thank you. Seems to be GUI bug and does not involve using HW crypto.

Qinn

@sikita I am on pfSense 2.5.0 and here it says:

Firefox_Screenshot_2021-03-12T16-51-01.718Z.png

Do you have AES-NI enabled?

Qinn

Can anyone share there System / Advanced / Networking on a APU2

Mine are

Firefox_Screenshot_2021-03-19T11-29-42.923Z.png

as these are the defaults, grabbed them from a VM installation, which is not quit the same setup.

The old and not anymore recommend settings from https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/ are quit different!

...and there is a new settings present in 2.5.0. " hn ALTQ support"

Could anyone elaborate on all these or there settings?

stephenw10

There are no hn NICs on any APU so it makes no difference. You can disable it.

Steve

valnar

I performed all the bootloader and other tweaks mentioned in various threads throughout the years on my <= 2.45-p1 installation and now I don't remember what they all are. It would be great if somebody could post what things to look for (to remove?) when you update your apu2 from 2.4.5 --> 2.5.0.

At the moment because of the performance issues, I'm not upgrading.

DaddyGo

@valnar said in PC Engines apu2 experiences:

when you update your apu2 from 2.4.5 --> 2.5.0.

Hi,

With that, I would wait a little longer

here,....you will find a lot of useful info if you even decide to upgrade...
https://teklager.se/en/knowledge-base/
https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/

+++edit:
and of course
https://pcengines.github.io/

Qinn

Smooth update to pfSense 2.5.1 CE

Qinn

Updated to bios coreboot v4.13.05.

FLOK

@qinn Fine !
I am still on 2.4.5_1.
Did you notice any performance degradation ?

Qinn

@flok No, so far not.

kevindd992002

I received an email notification about v4.14.0.2 and this IMPORTANT message was included:

To update the firmware and keep the runtime configuration unchanged please use the following command:
flashrom -p internal -w apuX_v4.14.0.2.rom --fmap -i COREBOOT
The persistent runtime configuration works only when migrating from versions v4.14.0.1 and later. The feature is not yet supported on apu1. Flashrom version needs to be v1.1 or newer.

I did the upgrade from v4.14.0.1 with that new command without any issues. However, for the longest time this is what I've been using:

flashrom -p internal -w apuX_v4.14.0.2.rom

What is the difference?

bigsy

@kevindd992002
I'm not by any means an expert on coreboot, but

flashrom -p internal -w apuX_v4.14.0.2.rom

will overwrite the entire flash chip with the new rom file.

flashrom -p internal -w apuX_v4.14.0.2.rom --fmap -i COREBOOT

The flash chip has various partitions defined in a 'flashmap' format and this command specifies which area to overwrite. This probably allows for user altered settings such as seabios boot order changes to persist and not get overwritten during the coreboot update, but I haven't tried it out.