View Single Post
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#239
Originally Posted by BertvanDorp View Post
Ran the 'old' settings:

Device is still responsive after a day. Tracker runs, camera is able to launch (this didn't work with Swappolube settings and SwapSet), but now I'm getting the message that states I can't send or reviece messages: device memory full.

Trying new settings now. @mr_jrt: including in SwapSet would be great, since it's clearly the only way to get ramz to work properly. You can also set Swappolube as a conflicting package, so users have to choose (does this make sense?).
Not really such a great idea, what if someone is using uSD but not ramz and wants swappolube settings?

I would encourage everyone to only use these settings as a start point and try to find what is optimal for the n900. Also, DO NOT USE:

Code:
echo 32 > /proc/sys/vm/min_free_kbytes
It is just too damn low. use this instead:

Code:
echo 1024 > /proc/sys/vm/min_free_kbytes

A good source of info is this

Finally I would not be so hasty to add this to your start up unless you are comfortable with using a rescue console to undo what may go wrong.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.

Last edited by vi_; 2012-05-30 at 10:05.
 

The Following 4 Users Say Thank You to vi_ For This Useful Post: