| nightishaman | mal: I don't know how but Android init seems to use a different order than the one suggested by modules.load. I wonder whether we could use Android init as starter instead. I didn't get far with hardlockup_detector, i cant enable it | 00:20 |
|---|---|---|
| nightishaman | I mean theoretically I could fork the android init and add a command "switch_root" that allows to switch the root and call a new init | 00:42 |
| nightishaman | the same problems happen with stock kernel and vendor_kernel_boot too, so it must have to do with the init system | 00:43 |
| *** amccarthy is now known as Guest10016 | 06:56 | |
| *** amccarthy_ is now known as amccarthy | 06:56 | |
| Mister_Magister | mal: i'll get to trying the gstreamer stuff soon | 12:20 |
| Mister_Magister | its like next one on my list | 12:20 |
| mal | Mister_Magister: which one? | 12:20 |
| Mister_Magister | the qmlgstsink | 12:21 |
| mal | ok | 12:21 |
| T42 | <NotKit> I tried this before for booting rootfs as DSU image (re @SailfishFreenodeIRCBridgeBot: <nightishaman>I mean...) | 12:22 |
| T42 | <NotKit> doable, but will need to ensure the filesystem layout matches Android early mounts expectations | 12:23 |
| nightishaman | @NotKit I'd just have to remove some of the code related to the SELinux stage since SailfishOS seems to use Yama, but it shouldn't be hard | 17:51 |
| nightishaman | mal: What do you think? I'd adapt Android init to load the kernel modules and then in second stage modify some code to mimic init-script | 17:53 |
| nightishaman | Do I get this correctly and hybris already builds Android init as part of the building process https://github.com/mer-hybris/hybris-boot/blob/master/Android.mk#L295 | 18:00 |
| T42 | <b100dian> yes, but it is not started as process 0, but inside the droid-hal-init service | 18:05 |
| nightishaman | hmm | 18:06 |
| nightishaman | I only need the first stage for kernel modules anyway | 18:06 |
| nightishaman | I could do a handoff to the init-script after that | 18:06 |
| T42 | <b100dian> question: how does detection of charger vs computer work? I have a very finniky dialog that sometimes shows up, sometimes not | 18:11 |
| T42 | <b100dian> and sometime shows up for 1s to pick developer/MTP or just charging. Like here https://pastebin.ubuntu.com/p/9VFjTQzTVG/ | 18:11 |
| T42 | <b100dian> nightishaman - no, it shouldn't use Yama, that's app-armour? Pretty sure selinux is needed | 18:11 |
| T42 | <b100dian> regarding my question 2 lines above - maybe I shouldn't have copied `extcon_tracking = 1` from fp5, seems no work better without | 18:15 |
| T42 | <elros34> @nightishaman droid-hal-init is patched android init, it even loads init*rc files (some are commented out) | 18:20 |
| nightishaman | @elros34 i only need init to load the kernel modules, because for some reason the order is important and android init loads in a different order | 18:36 |
| nightishaman | or they do something else in their modprobe | 18:36 |
| nightishaman | bcs the init-script begins to hang after some time | 18:37 |
| T42 | <elros34> are you sure it's not because hybris changes in defconfig or some other things you have enabled like oem ramdump. did you load excatly same modules as lineage? It hangs in init-script (initramfs) or init-debug or after? | 18:54 |
| nightishaman | @elros34 i tested booting with lineageos kernel and vendor_kernel_boot img and got the same problems, the only difference at that point was the init_boot and that hybris is on b slot. I have oem ramdump always enabled because its my only way of getting access to kernel logs. However android recovery boots fine with it on | 18:56 |
| nightishaman | so basically my partition layout right now is, on a: lineageos kernel, vendor_boot and vendor_kernel_boot to have a recovery, and on b i have sailfishos | 18:58 |
| nightishaman | if you got any idea what the problem is, i'd be really happy to hear it, ive been frustrated the last days because i cant seem to pinpoint the issue except "do it like android does" | 18:59 |
| T42 | <elros34> so again where doe it hangs: in init-script,init-debug or later? | 19:00 |
| nightishaman | init-script when loading vendor_kernel_boot | 19:00 |
| nightishaman | its trying to load the kernel modules from modules.load | 19:00 |
| T42 | <elros34> and you are loading excatly same modules as in lineage? | 19:01 |
| nightishaman | yes i tried with both my kernel and modules, and lineage kernel and modules | 19:02 |
| nightishaman | both failed at roughly the same spot | 19:02 |
| T42 | <elros34> I meant didn't you try to load some unnecessary debug modules especially if they are not used on linegae (lsmod on lineage) | 19:03 |
| nightishaman | i didnt modify the modules.load it produces, i used dmesg in android recovery to check out which modules it loads | 19:04 |
| nightishaman | there are some debug modules in the list, but other modules depend on them and i cant remove them | 19:06 |
| T42 | <elros34> how do you know it hangs when you use lineage kernel with init-script? do you get watchdog timeout. Do you use original lineage kernel file or compile it yourself? | 19:16 |
| nightishaman | @elros34, the kernel log doesnt get any further and after a minute it reboots, it gets stuck and nothing. if it were to panic, i would see that in the ramdump kernel.log | 19:18 |
| nightishaman | my load_kernel_modules function looks like this: | 19:20 |
| nightishaman | https://pastebin.com/3EbjckAE | 19:20 |
| nightishaman | it is very odd, because its not always the same place where it hangs | 19:21 |
| nightishaman | sometimes its after loading pcie-exynos-gs, sometimes while loading ufs-pixel-fips140 or ufs-pixel-gs | 19:21 |
| T42 | <elros34> can you show that log from failure? | 19:22 |
| T42 | <elros34> just precaution: remove mounting configfs in init-script | 19:37 |
| T42 | <elros34> have you tried searching for ubports port for this device, maybe something can be reused | 19:41 |
| nightishaman | https://pastebin.com/adxvQBxH | 19:59 |
| nightishaman | @elros34, as far as i am aware it has no ubports port | 19:59 |
| nightishaman | the log is from LineageOS kernel which doesnt setup /dev/kmsg | 20:01 |
| nightishaman | therefore no output from init | 20:01 |
| nightishaman | mal: Apparently the first stage android init gets patched by hybris-patches? Why? It doesnt seem to be used or compiled | 20:04 |
| T42 | <elros34> did you compare this log with lineage one? 2 modules with load_sequential | 20:11 |
| mal | nightishaman: android init is used later in boot in droid-hal-init systemd service | 20:15 |
| balta | Hey, I hope this is the right place to get help. As I really want to use all of my Xperia 10 V I started to build my own port based on LOS 22.2. I follow the HADK and am now in the packaging step, more precise the build of hybris. As I have a lot of compiler issues here because of clang syntax in the header files that gcc does not understand. Does it make sense to wait for Sailfish 5.1 with the updated toolchain? Could I | 20:27 |
| balta | use that already with the developer early access in the platform SDK? | 20:27 |
| mal | did you apply patches? | 20:32 |
| mal | the first part here https://github.com/mer-hybris/hadk-faq#hybris-16-0 | 20:33 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!