Saturday, 2026-05-23

nightishamannvm it was just a lucky streak00:00
rinigusnightishaman: I didn't do much. basically I am using default LOS module loading. see https://paste.opensuse.org/pastes/41cfb0803c7d07:04
rinigusvendor has already /vendor/etc/init/hw/init.qti.kernel.rc to call /vendor/bin/vendor_modprobe.sh on boot. that script checks vendor_dlkm and loads modules07:05
rinigusall is done via /vendor/bin/modprobe07:06
rinigusmodules are packed correctly by LOS  make and we later package them as in https://github.com/sailfishos-sony-nagara/droid-hal-vendor-dlkm07:08
rinigusnote that we have HADK for nagara together with other docs at https://github.com/sailfishos-sony-nagara/main/wiki . maybe it is of some use for you07:09
rinigus@b100dian: droidmedia looks good for me as well. I guess before we release it all in testing, I need to figure out how to disable esim on update of the config - to avoid blocking login due to SFOS bug07:17
T42<b100dian> rinigus: sh*t I think I released the configs with multisim08:05
T42<b100dian> let me revert the configs at least08:06
T42<b100dian> I think I don't understand how revert works, it did not trigger a rebuild08:17
T42<b100dian> oh it did, sorry08:17
T42<b100dian> rinigus: sorry I got ahead of me because a user already tested, pr was merged in droidmedia. Posted a wraning in the forum.08:20
T42<b100dian> i have only reverte testing08:26
rinigusb100dian: we don't need to revert as such, just pin to earlier commit10:06
rinigusI mean _service10:08
T42<b100dian> I did obs revert, which is probably the pinning to earlier _service in practice10:57
nightishamanrinigus: so ur just calling brunch and let entire LineageOS compile?19:03
nightishamansorry, im new to this so i dont know what quite to do19:03
rinigusnightishaman: yes and no. at first, for nagara, LOS had to be ported. so, LOS21 base used by SFOS port was actually the first LOS port with the only target to run SFOS on top of it. overall, that LOS port is relatively classical and I tried to follow LOS conventions, as much as I figured them out19:08
riniguswhen building SFOS, we use https://github.com/sailfishos-sony-nagara/main/wiki/HADK-for-Sony-Nagara-devices#build-hybris-hal-and-droidmedia19:09
nightishamanyeah but how do you get the init_boot image and get it to call SailfishOS later19:09
rinigusso, regular make19:09
riniguscross-posting. not sure I follow. we use regular SFOS init boot images. within that init, systemd gets started19:10
rinigussystemd calls droid-init and that one is the one that loads modules via regular android init scripts19:11
nightishamanoh19:11
nightishamani thought you use android init to load the vendor ramdisk modules19:11
rinigusnope, those we don't have - as far as I remember (will be afk for tonight, sorry)19:12
nightishamani dont really know how to debug this, the kernel just hangs at some point, no progress loading modules19:13
nightishamani added a usleep 50000 to the module loading and suddenly it already hangs at zsmalloc, there is something really wrong19:58
nightishamanim building kernel with hardlockup_detector now, hope i get something19:58

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!