View Single Post
  #1066 (permalink)  
Old 02-06-2011, 02:59 AM
[ACL]'s Avatar
[ACL]
VIP Member
Offline
Location: NY
 
Join Date: Feb 2010
Posts: 1,534
Reputation: 6350
[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 01-07: Panel power on/off fixes

Quote:
Originally Posted by Lmiller1708 View Post
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.
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?
__________________

Last edited by [ACL]; 02-06-2011 at 03:12 AM.
Reply With Quote