getting a wireless PCMCIA Card to work

Alvaro Chavarria yellowdog-general@lists.terrasoftsolutions.com
Mon Mar 1 19:03:02 2004 

I have been having problems too. I've tried three cards already =20
(including the Orinoco you mention). I am about to give up. If anyone =20=

has had any luck please tell me.


On 1 Mar, 2004, at 8:23 PM, Nathan Kline wrote:

>
> well, I got the Orinoco silver card today and I popped it in and went =20=

> through the configuration but still a no go. I went to the terminal =20=

> and did "cardctl ident" and got this:
>
> 	Socket 1:
> 		product info: "Agere Systems", "Wireless PC Card Model =
0110, "", ""
> 		manfid: 0x0156, 0x0003
> 		function: 6 (network)
>
> well in the list of possible drivers in Network Configuration i have =20=

> three Lucent  drivers:
> =09
> 	Lucent Orinoco and Prism II-based PCMCIA
> 	Lucent Orinoco/Melco PCMCIA (alternate)
> 	Lucent/Agere/Melco PCMCIA (alternate)
>
> well it seems obvious that I should use the Lucent/Agere/Melco PCMCIA =20=

> (alternate) but when i select it i get this error:
>
> 	modprobe wvlan_cs
>
> 	modprobe: Can't locate module wvlan_cs
>
> the Lucent Orinoco and Prism II-based PCMCIA loads fine but the two =20=

> alternate ones give me that error (the Lucent Orinoco/Melco PCMCIA =20
> (alternate) of course names a different driver that it cant find)
>
> Where should i look to find these or what should i do so i can load =20=

> the correct driver?
>
> -Mitb
> [o=F7<]
>> On Feb 23, 2004, at 5:24 PM, Nathan Kline wrote:
>>
>>> No it isn't, This D-link card is the latest revision of the DWL-650 =20=

>>> and is most likely not one that will work with that driver
>>>
>>> I did purchase an orinoco silver card from ebay for 22$ so I will =20=

>>> see if that works.
>>>
>>> http://cgi.ebay.com/ws/eBayISAPI.dll?=20
>>> ViewItem&item=3D3078905439&category=3D45000
>>> there is the link in case anyone wants to get one too. $22.95 and I =20=

>>> think there are 11 left.
>>>
>>> -Mitb
>>> [o=F7<]
>>> On Feb 23, 2004, at 3:35 PM, Jim Pelton wrote:
>>>
>>>> Eth1 should work fine, as long as there are no other devices using =20=

>>>> eth1.
>>>> Is your card working now? --Jim
>>>>
>>>> On Mon, 2004-02-23 at 13:11, Nathan Kline wrote:
>>>>> yes, the cardmgr is now running so I'm half way there. just to =
make
>>>>> sure, the device name should be set to eth1?
>>>>> -Mitb
>>>>> [o=C3=B7<]
>>>>> On Feb 23, 2004, at 11:10 AM, Jim Pelton wrote:
>>>>>
>>>>>> 	I struggled a while with my Wallstreet 266 and a Linksys wpc11 =20=

>>>>>> v.3
>>>>>> card.  I tried many cards, because I initially wanted a 54MBps =20=

>>>>>> card,
>>>>>> but
>>>>>> those chip-sets are not supported very well yet under YDL.
>>>>>> 	I recommend you use a card with the Orinoco PrismII chip-set =20
>>>>>> because
>>>>>> it
>>>>>> seems to be widely supported. You can check the net to find out =20=

>>>>>> what
>>>>>> chip-set your D-Link has in it. Be careful because cards are =20
>>>>>> packaged
>>>>>> under the same model, but with different chip-sets! For example =
my
>>>>>> Linksys wpc11 v.3 has the PrismII chip-set, however v.4 of the =20=

>>>>>> wpc11 is
>>>>>> a RealTek chipset or something, and is not totally supported out =20=

>>>>>> of the
>>>>>> box by YDL.
>>>>>> 	If you have a PrismII card, you should check this file:
>>>>>> /etc/sysconfig/pcmcia:
>>>>>> It should read:
>>>>>> PCMCIA=3Dyes
>>>>>> PCIC=3Dyenta_socket
>>>>>> PCIC_OPTS=3Ddo_scan=3D0
>>>>>> CORE_OPTS=3D
>>>>>> CARDMGR_OPTS=3D-f
>>>>>> 	After a clean install, my /etc/sysconfig/pcmcia file had read
>>>>>> pcmcia=3Dno
>>>>>> and pcic=3D*blank*.
>>>>>> 	This is the only change I had to make. After I made the change, =
I
>>>>>> restarted pcmcia services. cardmgr launched and recognized the =20=

>>>>>> card
>>>>>> (with two similar beeps). Then you can add the card via
>>>>>> redhat-config-network as an Orinoco/PrismII card.
>>>>>> 	If you do not have a PrismII card, you may still be able to get =20=

>>>>>> your
>>>>>> chipset to work. There are drivers online which you may compile =20=

>>>>>> and
>>>>>> install, though support for others seems pretty weak by =20
>>>>>> comparison to
>>>>>> PrismII. Or you can get the Linuxant DriverLoader, which allows =20=

>>>>>> you to
>>>>>> use Windows drivers for WLAN devices on Linux machines. It's =20
>>>>>> about $40
>>>>>> i
>>>>>> believe. Hope this helps, Jim
>>>>>>
>>>>>> On Mon, 2004-02-23 at 09:59, Nathan Kline wrote:
>>>>>>> hmm I edited my /etc/rc.d/init.d/pcmcia file as specified in =
your
>>>>>>> script and yet cardmgr is still not running even after a reboot.
>>>>>>>
>>>>>>> I have a D-link dwl-650 card on a powerbook walstreet running =
YLD
>>>>>>> 3.0.1. When I go into the network configuration panel I set up a =
=20
>>>>>>> new
>>>>>>> network device and select the D-link 650 driver (the IRQ is set =20=

>>>>>>> to
>>>>>>> unknown, should this be different?) and the device is eth1. I =20=

>>>>>>> then
>>>>>>> activate it and I get this error:
>>>>>>>
>>>>>>> "pcnet_cs device does not seem to be present, delaying eth1
>>>>>>> initialization."
>>>>>>>
>>>>>>> any light you or anyone else might be able to shed on this would =
=20
>>>>>>> be
>>>>>>> greatly appreciated.  so far this is hte only snag I have run =20=

>>>>>>> into
>>>>>>> with
>>>>>>> this install.
>>>>>>>
>>>>>>> -Mitb
>>>>>>> [o=C3=83=C2=B7<]
>>>>>>> On Feb 23, 2004, at 7:27 AM, george_geller@earthlink.net wrote:
>>>>>>>
>>>>>>>> First make sure that your /etc/rc.d/init.d/pcmcia is working =
and
>>>>>>>> launching cardmgr.
>>>>>>>>
>>>>>>>> Is cardmgr running?  To find out do a ps -aux | grep card
>>>>>>>>
>>>>>>>> Mine shows:
>>>>>>>> root       414  0.0  0.2  1604  708 ?        S    05:31   0:00
>>>>>>>> /sbin/cardmgr -f
>>>>>>>>
>>>>>>>> If you don't have cardmgr running, pcmcia cards will not work.
>>>>>>>>
>>>>>>>> I had to change /etc/rc.d/init.d/pcmcia according to this =20
>>>>>>>> script:
>>>>>>>>
>>>>>>>> --- pcmcia.01	2004-02-06 05:42:28.000000000 -0800
>>>>>>>> +++ pcmcia	2004-01-17 08:14:00.000000000 -0800
>>>>>>>> @@ -96,27 +96,31 @@
>>>>>>>>  	if [ ! -f $SC ] ; then umask 022 ; touch $SC ; fi
>>>>>>>>  	if [ "$SCHEME" ] ; then umask 022 ; echo $SCHEME > $SC ; =
fi
>>>>>>>>  	grep -q pcmcia /proc/devices
>>>>>>>> -	if [ $? -ne 0 ] ; then
>>>>>>>> -	    if [ -d /lib/modules/preferred ] ; then
>>>>>>>> -		PC=3D/lib/modules/preferred/pcmcia
>>>>>>>> -	    else
>>>>>>>> -		PC=3D/lib/modules/`uname -r`/pcmcia
>>>>>>>> -	    fi
>>>>>>>> -	    KD=3D/lib/modules/`uname -r`/kernel/drivers/pcmcia
>>>>>>>> -	    if [ -d $PC ] ; then
>>>>>>>> -		echo -n " modules"
>>>>>>>> -		/sbin/modprobe pcmcia_core $CORE_OPTS
>>>>>>>> -		/sbin/modprobe $PCIC $PCIC_OPTS
>>>>>>>> -		/sbin/modprobe ds
>>>>>>>> -	    elif [ -d $KD ] ; then
>>>>>>>> -		/sbin/modprobe pcmcia_core
>>>>>>>> -		/sbin/modprobe $PCIC
>>>>>>>> -		/sbin/modprobe ds
>>>>>>>> -	    else
>>>>>>>> -		echo $" module directory $PC not found."
>>>>>>>> -		break
>>>>>>>> -	    fi
>>>>>>>> -	fi
>>>>>>>> +# 	if [ $? -ne 0 ] ; then
>>>>>>>> +# 	    if [ -d /lib/modules/preferred ] ; then
>>>>>>>> +# 		PC=3D/lib/modules/preferred/pcmcia
>>>>>>>> +# 	    else
>>>>>>>> +# 		PC=3D/lib/modules/`uname -r`/pcmcia
>>>>>>>> +# 	    fi
>>>>>>>> +# 	    KD=3D/lib/modules/`uname -r`/kernel/drivers/pcmcia
>>>>>>>> +# 	    if [ -d $PC ] ; then
>>>>>>>> +# 		echo -n " modules"
>>>>>>>> +# 		/sbin/modprobe pcmcia_core $CORE_OPTS
>>>>>>>> +# 		/sbin/modprobe $PCIC $PCIC_OPTS
>>>>>>>> +# 		/sbin/modprobe ds
>>>>>>>> +# 	    elif [ -d $KD ] ; then
>>>>>>>> +# 		/sbin/modprobe pcmcia_core
>>>>>>>> +# 		/sbin/modprobe $PCIC
>>>>>>>> +# 		/sbin/modprobe ds
>>>>>>>> +# 	    else
>>>>>>>> +# 		echo $" module directory $PC not found."
>>>>>>>> +# 		break
>>>>>>>> +# 	    fi
>>>>>>>> +# 	fi
>>>>>>>> + 		/sbin/modprobe pcmcia_core
>>>>>>>> + 		/sbin/modprobe $PCIC
>>>>>>>> + 		/sbin/modprobe ds
>>>>>>>> +
>>>>>>>>  	if [ -s /var/run/cardmgr.pid ] && \
>>>>>>>>  	    kill -0 `cat /var/run/cardmgr.pid` 2>/dev/null ; =
then
>>>>>>>>  	    echo $" cardmgr is already running."
>>>>>>>>
>>>>>>>> Hope this helps,
>>>>>>>>
>>>>>>>> George
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> yellowdog-general mailing list
>>>>>>>> yellowdog-general@lists.terrasoftsolutions.com
>>>>>>>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-
>>>>>>>> general
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> yellowdog-general mailing list
>>>>>>> yellowdog-general@lists.terrasoftsolutions.com
>>>>>>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-=20=

>>>>>>> general
>>>>>>
>>>>>> _______________________________________________
>>>>>> yellowdog-general mailing list
>>>>>> yellowdog-general@lists.terrasoftsolutions.com
>>>>>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-=20=

>>>>>> general
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> yellowdog-general mailing list
>>>>> yellowdog-general@lists.terrasoftsolutions.com
>>>>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-=20
>>>>> general
>>>>
>>>> _______________________________________________
>>>> yellowdog-general mailing list
>>>> yellowdog-general@lists.terrasoftsolutions.com
>>>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-=20
>>>> general
>>>>
>>>
>>> _______________________________________________
>>> yellowdog-general mailing list
>>> yellowdog-general@lists.terrasoftsolutions.com
>>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-=20
>>> general
>>>
>>
>> _______________________________________________
>> yellowdog-general mailing list
>> yellowdog-general@lists.terrasoftsolutions.com
>> =
http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>>
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords> =
site:terrasoftsolutions.com'