Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Apr 2001 11:40:56 -0700
From:      "Kim C. Callis" <kcallis@c2associates.net>
To:        <freebsd-mobile@freebsd.org>
Subject:   Re: NICs & modems 
Message-ID:  <002001c0c900$453a3740$4200a8c0@c2associates.net>
References:  <200104182319.QAA24299@mina.soco.agilent.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I am getting the following message when inserting the Wavelan

pccardd[53]: Card "Lucent Technologies"("WaveLAN/IEEE")
[Version 01.01] matched "Lucent Technologies" ("WaveLAN/IEEE") [(null)]
[(null)]
pccardd[53]: Failed to allocate IRQ for Lucent Technologies

When I do a dmsg | grep pcic0 I get the following

pcic0: <VLSI 82C146> at port 0x3e0 irq 10 on isa 0
pcic0: mamagement 10
pccard0: <PC Card bus -- kludge version> on pcic0
pccard1: <PC Card bus -- kludge version> on pcic0

I thought maybe cleaning up the /etc/defaults/pccard.conf would make things
a little better. I changed the memory location and removed some of the irq,
and still nothing.

Any suggestions?

----- Original Message -----
From: "Darryl Okahata" <darrylo@soco.agilent.com>
To: "Kim C. Callis" <kcallis@c2associates.net>
Cc: "Brian Reichert" <reichert@numachi.com>; <freebsd-mobile@FreeBSD.ORG>
Sent: Wednesday, April 18, 2001 4:19 PM
Subject: Re: NICs & modems


> "Kim C. Callis" <kcallis@c2associates.net> wrote:
>
> > > > I can ifconfig the card, but I am unable to get it to communicate.
If I
> > set it to mode 1, both lights go out. If it is set to mode 3, one light
> > flashes, but still nothing. This is driving me to drink!
>      [ ... ]
> > WEP is enabled with a 10 character hex key which is correct. The same
key
> > functions for all of our linux laptops. And I double checked it on the
> > Airport which is providing our point to point.
>
>      If you're using an Apple Airport, you must use BSS mode (mode 1);
> mode 3 is ad-hoc mode, which does not and cannot communicate with access
> points like the Airport.
>
>      Unless you void the warranty, the Airport can only handle 40-bit
> encryption.  Make sure your keys are short enough.  Also, make sure that
> you've enabled encryption; setting the encryption key does not enable
> encryption (it just sets the key).  And make sure that you've selected
> the correct key (of the four possible keys), if encryption is enabled.
>
>      Is the network name correct?  It's got to match the network name on
> the Airport (unless you set it to "ANY", I believe).
>
>      Is the channel correct?
>
>      See the wicontrol man page for more information.
>
> --
> Darryl Okahata
> darrylo@soco.agilent.com
>
> DISCLAIMER: this message is the author's personal opinion and does not
> constitute the support, opinion, or policy of Agilent Technologies, or
> of the little green men that have been following him all day.
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-mobile" in the body of the message
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002001c0c900$453a3740$4200a8c0>