Ok. I've been bit-banging all day and cannot get docprobe to find the DOC chips.
This board is a tyan tiger 1832DL 440BX (2x750P3). I'm wonder if there are any known issues with DOC's on the 440bx boards? Or any known issues with any of the lately issued DOC Millinium chips?
It looks as if docprobe is a) not recognizing the DOC or b) isn't probing the correct address. (i've fiddled with the high (etc) settings for the driver in the kernel config too.)
I've gotten as far as this:
Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 89 found at 0xc8000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 31 found at 0xca000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xcc000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xce000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 0C found at 0xd0000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 66 found at 0xd2000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xd4000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xd6000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xd8000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xda000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xdc000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xde000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 00 found at 0xe0000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID C2 found at 0xe2000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 75 found at 0xe4000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID 6C found at 0xe6000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xe8000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xea000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xec000 Jun 7 16:17:16 Possible DiskOnChip with unknown ChipID FF found at 0xee000 Jun 7 16:17:16 No recognised DiskOnChip devices found
On 7 Jun 2003, roger wrote:
This board is a tyan tiger 1832DL 440BX (2x750P3). I'm wonder if there are any known issues with DOC's on the 440bx boards? Or any known issues with any of the lately issued DOC Millinium chips?
I hate to say it, but it may be the old "hidden write enable" problem, i.e. there is a special GPIO line used to control write enable in addition to the normal mechanism.
ron
On Sat, 2003-06-07 at 21:11, ron minnich wrote:
On 7 Jun 2003, roger wrote:
This board is a tyan tiger 1832DL 440BX (2x750P3). I'm wonder if there are any known issues with DOC's on the 440bx boards? Or any known issues with any of the lately issued DOC Millinium chips?
I hate to say it, but it may be the old "hidden write enable" problem, i.e. there is a special GPIO line used to control write enable in addition to the normal mechanism.
ron
(geez. i hate that. when clicking "reply" in the email client, it sets the return address to ron@blah.domain instead of using the linuxbios mailling address! oh well.)
I've done quite a bit of research and see you make mention of this once during a discussion (with no follow-ups).
Is this problem chip specific (issue with the DOC)?
A simple solution would be to aquire a Eeprom programmer (ie h/w to connect via serial cable to program/flash/read eeproms?)
If this problem is relative to my tyan tiger 1832dl (440BX) motherboard, I could probably utilize a 440GX(?) board that I also have as a solution.
Ok. by a fluke accident, i've gotten the DOC recognized.
I'm on a 2x750P3 SMP Tyan Tiger 1832dl and induced a "kernel oops" on cpu1 by trying to insmod ./bios.o (http://www.openbios.info/download/index.html devbios-0.3.2.tar.gz)
the docprobe.o is compiled with "Physical Address = 0" and no other options for docprobe.o. ... using doc2001.o
i've attached dmesg output below of the oops condition when trying to insmod bios.o and then after the kernel-oops occurred, modprobed mtdcore, mtdchar,dos2001,dosprobe doc_config_location=0xfff00000. (unknown if the doc_config_location is needed...have yet to try without as i've only duplicated 3 times.)
-
roger -
ron minnich