WiFi Cannot Scan

[eltone]

hi,
'udhcpc' passed burn-in on PC #2, BUT now is NON-functional, just like what was reported earlier!
This malfunction does NOT occur on other distros.   Please help.

Code: [Select]

sudo udhcpc -S -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid

The '-S' switch was enabled to ammend attached syslog . . .

Excellent CLI Network Configuration Article:
http://ubuntuforums.org/showthread.php?t=684495

THX4HLP!
eltone
* udhcpclg.txt FAILED
   udhcpcl2.txt PASSED

[eltone]

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

tc-5.x Guru's,

I have researched HOW2 make a personal extension for someone that's cutting-their-teeth w/tc-5.1 and find nothing but outdated material.  Any help from those that have done this before?

I hate to reinvent the . . .
eltone

[Rich]

Hi eltone
This doesn't look outdated to me:
http://wiki.tinycorelinux.net/wiki:extension_for_settings

[coreplayer2]

The wiki is a great place to learn and source of reference..

Meanwhile, try creating your extension in /tmp

For this example we'll call the firmware b43cut.img, and
the extension firmware-b43cut.tcz

start by creating your directory structure, at the command line
    mkdir -p /tmp/pkg/usr/local/lib/firmware/b43cut
    mkdir -p /tmp/pkg/usr/local/tce.installed

create a file (in this case a udevadm trigger)
    touch /tmp/pkg/usr/local/tce.installed/firmware-b43cut

open file "/tmp/pkg/usr/local/tce.installed/firmware-b43cut" and enter on the first two lines
the following, then save it

Code: [Select]

#!/bin/sh
udevadm trigger
copy (your firmware file) to /tmp/pkg/usr/local/lib/firmware/b43cut/


set permissions   (note the own/perm. of tce.installed)

sudo chmod 644 /tmp/pkg/usr/local/lib/firmware/b43cut/b43cut.img
sudo chown -R root:root /tmp/pkg/usr
sudo chown -R root:staff /tmp/pkg/usr/local/tce.installed
sudo chmod -R 775 /tmp/pkg/usr/local/tce.installed

Now you're ready to squash it

cd /tmp
tce-load -i squashfs-tools-4.x.tcz && mksquashfs pkg/ firmware-b43cut.tcz

then copy the new extension to tce/optional dir, load it

tc@box:/$ tce-load -i firmware-b43cut.tcz
firmware-b43cut.tcz: OK

and test it


see also http://wiki.tinycorelinux.net/wiki:creating_extensions

[Juanito]

'udhcpc' passed burn-in on PC #2, BUT now is NON-functional, just like what was reported earlier!
This malfunction does NOT occur on other distros.   Please help.

Hundreds of tinycore users are using udhcpc every day without problems - the problem is not with udhcpc, but with what comes before the the udhcpc command. Several users, myself included, have tried to help, but you need to follow what is suggested in the order it is suggested for things to work.

I sent you a pm two or three weeks ago offering to make a firmware extension for you, but (so far) you've ignored it.

Again, the order to do things is:

1. Load firmware

2. Load wireless module

3. Associate with wap

4. Run udhcpc

[tinypoodle]

And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead   

[eltone]

Again, the order to do things is:

1. Load firmware

2. Load wireless module

3. Associate with wap

4. Run udhcpc

hi,
Your instructions have been followed at the CLI level:

I. To cut/install your own firmware:

a) $ sudo mkdir -p /home/tc/b43fw

b) $ cd b43fw

c) $ sudo wget -c http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2

d) $ sudo tar xf broadcom-wl-5.100.138.tar.bz2

e) $ sudo mkdir -p /usr/local/lib/firmware

f) $ tce-load -i b43-fwcutter

g) $ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.138/linux/wl_apsta.o

II. Load wireless module:

a) $ tce-load -i wireless_tools

III. Associate with WEP

a) $ tce-load -i rfkill

b) $ sudo rfkill unblock wifi

c) $ sudo iwconfig wlan0 essid eltonenetwork

d) $ sudo iwconfig wlan0 key 6789abcdef

e) # sudo iwconfig

f) $ sudo ifconfig wlan0 up


IV. Run udhcpc

a) $ sudo udhcpc -S -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid

Suspect root cause is prior to your instructions mentioned above, in the boot phase.

The Control Panel 'Network' is always set to 'ethernet eth0/NO DHCP'

Q: How can Network be set to 'wlan0/use DHCP broadcast'??
'eth0' is always enabled, even without being hard-wired to machine.

eltone

[Juanito]

e) # sudo iwconfig

f) $ sudo ifconfig wlan0 up

I didn't mention either of these and believe that they are probably not necessary.

Suspect root cause is prior to your instructions mentioned above, in the boot phase.

I doubt it - I haven't seen anything so far that would suggest this is the case.

The Control Panel 'Network' is always set to 'ethernet eth0/NO DHCP'

That is so most wired connections work automatically, but it has no effect on wireless connections.

Q: How can Network be set to 'wlan0/use DHCP broadcast'??
'eth0' is always enabled, even without being hard-wired to machine.

The udhcpc command sets wlan0/dhcp, but you can also associate with your wap and then use the cpanel network gui if you wish. If you load the firmware, load the wireless extension and use rfkill to enable your hardware, the wifi extension will also work.

The fact that eth0 is always enabled does not affect anything to do with wifi.

[tinypoodle]

e) # sudo iwconfig

f) $ sudo ifconfig wlan0 up

I didn't mention either of these and believe that they are probably not necessary.

I did recommend e)
but:

1. That makes only sense after the interface is already up
2. This serves the purpose to verify if a link with WAP is established before attempting to run dhcp client, i.e. check fields:

Code: [Select]

Access Point:
Link Quality=
Signal level:

[eltone]

Suspect root cause is prior to your instructions mentioned above, in the boot phase.

The Control Panel 'Network' is always set to 'ethernet eth0/NO DHCP'

Q: How can Network be set to 'wlan0/use DHCP broadcast'??
'eth0' is always enabled, even without being hard-wired to machine.

eltone

hi,
The one clue that udhcpc will/might function is when the ethernet cable is hard-wired to notebook AND I see the dns server addresses flash on the screen during boot, similar to when udhcpc desides to function.  Removing ethernet cable and entering your posted CLI instructions is what worked to post this note (see syslog attachment)!

Please help resolve this elusive, but interesting problem . . .

eltone
PS. the path is getting warmer.

[eltone]

The wiki is a great place to learn and source of reference..

1

Meanwhile, try creating your extension in /tmp

2

For this example we'll call the firmware b43cut.img, and
the extension firmware-b43cut.tcz

3

start by creating your directory structure, at the command line
    mkdir -p /tmp/pkg/usr/local/lib/firmware/b43cut
    mkdir -p /tmp/pkg/usr/local/tce.installed

4

create a file (in this case a udevadm trigger)
    touch /tmp/pkg/usr/local/tce.installed/firmware-b43cut

5

open file "/tmp/pkg/usr/local/tce.installed/firmware-b43cut" and enter on the first two lines
the following, then save it

Code: [Select]

#!/bin/sh
udevadm trigger

6

copy (your firmware file) to /tmp/pkg/usr/local/lib/firmware/b43cut/


set permissions   (note the own/perm. of tce.installed)

sudo chmod 644 /tmp/pkg/usr/local/lib/firmware/b43cut/b43cut.img
sudo chown -R root:root /tmp/pkg/usr
sudo chown -R root:staff /tmp/pkg/usr/local/tce.installed
sudo chmod -R 775 /tmp/pkg/usr/local/tce.installed

Now you're ready to squash it

cd /tmp
tce-load -i squashfs-tools-4.x.tcz && mksquashfs pkg/ firmware-b43cut.tcz

then copy the new extension to tce/optional dir, load it

tc@box:/$ tce-load -i firmware-b43cut.tcz
firmware-b43cut.tcz: OK

and test it


see also http://wiki.tinycorelinux.net/wiki:creating_extensions

hi,

Indexing to #5, no problem, then #6 states:

copy (your firmware file) to /tmp/pkg/usr/local/lib/firmware/b43cut/

Your instructions say to call the firmware 'b43cut.img'

Q1: Is this IMG file what goes into the 'b43cut' directory?

Q2:  If correct, how are the numerous FW files made into an IMG file w/TCP 5.1?
Suspect an extension is needed.

eltone
PS. keep the pile to a minimum

[eltone]

And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead   

hi,
'dhcpcd' does not follow udhcpc Standards.  Also,  tc5.x man pages has nothing on it either:

tc@box:~$ dhcpcd --help
usage: dhcpcd [-dgknpqwxyADEGHJKLOTV] [-c script] [-f file] [-e var=val]
              [-h hostname] [-i classID ] [-l leasetime] [-m metric] [-o option]
              [-r ipaddr] [-s ipaddr] [-t timeout] [-u userclass]
              [-F none|ptr|both] [-I clientID] [-C hookscript] [-Q option]
              [-X ipaddr] <interface>
tc@box:~$

Q1: Has anyone been able to get dhcpcd to find a valid IP address & with what syntax?

Q2: Could dhcpcd be compiled from source w/TCP 5.1, following this protocol:

http://www.linuxfromscratch.org/blfs/view/svn/basicnet/dhcpcd.html

eltone

[coreplayer2]

For this example we'll call the firmware b43cut.img, and
the extension firmware-b43cut.tcz

Your instructions say to call the firmware 'b43cut.img'

Q1: Is this IMG file what goes into the 'b43cut' directory?

Q2:  If correct, how are the numerous FW files made into an IMG file w/TCP 5.1?

They're not exactly instructions to be followed to the letter,  more of an example (though the example does in fact work as advertised)..  If they were instructions it would say rename the file to this, etc etc. if that were necessary.     I believe the original file name should remain unchanged, I simply didn't know the final cut file name is all.  the dir name in this case is less important though ought to reflect the contents.  Similar for the extension name which additionally should not conflict with any in the repo (name could be myb43, whatever..)   

Rarely are two extensions alike, they differ greatly due to their contents.   
better to examine how a similar extension is constructed, sometimes names and permissions are important, use
this to examine an extension

Code: [Select]

unsquashfs -d extension_name extension_name.tcz

[tinypoodle]

And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead   

hi,
'dhcpcd' does not follow udhcpc Standards.  Also,  tc5.x man pages has nothing on it either:

Huh??   
Both udhcpc and dhcpcd follow dhcp protocol as described in the relevant RFC's.
The manpage of dhcpcd could be found within less than a minute on the web, like almost all manpages...   

Q1: Has anyone been able to get dhcpcd to find a valid IP address & with what syntax?

Q2: Could dhcpcd be compiled from source w/TCP 5.1, following this protocol:

http://www.linuxfromscratch.org/blfs/view/svn/basicnet/dhcpcd.html

eltone

dhcpcd.tcz is already in 5.x repo, I checked that before even suggesting so...

[eltone]

dhcpcd.tcz is already in 5.x repo, I checked that before even suggesting so...

My Dear Friend!

Q: Shouldn't ALL remnants of udhcpc be completely removed before installing the .TCZ?
It appears to be original settings of TCP 5.1 . . .
'udhcpc' has no .TCZ and suspect it to be part of the OS Standards.

Faithfully,
eltone
* FIX what's BROKEN *