DWA-552 won't access internet

pseudonyma · #1 (**permalink**) 07-Sep-2009, 16:16

To Whom It May Concern:

I am trying to use a D-Link wireless PCI card (model: DWA-552) with SuSE 10.3; however, I cannot get the card to connect to the internet.

I tried using MadWiFi drivers first--installing them via YaST--but I couldn't get the card to work. I uninstalled MadWiFi using YaST.

Next I tried using ndiswrapper, following the instructions at
Ndiswrapper - openSUSE
After completing the instructions I started Firefox, but the browser could not connect. It appears as if I'm able to connect to the access point but not to the internet.

Details:

The card works under Windows XP (I dual boot.)

YaST=>Hardware=>Hardware Information=>Wireless LAN=>AR5416 802.11 a/b/g/n Wireless PCI Adapter (wlan0)=>Kernal Driver: ndiswrapper

"lspci -v" outputs
02:0a.0 Network Controller: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI Adapter (rev 01)
Subsystem: D-Link System Inc Unknown device 3a6d
Flags: bus master, fast Back2Back, 66MHz, medium devsel, latency 128, IRQ 22
Memory at feae0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] #80 [0000]

"lspci -n" lists "02:0a.0 Class 0280: 168c:0023 (rev 01)"

"dmesg | grep firmware" only outputs an error message about intel_rng (nothing about my wireless card)

"iwlist scan" outputs present wireless networks

I turned of encryption and turned on SSID broadcasting to make connecting easier.

"iwconfig" lists the ESSID and MAC address of my access point (plus other info.)

"ifconfig" lists my IP as 192.168.1.103, which makes sense

I pinged my access point with "ping -c 5 192.168.1.1". Pings were successful.

I pinged an external address using "ping -c 5 66.70.73.150". This fails with "connnect: Network is unreachable"

Does anyone have any ideas to get my card working?

Thanks in advance,
Caleb

Akoellh · #2 (**permalink**) 08-Sep-2009, 02:46

Remove that ndiswrapper **** and install recent madwifi from the "driver:wireless" repository.

Code:

/lib/modules/2.6.27.29-0.1-default/updates/ath/ath_pci.ko
alias:          pci:v0000168Cd00000023sv*sd*bc*sc*i*

lwfinger · #3 (**permalink**) 08-Sep-2009, 10:27

Akoellh wrote:
> Remove that ndiswrapper **** and install recent madwifi from the
> "driver:wireless" repository.

Removing ndiswrapper is always good advice. Remember that with it, you
are exposing the Linux kernel to an unconstrained Windows driver. All
the errors that cause Blue Screens of Death (BSOD) in Windows now can
cause kernel oopses. It is the quickest way to convert a system that
is stable into something that needs rebooting regularly, just the way
Windows does!

The rule is "Use ndiswrapper _ONLY_ when you must!".

pseudonyma · #4 (**permalink**) 08-Sep-2009, 21:57

Thanks for your suggestion. I uninstalled ndiswrapper and installed MadWiFi using YaST. I followed the instructions at
Atheros madwifi - openSUSE

Unfortunately, my card is still not working. Here is the result of some tests:

Checked YaST=>Hardware=>Hardware Information=>Wireless LAN=>AR5416 802.11 a/b/g/n Wireless PCI Adapter (wlan0):
no kernal driver listed

"lspci -v" outputs:
02:0a.0 Network controller: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI Adapter (rev 01)
Subsystem: D-Link System Inc Unknown device 3a6d
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 11
Memory at feae0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] #80 [0000]
Capabilities: [80] #00 [0000]

"lspci -n" outputs:
02:0a.0 Class 0280: 168c:0023 (rev 01)

"dmesg | grep firmware" only outputs an error message about intel_rng (nothing about my wireless card)

"iwlist scan" does not mention any wireless networks

"ifconfig" does not mention any wireless networks

Does anyone have anymore ideas? I'm not sure what to do next.

Thanks for your help,
Caleb

Akoellh · #5 (**permalink**) 08-Sep-2009, 22:27

Just do what I told you:

Quote:

Originally Posted by my self

Remove that ndiswrapper **** and install recent madwifi from the "driver:wireless" repository.

driver:wireless

pseudonyma · #6 (**permalink**) 09-Sep-2009, 22:13

I installed MadWiFi from
Index of /repositories/driver:/wireless/openSUSE_10.3_update

Things look better. Thanks for the clarification. Unfortunately I'm still not able to connect to the internet.

Details:

YaST>Hardware>Hardware Information>Wireless LAN>AR5416 802.11 a/b/g/n Wireless PCI Adapter (wlan0)>Kernel Driver: madwifi

"lspci -v" outputs

Code:

02:0a.0 Network controller: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI Adapter (rev 01)
        Subsystem: D-Link System Inc Unknown device 3a6d
        Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 22
        Memory at feae0000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [40] #80 [0000]

"lspci -n" outputs

Code:

02:0a.0 Class 0280: 168c:0023 (rev 01)

"dmesg | grep firmware" only outputs an error message about intel_rng (nothing about my wireless card)

"iwlist scan" outputs present wireless networks

"iwconfig" lists

Code:

lo        no wireless extensions.
eth0      no wireless extensions.
wifi0     no wireless extensions.
wlan0     IEEE 802.11g  ESSID:"omitted"  Nickname:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:1C:10:BF:05:B3   
          Bit Rate:6 Mb/s   Tx-Power:19 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=37/70  Signal level=-59 dBm  Noise level=-96 dBm
          Rx invalid nwid:35522  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

"ifconfig" outputs, in part

Code:

wifi0     Link encap:UNSPEC  HWaddr 00-22-B0-BC-83-0E-30-30-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:69728 errors:0 dropped:0 overruns:0 frame:7085
          TX packets:8671 errors:2484 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:280 
          RX bytes:8782664 (8.3 Mb)  TX bytes:585474 (571.7 Kb)
          Interrupt:22 
wlan0     Link encap:Ethernet  HWaddr 00:22:B0:BC:83:0E  
          inet addr:192.168.1.103  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::222:b0ff:febc:830e/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:74 errors:0 dropped:0 overruns:0 frame:0
          TX packets:75 errors:1 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:8480 (8.2 Kb)  TX bytes:13670 (13.3 Kb)

I pinged my access point with "ping -c 5 192.168.1.1". Pings were successful.

I pinged an external address using "ping -c 5 66.70.73.150". This fails with "connnect: Network is unreachable"

Where do I go from here?

Thanks again,
Caleb

pseudonyma · #7 (**permalink**) 14-Sep-2009, 09:57

To Whom It May Concern:

I still haven't been able to connect to the internet using my wireless card. Does it mean anything that with both ndiswrapper and MadWiFi I was able to ping the router but not able to ping an external IP address?

There are several threads that mention installing bleeding edge MadWiFi to get their networks to work. Might this work in my case? If I install a bleeding edge version of MadWiFi and it messes my computer up, is there a way to uninstall it?

I've been using GNU/Linux almost exclusively for the past several years, and I'd hate to have to go back to using MS Windows because of this networking issue.

If it makes a difference, I'm using a 32-bit version of OpenSuSE 10.3.

Thanks again to anyone who can help, and thanks to those who already have helped me out,
Caleb

Akoellh · #8 (**permalink**) 14-Sep-2009, 10:23

Quote:

Originally Posted by pseudonyma

I still haven't been able to connect to the internet using my wireless card. Does it mean anything that with both ndiswrapper and MadWiFi I was able to ping the router but not able to ping an external IP address?

Then your problem is _not_ the driver but the network setup.

Also remove ndiswrapper completely, this is a proven way to get in trouble with Atheros cards being actually supported by madwifi (the above outputs also indicate, that this is the case, wlan0 and wifi0 is NOT what should be seen on using _ONLY_ madwifi OR on using _ONLY_ ndiswrapper).

The outputs of your posting before confirm actually that the driver is working.

Quote:

Originally Posted by pseudonyma

There are several threads that mention installing bleeding edge MadWiFi to get their networks to work.

You already do use the "bleeding edge" madwifi drivers (believe me, I am the guy who built the madwifi packages you are using at the moment).

Quote:

Originally Posted by pseudonyma

I've been using GNU/Linux almost exclusively for the past several years,

Well, then setting up your network correctly shouldn't be a problem (I guess your routing is hosed).

Quote:

Originally Posted by pseudonyma

If it makes a difference, I'm using a 32-bit version of OpenSuSE 10.3.

It does not make a difference for madwifi, but for your future planning maybe.

SUSE Linux Lifetime - openSUSE

pseudonyma · #9 (**permalink**) 14-Sep-2009, 21:32

Thanks for your response. It's good news that the driver is working; that narrows down what could be wrong.

I thought it was odd that wifi0 and wlan0 were both showing up. YaST shows ndiswrapper and ndiswrapper-kmp-default as being uninstalled. How do I make sure ndiswrapper is completely uninstalled?

Sorry if this is a silly question, but what kind of things should I check with my network setup?

I apologize if I'm being dense, and I appreciate you help!

Akoellh · #10 (**permalink**) 15-Sep-2009, 03:54

Quote:

Originally Posted by pseudonyma

How do I make sure ndiswrapper is completely uninstalled?

Find and grep are your friends (and /etc is the place to search).

Quote:

Originally Posted by pseudonyma

I thought it was odd that wifi0 and wlan0 were both showing up.

No, the odd thing is, that there is not "ath0" and "wifi0" with madwifi, "wlan0" was set by ndiswrapper, again find and grep are your friends (and /etc/udev/ the place to search).

But if your network setup is still incorrect, even that won't help, so correct your setup also, it must be faulty.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode