No need for a new thread.

Well, indeed, depending on that package will pull KP50 too, but you can make another(dummy) package too and depend on either dummy package or this one. And there is no need cleven to depend on the exact version of the package(use ">=" in debian/control), that way when a new KP enters repos some day, I will build a new version of linux-backports-modules-power and it should be automatically pulled on kernel upgrade. Or if you have a better solution I am OK with it.

Or you can pull that one and rebuild it against stock kernel (just a few modifications are needed) if bleeding-edge drivers work on stock kernel. I can do it too of course (but not today ).

Actually I am not .deb packaging guru, so any piece of advice is welcome

In a previous post, I unlocked channel 12 and 13 on my N900 with a simple modification of the regulatory domain variable. Being the 802.11 junkie I am, I also wanted to look at upping the TX power so I could really reach out and touch someone. This is normally controlled by CRDA and wireless-regdb which is digitally signed database of regions containing allowed channels and power usage. The great thing is, it allows generation of a self-signed database for binary reading - which means anybody with a brain the size of a lollipop can override it. Unfortunately for me. CRDA kicked in after 2.6.28 (wasn't backported with compat-wireless/bleeding-edge wl12xx) and left the old static regulatory domain setting in kernel space. No big deal. I modified the hardcoded values for JP to bump 20dBm to 30dBm

REG_RULE() is passed 6 arguments, first the low frequency (ch1) with a base underlap (2412MHz-10/1MHz), the upper frequency (ch14) with a high overlap (2484MHz-10/1MHz), band spacing (4MHz+1MHz over/under for total 5MHz), max antenna gain (600mBi), max EIRP (30dBm) and I have no idea what the last arg is for.

Patch in whatever new CRDA linker you want recognized for high transmit. I called mine "HX" and build your new modules. Drop them into /lib/modules/[whateverkernelyourun] and the easiest way to make sure they're loaded in proper succession is to reboot.

You can check your changes by watching dmesg and you're looking for the line that says;
2402000 KHz - 2494000 KHz @ 40000 KHz, 600mBi 3000mBm

This should indicate the driver is allowing 30dBm on all 14 channels. I truly don't know if the WL1251 chip stores a max transmission power in EEPROM or tertiary firmware with wl1251-cal nor have I done any pseudo-scientific testing yet.

What I do know is that I probably have the only phone in the world, that can completely disrupt and hose any 802.11b/g/n network with the push of a button...your phone is cool too though, you've got apps, right?!

In fact, I use iw reg set JP all the time, so I modified every script loading drivers in my device to do it automatically.

Hello,

I have two issues after installing cleven 2.5.2 :
- I can't scan for network after setting monitor mode and loading injection driver ;
- I have not the reaver/wps button on the interface whereas I have reaver and walsh installed.

1) When I click on "scan" button I have the following error :
By looking loaded modules I can't see wl1251. I see wl12xx instead. So I launched load.sh script from /opt/cleven (with -v2 switch) and I can see the right driver from cleven loaded. But, I can't set this driver to monitor mode, iwconfig command show me managed mode on wifi interface (wlan0).

2) I installed reaver and walsh and I can use them but cleven interface didn't show the reaver or wps button.


Regards,