Re: [Announce] kernel-power stable v53 in Extras Testing
 

In kp52 packet injection driver cause kernel panic and reboot when wifi was set to ad-hoc mode... This should be fixed. Power problems could be fixed too. But both needs to be tested by more people if it is really stable...

Benefit is to not have two (or more) drivers for wifi and unloading/loading when you need to switch between them. Currently for using packet injection by default is needed some hack in /etc/modprobe.d/ (which my script in first post is doing). And it would be great to get rid of it...

Userspace tools for using packet injection drivers can be fixed too if there are problems...

But first I need tests and discussion about possible problems...

Re: [Announce] kernel-power stable v53 in Extras Testing
 

I think I have to report a problem.
Enabled bleeding edge via advanced interface switcher and after leaving house (wifi range) I did not detect any higher power consumption. But when getting home there was no detection of my wlan nor was any other wlan shown. So I restarted icd2 as well as wlancond to no avail. Only stopping and restarting wlan from aifs applet let the wlan search succeed. :confused:

Re: [Announce] kernel-power stable v53 in Extras Testing
 

@peterleinchen: thanks for testing. can you use also script from first post for enabling packet injection drivers? maybe there can be problem with other applications/applets (as process of replacing drivers is not simple).

Re: [Announce] kernel-power stable v53 in Extras Testing
 

Yep, I can do so.
But I believe aifs does it already with same mechanism.

Just a few minutes happened again, wil enable now stock drivers and switch with your script.


--edit
here are aifs scripts
wlan_load0 stock
wlan_load1 bleeding
get_wlan_path checks availability

Re: [Announce] kernel-power stable v53 in Extras Testing
 

That would be great! No more fiddling with switching between drivers to get pocket injection or save power! :)

And doing so would in a way force people using kernel power to use this version of drivers, so bug hunting would be much much faster (more testers!).

Re: [Announce] kernel-power stable v53 in Extras Testing
 

Hey pali,
just went out (into the cold ;)) to check.
I have done:
script unload
script load
script enable

And same behaviour.
I had to do another
script load
to get my wlan connectivity back :confused:
(and had high power drain after doing so)

--
you may also check aifs scripts (see my earlier post)

Re: [Announce] kernel-power stable v53 in Extras Testing
 

Same issue here.. tried to reboot several times, disabling and reenabling shortcutd proximity sensor option in Settings, but no way to get it working again..
Any ideas on how to fix it? :confused:

Re: [Announce] kernel-power stable v53 in Extras Testing
 

Maybe this is related with shortcutd not working: in dmesg I see proximity log only while making a call;

otherwise I can trigger proximity sensor but no log results in dmesg.

p.s. happy new year to every maemo user in TMO!! :) :)

Re: [Announce] kernel-power stable v53 in Extras Testing
 

Now I looked at this problem... and proximity gpio-switch is for unknown reason disabled in kernel. I looked at diff between kp52 and kp53 and there is nothing which can disable gpio-switch. So problem must be somewhere in userspace. Maybe CSSU or U-Boot? Maybe other application?

This sysfs can enable or disable proximity gpio-switch:
$ cat /sys/devices/platform/gpio-switch/proximity/disable

And this command enable it (until reboot):
$ echo 0 > /sys/devices/platform/gpio-switch/proximity/disable

Re: [Announce] kernel-power stable v53 in Extras Testing
 

So it is problem of mce which is in cssu, see:
https://gitorious.org/community-ssu/...witches.c#L324

It disable proximity gpio-switch if call is not active or not ringing.

@freemangordon: what to do now?