Broadcom 43xx requieres modprobe and goes off after some time

thanks for your report. which version of ubuntu are you using? also can you attach the file that will be created on our desktop after doing:
lspci -vv > ~/Desktop/lspcivv12.txt

Sure. There you go.

Now it happened again, but the device appeared both in iwconfig and ifconfig (as eth1). I couldn't fix it with the command this time, but suspending and coming back worked. I hope this helps.

try to make sure eth0 is not up as a possible workaround. so, the command ifconfig should not list eth0 if you're using eth1.

which version of ubuntu are you using?

Thank you for your interest. Well, "eth0" is up, since this laptop has an Ethernet card. The problem is that shouldn't the wifi device show as "wlanX" instead of "ethX"?

I am using Ubuntu Edgy Eft 6.10.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ZombiekE wrote:
> Thank you for your interest. Well, "eth0" is up, since this laptop has
> an Ethernet card. The problem is that shouldn't the wifi device show as
> "wlanX" instead of "ethX"?
>
> I am using Ubuntu Edgy Eft 6.10.
>

what if you first take down eth0 and then try connecting with the
wireless? maybe bcm43xx is clashing with the driver of eth0 if they both
are active (I dunno). to take down eth0: sudo ifconfig eth0 down

the wireless card usually is called wlan0 when you're using ndiswrapper,
and eth1 when you're using bcm43xx.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFFRklnLM1JzWwJYEYRAjk5AJ4hvMSFwwFzB3YNovYOF4Xv+sF/GACfa09/
VCilJ4CkVcykNZOwhGP9Y4A=
=GFwz
-----END PGP SIGNATURE-----

Alright, I've just done so, and the Internet has been up all the time.

I also noticed that when experiencing these problems, once the wireless icon with the bar seemed to be frozen and I couldn't double-click on it to see the connection properties.

I will come here again next time I experience this problem. If I haven't had this issue by the 1st November I will post to tell you it works, and probably we will have to redefine this bug on Launchpad or something so that this eth0 vs. bcm43xx can be fixed.

thanks for letting us know. I'm setting this "needsinfo" to indicate that we will be waiting for your input about whether `sudo ifconfig eth0 down` fixes your issue.

So far it seems your fix works. But there's still one day left to test :). The only problem I am finding now is that it seems this has a huge ping or a DNS resolving problem (not existent in Windows XP).

So Firefox keeps "Looking up domain.whatever" until it times out. Should I file another bug for this? If you give me some tips about some things to check when this happens maybe we can make it more accurate :).

> So Firefox keeps "Looking up domain.whatever" until it times out. Should I file another bug
> for this?

I'm thinking you're bumping to bug # 24828 . Try disabling ipv6 in both ubuntu and firefox. Here's a howto https://help.ubuntu.com/community/WebBrowsingSlowIPv6IPv4

If that doesn't work, you may have a problematic dns server (ie it's because of your ISP). have a look at http://www.opendns.com and http://www.opendns.com/start/unix.php

PS. make sure to note the old DNS servers in case it doesn't work or something... and of course, always do a backup of it bf editing a system file.

Okay, my card disconnected twice today :/

When I click on the wifi icon it says it is disconnected.

Now, regarding the IPv6 solution, I think it didn't work, though I can't confirm that. I tried the Open DNS and I "accidentally" deleted my host (just under where you type the DNS) and it doesn't seem to come back if I reboot. So now I can't use Ubuntu to browse the Internet (any tip? if this is getting too off topic you can send me an e-mail).

> I "accidentally" deleted my host and it doesn't seem to come back if I reboot.

nope, don't know anything about that... I think someone from ubuntuforums.org could help...

Thanks. Still, "sudo ifconfig eth0 down" didn't fix the issue, since it "disconnected" itself again before I tried disabling IPv6 or changing the DNS. (It shows "Disconnected" if you check the status in the wifi icon, showing poor or no signal).

Could you test this with the latest version of Ubuntu? A new wireless driver is used by default, b43.

I think I didn't have these issues in 2007, so some newer version seemed to fix this stuff.

Thanks for the update, glad to hear that you no longer have this problem. I'll change the status accordingly.