On Apr 23 15:38:48, mcmer-open...@tor.at wrote:
> just asking because you did not mention: you are running single user,
> right?
No, I set securelevel to -1 for the duration of this.
> I documented an firmware upgrade on 2020-03-04, for an APU2:
> first I tried "flashrom -p internal -w apu2.rom",
On 2020-04-23, Jan Stary wrote:
> Eventually, flashrom aborts with
>
> Manufacturer: PC Engines
> Mainboard ID: apu2
> This coreboot image (PC Engines:apu2) does not appear to
> be correct for the detected mainboard (PC Engines:PCEngines apu2).
> Aborting. You can override this with -p i
Hello Jan,
just asking because you did not mention: you are running single user,
right?
I documented an firmware upgrade on 2020-03-04, for an APU2:
first I tried "flashrom -p internal -w apu2.rom", then I noted
"needs boardmismatch=force", which i then used.
That machine is still running, unbri
On Thu, Apr 23, 2020 at 3:04 PM Jan Stary wrote:
>
> Eventually, flashrom aborts with
>
> Manufacturer: PC Engines
> Mainboard ID: apu2
> This coreboot image (PC Engines:apu2) does not appear to
> be correct for the detected mainboard (PC Engines:PCEngines apu2).
> Aborting. You can ove
I am flashing my APU2's firmware on current/amd64,
using the flashrom port; script and dmesg below.
I would like to make sure about a few nits before going ahead.
Probe first:
# flashrom -p internal
flashrom v1.1 on OpenBSD 6.7 (amd64)
flashrom is free software, get the source code at https://fla
5 matches
Mail list logo