Matt, your post to StackExchange is very impressive, as is your machine
with a Threadripper!
What shows the problem & the answer is this:
"FCH device found but SMBus revision 0x59 does not match known values."

You installed flashrom as a binary package or app, but by now we have fixed
the issues with the AMD boards with rev 0x59 flash chips even if it's not
reflected in the binary packages yet. You will need to go to the Downloads
page and get the source and compile it on your machine. The source you
download has the problem fixed. Go here:

*https://www.flashrom.org/Downloads <https://www.flashrom.org/Downloads>*

Actually the page only tells you where  to go, not how to do it. After you
make sure have installed the requirements listed, you will want to download
thus:

*git clone https://review.coreboot.org/flashrom.git
<https://review.coreboot.org/flashrom.git>*

Then navigate to the flashrom directory, do: *make* & *make install*

If that fails to compile, it's probably because you need one of the several
linux utilities or libraries. It's impossible to list exactly what is
needed as everyone's machine is different and often running different linux
flavors. Just fix the missing dependencies and you will get it to compile:-)

Then try `*$ sudo flashrom --programmer internal*` or `*#flashrom -p
internal*`

Best of luck, and let us know how it goes.

Clay

On Sun, Jan 3, 2021 at 3:37 PM Matt Rixman <m...@rixman.org> wrote:

> Hi, I'm the asker of this question:
> https://superuser.com/questions/1613342/why-do-windows-updates-make-linux-run-slower-clearing-cmos-fixes-it
>
> I was hoping to use `flashrom` to gather before/after dumps, which I can
> (hopefully) compare to get to the bottom of my problem.
>
> When I run: `sudo flashrom --programmer internal`
> I get this:
>
> --- begin output ---
> flashrom  on Linux 4.19.0-13-amd64 (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Found chipset "AMD FP4".
> Enabling flash write... FCH device found but SMBus revision 0x59 does not
> match known values.
> Please report this to flashrom@flashrom.org and include this log and
> the output of lspci -nnvx, thanks!.
> Could not determine chipset generation.PROBLEMS, continuing anyway
> No EEPROM/flash device found.
> Note: flashrom can never write if the flash chip isn't found automatically.
> --- end output ---
>
> the output of lspci is attached.
>
> Thanks,
>
> Matt_______________________________________________
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org
>
_______________________________________________
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

Reply via email to