| View previous topic :: View next topic |
| Author |
Message |
TheEternalVortex
Apprentice
Joined: 15 Oct 2002
Posts: 207
Location: San Jose, CA
|
 Posted: Mon Jun 30, 2003 2:28 am Post subject: D-Link DWL-G520 drivers? |
 |
|
I just got a spiffy 802.11g network set up and I have a DWL-G520 PCI card. I can't seem to figure out what driver I should use to get it to work. I'd really like to get back to using Gentoo as I'm forced to use Windows for my browsing  .
Thanks...
_________________
-- Andy |
|
| Back to top |
|
 |
tphamm
Tux's lil' helper
Joined: 01 Jun 2003
Posts: 112
Location: Saskatoon, SK, CA
|
| Posted: Mon Jun 30, 2003 2:57 am Post subject: |
|
|
Unfortunately, Linux support for any 802.11g network devices right now is virtually nil. You can check out the ar5k project here, as they are working on support for the DWL-G520. So far, it looks like all they can do is initialize the cards and blink the LEDs 
_________________
"This is a UNIX system! I know this!" -- little girl from dinasaur park |
|
| Back to top |
|
|
mattman
n00b
Joined: 29 Jan 2003
Posts: 22
Location: St. Louis, MO, USA
|
| Posted: Wed Jul 02, 2003 11:40 pm Post subject: Limited success |
|
|
Updated July 10, 2003
I've had limited success with the card under linux 2.4.21 using the ath_pci driver available from the MadWiFi project, http://sourceforge.net/projects/madwifi/
I downloaded the 20030702 release from the URL listed above and also applied the WEP patch, available at the same URL under "Patches."
Summary of installation:
| Code: | $ tar xzf madwifi-20030702.tar.gz
$ cd madwifi-20030702
$ patch -p1 < ../mad_wep_err.patch
$ make
# make install |
I'm now using the card under Linux and it appears to work, though not without a few problems. As far as I can tell, you must bring up the interface with ifconfig before giving any options. Once the card was configured with iwconfig, I could never get a DHCP response, so I had to set things up statically. That's an issue the author of the driver mentions in his documentation.
Summary of commands:
| Code: | # /sbin/modprobe ath_pci
# /sbin/ifconfig ath0 up
# /usr/sbin/iwconfig ath0 essid 'my-essid' enc on
# /usr/sbin/iwconfig ath0 key 'my key' restricted
# /sbin/ifconfig ath0 <ipaddr> netmask <mask> broadcast <bcastaddr>
# /sbin/route add default gw <gatewayaddr>
# vi /etc/resolv.conf |
_________________
Matt
warning: `main' is usually a function |
|
| Back to top |
|
|
latexer
Retired Dev
Joined: 05 Mar 2003
Posts: 239
Location: NYC
|
| Posted: Sat Jul 19, 2003 2:50 pm Post subject: |
|
|
I've added the madwifi drivers into portage as "madwifi-driver" It's still marked ~x86, but i'd love to get some testing. It doesn't have the WEP patch applied, but i'll hopefully have that added this weekend.
| Code: | | ACCEPT_KEYWORDS='~x86' emerge madwifi-driver |
_________________
overlays - Use at your own risk. File bug reports on this stuff and i'll kick you in the junk. Ask me before asking upstream if these fail. I mean it. No, really.
#gentoo-dotnet on freenode |
|
| Back to top |
|
|
dweigert
Guru
Joined: 04 Oct 2002
Posts: 369
Location: Somerset, NJ USA
|
| Posted: Wed Aug 06, 2003 6:20 pm Post subject: |
|
|
Arrrrgh.... Ok, I've beaten my head against this for quite a while. It worked fine before I turned WEP on and hid the essid. Now the iwconfig refuses to take the essid, and the encryption refused to move to restricted. Does anyone have any clues on this? I'm using the latest version of madwifi from portage, the August version.
I'm wondering if my fersions of the wlan stuff is out of date...
Dan
_________________
"Always remember to mount a scratch monkey..." |
|
| Back to top |
|
|
|
Networking & Security
