View Single Post
Posts: 393 | Thanked: 67 times | Joined on Feb 2010
#70
For more information, I have recently updated to the newest Power Kernel from the previous version, it is very possible that the problem with Kismet started showing up after upgrading to the latest Power Kernel (Power Kernel 2.6.28.10power37).

Here is the basic timeline (if it is of any help I installed PR 1.2 the day it was released, installed the newest available Power Kernel, and things were running smoothly, Kismet was working well. About a week after PR 1.2 is released Titan released his new version of the Power Kernel, I upgraded to it, and didn't check Kismet for a while. I finally had some time to try Kismet and I started experiencing the previously stated problems with Kismet.

This would lead me to suspect the new Power Kernel causing the issue to come back, but this is more of a hypothesis than a fact.

Is anyone running the latest Power Kernel 2.6.28.10power37 with the latest Kismet, do you experience problems?

Thanks

Originally Posted by mail_e36 View Post
Hello everyone,

It appears I spoke too soon in my previous posting when I said there is no problem under PR 1.2.

Indeed all the same problems I had with my customized PR 1.1 have now come back with PR 1.2 (I did a completely fresh flash of everything on my N900, not an upgrade from PR 1.1), including the problem which "AutoGroups" everything came back.

Additionally, at times when I start up Kismet it cannot even bind to the wireless interface, with the console reading "capture source 'wlan0' doesn't appear to use the set_prismhdr i control". Selecting "Close Console Window" persistently shows zero visible networks in areas of high network concentrations.

Sometimes a reboot resolves the problem, more often a reboot does not resolve the problem.

I am running Power Kernel 2.6.28.10power37, dated May 26th 2010. Do we suspect this to be a driver issue?

Has any experience similar issues?