[SOLVED] Ubuntu 10.04 won't actually connect to wireless network

RealGomer · 07-30-2010, 09:56 PM

Right. I've removed the keyring files. I've blacklisted three of the four
rt28## files. I've followed every step and suggestion both here and on the Ubuntu forums. Still no internet. Do I need to enter / create a BSSID number (whatever & wherever that is)? Do I need to assign a MAC address? Do I need to cast bones and burn goat entrails?

Thank you.

dolphans1 · 07-31-2010, 08:35 AM

Not to hijack this thread, but I am having the same issue. When using wifi to log onto a WPA password protected wifi network, naturally, it calls for a password, then when I enter the password , it then asks for the password to "unlock keyring" , it used to just allow me to just hit cancel and I could connect via wifi, but now it just turns grey and hangs there.

Did numerous google searches and have hit a dead-end everywhere for a possible fix.

If you find a solution, please let me know...

d-1

Peacedog · 07-31-2010, 01:28 PM

@ RealGomer, Let's get some updated info from the card and your setup.

Code:

$ sudo ifconfig -a
$ sudo lsmod | grep rt
$ sudo iwconfig

@ dolphans1, Try posts # 12, 14, & 15.

Good luck. ;-)

dolphans1 · 07-31-2010, 02:23 PM

Thanks Peacedog, will try and report back....

d-1

GallopingGhost · 08-01-2010, 02:08 AM

Hate that this hasn't been resolved yet. So there was no driver in the System>Administration>Hardware Drivers? Was called Broadcom STA wireless driver. You had the exact same problem I did so I thought for sure that was it. Regardless, I hope you get this figured out

dolphans1 · 08-01-2010, 04:06 AM

Not sure if you're replying to me, but to answer, I could connect, my crude work around solution on the unlock keyring issue was to hit cancel. I never knew why it would even ask such a question because I was never asked or prompted for such an answer when making the original configuration. Just recently, it was asking the same question when I was using a wifi WPA password protected Network. the unlock keyring question would appear after entering correct WPA password, but this time it woulg grey itself out and the whole desktop would freeze. Currently Im at a place where the wifi is making an auto connection, so I can't test it, but will report make , when I go back and use same Network.

RealGomer · 08-03-2010, 02:27 PM

Here's what I got without using the switches:

red@Homebrew:~$ lsmod
Module Size Used by
rt2870sta 461811 1
binfmt_misc 6587 1
fbcon 35102 71
tileblit 2031 1 fbcon
font 7557 1 fbcon
bitblit 4707 1 fbcon
softcursor 1189 1 bitblit
vga16fb 11385 0
vgastate 8961 1 vga16fb
snd_intel8x0 25588 2
snd_ac97_codec 100646 1 snd_intel8x0
ac97_bus 1002 1 snd_ac97_codec
snd_pcm_oss 35308 0
snd_mixer_oss 13746 1 snd_pcm_oss
snd_pcm 70662 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_seq_dummy 1338 0
snd_seq_oss 26726 0
snd_seq_midi 4557 0
snd_rawmidi 19056 1 snd_seq_midi
snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
snd_seq 47263 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
radeon 674135 3
snd_timer 19098 2 snd_pcm,snd_seq
snd_seq_device 5700 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
ttm 49943 1 radeon
drm_kms_helper 29297 1 radeon
ns558 3056 0
ppdev 5259 0
drm 162471 5 radeon,ttm,drm_kms_helper
i2c_algo_bit 5028 1 radeon
gameport 9089 2 ns558
snd 54148 14 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
parport_pc 25962 1
amd64_agp 7025 1
soundcore 6620 1 snd
snd_page_alloc 7076 2 snd_intel8x0,snd_pcm
shpchp 28820 0
k8temp 3024 0
agpgart 31724 3 ttm,drm,amd64_agp
i2c_nforce2 5199 0
lp 7028 0
parport 32635 3 ppdev,parport_pc,lp
usbhid 36110 0
hid 67032 1 usbhid
pata_amd 8766 3
skge 35683 0
floppy 53016 0
red@Homebrew:~$
red@Homebrew:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0d:61:68:d7:81
inet addr:192.168.0.196 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20d:61ff:fe68:d781/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11499 (11.4 KB) TX bytes:6358 (6.3 KB)
Interrupt:19

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:480 (480.0 B) TX bytes:480 (480.0 B)

wlan0 Link encap:Ethernet HWaddr 00:40:36:3c:0a:d9
inet6 addr: fe80::240:36ff:fe3c:ad9/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:812 errors:0 dropped:0 overruns:0 frame:0
TX packets:429 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:191229 (191.2 KB) TX bytes:30616 (30.6 KB)

red@Homebrew:~$
red@Homebrew:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 RTxx70 Wireless ESSID:"" Nickname:"RT3070STA"
Mode:Auto Frequency=2.417 GHz Access Point: 00:24:01:6F: DA:F1
Bit Rate=1 Mb/s
RTS thr: off Fragment thr: off
Link Quality=10/100 Signal level:-47 dBm Noise level:-97 dBm
Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0

red@Homebrew:~$

Interesting that the 4411 says its a RT3070STA in Ubuntu but a RT2870 in WinXP. Could this be the problem? Zoom at first said it used the dongle used the 3070 driver set then changed and said it used the 2870. I had to insert some spaces wlan0 output to get rid of smilies.

RealGomer · 08-03-2010, 02:37 PM

And here is what I got with the switches:

red@Homebrew:~$ sudo ifconfig -a
[sudo] password for red:
eth0 Link encap:Ethernet HWaddr 00:0d:61:68:d7:81
inet addr:192.168.0.196 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20d:61ff:fe68:d781/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3043 errors:0 dropped:0 overruns:0 frame:0
TX packets:2978 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2639340 (2.6 MB) TX bytes:518873 (518.8 KB)
Interrupt:19

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:480 (480.0 B) TX bytes:480 (480.0 B)

wlan0 Link encap:Ethernet HWaddr 00:40:36:3c:0a:d9
inet6 addr: fe80::240:36ff:fe3c:ad9/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:7435 errors:0 dropped:0 overruns:0 frame:0
TX packets:3121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1754267 (1.7 MB) TX bytes:227012 (227.0 KB)

red@Homebrew:~$ sudo lsmod | grep rt
rt2870sta 461811 1
gameport 9089 2 ns558
parport_pc 25962 1
agpgart 31724 3 ttm,drm,amd64_agp
parport 32635 3 ppdev,parport_pc,lp
red@Homebrew:~$
red@Homebrew:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 RTxx70 Wireless ESSID:"" Nickname:"RT3070STA"
Mode:Auto Frequency=2.417 GHz Access Point: 00:24:01:6F: DA:F1
Bit Rate=1 Mb/s
RTS thr: off Fragment thr: off
Encryption key

ff
Link Quality=10/100 Signal level:-49 dBm Noise level:-97 dBm
Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0

Peacedog · 08-03-2010, 05:36 PM

It appears the wireless card is at least functioning. Have you solved the keyring problem?

Good luck. ;-)

RealGomer · 08-03-2010, 08:36 PM

No, not yet. I can connect directly thru the mobo ethernet port. I'll try the usb tomorrow with the cat5 disconnected.

RealGomer · 08-04-2010, 03:29 PM

Well, I've tried everything but the @#%$%#@ Zoom 4411 USB will not connect. Now I've found out the Windows has decided to firewall the bloody fool thing even though it's listed under Exceptions. Back it goes to MicroCenter. And off I go to th HCL.

Peacedog · 08-04-2010, 04:48 PM

You can't connect from either OS?

Good luck. ;-)

dolphans1 · 08-04-2010, 06:19 PM

Okay, I followed the steps provided and when I enter the correct password for WAP password it calls for creating a new keyring password, great right...?

Well No, when I try to enter the very first letter of my password on the first space colmun, it does not allow me to create a new keyring password.

It's as if it locks up, if I hit cancel, nothing happens, if I hit connect nothing happens, I have to shutdown

d-1

dolphans1 · 08-04-2010, 06:26 PM

Well I rebooted and the 2nd time it allowed be to connect and create the new keyring password and it allowed me to retype and was able to connect.

Not sure what happened the first go around.

Thanks,

d-1

Peacedog · 08-04-2010, 07:00 PM

Glad at least one of you is sorted.

Good luck. ;-)