Announcement

**claydoh** · Aug 03, 2010, 05:30 PM

Re: Wireless Networking Trouble

first off, we need to determine the exact device id for your wireless card as even though the models may be the same, sometimes the manufacturers change the chipset. I cannot be sure but this may be a Ralink card, and that might have some Ubuntu-specific issues that we MAY be able to fix

so run this command with the card plugged in:

Code:

lspci

and copy the results here

**.46caliber** · Aug 03, 2010, 08:28 PM

Re: Wireless Networking Trouble

If I remember correctly the RALink chipsets were used in aftermarket cards. The internal Intel chipsets, I thought, used their own Intel chipsets.

Here are the results of the lspci command. I assuI assume the 02:02.0 line, second from last, is the one we are looking for?me the 02:02.0 line, second from last, is the one we are looking for?

00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
02:00.0 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus Controller (rev 01)
02:00.1 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus Controller (rev 01)
02:02.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (MOB) Ethernet Controller (rev 81)

**claydoh** · Aug 03, 2010, 09:04 PM

Re: Wireless Networking Trouble

Sorry somehow I was thinking too much about the non-Intel card.

My first suggestion is probably to try wicd., though I am rather surprised the gnome applet does not work.

Wicd uses its own system separate from network-manager and the kde/gnome front-ends

Also I am not 100% sure if your card needs firmware or not, or what type of encryption it supports info is both sparse and quite old

**.46caliber** · Aug 03, 2010, 09:23 PM

Re: Wireless Networking Trouble

Originally posted by claydoh

Sorry somehow I was thinking too much about the non-Intel card.

My first suggestion is probably to try wicd., though I am rather surprised the gnome applet does not work.

Wicd uses its own system separate from network-manager and the kde/gnome front-ends

Also I am not 100% sure if your card needs firmware or not, or what type of encryption it supports info is both sparse and quite old

Come to think of it, I don't think I tried the Intel wireless when I updated my router to WPA2. Maybe I should disable that and focus on the Belkin since it is newer and is compatible with WPA2.

I found a pretty handy chart with chipset and compatibility info: http://linux-wless.passys.nl/query_p...andname=Belkin

For my model, F5D8013 Ver. 3000, the spreadsheet provides the following info:

host I/F: cardbus
chipset: Ralink
driver: rt2860
works with linux - included in mainline kernel since 2.6.29

**GreyGeek** · Aug 03, 2010, 09:32 PM

Re: Wireless Networking Trouble

That chip is over 6 years old.
The driver for it is ipw2100, and it is in your system.

First you can try the hardware driver menu option.
Plug an ethernet cat 5 cable from the back of your wireless router to your eth0 socket on your PC.
Kgear --> System --> Hardware Drivers.
If your wireless chip show up you should click the "Activate" button.

IF that doesn't work then open a Konsole and issue:

sudo modprobe ipw2100

Then, check to see what name it is given:

sudo iwlist scanning

You should see something like this:

jerry@sonyvgnfw140e:~$ sudo iwlist scanning
[sudo] password for jerry:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1E:E5:57:7B:68
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-29 dBm
Encryption key

n
ESSID:"GreyGeek"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000000af5e3bb8b
Extra: Last beacon: 80ms ago
IE: Unknown: 0008477265794765656B
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: Unknown: 32040C121860
IE: Unknown: DD06001018020004
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 02:BA

4:43:0E:47
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-35 dBm
Encryption key

n
ESSID:"greygeek"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Ad-Hoc
Extra:tsf=0000000001bbc17f
Extra: Last beacon: 5760ms ago
IE: Unknown: 0008677265796765656B
IE: Unknown: 010482848B96
IE: Unknown: 030106
IE: Unknown: 06020200
IE: Unknown: 2A0100
IE: Unknown: 32088C129824B048606C
Cell 03 - Address: 34:EF:44:68:BF:79
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=24/70 Signal level=-86 dBm
Encryption key

n
ESSID:"WIN_335"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=00000092ce788181
Extra: Last beacon: 5950ms ago
IE: Unknown: 000757494E5F333335
IE: Unknown: 010882848B960C121824
IE: Unknown: 030101
IE: Unknown: 050400010000
IE: Unknown: 0706555320010B1B
IE: Unknown: 2A0100
IE: Unknown: 32043048606C

vboxnet0 Interface doesn't support scanning.

Let's say your wireless chip is shown as wlan0:

sudo iwconfig wlan0 essid "what ever your essid is"
sudo iwconfig wlan0 key s:yourstringkey
sudo dhclient wlan0

If that gets your wireless going then issue
sudo depmod -a
to make it permanent.

IF the above doesn't work use the cat5 ethernet cable and run Synaptic (if you haven't installed it run "sudo apt-get install synaptic"). Do a search for wicd and install every program with "wicd" in its name. Uninstall every program with "networkmanager" in its name except those which tell you that deleting it will also delete KDE destkop stuff.

Then run wicd and see if it sees your wireless.

**.46caliber** · Aug 04, 2010, 05:39 AM

Re: Wireless Networking Trouble

GreyGeek,

Thank you very much. I'll run through it tonight after work to see what I can accomplish.

**.46caliber** · Aug 04, 2010, 05:56 AM

Re: Wireless Networking Trouble

GreyGreek,

Should I kill Knetworkmanager to do this? There were no proprietary drivers listed when I followed your first set of steps, but KNetworkManager is seeing the right driver.

See screen shot.

[img width=400 height=300]http://lh4.ggpht.com/_BMEWpbuUXks/TFlVbp9QFII/AAAAAAAAAGY/qUypaMrLm4w/s640/snapshot1.png[/img]

**.46caliber** · Aug 04, 2010, 06:03 AM

Re: Wireless Networking Trouble

I ran the iwlist scanning, my network is cell 08, and here are the results:

g
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

irda0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:15:6D:55:10:17
ESSID:"Network1-T12W-24"
Protocol:IEEE 802.11b
Mode:Master
Frequency:2.417 GHz (Channel 2)
Encryption key

ff
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality:18 Signal level:0 Noise level:0
Extra: Last beacon: 3872ms ago
Cell 02 - Address: 00:24:B2:0D:03:8C
ESSID:"NETGEAR-24-G"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.412 GHz (Channel 1)
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:20 Signal level:0 Noise level:0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 124ms ago
Cell 03 - Address: 00:15:6D:54:F0:8B
ESSID:"Network1-TN12-24"
Protocol:IEEE 802.11b
Mode:Master
Frequency:2.457 GHz (Channel 10)
Encryption key

ff
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality:16 Signal level:0 Noise level:0
Extra: Last beacon: 144ms ago
Cell 04 - Address: 00:1C

F:C1:41

7
ESSID:"The Egans"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.437 GHz (Channel 6)
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:25 Signal level:0 Noise level:0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Extra: Last beacon: 11456ms ago
Cell 05 - Address: 00:15:6D:55:07

8
ESSID:"BuzzBroadband-SO37"
Protocol:IEEE 802.11b
Mode:Master
Frequency:2.442 GHz (Channel 7)
Encryption key

ff
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Quality:20 Signal level:0 Noise level:0
Extra: Last beacon: 5008ms ago
Cell 06 - Address: 00:1C:10:A1:C3:48
ESSID:"b00bs"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.437 GHz (Channel 6)
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:50 Signal level:0 Noise level:0
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 6740ms ago
Cell 07 - Address: 00:1F:C6:0E:B2:18
ESSID:"Wendy Net"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.462 GHz (Channel 11)
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:35 Signal level:0 Noise level:0
Extra: Last beacon: 2040ms ago
Cell 08 - Address: 00:1A:70:78

B:2F
ESSID:"Xander"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.462 GHz (Channel 11)
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:85 Signal level:0 Noise level:0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 2048ms ago
Cell 09 - Address: 00:14

1:C6:CB:65
ESSID:"MegaLAN"
Protocol:IEEE 802.11g
Mode:Master
Frequency:2.437 GHz (Channel 6)
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:18 Signal level:0 Noise level:0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 1876ms ago
Cell 10 - Address: 00:25:3C:7B:9E:91
ESSID:"1247WagonWheel-Wii"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.442 GHz (Channel 7)
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:23 Signal level:0 Noise level:0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 1432ms ago

**GreyGeek** · Aug 04, 2010, 01:01 PM

Re: Wireless Networking Trouble

Should I kill Knetworkmanager to do this? There were no proprietary drivers listed when I followed your first set of steps, but KNetworkManager is seeing the right driver.

KNetworkMangager is a "work in progress". It works OK for some but not for others. A couple releases ago, when KNM was even worse than it is now, when someone used Synaptic to replace KNM, Synaptic would install wicd and remove KNM automatically. Now, unfortunately, it does not.

It appears that in your case, from your graphic screen capture, that KNM does see your wireless chip:

Cell 08 - Address: 00:1A:70:78

B:2F
ESSID:"Xander"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.462 GHz (Channel 11)
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:85 Signal level:0 Noise level:0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 2048ms ago

and many other APs as well.

What you have to do now is right click on the KNM icon in the system tray and select "Manage Connections". A dialog will pop up. IF you have an ethernet cable connected to your wireless router it will show as connected (and running "ifconfig" in a Konsole will show eth0 with a valid IP address, and you should be able to browse the web). Also showing will be the access points that "iwlist" gave for your wireless access point. Underneath your access point listing will be two buttons, "Connect" and "Properties". Click on "Properties" to bring up its dialog. In its dialog is a text box for entering your WPA2 password. Enter it and click "OK" (or maybe "Apply", I don't remember which it is). IF I recall correctly, WPA2-Personal works be the other doesn't, unless they've fixed that bug.

After entering your wireless router password and closing the Properties dialog, click the "Connect" button on the "Manage Connections" dialog. After the slider bar bounces back and forth a while it should stop, and show your AP as being connected. A status line at the bottom of the dialog will show the name of your AP and the assigned IP address. Click the "x" box in the upper right corner of the "Manage Connections" dialog to close it and enjoy your Internet!

**.46caliber** · Aug 04, 2010, 03:54 PM

Re: Wireless Networking Trouble

Originally posted by GreyGeek

Should I kill Knetworkmanager to do this? There were no proprietary drivers listed when I followed your first set of steps, but KNetworkManager is seeing the right driver.

KNetworkMangager is a "work in progress". It works OK for some but not for others. A couple releases ago, when KNM was even worse than it is now, when someone used Synaptic to replace KNM, Synaptic would install wicd and remove KNM automatically. Now, unfortunately, it does not.

It appears that in your case, from your graphic screen capture, that KNM does see your wireless chip:

Cell 08 - Address: 00:1A:70:78

B:2F
ESSID:"Xander"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.462 GHz (Channel 11)
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:85 Signal level:0 Noise level:0
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 2048ms ago

and many other APs as well.

What you have to do now is right click on the KNM icon in the system tray and select "Manage Connections". A dialog will pop up. IF you have an ethernet cable connected to your wireless router it will show as connected (and running "ifconfig" in a Konsole will show eth0 with a valid IP address, and you should be able to browse the web). Also showing will be the access points that "iwlist" gave for your wireless access point. Underneath your access point listing will be two buttons, "Connect" and "Properties". Click on "Properties" to bring up its dialog. In its dialog is a text box for entering your WPA2 password. Enter it and click "OK" (or maybe "Apply", I don't remember which it is). IF I recall correctly, WPA2-Personal works be the other doesn't, unless they've fixed that bug.

After entering your wireless router password and closing the Properties dialog, click the "Connect" button on the "Manage Connections" dialog. After the slider bar bounces back and forth a while it should stop, and show your AP as being connected. A status line at the bottom of the dialog will show the name of your AP and the assigned IP address. Click the "x" box in the upper right corner of the "Manage Connections" dialog to close it and enjoy your Internet!

I feel like a colossal moron. I really do.

Two weeks ago, my wife and I switched to Verizon to pick up our first Android devices, Motorola Droid X.

I was having difficulty getting the phones to connect with WEP, which I shouldn't have been using anyway, so I changed some settings on the router. I also changed the password.

I feel so dumb right now. Thank you all for the patience and advice. If nothing else, I've learned more about Kubuntu/Ubuntu.

I can't express how stupid I feel. It's always worse when you do it to yourself.

**claydoh** · Aug 04, 2010, 03:59 PM

Re: Wireless Networking Trouble

Aw, heck don't sweat it

we ALL have done similar at one time or another, way more in my case.

**.46caliber** · Aug 04, 2010, 04:01 PM

Re: Wireless Networking Trouble

Now, I assume I can turn off the internal 802.11B and run off the Belkin 802.11N card so that my whole wireless network isn't dragged down.

I will fiddle with that later.

**GreyGeek** · Aug 04, 2010, 09:40 PM

Re: Wireless Networking Trouble

Originally posted by claydoh

Aw, heck don't sweat it

we ALL have done similar at one time or another, way more in my case.

That how we can recognize our mistakes when we do them again!

**.46caliber** · Aug 05, 2010, 08:16 PM

Re: Wireless Networking Trouble

GreyGreek,

You're not the Jerry that's a huge Android and Linux fan that writes for Android Central are you?

Announcement

Wireless Networking Trouble [SOLVED]

Wireless Networking Trouble [SOLVED]

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment