Tiny Core Base > CorePlus
WiFi Cannot Scan
eltone:
--- Quote from: Juanito on January 15, 2014, 11:58:04 PM ---
--- 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")?
--- End quote ---
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.
--- Quote ---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"
--- End quote ---
Q: To remove this bloat, 'Apps > Maintenance > Dependencies And Deletions' is the one and only route to delete them?
--- Quote ---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.
--- End quote ---
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.
--- Quote ---The trick is to get them both to reliably connect to my WEP encrypted cell!
--- End quote ---
--- Quote ---Did you try this from the command line rather than using wifi.sh/wicd?
--- End quote ---
CLI has never been successful, only the wicd network-manager has!
--- Quote ---Did you try wicd in tc-5.x?
--- End quote ---
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: ---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:~$
--- End code ---
eltone
eltone:
--- Quote from: Juanito on January 16, 2014, 12:51:06 AM ---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 ---
--- End quote ---
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.
--- Quote from: eltone on January 16, 2014, 09:48:18 PM ---It is not in the tc-5.1 repo, but tried 4.73's wicd in 5.1 that trapped MANY errors!
--- End quote ---
As suggested previously, please try the wicd extension from the 4.x repo with tc-5.x
eltone:
--- Quote from: eltone on January 16, 2014, 10:01:42 PM ---
--- Quote from: Juanito on January 16, 2014, 12:51:06 AM ---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 ---
--- End quote ---
I will give this a try on the CLI once the syntax is clear . . .
--- End quote ---
hi,
This simple CLI indexing appeared to connect, once I made sure ssb and b43 got loaded:
--- Code: ---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:~$
--- End code ---
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:
--- Quote from: Juanito on January 15, 2014, 11:58:04 PM ---
Did you try wicd in tc-5.x?
--- End quote ---
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
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version