How to build? about kernel_poco_citrus HOT 15 CLOSED

its not the matter anymore that android 10 kernels will work on 11 since while doing the bringup of my oneplus device, I was not able to bootup 10 kernel on 11 OS because of some issues with encryption and stuff.

from kernel_poco_citrus.

@danascape but did you get up to the animation part at least? I fell I should be able to at least see the animation. It looks like the kernel is completely broken. Do you have any tips debugging this?

from kernel_poco_citrus.

check pstore

from kernel_poco_citrus.

@danascape the problem is that for checking pstore I need root, but there's no official TWRP for the Poco M3

from kernel_poco_citrus.

uh, you can use unofficials

from kernel_poco_citrus.

or AOSP recovery

from kernel_poco_citrus.

I tried all clang prebuilts from AOSP 10 and 11, some of them make the phone boot loop, and some simply make it get stuck at the boot logo forever. I rooted the phone with magisk and then tried to check pstore, last_kmsg, etc, there was nothing (and yes, xiaomi's official kernel has PSTORE activated). Also, there's no support for fastboot oem enable uart so I don't know what I can do anymore to make this work.

May I know where this specific kernel comes from? Is it from codeaurora? If so, how do you know which modifications needs to be done for it to work on the Poco M3? I want to get into this field but it's really hard to debug. I extracted qualcomm's bootloader and found some hidden fastboot commands like fastboot oem lkmsg and fastboot oem lpmsg:

fastboot oem lpmsg
FAILED (remote: 'Failed to get lpmsg')
fastboot: error: Command failed

I'm trying to analyze on Cutter the logic behind this, and I think that lpmsg means "last pstore message" but anyways, I couldn't get anything from it.

Could someone give me a hand? I'd appreciate very much :)

from kernel_poco_citrus.

do not expect uart to be this easy on a xiaomi.
the initial kernel source was released by OEM (xiaomi) at https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/lime-q-oss

from kernel_poco_citrus.

@danascape yes I'm using this source but this kernel stormbreaker-project/kernel_poco_citrus does not share the same history as [Xiaomi_Kernel_OpenSource/tree/lime-q-oss](https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/lime-q-oss)

Latest Xiaomi commit:

https://github.com/stormbreaker-project/kernel_poco_citrus/commits/main?after=0399cad3bd0bdcce0070259236a6e89ab2dfae7c+174&branch=main

which is not present in stormbreaker-project/kernel_poco_citrus commits, so it looks like they are different kernels.

And yes, I'm not optimistic about UART, but maybe fastboot oem lkmsg

from kernel_poco_citrus.

okay so @starlight5234 just mentioned that the issue is that the dtbo from miui kernel does not match the stock dtbo that is why you are stuck. 6159891

from kernel_poco_citrus.

from kernel_poco_citrus.

No it's not

from kernel_poco_citrus.

Ok I did

CONFIG_BUILD_ARM64_APPENDED_DTB_IMAGE=y

on the citrus-perf_defconfig because otherwise it won't even build the Image-gz.dtb. I made those patches also, but the device still boot loops. I tried both with Image-gz.dtb and Image.gz.

Just to confirm: I should repack with Image-gz.dtb, right?

And very important: which clang do you guys use? I tried all clangs from Android 10 and 11 and some of them bootloops, and some never reboot, but none arrive at the boot animation.

Also, I don't get why I need to insert the dtb inside the kernel. If you inspect the kernel with https://github.com/PabloCastellano/extract-dtb then you'll see that inside the kernel there is no device tree, only on boot.img in the dtb file

from kernel_poco_citrus.

Where is defconfig for juice or chime or citrus defconfig support lemon or lime?

from kernel_poco_citrus.

Where is defconfig for juice or chime or citrus defconfig support lemon or lime?

citrus support lime

from kernel_poco_citrus.