Joys of Atheros

Have been playing with the Nokia 5800 and Joikuspot which turns the 5800 into an ad hoc wireless 3/3.5G router which is nice, very, very nice.

Except that ad hoc on the U810's Atheros is distinctly non-trivial. With the madwifi (now moved to http://madwifi-project.org) drivers, the athX devices are VAP's (virtual access points) created from the root device, wifi0 using wlanconfig . The important thing to realise is that the athX device only supports a particular wireless mode. By default (in OpenSuSE 11.0, anyway) this is sta which is workstation infrastructure mode and requires an access point. The Joikuspot network shows up in KNetworkManager but you can't connect.

Fair enough, you can create another VAP to support adhoc mode as madwifi allows you to have multiple VAP's which allows you to neat things like use your U810 as a wireless repeater or gateway. Except there's a bug - the one sort of VAP you that doesn't play nicely in multiple VAP configurations is adhoc. And judging from project discussions fixing adhoc is not exactly top of the priority list since it's not "enterprise" and anyway we're meant to be moving to the fully open ath5k driver anyway.

The alternative then, is to destroy the default sta mode VAP and create the adhoc one so it is the only one. To their credit, the madwifi website does document this all quite clearly although it does confuse KnetworkManager a little. Then all is good except, of course, I can't roam and connect to the vast majority of infrastructure mode access points out there until I reverse the process. I did start setting up a couple of scripts to switch between the two modes when I encountered another issue with adhoc VAP's which is that every so often I was getting a hard lockup and I mean power-cycle hard.

So it's off to Bluetooth DUN profile tethering for me for a bit (shame the 5800 doesn't have a PAN profile...). Which might turn out for the best, since Bluetooth power consumption on both the 5800 and U810 is much lower than for wifi. Not as elegant though IMHO :(.

P.S. ath5k doesn't even recognise the card.

P.P.S. I tried swapping the Atheros for an Intel Wireless PCI-E card in the U810. No dice - the BIOS looks for the Atheros and doesn't seem to enable the PCI-E slot if it's not there.

Atheros hacking

Now I have Linux on, I will be downloading stuff and patching stuff so I want some connectivity. Wired ethernet works OK on my U810 with OpenSuSE 10.3 - some people have reported acpi issues but I have it enabled with no problems. However, this is a mobile device so I want to get wireless working.

I got the U810 in the USA and the Atheros WiFi chipset therefore has brain damaged firmware that restricts you to channels 1-11 for 802.11b/g. This is, of course, completely stupid for a device designed for mobility so it needs to be fixed but it appears that firmware updates are not exactly thick on the ground.

A bit of trawl takes me to Tamosoft who have something called CommView for WiFi which, if I was using Windows, seems to be quite a nice WiFi monitoring/analysing app. along with some other network tools. However, there is also an Atheros firmware adjuster mentioned on this page. You'll need to download the CommView for WFi trial to run it but it works. So now I have channels 1-13 (or 14 if you select a Japanese locale).

So there was a reason I kept that Vista partition about...

Now to get the Linux Atheros drivers, which aren't included in OpenSuSE because of licence conflict issues with Atheros' binary-only HAL. The madwifi guys are working on the problem but in the meantime, the OpenSuSE site has these instructions which do the trick.

The madwifi one-click-install also adds the OpenSuSE online repository to the software repository list. This contains all the stuff on the DVD and more so, now I have it in, I go into Yast and disable the DVD as a software source - that way, if I download anything that needs the DVD it will go to the online repository instead which is fine now I have WiFi working.