ChanServ changed the topic of #msm8937-mainline to: Boot Linux on your MSM8917/37/40 and QM215 mobile! | GitHub: https://github.com/msm89x7-mainline | Logs: https://oftc.irclog.whitequark.org/msm8937-mainline | Bridged to #msm8937-mainline:kde.org on Matrix
<barni2000[m]> because there is no packade devices yet
<barni2000[m]> s/packade/packaged/
checkfoc_us9 has quit []
checkfoc_us9 has joined #msm8937-mainline
<barni2000[m]> original powe collapse state also works in 8917
<barni2000[m]> s/powe/power/
<barni2000[m]> gpu is crashing a lot :(
<barni2000[m]> i have a feeling we have a regression now :'(
<barni2000[m]> gpu crashing instantly on 8917
<barni2000[m]> maybe just plamo not works fine on a306a
<barni2000[m]> You don't need to flash the boot.img but it can boot with it because I was using it
<barni2000[m]> lk2nd is mostly hard requirement for cpufreq atm
<barni2000[m]> So if it is not booting to you need to check what is missing from your port, maybe the display drivers from initfs etc.
<barni2000[m]> Btw extlinux is enough for boot an alarm rootfs so kupfer also should work you don't need boot.img
<fish4terrisa[m]> do I need to generate panel driver by myself for ugg? It seems that under drivers/gpu/drm/panel/msm89xy-generated in the kernel repo there's only driver for ugglite
<M0xCAFEBABE[m]> <fish4terrisa[m]> "do I need to generate panel..." <- ugg&ugglite shares the same panels
<barni2000[m]> lk2nd chosing the right panels for ugg
<barni2000[m]> You need msm and panel driver in your initfs
<fish4terrisa[m]> I get them in my initfs(using lsinitcpio)... but still no luck... I'm building the pmos ones and trying to figure out what they did.
<barni2000[m]> Maybe boot partition is not ,ext2
<fish4terrisa[m]> I'm trying to find a way to get the logs from kernel
<fish4terrisa[m]> barni2000[m]: it is
<barni2000[m]> Use the same ramoops what twrp uses and you can get it from it
<fish4terrisa[m]> lk2nd can find the extlinux
<barni2000[m]> Maybe your extlinux config is not correct
<fish4terrisa[m]> barni2000[m]: twrp didnt get it... the last_kmsg from twrp is empty. Or do I need to change something to get ramoops working?
<barni2000[m]> Yes you need to define same ramoops region in mainline dt
<fish4terrisa[m]> barni2000[m]: any examples? I'm not familiar with ramoops and where's the region of twrp's?
<barni2000[m]> Check downstream cmdline and grep for pstore and ramoops at twrp dmesg
<barni2000[m]> Xiaomi mostly put pstore at end of the memory region
<fish4terrisa[m]> oh I see so both cmdline and dts need to be edited?
<barni2000[m]> Only dt should be edited just downstream uses comandline for define pstore
<fish4terrisa[m]> ok I'll take a try
<barni2000[m]> Btw which config are you using for kernel compile?
<fish4terrisa[m]> <barni2000[m]> "Btw which config are you using..." <- https://github.com/fish4terrisa-MSDSM/kupfer-pkgbuilds-xiaomi-ugglite/raw/refs/heads/flyingfish/linux/msm8940/config.pmos from pmos
<barni2000[m]> You could enable simple drm also temporary
<fish4terrisa[m]> tested that pmos is working, so there must be something I messed up
<fish4terrisa[m]> <barni2000[m]> "You could enable simple drm also..." <- simple drm is built in my kernel, is there anything else I need to do to enable simple drm?(and get log printed on it)
<barni2000[m]> Enable in the dt
<barni2000[m]> simple drm and msmdrmfb should not used together so simpledrm is just for debugging
<fish4terrisa[m]> <barni2000[m]> "Enable in the dt" <- by change the status of simple-framebuffer to enable?
<barni2000[m]> status = "okay"
<fish4terrisa[m]> ok and do I need to change something to disable msmdrmfb?
<barni2000[m]> No
<barni2000[m]> Or you can disable the gpu node
<fish4terrisa[m]> ok thank you I'll give it a try.
<fish4terrisa[m]> well, it didnt work. even after disable the gpu node it still didnt shown up... I'm currently rebuilding my image to see if something I changed is not made into the image. And, strangely, maybe the usb-tethering in kupfer is broken... (never succeeded , but pmos can do it without problem...)
<fish4terrisa[m]> finally I got the console. Long story short: There is in fact something wrong with the display driver. With usb serial i finally can get a console. ( so probably at some point it started to boot and I didnt recognized)