From owner-freebsd-questions  Tue May  2 11:16:53 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id LAA11510
          for questions-outgoing; Tue, 2 May 1995 11:16:53 -0700
Received: from cs.weber.edu (cs.weber.edu [137.190.16.16])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA11489
          ; Tue, 2 May 1995 11:16:31 -0700
Received: by cs.weber.edu (4.1/SMI-4.1.1)
	id AA07855; Tue, 2 May 95 11:39:26 MDT
From: terry@cs.weber.edu (Terry Lambert)
Message-Id: <9505021739.AA07855@cs.weber.edu>
Subject: Re: Problems with zp0 driver in 041295 SNAP?
To: eaparis@mke.ab.com (Eloy A. Paris)
Date: Tue, 2 May 95 11:39:26 MDT
Cc: questions@FreeBSD.org, hackers@FreeBSD.org
In-Reply-To: <199505020420.XAA06693@tinman.mke.ab.com> from "Eloy A. Paris" at May 1, 95 11:20:41 pm
X-Mailer: ELM [version 2.4dev PL52]
Sender: questions-owner@FreeBSD.org
Precedence: bulk

> What's the problem? Well, the zp0 driver sees the card but then when it
> reads the card information to make sure it has what it is supposed to have
> (after the driver has written the I/O base address and the IRQ), there is
> nothing there.

[ ... ]

> I compiled the if_zp.c file with the symbol ZP_DEBUG defined but I could not
> tell what is going on since I do not have any technical infomation about the
> card nor the PCMCIA controller.
> 
> But this is not all: the weird part is that after each time I reboot my
> computer with FreBSD the Card Information Structure (CIS) of my card gets
> corrupted.

You will probably need to determine what PCMCIA bridge chipset is
being used by your machine before anyone can tell you if it is
supported (and if not, write code to support it).

> After this corruption I can not get into the 3Com's configuration program
> (for DOS) for this card (3C589CFG.EXE) because the program aborts with the
> message "Corrupted CIS. Please replace card with a good one and try again."
> Thanks God I found in 3Com's BBS a program to clean the CIS because if not I
> would not even be able to use Ethernet under DOS (that I am doing pretty fine.)

Clearly this is a sufficiently common problem that 3COM has had to build
a fix for it; it's kind of silly that that program is not built into the
configuration program if it's that common.

Since 3COM is aware of the problem, I'm betting that some clue to the
cause could be had by contacting 3COM.  If their BBS is cheaply
accessable to you, you might try posting a question about what is
causing the corruption, and then let the author of the driver for
FreeBSD know what to do about.  At the very least, the information
about how they fix the CIS would be useful, since breaking it must
be doing something similar.


					Terry Lambert
					terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.