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.
The infamous acx100-based wireless 802.11b network cards. This is D-Link's PCI-based card (the PCI version of the PCMCIA-based DWL-650 ). These are 22Mbps-44Mbps 256-bit encryption cards. Note that this is the ' ' card. The DWL-520 (without the ' ' is a completely different chipset - in most cases - the company has bad naming conventions).
Description from website: "The D-Link AirPlus DWL-520 PCI Adapter is an enhanced 802.11b adapter featuring advanced silicon chip technology from Texas Instruments. The DWL-520 is fully compatible with the IEEE 802.11b standard making it interoperable with all existing 802.11b compliant devices. Now you can transfer files or communicate up to 20% faster than previous 802.11b solutions, even when connected to a standard 802.11b network. When you?re connected to other D-Link AirPlus products, the performance is even greater ? up to 22Mbps!"
Would you recommend the product? yes | Price you paid? (in USD): $49.95 | Rating: 9
Kernel (uname -r):
2.4.22
Distribution:
Debian Sarge
D-Link has refused to release drivers and Texas Instruments (the makers of the ACX100 chipset it uses) has refused to release specifications for developers, despite continual pleas. There were, originally, some binary drivers that were leaked out - if you happen to have those distributions, other reviews have said that they're fine. However, the better solution is the open-source, reverse-engineered driver at http://acx100.sourceforge.net/. This driver is quite reliable at this point (I'm using version 0.2.0pre5), even though it is technically still an alpha release.
UPDATE (9/Feb/2004): I'm now using kernel 2.6.0. Trying to follow the readme to install in 2.6 can be a pain. But a simpler solution is that there are frequently-updated 2.6 kernel patches available here: http://luca.pca.it/projects/acx100/. Anyway, driver works perfectly - I have no problems at all with it. I've upgraded my compatibility rating from an 8 to a 9 now (not 10 because the driver's still not included as part of the kernel.org kernel).
Would you recommend the product? yes | Price you paid? (in USD): None indicated | Rating: 7
Kernel (uname -r):
2.6.2
Distribution:
Slackware 9.1
I give it a 7. The acx100-pre2 drivers worked well for me in 2.4.22 kernel but no higher level driver worked reliably.
I couldn't get it working in 2.6.0.
Sometimes the driver would flake out and the card would lose its connection to the AP, and I have to start over by re-insmod'ing the module.
If you want wireless linux save yourself a headache and get an orinoco based card. Skip D-link wireless products (both the 520+ and the 650+ PCMCIA wireless).
Would you recommend the product? yes | Price you paid? (in USD): None indicated | Rating: 8
Kernel (uname -r):
2.6.3
Distribution:
Slackware 9.1
Well I got it working with 2.4.22 which comes with Slack 9.1, but when I compiled it into the kernel of 2.6.3 and reboot, it tells me to specify the firmware_dir and that it can't load it because it doens't know where the firmware is. In the /etc/modules.conf file I have it in there from the 2.4.22 kernel and it still won't find it. So I'm not sure if it needs to be somewhere else or what.
Would you recommend the product? | Price you paid? (in USD): None indicated | Rating: 0
Kernel (uname -r):
2.6.0
Distribution:
Debian Sarge (Testing)
mindfrost82,
Try just using the start_net script from the acx100.sf.net set of stuff. I don't know how you did what you did in your modules.conf, but the script is probably the easier route. It works for me (I just put the script in /etc/init.d) on kernel 2.6.0. The firmare_dir=whatever argument is needed in the insmod command for the acx100 module. Anyway, just try the script instead of modules.conf
Would you recommend the product? yes | Price you paid? (in USD): $40.00 | Rating: 0
Kernel (uname -r):
N/A
Distribution:
Slackware 9.1
I'm attually installing a new version of Slackware, clean install, I'm upgrading my Redhat as I don't really like it. But anyway, I was wondering if anyone could give me a link for the 520+ drivers for Linux, I'm not quite sure the default Kernal I believe it's 2.4. If anyone could help me, I would very much apreachate it. I am currently on windows as the only way I can connect to the internet is through wireless.
Would you recommend the product? no | Price you paid? (in USD): None indicated | Rating: 0
Kernel (uname -r):
2.6.3
Distribution:
Mandrake 10.0
I have the same problem. Does the 'pre8' version of the driver work for 2.6.0?
Personally I would have used an Orinoco card, but the guy selling them only had one left. My sister took that one because her PC had been playing up and we decided to use the card that had the least visible problems with her PC. The only thing is, she doesn't use Linux at all.
Would you recommend the product? no | Price you paid? (in USD): $50.00 | Rating: 1
Kernel (uname -r):
Distribution:
Fedora Core 2
I used link-wlan for a driver and when installed the d-link never was recognized and after reinstalling fedora the driver will not install and although I have no idea why I don't know why D-Link doesn't just release a binary to make our lives easier.
Would you recommend the product? yes | Price you paid? (in USD): None indicated | Rating: 0
Kernel (uname -r):
2.4.26
Distribution:
Slackware 10
I copied the firmware files to a directory on my path (/usr/lib/dwl_firmware), add the line "options" to /etc/modprobe.conf, compiled the driver, and installed the module. Then, i'm restarted my network and worked fine.
But when I reboot my machine, the system can't load the module, and can't start the network.
Would you recommend the product? yes | Price you paid? (in USD): $22.00 | Rating: 9
Kernel (uname -r):
2.6.9 i686 GNU/Linux
Distribution:
Debian
With the acx100.sourceforge.net (acx100-0.2.0pre8_plus_fixes_39) drivers, works fairly well on my 2.6.9 kernel.
The only Issue that i have seen is receiving an occasional deauthen packet after a few minutes of inactivity and having the connection "freeze" for 5 or so seconds while it re-authenicates....
It doesn't drop the connection, and it's only a slight annoyance when ssh'd into the system.
Would you recommend the product? yes | Price you paid? (in USD): $60.00 | Rating: 9
Kernel (uname -r):
2.6.8-2-386
Distribution:
Debian Sarge
If you try to use the acx100 drivers i had alot of problems, with it detecting the card, but not detecting the wlan0. After investigating i decided to use the ndiswrapper, on the first try i got it. Just download the source .deb from their site using apt-get, then cd to /usr/src, extract it all, go in to drivers and do a ./configre, make, make install, then do the same in utils. Extract the 3 files in windows xp drivers from the cd (.bin, .inf and .sys) and do ndiswrapper -i GPLUS.inf. Afterwards do ndiswrapper -m and modprobe ndiswrapper, it should work. Get the wireless-tools package from the same site and do iwconfig, if it detects your card you're all set. Took me a while though to figure this out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.