Wireless card no longer works in 2.0
Forum: Networking
Topic: Wireless card no longer works in 2.0
started by: dtf
Posted by dtf on Dec. 20 2005,20:59
Network Card: D-Link DSL-650 IEEE 802.11bI can not configure my network card (above) in DSL 2.0 that previously was working in DSL 1.5.
When I go to DSL 2.0 I lose my wireless capability. I notice that during the boot sequence the D-LINK wireless card is no longer assigned to port eth0 but is now assigned wlan0. That seems reasonable and I can even see that the card and model are recognized. However, I am not able to configure to the card. With DSL 1.5 I used Wlanconfig to configure the card to eth0 but that does not work for DSL 2.0. I was making some progress with using Prism2. In fact, ifconfig shows me the wlan0 interface with what I am assuming is a valid MAC but my attempts to get network connections fail. I have tried both DHCP and assigning a static IP. This is all done using the DSLpanel tool.
Any thoughts? Thanks.
Posted by roberts on Dec. 20 2005,21:21
Looks like it is a discontinued product. Maybe that is why it is not in the latest kernel.See:
< http://support.dlink.com/products/view.asp?productid=DWL-650 >
However: It does appear to be one that can be used with ndiswrapper.
# Card: D-Link Air DWL-650
* Chipset: Realtek 8180
* pciid: 10ec:8180 (rev 20)
* Driver: XP Drivers from < http://www.dlink.com >
* Other: Tested on debian unstable with Ndiswrapper 0.8, kernel 2.6.5 custom on July 6th Works perfectly even under high transfer rates. Will come out of suspend properly. Ejecting card does NOT hang system. Issue: iwconfig reports 100% link quality all the time, even at high distances from access point ??
I would certainly try this approch.
1. download the driver for WinXP from < http://www.dlink.com >
2. unpack just the driver stuff into your home dir.
Then as user root
3. ndiswrapper -i xxxxxx.inf
Where xxxxxx is the name of the driver once unpacked.
4. modprobe ndiswrapper
5. iwconfig
This will show unconfiguered device name e.g., wlan0
6. iwconfig wlan0 essid your_sid_here
7. other iwconfig command as maybe necessary for encryption
8. pump -i wlan0
Step 6-8 could possibly be replaced with wlanconfig using the device name as shown from step 5
HTH
Posted by doobit on Dec. 20 2005,21:44
Remember, once you get it working to put myiwconfig.sh as a line in bootlocal.sh to make it permanent.
Posted by dtf on Dec. 22 2005,14:14
I appreciate the detail explanation. Thanks.I followed the instruction and downloaded the XP driver from the URL you gave me and unpacked it. There are 8 files, 3 having to do with the setup but of the other 5 I am not sure which file I should run ndiswrapper on.
data 1 --> cabinet file
data 2 --> cabinet file
layout --> bin (binary)
data1.hdr
ikernel.ex_
If I had to guess I would pick the last one or maybe I am missing a step but I do no see a file with the extension .inf.
Sorry for being so slow here but I hate working in windows other than running applications not available in Linux.
Posted by roberts on Dec. 22 2005,14:52
Sorry to head that Dlink is so windows. I think I would be at a loss too. I would have thought it would be a zip file with a xxx.inf and xxx.sys, as those are the usual suspects.I am curious about someting, you said you have a wlan0.
What is the output of the command
iwconfig
If iwconfig show a witeless device, maybe we can step you through the various iwconfig commands to properly configure it. If no device is shown then must keep digging in the windows stuff.
Posted by dtf on Dec. 22 2005,16:03
Thanks for the offer. I would really like to pursue this in the interest of helping resolve issues and increasing my understanding but I am giving this ebay special laptop as a gift to my son so I going to put this on the back burner for awhile. I really like what DSL can do on older platforms with little memory. Also I think this is a great introduction to LINUX and not as complicated as larger distributions. Anyway enjoy your holiday and keep up the good work. Guess I change the topic again 
.
Posted by msuho on Dec. 23 2005,16:05
Exactly one year ago today I posted this on the working wireless thread:| Quote |
| LInksys WUSB11 Ver 2.5 Works Prism2 Chipset edit /etc/modutils/linux-wlan-ng - change "prism2_pci" to "prism2_usb" in alias modprobe prism2_usb wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable wlanctl-ng wlan0 lnxreq_autojoin ssid=<your APs SSID> authtype=opensystem ifconfig wlan0 <yourIP> netmask <yourNetmask> broadcast <yourBroadcast> route add default gw <yourGateway> |
Well, I upgraded to 2.0, and this network card no longer works. I gather from the prceding discussion that perhaps my card's support has been deprecated. I guess I can try the ndiswrapper route.
Mark
Posted by roberts on Dec. 23 2005,18:23
Stating that something works 1.5 and not 2.0 is really helpful.The prism2 modules are in included with 2.0 and work fine with my prism2 netgear device.
/lib/modules/2.4.31/linux-wlan-ng/prism2_cs.o
/lib/modules/2.4.31/linux-wlan-ng/prism2_pci.o
/lib/modules/2.4.31/linux-wlan-ng/prism2_plx.o
/lib/modules/2.4.31/linux-wlan-ng/prism2_usb.o
If you are getting an error and even the output from running the following might be helpful...
# sh -x /usr/local/bin/prism2.sh wlan0 your_channel_nbr your_ssid
Posted by msuho on Dec. 24 2005,15:46
OK, pilot error on my part-I messed around with the prism2.sh script, and lo, I was using the wrong ssid
(I recently chnaged my router config). I'm typing this on my DSL 2.0 box,
so I'm back in business.
Thanks,
Mark
Posted by roberts on Dec. 24 2005,20:43
Thanks for the update.
Posted by iainm2 on Jan. 05 2006,10:28
Not sure if this helps. I had the same problem when I moved from DSL 1.5 to DSL 2.0 using a Netgear MA401 wireless card on a Dell Latitude Cpt 233Mhz. The MA401 was not detected as a wifi device. I had given up on wireless on this PC as I was more than happy with DSL in all other respects. Anyway to cut a long story short the laptop died irrecoverably but I have aquired a Dell Latitude cpi 400Mhz laptop. I moved the hard drive over as I use a hard drive install of DSL, it booted straight into DSL and has detected the MA401 flawlessly since.Anyway just wanted to add my tuppence worth.
Thanks to all as in my opinion DSL on slow hardware is just the business.
Posted by cbagger01 on Jan. 05 2006,19:05
Hmm..Maybe the problem is with the PCMCIA control drivers and services and not with the Wireless card drivers.
Your newer Dell laptop might use a different ACPI system or PCMCIA controller that plays nice with DSL 2.0
Posted by Shawn on Jan. 17 2006,00:58
This may very well be my problem. I'm trying to breathe new life into an old IBM Thinkpad 365XD with DSL. I've also got a Netgear MA-401, which I understand is supposed to work "out of the box" (so to speak).Unfortunately, I do not have a good way of getting output from the laptop to my main machine (for posting here) without a network connection.
What should I be looking for in the way of troubleshooting any potential PCMCIA issues?
Posted by cbagger01 on Jan. 17 2006,04:19
Unfortunately, my troubleshooting experience with PCMCIA is very limited because I do not own a laptop.I would try to search google for your laptop model and "linux" or "linux pcmcia" and hope there is help.
Posted by dslracer on Jan. 25 2006,08:59
try release dsl 2.2 (rc1)with kernel 2.4.26 everything should work
good luck