|
|
|
|
|
Reviews
|
Views
|
Date of last review
|
|
11
|
18533
|
03-25-2008
|
|
 |
|
Recommended By
|
Average Price
|
Average Rating
|
|
91% of reviewers
|
$42.00
|
7.6
|
|
|
|
|
|
|
|
Description:
|
a wireless pci network card that requires some configuration. NOT a plug 'n play device, madwifi drivers required, (and those are in alpha-beta stage, but work well) but people who are new to the linux wireless networking scene or to this card can follow this excellent howto thats at this address:
http://www.linuxquestions.org/questi...hreadid=163192
good luck, it can be a hassle sometimes.
|
|
Keywords:
|
dwl dlink g520 wireless
|
|
/sbin/lspci output:
|
00:0c.0 Ethernet controller: Unknown device 168c:0013 (rev 01)
|
|
Chipset:
|
DLink DWL 520 (not really sure)
|
|
Connection Type:
|
PCI
|
|
|
|
09-15-2004, 11:25 AM
|
#1
|
Registered: Aug 2004
Posts: 7
|
Would you recommend the product? yes | Price you paid?: None indicated | Rating: 8
|
Kernel (uname -r):
|
2.6.3-7mdk
|
|
Distribution:
|
Mandrake 10
|
[ Log in to get rid of this advertisement]
Initially incompatiable, but used the madwifi drivers:
http://sourceforge.net/projects/madwifi
I followed the directions as given on the MadWifi Wiki:
http://madwifiwiki.thewebhost.de/wiki/Mandrake100AndDLinkDWLG520
I've only used it with dynamic IP from a DHCP without encryption.
|
|
|
|
09-17-2004, 03:13 PM
|
#2
|
Registered: Jun 2004
Distribution: MDK 9.2/10.0, VectorLinux 4.0
Posts: 50
|
Would you recommend the product? yes | Price you paid?: $50.00 | Rating: 9
|
Kernel (uname -r):
|
2.6.3-7mdk-smp
|
|
Distribution:
|
Mandrake 10.0
|
Installed as per instructions above - worked like a charm.
LQ comes through once again!
|
|
|
|
09-19-2004, 04:14 AM
|
#3
|
Registered: Nov 2003
Distribution: Slackware, Debian, Gentoo, openSuSE
Posts: 357
|
Would you recommend the product? yes | Price you paid?: $44.99 | Rating: 8
|
Kernel (uname -r):
|
2.4.26
|
|
Distribution:
|
Slackware 10
|
I've only used ndiswrapper (available at http://ndiswrapper.sourceforge.net) to get this card running, but because of the simplicity of the install, I would consider it compatible with Linux. If you are comfortable following directions (read the INSTALL file) and compiling from source (read the INSTALL file), this card should work without a hitch. A couple things to be aware of...
1) Have wireless-tools installed.
2) Use the XP driver (the *.inf file) on the CD supplied with the card--it works with whatever chipset you happen to get.
3) If you write a script to activate the card on boot, put a "sleep" command after the modprobe. For me, "sleep 6" was long enough. If you try to configure your iwconfig settings too quickly, they will not take.
I've had this running with ndiswrapper .10 on Slack 10, Mandrake 10, and Mandrake 9.*. If you use Mandrake 10, make sure to remove ndiswrapper .04 before you start--It comes pre-loaded with Mandrake 10.
Good luck and PM me if you have any questions.
-Kris
|
|
|
|
10-22-2004, 08:49 PM
|
#4
|
Registered: Oct 2004
Distribution: Debian (etch), MythDora
Posts: 19
|
Would you recommend the product? yes | Price you paid?: $44.00 | Rating: 7
|
Kernel (uname -r):
|
Linux 2.4.22-1.2174.nptl
|
|
Distribution:
|
Fedora Core release 1 (Yarrow)
|
I'm new to Linux...just a few weeks into it. The information and links provided in previous HCL reviews of this product were valuable in figuring out how to download and install drivers, kernel updates, and edit/create configuration files needed to get this card up and running.
I do not have a coherent, step-by-step procedure of what I did to get this card to work for me. Trial and error, patience, and tidbits of knowledge snatched from various forums was the key.
I have an Apple Airport Express as my access point. Bellsouth DSL service with an Alcatel Speed Touch Home (DSL modem).
|
|
|
|
03-14-2005, 02:46 PM
|
#5
|
Registered: Jan 2005
Distribution: Fedora Core 3, Mandrake 10.1
Posts: 16
|
Would you recommend the product? yes | Price you paid?: $45.00 | Rating: 8
|
Kernel (uname -r):
|
2.6x
|
|
Distribution:
|
Fedora Core 3
|
I got this working using the madwifi drivers. I'm a newbie, so it took some figuring out, but it was a good learning experience. Looking back, what I did seems simple: I got the cvs snapshot, unpacked it, and installed that. It worked like a charm afterwards (despite some weird network setup stuff that was FC's fault :)). The card I have, by the way, is Rev. B.
For total newbies (like I was), here's the step-by-step guide.
1) go here: http://madwifi.otaku42.de/ and download the file called madwifi-cvs-current.tar.gz. I have a multi-boot system, so I downloaded from windows XP and transferred it to Linux via a VFAT partition.
2) Login as root. Go to the directory where you put the file (it doesn't matter where. Your home directory will do) and type gunzip madwifi-cvs-current.tar.gz. This outputs a file called madwifi-cvs-current.tar.
3) in the same directory, type tar -xvf madwifi-cvs-current.tar. This extracts a file structure with a top-level folder called madwifi. You can now cd madwifi and type vi README if you want to look at setup nuts and bolts. Otherwise, continue...
4) In the ~/madwifi directory, # make
5) # make install
6) # modprobe ath_pci, #modprobe ath_hal. Read the documentation on modprobe commands and which file to put them in so they automatically load on startup.
You're done. Type lspci to see that the card has registered. Now type iwconfig and see if you see a device called ath0. If you do, that's your card. All you have to do now is set it up properly. Type man iwconfig if you want some directions on how to change settings.
that's how I did it. I hope this works for someone else.
|
|
|
|
04-24-2005, 02:30 PM
|
#6
|
Registered: Apr 2005
Posts: 0
|
Would you recommend the product? yes | Price you paid?: $40.00 | Rating: 8
|
Kernel (uname -r):
|
2.6.9
|
|
Distribution:
|
Fedora Core 2
|
The card I got is H/W Version B3, F/W Version 4.10. I got this card working OK with the madwifi drivers. It uses the Atheros AR5212 chipset. Mine is the "ExtremeG", 108 Mbps version, but I haven't gotten to try that speed, as my signal strength isn't good enough. However, it's been running at 36 Mbps consistently.
I used the config script at the address below. It's actually supposed to be for RH9, but it worked better for me than the setup instructions I found for FC2.
http://www.linuxtested.com/notes/CFG_NOTE_MADWIFI_RH9.html
One final note: I did have my machine completely hang (i.e. punch the Reset button!) a couple times when trying to bring the device up, but now that it is totally configured, that hasn't happened again.
|
|
|
|
12-11-2005, 05:07 PM
|
#7
|
Registered: Feb 2003
Distribution: Gentoo
Posts: 85
|
Would you recommend the product? yes | Price you paid?: None indicated | Rating: 0
|
Kernel (uname -r):
|
2.6.14-gentoo-r4
|
|
Distribution:
|
Gentoo
|
I have rev. B of the card, and it works great with the madwifi drivers.
|
|
|
|
04-16-2006, 04:14 AM
|
#8
|
Registered: Apr 2006
Posts: 0
|
Would you recommend the product? no | Price you paid?: None indicated | Rating: 1
|
Kernel (uname -r):
|
2.6.13-15-default
|
|
Distribution:
|
SuSE 10.0
|
What a circus! As always of course, I might be the main clown, so please let me know if you can think of anything I may have missed. The gory details:
The card is a D-Link DWL-G520. H/W Version B3. F/W Version 4.3
The card is recognised by the kernel at installation:
Ethernet controller: Atheros Communications, Inc AR5212 802.11abg NIC (rev 01)
Following OS installation, I can set the card up with YaST. All the time, the two LEDS blink alternately. Once YaST config is complete, restart the box, but no change; alternately blinking LEDS, no IP. Can ping the iface itself (10.0.0.119), but no other IPs on the LAN.
iwconfig shows ath0 with:
Bit Rate: 0 kb/s Tx-Power: 18dBm Sensitivity=0/3
Link Quality=0/94 Signal level=-95dBm Noise level=-95dBm
So, download madwifi's latest ng release. Compiled ok, except for warnings about ath_hal_[buildopts|version|attach|process_noisefloor] being undefined. This could well be fatal, but I could not find anything on Google about it, and compilation completed without error.
Installed the modules, modprobe ath-pci and... nothing! :-) The LEDs stopped blinking alternately, with only the power LED remaining constantly on, and the LAN LED remaining constantly off. Can still ping the local iface, but still no IP beyond that.
I have done lots of other fiddly little changes over the past 10 hours (yay for Easter long weekends :-) but I can't get it to work. I did get a D-Link DWL-G510 to work with the same kernel on another box a couple of months back, but no luck with the DWL520, at least for the H/W B3 and F/W 4.3 that I have.
Ah well, time for a beer.
CU,
Tim.
|
|
|
|
11-30-2006, 01:50 PM
|
#9
|
Registered: Aug 2003
Distribution: SuSE
Posts: 73
|
Would you recommend the product? yes | Price you paid?: $28.00 | Rating: 9
|
Kernel (uname -r):
|
2.6.13-15.12
|
|
Distribution:
|
SuSE-10.0
|
The card is a D-Link DWL G520, hardware is B3. Card was a used card, purchased on ebay.de. We had to send an email to the supplier to confirm in advance the hardware firware version # was B3.
After the card arrived we installed it in my wife's PC (a Sempron-2800 cpu, with 1GByte RAM). Booted SuSE-10.0 and I went directly to YaST > Network Devices > Network Card. The card was recognized by YaST, and in YaST I selected "edit" to configure the card. I've done this before with the wireless on our family laptop, so I know the correct YaST settings to use. I then rebooted the PC. The wireless was immediately working upon reboot. We had internet access and could access our local LAN. Connection was good. No unexpected disconnections after hours of operation.
The total configuration time from boot to re-boot was about 5-minutes.
In contrast it took my wife 2-driver downloads, and 3-driver installs (total time about 3-hours) to get it working exactly the way she wanted under WindowsXP. (She had dropouts under WinXP with the driver that came with the D-Link card - which was fixed with the other two drivers she downloaded). Reference the total time for WinXP install, I couldn't help her much in that, as I don't know the first thing about Windows. Perhaps someone famililar with WinXP could have done it quicker on WinXP.
We have a Speedport W700V router.
|
|
|
|
07-16-2007, 12:40 PM
|
#10
|
Registered: Jul 2004
Distribution: Debian sarge and LFS (Linux From Scratch)
Posts: 14
|
Would you recommend the product? yes | Price you paid?: None indicated | Rating: 10
|
Kernel (uname -r):
|
2.6.20-16-generic
|
|
Distribution:
|
Ubuntu 7.04 "The Feisty Fawn"
|
This card is absolutely marvelous !
I have the Revision B, which is supported by MadWifi, and Ubuntu has detected it ever since I got it. I tried it using ndiswrapper - it works. And I think ndiswrapper works with Revision A.
Some versions of Ubuntu ago, I had a strange little problem : every now and then, maybe once in two or three days, my card would disconnect. I just had to restart the networking on my box to get it work again : I made a cron job that did this every hour, just in case.
But now it doesn't do that anymore :)
|
|
|
|
03-25-2008, 03:33 AM
|
#11
|
Registered: Aug 2003
Distribution: SuSE
Posts: 73
|
Would you recommend the product? yes | Price you paid?: None indicated | Rating: 0
|
Kernel (uname -r):
|
Yes
|
|
Distribution:
|
openSUSE-10.3
|
Further to my previous post, this card also works on openSUSE-10.3, through use of the 3rd party packaged madwifi drivers. As noted above, the card we use is a D-Link DWL G520, hardware is B3.
Madwifi drivers (packaged as rpms) for openSUSE-10.3 for the card are here:
http://madwifi.org/suse/10.3
Guide for openSUSE users in using the card are here:
http://en.opensuse.org/Atheros_madwifi
Per that guide, for openSUSE and the madwifi driver, one needs to install both madwifi and madwifi-kmp-<your kernel flavor>.
|
|
|
|
All times are GMT -5. The time now is 02:25 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
LQ Podcast
LQ Radio
|
|