Tiny Core Base > CorePlus

WiFi Cannot Scan

<< < (11/30) > >>

eltone:

--- Quote from: Juanito on January 15, 2014, 04:01:48 AM ---You would need to pm the maintainer and request an update, but I'm not sure how this extension is going to help?

--- End quote ---

Juanito,

Extension's complete, cutter, firmware & installer:


--- Quote ---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

--- End quote ---
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:

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

--- End quote ---

hi,

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


--- Code: ---
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:~$

--- End code ---



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

--- Quote ---


/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



--- End quote ---

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:

--- Quote from: eltone on January 15, 2014, 09:29:24 PM ---Whats interesting is that both wifi & wicd have NO problem enabling the hardware LED or finding neighborhood access points.

--- End quote ---
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.


--- Quote ---The trick is to get them both to reliably connect to my WEP encrypted cell!
--- End quote ---
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: ---$ 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
--- End code ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version