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]> I have find out something was shipped between next-20250228 and next-20250302 what cause rpm to not work
<barni2000[m]> i have got "failed to parse smd edge"
<barni2000[m]> and -ENOENT
<barni2000[m]> s/20250302/20250303/
<AakashSharma[m]> <barni2000[m]> "try to build lk2nd with these K..." <- Also tried to build with LK2ND_ADTBS="msm8937-xiaomi-land.dtb , lk2nd image is created but results are same. Device goes to 900E mode
<AakashSharma[m]> Can you please provide me your working lk2nd.img on xiaomi -land-msm8937
<barni2000[m]> does your device healthy, do you have battery panel everything?
<AakashSharma[m]> Yes battery is connected , default boot.img works fine , twrp works fine , but fastboot boot lk2nd.img makes it unusable
<barni2000[m]> AakashSharma[m]: what about the panel
<AakashSharma[m]> Will it give error if screen is not working ?
<AakashSharma[m]> Panel is damaged
<barni2000[m]> AakashSharma[m]: it can cause issues if it is not connected to the mb
<barni2000[m]> what is matter the display controller
<AakashSharma[m]> barni2000[m]: Yes I am flashing 8952 version & also tried to build manually ,
<AakashSharma[m]> Can I remove the panel lines from dts file
<barni2000[m]> i think it will not solve your issue
<barni2000[m]> you should search for error handling in the lk2nd code
<AakashSharma[m]> Ohk
<AakashSharma[m]> Where can I bypass the display panel initilization code , any idea
<barni2000[m]> idk, maybe travmurav have
<travmurav[m]> I think caf lk was supposed to just ignore the display if it's not present
<travmurav[m]> does the device reach lk2nd at all? (iow is it not original bootloader crashint)
<travmurav[m]> s/crashint/crashing/
<travmurav[m]> that is, pretty sure i was fine running lk2nd on devices with no display connected, and oem's bootloader just didn't initialize mdp
<barni2000[m]> ik some devices where they was not work without display but many are working
<barni2000[m]> <AakashSharma[m]> "Yes battery is connected..." <- boot.img was working so it could be issue on lk2nd side
<AakashSharma[m]> <barni2000[m]> "boot.img was working so it could..." <- Yes stock boot.img is working fine, it successfully boots AOSP extended rom without display, all adb commands runs fine.
<AakashSharma[m]> But it crashes on lk2nd.img
<barni2000[m]> <barni2000[m]> "I have find out something was..." <- i have find what causing the issue qcom,ipc was not parsed anymore because they have change error return value in request_mbox_channel
<barni2000[m]> s/request_mbox_channel/mbox\_request_channel/
ungeskriptet has quit [Read error: No route to host]