SUCCESS install the wireless for Acer Aspire 5101 laptop

[zolly]

Using "lspci" I see that I have
06:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

To make it works, I follow the steps:

1) System->Administration->Synaptic Package Manager I install "bcm43xx-fwcutter" and "wlassistant"
2) sudo /usr/share/bcm43xx-fwcutter/install_bcm43xx_firmware.sh
3) System->Administration->Windows Wireless Drivers->Install New Driver-> I choose "bcmwl5.inf" from CD with drivers which comes with my laptop
4) sudo modprobe bcm43xx
5) sudo wlassistant (this is a program which scan the available wireless networks). If it founds networks, then your wireless card works.
6) All you have to do is to configure your wireless card (System->Administration->Networking)
.

[woopud]

You think this will work for the Broadcom 4306 ?
I've tried setting it up according to Mint Linux instructions but no success so far. If I would use your instructions is it going to mess up what I already did ?

Bert

[zolly]

Use "lspci" to see if it is in category BCM43xx (from your post, it is). If you have no success until now, what do you have to lose ?
It works for me: I reinstall the Linux Mint Bea and I follow the steps and it works (just to be sure that what I post is 100% correct).

[essetee]

if you load bcm43xx don't load ndiswrapper.

sudo rmmod ndiswrapper
sudo rmmod bcm43xx

Now do dmesg

Look at the last lines.

Now do sudo modprobe bcm43xx

then again dmesg

Possible now that you see that he needs the firmware.

To install the firmware

sudo apt-get install bcm43xx-fwcutter

Then use de xp drivers from windows xp

There you find a file bcmxx.sys

Copy that file to your home dir

then

sudo bcm43xx-fwcutter bcmxx.sys -w /lib/firmware

This will copy the needed firmware to /lib/firmware

Then do sudo rmmod bcm43xx

Then again sudo modprobe bcm43xx

Now look at the output of dmesg

When all works fine :

sudo dhclient eth0

[woopud]

Well, now I used instruction from 3 different posts but it's working with wlassistant, but it doesn't show up under network manager? How do I start wlassistant ? Do I have to open a termianl everytime or can I get some kind of shortcut on my panel ?

Bert

[zolly]

You can use: "sudo wlassistant" (from Terminal) because it needs the root account to run. It doesn't work with Application->Internet->Wireless Assistant.

You can do the following steps if you want to use the menu above:
1) System->Preferences->Menu Layout
2) click Menus: Internet (left panel)
3) right-click "Wireless Assistant" -> Properties ->
edit the field Command: gksu wlassistant
[]Run Command in a terminal = should be disable
4) click "close"
5) click "close"
Now you can use the menu. The Terminal is not necessary anymore.

If you look carefully, the steps are the same, essetee's post is good for a user guide, my post described exactly the steps I have done to use the wireless for my laptop.
Our purpose is to help other people to use linux and we are happy if the results are good.

[woopud]

Thank you guys, finaly got a usefull Linux on my laptop !

Bert

[essetee]

Tip : if you have the firmware for your network card, keep it on a usb stick.
When reinstalling a linux dist, you can put directly the firmware in /lib/firmware, even with a live cd.

[ecd]

Hello,
I'm having the same problems as 'Bert'. I've read zolly's reply...however, I don't understand the: I install "bcm43xx-fwcutter" part. I've downloaded and installed the Wireless assistant, how do I install (download too?) bcm43xx-fwcutter?

My card is also the same as Berts...4306.

I'd really appreciate your help.

Apologies for butting into this post. But I really am stuck.

regards,
Pete

[zolly]

From menu: System->Administration->click the "Synaptic Package Manager". Search for the package "bcm43xx-fwcutter" then right click to it and from the menu that appears, choose "Install" then click "Apply".
When the installation is finished, open the "Terminal" from Application->Accesories->Terminal and write "sudo /usr/share/bcm43xx-fwcutter/install_bcm43xx_firmware.sh" (without "").
Then follow the rest of the steps ...

[ecd]

Hi Zolly,
thanks for the response, however...I found the file you talk about. But when I right-click it...it only says Mark for installation. You're dealing with a grade A dummy here my friend!
Hi Zolly...I found it...a tick marked Apply...Doh!
Sorry,
Pete

[ecd]

This is what appeared when it finished:
peter@EZ-Buddie:~$ sudo /usr/share/bcm43xx-fwcutter/install_bcm43xx_firmware.sh
--15:12:26-- http://svit.epfl.ch/stuff/wl_apsta.o
=> `wl_apsta.o'
Resolving svit.epfl.ch... 128.178.192.9
Connecting to svit.epfl.ch|128.178.192.9|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 652,866 (638K) [text/plain]

100%[====================================>] 652,866 46.98K/s ETA 00:00

15:12:38 (53.53 KB/s) - `wl_apsta.o' saved [652866/652866]

bcm43xx-fwcutter can cut the firmware out of wl_apsta.o

filename : wl_apsta.o
version : 3.130.20.0
MD5 : e08665c5c5b66beb9c3b2dd54aa80cb3

extracting bcm43xx_microcode2.fw ...
extracting bcm43xx_microcode4.fw ...
extracting bcm43xx_microcode5.fw ...
extracting bcm43xx_microcode11.fw ...
*****: Sorry, it's not possible to extract "bcm43xx_microcode13.fw".
*****: Extracting firmware from an old driver is bad. Choose a more recent one.
*****: Luckily bcm43xx driver doesn't include microcode11 uploads at the moment.
*****: But this can be added in the future...
extracting bcm43xx_pcm4.fw ...
extracting bcm43xx_pcm5.fw ...
extracting bcm43xx_initval01.fw ...
extracting bcm43xx_initval02.fw ...
extracting bcm43xx_initval03.fw ...
extracting bcm43xx_initval04.fw ...
extracting bcm43xx_initval05.fw ...
extracting bcm43xx_initval06.fw ...
extracting bcm43xx_initval07.fw ...
extracting bcm43xx_initval08.fw ...
extracting bcm43xx_initval09.fw ...
extracting bcm43xx_initval10.fw ...
peter@EZ-Buddie:~$


Am I moving in the right direction?

[essetee]

Normally you have the right drivers for your networkcard. When you buy a networkcard, normally the drivers for windows XP are included. When you look to the drivers, you wil see a file called xxxxxx.sys.

You need that file to extract the firmware.

When you found that file do :

bcm43xx-fwcutter name_file.sys -w /path/to/extract


When you run bcm43xx-fwcutter without any options you get :

bcm43xx-fwcutter version 20060501

Usage: bcm43xx-fwcutter [OPTION] [driver.sys]
-l|--list List supported driver versions
-i|--identify Only identify the driver file (don't extract)
-w|--target-dir DIR Extract and write firmware to DIR
-p|--postfix ".FOO" Postfix for firmware filenames (.FOO.fw)
-v|--version Print bcm43xx-fwcutter version
-h|--help Print this help

Example: bcm43xx-fwcutter bcmwl5.sys
to extract the firmware blobs from bcmwl5.sys

It's not so easy to understand.

man bcm43xx-fwcutter gives you also more information.

[ecd]

Thank you for the help, however...my brain has started to hurt! So, I'll let it cool down and have another try tomorrow.

I really appreciate the help though.

Regards,
Pete

[zolly]

This is what appeared when it finished:
peter@EZ-Buddie:~$ sudo /usr/share/bcm43xx-fwcutter/install_bcm43xx_firmware.sh
--15:12:26-- http://svit.epfl.ch/stuff/wl_apsta.o
=> `wl_apsta.o'
Resolving svit.epfl.ch... 128.178.192.9
Connecting to svit.epfl.ch|128.178.192.9|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 652,866 (638K) [text/plain]

100%[====================================>] 652,866 46.98K/s ETA 00:00

15:12:38 (53.53 KB/s) - `wl_apsta.o' saved [652866/652866]

bcm43xx-fwcutter can cut the firmware out of wl_apsta.o

filename : wl_apsta.o
version : 3.130.20.0
MD5 : e08665c5c5b66beb9c3b2dd54aa80cb3

extracting bcm43xx_microcode2.fw ...
extracting bcm43xx_microcode4.fw ...
extracting bcm43xx_microcode5.fw ...
extracting bcm43xx_microcode11.fw ...
*****: Sorry, it's not possible to extract "bcm43xx_microcode13.fw".
*****: Extracting firmware from an old driver is bad. Choose a more recent one.
*****: Luckily bcm43xx driver doesn't include microcode11 uploads at the moment.
*****: But this can be added in the future...
extracting bcm43xx_pcm4.fw ...
extracting bcm43xx_pcm5.fw ...
extracting bcm43xx_initval01.fw ...
extracting bcm43xx_initval02.fw ...
extracting bcm43xx_initval03.fw ...
extracting bcm43xx_initval04.fw ...
extracting bcm43xx_initval05.fw ...
extracting bcm43xx_initval06.fw ...
extracting bcm43xx_initval07.fw ...
extracting bcm43xx_initval08.fw ...
extracting bcm43xx_initval09.fw ...
extracting bcm43xx_initval10.fw ...
peter@EZ-Buddie:~$


Am I moving in the right direction?

It is OK. I had the same messages.
Now, do the rest steps, and finally verify with wlassistant if the wireless works.

[ecd]

For 2 days now I've followed the above instructions and got absolutely nowhere. I have the bcmwl5.sys sitting on my Desktop and non of the instructions above appear to get the thing installed! All I get back is rubbish I really don't understand.

Sorry for being a pain but can anyone give a dummy some clear instructions on how to:

1) Check the Wireless PCI card is ACTUALLY operating or, at the very least show that it has been recognised by this PC?
2) How to install the .sys file sitting on my Desktop?

Failing that, I wait another 18 months before trying Linux out again.

Regards,A strange idiot-boy

[scorp123]

1) Check the Wireless PCI card is ACTUALLY operating or, at the very least show that it has been recognised by this PC?
2) How to install the .sys file sitting on my Desktop?

About 1.)
Please give me the output of this shell command (you have to open a terminal to do this!):

Code: Select all

sudo lspci -n

This will spit out some columns and numbers. Please copy and paste that stuff and put it into a reply here. I will feed that output into a web form I happen to know and this will tell me if your card is even supported under Linux, and if so, which kernel module (= "driver" in Linux speak) needs to be used.

About 2.)
Sounds to me like you were trying to install a device driver for Windows?? Linux per default doesn't know *.sys files. Were you messing around with ndiswrapper? Please can you be specific and tell us what precisely step-by-step you were doing?

[ecd]

Hello Scorp123,
Answer to your first request:
00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

I'm not trying to use Ndiswrapper.

I'm getting confused with what appears to be conflicting instructions...see above posts. One says use the Windows wireless drivers i.e. bcmwl5.inf But I can't find that on the CD that came with the PCI card. I can find the bcmwl5.sys file but then this shouldn't be the one I use?

Just stuck with a PCI card in the PC and can go no further, Everything is fine by wire...but total disaster without!

I'm leaving it for now...absolutely shagged out!

I'll have another go tomorrow, if you can make head or tail of what my problem is...apart from being a brit!

Regards,
Pete.

PS: there's actually dozens of 'Driver's and various other .dll/.ini/...blah, blah, blah on the CD! It's just totally F*****g my head in.

[scorp123]

Answer to your first request:
00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

Well ... not exactly what I asked for but never mind. Did you use the forum search? Several people here got their bcm4xxx devices to work.

I'm getting confused with what appears to be conflicting instructions...see above posts. One says use the Windows wireless drivers i.e. bcmwl5.inf

Please be more specific and use the quote functions. Which step did you try to reproduce and where did you get stuck, or what precisely is confusing you?

[ecd]

New day, new try.

I'm trying to install the driver for a Broadcom chipset, the BCM4306. I follow the link via Mint wi-fi and it comes back with "No such file or directory". I look for the "bcmwl5.inf" file on the CD that came with the PCI card...cannot find such file.

Up to a point zolly's instructions worked fine...thank you zolly. However, as there doesn't appear to be a "bcmwl5.inf" file on the CD that came with the PCI card, I'm now..and have been for three days, very stuck.

My confusion seems to be; that I came in halfway through this post and perhaps I should have started a whole new one to myself? But, I thought what I was reading would help me...wrong.

So, I don't know if I should be using bcm43xx-fwcutter or, ndiswrapper to get the card to work. It may be that I have instructions for both and I'm trying to do both at the same time? When it should be one or the other?

I notice that in another post, someone asking for suggestions for the next release, someone has suggested inbuilt support for Broadcom and Intel chipsets. I'll second that. When I asked (on another forum) which card to use for wireless on Linux, I was told the "Buffalo Wireless-G 125 PCI" NOT USB.

I think someone may have been pulling my plonk, as this is the LEAST supported card for Linux! Yes, yes, I know, I should have come to these forums and asked...but I don't want to become a forum tart. So I tried to get the thing going. Failing miserably.

I really do appreciate everything that you guys (and guyesses) are doing to help. But I do get sick to the pit of my stomach, after three days and getting absolutely nowhere.

For now? I think I'll leave Linux, but keep an eye open for a Mint version that 'appears' to support this chip 'out-of-the-box. I was so close to having a fully working set up too with Mint (first time EVER in over five years trying with Linux). Though to be fair...My PC works wonderfully, if I use an ethernet cable...but that's a health and safety hazard in this house.

I have nothing but admiration for those that can 'work' Linux. Myself? I see it as a bit like Jazz music? You know you should like it, you hear certain refrains/riffs that really appeal. But then you hear some free-form jazz and think...what's all that about? So for now, it's back to the Spice-Girl equivalent (Windoze) Bugger.

Regards all,
Pete.

PS: Please don't post telling me...I know it's my own incompetence! And, that of hardware manufacturers not supporting Linux. I know Linux IS NOT the problem. I do hold Linux very high and wish it EVERY success.