Lost wireless connection after upgrading to 11.04

Please run to give us an idea of what hardware you have and what driver you are trying to run:
lspci -vvnn -d 14e4:*
sudo lshw -C network
lsmod

    Latency: 64
    Interrupt: pin A routed to IRQ 17
    Region 0: Memory at fe5fe000 (32-bit, non-prefetchable) [size=8K]
    Capabilities: <access denied>
    Kernel driver in use: b44
    Kernel modules: b44

0c:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g
WLAN [14e4:4311] (rev 01)
    Subsystem: Dell Wireless 1390 WLAN Mini-Card [1028:0007]
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 17
    Region 0: Memory at fe8fc000 (32-bit, non-prefetchable) [size=16K]
    Capabilities: <access denied>
    Kernel driver in use: b43-pci-bridge
    Kernel modules: wl, ssb

On Sat, Jun 25, 2011 at 6:30 PM, Ubfan <<email address hidden>
> wrote:

> Your question #162759 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/162759
>
> Status: Open => Needs information
>
> Ubfan requested more information:
> Please run to give us an idea of what hardware you have and what driver you
> are trying to run:
> lspci -vvnn -d 14e4:*
> sudo lshw -C network
> lsmod
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/162759
>
> You received this question notification because you asked the question.
>

configuration: driver=b43-pci-bridge latency=0
       resources: irq:17 memory:fe8fc000-fe8fffff
  *-network
       description: Ethernet interface
       product: BCM4401-B0 100Base-TX
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: eth0
       version: 02
       serial: 00:1c:23:b3:18:87
       size: 100Mbit/s
       capacity: 100Mbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical mii 10bt
10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=b44
driverversion=2.0 duplex=full ip=192.168.0.5 latency=64 link=yes
multicast=yes port=twisted pair speed=100Mbit/s
       resources: irq:17 memory:fe5fe000-fe5fffff

On Sat, Jun 25, 2011 at 6:43 PM, Cary Devlin <email address hidden> wrote:

> Latency: 64
> Interrupt: pin A routed to IRQ 17
> Region 0: Memory at fe5fe000 (32-bit, non-prefetchable) [size=8K]
> Capabilities: <access denied>
> Kernel driver in use: b44
> Kernel modules: b44
>
> 0c:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g
> WLAN [14e4:4311] (rev 01)
> Subsystem: Dell Wireless 1390 WLAN Mini-Card [1028:0007]
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
> <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 17
> Region 0: Memory at fe8fc000 (32-bit, non-prefetchable) [size=16K]
> Capabilities: <access denied>
> Kernel driver in use: b43-pci-bridge
> Kernel modules: wl, ssb
>
>
>
>
> On Sat, Jun 25, 2011 at 6:30 PM, Ubfan <
> <email address hidden>> wrote:
>
>> Your question #162759 on Ubuntu changed:
>> https://answers.launchpad.net/ubuntu/+question/162759
>>
>> Status: Open => Needs information
>>
>> Ubfan requested more information:
>> Please run to give us an idea of what hardware you have and what driver
>> you are trying to run:
>> lspci -vvnn -d 14e4:*
>> sudo lshw -C network
>> lsmod
>>
>> --
>> To answer this request for more information, you can either reply to
>> this email or enter your reply at the following page:
>> https://answers.launchpad.net/ubuntu/+question/162759
>>
>> You received this question notification because you asked the question.
>>
>
>

it seems that 11.04 has problem connecting to certain wireless routers. i have a linksys wireless and it won't connect to it. however, 10.04 works fine.

Choices are wonderful, but having two drivers to choose from can lead to configuration problems -- you appear to have parts of the b43 driver configuration and parts of the Broadcom wl (or STA) driver. The b43 driver is present by default, and all you had to do was load the firmware for it. The way to load this firmware is to either install package firmware-b43-installer (for your chip) OR to install package b43-fwcutter with an internet connection and accept the offer to download the Broadcom files. That should have given you a working connection. By loading the "Additional Drivers" Broadcom STA driver, you also SHOULD have gotten a working connection, but it looks like the process didn't successfully remove all the b43 pieces. See the link for details on setting up wireless for b43 chips:
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#b43%20-%20Internet%20access
  You didn't post the output of the lsmod command, so we don't know what driver (wl or b43) is actually loaded.
Why don't you disable the Additional Drivers Broadcom driver, and install the firmware (as described above). I run the b43 and use the open firmware from the firmware-b43-installer package on a linksys router with no problems. I don't run natty much, but it works fine with my hardware.
Good Luck

Here is the output of the ismod command.
The first command was previously sent.
  Sorry, I am not meaning for this issue to be getting so confusing.
I am not an expert, which I have mentioned.
Thank You for your help.
*-network
       description: Network controller
       product: BCM4311 802.11b/g WLAN
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:0c:00.0
       version: 01
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=b43-pci-bridge latency=0
       resources: irq:17 memory:fe8fc000-fe8fffff
  *-network
       description: Ethernet interface
       product: BCM4401-B0 100Base-TX
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: eth0
       version: 02
       serial: 00:1c:23:b3:18:87
       size: 100Mbit/s
       capacity: 100Mbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical mii 10bt
10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=b44
driverversion=2.0 duplex=full ip=192.168.0.5 latency=64 link=yes
multicast=yes port=twisted pair speed=100Mbit/s
       resources: irq:17 memory:fe5fe000-fe5fffff

On Sun, Jun 26, 2011 at 12:35 PM, Ubfan <
<email address hidden>> wrote:

> Your question #162759 on gnome-nettool in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/162759
>
> Status: Open => Answered
>
> Ubfan proposed the following answer:
> Choices are wonderful, but having two drivers to choose from can lead to
> configuration problems -- you appear to have parts of the b43 driver
> configuration and parts of the Broadcom wl (or STA) driver. The b43 driver
> is present by default, and all you had to do was load the firmware for it.
> The way to load this firmware is to either install package
> firmware-b43-installer (for your chip) OR to install package b43-fwcutter
> with an internet connection and accept the offer to download the Broadcom
> files. That should have given you a working connection. By loading the
> "Additional Drivers" Broadcom STA driver, you also SHOULD have gotten a
> working connection, but it looks like the process didn't successfully remove
> all the b43 pieces. See the link for details on setting up wireless for b43
> chips:
>
> https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#b43%20-%20Internet%20access
> You didn't post the output of the lsmod command, so we don't know what
> driver (wl or b43) is actually loaded.
> Why don't you disable the Additional Drivers Broadcom driver, and install
> the firmware (as described above). I run the b43 and use the open firmware
> from the firmware-b43-installer package on a linksys router with no
> problems. I don't run natty much, but it works fine with my hardware.
> Good Luck
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/162759/+confirm?answer_id=4
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/162759
>
> You received this question notification because you asked the question.
>

That's not the output from lsmod (not ismod!).

On 6/27/2011 4:01 PM, Ubfan wrote:
> Your question #162759 on gnome-nettool in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/162759
>
> Ubfan posted a new comment:
> That's not the output from lsmod (not ismod!).
>
I copied and pasted the command right from the link.
Sorry, I will do it again and send it and remember, I am not an expert
at this and having to deal with a wireless issue in a stable, not beta
release, is a hassle.

I am not how I did it and I downloaded BCM 43 wireless and firmware cutter
again and my wireless connection works.

On Mon, Jun 27, 2011 a t 5:21 PM, Cary Devlin <
<email address hidden>> wrote:

> Your question #162759 on gnome-nettool in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/162759
>
> You gave more information on the question:
> On 6/27/2011 4:01 PM, Ubfan wrote:
> > Your question #162759 on gnome-nettool in Ubuntu changed:
> >
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/162759
> >
> > Ubfan posted a new comment:
> > That's not the output from lsmod (not ismod!).
> >
> I copied and pasted the command right from the link.
> Sorry, I will do it again and send it and remember, I am not an expert
> at this and having to deal with a wireless issue in a stable, not beta
> release, is a hassle.
>
> --
> You received this question notification because you asked the question.
>