I tried the linux bios flash_rom utility today on a sis based board. I tried to read out the bios as a file. It failed. (output below)
flash_rom says: "Trying MD-2802 (M-Systems DiskOnChip Millennium Module), 8 KB". Interestingly, the second google hit of "M-Systems DiskOnChip Millennium 2802" was the linuxbios wiki :)
I thought I'd post the output for informative purposes. I'd dig more if anyone was interested.
Is the BIOS chip on this machine really only 8KB in size? I find that really hard to believe.
Jeff
lspci: 0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS 645xx (rev 51) 0000:00:01.0 PCI bridge: Silicon Integrated Systems [SiS]: Unknown device 0003 0000:00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 14) 0000:00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016 0000:00:02.3 FireWire (IEEE 1394): Silicon Integrated Systems [SiS] FireWire Controller 0000:00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] 0000:00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0) 0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0) 0000:00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 0000:00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 0000:00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 0000:00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 0000:00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) 0000:00:0c.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01) 0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
flash_rom -r output: Calibrating timer since microsleep sucks ... takes a second Setting up microsecond timing loop 796M loops per second OK, calibrated, now do the deed 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 0xff, id2 0xff Trying SST29EE020A, 256 KB probe_jedec: id1 0xff, id2 0xff Trying SST28SF040A, 512 KB probe_28sf040: id1 0xff, id2 0xff Trying SST39SF020A, 256 KB probe_jedec: id1 0xff, id2 0xff Trying SST39VF020, 256 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF040, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF002A/B, 256 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF003A/B, 384 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF004A/B, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF008A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying Pm49FL004, 512 KB probe_jedec: id1 0xff, id2 0xff Trying W29C011, 128 KB probe_jedec: id1 0xef, id2 0xd8 Trying W29C020C, 256 KB probe_jedec: id1 0xff, id2 0xff Trying W49F002U, 256 KB probe_jedec: id1 0xff, id2 0xff 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: 0x6d probe_md2802: IPL_0x0001: 0x00 probe_md2802: IPL_0x0002: 0x01 probe_md2802: IPL_0x0003: 0x83 probe_md2802: probe_md2802: ChipID: 0xed probe_md2802: DOCStatus: 0xba probe_md2802: FloorSelect: 0x00 probe_md2802: CDSNControl: 0xb0 probe_md2802: CDSNDeviceSelect: 0x70 probe_md2802: ECCConfiguration: 0xee probe_md2802: CDSNSlowIO: 0xed probe_md2802: ECCSyndrome0: 0xee probe_md2802: ECCSyndrome1: 0xe6 probe_md2802: ECCSyndrome2: 0xed probe_md2802: ECCSyndrome3: 0xb0 probe_md2802: ECCSyndrome4: 0xff probe_md2802: ECCSyndrome5: 0xee probe_md2802: AliasResolution: 0xf1 probe_md2802: ConfigurationInput: 0xe6 probe_md2802: ReadPipelineInitialization: 0xed probe_md2802: LastDataRead: 0xc0 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 root@jcarr:/home/jcarr/linuxbios/LinuxBIOSv2/util/flash_and_burn#
On 08/12/2005 01:19 AM, Jeff Carr wrote:
I tried the linux bios flash_rom utility today on a sis based board. I tried to read out the bios as a file. It failed. (output below)
I see now in the archive that the error: "EEPROM not found" came up on a thread last year. The thread ended in "find out what chip it is". As far as I know I can't see the BIOS chip on this portable. Oh well.
Then also something about using MTD. I guess I'll try that and see what MTD reports.
Is the BIOS chip on this machine really only 8KB in size? I find that really hard to believe.
I take it there aren't good programming manuals/data sheets for the M-Systems line of chips? I found one crappy document via google. That would be a shame; AMD and Intel seem real good about documenting their flash ships.
Jeff
-
Jeff Carr