Am Donnerstag, den 12.08.2010, 23:01 -0600 schrieb Rolan Christofferson: > Is this still an active email address? Yes, it is.
> flashrom v0.9.1-r946 > No coreboot table found. > Found ITE Super I/O, id 8712 > Found chipset "NVIDIA NForce2", enabling flash write... OK. > This chipset supports the following protocols: Non-SPI. > Calibrating delay loop... OK. > Found chip "PMC Pm49FL002" (256 KB, LPC,FWH) at physical address 0xfffc0000. > Flash image seems to be a legacy BIOS. Disabling checks. > Verifying flash... VERIFY FAILED at 0x00037e0c! Expected=0x14, Read=0x0c, > failed byte count from 0x00000000-0x0003ffff: 0x15 Hmm. This looks like the output of a verify operation, not a write operation. Note the missing "Writing flash chip..." in the output. If you verify a BIOS image against a file obtained on the same board before rebooting it, something like 0x15 different bytes is usual. Please note that the behaviour of flashrom if you specify both -w and -v. It might be that the result is a plain verify without write. Newer flashrom versions abort if more than one action is requested. > No coreboot table found. > Found ITE Super I/O, id 8712 > Found chipset "NVIDIA NForce2", enabling flash write... OK. > This chipset supports the following protocols: Non-SPI. > Calibrating delay loop... OK. > Found chip "PMC Pm49FL002" (256 KB, LPC,FWH) at physical address 0xfffc0000. > Flash image seems to be a legacy BIOS. Disabling checks. > Writing flash chip... Erasing flash chip... ERASE FAILED at 0x00000000! > Expected=0xff, Read=0x23, failed byte count from 0x00000000-0x00000fff: 0xff4 > ERASE FAILED! > ERASE FAILED at 0x00000000! Expected=0xff, Read=0x23, failed byte count from > 0x00000000-0x00003fff: 0x3fc8 > ERASE FAILED! > ERASE FAILED at 0x00000000! Expected=0xff, Read=0x23, failed byte count from > 0x00000000-0x0003ffff: 0x3b602 > ERASE FAILED! > FAILED! > ERASE FAILED! > FAILED! > Your flash chip is in an unknown state. This looks like your BIOS chip is write protected, probably there is a board-specific way to unprotect your chip. If you reply to this mail with the output of 'flashrom -V', 'lspci -nnvvvxxx', 'superiotool -deV' (all commands as root), the exact name of your board (including revision, if there are multiple revisions), and a link to the official BIOS download, a patch to support your board can be prepared. It is quite likely (but not warranted) that your flash contents did not change at all yet. > The file I used to set the bios was from an @bios dump of another > computer, same motherboard and chipset. OK, so the 0x15 differences contain stuff like the DMI database or the last boot-up time. No need to worry. Run a -v again, if you still get 0x15 differences, your BIOS is unchanged. Regards, Michael Karcher _______________________________________________ flashrom mailing list [email protected] http://www.flashrom.org/mailman/listinfo/flashrom
