Greetings, everyone. I am fairly new to LinuxBIOS, having fooled with it for only a couple of days. Needless to say, I've been learning a lot. I have had a lot of success with this great project, but recently have been meeting with some failures as well. I'm searching for the "Magic Potion" of CVS checkout date, patches, and config file that makes it work for me, even if only passably, until the v2 port can proceed and the VGA issues can be re-addressed.
I am trying to use a VIA EPIA M-1000 (Ezra) board and I'm having limited success that at this point, I cannot decide are problems with my LinuxBIOS configuration/build or problems with the code I am using. I was able to successfully build and run LinuxBIOS with the serial console and using FILO or etherboot (via-rhine and ide-disk) payloads without. I am building code from a current (Mar. 25, 2004) v1 cvs checkout.
1) The machine has 512MB SDRAM, but LinuxBIOS only sets up 128MB. Is this a problem with my config file? I know that v1 has some limitations with memory on this platform. Was there a time when this worked better on epia-m?
2) 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.
3) Despite my sincerest efforts, VGA is doing nothing. I have extracted the VGA bios from both /proc/kcore as described in the HOWTO and from a ROM image using CBROM (padded to 64k).. neither of these work. The VGA bios I'm trying is from the latest release of the BIOS from VIA.
I understand that some people are having success on epia-m/vga using a checkout from last july and a patch from Dave Ashley.. I may have mistakenly believed that all that made it into CVS, but if not, what is the correct checkout date, and where can I find the patch?
Thanks in advance to the list for any assistance!
John Laur
On Fri, 26 Mar 2004, John Laur wrote:
- The machine has 512MB SDRAM, but LinuxBIOS only sets up 128MB. Is
this a problem with my config file? I know that v1 has some limitations with memory on this platform. Was there a time when this worked better on epia-m?
It's a v1 limitation, which is why I want to start V2 next week.
- 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.
arg. flash_rom should have "just worked". My guess is we need southbridge docs for this thing as it is new hardware.
- Despite my sincerest efforts, VGA is doing nothing. I have extracted
the VGA bios from both /proc/kcore as described in the HOWTO and from a ROM image using CBROM (padded to 64k).. neither of these work. The VGA bios I'm trying is from the latest release of the BIOS from VIA.
let's do one thing at a time ... let's fix the first two things. Do we have chipset docs?
I understand that some people are having success on epia-m/vga using a checkout from last july and a patch from Dave Ashley.. I may have mistakenly believed that all that made it into CVS, but if not, what is the correct checkout date, and where can I find the patch?
I have incorporated dave's patches, which is why it ought to work ...
ron
ron minnich wrote:
let's do one thing at a time ... let's fix the first two things. Do we have chipset docs?
The Epia-M and M11 use the Via VT8235 southbridge, which is in the V1 source tree.
-Bari
Ron, I think the CVS is broken. 1 week ago I was trying to use it on my M-6000 and it failed. Let me take a diff between current CVS and what's working for me( IDE+VGA+Splash ). Dmitry/
PS: I've plans to visit clusterworld, will stop by if any...
----- Original Message ----- Subject: Re: EPIA-M "Magic Potion"?
I have incorporated dave's patches, which is why it ought to work ...
ron
On Fri, 26 Mar 2004, Dmitry Borisov wrote:
I think the CVS is broken. 1 week ago I was trying to use it on my M-6000 and it failed. Let me take a diff between current CVS and what's working for me( IDE+VGA+Splash ).
thanks, hope to see you at clusterworld.
ron
Ron, Dimitry,
Not to get too far ahead of myself here, but it seems CVS is probably not completely broken. I am booting into LinuxBIOS fine, just there is no PCI Bus #1 and no IRQ's are assigned to anything.
The reason VGA is not initializing is because for some reason LinuxBIOS is not seeing PCI Bus #1 and thus can't locate an 0x0300 VGA class PCI device when it goes to init the VGA BIOS; otherwise, I think it would probably work fine. The IRQ problem is a more serious issue...
Since memory detection is waiting on the v2 port and we have the flash problem at least identified, I'm going to poke at this VGA/PCI/IRQ thing some more and see what I can see...
Any ideas?
John
-----Original Message----- From: linuxbios-admin@clustermatic.org [mailto:linuxbios- admin@clustermatic.org] On Behalf Of Dmitry Borisov Sent: Friday, March 26, 2004 11:39 AM To: linuxbios@clustermatic.org Subject: Re: EPIA-M "Magic Potion"?
Ron, I think the CVS is broken. 1 week ago I was trying to use it on my
M-6000
and it failed. Let me take a diff between current CVS and what's
working
for me( IDE+VGA+Splash ). Dmitry/
PS: I've plans to visit clusterworld, will stop by if any...
----- Original Message ----- Subject: Re: EPIA-M "Magic Potion"?
I have incorporated dave's patches, which is why it ought to work
...
ron
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Subject: RE: EPIA-M "Magic Potion"?
Ron, Dimitry,
Not to get too far ahead of myself here, but it seems CVS is probably not completely broken. I am booting into LinuxBIOS fine, just there is no PCI Bus #1 and no IRQ's are assigned to anything.
The reason VGA is not initializing is because for some reason LinuxBIOS is not seeing PCI Bus #1 and thus can't locate an 0x0300 VGA class PCI device when it goes to init the VGA BIOS; otherwise, I think it would probably work fine. The IRQ problem is a more serious issue...
Since memory detection is waiting on the v2 port and we have the flash problem at least identified, I'm going to poke at this VGA/PCI/IRQ thing some more and see what I can see...
Any ideas?
John
Guys, Here is the patch to make EPIA-M work with splash and VGA. See attached config for my settings...
Ron, FYI: I did some changes in hardwaremain.c to make sure splash is called after VGA init and early enough to see the splash. It may brake some other builds, unlikely though...
Enjoy, Dmitry/
On Sun, 28 Mar 2004, Dmitry Borisov wrote:
Ron, FYI: I did some changes in hardwaremain.c to make sure splash is called after VGA init and early enough to see the splash. It may brake some other builds, unlikely though...
IF my epia-m builds I will try all of this EXCEPT for the hardwaremain changes for now. I worry just a bit since those change the order of some operations. But I will try them later.
ron
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.
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.
-----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
I am having the same difficulty flashing the same part on a Tyan s2885 board. I'll check to see that we're probing it correctly.
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
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
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
Maybe just not on that specific motherboard. Someone probably had it working on another motherboard, otherwise there we wouldn't have it in the code.
If you have some extra cash, you can try ordering a different part like the SST49LF080A.
On Fri, 26 Mar 2004, John Laur wrote:
So, am I correct to assume that flashing the BIOS on my board is not (at least) yet possible with flash_rom?
stick with DOS until we work this out.
ron
On Fri, 26 Mar 2004, Hendricks David W. wrote:
Oops, it's not LPC compatible :( Ollie says we need a really old mainboard to flash it.
david, bring up the geode cluster again and use that to flash.
ron
On Fri, Mar 26, 2004 at 12:27:31PM -0600, John Laur wrote:
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.)
The RD1-PL is working fine on my EPIA M9000:
[root@tiny bios]# ./flash_rom romimage Calibrating timer since microsleep sucks ... takes a second Setting up microsecond timing loop 184M loops per second OK, calibrated, now do the deed Enabling flash write on VT8235...tried to set 0x45 to 0x55 on VT8235 failed (WARNING ONLY) Trying Am29F040B, 512 KB probe_29f040b: id1 0x7f, id2 0x45 Trying At29C040A, 512 KB probe_jedec: id1 0xbf, id2 0xb6 Trying Mx29f002, 256 KB probe_29f002: id1 191, id2 182 Trying SST29EE020A, 256 KB probe_jedec: id1 0xbf, id2 0xb6 Trying SST28SF040A, 512 KB probe_28sf040: id1 0x7f, id2 0x45 Trying SST39SF020A, 256 KB probe_39sf020: id1 0xbf, id2 0xb6 SST39SF020A found at physical address: 0xfffc0000 Part is SST39SF020A Programming Page: 0063 at address: 0x0003f000
This is with the switch set to "RD1".
Couple of notes:
- don't run the setpci command that is in the epia-m readme. It causes all sorts of errors (if you already ran it, reboot and run flash_rom directly.)
- My flash_rom was compiled back in November; it is possible flash_rom has regressed. If you're still having problems I can email you my binary.
- I guess it is also possible that there are different RD1-PL models out there..
-Kevin
Holy crap! It works if you blatantly *DONT* follow the documentation and/or the advice of the developers! (Just kidding guys; you all rock ;) Seriously, though, the README under src/mainboard/via/epia-m/ ought to at least note that the setpci command is not necessary on some epia-m's...
Both the original BIOS flash part and the RD1 flash part are recognized. The RD1-PL uses W9F002U and the original BIOS is SST39SF020A like yours. Both flash fine with flash_rom.
Thank you very much for clueing me in. Flashing works perfectly! That DOS crap was a pain in the ass; especially since I had to pop the top to add a floppy drive externally...
John
-----Original Message----- From: linuxbios-admin@clustermatic.org [mailto:linuxbios- admin@clustermatic.org] On Behalf Of Kevin O'Connor Sent: Friday, March 26, 2004 7:21 PM To: John Laur Cc: linuxbios@clustermatic.org Subject: Re: EPIA-M "Magic Potion"?
On Fri, Mar 26, 2004 at 12:27:31PM -0600, John Laur wrote:
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.)
The RD1-PL is working fine on my EPIA M9000:
[root@tiny bios]# ./flash_rom romimage Calibrating timer since microsleep sucks ... takes a second Setting up microsecond timing loop 184M loops per second OK, calibrated, now do the deed Enabling flash write on VT8235...tried to set 0x45 to 0x55 on VT8235 failed (WARNING ONLY) Trying Am29F040B, 512 KB probe_29f040b: id1 0x7f, id2 0x45 Trying At29C040A, 512 KB probe_jedec: id1 0xbf, id2 0xb6 Trying Mx29f002, 256 KB probe_29f002: id1 191, id2 182 Trying SST29EE020A, 256 KB probe_jedec: id1 0xbf, id2 0xb6 Trying SST28SF040A, 512 KB probe_28sf040: id1 0x7f, id2 0x45 Trying SST39SF020A, 256 KB probe_39sf020: id1 0xbf, id2 0xb6 SST39SF020A found at physical address: 0xfffc0000 Part is SST39SF020A Programming Page: 0063 at address: 0x0003f000
This is with the switch set to "RD1".
Couple of notes:
- don't run the setpci command that is in the epia-m readme. It
causes
all sorts of errors (if you already ran it, reboot and run flash_rom directly.)
- My flash_rom was compiled back in November; it is possible flash_rom
has
regressed. If you're still having problems I can email you my
binary.
- I guess it is also possible that there are different RD1-PL models
out
there..
-Kevin _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Fri, Mar 26, 2004 at 10:11:22PM -0600, John Laur wrote:
Both the original BIOS flash part and the RD1 flash part are recognized. The RD1-PL uses W9F002U and the original BIOS is SST39SF020A like yours. Both flash fine with flash_rom.
That's odd - both the original and the RD1 show up as SST39SF020A for me. Maybe there are multiple RD1-PL models floating around out there.
In anycase, I'm glad it works for you. -Kevin
On Sat, 27 Mar 2004, Kevin O'Connor wrote:
That's odd - both the original and the RD1 show up as SST39SF020A for me. Maybe there are multiple RD1-PL models floating around out there.
sure. It's a standard pinout so they're going to plug in whatever is cheapest at the time. It's the PC world,
ron
On Fri, 26 Mar 2004, John Laur wrote:
Holy crap! It works if you blatantly *DONT* follow the documentation and/or the advice of the developers! (Just kidding guys; you all rock ;) Seriously, though, the README under src/mainboard/via/epia-m/ ought to at least note that the setpci command is not necessary on some epia-m's...
Whoever wrote that needs to fix it, but if they don't step up I'll do it.
Sorry about that.
ron
-
Bari Ari -
Dmitry Borisov -
Hendricks David W. -
John Laur -
Kevin O'Connor -
ron minnich