Hi All,

I just google a night to allow my N9 use 5Ghz. That's the regulatory domain problem.

The solution was quite easy: just remove /usr/lib/crda/regulatory.bin file. Then my N9 is able to see all the channels available

I switched it to 5Ghz and after executing '/sbin/iwconfig wlan0 power off' the awful delays (ping the device >100ms) gone, and I have ping 1ms, full speed, but probably less battery life, of course.

Any explanation as to how removing the file affects 5GHz availability?

isnt is locked for some countries because they have laws there prohibiting the use of wlan?

install iw for harmattan with Debinstaller and you will have possibility to change regulatory domain.

iw reg get - shows current domain and allowed ranges
iw reg set DOMAIN - sets choosed domain

/etc/iw/domain.conf - contains domain which will be set after reboot (regulatory domain always set to default after phone shutdown)

enjoy

I just installed the iw package as you suggested, but it says not found when I try to run it in console.

I see it's located in /usr/sbin/ and tried to run it from there as user and as root, still no success

export PATH=$PATH:/usr/sbin
iw reg get
iw reg set IT

it handy to have pull PATH line in /etc/profile, instead of default one

Thanks, that worked!

It seems there is an even more easy solution for the 5Ghz problem. Some frequencies seem to be disabled, so I just choosed in my router a frequency that was allowed and tada, I can see my 5Ghz WLAN.

To show, just use:

iw list

and lookout for Frequencies:

sample output from my N9: http://pastie.org/8205109

What do you mean by "no success" and what "by tried to run it from there". Please be more specific.

If ash says file not found and you have confirmed that /usr/sbin/iw exists, then I presume you are doing something wrong.

Let's verify it exists:
There's several ways to run executable files.
Either you use full path of the file:
...or you can use relative path, for example ( "./" means present working directory and "../" would mean one below it ):
...or if you have /usr/sbin in your current user's (root in this case) PATH variable,
...then you can just:

Were you doing this DOS/WIndoze thing where you _assumed_ that the current directory would be part of the search-path for executables/commands ?

In Unix/Linux, simply "cd"-ing to a directory containing a command and then typing the commandname won't work, unless you then actually type "./commandname".

Do you see what I mean ?

@LinuxClub just because of security reasons. But you can always add $PWD to PATH, and voila!