Reply
Thread Tools
Posts: 1,522 | Thanked: 392 times | Joined on Jul 2010 @ São Paulo, Brazil
#201
So far i haven't noticed any issues
 
Posts: 1,522 | Thanked: 392 times | Joined on Jul 2010 @ São Paulo, Brazil
#202
/me sighs

I wasn't paying enough attention and upgraded the power kernel from inside the copy, the N900 wouldn't go past the NOKIA screen. Had to reflash, i'm in the process of installing and setting things again
 
Posts: 1,225 | Thanked: 1,905 times | Joined on Feb 2011 @ Quezon City, Philippines
#203
Originally Posted by TiagoTiago View Post
/me sighs

I wasn't paying enough attention and upgraded the power kernel from inside the copy, the N900 wouldn't go past the NOKIA screen. Had to reflash, i'm in the process of installing and setting things again
This would easily be avoided by mount-binding ubifs' /lib/modules folder to the copy's /lib/modules folder.
An even better solution would be to make NOLO pass the eMMC's root in the atags.
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
 
Posts: 470 | Thanked: 173 times | Joined on Oct 2009 @ Melb
#204
So what's the current technique for getting this to work? is it still like the first post describes?

running pr13, full cssu, power kernel.. an yeah
 
Posts: 1,225 | Thanked: 1,905 times | Joined on Feb 2011 @ Quezon City, Philippines
#205
Originally Posted by optimaxxx View Post
So what's the current technique for getting this to work? is it still like the first post describes?

running pr13, full cssu, power kernel.. an yeah
Download kernel-power source, build with omap_hsmmc=y and CONFIG_EXT3 (or _EXT4)=y, copy Maemo to a partition, start Maemo with custom CMDLINE.
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
 
Posts: 95 | Thanked: 66 times | Joined on Mar 2012
#206
Just sharing my experience on this.
Based on heavily modified instructions from this thread, I managed to get this running on PR1.3, works with BackupMenu & Bootmenu (no both of them are not evil), & even have multiboot for the system in NAND & the system in eMMC. Even managed to upgrade the kernel *after* setting this up, either on the NAND system or eMMC system first (;note that both must at least have kernel-power & kernel-power-modules installed if you wanna install kp). My set up has an instance of optfs for NAND rootfs & eMMC rootfs each. Only thing I couldn't & didn't bother to fix was that it would boot up automatically again after a shutdown.

So, I basically ran rootfs on eMMC system for 2 days (used a current image created using BackupMenu), & I gave up. It was horrendously slow (boot up that usually took 1 minute or less on NAND took perhaps 5-10 minutes). I find that it sucked up more battery too (perhaps it kept the hardware up for longer time due to longer read/writes, & I have quite a bit of background processes running on mine). The main battery drain on my N900 was 24x7 online 2G which on NAND, can stay up for about 12 hours max without charging. With rootfs on eMMC, there wasn't any noticable battery savings.

Perhaps it was just not meant for my circumstance, where I have lots loading/writing from/to the file system & apps in memory.
A set up of rootfs on eMMC using a freshly flashed image was actually not too bad, provided one continues keeping things minimal in the device. I suspect the set up I made could stay quite stable if my eMMC rootfs wasn't created from image of my NAND rootfs.

Conclusion: Something I wouldn't go on anymore. But might be suited for folks who really scrutinize everything that goes into their device & keep things minimal. Not for those not familiar with technical stuff too.

I can share some of the work I did if anyone wants, but would expect whoever wants it to be able to figure out stuff on his/her own & reverse engineer things as well. Won't be actively providing help.

kh
 

The Following User Says Thank You to bozoid For This Useful Post:
Posts: 95 | Thanked: 66 times | Joined on Mar 2012
#207
Originally Posted by Hurrian View Post
This would easily be avoided by mount-binding ubifs' /lib/modules folder to the copy's /lib/modules folder.
An even better solution would be to make NOLO pass the eMMC's root in the atags.
I found that that isn't enough. One still needs to do dpkg -i kernel-power_*deb & dpkg -i kernel-power-module*deb too. I tried only running post install scripts but it was somehow not enough.

kh
 

The Following User Says Thank You to bozoid For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 15:09.