Date: Thu, 23 Oct 1997 16:31:56 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: Kenneth Ingham <ingham@i-pi.com> Cc: mobile@freebsd.org Subject: Re: 2.2.5-RELEASE and PC Cards Message-ID: <199710232231.QAA17227@rocky.mt.sri.com> In-Reply-To: <19971023142754.64160@fatman.i-pi.com> References: <19971023142754.64160@fatman.i-pi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I just upgraded my laptop which used to run 2.2.2+PAO to 2.2.5-RELEASE.
> The upgrade went OK except for the PCCArds no longer work. I built a
> new kernel with the ep, crd, and pcic drivers and booted it.
So far so good.
> I've verified with pccardc dumpcis that the manufacturer and version
> match. This is not the PAO pccard.conf file that I was using (but
> it didn't work either). In fact, here's my pccard.conf file (I
> removed everything except the info for the cards I am trying to
> use (hmmm, the date in this is old, but I didn't see a newer one
> in the upgrade files):
It's the same in 2.2.5.
> # Removing all IRQ conflicts from this file can't be done because of some
> # IRQ-selfish PC-cards. So if you want to use some of these cards in
> # your machine, you will be forced to modify their IRQ parameters from
> # the following list.
> #
> # IRQ == 0 means "allocate free IRQ from IRQ pool"
> # IRQ == 16 means "do not use IRQ (e.g. PIO mode)"
> #
> # $Id: pccard.conf.sample,v 1.4 1996/06/19 01:28:07 nate Exp $
>
> # Generally available IO ports
> io 0x240-0x360
> # Generally available IRQs (Built-in sound-card owners remove 5)
> irq 3 5 10 11 13 15
> # Available memory slots
> memory 0xd4000 96k
>
> # 3Com Etherlink III 3C589B, 3C589C
> card "3Com Corporation" "3C589"
> config 0x1 "ep0" ?
^
Change this to 10 or 11. (I know, humor me.)
> insert echo 3Com Etherlink III inserted
> insert /etc/pccard_ether ep0 -link0 link1
> # insert /etc/pccard_ether ep0 link0 -link1
> remove echo 3Com Etherlink III removed
> remove /sbin/ifconfig ep0 delete
> # US Robotics Sportster PCMCIA V.34
> # US Robotics COURIER PCMCIA V.34
> card "USRobotics" "PCMCIA 28800 Data/Fax"
> config 0x3 "sio2" 3
> insert echo USRobotics PCMCIA Modem inserted
> remove echo USRobotics PCMCIA Modem removed
OK, from above:
> sio2 not found at 0x3e8
^^^^^
> Tuple #13, code = 0x1b (Configuration entry), length = 11
> 000: 83 41 18 aa 60 f8 02 07 30 b8 86
> Config index = 0x3
^^^^^^^^^^^
> Interface byte = 0x41 (I/O) +RDY/-BSY active
> Card decodes 10 address lines, 8 Bit I/O only
> I/O address # 1: block start = 0x2f8 block length = 0x8
^^^^^
> I/O address # 1: block start = 0x2f8 block length = 0x8
> IRQ modes: Level
> IRQs: 4 5 11 12 13 15
^^^^^^^^^^^^^^^
The config index and the port differ. Also, the card "doesn't support"
IRQ 3 (although that shouldn't mattter, but it does due to a bug I
think.)
So, replace the above config line with:
config 0x3 "sio1" 5
(Use IRQ 5 or 11, again humor me.)
> And, I used the undocumented pccardc dumpcis on the cards and got the
> following.
It's documented as well as most things are documented. :) :)
[ Dumps deleted ]
> The link light lights on the 3com card. When I insert it (or the modem),
> the following appear in the log:
The link light is the 'power light'.
> Oct 23 13:18:00 socrates cardd[264]: driver allocation failed for 3Com Corporation
Something must have happened before this.
> Oct 23 13:18:09 socrates su: ingham to root on /dev/ttyp3
> Oct 23 14:06:37 socrates /kernel: Card removed, slot 0
> Oct 23 14:06:45 socrates /kernel: Card inserted, slot 0
> Oct 23 14:06:51 socrates /kernel: Card removed, slot 0
> Oct 23 14:06:56 socrates cardd[264]: ioctl (PIOCSIO): Device not configured
This error is due to the card being swapped in/out quickly, so the
device driver never was fully loaded/unloaded.
> Oct 23 14:06:58 socrates /kernel: Card inserted, slot 1
> Oct 23 14:06:58 socrates /kernel: Card inserted, slot 0
> Oct 23 14:07:08 socrates cardd[264]: driver allocation failed for USRobotics
> Oct 23 14:07:18 socrates cardd[264]: driver allocation failed for 3Com Corporation
>
> (The dreaded ``driver allocation failed'' message! :-)
See above how to correct them.
> One thing that might be useful in troubleshooting is to know what
> device is not configured in the message above...
The card was inserted/removed too quickly.
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710232231.QAA17227>