WiFi Cannot Scan

[tinypoodle]

1. Nothing can be said about that trace without seeing the preceding lines.
2. I suggest you add boot code

Code: [Select]

syslog and then post or attach /var/log/messages
3. There is no sense in running udhcpc without first being associated with AP which could be checked e.g. with

Code: [Select]

iwconfig

[eltone]

1. Nothing can be said about that trace without seeing the preceding lines.
2. I suggest you add boot code

Code: [Select]

syslog and then post or attach /var/log/messages

syslog attached . . .

eltone

[eltone]

3. There is no sense in running udhcpc without first being associated with AP which could be checked e.g. with

Code: [Select]

iwconfig

iwconfig:

Code: [Select]

tc@box:~$ tce-load -i firmware-openfwwf
/etc/sysconfig/tcedir/optional/firmware-openfwwf.tcz: OK
tc@box:~$ tce-load -i wireless_tools
wireless-3.8.13-tinycore.tcz: OK
libiw.tcz: OK
wireless_tools.tcz: OK
tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo iwconfig
ip_vti0   no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"eltonenetwork" 
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:6789-abcd-ef
          Power Management:on
         
dummy0    no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

tunl0     no wireless extensions.

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...
No lease, forking to background
tc@box:~$

eltone

[tinypoodle]

syslog attached . . .

It appears like the kernel spits out a warning and call trace when udhcpc is executed while expected firmware is missing.

Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

If I were you I would try to pursue the path of above instructions.

[tinypoodle]

Access Point: Not-Associated

Exactly what I meant

Tx-Power=0 dBm   

That looks wrong, possibly caused by missing firmware.

[eltone]

Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

If I were you I would try to pursue the path of above instructions.

Hey tinypoodle!

Those instructions have nothing etched-in-stone for TCP 5.1.

Dry run:

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
$ tce-load -i b43-fwcutter
$ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.138/linux/wl_apsta.o


No firmware cutting was required w/TCP 4.73.  'b43-tools' had a script to install it automatically.
eltone

[eltone]

Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

If I were you I would try to pursue the path of above instructions.

Dear TCP 5.x Team:
WLAN is functional:

Code: [Select]

[ctc@box:~/b43fw$ sudo mkdir -p /usr/local/lib/firmware
tc@box:~/b43fw$ tce-load -i b43-fwcutter
/etc/sysconfig/tcedir/optional/b43-fwcutter.tcz: OK
tc@box:~/b43fw$ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.1
This file is recognised as:
  filename   :  wl_apsta.o
  version    :  666.2
  MD5        :  e1b05e268bcdbfef3560c28fc161f30e
Extracting b43/lp0initvals14.fw
Extracting b43/lcn0bsinitvals25.fw
Extracting b43/n0bsinitvals25.fw
Extracting b43/n0bsinitvals17.fw
Extracting b43/ucode17_mimo.fw
Extracting b43/ucode16_lp.fw
Extracting b43/sslpn1initvals27.fw
Extracting b43/lp2bsinitvals19.fw
Extracting b43/sslpn3bsinitvals21.fw
Extracting b43/ucode16_sslpn.fw
  ucode time:     01:15:07
Extracting b43/ucode25_lcn.fw
Extracting b43/ucode21_sslpn.fw
Extracting b43/lp0bsinitvals14.fw
Extracting b43/b0g0initvals9.fw
Extracting b43/ucode20_sslpn.fw
Extracting b43/a0g1bsinitvals9.fw
Extracting b43/lp1initvals20.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/lp2initvals19.fw
Extracting b43/n2bsinitvals19.fw
Extracting b43/sslpn4bsinitvals22.fw
Extracting b43/ucode16_sslpn_nobt.fw
  ucode date:     2011-02-23
Extracting b43/n1bsinitvals20.fw
Extracting b43/n1initvals20.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/ucode22_sslpn.fw
Extracting b43/b0g0initvals13.fw
Extracting b43/ht0initvals26.fw
Extracting b43/ucode33_lcn40.fw
Extracting b43/sslpn1bsinitvals20.fw
Extracting b43/lcn400bsinitvals33.fw
Extracting b43/ucode14.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/lp1bsinitvals22.fw
Extracting b43/n16initvals30.fw
Extracting b43/lp0bsinitvals16.fw
Extracting b43/lcn1bsinitvals25.fw
Extracting b43/lcn400initvals33.fw
Extracting b43/n0bsinitvals24.fw
Extracting b43/lcn2bsinitvals26.fw
Extracting b43/lcn1initvals26.fw
Extracting b43/n0bsinitvals22.fw
Extracting b43/n18initvals32.fw
Extracting b43/lcn2initvals26.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/n0bsinitvals11.fw
Extracting b43/lcn2initvals24.fw
Extracting b43/lcn0initvals26.fw
Extracting b43/n0absinitvals11.fw
Extracting b43/ucode21_sslpn_nobt.fw
  ucode time:     01:15:07
Extracting b43/ucode26_mimo.fw
Extracting b43/n2initvals19.fw
Extracting b43/sslpn3initvals21.fw
Extracting b43/a0g1bsinitvals13.fw
Extracting b43/sslpn4initvals22.fw
Extracting b43/pcm5.fw
Extracting b43/ucode22_mimo.fw
Extracting b43/ucode9.fw
Extracting b43/lcn2initvals25.fw
Extracting b43/lp1initvals22.fw
Extracting b43/sslpn1bsinitvals27.fw
Extracting b43/lcn0initvals24.fw
Extracting b43/ucode32_mimo.fw
Extracting b43/a0g0bsinitvals9.fw
Extracting b43/n18bsinitvals32.fw
Extracting b43/n0initvals24.fw
Extracting b43/n0initvals25.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/ucode24_lcn.fw
Extracting b43/n0initvals17.fw
Extracting b43/n0bsinitvals16.fw
Extracting b43/lp0initvals15.fw
Extracting b43/b0g0initvals5.fw
Extracting b43/ucode20_sslpn_nobt.fw
Extracting b43/lcn1initvals24.fw
Extracting b43/sslpn0initvals16.fw
Extracting b43/a0g1initvals13.fw
Extracting b43/lp1bsinitvals20.fw
Extracting b43/sslpn2initvals19.fw
Extracting b43/a0g1initvals9.fw
Extracting b43/lcn1bsinitvals24.fw
Extracting b43/ucode5.fw
Extracting b43/lcn2bsinitvals24.fw
Extracting b43/lp0bsinitvals13.fw
Extracting b43/n0initvals16.fw
Extracting b43/ucode19_sslpn_nobt.fw
Extracting b43/b0g0bsinitvals9.fw
Extracting b43/ucode11.fw
Extracting b43/lp0initvals16.fw
Extracting b43/ucode16_mimo.fw
Extracting b43/lcn0bsinitvals26.fw
Extracting b43/ht0initvals29.fw
Extracting b43/lcn2bsinitvals25.fw
Extracting b43/a0g0initvals9.fw
Extracting b43/ucode29_mimo.fw
Extracting b43/lcn0bsinitvals24.fw
Extracting b43/ucode19_sslpn.fw
Extracting b43/lcn1initvals25.fw
Extracting b43/ucode30_mimo.fw
Extracting b43/n16bsinitvals30.fw
Extracting b43/ucode25_mimo.fw
Extracting b43/ucode24_mimo.fw
Extracting b43/ucode27_sslpn.fw
Extracting b43/lp0initvals13.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/ht0bsinitvals26.fw
Extracting b43/ucode13.fw
Extracting b43/sslpn2bsinitvals19.fw
Extracting b43/ucode15.fw
Extracting b43/lp0bsinitvals15.fw
Extracting b43/n0initvals11.fw
Extracting b43/lcn0initvals25.fw
Extracting b43/sslpn0bsinitvals16.fw
Extracting b43/sslpn1initvals20.fw
Extracting b43/lcn1bsinitvals26.fw
Extracting b43/n0initvals22.fw
Extracting b43/ht0bsinitvals29.fw
tc@box:~/b43fw$ tce-load -i wireless_tools
wireless-3.8.13-tinycore.tcz: OK
libiw.tcz: OK
wireless_tools.tcz: OK
tc@box:~/b43fw$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~/b43fw$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~/b43fw$ sudo iwconfig
ip_vti0   no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"eltonenetwork" 
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:6789-abcd-ef
          Power Management:on
         
dummy0    no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

tunl0     no wireless extensions.

tc@box:~/b43fw$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending select for 135.79a.0.ce...
Lease of 135.79a.0.ce obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 123.456.7.89
adding dns 8.8.4.4
adding dns 987.654.3.21
adding dns 8.8.8.8
tc@box:~/b43fw$ode]


Please note:

Tx-Power=0 dBm

Q: How can firmware cutting/installing survive reboot, so it's a one-shot setup?
Thanks,
eltone
PS. First post using TCP 5.1 LiveUSB w/WLAN b43

[tinypoodle]

PHEW!!
 

Does Tx-Power still after 0 dBm after connection has become fully functional?

Also, are you sure you want 4 DNS resolver entries?

[gerald_clark]

Q: How can firmware cutting/installing survive reboot, so it's a one-shot setup?
Thanks,
eltone

I answered that back on page 3.

[eltone]

Does Tx-Power still after 0 dBm after connection has become fully functional?

Also, are you sure you want 4 DNS resolver entries?

tinypoodle,

WLAN burn-in appears more stable than the hard wired ethernet connection!

If it works, don't fix it, but why question the DNS?

Code: [Select]

tc@box:~$ sudo iwconfig
ip_vti0   no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"eltonenetwork" 
          Mode:Managed  Frequency:2.427 GHz  Access Point: 00:21:1E:57:DC:60   
          Bit Rate=54 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:6789-abcd-ef
          Power Management:off
          Link Quality=70/70  Signal level=-38 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:10  Invalid misc:139   Missed beacon:0

dummy0    no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

tunl0     no wireless extensions.

tc@box:~$


eltone

[Juanito]

Q: How can firmware cutting/installing survive reboot, so it's a one-shot setup?

I sent you a pm offering to help with this about 10 days ago 

[tinypoodle]

Now that looks all perfect, I would guess the interface was not up before you ran udhcpc, making for the difference in output.

Such a DNS mix is just not very common, but if that's how you want it and are aware of the potential consequences, ok.

[coreplayer2]

YAY!!!   


I gotta say, those DNS server addresses are weird..   

[eltone]

Code: [Select]

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:
...
Q: Shouldn't it be recompiled first?We'll know that once you've tested it 

hi,
wicd tested OK on TCP 5.1 today.  The only problem was that the firmware has to be reinstalled following each boot!

Apparently the driver gets loaded before the firmware folder is restored during the boot phase.

FILETOOL.LST:
opt
home
usr/share/udhcpc/default.script
usr/local/lib/firmware/b43
opt/wlan0.sh
usr/local/etc/wicd
var/lib/wicd/configurations
opt/eth0.sh

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

ONBOOT.LST:
Xlibs.tcz
Xprogs.tcz
Xvesa.tcz
aterm.tcz
fltk-1.1.10.tcz
flwm_topside.tcz
freetype.tcz
imlib2.tcz
libICE.tcz
libSM.tcz
libX11.tcz
libXau.tcz
libXdmcp.tcz
libXext.tcz
libXfont.tcz
libXi.tcz
libXmu.tcz
libXpm.tcz
libXrandr.tcz
libXrender.tcz
libXt.tcz
libfontenc.tcz
libjpeg-turbo.tcz
libpng.tcz
libxcb.tcz
libXft.tcz
libXinerama.tcz
libXcursor.tcz
liblzma.tcz
libffi.tcz
gdk-pixbuf2.tcz
libtiff.tcz
glib2.tcz
imlib2-bin.tcz
wbar.tcz
fluxbox.tcz
wicd.tcz

Q: How can the b43 driver get loaded after the firmware gets restored during boot?

eltone

[Juanito]

Remember that extension deps are recursive, there is no need to have most of those extensions named in onboot.lst

It would be better to make a personal extension out of a large amount of static data like the b43 firmware rather than making it part of your backup.

Once you've made a personal extension out of the b43 firmware, you can place it before wicd in onboot.lst