Tiny Core Base > CorePlus
WiFi Cannot Scan
tinypoodle:
And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead ;)
eltone:
--- Quote from: Juanito on February 01, 2014, 12:45:12 AM ---
Again, the order to do things is:
1. Load firmware
2. Load wireless module
3. Associate with wap
4. Run udhcpc
--- End quote ---
hi,
Your instructions have been followed at the CLI level:
--- Quote ---
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
--- End quote ---
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:
--- Quote from: eltone on February 01, 2014, 01:59:09 AM ---e) # sudo iwconfig
f) $ sudo ifconfig wlan0 up
--- End quote ---
I didn't mention either of these and believe that they are probably not necessary.
--- Quote ---Suspect root cause is prior to your instructions mentioned above, in the boot phase.
--- End quote ---
I doubt it - I haven't seen anything so far that would suggest this is the case.
--- Quote ---The Control Panel 'Network' is always set to 'ethernet eth0/NO DHCP'
--- End quote ---
That is so most wired connections work automatically, but it has no effect on wireless connections.
--- Quote ---Q: How can Network be set to 'wlan0/use DHCP broadcast'??
'eth0' is always enabled, even without being hard-wired to machine.
--- End quote ---
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:
--- Quote from: Juanito on February 01, 2014, 02:30:05 AM ---
--- Quote from: eltone on February 01, 2014, 01:59:09 AM ---e) # sudo iwconfig
f) $ sudo ifconfig wlan0 up
--- End quote ---
I didn't mention either of these and believe that they are probably not necessary.
--- End quote ---
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: ---Access Point:
Link Quality=
Signal level:
--- End code ---
eltone:
--- Quote from: eltone on February 01, 2014, 01:59:09 AM ---
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
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version