Now I have it recognized with without the irq and I/O space problem because I
had an irq 9 conflict but now I am getting :
wi0: <WaveLAN/IEEE 802.11> at port 0x240-0x27f irq 9 slot 0 on pccard0
wi0: Ethernet address: 00:60:1d:03:f4:08
wi0: device timeout
wi0: tx buffer allocation failed
wi0: xmit failed
wi0: device timeout
wi0: tx buffer allocation failed
wi0: xmit failed
It worked fine with this configuration on current for many months. I'm not
sure if I am making progress or not:-)
ed
I'm using 5.0 current as of this morning.
Russell Cattelan wrote:
> Edwin Culp wrote:
>
> > On today's current, I plugged in my WaveLan Card that I haven't used for
> > about a week and it first has a problem with IRQ: wi0: No irq?! I
> > added some others and it responded with: wi0: No I/O space?! Has
> > something changed in the last few days that would cause this? My
> > network card DE-660 just keeps plugging away, thank goodness:-)
> >
> > Thanks for any help,
>
> That card is really sensitive to what base address and what irq is
> used, it can't conflict with anything.
>
> I've had better luck with setting the io to 0x100 in pccard.conf.
> irq 9 has worked, if you aren't using the parallel port disable it
> in the bios then irq 7 will be free.
>
> Now if I can only figure out why after upgrading my 4.0-RELEASE
> to the latest 4.0 the pccardd stops reading any info from the card.
>
> May 1 00:46:19 lupo pccardd[68136]: No card in database for ""("")
>
> >
> >
> > ed
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
