Tiny Core Base > piCore Test Releases

piCore 5.0.alpha3

<< < (11/11)

bmarkus:
Try this:

http://forum.tinycorelinux.net/index.php/topic,15934.msg94359.html#msg94359

Gerrelt:

--- Quote from: sbp on October 02, 2013, 02:28:29 PM ---So it has the same problem. Somehow Gerrelt seems to be able to work around the problem with his manual set-up script.

--- End quote ---

It could be because I use -b with the udhcpc command instead of -n, which the wifi.tcz script uses.

From the udhcpc man page:

--- Code: ----n              Exit with failure if lease is not immediately obtained
-b              Background if lease is not immediately obtained
--- End code ---

So, -n exits with a failure if, after certain time, the lease is not obtained.
With -b the process goes to the background and keeps waiting until a lease is obtained.
Our Raspberries aren't the fastest machines, so -b might be more suitable then -n.
Also if your network or router isn't very fast, -b might be more suitable too.

This is the result of using -n :


--- Quote from: sbp on October 02, 2013, 02:28:29 PM ---
--- Code: ---udhcpc (v1.21.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
Failed to connect.
--- End code ---

--- End quote ---

Have you tried my wpa_supplicant.conf and wifi script?

Navigation

[0] Message Index

[*] Previous page