WiFi stack added

[bmarkus]

Hi sbp
To the best of my knowledge, that firmware executes in the hardware on the wireless card and does not need
to be recompiled for ARM. Assuming that the tcz formats between ARM and X86 are the same, you should be
able to use it.

.tcz as a container is the same and portable. One example is mirrors.tcz

[Gerrelt]

Check sent/received frames with ifconfig to see where the traffic goes.

iptraf.tcz can provide details on traffic.

Thanks! That's a brilliant programme.

Hi gerrelt.

Is it possible for you to confirm that using WPA and reducing the speed of the router to 54 Mb/s Will solve the sound problem?

It would be good to know if we Could solve the problem by going this route.

I think I am using WPA. And I think my problem is not exactly the same as yours, see below.
But I can do some tests with my old 54 Mb/s router. But I will have to figure out how to reach the nas first, where the LMS server is. That's connected to the new router.

Offtopic.....
So, I've forwarded some ports (9001 and 3483) to the LMS server to be able to access the LMS server from the other router. And I had to tell squeezelite to use the routers IP address as the LMS server's address. And then I could connect to the LMS server. And I got squeezelite working.
Ontopic...

The old router is a 54 Mb/s router that supports WPA and WPA2. At first I connected it through WPA2, which worked pretty good. But after about an hour the music started to break up.
Then I switched the router to WPA. And it played without faults for hours! That supports your findings, sbp!

Even better, the next day, the raspberry could still connect to wifi. Even switching it on and off (pulling the plug) didn't matter, it connected everytime.
Today I plugged it back in, and it still works without problems.

So, it works a lot better with 54 Mb/s and WPA.

The strange thing is, that I have had raspberries running through wifi on 150 Mb/s and WPA2 without problem. But then I used the raspbian wheezy os. Is it because tinycore is run entirely in memory that the processor of the raspberry has to work harder?

[bmarkus]

The strange thing is, that I have had raspberries running through wifi on 150 Mb/s and WPA2 without problem. But then I used the raspbian wheezy os. Is it because tinycore is run entirely in memory that the processor of the raspberry has to work harder?

piCore base system is running in RAM, but .tcz extensions are mounted. You can load all tcz's or selected one's copy to RAM instead of loop mounting. You can try to copy everything to RAM and check WiFi, but I do not expect difference. However interested in the result

[sbp]

So, it works a lot better with 54 Mb/s and WPA.

So if only we could find a way to force microcore wifi to connect at max 54Mb/s and WPA we could be back in business.

Steen

[tinypoodle]

So if only we could find a way to force microcore wifi to connect at max 54Mb/s

Have you tried to follow suggested instructions in #Reply 58 in detail?

[bmarkus]

wpa_supplicant is using /etc/wpa_supplicant.conf created by wifi.sh It is always recreated when wifi.sh started. For testing, start wifi manually.

1) Stop wifi (disconnect than quit in wifi.sh)
2) Edit /etc/wpa_supplicant.conf
3) Start wpa_supplicant in a teminal:

    wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf

It will run in foreground and you will see messages

4) In a new terminal start dhcp client

    udhcpc -b -i wlan0 -x hostname box -p /var/run/udhcpc.wlan0.pid

It will run in background. You will see messages on leased IP and DNS.

Now you have a WiFi connection using /etc/wpa_supplicant.conf settings and you can test it. For settings see

http://linux.die.net/man/5/wpa_supplicant.conf

or Google

To set rate:

sudo iwconfig wlan0 rate 1M

(or any supported value)

[bmarkus]

BTW what is the CPU load of wpa_supplicant using WPA2 and 150 Mbit/s?

[Gerrelt]

BTW what is the CPU load of wpa_supplicant using WPA2 and 150 Mbit/s?

Not very high, max 2 percent, if I remember correctly. In fact, the raspberry wasn't very busy at all, according to the "top" command.
Which is strange, isn't it?

It must be some kind of IO problem then?

[sbp]

Another thing to consider.

When I'm connected to my router at 150 Mb/s, the music is breaking up even when connected without any WPA protection (so I guess that WPA_supplicant is not used?)

Steen

[Gerrelt]

Hi,

I've upgrade my Pi with the piCore-20130521 image (the one with the 4.7.7 base and 3.8.13 kernel), and now I don't have any problems with wifi anymore!   

I can now even connect to my 150 Mb/s router using WPA2 without problems, it connects everytime and the music does not break up. I am very happy with it!

I wanted to mention this here, just to be complete.

Greetings,
    Gerrelt.

[bmarkus]

Thanks a lot for reporting. Glad to hear it works fine. This 3.8.13 kernel solved many problems, I like it.

[joaosombra]

Hello,

I've trying to make my Wifi usb dongle work reading this tutorial. My usb dongle is a TPLink TL-WN721N that shows "Atheros Communications, Inc. AR 9271 802.11n" when I type lsusb into console terminal.

When I connect the Wifi usb dongle I got the message into dmesg - Failed to load firmware htc_9271.fw.

So, after a research, I've found this file into the Linux Wireless site. So I've downloaded this file and put it into the /usr/local/firmware folder.

I've disconnected and connected the wifi usb dongle again, and I've got the wireless working.

But when I reboot, all my changes go away. I've tried to install the wireless*.tcz packages, but no success.

So, Have I make an extension to keep this file into /usr/local/firmware persistent?

Thanks

[gerald_clark]

Install firmware.tcz.

[gerald_clark]

Sorry, I missed that it was an ARM forum.
I wish we could unsubscribe to specific fora.

[joaosombra]

No problem. I'm actually trying to enable WiFi access into my RPi with this brand of wifi usb dongle. But into the tce app I couldn't find the firmware package.