Fixing wi-fi on Asus Eee PC 901 with Linux

I mentioned my annoyance that wi-fi with WPA encryption did not work on the Asus 901 Eee PC with Linux which I am reviewing. I later found that even a WEP connection, while it worked a bit, tended to drop out after few minutes. Worse still, the Asus repositories are messed up so getting updates is tricky.

I’ve managed to fix it. For the record, here’s what I did; though I can’t promise it will work for you; try it at your own risk. I should think there will be an easier way to install an updated driver soon.

One of the irritations about the repository problem is that attempted updates fill up your /dev/sda1. I wanted as much space as possible (without removing the recovery partition) so I reset the system with F9 on boot. Then I went into /etc/apt/sources.list and removed the default repositories, replacing them with these two:

deb http://xnv4.xandros.com/xs2.0/upkg-srv2 etch main contrib non-free

deb http://download.tuxfamily.org/eeepcrepos/ p701 main

(This is probably not a good arrangement long-term; but having the Asus repositories enabled right now makes it hard to install anything).

Then I did:

apt-get update

apt-get install build-essential

I also installed ksmserver and kicker to get access to the full desktop; but this wasn’t needed to get wi-fi working.

Next, I downloaded the latest driver source for the 901’s Ralink wi-fi card:

http://www.ralinktech.com.tw/data/drivers/2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2 (Update: don’t use this code – see Update 3 below).

Extracted it; then edited /os/linux/config.mk and changed:

HAS_WPA_SUPPLICANT=y

HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y – but see update 2 and update 3 below for the problems this caused.

I also removed –DDBG from WFLAGS

WFLAGS += –DCONFIG_STA_SUPPORT

In order to compile you need the kernel source. I adapted the instructions here. In essence, download the source from http://dlsvr01.asus.com/pub/ASUS/EeePC/701/Linux_Kernel_071127.rar, extract, install the deb, unpack the source in /usr/src, delete the .bz2 to save space, build the kernel with:

make oldconfig

make

(don’t actually install it), then create the following symbolic link:

ln -s /usr/src/linux-source-2.6.21.4-eeepc /lib/modules/2.6.21.4-eeepc/build

Now I was able to compile and install the ralink driver by switching to the RT2860 directory and typing:

make

make install

Wi-fi now worked with WPA; at least, it did on my second attempt after disabling native WPA supplicant support. I’ve also found it perfectly stable so far – much better.

Active wi-fi connection with WPA; a few numbers changed to reassure the paranoid

I’m happy now, but… what is Asus thinking?

I doubt the Eee brand would have ever taken off, except that the first 7xx releases made excellent use of Linux and open source applications to win people over; you did not even need to know that it was Linux.

Now we get this; the support for the 901 is dire; updates don’t work, the wi-fi doesn’t work properly, and the only fix I’ve found is a hack. Wi-fi is critical for a gadget like this, which is not much use without an Internet connection.

Together with short supply of the Linux version, this does suggest that Asus is keen to favour the Windows XP variant.

Update: I’ve made the binary (rt2860sta.ko) available for download here. Download includes RT2860STA.dat which goes in /etc/Wireless/RT2860STA. I guess we need an install script; I’ll have a go when I get a moment.

Update 2: Unfortunately I’m not quite there yet. If I compile with HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y then WEP works but WPA does not. If I compile with HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n then WPA works but (I now discover) WEP does not. Weird. I’m going to seek advice. If anyone wants the binary that works great with WEP but not WPA, let me know.

Update 3: Thanks to Ralink tech support I now have a fully working driver. I’ve updated the download above. The new code defines EEEPC_SPECIAL_SETTING and has some edits in common/mlme.c. It now works OK with HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y. Interesting point: the code is dated 15th July; which suggests that the problem was both known and fixed 2 and half weeks ago; it’s a shame nobody shared this with the community.

Update 4: I suggest you delete the old copy of rt2860sta.ko in /lib/modules/2.6.21.4-eeepc/rt2860 (if it exists).

PS: I’ve posted instructions for the binary install, with download links, here.

Technorati tags: , ,
VN:F [1.9.18_1163]
Rate this post
Rating: 10.0/10 (1 vote cast)
Fixing wi-fi on Asus Eee PC 901 with Linux, 10.0 out of 10 based on 1 rating

Related posts:

  1. Eee 901 problems – does Asus still care about Linux?
  2. 8GB Asus Eee PC from April 2008, Windows or Linux
  3. Fixing Webcam black screen on an Asus Eee PC
  4. Users petition Asus over locked bootloader in Asus Transformer Prime
  5. Firefox segmentation fault on Asus Eee PC after update

100 comments to Fixing wi-fi on Asus Eee PC 901 with Linux

  • pb

    hi..

    Thanks for the driver, WEP now works fine for me with my NETGEAR wgr614 router, was running unencrypted upto now. I had to run your installation script twice though.. and also reboot

    PB

  • hi… thank you very very much for your job ;-)
    my results:
    -original drivers: only working with unencrypted networks
    -your wep driver: working with unencrypted, wep and wpa networks :-)
    -your wpa driver: working with unencrypted and wep networks (not with wpa)

  • tim

    @ryke thanks for the report. I wish I got the same result with my wifi access point!

    Tim

  • pj

    Hello,

    well, I have followed the instructions to the letter, and have had no error messages.

    My 901 still doesn’t connect :( (similar to post 47)

    The new driver has not seemed to make any difference at all – I do not get an offer of a lease from the modem, and I have tried it both at home and in the office where we have another type.

    Strangely, and I have no idea why, if I set up the static address, it will connect to the modems, but it doesn’t get out any further – it is as though it cannot find the DNS, but that is not the case.

    Can I post any error log etc. which might help pinpoint the problem? It seems that this is almost a system-wide error with eees, when I read the posts.

    Kind regards

  • JPF

    Thank you Tim !
    Your fix also work with my 1000 for WEP (did not try WPA)
    You did a great job.
    Cheers,

  • Alan

    So I had some time to tinker today and solved my problem with WEP by manualy configuring the driver:-

    iwpriv ra0 set AuthMode=SHARED

    Hope this helps

    -Alan

  • Jon

    I’ve eventually got mine working too, using the WEP version of the driver, it connects to WPA Enterprise and unencrypted sites OK. But I d have difficulty getting an IP address, especially when moving from one site to another. This looks like some problem with DHclient (since other laptops connect to these routers without difficulty). I’ve observed that the link may go into ‘pending’ mode for several minutes before it gets an IP address successfully for the first time(and sometimes it does not get an IP address). I’ve noticed that going closer to the AP can help. Despite that overall range of the wifi caard is about the same as for other laptops, including a 701.

  • Cris

    Alan

    I’ve got the same problem with my 901:

    When trying to connect the log shows a few DHCPDISCOVER attempts and then NO DHCPOFFERS

    Where do you run the command:

    iwpriv ra0 set AuthMode=SHARED

    Sorry first time using Linux.
    Thanks
    Cris

  • Alan

    Cris,

    Assuming you are running a WEP encrypted wifi with a shared key – here’s what I did
    1) First intsall the new package per Tim’s instructions above & restart your WIFI
    2) Open a console by pressing Ctrl-Alt-T
    3) Type in the command line as a “su” or by prefixing with sudo

    FYI – set up my 901 with a static IP address but it works with DHCP – the issue is to get it to speak with the encrypted WIFI AP/modem. and the existing driver sets the mode to OPEN and lacks i/f to change the setting

    -Alan

  • Cris

    Alan

    Initially didn’t work, however got it working by playing around with the Wireless connection, disconnect, re-connect, etc…

    However when I reboot the setting seems to be lost, and seems to revert back to its default. How can I set this setting permanently for this wireless connection?

    Is there a boot up script I can place this setting in?

    Regards
    Cris

  • andrew_k

    I downloaded the wep version (rt2860wep.tgz above) onto my Linux eeePC 901, which was intermittently losing the wireless signal and needing to restart the network connection. That was about a week ago and it hasn’t dropped the signal once since. Thanks very much for this fix!

  • Tim, Thanks for this.
    Installed the WEP version and it works fine for me. No problems. Better support than ASUS! What’s the point of delivering a device with its main function broken? Cheers, Paul.

  • Matt

    Tim, thanks heaps for the advice and the new driver. Had spent hours on it previously trying to get WPA to work. Now works like a charm on my 901.

  • Thanks very much Tim. My 901 used to stop work a few seconds after start up, but with your driver it works like a charm.

    Thank you very much

  • misterjaytee

    Tim, tried the drivers above on both WEP and WPA, but no joy – wouldn’t even work with encryption switched off, SSID being broadcast and completely open access :O …

    Until I decided to set the IP address as Static instead of DHCP – then it all seems to be working now (on WEP anyway – I’ll try WPA later once I’m confident it’s all working).

    I’m using a Draytek Vigor 2800 router, but all other Wireless devices seem to work okay with this router, so minimal chance of there being problems there.

    Looks like Asus have shot themselves in the foot here – a netbook with it’s wireless broken seems pretty much an own goal. I’m assuming that they think anyone going for the Linux version is a geek and will work out what’s wrong with it anyway :D

    Anyway, thanks for putting up your new driver and some info about this – it gave me some good pointers on how to get this working…

    Thanks.

  • fredex

    Tim:

    i’ve been using one of your earlier efforts, for wpa, for some weeks (since mid August, at least) and it’s been FINE.

    Until Asus issued their new ralink driver update for the 901/linux. I’ve REFUSED to allow it to install, but since it was downloaded the system asks me, at every boot, if I want to install it–TWICE. I always say NO.

    but something has “gone bad” since then. the other day the file /etc/network/interfaces was hosed (I was able to manually patch it up).

    Today it doesn’t appear to be hosed, but I can’t connect to WPA at work (it was fine, last night, at home on WPA). I keep getting the error “Unable to determine interface to use. (lanservice.cpp: 574)”

    As a result and as an experiment I’ve downloaded your latest WEP and WPA binaries, installed the WPA one and it hasn’t changed a thing.

    I also note that neither depmod nor a reboot is actually loading the rt2860sta.ko module. Loading it manually (with lsmod) doesn’t help the problem at all. Neither did rerunning the depmod command that’s in the istaller script you provided.

    Suggestions? Thanks in advance!

  • fredex

    [later]…
    actually, I was wrong about one thing: after a reboot the rt2860sta.ko IS being loaded automatically. But I still get the same error message when trying to bring up the WPA connection here at my office.

  • csakDúk

    Hi out there,

    just got my 901 shipped the other day. Nice deeevice..Anyway.
    Booting it up, i connected right away to an open access point. The 901 downloaded some updates (lately including the ralink_WLAN_patch 1.7.1.1. 2008-10-02, and the 1301 bios).
    I must admit, i’m new to linux, and without notifying any issues the first time, i didn’t follow the whole update process with much attention.
    Now, i want to set up my local network, one with my XP laptop connected to internet via cable modem, sharing internet connection over wifi ad-hoc to the linux-dEeevice.
    At the point where i am (still unable to get a valid IP through DHCP on the dEeeevice) found this blog, and my head starts to hurt…
    I’m following this M$ guide

    http://www.microsoft.com/downloads/details.aspx?FamilyID=fac8708e-3762-4e78-b372-8404eeb7f41a&displaylang=en

    to set things up, but i can’t confirm, that i have them set up correctly, or not – obviously (?) issues on 901 wireless.

    My question is, with the latest 1.7.1.1. ralink _patch and the 1301 revision bios (not sure, if the last one HAS something to do with wifi) am i ready and set to connect 901 to the ad-hoc wLan?
    or should i try to install one of these binaries posted here? which one should i start with?

    and while i’m here, maybe somebody could confirm i have the XP set up right…
    three IPs. two on XP ‘a’-'b’, and one on Linux ‘c’

    ‘a’_got DHCP, connecting to internet via ethernet, ICS enabled.
    ‘b’_got static, ip 192.168.0.1 – subnet. 255.255.255.0 – no gateway, no dns
    ‘c’_got static, ip 192.168.0.2 – subnet. 255.255.255.0 – no gateway, no dns

    i tried setting ‘b’s gateway to the ‘a’ dynamic IP (obviously this will change time to time, boot-to-boot), setting ‘c’s gateway to ‘b’s IP…
    if i set my 901 wifi to DHCP can’t get connection (pending), if i set it to static, it gets to connect (at least in the Network panel) but the wireless icon on the bottom says ” ” and “10% signal” right under the empty line where the name of the SSID should be(?), but PING-ing doesn’t transfer no packets.

    sorry for the complexity and size of the post-o-problem, any help would be appreciated!

    thanks.
    d.

  • tim

    @csakDúk

    OK, you have:

    Laptop with XP
    Cable modem

    and now you want to connect the Eee to the network and Internet.

    Solution: get a wireless router. Connect it to the cable modem with an ethernet cable. Connect your other two machines to the router either wireless or wired.

    This is much easier and more reliable than messing around with XP internet sharing.

    Tim

  • csakDúk

    Thanks Tim, for the quick reply…
    have asked an IT friend of mine, told me the exact same thing…but for now, this isn’t the solution i was looking for, nor an option.
    So, people of the NET, any help about this setup-topic would be much appreciated, still!

    Easier, cheap? Probably.
    But hey, why spend even one cent, if i’ve got EVERYTHING (minus the knowledge) just right under the hood?! I mean, someone could spend some extra cash and change the wifi antenna for a better working one, without driver issues, right?!

    What’s Your experience with the radlink_wlan_patch.1.7.1.1?
    Or You still got this hotfix of Yours installed? (post #5, or #15?)
    Which BIOS You’re using? (does it have anything to do with the wlan issue?)

    And what about these drivers, i have installed? Should the wifi work on an OPEN ACCESS POINT, without any encryption? Or the asus drivers can’t connect to NO AP (open-WPA-WEP)?

    cheers Tim,
    d.

  • fredex

    another follow-up on my postings from yesterday…

    the WPA driver works fine on my WPA2 at home. It does not work at all on WPA1 at the office, giving the error message shown in yesterday’s posting (“unable to determine interface to use…”).

    The WEP driver conects to and appears to work with the WPA1 router at work. Go figure.

    NEITHER one of them will connect to the neighbor’s unencrypted wlan. Before I started having this trouble I used what I think was an earlier binary of tim’s that worked fine on both home and office WPA as well as the neighbor’s unencrypted wlan. (I had never tried it with a WEP wlan.)

    I’m planning to travel in a few weeks and it would be very nice if I could get it working, once again, on unencrypted wireless networks such as hotels have.

    Anybody have any thoughts on this?

    Thanks!

  • csakDúk

    to: fredex @ #71

    i got this afternoon the ASUS BIOS update of today, it’s version 1603.
    Had no time to dig deeper into linux though, so i still have the official ASUS updated ralink_WLAN PATCH-1.7.1.1 (dated 2008-10-02) installed. Have tried to connect again to an unsecured/open wireless AP (this time it isn’t the ad-hoc i was trying to set up these days, this one is infrastructured), and guess what, have a stable connection.

    Matter of fact, i didn’t install any of the drivers posted in this blog, because i still can’t find my way through all these partitions, with all these ‘mirrors’ of files (me a linux lamer)…and didn’t found the right one to make the backup of (and WHERE to copy it). By the way…do somebody know a good place to start with it (Google search)?

    This means that i STILL miss something in the setup of that d@rn ADHOC wlan connection of mine…will try to start from an open infrastructured one ASAP – and maybe i give the control to the Manufacturer Drivers of wifi. Could it be more functional than the sp2 driver?

    d.

    ps: 1603 – just got yesterday’s jam!

  • csakDúk

    to: Tim @ root

    messed up big time on that html embedded last post-o-mine…probably the syntax, missing the closing tags.
    previewing the post, it’s missing all the correct hyperlinked words.

    these are:
    - for the ASUS BIOS – “1603″ :
    http://update.eeepc.asus.com/bios/901-ASUS-1603.zip
    - the good place to start with it (“linux-partitions”) :
    http://www.google.es/search?hl=en&q=linux%2Bfile%2Bsystem&btnG=Search

    and another strange suggestion starting the last paragraph, namely “Tim might mod this part, because maybe it’s out of the scope of this blog, but…” This means that i STILL…
    (odd joke of xml-tag-stile-embedding this paragraph between this sentence – sillyme)

    meaculpa.

    it’s up to You now, correct it or delete it!
    Thanks – and beg Your pardon,
    d @ #72-#73

  • fredex

    csakDúk
    Sorry, I have zero experience in connecting a laptop to an adhoc network.

    You could try opening a terminal, doing “sudo sh” (which leaves you with root privileges, so BE CAREFUL WHAT YOU DO), then type /etc/cron.daily/find which will update the database used by the ‘locate’ command. when that’s done try doing “locate -i rt2860 | ls -ld” without the quotes. it should show you all files/directories with rt2860 in their names. one of them should be the “original” one you want to back up before installing Tim’s drivers. when done with the terminal either close it or type exit twice.

    Tim
    one more data point, as a follow up to my postings over the last day or so:
    the binary labeled as “wep” works fine on the WPA1 network at work AND my WPA2 PSK with AES at home. It APPEARS to be the same as the one I was using previously, before the lan at work suddenly went wonky on me (or at least connecting to it did) the other day.

    I cannot even pretend to understand why things went bad, or why what appears to be the same driver now doesn’t want to work on the neighbor’s open network. (in this case, it never sees a response to its DHCP requests).

    Clues?

  • tim

    @fredex

    Yes, the binary labeled as “wep” should work with WPA as well; it just happens not to on my access point. Things have moved on in that there are now more recent drivers, so you could also try using the latest.

    Tim

  • fishing

    Hello,

    I have problems with connections at my state library and it is an open unencrypted network, should I be looking at dl these new drivers. I have ZERO knowledge of linux, and very limited tech knowledge on how to even get into computer software. I mainly bought this to be a user, not a tweaker. I only wanted web access and word processing w the portability. And now , I am almost considering taking this thing back b’c it’s not doing what I thought it would.

    If i have no programming /tech experience, is this do-able, the above info is just baffling to me. It’s another language. I currently have a MAC OSX on my desktop, and thought the 901 would be as easy.

    Asus have said I need to get the library’s proxy server’s address, the library aren’t equipped with dealing with any tech issues, and sai they never have to give out proxy server addresses to anyone.

    When I am in the library . I have full strength signal (90-100%) and can even get into the library’s intranet, but cannot browse beyond that..

    can anyone help, PLEASE!?!

    Many thanks.

  • fishing

    oh, I have only just bought the 901 LInux, so it’s still got the stock Xandros on it. I’m not quite game to go wipe it and get Ubuntu at this stage, esp because I know it’ll be a time-consuming exercise, and I haven’t got the time right atm to be messing around with it. I’m meant to be studying not messing around with a new gadget.

  • Theodoros Ch.

    Hi!

    Thank you for your support and effort to try to fix WPA support on the EEE 901.

    I managed once to get it connected but with static IP with Adam’s kernel wwhich includes a version of your drivers.

    Apart from that I haven’t succeeded to connect it again. I get no response from the DHCP server of my router (USR 9108). Unfortunately, even if enter static IP I can’t get it connected.

    What is your recommendation and what drivers should I try to install?

    Thank you in advance,
    Theodoros Ch.

  • Theodoros Ch.

    This is my deamon.log
    Hope it helps.
    During the connecting procedure I can see from the router that the EEE 902 has associated and authorized successfully but it disconnects the moment it can’t get an IP.

    Oct 16 19:44:46 teodor-eeelaptop avahi-daemon[4843]: Registering new address record for fe80::222:43ff:fe24:694e on ra0.*.
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: [1224182714.637849] nm_device_802_11_wireless_get_activation_ap(): Forcing AP ‘TheGreeks’
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: User Switch: /org/freedesktop/NetworkManager/Devices/ra0 / TheGreeks
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Deactivating device ra0.
    Oct 16 19:45:14 teodor-eeelaptop avahi-daemon[4843]: Withdrawing address record for fe80::222:43ff:fe24:694e on ra0.
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Device ra0 activation scheduled…
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Activation (ra0) started…
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled…
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) started…
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 2 of 5 (Device Configure) scheduled…
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 2 of 5 (Device Configure) starting…
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Activation (ra0/wireless): access point ‘TheGreeks’ is encrypted, but NO valid key exists. New key needed.
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Activation (ra0) New wireless user key requested for network ‘TheGreeks’.
    Oct 16 19:45:14 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 2 of 5 (Device Configure) complete.
    Oct 16 19:45:42 teodor-eeelaptop NetworkManager: Activation (ra0) New wireless user key for network ‘TheGreeks’ received.
    Oct 16 19:45:42 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled…
    Oct 16 19:45:42 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) started…
    Oct 16 19:45:42 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 2 of 5 (Device Configure) scheduled…
    Oct 16 19:45:42 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
    Oct 16 19:45:42 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 2 of 5 (Device Configure) starting…
    Oct 16 19:45:42 teodor-eeelaptop NetworkManager: Activation (ra0/wireless): access point ‘TheGreeks’ is encrypted, and a key exists. No new key needed.
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘INTERFACE_ADD ra0^I^Iwext^I/var/run/wpa_supplicant0^I’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ‘OK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘AP_SCAN 1′
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ‘OK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘ADD_NETWORK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ’0′
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘SET_NETWORK 0 ssid 546865477265656b73′
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ‘OK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘SET_NETWORK 0 proto WPA2′
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ‘OK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘SET_NETWORK 0 key_mgmt WPA-PSK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ‘OK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘SET_NETWORK 0 psk ‘
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ‘OK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘SET_NETWORK 0 pairwise TKIP’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ‘OK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘SET_NETWORK 0 group TKIP’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ‘OK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: sending command ‘ENABLE_NETWORK 0′
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: SUP: response was ‘OK’
    Oct 16 19:45:43 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 2 of 5 (Device Configure) complete.
    Oct 16 19:45:44 teodor-eeelaptop avahi-daemon[4843]: Registering new address record for fe80::222:43ff:fe24:694e on ra0.*.
    Oct 16 19:45:48 teodor-eeelaptop NetworkManager: Supplicant state changed: 1
    Oct 16 19:45:48 teodor-eeelaptop NetworkManager: Activation (ra0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point ‘TheGreeks’.
    Oct 16 19:45:48 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 3 of 5 (IP Configure Start) scheduled.
    Oct 16 19:45:48 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 3 of 5 (IP Configure Start) started…
    Oct 16 19:45:49 teodor-eeelaptop NetworkManager: Activation (ra0) Beginning DHCP transaction.
    Oct 16 19:45:49 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 3 of 5 (IP Configure Start) complete.
    Oct 16 19:45:49 teodor-eeelaptop dhclient: There is already a pid file /var/run/dhclient.ra0.pid with pid 134519072
    Oct 16 19:45:49 teodor-eeelaptop NetworkManager: DHCP daemon state is now 12 (successfully started) for interface ra0
    Oct 16 19:45:50 teodor-eeelaptop NetworkManager: DHCP daemon state is now 1 (starting) for interface ra0
    Oct 16 19:45:53 teodor-eeelaptop dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 3
    Oct 16 19:45:56 teodor-eeelaptop dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 7
    Oct 16 19:45:56 teodor-eeelaptop NetworkManager: Supplicant state changed: 0
    Oct 16 19:46:03 teodor-eeelaptop dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 21
    Oct 16 19:46:06 teodor-eeelaptop NetworkManager: Supplicant state changed: 0
    Oct 16 19:46:06 teodor-eeelaptop last message repeated 2 times
    Oct 16 19:46:10 teodor-eeelaptop NetworkManager: Supplicant state changed: 1
    Oct 16 19:46:22 teodor-eeelaptop NetworkManager: Supplicant state changed: 0
    Oct 16 19:46:24 teodor-eeelaptop dhclient: No DHCPOFFERS received.
    Oct 16 19:46:24 teodor-eeelaptop avahi-autoipd(ra0)[8292]: Found user ‘avahi-autoipd’ (UID 105) and group ‘avahi-autoipd’ (GID 113).
    Oct 16 19:46:24 teodor-eeelaptop avahi-autoipd(ra0)[8292]: Successfully called chroot().
    Oct 16 19:46:24 teodor-eeelaptop avahi-autoipd(ra0)[8292]: Successfully dropped root privileges.
    Oct 16 19:46:24 teodor-eeelaptop avahi-autoipd(ra0)[8292]: Starting with address 169.254.4.63
    Oct 16 19:46:29 teodor-eeelaptop avahi-autoipd(ra0)[8292]: Callout BIND, address 169.254.4.63 on interface ra0
    Oct 16 19:46:29 teodor-eeelaptop avahi-daemon[4843]: Joining mDNS multicast group on interface ra0.IPv4 with address 169.254.4.63.
    Oct 16 19:46:29 teodor-eeelaptop avahi-daemon[4843]: New relevant interface ra0.IPv4 for mDNS.
    Oct 16 19:46:29 teodor-eeelaptop avahi-daemon[4843]: Registering new address record for 169.254.4.63 on ra0.IPv4.
    Oct 16 19:46:32 teodor-eeelaptop NetworkManager: Supplicant state changed: 0
    Oct 16 19:46:32 teodor-eeelaptop NetworkManager: Supplicant state changed: 0
    Oct 16 19:46:33 teodor-eeelaptop avahi-autoipd(ra0)[8292]: Successfully claimed IP address 169.254.4.63
    Oct 16 19:46:33 teodor-eeelaptop NetworkManager: DHCP daemon state is now 9 (fail) for interface ra0
    Oct 16 19:46:33 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 4 of 5 (IP Configure Timeout) scheduled…
    Oct 16 19:46:33 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 4 of 5 (IP Configure Timeout) started…
    Oct 16 19:46:33 teodor-eeelaptop NetworkManager: Activation (ra0) failure scheduled…
    Oct 16 19:46:33 teodor-eeelaptop NetworkManager: Activation (ra0) Stage 4 of 5 (IP Configure Timeout) complete.
    Oct 16 19:46:33 teodor-eeelaptop NetworkManager: DHCP daemon state is now 14 (normal exit) for interface ra0
    Oct 16 19:46:33 teodor-eeelaptop NetworkManager: Activation (ra0) failed for access point (TheGreeks)
    Oct 16 19:46:33 teodor-eeelaptop NetworkManager: Activation (ra0) failed.
    Oct 16 19:46:33 teodor-eeelaptop NetworkManager: Deactivating device ra0.
    Oct 16 19:46:34 teodor-eeelaptop avahi-daemon[4843]: Withdrawing address record for 169.254.4.63 on ra0.
    Oct 16 19:46:34 teodor-eeelaptop avahi-daemon[4843]: Leaving mDNS multicast group on interface ra0.IPv4 with address 169.254.4.63.
    Oct 16 19:46:34 teodor-eeelaptop avahi-daemon[4843]: Interface ra0.IPv4 no longer relevant for mDNS.
    Oct 16 19:46:34 teodor-eeelaptop avahi-daemon[4843]: Withdrawing address record for fe80::222:43ff:fe24:694e on ra0.

  • Roman

    So I tried both the WPA and WEP versions, no dice on my parent’s home network. Its WPA secured, and I get stuck at “pending”

    No problem finding the network, so hardware is working as it should, just can’t connect. Any ideas?

  • Gorilla

    I have tried both outlined in post 15 to no avail. I’m using a fresh EEE 901 with with BIOS 1603. I noticed on the ralink website that theres a 1.8.0.0. Has anyone tried to compile using that one yet?

  • Gorilla

    Guys. I have some news.

    I got sick of playing around with drivers so i started to play with my AP.

    Turns out the WPA key cipher was set to tkip. Changing it to Auto fixed everything.

    Hope this helps with someone.

  • SimonP

    Tim,

    Thank you for all your work on this. I installed your version of the WPA driver on my 901 and it can now connect to my D-Link DI-514 AP, which is a great step forward.

    The only problem is that the AP has to be broadcasting its SSID for the 901 to find it, otherwise the WPA supplicant just keeps scanning indefinitely. I also note that iwconfig seems unable to set the SSID (it doesn’t produce an error – the command just seems to have no effect). I’m no expert on WiFi and I am wondering if these two problems are symptomatic of the same cause Has anyone else experienced this and found a way around it?

    SimonP

  • sebastian

    Nope it did not work for me… after i did it i get a new error now the wifi wont even see the network it just sats unary operator expected line 195 line 198 line 201. i am not a newbie but this is not what i expect from asus i have just recommended it to all friends since we got of so well but now i am starting to doubt it… i have no idea what to do

  • sebastian

    and i was so convienced it was going to work i took no backup…

  • Dave

    I was having “some” problems with connecting to some networks but now it doesn’t work at all – I too got too convinced that it would work or that it would just update the drivers… think twice next time as now it doesn’t work at all!

  • james

    What the hell is this pathetic device doing to our heads.It should state you need to be a programmer on the box to set this up to work.Asus should be ashamed of themselves to allow the 901′s to be sold while it’s most important application of networking was all over the place.I’m not wasting any more of my precious time on this fat useless nintendo joke.Please God send us a Macbook nano soon

  • PurplePenny

    I told that the reason I cannot connect to my router is that my WPA passphrase contains spaces. I’m a Linux newb so before I start messing a around can you tell me whether this fix address that issue?

    I had the same problem with an old router and WEP when I first got the 901 last summer but I got round it then by typing the passphrase in hex… which doesn’t work with WPA.

    Like you Tim I wonder what Asus are thinking! As others have said this should work out of the box, we shouldn’t have to fiddle this much. Asus support have been hopeless, they don’t even seem to be aware that this is a known problem posted repeatedly on Linux forums! I realise that I could change the passphrase to one without spaces but spaces are implicit in the word passphrase and I don’t see why I should have to go around changing the settings on the 2 PCs, 3 laptops (incl a Mac) and 1 printer that are already accessing the router with no problems.

  • gzip

    Wow, so easy. The rt2860wep.tgz version works for WPA too. I’m running Ubuntu 8.10 Intrepid. You’re the man Tim!

  • KOldham

    I’ve just received my 901 today and am having problems despite a Linux history back to V1.3.

    The device out of the box can see the access points, iwconfig & ifconfig look OK apart from a low datarate, but the signal level was 0% until I installed Tim’s new module. Now the signal level is 10% – my AP – a WG602 in WEP mode shows the 901 as disconnected all the time except when the 901 is off when the entry disappears. So as far as I can tell everything is OK but I can’t even ping the AP. I’ve had plenty of problems/experience with Linux wireless connections in the past which have all been resolvable but this is a puzzle.

  • KOldham

    Got it working !

    Followed some clues from ifconfig & iwconfig for the 901 compared to my other Linux laptop and googled more specifcially.

    This link http://bbs.archlinux.org/viewtopic.php?pid=417599 gave me the info necessary to write a script to make the d*** thing work. Just altering the .dat file as suggested first did not work.

    Will explore this in more detail

    Many thanks for the great work on the module Tim

  • Ben Selinger

    I had no problems with version 1.8.0.0

    wget http://www.ralinktech.com.tw/data/drivers/2008_0918_RT2860_Linux_STA_v1.8.0.0.tar.bz2

    tar -xvjpf 2008_0918_RT2860_Linux_STA_v1.8.0.0.tar.bz2
    cd 2008_0918_RT2860_Linux_STA_v1.8.0.0
    vi os/linux/config.mk
    #set the following
    HAS_WPA_SUPPLICANT=y
    HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y

    make
    sudo make install
    sudo modprobe -r rt2860sta
    sudo modprobe rt2860sta

    everything should work now.

  • Ben Selinger

    P.S. WPA, WPA2, WPA2 Enterprise, WEP, and open, are all working correctly.

  • Ben Selinger

    P.P.S. I compiled against the 2.6.27-13-generic kernel. The eeepc kernel is missing kernel debugging and timer support, which means a lot of ACPI battery functions are not reported.

  • C Itle

    Tim,

    I just wanted to say thank you. Post 15 is the real answer. I talked to ASUS tech support and searched the internet for 7 hours before finally finding this solution. Thanks, again.

  • bt27uk

    Hello,

    First – many thanks to Tim, and others, for all their efforts on this topic and making their advice and experiences available.

    I am running an Asus 1000 and have successfully connected using WEP in the past without problem. Today I started trying to connect with WPA…and the trials and tribulations of that are how I ended up on this site.

    Before I took the leap of seeing if post 15 could help me, I read through most of the other posts, and number 82 from Gorilla caught my eye. And I’m glad it did.

    I checked, and my WPA was set to TKIP by default. I changed this to WPA2-PSK (AES) in my internet wireless settings, edited my network settings accordingly on my Asus machine (using the graphical Network Connections window), et voila!

    So, making the rather large and hopeful assumption that this is a real fix, as opposed to a freak connection success, Gorilla’s suggestion may be a simple fix for some.

  • Jon

    This solution didn’t work for me, but hacking a few of the config files as described here: http://forum.eeeuser.com/viewtopic.php?id=48375 for the 901 to get it to correctly navigate shared keys (restricted instead of open networks) worked like a charm!

  • Walter

    Hi Ben,

    Thanks for this information, after a long search I finally got it working with the description in
    Ben Selinger
    March 4th, 2009 at 5:42 am
    I had no problems with version 1.8.0.0

    FYI, I used the latest 2010_01_29_RT2860_Linux_STA_v2.3.0.0.tar.bz2 instead, which I downloaded from http://www.ralinktech.com/support.php?s=2

    Kind regards

  • Diego

    Walter,
    Please, can you let me know the steps to install 2010_01_29_RT2860_Linux_STA_v2.3.0.0.tar.bz2.
    I’m new in Linux and I don’t know how I can install:
    I run the command make install but I had the folowing message:

    make -C /home/network/Share_SrvLnx/Network/2010_01_29_RT2860_Linux_STA_v2.3.0.0/os/linux -f Makefile.6 install
    mkdir: no se puede crear el directorio «/etc/Wireless»: El archivo ya existe
    make[1]: se ingresa al directorio `/home/network/Share_SrvLnx/Network/2010_01_29_RT2860_Linux_STA_v2.3.0.0/os/linux’
    rm -rf /etc/Wireless/RT2860STA
    mkdir /etc/Wireless/RT2860STA
    cp /home/network/Share_SrvLnx/Network/2010_01_29_RT2860_Linux_STA_v2.3.0.0/RT2860STA.dat /etc/Wireless/RT2860STA/.
    install -d /lib/modules/2.6.28-17-server/kernel/drivers/net/wireless/
    install -m 644 -c rt2860sta.ko /lib/modules/2.6.28-17-server/kernel/drivers/net/wireless/
    install: no se puede efectuar `stat’ sobre «rt2860sta.ko»: No existe el fichero ó directorio
    make[1]: *** [install] Error 1
    make[1]: se sale del directorio `/home/network/Share_SrvLnx/Network/2010_01_29_RT2860_Linux_STA_v2.3.0.0/os/linux’
    make: *** [install] Error 2

  • mishal

    dear sir i have wi-fi signal avilavile but not warking.everithing ok but receving 0