Reply
Thread Tools
Posts: 619 | Thanked: 100 times | Joined on Jan 2010
#1
So has anyone actually managed to break their device with the custom kernel? And I don't mean just by using the OC feature - has anyone toyed with it and then had to reflash?
I see it's out of extras-devel which is already a great start.
________
BUY GLASS PIPES

Last edited by nax3000; 2011-03-18 at 13:14.
 
MohammadAG's Avatar
Posts: 2,473 | Thanked: 12,265 times | Joined on Oct 2009 @ Jerusalem, PS/IL
#2
Custom kernel can't break the device, worst case scenario is that you have to reflash the kernel with another one cause you didn't rebuild the modules.
 
Posts: 619 | Thanked: 100 times | Joined on Jan 2010
#3
Originally Posted by MohammadAG View Post
Custom kernel can't break the device, worst case scenario is that you have to reflash the kernel with another one cause you didn't rebuild the modules.
I see, thanks. Care to explain what "rebuild the modules" means though?
________
Yamaha Tdm850

Last edited by nax3000; 2011-03-18 at 13:14.
 
MohammadAG's Avatar
Posts: 2,473 | Thanked: 12,265 times | Joined on Oct 2009 @ Jerusalem, PS/IL
#4
A bit simplified but:
When you build a kernel, you get a zImage, this contains only the base kernel files, modules will need to be loaded after loading that base image. If the custom kernel is the same name as the stock kernel, it will use the stock modules, if these are incompatible, it will go into a boot loop till you replace either the modules, or reflash the stock kernel.
Same happens if the modules are missing.

As an end user, you don't need to worry about this.
 

The Following User Says Thank You to MohammadAG For This Useful Post:
Posts: 619 | Thanked: 100 times | Joined on Jan 2010
#5
Originally Posted by MohammadAG View Post
A bit simplified but:
When you build a kernel, you get a zImage, this contains only the base kernel files, modules will need to be loaded after loading that base image. If the custom kernel is the same name as the stock kernel, it will use the stock modules, if these are incompatible, it will go into a boot loop till you replace either the modules, or reflash the stock kernel.
Same happens if the modules are missing.

As an end user, you don't need to worry about this.
Thanks a lot!

I forgot to ask, the custom kernel works fine with pr1.2 right?
________
PISSING VIDEO

Last edited by nax3000; 2011-03-18 at 13:14.
 
Posts: 346 | Thanked: 271 times | Joined on Jan 2010
#6
Yes, the version 37 of Titan kernel work with all firmwares so far
 

The Following User Says Thank You to Megaltariak For This Useful Post:
Posts: 619 | Thanked: 100 times | Joined on Jan 2010
#7
Originally Posted by Megaltariak View Post
Yes, the version 37 of Titan kernel work with all firmwares so far
Great!

Now to find that overclocking freq widget I keep seeing in people's screenshots.
________
SHEMALE YOUNG

Last edited by nax3000; 2011-03-18 at 13:14.
 
Posts: 42 | Thanked: 27 times | Joined on Jun 2010
#8
Is it also posible to use a newer kernel version than the 2.6.28?

I would really like to try 2.6.33, with compcache enabled, I don't like the idea of breaking the internal flash with constant writing because of swapping.
 
clasificado's Avatar
Posts: 466 | Thanked: 180 times | Joined on Feb 2010
#9
it is technically possible, but is hard as hell. and AFAIK isnt packaged for easy use.

natisbad has tried here http://natisbad.org/N900/n900-curren...ap-kernel.html he was partially succesfull

we need more work with the omap1 diff dissection, and we cant survive without disabling the watchdogs, but hey! its the upstream!

its not a simple task and is for brave poeple only, with a spare n900 to brick

Last edited by clasificado; 2010-06-27 at 18:16.
 
Posts: 42 | Thanked: 27 times | Joined on Jun 2010
#10
I see... it seems it is not an easy task.
 
Reply


 
Forum Jump


All times are GMT. The time now is 02:16.