Sees wireless networks but wont connect

[theboomboomcars]

I have a Gateway mx3210 notebook with the realtek 8185 wireless chip in it. I have not had any problems with loading the module, so I took it off the blacklist and put the module in the load module file, with no problems. When I use the wireless assistant I can see the networks, but it always fails to connect. The system monitor shows activity, but I can't do anything with the network.

Using iwconfig I can see the network info, essid, access point, etc.

uname -a: Linux lapticus-compuman 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

[theboomboomcars (theboomboomcars)]

Here is the dmesg out put.

[theboomboomcars (theboomboomcars)]

Here is the lspci -vvnn out put.

[Susan Cragin (susancragin)]

This is my 2-cent workaround, in case you have the same problem I do.
My Acer Ferrari never finds the wireless on bootup. Somehow it always looks for the last IP address rather than a new one.
So, I just open the wireless icon in the top right-hand corner and re-click on the wireless network I want.
When it start looking again, it usually succeeds.
If not, I re-boot the modem.
"Instant" success.

[theboomboomcars (theboomboomcars)]

When I click on the network it tries to connect and after a while it says
that it failed to connect to the network. I have tried with 3 different
networks, the one at school, it has a hidden essid and mac address filtering
but no other security. One at home that has a hidden essid, mac address
filtering, and wep. Another one at home that I set up to test with an old
router with no security. It fails to connect every time.

It fails at boot, when I use the network manager, wlassistant, or if I use
ifdown and ifup in the terminal.

Thanks for the assistance, but unfortunately it doesn't want to respond to
an easy fix.

On 3/29/07, susancragin <email address hidden> wrote:
>
> This is my 2-cent workaround, in case you have the same problem I do.
> My Acer Ferrari never finds the wireless on bootup. Somehow it always
> looks for the last IP address rather than a new one.
> So, I just open the wireless icon in the top right-hand corner and
> re-click on the wireless network I want.
> When it start looking again, it usually succeeds.
> If not, I re-boot the modem.
> "Instant" success.
>
> --
> Sees wireless networks but wont connect
> https://launchpad.net/bugs/98612
>

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the contents of your '/etc/network/interfaces' file? Thanks in advance.

[theboomboomcars (theboomboomcars)]

I have two files, one for home, and one for school. I'll attatch both.
I haven't found another reliable way to be able to connect to the network at
school and the network at home, that was on edgy, since fiesty wont connect
at all.

On 3/29/07, Brian Murray <email address hidden> wrote:
>
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. Could you please add the contents of your
> '/etc/network/interfaces' file? Thanks in advance.
>
> ** Changed in: Ubuntu
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>
> --
> Sees wireless networks but wont connect
> https://launchpad.net/bugs/98612
>

[Brian Murray (brian-murray)]

I take your statement to mean that you have two
'/etc/network/interfaces' files. If that is the case and there is
information statically configured in them for your network interface
this will not work with network manager. For network manager to manage
your interface there should only be lines like this:

auto eth0
iface eth0 inet dhcp

in it.

[theboomboomcars (theboomboomcars)]

The only thing different between the two is the wlan0 info, essid and the
pass code. WIth edgy I had no problems doing it this way, since it wouldn't
remember multiple locations for the wireless network. Network manager is
now showing the network under available networks, but when I click on it it
still fails to connect.

On 3/29/07, Brian Murray <email address hidden> wrote:
>
> I take your statement to mean that you have two
> '/etc/network/interfaces' files. If that is the case and there is
> information statically configured in them for your network interface
> this will not work with network manager. For network manager to manage
> your interface there should only be lines like this:
>
> auto eth0
> iface eth0 inet dhcp
>
> in it.
>
> --
> Sees wireless networks but wont connect
> https://launchpad.net/bugs/98612
>

[theboomboomcars (theboomboomcars)]

Sorry this didn't get up last night, I just responded through e-mail and attatched them, but I guess you can't do that.

[Brian Murray (brian-murray)]

My point is that network manager will _not_ manage your interface if it is configured more than what I showed earlier. Network manager via gnome-keyring will remember the network information you have in both of your interfaces files.

[theboomboomcars (theboomboomcars)]

I copied the default interfaces file back and it didn't help. Should I try
it with just the eth0 like you stated earlier, rr does it need each device
there? I only have 2 eht0 for the wired, and wlan0 for the wireless but the
default file has a bunch of eths.

They are all now set like:
auto eth0
iface eth0 inet dhcp

Still not connecting to anything. I can see the network in the network
manager, usually, but it doesn't connect. I don't receive an IP and I can't
ping the router.

Thank you for the help.

On 3/30/07, Brian Murray <email address hidden> wrote:
>
> My point is that network manager will _not_ manage your interface if it
> is configured more than what I showed earlier. Network manager via
> gnome-keyring will remember the network information you have in both of
> your interfaces files.
>
> --
> Sees wireless networks but wont connect
> https://launchpad.net/bugs/98612
>

[theboomboomcars (theboomboomcars)]

I just tried again at my home network with the default interfaces file(attached). When I plug in the wired network I get the little icon with two dots and the blue thing circling the front dot is green and the back dot is blue. When I try to connect with the wireless I get the same thing except both dots are blue. I don't know if this is significant but I thought I would mention it.

[theboomboomcars (theboomboomcars)]

After trying to connect to the network I check dmesg again.
At the end of the report this is what is says:
rtl8180: Setting SW wep key
[108895.912000] rtl8180: Bringing up iface
[108896.120000] rtl8180: Card successfully reset
[108897.012000] ADDRCONF(NETDEV_UP): wlan0: link is not ready

It repeats "rtl8180: Setting SW wep key" almost 100 times. before it goes to the next step.
 Attached is the new log

[Brian Murray (brian-murray)]

Looking in your dmesg log it appears that it is attempting to connect to the wrong ESSID - "Linking with UVSC-Wireles". As you can see an 's' is getting truncated. Please add an extra character to the ESSID name to see if that resolves the issue. This may be the same bug as bug 74672.

[theboomboomcars (theboomboomcars)]

That did it. Thank you.

On 3/31/07, Brian Murray <email address hidden> wrote:
>
> Looking in your dmesg log it appears that it is attempting to connect to
> the wrong ESSID - "Linking with UVSC-Wireles". As you can see an 's' is
> getting truncated. Please add an extra character to the ESSID name to
> see if that resolves the issue. This may be the same bug as bug 74672.
>
> --
> Sees wireless networks but wont connect
> https://launchpad.net/bugs/98612
>