Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Assuming the module has already been downloaded to a temp directory on the HD:
* cp pcmcia-cs-3.1.22.tar.gz /usr/src/linux
* cd /usr/src/linux
* tar zxvf pcmcia-cs-3.1.22.tar.gz
* cd pcmcia-cs-3.1.22
* make config
*/At this point a series of questions will be asked to determine the configuration. Most default answers will work, however, confirm the location of the source directories it asks about. Ensure that if the BIOS is set for a PnP OS, answer YES to this! (Next, it should display "Configuration Successful"/*
* make all(this will display a long list of compile messages - this could take some time)
* make install
At this point the PCMCIA module has been installed.
Basic Install of the Prism2 Wireless Module
Assuming the module has already been downloaded to a temp directory on the HD:
* cp linux-wlan-ng-0.1.8-pre11.tar.gz /usr/src
* cd /usr/src/
* tar zxvf linux-wlan-ng-0.1.8-pre11.tar.gz
* cd linux-wlan-ng-0.1.8-pre11
* make config
*/At this point a series of questions will be asked to determine the configuration. Most default answers will work, however confirm the location of the source directories it asks about.Next, it should display "Configuration Successful"/*
* make all(this will display a long list of compile messages - this could take some time)
* make install
* init 6 (to restart)
somebody who is well used to writing windows docs wrote that doc i guess. this is linux you dont have to reboot after you do some installation. just restart pcmcia service and then use iwconfig
There are actually 3 sets of drivers that work with prism2 based cards, first though is to make certain that you actually have one. Dlink, Linksys, etc. have all recently started changing their onboard chipsets in their cards without actually having changed the model numbers, and no kidding, linksys has even had the gall to keep shipping a CD with links to the linux-wlan site, but with a broadcom card in the box!
To make certain:
/sbin/cardctl ident
and just look to see if it mentions Harris and Prism or the ugly: Texas Instruments or Broadcom.
Under my Profile, in links, are the three main driver packages for prism2 cards.
Also, manthram, I might be wrong about this one, and I kinda hope I am, because I always hated this about the linux-wlan modules, but the last time I used them, a while ago really, they still didn't function properly with wireless extensions and so iwconfig and iwpriv and iwspy never really work right, or really at all.
Is your DWL-650 the newer one with the rectangular antenna housing or the older one with the "axe-head" looking antenna housing? Sadly, the model number is identical for both of these cards, while the chipsets are different. Another way to tell is to check the FCCID on the back of the card, if it ends in "V2", then you've got an ADMtek chipset on your hands.
With the older card, most of the info you'll find when searching on DWL-650 and linux will be correct. With the newer one you may want to check out this page which I've recently put up: http://www.houseofcraig.net/belkin_howto.php
Don't be put off by the filename, it's a howto for revision 2 of both the belkin f5d6020 and the dwl-650. I put it up since so much of the info on the net addresses the older versions of these cards and I was not able to find anything helpful on these revision 2 cards.
I am currently dealing with a DWL-650 that I bought recently. It is a revision P card, which is apparently the latest. Maybe you have a revP card too: look on the back of the card at the serial number, if the last digits say "V.P1" then you have a revP card.
I contacted Tech Support at D-link and they said that the card has a Intersil Prism 3 chipset. I've been trying to get the prism2_cs module to work but to no avail. Then again, when it comes to wireless I'm a complete newbie (when it comes to many things I'm a complete newbie ).
I also read something yesterday about the DWL-650 using a ACX100 chipset (http://acx100.sourceforge.net/matrix.html, footnote 2). I would hope that I got an accurate answer from the folks at D-link about the chipset, but ya never know. . .
Any thoughts from anyone why this card might not be working?
Easiest is to just plug it in and run the command:
/sbin/cardctl ident
and...
/sbin/lspci
If its a prism3 card or an ACX100 card, it'll say so in the ident line. If D-link has switched to something else, then its probably cardbus and will appear under the lspci. Post back here with which it is...
Also, different from the cardbus Linksys WPC11 v4 (Realtek 8180 chipset) I just gave up on, this DWL-650 does not show up in lspci nor does it have the copper strip on the connector.
Thanks.
Last edited by Dark Helmet; 11-26-2003 at 03:11 PM.
I contacted Tech Support again at D-Link asking if anyone had been using the card with Linux there. They said that the only thing that they could suggest is to have the latest version of linux-wlan installed. I guess I'll try that.
Here's a bit of an aside: has anyone been able to to get the WPC11 v4 working without the machine going bonkers and locking up? I had that card at first but traded it for the DWL-650. Once I saw what the driver did I didn't want any part of *that*.
Thank you all for your help!! I'll keep seeing what I can do.
This is a little weird, it looks, I mean really looks like D-Link has switched back to the Intersil Prism chipset for some reason and changed the ident and the manfid again. I wouldn't know why since Intersil got out of the business recently and sold their chipmaking business. D-Link went with the ADMtek chipset with a DWL-650 Version 2, but who knows... maybe with the Intersil transaction done, they've switched back? The ADMtek is a cardbus card, so it should have appeared under lspci, with any other cardbus card, but you guys seem to have a straight pcmcia 16-bit card... so, let's guess for a moment that it's a prism2 card. I hacked up hermes.conf, its the patch file from David Gibson's orinoco+prism driver that you have onboard, its been in the kernel for over a year and a half now. It has idents for cardmgr to bind orinoco_cs with based on the manfid you guys posted above. Copy this file:
finegan: I hacked up hermes.conf, its the patch file from David Gibson's orinoco+prism driver that you have onboard, its been in the kernel for over a year and a half now. It has idents for cardmgr to bind orinoco_cs with based on the manfid you guys posted above. ...
Then hard restart pcmcia so cardmgr re-reads the file and look at the last few lines of: dmesg And see if it loaded the driver. I should look somewhat like this:
Thanks finegan. Ok, with the external pcmcia drivers activated, I get:
Code:
cardmgr[2476]: socket 1: D-Link new DWL-650?? a rev.P?
kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
cardmgr[2476]: executing: 'insmod -v /lib/modules/2.4.20-4GB//pcmcia-external/hermes.o'
cardmgr[2476]: + Using /lib/modules/2.4.20-4GB//pcmcia-external/hermes.o
cardmgr[2476]: + Symbol version prefix ''
kernel: hermes.c: 5 Apr 2002 David Gibson <hermes@gibson.dropbear.id.au>
cardmgr[2476]: executing: 'insmod -v /lib/modules/2.4.20-4GB//pcmcia-external/orinoco.o'
cardmgr[2476]: + Using /lib/modules/2.4.20-4GB//pcmcia-external/orinoco.o
cardmgr[2476]: + Symbol version prefix ''
kernel: orinoco.c 0.11b (David Gibson <hermes@gibson.dropbear.id.au> and others)
cardmgr[2476]: executing: 'insmod -v /lib/modules/2.4.20-4GB//pcmcia-external/orinoco_cs.o'
cardmgr[2476]: + Using /lib/modules/2.4.20-4GB//pcmcia-external/orinoco_cs.o
cardmgr[2476]: + Symbol version prefix ''
kernel: orinoco_cs.c 0.11b (David Gibson <hermes@gibson.dropbear.id.au> and others)
kernel: hermes @ IO 0x400: Timeout waiting for card to reset (reg=0x0000)!
kernel: eth1: failed to reset hardware (err = -110)
kernel: orinoco_cs: register_netdev() failed
kernel: eth0: no IPv6 routers present
cardmgr[2476]: get dev info on socket 1 failed: No such device
and with the kernel pcmcia drivers activated, we see:
Code:
cardmgr[2245]: socket 1: D-Link new DWL-650?? a rev.P?
kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
cardmgr[2245]: module /lib/modules/2.4.20-4GB//pcmcia/hermes.o not available
cardmgr[2245]: executing: 'modprobe -v hermes'
cardmgr[2245]: + /sbin/insmod /lib/modules/2.4.20-4GB/kernel/drivers/net/wireless/hermes.o
cardmgr[2245]: + Using /lib/modules/2.4.20-4GB/kernel/drivers/net/wireless/hermes.o
cardmgr[2245]: + Symbol version prefix ''
kernel: hermes.c: 4 Dec 2002 David Gibson <hermes@gibson.dropbear.id.au>
cardmgr[2245]: module /lib/modules/2.4.20-4GB//pcmcia/orinoco.o not available
cardmgr[2245]: executing: 'modprobe -v orinoco'
cardmgr[2245]: + /sbin/insmod /lib/modules/2.4.20-4GB/kernel/drivers/net/wireless/orinoco.o
cardmgr[2245]: + Using /lib/modules/2.4.20-4GB/kernel/drivers/net/wireless/orinoco.o
cardmgr[2245]: + Symbol version prefix ''
kernel: orinoco.c 0.13b (David Gibson <hermes@gibson.dropbear.id.au> and others)
cardmgr[2245]: module /lib/modules/2.4.20-4GB//pcmcia/orinoco_cs.o not available
cardmgr[2245]: executing: 'modprobe -v orinoco_cs'
cardmgr[2245]: + /sbin/insmod /lib/modules/2.4.20-4GB/kernel/drivers/net/wireless/orinoco_cs.o
cardmgr[2245]: + Using /lib/modules/2.4.20-4GB/kernel/drivers/net/wireless/orinoco_cs.o
cardmgr[2245]: + Symbol version prefix ''
kernel: orinoco_cs.c 0.13b (David Gibson <hermes@gibson.dropbear.id.au> and others)
kernel: hermes @ IO 0x280: Timeout waiting for card to reset (reg=0x0000)!
kernel: eth0: failed to initialize firmware (err = -110)
kernel: orinoco_cs: register_netdev() failed
kernel: orinoco_lock() called with hw_unavailable (dev=c22a6000)
cardmgr[2245]: get dev info on socket 1 failed: Resource temporarily unavailable
Does this give you any insight?
For what it's worth, in the first case (external drivers), the internal PCMCIA ethernet is already attached to eth0 and it's trying to attach the DLink to eth1. In the second case (kernel drivers), only the external PCMCIA bridge driver is loaded (yenta_socket doesn't support the internal PCMCIA bridge), so it's trying to attach to eth0.
Last edited by Dark Helmet; 11-27-2003 at 10:04 PM.
Yep, it did what I wanted... at least for testing purposes. It got the right manfid, cardmgr saw the card as we wanted it to, and then it barfed on trying to initialize the firmware as there just isn't an Intersil card there. This is something else. Its a 16-bit pcmcia chipset, and its not Intersil Prism, or at least not a version of the firmware that the driver can talk to... which is weird. Really Weird. .13b of Orinoco is pretty damn recent too...
I can't find anything on a Rev P of this card. How new is this thing?
finegan: Yep, it did what I wanted... at least for testing purposes. It got the right manfid, cardmgr saw the card as we wanted it to, and then it barfed on trying to initialize the firmware as there just isn't an Intersil card there. This is something else. Its a 16-bit pcmcia chipset, and its not Intersil Prism, or at least not a version of the firmware that the driver can talk to...
Did you see kingkevbo's reply in the associated thread (http://www.linuxquestions.org/questi...hreadid=119550) where he'd called DLink and they say it's got a Prism3? The ISL number in the ident also matches what's listed as a Prism3 on some of the Intersil web docs.
Quote:
I can't find anything on a Rev P of this card. How new is this thing?
Just purchased mine at Fry's earlier this week. I posted links to the DLink pages on the Rev P on that other thread. And let me know if there are any tools you'd like me to run that'll help identify this card better.
For what it's worth, I borrowed a Lucent Orinoco Gold card from a friend (which I unfortunately cannot keep ) and it double-beeps and configs up just fine with either the external or kernel PCMCIA drivers, so seems our issue is likely card-related and not due to some odd distro PCMCIA quirk.
Last edited by Dark Helmet; 11-28-2003 at 10:12 AM.
That's good, I was pretty certain that pcmcia was just dandy... since cardmgr did actually try to initiate the firmware. I was looking at the other thread too, and you pretty much proved it with the linux-wlan-ng drivers also, I'm willing to bet this is not a Prism card at all.
D-Link commonly has their heads up their asses, every tier 1 tech support will... or might not have even been notified if the company switched chipsets. This happened a lot when the rtl8180 hit the market. People kept calling: Dlink, Linksys, etc... and were told it was prism2/2.5/3 (there's really no important difference in the prisms from our standpoint).
Alright, I've got to admit, I'm spooked. "cardctl ident" is the only way I know to pull info off of the card. Maybe the FCC ID on the back of the card may help... that's a very very old trick. Using the Ident info, I just keep googling straight to the other LQ thread.
Which reminds me, if this turns into another gigantic WPC11 v4-esque thread, its time to consolidate, we'll pick it up over on the other one:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.