They will continue to work.

Hello. I have a dependency problem with "Maemo Kernel power config for multiboot". If i uninstall it, will i be able to install it again to use nitdroid?

when i click on the update on HAM it says i need pc suite to update it. how to solve that?

Since I m not afraid of having to flash, I just ran root and then apt-get update and apt-get upgrade and lived happily ever after.

However, the literal cause of the problem is you don't have enough memory to update. You could minimize the number of programs you hane installed and remove installed repositories and do other tricks to increase rootfs memory.

Or you could actually install pc suite.

Go to see the details and you will see what's the problem. You will need to unistall something, in my case it is "Maemo Kernel power config for multiboot". But i won't do it because i don't want to lose nitdroid.

sorry for the off topic

Brian_7 you will lose your N900 with multiboot and nitdroid

I was worried that this would conflict somehow with MaeMeeMo, but I haven't had problems. My N900 seems faster than ever -- feels like it's gaining on my N9!

Now it works
After the update with thumb system after restart uses about 90mb instead of 106 without it. I hope that this project will move on as the benefits are clear!!!

Thank you for your hard work freemangordon (and merlin1991 for hosting it )

A good test of Thumb2 power might be using a rebuilt version of Firefox, as it's the most memory offender application for the N900.

with this i suppose the performance lost by using thumb2 is less noticable in low memory situations due to the gain made reducing i/o to swap. great achievement getting this far but as it is my only device i'll hold off for now until its had a little broader testing.

i noticed you stated it reduced memory footprint by about 30mb. it would be interesting if someone could put together a comparison of memory usage for some common apps compiled with and without thumb support to illustrate the difference.

all we need now is a way to avoid swap fragmentation, maybe a different allocation startergy @ kernel level. ereswap solves it in userland for now but, no direspect intended, i don't feel it is the best solution.