APU2 Bios
-
@rustydusty1717 Going to try the TinyCore option tonight and see how it goes since doing the update within pfsense doesn't seem to work.
-
@rustydusty1717 Not sure if you've got some pfS version/package mismatches, but it seems OK on 2.5.1-RC from 24th March.
[2.5.1-RC][root@]/root: pkg install -y flashrom Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 3 package(s) will be affected (of 0 checked): New packages to be INSTALLED: flashrom: 1.2 [pfSense] libpci: 3.7.0_1 [pfSense] pciids: 20201127 [pfSense] Number of packages to be installed: 3 The process will require 2 MiB more space. 447 KiB to be downloaded.and
[2.5.1-RC][root@]/tmp: flashrom -w /tmp/apu2_v4.13.0.4.rom -p internal flashrom v1.2 on FreeBSD 12.2-STABLE (amd64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 4, resolution: 2ns). coreboot table found at 0xcfec1000. Found chipset "AMD FCH". Enabling flash write... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. Reading old flash chip contents... done. Erasing and writing flash chip... Warning: Chip content is identical to the requested image. Erase/write done. [2.5.1-RC][root@]/tmp: -
@rustydusty1717 said in APU2 Bios:
Trying to update BIOS on my two APU2 units and this is what I get when trying to install the flashrom package:
pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pkg: Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries:
pkg: Newer FreeBSD version for package pfSense-pkg-zabbix-proxy52:
To ignore this error set IGNORE_OSVERSION=yes- package: 1202504
- running kernel: 1102000
pkg: repository pfSense contains packages for wrong OS version: FreeBSD:12:amd64
Processing entries... done
Unable to update repository pfSense
Error updating repositories!I think your have recently updated to 2.5.0? If so go to System / Update / Update Settings and set it to 2.5.x save and try again.
-
@qinn Nope still on 2.4.4p3 as I've heard 2.5 has lots of issues. Didn't want to upgrade until it was more stable.
-
Just tried using the TinyCore method and this is what I get when trying to use flashrom using the command:
[root@box:/media/TINYCORE]$ flashrom -w /media/SYSLINUX/apu2_v4.13.0.3.rom -p internal
flashrom v0.9.9-r1954-beead91-17 on Linux 4.2.9-tinycore (i686)
flashrom is free software, get the source code at https://flashrom.orgError accessing high tables, 0x100000 bytes at 0x77fce000
/dev/mem mmap failed: Resource temporarily unavailable
Failed getting access to coreboot high tables.
Found chipset "AMD FCH".
Enabling flash write... OK.
Identifying board "PC Engines apu2"... OK.
Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0.
Error: opening file "/media/apu2_v4.13.0.3.rom" failed: No such file or directoy -
@rustydusty1717 pfSense 2.4.4-p3 that was released on 2019-05-20, I do not think there is a feed/repository anymore.
-
@rustydusty1717 said in APU2 Bios:
@qinn Nope still on 2.4.4p3 as I've heard 2.5 has lots of issues. Didn't want to upgrade until it was more stable.
I would not stay on a firewall that's (that) old https://docs.netgate.com/pfsense/en/latest/releases/versions.html and deprecated. When you are on 2.4.4-p3 you're OS is FreeBSD 11.3 (07-2019) pfSense 2.5.0. is on FreeBSD 12.2 (10-2020)
Concerning stability and pfSense 2.5.0. I have no issues. There have been some "speed" issues, meaning not 100% and Wireguard has issues. Well, I don't use Wireguard I am using OpenVPN. With pfSense 2.5.1 Wireguard will be removed.
My advise, first make a backup of your config and than move over (upgrade) to pfSense 2.5.0 and then upgrade the bios to 4.13.0.4 Don't forget to halt the system after every bios upgrade when the system is halted and down remove power cable and wait for 20 sec and power backup.
-
@rustydusty1717 If you're following the PC Engines instructions for upgrading the bios with TinyCore, you've got the syntax wrong:
____ ____ _____ _ | _ \ / ___| | ____|_ __ __ _(_)_ __ ___ ___ | |_) | | | _| | '_ \ / _` | | '_ \ / _ \/ __| | __/| |___ | |___| | | | (_| | | | | | __/\__ \ |_| \____| |_____|_| |_|\__, |_|_| |_|\___||___/ |___/ TinyCore 6.4 www.tinycorelinux.com login[615]: root login on 'ttyS0' waiting for USB being mounted ... Welcome to TinyCore running on PC Engines apu boards To update the BIOS type "flashrom -w apu_xyz.rom -p internal" [+49.6 C][root@box:/media/TINYCORE]$ flashrom -w apu2_v4.13.0.4.rom flashrom v0.9.9-r1954-beead91-17 on Linux 4.2.9-tinycore (i686) flashrom is free software, get the source code at https://flashrom.org Using default programmer "internal" with arguments "". coreboot table found at 0xcfec1000. Found chipset "AMD FCH". Enabling flash write... OK. Identifying board "PC Engines apu2"... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0xff800000. Reading old flash chip contents... done. Erasing and writing flash chip... Warning: Chip content is identical to the requested image. Erase/write done. [+50.0 C][root@box:/media/TINYCORE]$ -
@rustydusty1717 , some of my clients use also APU. Don't connect to internet while updating your BIOS. You need to extract the files on usb and put the exact file name and command line:
flashrom -w apu2_v4.13.0.4.rom -p internalHope this help.
-
I appreciate all the reponses and this involved lots of trial and error on my end. I ended up re-imaging both of the APU2's using the latest 2.5.0 image. Immediately noticed weird things. I game a fair amount and my overall ping had increase upwards of 25%. Using WinMTR I was able to determine it was just my two networks using the APU2's. Using a 3rd network running an old Alix board was way more stable pings and a lot lower. All using same ISP and in same general area.
Ended up rolling both back to 2.4.5-RELEASE-p1 and eventually got bios version v4.13.0.3 installed inside of pfsense using an online guide I found. Everything is back to stable and no inconsistencies. I was also experience OpenVPN issues as the two APU2's have a site to site VPN. Keep in mind my two pfsense boxes are very basic they don't even do DHCP or DNS that is handled by Active Directory at either site.
Not sure why the latest version of Pfsense was causing these issues but will definitely wait until 2.5.x is more stable and widespread before I upgrade again.
-
@rustydusty1717 said in APU2 Bios:
I appreciate all the reponses and this involved lots of trial and error on my end. I ended up re-imaging both of the APU2's using the latest 2.5.0 image. Immediately noticed weird things. I game a fair amount and my overall ping had increase upwards of 25%. Using WinMTR I was able to determine it was just my two networks using the APU2's. Using a 3rd network running an old Alix board was way more stable pings and a lot lower. All using same ISP and in same general area.
Ended up rolling both back to 2.4.5-RELEASE-p1 and eventually got bios version v4.13.0.3 installed inside of pfsense using an online guide I found. Everything is back to stable and no inconsistencies. I was also experience OpenVPN issues as the two APU2's have a site to site VPN. Keep in mind my two pfsense boxes are very basic they don't even do DHCP or DNS that is handled by Active Directory at either site.
Not sure why the latest version of Pfsense was causing these issues but will definitely wait until 2.5.x is more stable and widespread before I upgrade again.
Rat who can swim will leaving a sinking ship first.
-
@akegec Excuse me? I want a reliable setup. If I had money to burn I'd purchase a few more APU2 boards and have a sandbox environment with the same site-to-site vpn setup to test new versions on.
Unfortunately it just doesn't make sense and right now the 'latest version' does not seem reliable. I had immediate negative performance issues that caused me to drive to both sites and flash the old version just to get things working consistently again.
Although this may have nothing to do with any of the issues I experienced it's concerning enough to upgrade to the new version right now:
https://arstechnica.com/gadgets/2021/03/buffer-overruns-license-violations-and-bad-code-freebsd-13s-close-call/
