Active Topics
-
Longtime users: What device(s) are you using today? (52)
to General by Wikiwide - 1 day, 5 hrs ago -
Registering (1)
to General by Halftux - 1 day, 20 hrs ago -
Applications Wishlist (55)
to Maemo 7 / Leste by sixwheeledbeast - 2 days, 22 hrs ago -
Error after installing Leste on sdcard (2)
to Maemo 7 / Leste by insanelysexy - 4 days, 22 hrs ago -
Using LM2596 DC-DC for N900 (7)
to General by insanelysexy - 6 days, 15 hrs ago - more...
| The Following 15 Users Say Thank You to lxp For This Useful Post: | ||
|
2010-12-02
, 21:28
|
|
Posts: 34 |
Thanked: 15 times |
Joined on Jan 2010
|
#112
|
Hi, i don't know if this is the correct place to ask this.
I've been trying to compile rtl8187.ko (r8187) for N900 and kernel-power v46... (Thanx to h-e-n)
Ok got it compiled but ...
ieee80211_crypt-rtl.ko
ieee80211_crypt_wep-rtl.ko
ieee80211_crypt_tkip-rtl.ko
ieee80211_crypt_ccmp-rtl.ko
ieee80211-rtl.ko
insmoded ok
but r8187.ko fails to insmod
insmod: error inserting 'r8187.ko': -1 Unknown symbol in module
I'm using this source http://dl.aircrack-ng.org/drivers/rt...ux_26.1010.zip
Can someone try to compile with scratchbox?
I've been trying to compile rtl8187.ko (r8187) for N900 and kernel-power v46... (Thanx to h-e-n)
Ok got it compiled but ...
ieee80211_crypt-rtl.ko
ieee80211_crypt_wep-rtl.ko
ieee80211_crypt_tkip-rtl.ko
ieee80211_crypt_ccmp-rtl.ko
ieee80211-rtl.ko
insmoded ok
but r8187.ko fails to insmod
insmod: error inserting 'r8187.ko': -1 Unknown symbol in module
I'm using this source http://dl.aircrack-ng.org/drivers/rt...ux_26.1010.zip
Can someone try to compile with scratchbox?
|
|
2010-12-02
, 22:05
|
|
Posts: 422 |
Thanked: 244 times |
Joined on Feb 2008
|
#113
|
That is your third cross-post for this issue.
__________________
Servwise Advanced Hosting - Better, Faster, Smarter
Hum Consulting - IT and Marketing services to sing about
Servwise Advanced Hosting - Better, Faster, Smarter
Hum Consulting - IT and Marketing services to sing about
| The Following User Says Thank You to paulkoan For This Useful Post: | ||
|
|
2010-12-03
, 14:50
|
|
Posts: 34 |
Thanked: 15 times |
Joined on Jan 2010
|
#114
|
Sorry for that, i´ve been researching threats about this issue, and it seems to be lost in space.
I suppose im starting to get desperate.
I suppose im starting to get desperate.
|
|
2010-12-13
, 16:31
|
|
Posts: 1,042 |
Thanked: 430 times |
Joined on May 2010
|
#115
|
Just bumping this thread...
Any updates for the modified drivers release?
Any updates for the modified drivers release?
|
|
2010-12-16
, 16:43
|
|
Posts: 1,042 |
Thanked: 430 times |
Joined on May 2010
|
#116
|
Another bump only for this post.
Originally Posted by lxp
I just want to give some updates regarding the packet injection driver:
I will definitively publish the patches on my own, because Neopwn hasn't answered my mails even one week after the deadline I set.
I am currently working on fixing a bug with managed/station mode. I have already invested much time into debugging this bug, but I still need some time to get the optimal workaround. (It seems to be a firmware issue.)
After I have fixed the bug I will forward-port the patches onto the current wireless-testing tree and do some testing with the current power kernel. Right before testing I also have to update my phone to PR1.3. (Still had no time to do that)
|
|
2010-12-19
, 22:02
|
|
Posts: 50 |
Thanked: 444 times |
Joined on Apr 2010
@ Austria
|
#117
|
Another update regarding the packet injection driver:
It seems that I finally found the firmware issue causing the bug in managed/station mode. It wasn't too easy to figure this out due to the closed-source firmware, but I found a workaround.
Today I have successfully verified it at various locations and now I am continuing with upgrading my phone to PR1.3 and forward-porting the patches to current wireless-testing.
If nothing went wrong I may release the driver before Christmas.
It seems that I finally found the firmware issue causing the bug in managed/station mode. It wasn't too easy to figure this out due to the closed-source firmware, but I found a workaround.
Today I have successfully verified it at various locations and now I am continuing with upgrading my phone to PR1.3 and forward-porting the patches to current wireless-testing.
If nothing went wrong I may release the driver before Christmas.
| The Following 28 Users Say Thank You to lxp For This Useful Post: | ||
|
|
2010-12-19
, 22:55
|
|
Posts: 1,042 |
Thanked: 430 times |
Joined on May 2010
|
#118
|
*Cheers* lol You made my day lxp! ^_^
|
|
2010-12-21
, 19:47
|
|
Posts: 19 |
Thanked: 2 times |
Joined on Dec 2009
|
#119
|
Gents,
Is there a repo I need to add to see the wireless-testing tree?
Thanks!
houz
Is there a repo I need to add to see the wireless-testing tree?
Thanks!
houz
 |
|
2010-12-22
, 03:44
|
|
Posts: 1,030 |
Thanked: 792 times |
Joined on Jun 2009
|
#120
|
No. Patches are going upstream and will get backported by the required people. Please wait until the kernel is released publicly, and any accompanying drivers can be compiled and provided.
I will include a new modified power kernel, when I publish the driver. After that the required changes will hopefully be incorporated into the power kernel itself, so we don't need modified power kernels in the future. (To not confuse people: that doesn't mean power kernel will support packet injection "out-of-the-box", it only means that the power kernel should then be compatible with compat-wireless)