Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[titan] Cannot boot kernel compiled with pmOS #126
It can happen as well to other devices.
LineageOS boot image is 8MB and I can flash it but my pmOS boot image is 12MB, of which 8MB is the kernel.
We need to find some way to make the kernel smaller. I had to disable
Things to investigate:
(*) MartijnBraam said on IRC:
This is the output of fastboot:
With LineageOS boot.img:
What you could do now:
referenced this issue
Jul 2, 2017
(*) But it doesn't boot either - it just reboots
This was referenced
Jul 19, 2017
I think it's a good idea to put extra files in the boot partition - but I would put them in an extra file (e.g.
What we would need to keep in the real initramfs is:
After #257 has been merged, I'm still unable to flash the boot partition.
If you don't mind I'd like to keep the issue opened so that I don't forget about investigating and documenting some of the findings
added a commit
Sep 20, 2017
In arch/arm/mach-msm/Makefile.boot remove or commented thea dts files (if you want titan), like this:
MSM8226 Motorola Devices ifeq ($(CONFIG_MMI_TITAN_DTB),y) dtb-$(CONFIG_ARCH_MSM8226) += msm8226-titan-4b.dtb dtb-$(CONFIG_ARCH_MSM8226) += msm8226-titan-4c.dtb dtb-$(CONFIG_ARCH_MSM8226) += msm8226-titan-4d.dtb dtb-$(CONFIG_ARCH_MSM8226) += msm8226-titan-4e.dtb dtb-$(CONFIG_ARCH_MSM8226) += msm8226-titan-4f.dtb #dtb-$(CONFIG_ARCH_MSM8226) += msm8926-thea-p1a.dtb #dtb-$(CONFIG_ARCH_MSM8226) += msm8926-thea-p1c.dtb #dtb-$(CONFIG_ARCH_MSM8226) += msm8926-thea-p2.dtb #dtb-$(CONFIG_ARCH_MSM8226) += msm8926-thea-p3.dtb
The size will be reduce, i have same issue in ubuntu touch, i got big kernel size and i can't flash it, but after this change, boot.img work well and ubuntu touch also
So finally I found the issue with XZ compression in my kernel
It turns out that the kernel makefile is broken because it uses a very weak method to detect if you are using the non-gnu version fo the
I solved it by adding
As a last note, I suspect that my device admits both appended dtb to zImage and to the boot image.