sasa@sunflower:~> /bin/dmesg | grep -n “b43”
415:b43-phy0: Broadcom 4318 WLAN found
447:input: b43-phy0 as /devices/virtual/input/input8
448:b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
449:Registered led device: b43-phy0::tx
450:Registered led device: b43-phy0::rx
451:Registered led device: b43-phy0::radio
452:b43-phy0: Radio hardware status changed to DISABLED
sasa@sunflower:~> /bin/dmesg | grep -n “wlan0”
453:ADDRCONF(NETDEV_UP): wlan0: link is not ready
This is the first point where something is wrong, as far as I can tell. The card is there, the firmware is there, but it fails to activate the link? Not sure if I should post more lines from dmesg?
Here’s more info:
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
No ESSID, though I’ve defined it using YaST (Network Devices/Network Settings recognizes the card but says “Not connected”) and added a connection through the applet (the gear turns and turns, but no connection is made and no error is reported on screen).
Predictably, the scan returns no results:
sasa@sunflower:~> /usr/sbin/iwlist wlan0 scan
wlan0 No scan results
Yes - there is a switch/button for turning wireless on/off on the laptop. The problem is nothing happens when I press it Or almost nothing - the HDD light flickers a bit and that’s it. As if it tries to start/read something, but fails…
The wireless router is up & running - I can connect to it (at to the internet) from the other computer.
Switch it on with the on/off button. When SuSE starts it should then see that the device can be activated for use. Basically,the on/off switch is there to provide power to the device,much like switching on your tv before using it ( unless it is on stand-by )
It’s a button - it doesn’t have the ON (or OFF) position exactly, and pressing it does nothing until the computer/OS is up and running. As I said earlier, if I press it when it’s already up, then the HDD LED flickers for a moment, but the Wireless LED stays off at all times
It worked fine under WinXP - the wireless LED stayed off during booting; after logging in I would press the button and it would turn the Wireless LED on.
Am I looking at incorrect driver/firmware? Is ndiswrapper my only way out?
Go to terminal and go to the extracted folder and digit:
sudo modprobe fsaa1655g
Now for some Opensuse users a problem will occur. Even with “sudo” the modprobe command can’t be used. To solve this inconvenient you can add modprobe as a command that can run with sudo, but It’s not always a good thing change the safety settings of opensuse. The easyest way is to give the command:
then insert the root password and give
now the wifi would works fine!
I’ve tried also to use the command echo 1 > /proc/fsaa1655g/radio to turn on the wifi card and echo 0 > /proc/fsaa1655g/radio
to turn it off but it doesn’t work. If you have the same problem you can solve it doing:
*to turn on the card:
to turn it off:
modprobe -r fsaa1655g
Maybe some linux expert would say that It’s not the best way, but It works, so for me It’s an excellent solution. Notice that with those commands you can turn the card on/off “on demand”.