ACER ASPIRE 5003WLMI BROADCOM WIRELESS.

Dear all,
I have just installed OpenSUSE 12.1 in my ACER ASPIRE 5003WLMI LAPTOP. Everything is running Ok, except the Broadcom Wireless.
I have installed the drivers through Yast, “b43-fwcutter” and also tried to follow the instructions provided on b43 - Linux Wireless ; but nothing is able to make it get turned on.
The PCI device is recognized as b43 driver command “lspci -vnn | grep 14e4”. Prior moving to OpenSUSE 12.1, I was using Debian 6.0, and the instructions provided by b43 - Linux Wireless were able to make it work, but not now.

Best Regards, J.

On 11/25/2011 10:56 AM, jaymeoliveirajr wrote:
>
> Dear all,
> I have just installed OpenSUSE 12.1 in my ACER ASPIRE 5003WLMI
> LAPTOP. Everything is running Ok, except the Broadcom Wireless.
> I have installed the drivers through Yast, “b43-fwcutter” and also
> tried to follow the instructions provided on ‘b43 - Linux Wireless’
> (http://www.linuxwireless.org/en/users/Drivers/b43?highlight=(b43))
> ; but nothing is able to make it get turned on.
> The PCI device is recognized as b43 driver command “lspci -vnn |
> grep 14e4”. Prior moving to OpenSUSE 12.1, I was using Debian 6.0, and
> the instructions provided by ‘b43 - Linux Wireless’
> (http://www.linuxwireless.org/en/users/Drivers/b43?highlight=(b43))
> were able to make it work, but not now.

PLEASE DO NOT SHOUT IN YOUR SUBJECT. I find all caps very offensive.

First of all, b43-fwcutter has nothing to do with a driver. It installs the
firmware. The driver is built into the kernel.

With openSUSE, there is no need to use any instructions from ‘b43 - Linux
Wireless’. Once you install the ‘b43-fwcutter’ package, you need to run the command


sudo /usr/sbin/install_b43_firmware

This step is necessary because Broadcom does not permit anyone from
redistributing their firmware - this is a legal way to get around that restriction.

After the above command finishes, you should make sure that your wireless switch
is on, and then scan for your AP with


sudo /usr/sbin/iwlist scan

Many thanks for your help.
I am truly sorry about having used All Caps. I did not meant to be offensive.

The first command only worked with a little modification, such as:
sudo /usr/sbin/install_bcm43xx_firmware

The installation was completed successfully.

But, unfortunately the Wireless does not turn on. If you press the button that should get it turned on, it simply does not work.

After running the second command just like you mentioned, I did got the answers as follows:
lo Interface does not support scanning.
eth0 Interface does not support scanning.
wlan0 Interface does not support scanning : Network is down.
br0 Interface does not support scanning.

Any idea to make the Wireless get turned on?

Best Regards, J.

On 11/26/2011 03:36 PM, jaymeoliveirajr wrote:
>
> Many thanks for your help.
> I am truly sorry about having used All Caps. I did not meant to be
> offensive.
>
> The first command only worked with a little modification, such as:
> sudo /usr/sbin/install_bcm43xx_firmware
>
> The installation was completed successfully.
>
> But, unfortunately the Wireless does not turn on. If you press the
> button that should get it turned on, it simply does not work.

Do you mean the light does not change, or what? Saying “it simply does not work”
is not very specific.

> After running the second command just like you mentioned, I did got the
> answers as follows:
> lo Interface does not support scanning.
> eth0 Interface does not support scanning.
> wlan0 Interface does not support scanning : Network is down.
> br0 Interface does not support scanning.
>
> Any idea to make the Wireless get turned on?

Are you running NetworkManager or ifup? If the latter, does it scan after ‘sudo
/sbin/ifup wlan0’?

If you are using NetworkManager, you need to install the ‘rfkill’ package and
report the output of ‘/usr/sbin/rfkill list’.

I have tried with both. Network Manager and ifup.
But unfortunately, no one turns the wireless on, and it also does not connects to the configured wireless network (Yast/Network Devices).

“rfkill list” reports:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no

On 11/29/2011 01:16 PM, jaymeoliveirajr wrote:
>
> “rfkill list” reports:
> 0: phy0: Wireless LAN
> Soft blocked: yes
> Hard blocked: no

I no longer answer people that shout their subject. Good luck.

Fedora 16 is working fine. No need to run any kind of config.
Debian 6.0 is working fine.
But, I will keep trying to find a solution …
If any body knows one do let me know.