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
Best regards Simon Riget
On Tue, 13 Nov 2012 11:33:32 +0100 Simon Riget simon@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.
Den 13-11-2012 14:06, Stefan Tauner skrev:
On Tue, 13 Nov 2012 11:33:32 +0100 Simon Riget simon@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.
On Fri, 16 Nov 2012 10:33:25 +0100 simon simon.riget@gmail.com wrote:
Den 13-11-2012 14:06, Stefan Tauner skrev:
On Tue, 13 Nov 2012 11:33:32 +0100 Simon Riget simon@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?
On Fri, 16 Nov 2012 12:07:27 +0100 Stefan Tauner stefan.tauner@student.tuwien.ac.at wrote:
On Fri, 16 Nov 2012 10:33:25 +0100 simon simon.riget@gmail.com wrote:
Den 13-11-2012 14:06, Stefan Tauner skrev:
On Tue, 13 Nov 2012 11:33:32 +0100 Simon Riget simon@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 :)
Den 24-11-2012 19:09, Stefan Tauner skrev:
On Fri, 16 Nov 2012 12:07:27 +0100 Stefan Tauner stefan.tauner@student.tuwien.ac.at wrote:
On Fri, 16 Nov 2012 10:33:25 +0100 simon simon.riget@gmail.com wrote:
Den 13-11-2012 14:06, Stefan Tauner skrev:
On Tue, 13 Nov 2012 11:33:32 +0100 Simon Riget simon@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
Den 16-11-2012 12:07, Stefan Tauner skrev:
On Fri, 16 Nov 2012 10:33:25 +0100 simon simon.riget@gmail.com wrote:
Den 13-11-2012 14:06, Stefan Tauner skrev:
On Tue, 13 Nov 2012 11:33:32 +0100 Simon Riget simon@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)
On Fri, 30 Nov 2012 19:50:01 +0100 simon simon.riget@gmail.com wrote:
-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"
^^^^^^^^ compare that to http://paste.flashrom.org/view.php?id=1442 while the DMI data is not directly read from flash, it is a clear sign that the BIOS has changed (the firmware sets up the DMI table in memory where flashrom reads it then). so flashrom clearly did work as intended, that's great.
because elitegroup changed the chassis type to "portable" flashrom thinks it is running on a laptop and bails out for safety reasons. you have to use -p internal:laptop=force_I_want_a_brick because of that until we whitelist that system in a future version, sorry.
why they did not increment/change the bios version i dont know... but as you see they do lots of errors :)
so as far as i am concerned, everything looks normal and i will add the board/chipset etc to our list of supported hardware with an appropriate note.
On Fri, 30 Nov 2012 22:25:09 +0100 Stefan Tauner stefan.tauner@student.tuwien.ac.at wrote:
On Fri, 30 Nov 2012 19:50:01 +0100 simon simon.riget@gmail.com wrote:
-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"
^^^^^^^^compare that to http://paste.flashrom.org/view.php?id=1442 while the DMI data is not directly read from flash, it is a clear sign that the BIOS has changed (the firmware sets up the DMI table in memory where flashrom reads it then). so flashrom clearly did work as intended, that's great.
because elitegroup changed the chassis type to "portable" flashrom thinks it is running on a laptop and bails out for safety reasons. you have to use -p internal:laptop=force_I_want_a_brick because of that until we whitelist that system in a future version, sorry.
i have prepared a patch to whitelist that laptop. it would be awesome if you could compile flashrom with the following line added to the big array in board_enable.c around line 2400, the exact line does not matter as long as it is somewhere inside the table {0x1039, 0x6325, 0x1019, 0x0f05, 0x1039, 0x0016, 0, 0, NULL, NULL, NULL, P2, "Elitegroup", "A928", 0, OK, p2_whitelist_laptop},
after adding that and recompiling, you should be able to use flashrom again without the laptop force switch (and i could rest assured that the patch works).
Den 01-12-2012 02:13, Stefan Tauner skrev:
On Fri, 30 Nov 2012 22:25:09 +0100 Stefan Tauner stefan.tauner@student.tuwien.ac.at wrote:
On Fri, 30 Nov 2012 19:50:01 +0100 simon simon.riget@gmail.com wrote:
-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"
^^^^^^^^compare that to http://paste.flashrom.org/view.php?id=1442 while the DMI data is not directly read from flash, it is a clear sign that the BIOS has changed (the firmware sets up the DMI table in memory where flashrom reads it then). so flashrom clearly did work as intended, that's great.
because elitegroup changed the chassis type to "portable" flashrom thinks it is running on a laptop and bails out for safety reasons. you have to use -p internal:laptop=force_I_want_a_brick because of that until we whitelist that system in a future version, sorry.
i have prepared a patch to whitelist that laptop. it would be awesome if you could compile flashrom with the following line added to the big array in board_enable.c around line 2400, the exact line does not matter as long as it is somewhere inside the table {0x1039, 0x6325, 0x1019, 0x0f05, 0x1039, 0x0016, 0, 0, NULL, NULL, NULL, P2, "Elitegroup", "A928", 0, OK, p2_whitelist_laptop},
after adding that and recompiling, you should be able to use flashrom again without the laptop force switch (and i could rest assured that the patch works).
Hi Stefan
Patch added and seems to work fine.
I will not claim that I understand why the updated BIOS don't show any signs of being updated. Clearly something was changes in the Flash as the readout are different. But I will leave it at that for now.
Thank you for all your time and effort in this project.
#flashrom -p internal -r readrom2.rom <output> flashrom v0.9.6.1-r1627 on Linux 3.2.0-34-generic-pae (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found chipset "SiS 650". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom@flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... OK. Found Winbond flash chip "W49F002U/N" (256 kB, Parallel) at physical address 0xfffc0000. Reading flash... done. </output>
cmp bios_old.rom readrom2.rom : <output> bios_backup.rom readrom2.rom differ: byte 9341, line 1 </output>
2012/12/1 simon simon.riget@gmail.com:
Den 01-12-2012 02:13, Stefan Tauner skrev:
Hi Stefan
Patch added and seems to work fine.
Can you re-send the patch, which we'll happily integrate, this time not as a .vcf?
Idwer
-
Idwer Vollering -
simon -
Simon Riget -
Stefan Tauner