On 22.11.2007 08:24, Andreas B. Mundt wrote: > On Thu, Nov 22, 2007 at 01:02:29AM +0100, Torsten Duwe wrote: > >> On Wednesday 21 November 2007, Andreas B. Mundt wrote: >> >>> On Wed, Nov 21, 2007 at 11:19:01PM +0100, Harald Gutmann wrote: >>> >>>> did you use flashrom -E befor writing the new file to the chip? >>>> >>> tried that: >>> >>> >>> $ sudo flashrom -E >>> Erasing flash chip >>> >>> $ sudo flashrom -V --verify --write /home/andi/freeBIOS/testbios >>> >> Does flashrom -r actually return a file of all 0xFFs after the erase? >> > > In fact it does not. Most of the file looks as if it is still the > linuxbios.rom. > > $ cmp after_erase linuxbios.rom > after_erase linuxbios.rom differ: byte 983041, line 1695 >
To summarize: Proprietary BIOS: * Erasing the chip was tested, reading from the chip gives you all 0xFFs after erase. * Writing the chip after erase was tested, verify successful. LinuxBIOS: * Erasing the chip fails, only a few bytes are changed (if any). * Writing fails as well because erase failed. I need the exact LinuxBIOS revision you are using and superiotool dumps under proprietary BIOS and LinuxBIOS. I have a suspicion about the cause of the failure. Please state your exact board revision as well. Regards, Carl-Daniel -- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
