NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[[ACL]]

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:

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?

[Lmiller1708]

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.

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?

humm... I guess I read it wrong then. Here is the link. (Look at the bottom of the page) Seems like the same problem...

I do have those line commented out in the init.

Attached is my dmesg after a reboot. It looks like my cmdline is getting reset and losing the mtdparts?

[[ACL]]

Originally Posted by Lmiller1708

humm... I guess I read it wrong then. Here is the link. (Look at the bottom of the page) Seems like the same problem...

I do have those line commented out in the init.

Attached is my dmesg after a reboot. It looks like my cmdline is getting reset and losing the mtdparts?

yeah i see your dmesg doesnt have any parts at all. but its still not the same issue as wozzer. He wasnt able to write to nand at all, so all his writes were on memory. Once reboot, bam writes get wiped. It still doesnt explain the cmd line tho. hmm.. never seen a cmd line dissapear

I need to re-create this issue. So you are 100% sure you arent rewiping tour nand right?

[Lmiller1708]

Originally Posted by [ACL]

yeah i see your dmesg doesnt have any parts at all. but its still not the same issue as wozzer. He wasnt able to write to nand at all, so all his writes were on memory. Once reboot, bam writes get wiped. It still doesnt explain the cmd line tho. hmm.. never seen a cmd line dissapear

I need to re-create this issue. So you are 100% sure you arent rewiping tour nand right?

I didn't think he had the correct drivers... But you never know sometimes.

Yes I 100% sure. It seems to change the cmdline all together to what you see? Very weird!

Does it only get read from the tinboot once?

[[ACL]]

Originally Posted by Lmiller1708

I didn't think he had the correct drivers... But you never know sometimes.

Yes I 100% sure. It seems to change the cmdline all together to what you see? Very weird!

Does it only get read from the tinboot once?

crazy weird.. i'm working on it.. thing is im still partially booting off sd since i havent figured out if im going to bypass rootfs or just try to do it directly.

nope.. reads it all the time.. think about it. our cmd line gets passed down each time we reboot.