So, am I correct to assume that flashing the BIOS on my board is not (at least) yet possible with flash_rom? I don't have the experience to mess with MTD, really, so I'll just stick with flashing from DOS. Thanks for your help on this.
John
-----Original Message----- From: Hendricks David W. [mailto:dwh@lanl.gov] Sent: Friday, March 26, 2004 1:20 PM To: John Laur Cc: linuxbios@clustermatic.org Subject: RE: EPIA-M "Magic Potion"?
Oops, it's not LPC compatible :( Ollie says we need a really old
mainboard
to flash it.
Or perhaps MTD would work?
On Fri, 26 Mar 2004, John Laur wrote:
-----Original Message----- From: linuxbios-admin@clustermatic.org [mailto:linuxbios- admin@clustermatic.org] On Behalf Of Hendricks David W. Sent: Friday, March 26, 2004 11:49 AM To: John Laur Cc: linuxbios@clustermatic.org Subject: Re: EPIA-M "Magic Potion"?
What is the model/part number on your flash? It *might* work with
the
code
already in flash_and_burn, but we might need to add a device id or something.
You will have to forgive me; I am still pretty green with this whole thing. Which model/part number do you need exactly? I have included
some
information here, but if you need to know something else, please
just
let me know, and I'll be happy to provide it.
I am using an RD1-PL Bios Savior with the original BIOS chip in the socket. Flash_rom recognizes neither the original BIOS nor the
backup
flash part (I don't know exactly what chip the RD1-PL uses offhand.)
When the RD1 is switched to the ORG (original bios), AWFLASH.EXE
reports
the following:
For VT8623-8235-CLE26I01C-00 DATE: 12/11/2003 Flash Type - SST 39SF020 /5V
The actual chip says on it:
SST MPF 39SF020A 70-4C-NH 0219037-A
Here is the output of my lspci -vvn for the southbridge (00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge):
00:11.0 Class 0601: 1106:3177 Subsystem: 1106:aa01 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium
TAbort-
<TAbort- <MAbort- >SERR- <PERR- Latency: 0 Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Here is what flash_rom returns. As you can see it's probing for the SST29SF020A, which is what I have, and failing:
m3:~/freebios/util/flash_and_burn# setpci -s 0:11.0 40.b=54
m3:~/freebios/util/flash_and_burn# ./flash_rom Calibrating timer since microsleep sucks ... takes a second Setting up microsecond timing loop 199M loops per second OK, calibrated, now do the deed Enabling flash write on VT8235...OK Trying Am29F040B, 512 KB probe_29f040b: id1 0xff, id2 0xff Trying At29C040A, 512 KB probe_jedec: id1 0xff, id2 0xff Trying Mx29f002, 256 KB probe_29f002: id1 37, id2 0 Trying SST29EE020A, 256 KB probe_jedec: id1 0x25, id2 0x0 Trying SST28SF040A, 512 KB probe_28sf040: id1 0xff, id2 0xff Trying SST39SF020A, 256 KB probe_39sf020: id1 0x25, id2 0x0 Trying SST39VF020, 256 KB probe_39sf020: id1 0x25, id2 0x0 Trying W29C011, 128 KB probe_jedec: id1 0x68, id2 0x5b Trying W29C020C, 256 KB probe_jedec: id1 0x25, id2 0x0 Trying W49F002U, 256 KB probe_49f002: id1 0x25, id2 0x0 Trying M29F400BT, 512 KB probe_m29f400bt: id1 0xff, id2 0xff Trying 82802ab, 512 KB probe_82802ab: id1 0xff, id2 0xff Trying 82802ac, 1024 KB probe_82802ab: id1 0xff, id2 0xff Trying MD-2802 (M-Systems DiskOnChip Millennium Module), 8 KB probe_md2802: probe_md2802: ******************************* probe_md2802: * THIS IS A PRE ALPHA VERSION * probe_md2802: * IN THE DEVELOPEMENT ********* probe_md2802: * PROCESS RIGHT NOW. ********** probe_md2802: ******************************* probe_md2802: * IF YOU ARE NOT A DEVELOPER ** probe_md2802: * THEN DO NOT TRY TO READ OR ** probe_md2802: * WRITE TO THIS DEVICE ******** probe_md2802: ******************************* probe_md2802: probe_md2802: switching off reset mode ... probe_md2802: switching off reset mode ... done probe_md2802: probe_md2802: switching off write protection ... probe_md2802: switching off write protection ... done probe_md2802: probe_md2802: IPL_0x0000: 0x41 probe_md2802: IPL_0x0001: 0x77 probe_md2802: IPL_0x0002: 0x61 probe_md2802: IPL_0x0003: 0x72 probe_md2802: probe_md2802: ChipID: 0x0e probe_md2802: DOCStatus: 0x17 probe_md2802: FloorSelect: 0x01 probe_md2802: CDSNControl: 0xeb probe_md2802: CDSNDeviceSelect: 0x2c probe_md2802: ECCConfiguration: 0xf6 probe_md2802: CDSNSlowIO: 0x2e probe_md2802: ECCSyndrome0: 0x01 probe_md2802: ECCSyndrome1: 0x86 probe_md2802: ECCSyndrome2: 0xc4 probe_md2802: ECCSyndrome3: 0x8b probe_md2802: ECCSyndrome4: 0x1e probe_md2802: ECCSyndrome5: 0x1c probe_md2802: AliasResolution: 0x83 probe_md2802: ConfigurationInput: 0xc3 probe_md2802: ReadPipelineInitialization: 0x02 probe_md2802: LastDataRead: 0x1e probe_md2802: probe_md2802: checking ECCConfiguration toggle bit probe_md2802: 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 probe_md2802: toggle result: 5/5 EEPROM not found
Thank you, everyone for all the help. Hopefully, I can get this
thing
figured out eventually.
John
On Fri, 26 Mar 2004, John Laur wrote:
- I cannot for the life of me flash the BIOS under Linux. For
now,
I
have to reboot to a DOS floppy and flash the original BIOS, then
reboot
again and flash the LinuxBIOS image (AWFLASH will for some
reason
not
flash a LinuxBIOS image over a LinuxBIOS image already on the
flash
part) I have run 'setpci -s 0:11.0 40.b=54' as described in the
docs
and on the mailing list, but flash_rom still detects no flash
device.
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios