Date: Thu, 4 Dec 1997 01:04:12 -0700 From: Nate Williams <nate@mt.sri.com> To: Mike Smith <mike@smith.net.au> Cc: "Glenn Dicus" <gdicus@nomadix.com>, mobile@FreeBSD.ORG Subject: Re: Help Message-ID: <199712040804.BAA24286@mt.sri.com> In-Reply-To: <199712040625.QAA01864@word.smith.net.au> References: <199712040551.VAA15167@mail.nomadix.com> <199712040625.QAA01864@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'm keeping this cc'd to the list; there's every chance that this
> information is useful to other people as well.
>
> > Sorry, you have to excuse me. I have been trying to get the PC Card on the
> > ElanSC400 Evaluation Board for 3 weeks 24-7 with no luck what so ever. The
> > problems have been to many to name.
In the future, try emailing the mobile list. We're here to help, or at
least bitch about the hardware. :)
> > However, my present situation is that
> > FreeBSD does not recognize the second slot when a card is inserted.
Sounds like a VLSI board. They do things a non-standard way, and
it's possible the VLSI work-around code doesn't work on all the
hardware.
> The
> > cards that I have tried have been Eagle Technology's NE2000, Fujitsu
> > MBH10302, 3Com 3C3589C/D.
The 3COM card should *always* work. If it doesn't, then you've got
setup/hardware problems.
> > Also, a reoccurring problem has been pccardc's inability to read the CIS,
> > returning "no entry in database for "null" ("null")".
>
> It sounds like this is indicative of a pretty major problem; if pccardc
> can't read the CIS information, pccardd (which uses the same code) is
> not going to be able to determine what the card is.
Right, something is *really* bogus. Did this ever work? What kind of
changes are you making to the FreeBSD kernel code? Did you make any
changes? We'd like to help, but need more information than you're
giving us.
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712040804.BAA24286>