piCore 5.0.alpha3

[bmarkus]

Thanks for the feedback. Regarding WiFi, are you using WPA?

[Gerrelt]

Thanks for the feedback. Regarding WiFi, are you using WPA?

Yep. See: reply #41.

[sbp]

hi bmarkus

Just tried with my other wifi adaptor a Comfast WU710N: chipset RTL8188CUS.

This one has been working in all your piCore versions up until version 5. I usually only need to install wifi.tcz via tce package manager.

However in version 5 (after installing wifi.tzc (and not the ralink firmware)):
When writing:

Code: [Select]

iwconfigI get this error:

Code: [Select]

iwconfig: error while loading shared libraries: libiw.so29: cannot open shared object file: No such file or directory

I don't know if this is related with the ralink wifi problem?

Steen

[bmarkus]

Install libiw.tcz

[sbp]

Hi

Thanks - Did you fix something already?

I just started from scratch once again with piCore 5, installed wifi.tcz  (and now I noticed that it also downloaded libiw - I don't remember if it did so before)?

But anyhow, now my Comfast adaptor is working (sort of) it can scan and detect my router but I get exactly the same result as with the ralink adaptor:

Code: [Select]

    ESSID                               Enc   Qual    Channel Type
 1. Steens 2.4GHz                         on    77       7     WPA
 2. Djurs5                               on    65       3     WPA

Enter selection ( 1 - 2 ) or (q)uit: 1
Enter password for Steens 2.4GHz (8 to 63 characters): ********
Sending credentials to requested access point Steens 2.4GHz...................
udhcpc (v1.21.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
Failed to connect.
So it has the same problem. Somehow Gerrelt seems to be able to work around the problem with his manual set-up script.

Steen

[bmarkus]

Try this:

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

[Gerrelt]

So it has the same problem. Somehow Gerrelt seems to be able to work around the problem with his manual set-up script.

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: [Select]

-n              Exit with failure if lease is not immediately obtained
-b              Background if lease is not immediately obtained
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 :

Code: [Select]

udhcpc (v1.21.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
Failed to connect.

Have you tried my wpa_supplicant.conf and wifi script?