Tiny Core Extensions > TCE Q&A Forum

wifi.tcz

<< < (17/18) > >>

andrewb:
Robert,

Just to report:

On a EEEPC 900ax wifi.tcz doesn't work 'out-of-the-box' due to the output from iwconfig. Running iwconfig gives the output
--- Code: ---~$ iwconfig
lo        no wireless extensions.

dummy0    no wireless extensions.

eth0      no wireless extensions.

wlan0     Ralink STA  ESSID:""  Nickname:""
              Mode:Auto  Frequency=2.412 GHz 
              Link Quality=10/100  Signal level:0 dBm  Noise level:-143 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0
                                       

--- End code ---

So no IEEE phrase for wifi.sh to find the wireless adapter. Changing the search phrase to ESSID, everything works.

roberts:
Actually, the IEEE test is a relic of v0.1. In v0.2 - v0.4 I had changed it
Without knowing what many and various wifi devices report when unconfigured I am now using:

WIFI="$(iwconfig 2>/dev/null | awk '{if (NR==1)print $1}')"

roberts:
Thanks for feedback. v0.6 with corrected initial wifi device detection now posted.

OldAdamUser2:
Robert,

I'm pleased to report that wifi.sh works perfectly on my Eee900. It allows me to get rid of wicd and all  of its dependencies, hence networking on a leaner, meaner system.

Many thanks. . . .

Actually, I may have spoken too quickly. The script runs properly and allows me to connect to my home wifi when I run it from wbar.

But, when I plug in the recommended "/usr/local/bin/wifi.sh auto 2>&1 > /tmp/wifi.log" in bootlocal.sh it does not auto-connect. If I then open a terminal window and try the command (with or without sudo), it says I don't have permission to write /tmp/wifi.log. If I delete that part of the command and try the rest, the script scans for available networks but fails to connect. But I can still go back and run the script from wbar and connect without problem. This is not a password-protected wifi.

The auto-connect that DOES work for me is--

        sudo iwconfig wlan0 essid "my-esssid#"
        sudo udhcpc -i wlan0

roberts:
Auto connect writes to /tmp/wifi.log You should cat that file to see what happened. Based on it working from wbar would suggest that the device was not ready. You might need to add a sleep command before the wifi.sh call to allow time for the device to be created.

Navigation

[0] Message Index

[#] Next page

[*] Previous page