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

[damage_them]

im getting stuck @ this line..73.6437681] kernal panic-not syncing: attemped to kill int!..or should i just delete my data.img ??

[kaotek]

does this fixed the power down and up ?

[natemcnutty]

Originally Posted by damage_them

im getting stuck @ this line..73.6437681] kernal panic-not syncing: attemped to kill int!..or should i just delete my data.img ??

Just figured it out. I forgot to re-comment my testing code for machine_variant stuff. Building now and will upload a fixed one here in just a minute.

New one is now up. Sorry about that.

[natemcnutty]

Originally Posted by kaotek

does this fixed the power down and up ?

What do you mean by power down and up? Are you talking about powering the display off and back on? That has not been implemented yet. This is just the first working hw3d we've been able to build since the hw3d commit. Something in ACL's patch just didn't go through to the repository, so we haven't been able to build a working kernel since that change was made.

[damage_them]

Originally Posted by natemcnutty

Just figured it out. I forgot to re-comment my testing code for machine_variant stuff. Building now and will upload a fixed one here in just a minute.

New one is now up. Sorry about that.

also the new roots(10/20) dont work ..thats where the kernal panic came from..cuz i tried 10/3 and it passed and went to boot animation but the phone just rebooted..

[natemcnutty]

Originally Posted by damage_them

also the new roots(10/20) dont work ..thats where the kernal panic came from..cuz i tried 10/3 and it passed and went to boot animation but the phone just rebooted..

Yeah, I think I fixed it, but I would use 10/3 if you want stability. 10/20 is for testing only at this point.

[damage_them]

Originally Posted by natemcnutty

Yeah, I think I fixed it, but I would use 10/3 if you want stability. 10/20 is for testing only at this point.

well thats what this is all about..will try 10/20 now and let u know inna sec

[coolsilver]

Originally Posted by natemcnutty

I think he just meant to merge the new changes from the linux-msm project into the linux-msm-rhod-nand project.

@Coolsilver: Unfortunately, there are some major differences between booting with haret vs. nand. Some of the changes don't translate over, and nand is a branch that only supports the rhodium devices whereas the "haret" tree supports many devices.

Yea but I knew you would need to patch any merged code to make it NAND compatible. Just a thought. I see you found why things were acting strange.

[natemcnutty]

Originally Posted by damage_them

well thats what this is all about..will try 10/20 now and let u know inna sec

Yeah, all in the name of testing :P

I just noticed that the commits don't even apply to our device unless you are running European models of the rhod, so it should be the exact same as 10-03 for those of us with rhod500 and rhod400's.

In any case, I've been playing around with rootfs stuff, and I still haven't been able to get much on the machine_variant front. I'm pretty bummed since I thought it might be something I could actually help with :P

Edit: Heading home now. Will try to check back a little later

[damage_them]

Originally Posted by natemcnutty

Yeah, I think I fixed it, but I would use 10/3 if you want stability. 10/20 is for testing only at this point.

OH YEAA!! the fix worked..now its up and running..great work mehn..whoohoo..working 3d here i come!!..lol