Hello,
First, I want to thank Flashrom developers and maintainers and all the helpers who help make this wonderful utility. Please help urgent problem - flashrom erase failed, flash chip in unknown state now. PLEASE help - what do I do now ? THANK YOU.
Attached diagnostic output plain-text files. Thanks again.
My system: HP Pavilion a445w, P4SD-LA Motherboard (Stingray), XUbuntu 9.10 Karmic uname -a gives Linux 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC 2010 i686 GNU/Linux
Extracted Windows exe "sp26381.exe" from HP software and downloads site at ftp://ftp.hp.com/pub/softpaq/sp26001-26500/sp26381.exe - it contains "328.rom" (524288 bytes) - new BIOS version 3.28
Current existing BIOS version 3.19
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.
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 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! Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net channel #flashrom or mail flashrom@flashrom.org ------------------------------------------------------------ DO NOT REBOOT OR POWEROFF!
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
This one was so easy that I didn't wait for a request.
Signed-off-by: Michael Karcher flashrom@mkarcher.dialup.fu-berlin.de --- board_enable.c | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/board_enable.c b/board_enable.c index f1f7953..5a3e9f0 100644 --- a/board_enable.c +++ b/board_enable.c @@ -1011,6 +1011,14 @@ static int intel_ich_gpio26_raise(const char *name) }
/** + * Suited for P4SD-LA (HP OEM): i865 + ICH5 + */ +static int intel_ich_gpio32_raise(const char *name) +{ + return intel_ich_gpio_set(32, 1); +} + +/** * Suited for Acorp 6A815EPD: socket 370 + intel 815 + ICH2. */ static int board_acorp_6a815epd(const char *name) @@ -1377,6 +1385,7 @@ struct board_pciid_enable board_pciid_enables[] = { {0x8086, 0x1A30, 0x1043, 0x8088, 0x8086, 0x24C3, 0x1043, 0x8089, NULL, NULL, NULL, "ASUS", "P4B533-E", 0, NT, intel_ich_gpio22_raise}, {0x8086, 0x24D3, 0x1043, 0x80A6, 0x8086, 0x2578, 0x1043, 0x80F6, NULL, NULL, NULL, "ASUS", "P4C800-E Deluxe", 0, OK, intel_ich_gpio21_raise}, {0x8086, 0x2570, 0x1043, 0x80F2, 0x105A, 0x3373, 0x1043, 0x80F5, NULL, NULL, NULL, "ASUS", "P4P800-E Deluxe", 0, OK, intel_ich_gpio21_raise}, + {0x8086, 0x2570, 0x1043, 0x80A5, 0x105A, 0x24D3, 0x1043, 0x80A6, NULL, NULL, NULL, "ASUS", "P4SD-LA", 0, OK, intel_ich_gpio32_raise}, {0x10B9, 0x1541, 0, 0, 0x10B9, 0x1533, 0, 0, "^P5A$", "asus", "p5a", "ASUS", "P5A", 0, OK, board_asus_p5a}, {0x10DE, 0x0030, 0x1043, 0x818a, 0x8086, 0x100E, 0x1043, 0x80EE, NULL, NULL, NULL, "ASUS", "P5ND2-SLI Deluxe", 0, OK, nvidia_mcp_gpio10_raise}, {0x1106, 0x3149, 0x1565, 0x3206, 0x1106, 0x3344, 0x1565, 0x1202, NULL, NULL, NULL, "Biostar", "P4M80-M4", 0, OK, it8705f_write_enable_2e},
Michael and the flashrom team,
Thank you very much for the helpful, prompt response. Your time and efforts put into this are much appreciated. Looks like I need further help.
After this issue early today morning, I went to sleep and when I woke up, found that the computer had powered off probably due to a transient power outage. When turned on again, it has booted up seemingly fine (so noticeable issues so far, 7 hours uptime after power-on).
As Michael has suggested for verification, I now tried $ sudo flashrom -v current_bios_amibios3.19.img 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. Verifying flash... VERIFY FAILED at 0x0006e010! Expected=0x08, Read=0x27, failed byte count from 0x00000000-0x0007ffff: 0x6
Now it says VERIFY FAILED. Please could you advise what to do now ? Once again, THANK YOU ALL so much. Regards.
On Sat, Apr 24, 2010 at 3:30 AM, Michael Karcher edvsupport@mkarcher.dialup.fu-berlin.de wrote:
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
Hi,
On 24.04.2010 22:26, csh tmp wrote:
Thank you very much for the helpful, prompt response. Your time and efforts put into this are much appreciated. Looks like I need further help.
After this issue early today morning, I went to sleep and when I woke up, found that the computer had powered off probably due to a transient power outage. When turned on again, it has booted up seemingly fine (so noticeable issues so far, 7 hours uptime after power-on).
Good.
As Michael has suggested for verification, I now tried $ sudo flashrom -v current_bios_amibios3.19.img 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. Verifying flash... VERIFY FAILED at 0x0006e010! Expected=0x08, Read=0x27, failed byte count from 0x00000000-0x0007ffff: 0x6
Now it says VERIFY FAILED. Please could you advise what to do now ?
No reason to worry. It seems your BIOS rewrites a small part of the ROM on every boot. This is probably the date/time when the computer was powered on, and you can ignore this failure. Basically, for most recent BIOS, verify will work before reboot, and will fail after reboot because the BIOS changed some flash contents.
Regards, Carl-Daniel
-
Carl-Daniel Hailfinger -
csh tmp -
Michael Karcher -
Michael Karcher