WiFi Cannot Scan

[eltone]

b43-fwcutter updated to the latest version.

To cut your own firmware:

Code: [Select]

$ wget -c http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
$ tar xf broadcom-wl-5.100.138.tar.bz2
$ sudo mkdir -p /usr/local/lib/firmware
$ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.138/linux/wl_apsta.o

hi,
TCP 4.73 LiveUSB trapped this error while attempting to cut firmware, using the 5.1 protocol:

Code: [Select]

tc@box:~/b43fw$ tar xf broadcom-wl-5.100.138.tar.bz2
tc@box:~/b43fw$ sudo mkdir -p /usr/local/lib/firmware
tc@box:~/b43fw$ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.1
38/linux/wl_apsta.o
Sorry, the input file is either wrong or not supported by b43-fwcutter.
This file has an unknown MD5sum e1b05e268bcdbfef3560c28fc161f30e.
tc@box:~/b43fw$

Q: Why would TCP 5.1 overlook this obvious problem TCP 4.73 reports?
eltone

:

[Juanito]

tc-4.x uses an earlier version of the firmware cutter, maybe this is the reason for the error?

[Juanito]

Once the WLAN framework is stable, I'd be happy to do further beta  . . .

As mentioned earlier, due to the fact that a lot of wifi hardware is closed source, getting wifi working under linux is often a matter of trial and error to find a working driver and/or firmware.

The above being said, yours is the first case I've seen where wifi is disabled in software on boot.

Wifi works in tc-5.x for me and others with broadcom hardware and I believe it will work for you once we find the right method.

Given that you reported earlier that the wifi extension displayed several wireless access points, you cannot be that far from success.

I suggest you make an extension of the cut firmware and try the following:

* remove any "blacklist" boot codes
* remove any firmware/wireless extensions from "onboot"
* reboot
* load the firmware extension
* load the wireless-KERNEL extension
* load the rfkill and wifi extensions
* unblock the wifi software switch with rfkill
* run the wifi.sh script

..and let us know how you get on.

[eltone]

I suggest you make an extension of the cut firmware

Dear Juanito:

Better yet, have your TCP 5.1 team recompile this extension:

http://repo.tinycorelinux.net/4.x/x86/tcz/b43-tools.tcz

Once completed, I hope it's all down-hill \
                                                                 \.
eltone

[Juanito]

You would need to pm the maintainer and request an update, but I'm not sure how this extension is going to help?

[eltone]

You would need to pm the maintainer and request an update, but I'm not sure how this extension is going to help?

Juanito,

Extension's complete, cutter, firmware & installer:

Title:          b43-tools.tcz
Description:    Tools for the Broadcom 43xx series WLAN chip.
Version:        20110514
Author:         Michael Buesch and others
Original-site:  bu3sch.de/gitweb?p=b43-tools.git;a=summary
Copying-policy: GPL2
Size:      76K
Extension_by:   Jason W
Tags:       Tools Broadcom 43xx series WLAN chip.
Comments:       This extension is PPI compatible.
      This extension also contains b43-fwcutter that is also
      in the b43-fwcutter.tcz extension.
Change-log:     --------
           
Current:   2011/05/14 First version 20110514

Enough said.
eltone

[Juanito]

The version of b43-fwcutter in this extension is out of date and superseded by the latest version in the 5.x repo.

The rest of the tools in this extension seem to be (I may be mistaken) intended for developers to aid in reverse engineering and related tasks.

[eltone]

author=Juanito link=topic=16474.msg98195#msg98195 date=1389670198]
You could test wicd in tc-5.x and let us know if it works..

hi,

Trace w/wicd on TCP 4.73 at the point where 5.1 fails access point connection:

Code: [Select]


tc@box:~$ dmesg
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
ieee80211 phy0: Selected rate control algorithm 'pid'
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PMNL, Firmware-ID: FW13 ]
powernow-k8: Found 1 AMD Turion(tm) 64 Mobile Technology ML-32 (1 cpu cores) (ve       rsion 2.20.00)
powernow-k8: fid 0xa (1800 MHz), vid 0x4
powernow-k8: fid 0x8 (1600 MHz), vid 0x6
powernow-k8: fid 0x0 (800 MHz), vid 0x16
8139too 0000:06:06.0: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
8139too 0000:06:06.0: eth0: link down
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: authenticate with 00:21:1e:57:dc:60 (try 1)
wlan0: authenticated
wlan0: associate with 00:21:1e:57:dc:60 (try 1)
wlan0: RX AssocResp from 00:21:1e:57:dc:60 (capab=0x451 status=0 aid=1)
wlan0: associated
wlan0: deauthenticating from 00:21:1e:57:dc:60 by local choice (reason=3)
cfg80211: Calling CRDA to update world regulatory domain
tc@box:~$



Files that were altered by wicd setup, please confirm accuracy:

/opt/.filetool.lst:
opt
home
opt/eth0.sh
usr/local/etc/wicd
var/lib/wicd/configurations

/opt/bootlocal.sh:
#!/bin/sh
# put other system startup commands here
/opt/eth0.sh &
/usr/local/etc/init.d/dbus restart
/usr/local/etc/init.d/wicd start


/mnt/sdb1/tce/onboot.lst:
Xvesa.tcz
Xlibs.tcz
Xprogs.tcz
wbar.tcz
fluxbox.tcz
wifi.tcz
iw.tcz
pci-utils.tcz
ndiswrapper.tcz
firmware.tcz
firmware-ipw2100.tcz
firmware-ipw2200.tcz
firmware-iwlwifi.tcz
firmware-libertas.tcz
firmware-openfwwf.tcz
firmware-wimax.tcz
firmware-zd1211.tcz
tc-install.tcz
b43-tools.tcz
wicd.tcz

Whats interesting is that both wifi & wicd have NO problem enabling the hardware LED or finding neighborhood access points.  The trick is to get them both to reliably connect to my WEP encrypted cell!

eltone
PS. Posted w/TCP 4.73 LiveUSB/wicd

[Juanito]

Whats interesting is that both wifi & wicd have NO problem enabling the hardware LED or finding neighborhood access points.

Are you using rfkill to unblock your wifi hardware (ref "Soft blocked: yes")?

iw.tcz, ndiswrapper.tcz, firmware-ipw2100.tcz, firmware-ipw2200.tcz, firmware-iwlwifi.tcz, firmware-libertas.tcz, firmware-wimax.tcz, firmware-zd1211.tcz and b43-tools.tcz are not required "onboot"

As per "Hardware crypto acceleration not supported by firmware" from dmesg, you might be better off using the cut oem firmware rather than the firmware/firmware-openfwwf extensions.

The trick is to get them both to reliably connect to my WEP encrypted cell!

Did you try this from the command line rather than using wifi.sh/wicd?

Did you try wicd in tc-5.x?

[Juanito]

I looked back to when I used to have broadcom wifi hardware that worked with b43 and a wap that used wep and this worked for me:

Code: [Select]

$ tce-load -i b43_firmware [oem cut firmware]
$ tce-load -i wireless_tools
[at this point you would need to load rfkill and use it to unblock your hardware]
$ sudo iwconfig wlan0 essid "342rju1656"
$ sudo iwconfig wlan0 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid

[eltone]

Whats interesting is that both wifi & wicd have NO problem enabling the hardware LED or finding neighborhood access points.

Are you using rfkill to unblock your wifi hardware (ref "Soft blocked: yes")?

hi,
This evening, to turn on the WLAN LED w/wicd, I tried 'rfkill unblock wifi' first, after wicd did not.  Then I decided to click wifi in wbar, which got it to turn on and immediately closed wifi.

iw.tcz, ndiswrapper.tcz, firmware-ipw2100.tcz, firmware-ipw2200.tcz, firmware-iwlwifi.tcz, firmware-libertas.tcz, firmware-wimax.tcz, firmware-zd1211.tcz and b43-tools.tcz are not required "onboot"

Q: To remove this bloat, 'Apps > Maintenance > Dependencies And Deletions' is the one and only route to delete them?

As per "Hardware crypto acceleration not supported by firmware" from dmesg, you might be better off using the cut oem firmware rather than the firmware/firmware-openfwwf extensions.

I'm using TCP 4.73 LiveUSB, the b43 driver w/wicd to post this note.  The original firmware  install settings have not been altered and there is no need for b43-fwcutter, as prescribed for 5.1.

The trick is to get them both to reliably connect to my WEP encrypted cell!

Did you try this from the command line rather than using wifi.sh/wicd?

CLI has never been successful, only the wicd network-manager has!

Did you try wicd in tc-5.x?

It is not in the tc-5.1 repo, but tried  4.73's wicd in 5.1 that trapped MANY errors!

Todays dmesg showing a functional b43/wicd:

Code: [Select]

tc@box:~$ dmesg
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
ieee80211 phy0: Selected rate control algorithm 'pid'
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PMNL, Firmware-ID: FW13 ]
8139too 0000:06:06.0: eth0: link down
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: authenticate with 00:21:1e:57:dc:60 (try 1)
wlan0: authenticated
wlan0: associate with 00:21:1e:57:dc:60 (try 1)
wlan0: RX AssocResp from 00:21:1e:57:dc:60 (capab=0x451 status=0 aid=1)
wlan0: associated
wlan0: deauthenticating from 00:21:1e:57:dc:60 by local choice (reason=3)
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: authenticate with 00:21:1e:57:dc:60 (try 1)
wlan0: authenticated
wlan0: associate with 00:21:1e:57:dc:60 (try 1)
wlan0: RX AssocResp from 00:21:1e:57:dc:60 (capab=0x451 status=0 aid=1)
wlan0: associated
wlan0: deauthenticating from 00:21:1e:57:dc:60 by local choice (reason=3)
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 92:aa:9a:e9:10:81
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 5a:14:db:cc:d9:ae
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 7a:74:ca:f7:27:2e
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: authenticate with 00:21:1e:57:dc:60 (try 1)
wlan0: authenticated
wlan0: associate with 00:21:1e:57:dc:60 (try 1)
wlan0: RX AssocResp from 00:21:1e:57:dc:60 (capab=0x451 status=0 aid=1)
wlan0: associated
tc@box:~$

eltone

[eltone]

I looked back to when I used to have broadcom wifi hardware that worked with b43 and a wap that used wep and this worked for me:

Code: [Select]

$ tce-load -i b43_firmware [oem cut firmware]
$ tce-load -i wireless_tools
[at this point you would need to load rfkill and use it to unblock your hardware]
$ sudo iwconfig wlan0 essid "342rju1656"
$ sudo iwconfig wlan0 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid


Hey Juanito!
I think 'sudo modprobe -a b43' can replace the first two lines for 4.73.

Q: How would the 10 digit WEP key '6,7,8,9,a,b,c,d,e,f' be successfully entered in line four?
I will give this a try on the CLI once the syntax is clear in my head.

eltone

[Juanito]

my troubleshooting suggestions assume that no firmware/wireless extensions are loaded on boot - I was also assuming that you were trying to get things working on tc-5.x

No, "sudo modprobe -a b43" cannot replace the first two lines - these two lines load the firmware for your hardware and then load the extension that contains the b43 module. Normally the b43 module should load automatically, but it would be good to check after "tce-load -i wireless_tools" that the b43 module is loaded and, if not, use "sudo modprobe b43" to load it.

I don't know how you would enter the WEP key '6,7,8,9,a,b,c,d,e,f' - maybe it would be a good idea to take a look at your wap browser admin page to see if there is a 26 digit code associated with it and, if so, use that.

It is not in the tc-5.1 repo, but tried  4.73's wicd in 5.1 that trapped MANY errors!

As suggested previously, please try the wicd extension from the 4.x repo with tc-5.x

[eltone]

I looked back to when I used to have broadcom wifi hardware that worked with b43 and a wap that used wep and this worked for me:

Code: [Select]

$ tce-load -i b43_firmware [oem cut firmware]
$ tce-load -i wireless_tools
[at this point you would need to load rfkill and use it to unblock your hardware]
$ sudo iwconfig wlan0 essid "342rju1656"
$ sudo iwconfig wlan0 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid


I will give this a try on the CLI once the syntax is clear . . .

hi,
This simple CLI indexing appeared to connect, once I made sure ssb and b43 got loaded:

Code: [Select]

tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
Sending select for 192.168.0.64...
Lease of 192.168.0.64 obtained, lease time 86400
deleting routers
SIOCDELRT: No such process
adding dns 192.168.0.1
tc@box:~$

I had to launch the browser and note that the home page timed out, before learning this CLI indexing failed to connect to router.  Also, the IP & dns address'  looks syspicious.

When using wicd, static addresses are used.  I have seen this anomaly with this particular dns address before and suspect that is the problem here.
eltone

[eltone]

Did you try wicd in tc-5.x?

hi,

Now that wicd.tcz has completed the burn-in phase on tc-4.73, it will be installed on tc-5.10 next go-around:

http://repo.tinycorelinux.net/4.x/x86/tcz/wicd.tcz

Q: Shouldn't it be recompiled first?

eltone