try

Thanks to all...here you go all the outputs...

pablo@pablo-laptop:~$ sudo ifconfig wlan0 down
[sudo] password for pablo:
pablo@pablo-laptop:~$ sudo ifconfig wlan0 192.168.2.20
SIOCSIFFLAGS: No such file or directory
pablo@pablo-laptop:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory
pablo@pablo-laptop:~$ sudo iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down

Ok, try to do:

sudo modprobe -r b43

post output.

sydo modprobe b43

post output.

then post output for:

dmesg | tail -n 30

Hi, thanks for the patience and time.

As nothing seems to come out I repeated “sudo modprobe -r b43”, I hope that is fine. I changed “ sydo modprobe b43” for “ sudo modprobe b43” (also no output). I read (although difficult for me) the output for “ dmesg | tail -n 30” and I looked at the website indicated (http://wireless.kernel.org/en/users/...devicefirmware). I did not download anything but suddenly remembered that one day I looked into System > Administration > Hardware drivers and saw a non activated driver called “Broadcom B43 Wireless driver”. I have not activated it just in case but I guess this could be the solution...

There you go the outputs:


pablo@pablo-laptop:~$ sudo modprobe -r b43

[sudo] password for pablo:

pablo@pablo-laptop:~$ sudo modprobe -r b43

pablo@pablo-laptop:~$ sydo modprobe b43

No command 'sydo' found, did you mean:

Command 'syco' from package 'emboss' (universe)

Command 'sudo' from package 'sudo' (main)

Command 'sudo' from package 'sudo-ldap' (universe)

sydo: command not found

pablo@pablo-laptop:~$ sudo modprobe b43

pablo@pablo-laptop:~$

pablo@pablo-laptop:~$ dmesg | tail -n 30

[ 388.761870] eth0: no link during initialization.

[ 388.762594] ADDRCONF(NETDEV_UP): eth0: link is not ready

[ 403.527153] eth0: link up.

[ 403.527968] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

[ 405.956097] b43 ssb0:0: firmware: requesting b43/ucode5.fw

[ 405.965230] b43 ssb0:0: firmware: requesting b43-open/ucode5.fw

[ 405.973474] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found

[ 405.973489] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found

[ 405.973497] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

[ 406.021067] b43 ssb0:0: firmware: requesting b43/ucode5.fw

[ 406.028444] b43 ssb0:0: firmware: requesting b43-open/ucode5.fw

[ 406.042196] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found

[ 406.042209] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found

[ 406.042218] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

[ 416.812052] eth0: no IPv6 routers present

[ 853.045307] b43-pci-bridge 0000:01:00.0: PCI INT A disabled

[ 1234.901158] cfg80211: Calling CRDA to update world regulatory domain

[ 1234.943873] cfg80211: World regulatory domain updated:

[ 1234.943883] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)

[ 1234.943892] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

[ 1234.943900] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)

[ 1234.943907] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)

[ 1234.943915] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

[ 1234.943922] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

[ 1235.020366] b43-pci-bridge 0000:01:00.0: PCI INT A -> Link[LK2E] -> GSI 19 (level, high) -> IRQ 19

[ 1235.020388] b43-pci-bridge 0000:01:00.0: setting latency timer to 64

[ 1235.076161] ssb: Sonics Silicon Backplane found on PCI device 0000:01:00.0

[ 1235.089152] b43-phy0: Broadcom 4311 WLAN found (core revision 10)

[ 1235.161668] phy0: Selected rate control algorithm 'minstrel'

[ 1235.163697] Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]

We have an answer, why you are not happy.

Because:
[ 405.956097] b43 ssb0:0: firmware: requesting b43/ucode5.fw

[ 405.965230] b43 ssb0:0: firmware: requesting b43-open/ucode5.fw

[ 405.973474] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found

[ 405.973489] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found

[ 405.973497] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.


Do what it is suggested. You need to download and install firmware:

[ 405.973497] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

2 members found this post helpful.

Problem solved!

Thank you all very much for the help.

I have installed the b43-fwcutter using the Synaptic Package Manager (at System > Administration). It was there and I just installed it. After it WICD have detected the wireless connections around. I can not prove the connections since all need a password. I will try on open connections and see if it works ok.

First I tried to activate “Broadcom B43 Wireless driver” (at System > Administration > Hardware Drivers) but it did not work. Now I understand why: basically the driver was not there and it needed from the fwcutter to extract the firmware. I think I start to understand this a little. However I did not installed the fwcutter using the Terminal as it is indicated in http://wireless.kernel.org/en/users/..._and_b43legacy because I am not very familiar with the Terminal use. I have the feeling I can screw up the OS very easily if I use it wrong. As explained above I used Synaptic Package Manager.

All the best,

Pablo

Hello,

I am back! The wireless work wells but behaves strangely. It can work for few hours and then disconnect. When I look in the WICD it says “No wireless networks found”. It is like that until perhaps a few hours later or the day after. Do you know what could be the problem? Thanks in advance.

Note: It seems that after restarting the computer works again.

Best,

Pablo