D-Link DWL-520+ cannot get it working in Redhat nor Mandrake

rEph · 01-03-2003, 11:28 PM

I'm a relative newbie to linux, while I've used it for several years as an enduser, really don't have much experience with the intracacies of administration. So you don't have to keep it too simple, but don't blow me away. That out of the way, my question.

I purchased a D-Link DWL-520+, it happened to be a good deal at best buy, so I grabbed the last two. Apparently it has an odd chipset, it runs 256 WEP, and supposedly at 22mbps, which my AP doesn't support so I really don't need so I can take it back, just would rather simply get it working. Searching around I found these drivers ( http://www.eusso.com/Model2/GL2422-A...22_utility.htm ) it says they only work in mandrake, since I had a near clean install of redhat 8.0 I decided to try and get that to work (preferably) but couldn't. so I go with mandrake 9, I followed the directions best I could, they're a bit loose and don't explain much in detail, I got an error message from mandrake which I shouldv'e copied, as it'd prolly help. But from what I gathered I am missing some files needed to make that work, I followed the directions exactly (see link for directions) so if you know of any way to get this card working in redhat 8.0 that'd be appreciated, if not I'm assuming I'm missing some dependencies for it to work in mandrake, when I get a chance I'll post the error message if this isn't enough information, thank you.

-robf

rsbecker007 · 01-05-2003, 03:45 PM

I also just bought 2 of these, along w/ a wap that supports the 256 WEP and 22M, will try w/ mandrake first and report back...

rsbecker007 · 01-06-2003, 06:28 AM

good news: I did a fresh install of Mandy 8.2, and was able to get the card to work. I'm trying w/ redhat 8.0 at the moment. I'm not going to be able to get it to work as is, when using rh8 and I try to insmod the driver, It gives an error about the module being compiled w/ gcc2 as opposed to gcc3. From the looks of the page, they didn't release the source, so I think the chances of getting it to work on redhat w/o their support would be impossible. I am going to try contacting them directly, we'll see how that goes. If you want, I can help you get it working w/ mandy though.

rEph · 01-06-2003, 11:33 AM

I traded my dlink for two wNICs with lucent chipsets that work fine, my AP isn't dlink, so not really needing the propriety included with it. Now I'm having trouble with port forwarding on my Netgear MR814 wirless AP/router.... I can hit port 22 (SSH) from behind my gateway (192.168.0.4:22) fine, but port forwarding is not functioning correctly..as noone from the outside that has tried can connect. I'll prolly start a new thread about this. but if anyone seeing this here knows anything about this router post here - ( http://www.linuxquestions.org/questi...threadid=40477 ). I reinstalled RH8 and am getting the lucent wnic's to work fine, but I decided to place that machine next to the router so an ethernet line will suffice for now, I've less trouble with ethernet than I do wireless in linux anyhow.

-robf

rsbecker007 · 01-08-2003, 10:53 AM

I know this is no longer relavent for the original poster, but I have the same problem, so I will post my info here for future questions.

I got in touch with the both dlink, the maker of the cards, and eusso, a (tiawanese?) company that had the drivers available. What I *did* get from eusso was three versions of the driver. The first version, which I have gotten to work with Mandy 8.2, a newer one (I don't know what's different about it), and one compiled with gcc3 that I had hoped would work with redhat (it still might if I can modify the redhat kernel to be as like to the mandy kernel.) Then, I got an email from eusso saying that the driver page had been pulled from the web because of limited OS alaivability (Mandy only), and the reason no one has the source or drivers is a NDA from TI... SO, I guess either TI has to be convinced to release (tech specs?) for their ACX-100 chipset, and/or an open source driver will have to be made. In any event, I *do* have the drivers that work with mandy if someone needs them for whatever...

Now on to pester TI...

rsbecker007 · 01-11-2003, 06:06 PM

well, haven't quite gotten an answer out of TI yet, but what I do have is now posted on http://www.lemnar.com/lq/acx-100/

kunalsen · 01-13-2003, 04:16 AM

I am totally new to Linux and tried to install DWL-520 on my Linux 8.2 system. Based on the instructions in this thread, I created the Network Script, "insmod" the driver, and checked the existance of the wlan0 using "route". What else do I have to do to make work? Any help will be greatly appreciated.

= Kunal

rsbecker007 · 01-13-2003, 06:44 AM

okay, if you haven't yet, make sure the driver (the .o file) is copied to /lib/modules/2.4.18*/kernel/drivers/net/
then, add the line "alias wlan0 acx100_pci" to /etc/modules
and, make sure that /etc/sysconfig/network-scripts/ifcfg-wlan0 has ONBOOT=yes

reboot, and check route for wlan0 and also run ifconfig to check for wlan0

That will take care of the first part of the instructions. The second part involves setting up the wireless device to communicate with the access point or whatever.

this assumes a floppy with the files is mounted at /mnt/floppy

Code:

cd /etc
mkdir wireless
cd wireless
mkdir acx100
cd acx100
cp /mnt/floppy/wlanconfig . 
cp /mnt/floppy/wlan.opts .
cp /mnt/floppy/wlanctl .
cp /mnt/floppy/help
chmod 700 *
ll

you should see wlanconfig, wlan.opts, wlanctl, and help

edit the wlan.opts file with your favorite editor vi, pico, emacs ...

check that the driver loaded correctly after the reboot with route and ifconfig, if so run

Code:

./wlanconfig wlan0

backup the ifup file

Code:

cd /sbin/ifup
cp ifup ifup.bak

edit ifup:

after you see:

Code:

elif [ "${GATEWAYDEV}" = "${DEVICE}" ]; then

ip route add default dev ${REALDEVICE}

fi

fi

fi

but before you see:

Code:

. /etc/sysconfig/network



# IPv6 initialisation?

if [ "${NETWORKING_IPV6}" = "yes" ]; then

/etc/sysconfig/network-scripts/ifup-ipv6 ${CONFIG}

fi

insert these lines:

Code:

if [ -x /usr/usr-script/wlanconfig ] ; then

exec /usr/usr-script/wlanconfig $DEVICE

fi

then save changes to ifup.

did it work? tell us how it went, if things are unclear etc., I mainly just copied the instructions verbatim.

garethevans123 · 01-13-2003, 11:51 AM

Hi, I'm using Mandrake 9.0. I have followed the instructions. I seem to have the following problem:

[root@localhost net]# chmod 700 acx100_pci.o
[root@localhost net]# insmod acx100_pci.o
acx100_pci.o: unresolved symbol netif_rx_R8fa84786
acx100_pci.o: unresolved symbol __kfree_skb_R2aa7f7c4
acx100_pci.o: unresolved symbol unregister_netdev_R6073b2e9
acx100_pci.o: unresolved symbol pci_free_consistent_Rd23139f1
acx100_pci.o: unresolved symbol alloc_skb_Re2a6b56f
acx100_pci.o: unresolved symbol register_netdev_Rbd99562f
acx100_pci.o: unresolved symbol pci_alloc_consistent_R1f6a8dc8
acx100_pci.o: unresolved symbol eth_type_trans_R9ccac474
acx100_pci.o: unresolved symbol pci_enable_device_R944b5e42
acx100_pci.o: unresolved symbol skb_over_panic_R8f8e21d2
acx100_pci.o: unresolved symbol softnet_data_R5a0882b5
acx100_pci.o: unresolved symbol do_BUG_R577f4bff
acx100_pci.o: unresolved symbol ether_setup_R2a548a49
acx100_pci.o: unresolved symbol pci_register_driver_R465aa46c
acx100_pci.o: unresolved symbol pci_unregister_driver_R26713b86
[root@localhost net]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
[root@localhost net]#

Here are my wlan.opts settings:

DEVICE=wlan0
ESSID=wesley
#CHANNEL=6
#MODE=1
MODE=2
RATE=6
KEY="14789632147896321478963214 [1]" ## 128 bit encrypt

And here are is my network-script

DEVICE=wlan0
BOOTPROTO=no
IPADDR=192.168.0.16 ## My manually set ip (Not using DHCP)
NETMASK=255.255.255.0
NETWORK=192.168.0.1 ## Broadband router
BROADCAST=192.168.98.255 ## Not sure about this?
ONBOOT=yes

Also, under mandrake hardware, the wireless PCI card was detected with Module: Unknown. Do i install a (generic) wireless device from the list of available hardware drivers available under Mandrake?

If anyone could help, I'd be really happy :-)

Thanks
Gareth

rsbecker007 · 01-14-2003, 08:56 AM

This is the root of the problem with TI. They don't release info, so all we have for now is precompile binaries with limited OS applicability. You might be able to switch to the Mandy 8.2 kernel, but, your problem lies in the new madrake is not the same as the old one, thus problems ensue when inserting an older module, I don't think I have any good answers for you, other than for now run Mandy 8.2...

garethevans123 · 01-14-2003, 09:07 AM

Thanks for your reply. I will probably wait until DLink release their drivers. They said they should be out in the first quarter.

rsbecker007 · 01-14-2003, 10:43 AM

well, that's news to me, but good. I hope it would be open source, but from what I've found out about TI, I would be surprised if it was.

garethevans123 · 01-14-2003, 11:41 AM

These FAQs where on DLink website:

Q. Where can I find Linux drivers for my D-Link DWL-520+ and DWL-650+ Airplus adapters?

A. Currently, we do not have Linux drivers for these adapters. D-Link is working on drivers. Proper functioning source code or modules will be posted at support.dlink.com/products as soon as they are available.

Q. Why is it taking so long for Linux drivers to be released for the DWL-520+ and DWL-650+?

A. The DWL-520+ and DWL-650+ adapters use the Texas Instruments ACX-100 chipset. As soon as the source code is released, instructions and modules will be created and posted.

aaz · 01-30-2003, 04:58 PM

Dear Sir, it receives a warm greeting beforehand, wishing him the best thing.

I go to you to do a requirement to him about driver acx100_pci.o, which made me arrive very formally in last days. I have the following problem and to know to me that solution can exist for. I have installed the Mandrake 9.0, i follow the passages for the adjustment of the surroundings of work of driver in question and its configuration, but when executing the command "insmod acx100_pci-2.4.19.o" leaves the following list to me errors:
> acx100_pci-2.4.19.o: unresolved symbol netif_rx_R8fa84786
> acx100_pci-2.4.19.o: unresolved symbol __ kfree_skb_Ràa7f7c4
> acx100_pci-2.4.19.o: unresolved symbol unregister_netdev_R6073bè9
> acx100_pci-2.4.19.o: unresolved symbol pci_free_consistent_Rd23139f1
> acx100_pci-2.4.19.o: unresolved symbol alloc_skb_Reà6b56f
> acx100_pci-2.4.19.o: unresolved symbol register_netdev_Rbd99562f
> acx100_pci-2.4.19.o: unresolved symbol pci_alloc_consistent_R1fã8dc8
> acx100_pci-2.4.19.o: unresolved symbol eth_type_trans_R9ccac474
> acx100_pci-2.4.19.o: unresolved symbol zone_table
> acx100_pci-2.4.19.o: unresolved symbol pci_enable_device_R944bë42
> acx100_pci-2.4.19.o: unresolved symbol skb_over_panic_R8f8e21d2
> acx100_pci-2.4.19.o: unresolved symbol softnet_data_Rä0882b5
> acx100_pci-2.4.19.o: unresolved symbol ether_setup_Rà54å49
> acx100_pci-2.4.19.o: unresolved symbol pci_register_driver_R46äa46c
> acx100_pci-2.4.19.o: unresolved symbol pci_unregister_driver_R26713b86

In truth not like correcting this part, excuses the caused annoyance, but him infinitely thanks any recommendation on the matter.

Thank you very much by the lent attention.

Thousands of succesful for you!

rsbecker007 · 01-31-2003, 06:28 AM

Well, sorry to say that, for now, No OS other than widows or Mandrake 8.2 has been comfirmed to work with the acx-100 chipset. Work is underway however...