[Kernel] Moggy v13 - for 4G Stock ROM users

[bedalus]

Lollipop kernel: this post Moto G 4G peregrine only

Mog shot

Stock ROM (UK ONLY!)
Tesco GB 4.4.4 ROM mirror here May be useful to UK users who want to flash back and re-download the OTAs

Stock 5.1 Kernel zip
Thank user J0kker then download in the post below his

Final KitKat zip: this post

 

[bedalus]

Source code: https://github.com/bedalus/moggy/

Toolchain: http://xdaforums.com/showthread.php?t=2098133 4.9.3 a7 optimised version

 

[hekomat]

Holy smoke.... it's bedalus!:highfive:

@hekomat Please do not swear on XDA.
From you friendly moderator, @Toledo_JAB

 

[OldYellowBricks]

bout 2 sound like an jerk...but...can you build one for the falcon too?

thanks sooo much

 

[CJMom]

Sorry for asking but what are the actual changes from the stock kernel?

 

[bedalus]

what are the actual changes from the stock kernel?

So far the only changes are using an up-to-date linaro toolchain, removal of some debug logging, and switching the IO scheduler to cfq.

I saw there was no option for peregrine users so I thought I'd make one. At the moment the repo is very clean. It would make a good jumping off point if any other devs want to fork it and add fun stuff. I personally prefer to keep it simple.

 

[bedalus]

can you build one for the falcon too?

There's already a few kernels for falcon. What is it you're hoping I'll offer?

 

[knizmi]

There's already a few kernels for falcon. What is it you're hoping I'll offer?

To have a stock kernel built with latest linaro? Currently trying to do it myself for falcon, but I've just encountered the Motorola module whitelisting (WTF?). Never seen that before on other devices...

 

[bedalus]

To have a stock kernel built with latest linaro? Currently trying to do it myself for falcon, but I've just encountered the Motorola module whitelisting (WTF?). Never seen that before on other devices...

I'll happily talk you through it. How far are you through?

 

[knizmi]

Oh, and you probably forgot to strip your wlan.ko, it has well over 30 MB I am surprised it even loads on peregrine.

---------- Post added at 10:11 PM ---------- Previous post was at 10:06 PM ----------

I'll happily talk you through it. How far are you through?

Everything is allright - the kernel boots and everything works fine, the only problem was that I couldn't get wlan.ko to load. I didn't know about the whitelist thing, though. You can imagine my face when I looked at dmesg.

I should have some more time in an hour or so, if don't get it running by morning, I will PM you. Thanks for the offer.

 

[knizmi]

OK, I've done it by adding

chmod 0666 module_hashes
echo ee04251847ff70190bfec61b19802c19afe29a16 >> module_hashes
chmod 0400 module_hashes

to your repack-ramdisk.sh. Seems a little dirty, but works
The other modules will have the same problem I believe. Unless I want to add their SHA hashes the same way, what is the correct way to bypass/update that whitelist? You don't mess with that file anywhere in your build or install scripts. Gonna try deleting it, but you don't do that either...

 

[bedalus]

OK, I've done it by adding

chmod 0666 module_hashes
echo ee04251847ff70190bfec61b19802c19afe29a16 >> module_hashes
chmod 0400 module_hashes

to your repack-ramdisk.sh. Seems a little dirty, but works
The other modules will have the same problem I believe. Unless I want to add their SHA hashes the same way, what is the correct way to bypass/update that whitelist? You don't mess with that file anywhere in your build or install scripts. Gonna try deleting it, but you don't do that either...

I've seen your new falcon thread congratulations on making it work. Thanks for the credit.

To circumvent the whitelist, you need to disable it in the kernel config: see here

You're right about the module stripping. I tried doing it in the build script, but it was the wrong approach. This commit works. Thanks for reminding me! I've updated the download link. The zip is now less than 8MB, much better.

 

[beeeto]

Love to see new stuff in our beloved 4G.

Downloading and testing it right now. Thank you.

 

[CJMom]

I want to try this too.
I just need to flash it from recovery?
deleting caches is needed?
If I want to go back to stock kernel just flash boot.img from my stock firmware using mfastboot?

Thanks!

 

[bedalus]

I just need to flash it from recovery?
deleting caches is needed?
If I want to go back to stock kernel just flash boot.img from my stock firmware using mfastboot?

Yep, the zip is flashable in CWM or TWRP. Deleting caches is not needed.

To return to stock, like you say...

mfastboot flash boot boot.img

But the stock boot.img does not contain copies the kernel modules. If you intend to go back to stock, you'll need to back up the entire folder /system/lib/modules from a stock install before flashing my kernel.

Stock peregrine boot.img: http://d-h.st/yF6

 

[knizmi]

To circumvent the whitelist, you need to disable it in the kernel config: see here

Lol, how easy. Didn´t see that, thank you.

To return to stock, like you say...

mfastboot flash boot boot.img

Actually, I'm not sure if the stock boot.img copies the kernel modules or not. If you intend to go back to stock, it would be a good idea to back up the entire folder /system/lib/modules from a stock install before flashing my kernel.

Stock peregrine boot.img: http://d-h.st/yF6

To return to stock you need both boot.img and modules. Flashing boot.img only will disable your wifi.

 

[CJMom]

Flashed it and everything is OK.
Waiting for future updates and features

 

[beeeto]

Hey bedalus,

Are you planning to make a CM11 version?

 

[bedalus]

Hey bedalus,

Are you planning to make a CM11 version?

No, at this time I'm planning to build what I need and share. I'm fairly sure I'll be sticking with stock 4.4.4

 

[bedalus]

testing version 3: http://d-h.st/1Sn

- Got the download to just over 5MB by switching to XZ compression
- f2fs cherry-picks from torvalds git up to kernel v3.18

I consider f2fs the newest piece of the kernel, and the filesystem is always a bottleneck for system performance, being slow compared to everything else. It makes sense to apply as many improvements in this regard as possible.

The cherry-picks may have affected stability. It's always hard to tell with such a huge amount of code revision. I've seen one new bug where if there is an unexpected shutdown, this causes a kernel oops on the subsequent reboot right after the filesystem recovery. Then the following reboot works normally. No damage the to filesystem, just a null pointer dereference.