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

[arrrghhh]

Originally Posted by Lmiller1708

My dmesg says wifi was loaded. This is what my dmesg says once I try turn on wifi:

[  129.991943] bcm4329: version magic '2.6.27.46-01238-ge739b29-dirty preempt mod_unload ARMv6 ' should be '2.6.27.46-01238-ge739b29 preempt mod_unload ARMv6 '

Would appear the kernel modules don't match the kernel... I'm certainly no expert on this topic tho .

[[ACL]]

Originally Posted by arrrghhh

Would appear the kernel modules don't match the kernel... I'm certainly no expert on this topic tho .

ahh yes.. you need to update the android update with the modules from your kernel you build... they have to match..

[Lmiller1708]

Originally Posted by arrrghhh

Would appear the kernel modules don't match the kernel... I'm certainly no expert on this topic tho .

Originally Posted by [ACL]

ahh yes.. you need to update the android update with the modules from your kernel you build... they have to match..

That did it! Thanks guys!

[[ACL]]

Ok, so we need more comparisons in the /dev directory to make sure we got it all covered.

Also i never got a final mtd parts from you guys. What do you want me to commit ?

Nate: you can test this install with your busybox see if naything breaks. if not, then we can commit that too.

ill be busy the next few days with the camera patch. So i want this stable build to be released to the cookers so they can master mid some builds..

[Lmiller1708]

Originally Posted by [ACL]

Ok, so we need more comparisons in the /dev directory to make sure we got it all covered.

Also i never got a final mtd parts from you guys. What do you want me to commit ?

Nate: you can test this install with your busybox see if naything breaks. if not, then we can commit that too.

ill be busy the next few days with the camera patch. So i want this stable build to be released to the cookers so they can master mid some builds..

Here is my CMDLINE:

mtdparts=msm_nand:0x20000000@0x0(nand),0x01000000@0x04000000(root),0x08000000@0x05000000(system),0x13000000@0x0D000000(userdata)"

Question is how big does the Root need to be?
@Nate Not sure why they start a 64MB... Might be for a very good reason though so I would be careful... Also where can we reclaim the space in the partition table?

[[ACL]]

Originally Posted by Lmiller1708

Here is my CMDLINE:

mtdparts=msm_nand:0x20000000@0x0(nand),0x01000000@0x04000000(root),0x08000000@0x05000000(system),0x13000000@0x0D000000(userdata)"

Question is how big does the Root need to be?
@Nate Not sure why they start a 64MB... Might be for a very good reason though so I would be careful... Also where can we reclaim the space in the partition table?

I'll commit that table tonight if you are 100% sure its tested and all kosher .

also here is a good test for anyone.. dump mtd1 (or whereever tinboot is at) and do a binary compare to what we give the boot loader.

Replacing the kernel may be a simple as wriring to that partion..

[natemcnutty]

Originally Posted by [ACL]

I'll commit that table tonight if you are 100% sure its tested and all kosher .

also here is a good test for anyone.. dump mtd1 (or whereever tinboot is at) and do a binary compare to what we give the boot loader.

Replacing the kernel may be a simple as wriring to that partion..

Yeah, I don't think we have a mtd parts being assigned to where tinboot is being written to. In fact, I'm not sure that the root partition we are setting aside is even being used. Are you able to cat mtd1 and see if anything is even in it? I'd say go ahead and commit as long as system is at least 128MB. We can shift the rest around later, but I want to commit to a specific size for system for the chefs (and we have to keep module size in mind too)