Am Samstag, den 24.04.2010, 01:47 -0500 schrieb csh tmp:
Using flashrom v0.9.1-r706, I first earlier saved current BIOS image to "current_bios_amibios3.19.img" (524288 bytes) - got the following output: flashrom v0.9.1-r706 No coreboot table found. Found chipset "Intel ICH5/ICH5R", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "Winbond W39V040FA" (512 KB, FWH) at physical address 0xfff80000. Reading flash... done.
Very good. I hope this file is still OK.
I stupidly made a typo in testing by first trying to re-write current bios back to the chip, to test. I typed the following cmd (missed giving the '-' char to -v option)
$ sudo flashrom -w current_bios_amibios3.19.img v current_bios_amibios3.19.img
Doesn't matter. You have no "-v" now, but this still rewrites the current imae.
flashrom v0.9.1-r706 No coreboot table found. Found chipset "Intel ICH5/ICH5R", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "Winbond W39V040FA" (512 KB, FWH) at physical address 0xfff80000. Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... ERASE FAILED at 0x000061f0! Expected=0xff, Read=0x3c, failed byte count from 0x00000000-0x0007ffff: 0x6a379 ERASE FAILED! ERASE FAILED! FAILED!
This one very much looks like there is a write protection enabled on your board flashrom doesn't know how to remove, and nothing has changed yet. If you run flashrom -v current_bios_amibios3.19.img and it outputs "VERIFIED" you know that the data in your flash chip is unmodified and you are safe to reboot. If a flashrom developer finds some time, he might try to add support for your board to flashrom.
Regards, Michael Karcher