Previously, to update PCEngines APUs I used these commands:
flashrom -p internal:boardmismatch=force -w apu2_v18.104.22.168.rom
And everything was updated correctly (it was nice).
Now when I try to do the same process with the “IPFire 2.27 (x86_64) - Core Update 164” it gives me this error:
[root@bs ~]# wget https://3mdeb.com/open-source-firmware/pcengines/apu2/apu2_v22.214.171.124.rom
--2022-03-31 15:03:42-- https://3mdeb.com/open-source-firmware/pcengines/apu2/apu2_v126.96.36.199.rom
Resolving 3mdeb.com... 188.8.131.52
Connecting to 3mdeb.com|184.108.40.206|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8388608 (8.0M) [application/octet-stream]
Saving to: 'apu2_v220.127.116.11.rom'
apu2_v18.104.22.168.rom 100%[===================>] 8.00M 16.8MB/s in 0.5s
2022-03-31 15:03:43 (16.8 MB/s) - 'apu2_v22.214.171.124.rom' saved [8388608/8388608]
[root@bs ~]# flashrom -p internal:boardmismatch=force -w apu2_v126.96.36.199.rom
flashrom: /lib/libc.so.6: version `GLIBC_2.34' not found (required by flashrom)
It looks like the latest flashrom code requires version 2.34 of glibc. In Core Update 164 the version is 2.33.
Core Update 165 has version 2.35 of glibc.
Looks like you need to update IPFire to CU165 before trying to update the latest PCEngines firmware.
I have had a further look around at flashrom, glibc and apu2.
The message that flashrom requires glibc-2.34 doesn’t make sense as the version of flashrom running in IPFire is 1.2 and was updated in IPFire in January 2021.
flashrom-1.2 was released in February 2020.
glibc-2.34 was released in August 2021 so around 18 months after flashrom-1.2 was released so flashrom cannot be the program that is demanding glibc-2.34
I suspect that apu2_v188.8.131.52 is the program that has decided that glibc-2.34 is the minimum required.
In none of the changelogs from flashrom or apu2 is there any mention of an increased run dependency on glibc to version 2.34
Currently IPFire is on apu2 version 184.108.40.206 so any upgrade will occur with CU167 or later so glibc will be at or above version 2.34 at that time.
Conclusion is still that an update to CU165 should allow you to do the firmware update successfully.
YESSSS, you have reason, with CORE 165 work fine.