Hello All and Merry Christmas,
Our first hands-on with Linux Bios.
We removed the Flashrom from K8Upgrade-VM800 Bios socket and inserted the new Flashrom SST49LF004A/B.
But the flash is not happening properly and the Bios is not written to the Bios chip.
Hence unable to boot with new Flashrom.
Is it the problem of the flashrom utility ?
We are ready fix things, please guide us.
Note: We did not try to boot Linux bios, instead we tried to boot the PC-Bios which is present in the Motherboard by writing it on to new flashrom, so as to check whether the flashrom utility is working properly or not.
Execution steps: -------------------------- lspci output: ------------------- root@example:/home/kiran/bios_files# lspci 00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)
Erasing Flashrom: ----------------------------- root@example:/home/kiran/bios_files# flashrom -E Calibrating delay loop... ok No LinuxBIOS table found. Found chipset "VT8237": Enabling flash write... OK. SST49LF004A/B found at physical address: 0xfff80000 Flash part is SST49LF004A/B (512 KB) Erasing flash chip
Writing the Original Bios to the new Flashrom: --------------------------------------------------------------------------- root@example:/home/kiran/bios_files# flashrom -w Dec26_Bios Calibrating delay loop... ok No LinuxBIOS table found. Found chipset "VT8237": Enabling flash write... OK. SST49LF004A/B found at physical address: 0xfff80000 Flash part is SST49LF004A/B (512 KB) Flash image seems to be a legacy BIOS. Disabling checks. Programming Page: 0007 at address: 0x00070000
Verifying flash against file: ------------------------------------------ The last step shows FAILED which means the Bios has not been written properly.
root@example:/home/kiran/bios_files# flashrom -v Dec26_Bios Calibrating delay loop... ok No LinuxBIOS table found. Found chipset "VT8237": Enabling flash write... OK. SST49LF004A/B found at physical address: 0xfff80000 Flash part is SST49LF004A/B (512 KB) Flash image seems to be a legacy BIOS. Disabling checks. Verifying flash - FAILED
Reading flash and saving into file: ------------------------------------------------------ root@example:/home/kiran/bios_files# flashrom -r Pc_Bios Calibrating delay loop... ok No LinuxBIOS table found. Found chipset "VT8237": Enabling flash write... OK. SST49LF004A/B found at physical address: 0xfff80000 Flash part is SST49LF004A/B (512 KB) Reading Flash...done
Diff of Original Bios and latest read Bios: ------------------------------------------------------------------ root@example:/home/kiran/bios_files# diff Dec26_Bios Pc_Bios Binary files Dec26_Bios and Pc_Bios differ
Thanks, Kiran.
On Wed, Dec 26, 2007 at 08:41:14PM +0530, Kiran Patil wrote:
Hello All and Merry Christmas,
The same to you.
Diff of Original Bios and latest read Bios:
root@example:/home/kiran/bios_files# diff Dec26_Bios Pc_Bios Binary files Dec26_Bios and Pc_Bios differ
So how do they differ?
Can you tell if any writes to the flash chip worked - including the erase?
You can use xxd to get a hex dump of the files, and then do diff -u on those.
//Peter
Hi,
When I do execute the following command, it really shows that it is writing on to the chip. The Programming Pages will increment form 0000 to 0007. *Programming Page: 0007 at address: 0x00070000*
I am attaching the hexdump files.
root@example:/home/kiran/bios_files# flashrom -w Dec26_Bios Calibrating delay loop... ok No LinuxBIOS table found. Found chipset "VT8237": Enabling flash write... OK. SST49LF004A/B found at physical address: 0xfff80000 Flash part is SST49LF004A/B (512 KB) Flash image seems to be a legacy BIOS. Disabling checks. Programming Page: 0007 at address: 0x00070000
Erasing Flashrom: ----------------------------- root@example:/home/kiran/bios_files# flashrom -E Calibrating delay loop... ok No LinuxBIOS table found. Found chipset "VT8237": Enabling flash write... OK. SST49LF004A/B found at physical address: 0xfff80000 Flash part is SST49LF004A/B (512 KB) Erasing flash chip
It is showing the above message as if it is doing it. But I think no writes are happening and only read is happening.
Thanks, Kiran.
On Dec 26, 2007 9:14 PM, Peter Stuge peter@stuge.se wrote:
On Wed, Dec 26, 2007 at 08:41:14PM +0530, Kiran Patil wrote:
Hello All and Merry Christmas,
The same to you.
Diff of Original Bios and latest read Bios:
root@example:/home/kiran/bios_files# diff Dec26_Bios Pc_Bios Binary files Dec26_Bios and Pc_Bios differ
So how do they differ?
Can you tell if any writes to the flash chip worked - including the erase?
You can use xxd to get a hex dump of the files, and then do diff -u on those.
//Peter
-- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
-
Kiran Patil -
Peter Stuge