D-Link DWL-G520 Wireless - Not Working

Daemonized · December 7, 2008, 8:09pm

I’ve been trying to set up openSUSE 11 on my PC yesterday, which I installed via LiveCD, but I can’t get my wireless card to connect to the internet via my router. I’ve got no way of connecting to my router with a wired connection from here, so in SUSE I’m stuck without internet. I’ve tried various configurations in yast, but no luck. Any suggestions?

Here are the results from the steps listed in the stickied thread:

Step 2:
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
03:00.0 VGA compatible controller: nVidia Corporation Geforce 9600 GT 512mb (rev a1)
04:09.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)

Step 2 with -n:
00:00.0 0500: 10de:02f0 (rev a2)
00:00.1 0500: 10de:02fa (rev a2)
00:00.2 0500: 10de:02fe (rev a2)
00:00.3 0500: 10de:02f8 (rev a2)
00:00.4 0500: 10de:02f9 (rev a2)
00:00.5 0500: 10de:02ff (rev a2)
00:00.6 0500: 10de:027f (rev a2)
00:00.7 0500: 10de:027e (rev a2)
00:02.0 0604: 10de:02fc (rev a1)
00:03.0 0604: 10de:02fd (rev a1)
00:04.0 0604: 10de:02fb (rev a1)
00:09.0 0500: 10de:0270 (rev a2)
00:0a.0 0601: 10de:0260 (rev a3)
00:0a.1 0c05: 10de:0264 (rev a3)
00:0a.2 0500: 10de:0272 (rev a3)
00:0b.0 0c03: 10de:026d (rev a3)
00:0b.1 0c03: 10de:026e (rev a3)
00:0d.0 0101: 10de:0265 (rev a1)
00:0e.0 0101: 10de:0266 (rev a1)
00:0f.0 0101: 10de:0267 (rev a1)
00:10.0 0604: 10de:026f (rev a2)
00:10.1 0403: 10de:026c (rev a2)
00:14.0 0680: 10de:0269 (rev a3)
00:18.0 0600: 1022:1100
00:18.1 0600: 1022:1101
00:18.2 0600: 1022:1102
00:18.3 0600: 1022:1103
03:00.0 0300: 10de:0622 (rev a1)
04:09.0 0200: 168c:0013 (rev 01)

Step 3 (relevant part):
ACPI: PCI Interrupt 0000:04:09.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
ath5k_pci 0000:04:09.0: registered as ‘phy0’
phy0: Selected rate control algorithm ‘pid’
ath5k phy0: Atheros AR5213A chip found (MAC: 0x79, PHY: 0x45)
ath5k phy0: RF2112A 2GHz radio found (0x56)

Step 4:
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Step 5:
wlan0 No scan results

deltaflyer44 · December 7, 2008, 8:17pm

Looks ok to me, just need to associate it with your router/modem,which can be done via right-clicking network manager - new connection. Keep clicking next & filling in relevant details,then save. then you can connect to it. Or you can set it up via YaST - network devices - network settings

Andy

Daemonized · December 7, 2008, 9:35pm

Thanks very much for the quick reply!

I’ve been playing around with various settings in KNetworkManager and yast, but no luck so far. Any advice for what I should try next?

Here are my network settings in yast:

Global Options

User Controlled with NetworkManager - Yes
Traditional Method with ifup - No
Enable IPv6 - Yes
Request Broadcast Response - No
DHCP Client Identifier - blank
Hostname to Send - AUTO
Change Default Route via DHCP - Yes

Hostname/DNS

Hostname - linux-iq7z
Domain Name - site
Change Hostname via DHCP - Yes
Write Hostname to /etc/hosts - Yes
Change /etc/resolv.conf manually - No, greyed out
Update DNS data via DHCP - Yes

Routing
(nothing checked or set)

Here are my network card settings:

General

Activate device - At Boot Time
Assign Interface to Firewall Zone - Automatically Assigned Zone
Enable Device Control for Non-root User Via KInternet - No
Set MTU - blank

Address

Dynamic Address - DHCP
everything else blank/greyed out

Hardware

Device Name - wlan0 also greyed out
Module Name - ath5k
Options - blank

I’ve left the Wireless Network Card Configuration blank, because I set up the network in KNetworkManager - is this fine?

Now, for my connection entry in KNetworkManager:

ESSID - homenet
Use Wireless Security - yes
Security - WEP
Type - WEP 40/128-bit ASCII this is the same setting as on my router
Key1 - (I’ve ensure that this is correct)
Use manual IP configuration - No
Connection Name - homenet
Autoconnect - Yes

deltaflyer44 · December 8, 2008, 8:51am

1 ) Turn off ipv6
2 ) set the device to external in the firewall
3 ) try changing ath5k to ath_pci in the hardware settings

Andy

Daemonized · December 9, 2008, 2:50am

I tried 1) and 2), but no luck. When I tried 3), “iwconfig” didn’t show wlan0 any more, so I switched that option back. ath5k seems to be the correct driver, but “iwlist scan” still says “No scan results”.

What else can I do to further diagnose this problem?

mattm3a · December 12, 2008, 5:37pm

See my note here:
Another Atheros not working - openSUSE Forums

Daemonized · December 16, 2008, 2:01am

I tried out some other distros just to see if those supported wireless out of the box. That experiment is done, and I’m now going back to openSUSE. This time, I decided to install openSUSE from the full install DVD so that I could get MadWiFi off the DVD repo like I did for Debian. However, I can’t find the MadWiFi package on the openSUSE DVD.

Is MadWiFi actually on the install DVD in a place that I haven’t checked yet?
If it isn’t, what is the most painless way to obtain and install MadWiFi, keeping in mind that I do not have any internet access from my openSUSE system yet? I can transfer files from a flash drive or CD, but that’s it.

lwfinger · December 16, 2008, 2:29am

Daemonized wrote:
> 1. Is MadWiFi actually on the install DVD in a place that I haven’t
> checked yet?

No - madwifi contains a binary blob that is not available under GPL, or any
other open-source license. As a result it violates the “open” part of openSUSE
and will never be part of an openSUSE distribution.

> 2. If it isn’t, what is the most painless way to obtain and install
> MadWiFi, keeping in mind that I do not have any internet access from my
> openSUSE system yet? I can transfer files from a flash drive or CD, but
> that’s it.

Download the “tar” file, which is like zip on steroids and put that file on your
favorite removable medium. Then go to or boot Linux, install the medium and
perform the untarring from that source according to the installation
instructions for that package. The process has the technical name of
“sneakernetting”.

Larry

mattm3a · December 16, 2008, 7:24am

Actually, the madwifi hardware abstraction layer (HAL) binary now has source available, I believe under the ISC license. Madwifi development, however, is basically stopped because there was a collective decision to discard it in favor of ath5k development. I don’t believe anyone has yet added the HAL source to replace the binary.

If you’re willing to wait a couple of days, you can try out suse 11.1 with the updated ath5k drivers. I suspect they should be working fine for regular station mode use.

If you do decide to compile madwifi from source, don’t forget to install gcc.

Daemonized · December 17, 2008, 1:42am

Installing MadWifi was a piece of cake after I installed the kernel headers and the C++ compiler from my DVD. It works flawlessly, and I’m posting this using openSUSE! Thanks very much for your help. This will do just fine until ath5k is working on openSUSE.