it can be it doesn't work with kernel 3.6.11: try with the packages kernel_raspi, raspi-boot and kernel-modules from

http://ponce.cc/slackware/slackwarea...extras-3.2.27/

(raspberrypi's devs don't maintain the 3.2.27 branch anymore)

1 members found this post helpful.

I guess I should issue un upgradepkg Command instead of installpkg... Then first I think I must save the image, for later use.

yes, with /dev/mmcblk0p1 already mounted on /boot (check with df): at kernel update, some files on that partition must be updated too.

1 members found this post helpful.

Ok ponce, I have tried the 3.2.27 packages but it doesn't work either. Now I'm upgrading to last packages to test them too.

with 3.2.27 look for errors in dmesg
should show something if the firmware has problem loading: use the raspbian's firmware files with this kernel if you think they work, or try also the stock ones.

try also to modprobe the stuff manually and see if something shows in the latest lines of dmesg ("dmesg | tail") or as output.

Thanks ponce, I think i might have done it with guanxs's drivers that he indicated. Thanks guanx. But still I have one question: why the device is ra0 and not wlan0? Still I must test it that it works with wicd, and then set it as AP. But I hope it works, although it seems to have his own's configurations, and I hope it dosn't interfere with Slackware's configurations.

Just got my RasPi and got Slackware installed and working on it.

The installer provided at Dave's Collective ( http://www.daves-collective.co.uk/ra...stalling.shtml ) was giving me the Rainbow Screen Of Death.

I finally succeeded, by using the 16GB image from http://stanleygarvey.com/Slackberry/download.php

Looking forward to a lot of fun!

Hi again,

I'm trying to start hostapd but it fails with this messages:
@guanx: because you have the same driver, maybe you encountered the same problem with hostapd. Can you help?

I believe (from what I've read) that it is because it has no firmware - that driver from ralink doesn't have any firmware with it, it is only the driver.

Which driver are you using? Please note in post #160 I only used the firmware and not the driver from the manufacturer.

With the driver from Linux 3.7.x I am having no problem setting up either an AP (Master) or a station (Managed) with RT5370, except that I cannot have multiple virtual interfaces up at the same time.

I'm using the driver for rt5370 from ralink page that you indicated and after compiling it results several object files (.o and .ko) and then I run insmod rt5370sta.ko.

But I looked again and now I am compiling it again with 2 different options/modifications which might cause it to function like I want to. So, there is no firmware, maybe your version differs.

Yes there is. With the official Linux driver and not the manufacturer driver you need the firmware. The firmware link is misspelled as "rmware" on the manufacturer's webpage. The first two letters of "Firmware" are missing. The official Linux driver for RT5370 is RT2800USB (module "rt2800usb.ko").

I have never tried and never suggested to use the manufacturer's driver. But since you are already using that, could you try if you can bring up multiple virtual interfaces at the same time, with different ESSIDs? If yes, then the manufacturer's driver is worth trying.

I think it has. There is a compiling option "Suport for multiple cards" (maybe virtual) in os/linux/config.mk but I haven't compiled the driver with it.

I have downloaded the firmware but I see that it was already there (rt2870.bin in /lib/firmware) so it doesn't work.

Thank you! I'll take a look then.

Hey people!
Why we don't use the raspberry-pi forum for a true Slackware ARM section.

It would be nice see more of you there.

http://www.raspberrypi.org/phpBB3/vi...p?f=56&t=21805

I have managed to make the TP-Link TL-WN727N wireless adapter work with the linux drivers. It was right, the drivers existed, they only needed the firmware update (like drmozes suggested) from slackwarearm patches directory, only that when I updated the firmware, before that, I messed with the modules so this is the reason that it didn't work. Now, I installed slackwarearm again and it works.

Also, ponce, maybe you should know that your last install image has a problem: after finishing the install, somehow when rebooting it mounts the / partition rw when it needs to be ro for checking. There it gives some errors, I think.