Today I was about to try write support for flashrom with the Xi 3650 BIOS and see whether it would work. The two images used for write were not too different (the only difference was a BIOS setting letting you choose between the on-board graphics card and an Nvidia Geforce 9600M GT). Nonetheless it seems to have written (and erased) at least one block of the BIOS ROM correctly.
Yours, Elmar
P.S. the console screenshot:
Proceeding anyway because user forced us to. Found chipset "Intel ICH9M-E". Enabling flash write... OK. Found Winbond flash chip "W25X16" (2048 kB, SPI) at physical address 0xffe00000. Reading flash... done. root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % ls intermediate Xi3650-T6400-1.0B-1646-0020.rom Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % cmp Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom intermediate/Xi3650-T6400-1.0H-1646-0024-IGD.rom Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom intermediate/Xi3650-T6400-1.0H-1646-0024-IGD.rom differ: char 1575900, line 3706 root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % ls intermediate Xi3650-T6400-1.0B-1646-0020.rom Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % flashrom -p internal:laptop=force_I_want_a_brick --write intermediate/Xi3650-T6400-1.0H-1646-0024-Nvidia.rom flashrom v0.9.7-r1711 on Linux 3.14.50-std460-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. ======================================================================== 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 the manpage and 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. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel ICH9M-E". Enabling flash write... OK. Found Winbond flash chip "W25X16" (2048 kB, SPI) at physical address 0xffe00000. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % flashrom -p internal:laptop=force_I_want_a_brick --write Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom flashrom v0.9.7-r1711 on Linux 3.14.50-std460-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. ======================================================================== 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 the manpage and 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. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel ICH9M-E". Enabling flash write... OK. Found Winbond flash chip "W25X16" (2048 kB, SPI) at physical address 0xffe00000. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 %
On Thu, 17 Sep 2015 22:11:37 +0200 Elmar Stellnberger estellnb@elstel.org wrote:
Today I was about to try write support for flashrom with the Xi 3650 BIOS and see whether it would work. The two images used for write were not too different (the only difference was a BIOS setting letting you choose between the on-board graphics card and an Nvidia Geforce 9600M GT). Nonetheless it seems to have written (and erased) at least one block of the BIOS ROM correctly.
Hi,
but you are definitely sure, that they actually were different (e.g. different MD5 checksum)? We should add that board to our laptop white list since 1) it is no laptop, 2) works flawlessly anyway. To that end, can you please send us the 'lspci -nn' output of that system and the file named 'e5730.log' created by 'flashrom -p internal:laptop=force_I_want_a_brick -o e5730.log' Thanks!
Yes, the md5sum of both images was different (i.e. it really did something). I will set a remark on this mail to gather the outstanding information soon.
lg Elmar
On 30.09.2015 01:24, Stefan Tauner wrote:
On Thu, 17 Sep 2015 22:11:37 +0200 Elmar Stellnberger estellnb@elstel.org wrote:
Today I was about to try write support for flashrom with the Xi 3650 BIOS and see whether it would work. The two images used for write were not too different (the only difference was a BIOS setting letting you choose between the on-board graphics card and an Nvidia Geforce 9600M GT). Nonetheless it seems to have written (and erased) at least one block of the BIOS ROM correctly.
Hi,
but you are definitely sure, that they actually were different (e.g. different MD5 checksum)? We should add that board to our laptop white list since 1) it is no laptop, 2) works flawlessly anyway. To that end, can you please send us the 'lspci -nn' output of that system and the file named 'e5730.log' created by 'flashrom -p internal:laptop=force_I_want_a_brick -o e5730.log' Thanks!
Hi Stefan,
Here comes the requested information: (in the attachements)
lg Elmar
On 30.09.2015 01:24, Stefan Tauner wrote:
On Thu, 17 Sep 2015 22:11:37 +0200 Elmar Stellnberger estellnb@elstel.org wrote:
Today I was about to try write support for flashrom with the Xi 3650 BIOS and see whether it would work. The two images used for write were not too different (the only difference was a BIOS setting letting you choose between the on-board graphics card and an Nvidia Geforce 9600M GT). Nonetheless it seems to have written (and erased) at least one block of the BIOS ROM correctly.
Hi,
but you are definitely sure, that they actually were different (e.g. different MD5 checksum)? We should add that board to our laptop white list since 1) it is no laptop, 2) works flawlessly anyway. To that end, can you please send us the 'lspci -nn' output of that system and the file named 'e5730.log' created by 'flashrom -p internal:laptop=force_I_want_a_brick -o e5730.log' Thanks!
On Wed, 30 Sep 2015 17:10:25 +0200 Elmar Stellnberger estellnb@elstel.org wrote:
Hi Stefan,
Here comes the requested information: (in the attachements)
Hi,
thanks for the files. I have created a patch (attached) that adds the Amilo Xi 3650 to our list of supported laptop and also whitelists it so that the warning at startup does not show up. Testing it would be appreciated.
Just one further question: what does that have to do with the Esprimo E5730 that seems to be a completely unrelated desktop PC by FSC? :)
Hi Stefan,
What a nice Christmas present! I just love to see my Amilo Xi 3650 well supported!
While I currently run the external display of the Xi 3650 with 2560x1440 it would likely be technically possible to run it at 4K: https://bugs.freedesktop.org/show_bug.cgi?id=93405
The Esprimo E5730; oops it is in deed a very different machine currently not supported by flashrom. However Fujitsu has already given me a contact address for the people in hold of the BIOS who would likely also know for the schematic of the board.
Of course will I compile and test the patched version of flashrom; it is just the way that we are currently relocating.
Compliments of the Season, Merry Christmas and a Happy New Year for all people on the flashrom list!
Yours, Elmar
Am 2015-12-24 um 20:14 schrieb Stefan Tauner:
On Wed, 30 Sep 2015 17:10:25 +0200 Elmar Stellnberger estellnb@elstel.org wrote:
Hi Stefan,
Here comes the requested information: (in the attachements)
Hi,
thanks for the files. I have created a patch (attached) that adds the Amilo Xi 3650 to our list of supported laptop and also whitelists it so that the warning at startup does not show up. Testing it would be appreciated.
Just one further question: what does that have to do with the Esprimo E5730 that seems to be a completely unrelated desktop PC by FSC? :)
Read support works well with Stefan`s patch (even during music playback). It should not be necessary to test write support another time, or should it?
root:~/flashrom> flashrom --programmer internal --read current-Xi3650-bios.flashrom-img flashrom v0.9.8-r1904 on Linux 4.2.5-1-ARCH (x86_64) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found chipset "Intel ICH9M-E". Enabling flash write... OK. Found Winbond flash chip "W25X16" (2048 kB, SPI) mapped at physical address 0x00000000ffe00000. Reading flash... done.
root:~/flashrom> ls -l current-Xi3650-bios.flashrom-img -rw-r--r-- 1 root root 2097152 27. Dez 23:05 current-Xi3650-bios.flashrom-img
root:~/flashrom> md5sum 0001-Add-Fujitsu-Amilo-Xi-3650-to-laptop-whitelist.patch dcd89c6a3b44aeb0a186b4738f7784a2 0001-Add-Fujitsu-Amilo-Xi-3650-to-laptop-whitelist.patch
Elmar
Am 2015-12-24 um 20:14 schrieb Stefan Tauner:
On Wed, 30 Sep 2015 17:10:25 +0200 Elmar Stellnberger estellnb@elstel.org wrote:
Hi Stefan,
Here comes the requested information: (in the attachements)
Hi,
thanks for the files. I have created a patch (attached) that adds the Amilo Xi 3650 to our list of supported laptop and also whitelists it so that the warning at startup does not show up. Testing it would be appreciated.
Just one further question: what does that have to do with the Esprimo E5730 that seems to be a completely unrelated desktop PC by FSC? :)
On Sun, 27 Dec 2015 23:17:11 +0100 Elmar Stellnberger estellnb@elstel.org wrote:
Read support works well with Stefan`s patch (even during music playback). It should not be necessary to test write support another time, or should it?
Thanks! No further actions on your side are necessary.
-
Elmar Stellnberger -
Stefan Tauner