Quote:
Originally Posted by Lmiller1708
Attached is the Log from tonight. (Had to zip it)
Same issues as before... Couple of them should be easy to solve.
But currently the modules are not getting added.
I'm going to strip down the system as much as possible to save ~15 MB.
Just to get it to load the modules and hopefully get a clean boot.
I also attached my INIT from the initrd. I left most of the stuff from the Vogue in there... Just incase... 
Update: After some reading HERE, I decided to change my Command Line code to this:
Code:
mtdparts=msm_nand:0x10000000@0x0(nand)ro,0x01500000@0x04000000(root),0x07BA0000@0x05500000(system),0x06f60000@0x0CFA0000(userdata)
This gave me a larger system while keeping the data partition the same. This them allowed me to load in the modules.
I also added the "ro" at the end of the nand partition, not too sure what this does but devices with similar mtdparts cmdline have this. Basically everything but the Vogue.
Also I still can't get my System nor my Data to stick after a reboot. I thought it was just my Data but now it seems to be both.  Reading back in the irc logs i see wozzer had this same issue. Might be something with the mtdparts cmdline. |
Hehe, looks like you had a similar idea as I did. I extended the size of the system partition by 30MB in my tinboot and was finally able to install the modules. It gets further than I did before, but still have some refactoring to do.
Also of interest for the mtdparts commands, I believe the ro option means it is treated as read-only, and if we place a minus before the data partition, it will use the remaining available flash for data. Here is the way I have mine right now:
Code:
mtdparts=msm_nand:0x10000000@0x0(nand),0x01500000@0x04000000(root),0x076C0000@0x05540000(system),-0x06f60000@0x0cc00000(userdata)
Quote:
Originally Posted by [ACL]
nahh wozzer never got this far.. he didnt have the driver remember ..lol. nor was yaffs even enabled on the kernel. You issue i think may be android. Once android boots it goes and tries to remount everything. you need to comment those lines out in the rc file and experiment. Read my post below.
Edit: oops so it only happens after reboot? ok thats something else then. odd.. you may need to check the dmesg to see if there are errors writing to nand. Or go over your script and make sure you arent reinstalling each time.. you could be rewiping nand
also how did you handle the directory structure for the rootfs. Your init looks like it just bypassed the whole thing. did you just merge it with the initrd?
|
I bypassed rootfs entirely by merging stuff from rootfs into initrd. Unfortunately, I'm still ironing out some kinks that were caused by doing that. This is the way that the Vogue currently does it.
Also, I was looking back through IRC logs, and it looks like Wozzer was having issues with data staying on NAND as well.
IRC logs