[Announce] kernel-power stable v49 in Extras-Testing - Page 284 - maemo.org

Active Topics

Error after installing Leste on sdcard (18)
to Maemo 7 / Leste by Maemish - 5 hrs, 33 mins ago
Maemo 20th Anniversary (4)
to Brainstorm by teroyk - 2 days ago
Nokia Booklet 3G (RX-75) Drivers (64)
to Alternatives by teroyk - 2 days ago
Porting apps to Leste (46)
to Maemo 7 / Leste by teroyk - 4 days, 4 hrs ago
more...

Page 284 of 300

284

Thread Tools

magic_doc	2012-02-18 , 13:33
Posts: 87 \| Thanked: 80 times \| Joined on Sep 2009	#2831

Originally Posted by woody14619

One thing I find odd though, why is fmtxd running on your system at all? On my N900, the only time that runs is when FM has been enabled and it's actively transmitting audio. By default it runs at start up but goes away on it's own after a short delay. So the fact that it was even running implies to me that something was trying to activate it?

During my effort the track down battery draining programs and processes on n900 while it's idle I found out the same: the fmtxd was waking up the cpu all the time when it is not needed.
So I tried out the modified binary from here and the problem was solved- the fmtxd is now shut down completely when it is not used.

HTH and HAND

Michael

Quote & Reply |

The Following 2 Users Say Thank You to magic_doc For This Useful Post:
Estel, woody14619

freemangordon	2012-02-18 , 13:59
Posts: 3,074 \| Thanked: 12,964 times \| Joined on Mar 2010 @ Sofia,Bulgaria	#2832

@Pali, patches 0001-mtd-fix-a-huge-latency-problem-in-the-MTD-CFI-flash-.diff and 0002-mtd-change-struct-flchip_shared-spinlock-locking-int.diff are still enabled in series file, please disable them as it is confirmed those cause reboots/slowdowns.

Also I am unable to use QtMobileHotspot with USB, device reboots in 1-2 seconds after connecting USB cable. Please anyone to test if it is working for him with latest KP. I suspect it might be USB sysfs notify patch, will disable it and will test.

EDIT:
it is not USB sysfs notify which bugs the kernel.

Last edited by freemangordon; 2012-02-18 at 14:11.

Quote & Reply |

The Following 4 Users Say Thank You to freemangordon For This Useful Post:
don_falcone, Estel, nkirk, reinob

	Gusse	2012-02-18 , 14:39
	Posts: 168 \| Thanked: 206 times \| Joined on Apr 2010 @ Finland	#2833

Originally Posted by freemangordon

Also I am unable to use QtMobileHotspot with USB, device reboots in 1-2 seconds after connecting USB cable. Please anyone to test if it is working for him with latest KP. I suspect it might be USB sysfs notify patch, will disable it and will test.

EDIT:
it is not USB sysfs notify which bugs the kernel.

Running latest KP (including git updates from 2 days ago) and I'm writing this reply from laptop using USB QtMobileHotspot. No problems.

Quote & Reply |

The Following 3 Users Say Thank You to Gusse For This Useful Post:
Estel, freemangordon, nkirk

freemangordon	2012-02-18 , 14:53
Posts: 3,074 \| Thanked: 12,964 times \| Joined on Mar 2010 @ Sofia,Bulgaria	#2834

Well, seems I am hitting this. Will prepare a patch and will send it to Pali (if this solves the kernel crash)

EDIT: Bug smashed, patch sent to Pali.

Last edited by freemangordon; 2012-02-18 at 15:48.

Quote & Reply |

The Following 10 Users Say Thank You to freemangordon For This Useful Post:
don_falcone, Estel, fw190, Gusse, JSTAR, kent_autistic, nkirk, reinob, vi_, woody14619

freemangordon	2012-02-18 , 17:46
Posts: 3,074 \| Thanked: 12,964 times \| Joined on Mar 2010 @ Sofia,Bulgaria	#2835

Originally Posted by pali

This is because that wifi driver is compiled against old kernel-power. For proper working each module must be compiled against actual kernel version. But there was nothing changed in wifi stack, so packet injection wifi driver worked. But now in kernel power are some changes (disabled mesh, ...) and binary wl1251 packet injection driver is incompatible with last kernel-power...

So, someone should build them against KP50

Quote & Reply |

The Following 3 Users Say Thank You to freemangordon For This Useful Post:
don_falcone, Estel, nkirk

g0r	2012-02-20 , 15:51
Posts: 105 \| Thanked: 87 times \| Joined on Jun 2011 @ Unknown	#2836

I have tried the latest kp pre-50 and worked no problems for me with the exception of wifi lxps driver so I went back to freemangordons pre-50 and as usual I do a autoremove & autoclean only this time after autoclean a lot of my aps with lots of lib files where deleted resulting in a mess. I could not get any updates as repositories reported errors ex: "sub-process bzip2 returned an error code (1)" and "applet not found" so I had to reflash my device. Not sure if there is a bug by reverting back to a previous KP you can lose files (being deleted) by trying to autoclean your device, can anyone else confirm the above.

Quote & Reply |

	woody14619	2012-02-20 , 18:49
	Posts: 1,455 \| Thanked: 3,309 times \| Joined on Dec 2009 @ Rochester, NY	#2837

Originally Posted by magic_doc

So I tried out the modified binary from here and the problem was solved- the fmtxd is now shut down completely when it is not used.

I think this may be a regional thing? One would hope that such a setting wouldn't change behavior like this, but all things are possible with closed-source blobs.

Quote & Reply |

The Following User Says Thank You to woody14619 For This Useful Post:
Estel

pali	2012-02-21 , 16:33
Posts: 2,154 \| Thanked: 8,464 times \| Joined on May 2010	#2838

Originally Posted by freemangordon

@Pali, patches 0001-mtd-fix-a-huge-latency-problem-in-the-MTD-CFI-flash-.diff and 0002-mtd-change-struct-flchip_shared-spinlock-locking-int.diff are still enabled in series file, please disable them as it is confirmed those cause reboots/slowdowns.

Also I am unable to use QtMobileHotspot with USB, device reboots in 1-2 seconds after connecting USB cable. Please anyone to test if it is working for him with latest KP. I suspect it might be USB sysfs notify patch, will disable it and will test.

EDIT:
it is not USB sysfs notify which bugs the kernel.

I builded new deb packages. I disabled both patches + included that you sent me.

Quote & Reply |

The Following 5 Users Say Thank You to pali For This Useful Post:
Estel, freemangordon, Netweaver, nkirk, strange1712

mr_pingu	2012-02-21 , 16:47
Posts: 1,163 \| Thanked: 1,873 times \| Joined on Feb 2011 @ The Netherlands	#2839

Be prepared, long post of kernel-power-settings which is driving me crazy. Really kernel-power settings is gone nuts.

In this post I describe exactly what steps I took to get this result, and it's reproducable 10/10.

I already thought kernel power-settings was acting weird on me so I ran:

Code:

apt-get remove --purge kernel-power-settings
rm -r /home/user/.kernel

That last command was to be sure there were no bits left of my personal config files.

This part describes why I am posting this...
After removing kernel-power-settings, I installed kernel-power-settings again by issuing

Code:

sudo gainroot
apt-get install kernel-power-settings

Followed by loading the default config

I thought these voltages were quite weird, and yet it becomse even weirder, here the voodoo kicks in, when I recheck the config I just loaded with nano

WTF

, other values in the config file than kernel-config show reports... Especially freq 500 and 600 are weird

I did not set any profile as default so why don't we reboot and let it load the original "nokia" config? Easy said easy done:

Then load the default profile and check again. Seems quite normal, except still that voltage voodoo bug ( 550 and 600)

Let's make the default profile default so it loads at boot

Reboot...
Checking again

Voltages seems normal atleast they are linear increased with frequency increasement, not the weird jumps as when loading it. Though it still makes me wonder where the vuck do these values come from as they are definitely not in the config file(see screenshot 2, the one opened in nano)