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

[Lmiller1708]

Originally Posted by [ACL]

Right now to get it to be small i removed e2fsck from the bin folder. This is because we dont check on ext2 partitions anymore so no need to have it there. That file alone is pretty big so im going to commit my change. This isnt part of busybox, but the vogue script supported ext2 img files which we dont, so it can be removed.

Well the system partition already has its own bin directory with all the goodies possible so the busybox for initrd should be the bare essentials to boot and run the install script. So i think we will be safe with a small busybox.. I think we should be good to test your busybox.

edit: oops.. not a bin directory but xbin is on system. Not sure if it has a full busy box in there..

Edit2: Also here is the latest install, update and install-seq

You are big boys so you can make your own NHB and harvest your own modules and apply it to the android update. Wifi is working for me but i cant test cdma data. I'll leave that up to you fellas.

Index of /files/xdandroid/

Thanks for the files. I tested them out this morning and I got it to boot but still have no service or data or WIFI, calibration works.
Here is the catlog you asked me to do yesterday:
I/PHONE ( 250): Network Mode set to 0 I/PHONE - Logcat Radio
Here is my log taken from Droid explorer: (From Boot)
02-16 12:50:19.180: DEBUG/AndroidRuntime(123): >>> - Nand_Bootup_Log

Hope this helps!

[[ACL]]

Originally Posted by Lmiller1708

Thanks for the files. I tested them out this morning and I got it to boot but still have no service or data or WIFI, calibration works.
Here is the catlog you asked me to do yesterday:
I/PHONE ( 250): Network Mode set to 0 I/PHONE - Logcat Radio
Here is my log taken from Droid explorer: (From Boot)
02-16 12:50:19.180: DEBUG/AndroidRuntime(123): >>> - Nand_Bootup_Log

Hope this helps!

No wifi !!! ? woa

ok, lets troubleshoot this.

Follow these steps.

1) check the sysinit.rc file on the bottom for the wpa supplicant service. Make sure it all ways eth0 and not tiwlan. This was my first mistake.

2) Make sure /etc/wifi has the correct wpa supplicant.conf that uses eth0 as the interface

3) Check that the correct interface is on the dhcpcd.conf file.. eth0

and last, when you try to enable wifi, check dmesg and logcat as they will let u know the reason why. But the above two should be checked.

[Lmiller1708]

Originally Posted by [ACL]

No wifi !!! ? woa

ok, lets troubleshoot this.

Follow these steps.

1) check the sysinit.rc file on the bottom for the wpa supplicant service. Make sure it all ways eth0 and not tiwlan. This was my first mistake.

2) Make sure /etc/wifi has the correct wpa supplicant.conf that uses eth0 as the interface

3) Check that the correct interface is on the dhcpcd.conf file.. eth0

and last, when you try to enable wifi, check dmesg and logcat as they will let u know the reason why. But the above two should be checked.

I checked all of these values in the sys.tar and they were all tiwlan... But the Update.tar had all the correct ones. So I didn't make any changes since the update.tar comes second. Still a no go with WIFI. Data either... (Maybe they have something in common?)

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 '

[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)