Tiny Core Base > piCore Test Releases
piCore 5.0alpha4
Gerrelt:
@bmarkus:
I've tested Alpha 4, and everything works. I've tested it with two wifi adapters, one with the RTL8188CUS chipset, and one with the RT5370. That last one needed the ralink drivers.
sbp:
I tested it with gerrelts script, and I was able to connect.
So somehow the automatic wifi script is not working. Hopefully, we can get it to work.
If you have an idea to test, please say so and I will try.
Gerrelt:
Yes, I have an idea you can test. I tried to test it, but I just discovered wifi.sh works on my raspberry.. But it will probably not work all the time. But testing will be difficult for me this way.
OK, here it goes: the script uses -n, which means the udhcpc command exits if it can not get a lease after a short period of waiting.
The -b option forks to te background after that period of time and keeps on trying to obtain a lease. This means the wifi.sh script continuus after that period of time with the rest of the script while the udhcpc command is trying to obtain a lease in a different process thread.
Now, I am curious what happens if we don't use either. So no "-n" and no "-b".
I am hoping the udhcpc command keeps the script thread waiting until it obtains a lease. That way the script can execute in it's normal fashion after udhcpc is finished and obtained a lease.
The downside to this would be it will wait forever if it cannot get a lease... But hey, if the only network connection is Wifi, the raspberry is useless anyway without a connection.
So could you remove all the "-n" options from the udhcpc command in the wifi.sh script and try again?
I believe we are breaking some rules concerning extension management... Maybe we should get in contact with the wifi extension manager?
edit: Just tested my own script without the -b or -n option, and it seems to work! It takes a little longer to complete the script, but it is connected afterwards.
bmarkus:
--- Quote from: meo on October 05, 2013, 07:27:12 AM ---Hi bmarkus!
Tried it out and issued following command "tce-load -wi TC" after which I gave the command, startx, after which I got the error message: "failed waitforX". Is something missing or am I doing something wrong?
Have fun with piCore,
meo
--- End quote ---
There was a missing dep. Fixed, now it works.
sbp:
OK
As suggested by Gerrelt I tried to remove all the "-n" options from the udhcpc command in the wifi.sh script.
Now it continues with:
--- Code: ---Sending discover...
Sending discover...
Sending discover...
Sending discover...
Sending discover...
Sending discover...
--- End code ---
Until I kill the process.
So there must be something else wrong with how the connection is made - I never had these problems with version 4.7.7 and it is the same wifi adaptors and the same router.
Steen
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version