[flashrom] Need help with failed flash. part 2.1

simon simon.riget at gmail.com
Mon Nov 26 09:53:11 CET 2012


Den 24-11-2012 19:09, Stefan Tauner skrev:
> On Fri, 16 Nov 2012 12:07:27 +0100
> Stefan Tauner <stefan.tauner at student.tuwien.ac.at> wrote:
>
>> 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?
> what was the outcome eventually? i would like to know if i can mark the
> chipset and mainboard as supported :)
>
I'm sorry. I will get back to you as soon at I can. Probably within a week.
BR

-- 
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/20121126/767a5222/attachment.vcf>


More information about the flashrom mailing list