Ubuntu
gnome-nettool package

Getting DWA-140 to work in 10.10

Asked by Carl

I got the desktop CD to install Ubuntu x64 on a computer which I've done a few times before. But this machine is using a D-Link DWA-140 to connect to a D-Link DIR-635(with hidden SSID and WPA). I can dual boot to Windows 7 which have no problem to give me a connection to the Internet. But with Ubuntu there seems to be some issue as it constantly loops back and ask me for the network key.
The card seems supported out of the box according to:
https://help.ubuntu.com/community/HardwareSupportComponentsWirelessNetworkCardsDlink#USB
And I've tried to set the network key to a simple, all ASCII word. But still no luck. So what am I missing?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
Carl
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

What windows does is of no value to us, its a different OS with different support.

Can you give the output of:

sudo lshw -C network; sudo iwlist scan | head -n 25

Thanks

Revision history for this message
Carl (bluelight1991) said : 		#2

True, Windows is different. I was merely thinking that the card seems to work and be able to connect to the AP, just not in Ubuntu.

  *-network
       description: Ethernet interface
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: eth0
       version: 03
       serial: e0:cb:4e:da:79:f0
       size: 10MB/s
       capacity: 1GB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=no multicast=yes port=MII speed=10MB/s
       resources: irq:47 ioport:c800(size=256) memory:dffff000-dfffffff memory:dfff8000-dfffbfff memory:fbcf0000-fbcfffff
  *-network
       description: Wireless interface
       physical id: 1
       logical name: wlan0
       serial: 1c:af:f7:6a:eb:ff
       capabilities: ethernet physical wireless
       configuration: broadcast=yes multicast=yes wireless=Ralink STA

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
          Cell 01 - Address: 00:1C:F0:5D:11:61
                    Protocol:802.11g/n
                    ESSID:""
                    Mode:Managed
                    Channel:1
                    Quality:78/100 Signal level:-59 dBm Noise level:-91 dBm
                    Encryption key:on
                    Bit Rates:11 Mb/s
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
          Cell 02 - Address: 00:26:5A:24:C1:F4
                    Protocol:802.11b/g/n
                    ESSID:"Fjant"
                    Mode:Managed
                    Channel:6
                    Quality:2/100 Signal level:-89 dBm Noise level:-91 dBm
                    Encryption key:on
                    Bit Rates:300 Mb/s

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

Ok you are finding SSIDs which is fine. The device is working. Have you tried installing wicd?

Revision history for this message
Carl (bluelight1991) said : 		#4

No, I had not tried wicd as I assumed it should work "out of the box". But I did try to install it and it was kind enough to give me an error message about my password which was odd. So I did a Google search for it and it seems some linux drivers have an issue if the AP is set to use both WPA and WPA2. Changing the DIR-635 to use only WPA2 solved my problem and I'm now able to connect with the standard install.