BCM4311 - active connection - no internet

Hi,

I’m on a brand new openSUSE 11.2 KDE,
wireless is bcm4311,
I installed the bcm43xx_firmware and followed the instruction from linuxwireless.org
I tried

b43 - Linux Wireless
and the one before this but with this one I managed to make the wireless work on Gnome (openSUSE 11.2) but no luck in KDE

The light is on, the networkmanager detects the wireless and connects to it. sometimes it says that it’s active and sometimes not, but even when it says it’s active there is no internet. no application can connect to internet and there’s no ping.

Here are some info which may be helpful:

sam@linux-p62u:~> /sbin/lspci
...
03:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
sam@linux-p62u:~> /sbin/lspci -n
...
03:01.3 0880: 1180:0852 (rev 05)
0b:00.0 0280: 14e4:4311 (rev 01)
sam@linux-p62u:~> dmesg | grep b43
    7.788061] b43-pci-bridge 0000:0b:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    7.788074] b43-pci-bridge 0000:0b:00.0: setting latency timer to 64
    7.899726] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
   25.866084] b43 ssb0:0: firmware: requesting b43/ucode5.fw
   25.878195] b43 ssb0:0: firmware: requesting b43/pcm5.fw
   25.891629] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
   25.904593] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
   26.030060] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
   26.072622] Registered led device: b43-phy0::tx
   26.072676] Registered led device: b43-phy0::rx
   26.072732] Registered led device: b43-phy0::radio
  533.652078] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
  533.694885] Registered led device: b43-phy0::tx
  533.695356] Registered led device: b43-phy0::rx
  533.695790] Registered led device: b43-phy0::radio

sam@linux-p62u:~> /usr/sbin/iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"Glocalnet Wireless"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:90:D0:EF:79:8D
          Bit Rate=54 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=65/70  Signal level=-45 dBm  Noise level=-57 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

pan0      no wireless extensions.
sam@linux-p62u:~> sudo /usr/sbin/iwlist scan                                                        
root's password:                                                                                    
lo        Interface doesn't support scanning.                                                       

eth0      Interface doesn't support scanning.

wmaster0  Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: 00:90:D0:EF:79:8D
                    Channel:6                 
                    Frequency:2.437 GHz (Channel 6)
                    Quality=66/70  Signal level=-44 dBm  
                    Encryption key:on                    
                    ESSID:"Glocalnet Wireless"           
                    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=00000001bfafd188                          
                    Extra: Last beacon: 872ms ago                       
                    IE: Unknown: 0012476C6F63616C6E657420576972656C657373
                    IE: Unknown: 010882848B962430486C                    
                    IE: Unknown: 030106                                  
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD060010180200F0
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101880003A4000027A4000042435E0062322F00
          Cell 02 - Address: 00:22:3F:C2:12:B6
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=40/70  Signal level=-70 dBm
                    Encryption key:on
                    ESSID:"Dora-Wireless"
                    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=0000040fa6a5cf21
                    Extra: Last beacon: 1379ms ago
                    IE: Unknown: 000D446F72612D576972656C657373
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 030101
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD090010180200F0000000
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00

pan0      Interface doesn't support scanning.

and lspci -v

0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
        Subsystem: Dell Wireless 1390 WLAN Mini-Card
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at efcfc000 (32-bit, non-prefetchable) [size=16]
        Capabilities: [40] Power Management version 2
        Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Express Legacy Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel <?>
        Kernel driver in use: b43-pci-bridge

Thanks for your time and will appreciate any help. :)[/size]

From YaST (Network Devices >>> Network Setting >>> General Options) I switch from NetworkManager to Traditional ifup.
Then go and change Activate device for both wlan0 and eth0 from “At Boot Time” to “On Cable Connection” (as I read in the other thread) and now the internet is up in ifup mode. But I still have no idea why it doesn’t work with NetworkManager. With NetworkManager that’s the same story again. It says active but no application can connect to internet.

On 11/15/2009 10:06 AM, samadg wrote:
>
> From YaST (Network Devices >>> Network Setting >>> General Options) I
> switch from NetworkManager to Traditional ifup.
> Then go and change Activate device for both wlan0 and eth0 from “At
> Boot Time” to “On Cable Connection” (as I read in the other thread) and
> now the internet is up in ifup mode. But I still have no idea why it
> doesn’t work with NetworkManager. With NetworkManager that’s the same
> story again. It says active but no application can connect to internet.

Wireless should be “on boot”, wired " cable connection". Once you do that, both
ifup and NM should work.

Thank for the reply.
Wireless is now set to “on boot”, but again it works with ifup and in NetworkManager it says active but there’s no connection :\

Either there was something wrong with the KDE’s NetworkManager or my lack of knowledge to get it to work, I got wicd from
Index of /repositories/system:/wicd/openSUSE_11.1
and everything is fine. (There was no 11.2 so I went for 11.1) It does the job NetworkManager couldn’t and in a better way.
Thanks for your time.:slight_smile:

This was easier than I expected - there should be some way of letting users know they have to run this command or having OS 11.2 do it.

Basically connect a wire;
sudo /usr/sbin/install_bcm43xx_firmware

and viola it works like a champ. I think I have the same card as the OP BCM4311 was active no connection. Network manager worked fine after that.

On 11/27/2009 12:16 AM, scoday wrote:
>
> This was easier than I expected - there should be some way of letting
> users know they have to run this command or having OS 11.2 do it.
>
> Basically connect a wire;
> sudo /usr/sbin/install_bcm43xx_firmware

This procedure has been discussed many times in these forums and is part of the
stickies. My conclusion is that users will not read anything - even a dmesg
output that hits them over the head with a “firmware not found” message.

For 11.3, a change has been committed that runs that script during installation
if a Broadcom device has been found. This feature was requested fairly early in
the 11.2 cycle, but did not get implemented.

Larry Finger wrote:

> On 11/27/2009 12:16 AM, scoday wrote:
>>
>> This was easier than I expected - there should be some way of letting
>> users know they have to run this command or having OS 11.2 do it.
>>
>> Basically connect a wire;
>> sudo /usr/sbin/install_bcm43xx_firmware
>
> This procedure has been discussed many times in these forums and is part
> of the stickies. My conclusion is that users will not read anything - even
> a dmesg output that hits them over the head with a “firmware not found”
> message.
>
> For 11.3, a change has been committed that runs that script during
> installation if a Broadcom device has been found. This feature was
> requested fairly early in the 11.2 cycle, but did not get implemented.

What’s a “sticky”?

On 11/28/2009 06:24 AM, Larry Bristol wrote:
>
> What’s a “sticky”?

That is an entry in the forum that “sticks” at the beginning because
it has special information that should be read by everyone. See the
first 3 in this forum.

Larry Finger wrote:

> On 11/28/2009 06:24 AM, Larry Bristol wrote:
>>
>> What’s a “sticky”?
>
> That is an entry in the forum that “sticks” at the beginning because
> it has special information that should be read by everyone. See the
> first 3 in this forum.

Thanks, Larry, but I still do not understand. The first three threads in
this forum are:
problem: wireless to wlan works - no internet access
Cannot connect to a hidden SSID
BCM 4322 On Fresh 11.2 Install, Not Working
Perhaps I am missing something, because I do not see anything “special”
about these particular threads.

On 11/29/2009 07:14 AM, Larry Bristol wrote:
>
> Thanks, Larry, but I still do not understand. The first three threads in
> this forum are:
> problem: wireless to wlan works - no internet access
> Cannot connect to a hidden SSID
> BCM 4322 On Fresh 11.2 Install, Not Working
> Perhaps I am missing something, because I do not see anything “special”
> about these particular threads.

Go to http://forums.opensuse.org/network-internet/wireless/.

Larry Bristol wrote:

> Larry Finger wrote:
>
>> On 11/28/2009 06:24 AM, Larry Bristol wrote:
>>>
>>> What’s a “sticky”?
>>
>> That is an entry in the forum that “sticks” at the beginning because
>> it has special information that should be read by everyone. See the
>> first 3 in this forum.
>
> Thanks, Larry, but I still do not understand. The first three threads in
> this forum are:
> problem: wireless to wlan works - no internet access
> Cannot connect to a hidden SSID
> BCM 4322 On Fresh 11.2 Install, Not Working
> Perhaps I am missing something, because I do not see anything “special”
> about these particular threads.

It’s pretty sad when you ask a question in a newsgroup, get a response that
insists you “read the stickies”, have no idea what that means, ask where
you can find these “stickes”, and do not get an answer for that either. Is
there a “sticky” that tells you what a “sticky” is and where you go to find
the “stickies”?

On 12/05/2009 09:30 AM, Larry Bristol wrote:
>
> It’s pretty sad when you ask a question in a newsgroup, get a response that
> insists you “read the stickies”, have no idea what that means, ask where
> you can find these “stickes”, and do not get an answer for that either. Is
> there a “sticky” that tells you what a “sticky” is and where you go to find
> the “stickies”?

OK, I see my mistake. I referred you to “this forum”, when I should
have given you a URL. Go to

http://forums.opensuse.org/network-internet/wireless/

When you bring up that page, you will notice that the first 3 articles
are:

Sticky: Getting Your Wireless to Work
lwfinger

Sticky Thread Sticky: My wireless doesn’t work - a primer on what I
should do next
lwfinger

Sticky Thread Sticky: Welcome
deltaflyer44

I do not know how you are reading these posts, but in the future when
someone tells you to go to the forum, fire up a browser.

As stated above:
Go to Wireless - openSUSE Forums

This will land you on the first page of the Wireless sub-forum.
openSUSE Forums > Network/Internet » Wireless
The first three thread entries are entitled “Sticky”.

If you still are finding it try:
Getting Your Wireless to Work - openSUSE Forums
My wireless doesn’t work - a primer on what I should do next - openSUSE Forums
Welcome - openSUSE Forums

Larry Finger wrote:

> On 12/05/2009 09:30 AM, Larry Bristol wrote:
>>
>> It’s pretty sad when you ask a question in a newsgroup, get a response
>> that insists you “read the stickies”, have no idea what that means, ask
>> where
>> you can find these “stickes”, and do not get an answer for that either.
>> Is there a “sticky” that tells you what a “sticky” is and where you go to
>> find the “stickies”?
>
> OK, I see my mistake. I referred you to “this forum”, when I should
> have given you a URL. Go to
>
> http://forums.opensuse.org/network-internet/wireless/
>
> When you bring up that page, you will notice that the first 3 articles
> are:
>
> Sticky: Getting Your Wireless to Work
> lwfinger
>
> Sticky Thread Sticky: My wireless doesn’t work - a primer on what I
> should do next
> lwfinger
>
> Sticky Thread Sticky: Welcome
> deltaflyer44
>
> I do not know how you are reading these posts, but in the future when
> someone tells you to go to the forum, fire up a browser.

OK, thanks. I can understand that (although I am not thrilled with the
prospect). When using a browser to access this newsgroup, I can actually
see these things called “stickies”. Something is pretty screwed up,
however, when you cannot see them using a standard newsreader, such as
knode!

fuscop wrote:

>
> As stated above:
> Go to ‘Wireless - openSUSE Forums’
> (http://forums.opensuse.org/network-internet/wireless/)
>
> This will land you on the first page of the Wireless sub-forum.
> openSUSE Forums > Network/Internet » Wireless
> The first three thread entries are entitled “Sticky”.
>
> If you still are finding it try:
> ‘Getting Your Wireless to Work - openSUSE Forums’
> (http://tinyurl.com/cwx2vt)
> ‘My wireless doesn’t work - a primer on what I should do next -
> openSUSE Forums’ (http://tinyurl.com/6peanc)
> ‘Welcome - openSUSE Forums’ (http://tinyurl.com/6qbqn8)

Thanks. I can see the 3 “stickies” when using a browser.

On 12/06/2009 08:08 AM, Larry Bristol wrote:
>
> OK, thanks. I can understand that (although I am not thrilled with the
> prospect). When using a browser to access this newsgroup, I can actually
> see these things called “stickies”. Something is pretty screwed up,
> however, when you cannot see them using a standard newsreader, such as
> knode!

I use Thunderbird to read the forums. It saves only the last 500
headers. Presumable knode does something like that.

Larry Finger wrote:

> On 12/06/2009 08:08 AM, Larry Bristol wrote:
>>
>> OK, thanks. I can understand that (although I am not thrilled with the
>> prospect). When using a browser to access this newsgroup, I can actually
>> see these things called “stickies”. Something is pretty screwed up,
>> however, when you cannot see them using a standard newsreader, such as
>> knode!
>
> I use Thunderbird to read the forums. It saves only the last 500
> headers. Presumable knode does something like that.

It’s configurable. I’m using the defaults. For what it’s worth, these are:
expire old articles automatically
purge groups every: 5 days
keep read articles: 10 days
keep unread articles: 15 days
remove articles that are not available on the server
preserve threads

At the beginning I had the same problem with NM after installing Suse 11.2 After reading a couple of your comments now it works.

  1. The first thing is with Yast (Applications -> Yast -> Network devices) make the wlan0 start-up from boot, and eth0 cable connection; options are available if you change among top options ‘General’ and others.
  2. Configure the the SSID, password, etc. be sure to allow NM control
  3. Once you finished logout and restart
  4. Log in as normally you do, click over the NM icon, select the network, and click over, It will start activating the connection.
  5. Successfully connected :slight_smile:

I hope this step may help you, so you don’t waste as much time as I did :slight_smile: