[flashrom] EC A928 failed flash. part 2.1

[simon]

Den 16-11-2012 12:07, Stefan Tauner skrev:
> On Fri, 16 Nov 2012 10:33:25 +0100
> simon <simon.riget at gmail.com> wrote:
>
>> Den 13-11-2012 14:06, Stefan Tauner skrev:
>>> On Tue, 13 Nov 2012 11:33:32 +0100
>>> Simon Riget <simon at paragi.dk> wrote:
>>>
>>>> Biso was flashed with backup and are hopefully restored.
>>>>
>>>>
>>>> flashrom -p internal -V: http://paste.flashrom.org/view.php?id=1442
>>>> lspci -nnvvvxxx: http://paste.flashrom.org/view.php?id=1443
>>>> superiotool -deV : http://paste.flashrom.org/view.php?id=1444
>>>> flashrom -p internal -r readout.rom:
>>>> http://paste.flashrom.org/view.php?id=1445
>>> as discussed on IRC it is believed that the chip's "boot block lockout"
>>> is enabled and not possible to be disabled by software and that it is
>>> safe to update the bios by only writing to the unprotected parts.
>>>
>>> flashrom supports writing arbitrary address ranges out of the box
>>> (reading, verifying and erasing support has not been merged though).
>>> to do so one has to tell flashrom the flash "partition table" with the
>>> help of a layout file. please consult the manpage about the details for
>>> example how to select an address range to operate on.
>>>
>>> your layout file should look like this:
>>> 00000000:0003bfff main
>>> 0003c000:0003ffff bootblock
>>>
>>> and you want to flash the main part only. presuming that the layout
>>> file is named "layout.txt", you will probably want to execute something
>>> like this:
>>>
>>> flashrom -p internal -V -l layout.txt -i main -w <imagename>
>>> it should say verified at the as you have seen already. if it does not
>>> for any reason, but tell you the "unknown state" message, please write
>>> the backup again. you should always be able to go back to this safe
>>> state, as long as you dont reboot.
>>>
>>> if it says verified then the new contents mixed with the old bootblock
>>> are written correctly. as i explained to you we are not 100% sure that
>>> his is a legit state, but have little doubt and you can reboot then.
>>>
>> Result:
>> The flashrom program terminated succesfully
>> The BIOS settings where wiped. (Reinstated with BIOS setup)
>> The mashine can boot
>>
>> However the BIOS version are still the same and I have seen no other
>> signs that the BIOS was upgraded.
> please upload the following images to http://paste.flashrom.org
>   - the original backup you have read out before doing the write (should
>     be equal to the one you did at the very beginning i presume)
>   - the image you used in the -l ... -w ... call
>   - the image flashrom reads after issuing the -l -w call (this should
>     be a mixture of the first (the bootblock part) and the second one
>
> also i would like to see the log file generated by
> flashrom -p internal -V -l layout.txt -i main -w <imagename> -o flashrom.log
> or at least the verbose output.
>
> you said the bios version did not change. how did you determine this
> fact exactly?
>
Files:
backup before any tampering: http://paste.flashrom.org/view.php?id=1475
Image of bios update: http://paste.flashrom.org/view.php?id=1476

-I determined BIOS version by entering the BIOS setup.

-The flashrom version i'm using doesn’t support the -o option
-Output didn't show any errors.

- Now I can't read the flashrom to file. Do you recommend using the -f 
option?

#flashrom -p internal -r read2.rom -V
<output>
flashrom v0.9.5.2-r1517 on Linux 3.2.0-33-generic-pae (i686), built with 
libpci 3.1.8, GCC 4.6.3, little endian
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OS timer resolution is 2 usecs, 1185M loops 
per second, 10 myus = 11 us, 100 myus = 101 us, 1000 myus = 1030 us, 
10000 myus = 10130 us, 8 myus = 10 us, OK.
Initializing internal programmer
No coreboot table found.
DMI string system-manufacturer: "Elitegroup Co.                  "
DMI string system-product-name: "i-Buddie                        "
DMI string system-version: "1.0                             "
DMI string baseboard-manufacturer: "Elitegroup Co. "
DMI string baseboard-product-name: "i-Buddie "
DMI string baseboard-version: "2.0                             "
DMI string chassis-type: "Portable"
Laptop detected via DMI.
========================================================================
WARNING! You seem to be running flashrom on an unsupported laptop.
Laptops, notebooks and netbooks are difficult to support and we
recommend to use the vendor flashing utility. The embedded controller
(EC) in these machines often interacts badly with flashing.
See http://www.flashrom.org/Laptops for details.

If flash is shared with the EC, erase is guaranteed to brick your laptop
and write may brick your laptop.
Read and probe may irritate your EC and cause fan failure, backlight
failure and sudden poweroff.
You have been warned.
========================================================================
Aborting.
</output>

(No file created)


-- 
Simon Rigét
Kløvermarksvej 17
Annisse
3200 Helsinge
Tlf. 4096 8217
-------------- next part --------------
A non-text attachment was scrubbed...
Name: simon_riget.vcf
Type: text/x-vcard
Size: 138 bytes
Desc: not available
URL: <http://www.flashrom.org/pipermail/flashrom/attachments/20121130/e29b919f/attachment.vcf>