Wired/Wireless disconnected, device not ready (firmware missing)

https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx

I followed the instructions for b43 - No Internet access. I placed the files in the Home folder, I installed the b43-fwcutter from the DVD I installed ubuntu from and I typed the things I got from the instructions and these are what I got:

jaime@jaime:~$ tar xfvj broadcom-wl-4.150.10.5.tar.bz2
tar (child): broadcom-wl-4.150.10.5.tar.bz2: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
jaime@jaime:~$ sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o
This file is recognised as:
  ID : FW10
  filename : wl_apsta.o
  version : 295.14
  MD5 : e08665c5c5b66beb9c3b2dd54aa80cb3
Extracting b43legacy/ucode2.fw
Extracting b43legacy/ucode4.fw
Extracting b43legacy/ucode5.fw
Extracting b43legacy/ucode11.fw jaime@jaime:~$ tar xfvj broadcom-wl-4.150.10.5.tar.bz2
tar (child): broadcom-wl-4.150.10.5.tar.bz2: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
jaime@jaime:~$ sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o
This file is recognised as:
  ID : FW10
  filename : wl_apsta.o
  version : 295.14
  MD5 : e08665c5c5b66beb9c3b2dd54aa80cb3
Extracting b43legacy/ucode2.fw
Extracting b43legacy/ucode4.fw
Extracting b43legacy/ucode5.fw
Extracting b43legacy/ucode11.fw
Extracting b43legacy/pcm4.fw
Extracting b43legacy/pcm5.fw
Extracting b43legacy/a0g0bsinitvals2.fw
Extracting b43legacy/b0g0bsinitvals5.fw
Extracting b43legacy/a0g0initvals5.fw
Extracting b43legacy/a0g1bsinitvals5.fw
Extracting b43legacy/a0g0initvals2.fw
Extracting b43legacy/a0g1initvals5.fw
Extracting b43legacy/b0g0bsinitvals2.fw
Extracting b43legacy/b0g0initvals5.fw
Extracting b43legacy/b0g0initvals2.fw
Extracting b43legacy/a0g0bsinitvals5.fw
jaime@jaime:~$ sudo b43-fwcutter --unsupported -w /lib/firmware broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o
Cannot open input file broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o
Extracting b43legacy/pcm4.fw
Extracting b43legacy/pcm5.fw
Extracting b43legacy/a0g0bsinitvals2.fw
Extracting b43legacy/b0g0bsinitvals5.fw
Extracting b43legacy/a0g0initvals5.fw
Extracting b43legacy/a0g1bsinitvals5.fw
Extracting b43legacy/a0g0initvals2.fw
Extracting b43legacy/a0g1initvals5.fw
Extracting b43legacy/b0g0bsinitvals2.fw
Extracting b43legacy/b0g0initvals5.fw
Extracting b43legacy/b0g0initvals2.fw
Extracting b43legacy/a0g0bsinitvals5.fw
jaime@jaime:~$ sudo b43-fwcutter --unsupported -w /lib/firmware broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o
Cannot open input file broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o

Still can`t connect to the internet...

I'm having the exact same problems. However, I've been trying to use the 64bit version, so i'm going to install the 32bit version and give that a try. Also I can't seem to find the device list...

According to the link to a list of supported PCI devices just under the "installing b43 drivers" section, your 4311 chip needs the b43 firmware, not the b43legacy. When the b43-fwcutter is installed from scratch, and has a wired link, it will download the correct file from Broadcom (if you accept it's offer to download). If you really do not have the firmware files in location: /lib/firmware/b43 , you may try locating a slightly later version of the file you downloaded, or try the open source firmware from firmware-b43-installer. The open source firmware will be put into directory /lib/firmware/b43-open, which will be checked if the /lib/firmware/b43 directory is not present. Alternatively, run the b43-fwcutter on the file from your windows install disk, that should be the correct version of firmware.

Sorry, I'm having a hard time following what you mean by that. I've just recently started using Ubuntu and I'm not really that much familiar with the tricks in here. Would you mind making it a little bit more simple?

From what you posted above, I could not tell if the correct firmware had been installed -- the correct firmware for you 4311 chip should be put into directory /lib/firmware/b43, so take a command line listing of that directory. Pop up a terminal with Ctrl-Alt-t and type:
ls /lib/firmware/b43
If you see a bunch of ucode... .fw files, you have the correct firmware, the the issue become one of driver selection.
If you do not have anything output from the ls command, the directory probably does not exist, so the firmware was not installed. The /lib/firmware/b43legacy is NOT the correct firmware, but if it exists, just ignore it.
Another set of firmware which should work with your 4311 chip is the open source firmware -- I use it myself with a 4312 chip. If you cannot get a wired connection working to allow the b43-fwcutter package installation to download the files to get the b43 Broadcom proprietary firmware, you might try the open source firmware which is on the installation disk in package firmware-b43-installer. This package will install firmware in a separate directory, /lib/firmware/b43-open, so it may be installed along with the /lib/firmware/b43 directory. If both sets of firmware are present, the b43 will be used.
Another way to get the firmware is to run the b43-fwcutter on the driver file pulled off your Wireless installation disk if you have one. Its been so long since I've done that that I forget which file -(something like BCM???.sys ) -- check the man page for b43-fwcutter (man b43-fwcutter). Hopefully, once the correct firmware is installed, things will work. If not, we'll need to see what driver is being loaded (two choices for driver which should work for you, the b43 or the Braodcom STA also known as the wl driver), and if it is being configured correctly.

i've manage to get it working.

on the ubuntu disc there's a folder called 'pool', click in. go to the
folder called 'main'
, then 'n', then 'ndiswrapper', double click the 'common' file, install it,
then install the 'utils' file. after that go up a level, go to the folder
'ndisgtk', double click the file and install it.

once installed, go to System/Administration, you should now see 'Windows
Wireless Drivers', click this and install your driver. you will need to
restart the computer. well it worked for me. give it a go if you haven't
already.

Cheers.

On 26 March 2011 06:26, Ubfan <email address hidden> wrote:

> Question #150362 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/150362
>
> Ubfan posted a new comment:
> >From what you posted above, I could not tell if the correct firmware had
> been installed -- the correct firmware for you 4311 chip should be put into
> directory /lib/firmware/b43, so take a command line listing of that
> directory. Pop up a terminal with Ctrl-Alt-t and type:
> ls /lib/firmware/b43
> If you see a bunch of ucode... .fw files, you have the correct firmware,
> the the issue become one of driver selection.
> If you do not have anything output from the ls command, the directory
> probably does not exist, so the firmware was not installed. The
> /lib/firmware/b43legacy is NOT the correct firmware, but if it exists, just
> ignore it.
> Another set of firmware which should work with your 4311 chip is the open
> source firmware -- I use it myself with a 4312 chip. If you cannot get a
> wired connection working to allow the b43-fwcutter package installation to
> download the files to get the b43 Broadcom proprietary firmware, you might
> try the open source firmware which is on the installation disk in package
> firmware-b43-installer. This package will install firmware in a separate
> directory, /lib/firmware/b43-open, so it may be installed along with the
> /lib/firmware/b43 directory. If both sets of firmware are present, the b43
> will be used.
> Another way to get the firmware is to run the b43-fwcutter on the driver
> file pulled off your Wireless installation disk if you have one. Its been
> so long since I've done that that I forget which file -(something like
> BCM???.sys ) -- check the man page for b43-fwcutter (man b43-fwcutter).
> Hopefully, once the correct firmware is installed, things will work. If
> not, we'll need to see what driver is being loaded (two choices for driver
> which should work for you, the b43 or the Braodcom STA also known as the wl
> driver), and if it is being configured correctly.
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Thanks for posting your solution Scott, I stopped using ndiswrapper when the b43 driver could do WPA, and remember it was a real problem getting it configured to run at boot time. Time for me to take a look at ndisgtk and how it works.

Hi there, Ubfan, Scott. I did what I read from your comments and here is the step by step procedure of how I tried to do it.

1. I went to Terminal
2. I typed: ls /lib/firmware/b43 and I got this: bash: ls/lib/firmware/b43: No such file or directory
3. So I went to Computer>File System>lib>firmware.
4. I tried to look for b43-open, but the only thing I found closest to it was b43legacy (which you said was NOT the correct firmware for me)

5. So I went to the Ubuntu disk folder (Ubuntu 10.10 i386) and did what Scott did above).
6. I installed the ndiswrapper (both common and utils) together with the ndisgtk file.
7. True enough I did find Windows Wireless Drivers in System>Administration, however, after I clicked on the button where it says Install New Driver, it comes up with a bunch of folders...
*I did notice however that there was this folder in there: broadcom-wl-4.150.10.5.tar.bz2, which was useless because when I tried installing it, it says Not valid driver .inf file.

8. So I tried to look for the b43-fwcutter again. I found it over at Ubuntu...>pool>main>b>b43-fwcutter and I reinstalled it again. After that I did the steps 1-7 again with no success.

Any steps that I missed out on?

The way i see it, once you get to the point where it asks you to install the
new driver, it's probably up to the driver, or the hardware. have you
googled compatibility issues with your wi-fi dongle on linux?

i'm afraid i'm only 1 day old when it comes to ubuntu/linux, so i can't
offer any real assistance. :(

Scott

On 26 March 2011 19:48, jxwxnx <email address hidden> wrote:

> Question #150362 on gnome-nettool in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/150362
>
> Status: Answered => Open
>
> jxwxnx is still having a problem:
> Hi there, Ubfan, Scott. I did what I read from your comments and here is
> the step by step procedure of how I tried to do it.
>
> 1. I went to Terminal
> 2. I typed: ls /lib/firmware/b43 and I got this: bash: ls/lib/firmware/b43:
> No such file or directory
> 3. So I went to Computer>File System>lib>firmware.
> 4. I tried to look for b43-open, but the only thing I found closest to it
> was b43legacy (which you said was NOT the correct firmware for me)
>
> 5. So I went to the Ubuntu disk folder (Ubuntu 10.10 i386) and did what
> Scott did above).
> 6. I installed the ndiswrapper (both common and utils) together with the
> ndisgtk file.
> 7. True enough I did find Windows Wireless Drivers in
> System>Administration, however, after I clicked on the button where it says
> Install New Driver, it comes up with a bunch of folders...
> *I did notice however that there was this folder in there:
> broadcom-wl-4.150.10.5.tar.bz2, which was useless because when I tried
> installing it, it says Not valid driver .inf file.
>
> 8. So I tried to look for the b43-fwcutter again. I found it over at
> Ubuntu...>pool>main>b>b43-fwcutter and I reinstalled it again. After
> that I did the steps 1-7 again with no success.
>
> Any steps that I missed out on?
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>

When you reinstalled the b43-fwcutter, did you get asked to approve a download of the Broadcom driver/files? If you did not get asked, probably that was because of the previous install was not completely removed. Try a full remove, then do the install (when on a wired connection so the download will work).
sudo apt-get purge b43-fwcutter
sudo apt-get install b43-fwcutter

Ok. I wanted to have a fresh new start so I reinstalled the whole thing all over again. And then I did these:

1. I connected the internet wire to the laptop. It did that "signal thing" for a while and then it turned up with an exclamation mark.
2. I did the "sudo apt-get purge b43-fwcutter" in the terminal, I got this:

Reading package lists...Done
Building dependency tree
Reading state information...Done
E: Unable to locate package b43-fwcutter

3. Then "sudo apt-get install b43-fwcutter", I got this:

Reading package lists...Done
Building dependency tree
Reading state information...Done
E: Unable to locate package b43-fwcutter

4. With nothing happening, I did Scott's advice. I installed ndiswrapper common and utils + ndisgtk.
5. And then went to System>Administration>Windows Wireless Drivers. Just like before, there's still nothing in there.

6. So I went back to CD, Ubuntu 10.10>pool>main>b>b43-fwcutter and installed the content.
7. I went back to terminal for this: "sudo apt-get install b43-fwcutter" and got this:

Reading package lists...Done
Building dependency tree
Reading state information...Done
b43-fwcutter is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Right now I still am not connected to the internet (there's still that exclamation mark in the wi-fi icon) even though I kept the internet wire inserted in the laptop for the whole time. :(

It doesn't look like you actually connected to the internet with the wire -- that red exclamation point makes me think you were not connected. With the wire in, do you see your ip address for eth0 when you type
ifconfig
Typically the ip address looks something like:
inet addr:192.168.1.110 Bcast:192.168.1.255 Mask:255.255.255.0
R click on the network-manager icon, and select edit connections. Select the wired tab, and select the auto eth0, then click the edit button. Connect automatically should be checked. Look at the ipv4 tab and see that dhcp is checked, and that the "require ipv4 addressing..." is checked. look at the ipv6 and check that the method is ignore.
The wired connection is usually all set up by default. Maybe your router/modem needs to be reset?

Try the firmware-b43-installer package to get the open source firmware which will go into /lib/firmware/b43-open
That should be on your disk and you should not need an internet connection, but if your wired connections do not work, chances are not good for the wireless.

Here`s the ifconfig result with the wire on:

jaime@jaime-Aspire-3680:~$ ifconfig

eth0 Link encap:Ethernet HWaddr 00:1b:24:32:14:a3

          inet6 addr: fe80::21b:24ff:fe32:14a3/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

          RX packets:844 errors:0 dropped:0 overruns:0 frame:0

          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:58279 (58.2 KB) TX bytes:6627 (6.6 KB)

          Interrupt:16

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:288 errors:0 dropped:0 overruns:0 frame:0

          TX packets:288 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:22704 (22.7 KB) TX bytes:22704 (22.7 KB)

Here`s the ifconfig result without the wire on:

jaime@jaime-Aspire-3680:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1b:24:32:14:a3
          inet6 addr: fe80::21b:24ff:fe32:14a3/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:9197 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:634280 (634.2 KB) TX bytes:12099 (12.0 KB)
          Interrupt:16

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:432 errors:0 dropped:0 overruns:0 frame:0
          TX packets:432 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:34224 (34.2 KB) TX bytes:34224 (34.2 jaime@jaime-Aspire-3680:~$ ifconfig

You got an IPV6 address! Unless you explicitly are trying to use IPV6, you should turn it off and use IPV4. Right click on the network-manager icon, edit connections, and for the wired, select the eth0, and click the edit button. Under the Wired tab: The connect automatically box should be checked, MTU set to automatic, your MAC address present, and available to all users at the bottom checked.
Under the ipv4 tab, method is Automatic dhcp, and the require ipv4 addressing box is checked. Under the ipv6 tab, method is ignore. Do the same things for the wireless connections

Yes all of those descriptions are in my connection. Everything you've said in IPV4 is there, and IPV6 is set to ignore. But I still can't connect. There's still that red exclamation mark in the connections icon.

I disabled the Ipv6 as the command in the link said "1" means it's already been disabled. And then I connected it to the internet wire and then i did "ifconfig in the command. This is what came up:

jaime@jaime-Aspire-3680:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1b:24:32:14:a3
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2929 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:185053 (185.0 KB) TX bytes:5814 (5.8 KB)
          Interrupt:16

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:100 errors:0 dropped:0 overruns:0 frame:0
          TX packets:100 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7784 (7.7 KB) TX bytes:7784 (7.7 KB)

I still can't connect to the internet as there's still that same icon in there...

You did get rid of the unwanted ipv6 address! Unfortunately, you did not pick up an ipv4 address. I don't know enough about the network configuration to suggest a reason for that, other than checking the network-manager (R click), edit connections, and select the auto eth0 and edit. Click on the ipv4 settings tab, and ensure the dhcp box is checked and the require ipv4 addressing box is also checked. Maybe you should ask another question about the wired ethernet config, then when that's working, we can continue here on getting the wireless firmware/drivers.

Thank you, Ubfan. I have just asked the question over at this link: https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/151892. Hopefully somebody will be able to help.

Thanks so much!~

Just had a thought, routers have the capability of limiting the number of dhcp leases they pass out, so if all are passed out, you may not be getting an IP from your router even though it is running dhcp. You didn't ever change any router settings did you? The default is not to artificially limit the number of addresses.

Hey Ubfan! You're right! I might have probably messed up the router settings somehow. I re-installed the whole thing and disabled the ipv6 and it finally connected through the wired connection! (sweetest words I've read in Ubuntu so far!).

Anyway I did the updates through "Additional Drivers" and it took a while to finish.

The only thing left for me is to setup the wireless connection. I looked its tab (Wireless Networks) and I didn't see anything in there. I'm kinda hesitant in customizing it too. So yeah...that's one last thing I need to finally finish this thing up.

Erase that. I went back to your previous posts. So basically here's what I did to solve everything.

1. I went to this site: http://www.webupd8.org/2010/05/how-to-disable-ipv6-in-ubuntu-1004.html to disable ipv6.
2. I restarted the computer.
3. I restarted the router itself.
4. Connected the laptop to the internet wire.
5. Went to the Terminal (Ctrl + Alt + T) and typed the command:
sudo apt-get purge b43-fwcutter
sudo apt-get install b43-fwcutter
6. Went to System>Additional Drivers
7. Installed everything in there (it's basically B43 and STA wireless driver)
8. Reset the router again.
9. Waited for a while...

and Voila! Wireless Connection established!!!

Thanks so much, Scott, actionparsnip and most especially Ubfan!!!

Thanks Ubfan, that solved my question.

Yay!

On 12 April 2011 00:23, jxwxnx <email address hidden> wrote:

> Question #150362 on gnome-nettool in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/150362
>
> Status: Open => Solved
>
> jxwxnx confirmed that the question is solved:
> Thanks Ubfan, that solved my question.
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>