Friday, 2024-11-15

rinigus@b100dian: Great test! Ok, so it's working in terms of config on pc. Maybe we just miss something in kernel config.05:25
T42<elros34> similar dmseup issue: https://irclogs.sailfishos.org/logs/%23sailfishos-porters/%23sailfishos-porters.2023-03-29.log.html07:02
rinigus@elros34: unfortunately, no solution in that log08:00
rinigusbut they refer to ubuntu touch where it works.08:00
rinigus@TheVancedGamer: ping. did you managed to resolve your issue with dmsetup of system (see link to the log above)11:41
T42<TheVancedGamer> I gave up because of time constraints back then12:04
T42<TheVancedGamer> I'll try again some day12:04
rinigus@TheVancedGamer: thanks! we will probably try to update lvm2 and see if it helps12:15
malrinigus: I have lvm update branch somewhere12:46
malI should sync it with upstream, I also have that libaio in my github https://github.com/mlehtima/libaio12:47
malI forgot to push that to github.com/sailfishos12:47
rinigusmal: great! I started to look into packaging of libaio - would be happy to use yours :)12:49
malI will sync that to latest version also12:49
rinigusthank you very much!12:50
malrinigus: libaio is now ready in my github, lvm2 to latest version is still wip12:58
rinigusmal: nice! I am hacking some dirty lvm2 update meanwhile - we will switch over to your version as soon as it is ready13:02
malthe reason why lvm2 was not merged was that I didn't have enough time to test it, maybe it's finally time to update it13:03
rinigusI hope that new lvm2 will be able to run our dmsetup and, as a result, we could become your first testers13:05
rinigusnot that we can test much yet with non-booting fully to sfos device13:06
riniguslet me know when some newer lvm2 will land and we can use that branch13:06
malwhat is the problem with dmsetup?13:09
T42<adampigg> getting a new device to port soon also13:11
rinigusmal: we cannot create system_a on nagara devices. it was discussed last night, will find pastes that describe it13:12
riniguson device, it fails with "device-mapper: table: 253:2: linear: Invalid argument count"13:12
riniguson PC, @b100dian managed to mount super partition. corresponding config at https://paste.mozilla.org/RafuTi9i/raw13:13
T42<b100dian> So mal was two steps ahead, with aio prepared and all,can't wait to test tonight13:42
T42<b100dian> @adampigg which device are you eyeing?13:43
rinigusmal: seems like issue is not new, @elros34 found a similar description from 2023 as well. see https://irclogs.sailfishos.org/logs/%23sailfishos-porters/%23sailfishos-porters.2023-03-29.log.html13:45
rinigus@b100dian: lvm2/aio waiting at our obs repo already13:45
T42<b100dian> Great!13:47
T42<adampigg> getting sent the new volla (re @b100dian: @adampigg which devi...)13:53
T42<b100dian> The amoled one?13:57
T42<b100dian> I wonder who's manufacturing this time13:59
T42<leandrofriedrich> me14:02
T42<adampigg> didnt realise how pricey it was! https://www.kickstarter.com/projects/volla/volla-phone-quintus14:03
T42<b100dian> looks like a couple of oppo phones. good luck with the under-display fingerprint! 🙂14:25
T42<b100dian> phones with this chipset https://www.gsmarena.com/results.php3?sChipset=13714:25
*** deathmist1 is now known as deathmist14:44
malrinigus: latest lvm2 is now here https://github.com/sailfishos/lvm2/tree/jb60487 only build tested so far15:05
rinigusmal: thank you very much! we will test it tonight15:16
rinigusI am sure @b100dian is also looking forward. will build on obs in a sec15:17
rinigus@b100dian and mal : new lvm helped! we have partitions mounted18:21
rinigusmal: now it reboots into bootloader18:21
rinigusI remember you having a fix for that18:21
T42<b100dian> great, lvm update helped18:21
T42<adampigg> good to watch your progress :)18:21
T42<b100dian> you mean if you leave it running it reboots? Need to see some logs. I am curl-ing the lvm/asio packages now18:22
rinigus@b100dian: I will upload hal packages to OBS with updated init script - the one with sleep instead of usleep18:25
riniguswill take few minutes18:25
T42<b100dian> thanks18:25
rinigusI actually reflashed it, to check if obs is up to date. wasn't in terms of init :)18:26
rinigusif you let it boot into sfos, it does proceed after, but at some moment just reboots into bootloader. I remember mal asked about it, will have to see the logs18:27
rinigus@adampigg: progress is relatively slow, but it is there :)18:27
rinigusfrom grepping logs: seems its related to https://android.googlesource.com/platform/build/+/refs/heads/main/target/product/gsi/init.vndk-nodef.rc18:33
malyes, either set the property or patch that file to not reboot18:34
malI haven't yet found what the root cause of the issue is18:35
rinigussounds like patching the file is easier. now just will have to find where it is ...18:38
rinigusI wonder whether this property is somewhere defined in aosp sources. will look around a bit18:39
T42<b100dian> rinigus: I don't have a bootloader reboot, but I do have a reboot https://paste.mozilla.org/erKpNKQ8/raw - do you have logcat for that early-init thingie? I didn't manage to launch logcat timely19:03
rinigusno logcat. but if we look here then we can see where it is called from: https://android.googlesource.com/platform/build/+/refs/heads/main/target/product/gsi/init.gsi.rc19:05
rinigusso, we need to have ro.vndk.version defined19:05
rinigusI wonder if we have one in our getprop19:06
*** deathmist1 is now known as deathmist19:06
rinigusweird, but there are no files other than nodef in /system/system_ext/etc/gsi/19:14
rinigusmal and @b100dian: I had older logs from AOSP. in those logs, this service is parsed but fails. see https://paste.mozilla.org/H3xmUTkm/raw19:19
rinigusso, we should probably just disable it.19:19
T42<b100dian> lol, so it doest reboot because 🤦19:27
T42<b100dian> I'm still unsure if mine rebooted to bootloader - what does that mean, normal reboot?19:30
T42<b100dian> cant really disable an on early-init hook though, you mean editing the partition?19:32
riniguslooking exactly for the same solution - how do I disable it...19:33
rinigusas for reboot. for me, with usb connected, I reboot into "blue light"19:33
malrinigus: some other file is loading that based on build prop19:33
malforgot which, need to check19:33
malyou can grep for gsi.*rc in /*/etc/init/*19:34
rinigusthe one in /system_ext/etc/init/init.gsi.rc19:34
rinigusmal: is there a way to disable that file specifically from hybris side? as we do with disabled_services19:35
T42<b100dian> that's just19:35
T42<b100dian> import /system/system_ext/etc/gsi/init.vndk-${ro.vndk.version:-nodef}.rc19:35
rinigus@b100dian exactly19:36
T42<elros34> mount /dev/null to this file19:37
T42<b100dian> ah, voice of reason!19:37
T42<b100dian> that could work ;)19:37
rinigusbut sounds like this is aosp bug.19:40
T42<b100dian> # mount -o bind /dev/null /system/system_ext/etc/gsi/init.vndk-nodef.rc19:40
rinigus@elros34: how would I do that? using systemd service19:40
riniguswill have to look it up19:41
T42<elros34> I guess probably n oraml mount unit will do the job19:41
T42<elros34> I think simple droid-hal-early-init .sh is not bad idea too19:43
rinigusthanks, that would probably work indeed19:44
T42<b100dian> yeah, i added that to /usr/bin/droid/droid-hal-early-init.sh19:45
T42<b100dian> SELinux: Loaded vndservice context from: /vendor/etc/selinux/vndservice_contexts19:50
T42<b100dian> time to grap those selinux files from actual device/image19:50
rinigus@b100dian I'll be afk. Will try to catch up tomorrow19:56
ecrnthings get super weird20:29
ecrnthe very first problem with hwcomposer was that it was segfaulting at exynos_open, due to messed memory leading to getExynosHWCService returning junk address20:30
ecrnwhen I patched out the hwcomposer module to ignore return value of getExynosHWCService and assume simply that it failed, the hwcomposer worked to the extent which allowed me to run lomiri composer displaying loading screen20:31
ecrnBUT the thing is20:32
ecrntest_hwcomposer didn't segfault20:32
ecrnand I made an isolated case from its code, that loads the hwcomposer module and calls hwc_open_120:33
ecrnwhich in turn calls exynos_open20:33
ecrnthat also doesn't segfault20:33
ecrnall these things don't segfault even on the "unpatched" hwcomposer module20:33
ecrnonly if it is the android.hardware.graphics.composer@2.4-service  that loads the module, there is segfault20:35
ecrnso I checked what else is done in the android sources for the composer 2.420:36
ecrnthe answer is: not much20:36
ecrnafter some boilerplate, the function below is reached iimmediately20:37
ecrnhttps://android.googlesource.com/platform/hardware/interfaces/+/refs/tags/android-14.0.0_r75/graphics/composer/2.1/utils/passthrough/include/composer-passthrough/2.1/HwcLoader.h?autodive=0%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F#10020:37
ecrnso then, the fault mystery is getting interesting20:38
ecrnis it possible that somehow the module loading is the problem? does libhybris use other rtld implementation for example for android "native" versus globc programs?20:39
ecrnglibc20:39
ecrnbecause the hw_get_module on android is a rtld action20:39
maldoes it load correct lib?20:40
ecrnprobably, how do I check? right now there is only one hwcomposer.*.so in my linking paths20:42
ecrnor you mean some other lib?20:43
ecrnor, maybe there is some stack size issue?21:03
ecrnquite unlikely21:03
ecrncopying bionic from original image crashes something so that it stops initializing usb21:20
malis that android 14 base?21:27
ecrnandroid 12 hopefully21:27
ecrnI mean, I have both 12 and 14 downloaded and I flashed 1221:28
malI think nobody has used android 12 base before21:28
malat least not on sailfish device21:28
ecrnxperia III can also work with android 12 base if the instructions are correct21:30
ecrnso are things that much different?21:30
malnot sure what you mean21:33
malif you mean the flashing instructions about which android to have before flashing sailfish then it's a different thing, sfos flashing on x10iii replaces everything except firmware partitions etc21:35
ecrnok21:35
T42<b100dian> rinigus: I pushed selinux and droid-hal-early-init.sh (edited on device, build not tested)21:40
T42<b100dian> I had to change odm.mount to sda76 instead of sda76_a (why?) and added CMDLINE+=audit=0 in my BoardConfig.mk for clarity in logs21:40
T42<b100dian> not sure why is there /odm and /odm_root as the latter was supposed to be linked to|from /odm/etc ? or is it only for Lineage21:40
T42<b100dian> With droid-hal-init masked and started after checking /odm mount I got a first logcat https://paste.mozilla.org/DB2HDAqy/raw21:40
T42<b100dian> We have tombstones in /data/tombstones ;)21:40
ecrnreplacing the com.android.runtime files with original ones yielded:21:44
ecrnNov 14 14:32:58 ubuntu-phablet lxc-android-ready[3501]: TLS relocations not yet implemented in libhybris21:44
malwhich libhybris version do you have?21:49
ecrnprobably some old one22:01
ecrnit has only up to q.so22:01
ecrnin the linker directory22:01
ecrnVersion: 0.1.0+git20240229+9dea23c-0ubports1+0~20240912111840.3+ubports20.04~1.gbp1dda9922:02
malq is latest linker in lihybris but we add TLS relocation support on August 13th22:06
mal*added22:06
ecrnok22:07
ecrnI could update if you recommend to, but that only prevents systemd from continuing boot beyond the container (and possibly will prevent using glibc programs after that) with the original rom's libc22:08
ecrnthe container still booted, and has the same exact issue with hwcomposer22:09
ecrnso I probably don't need to replace the bionic libs22:09
ecrntrying to run /vendor/bin/hw/android.hardware.graphics.composer\@2.4-service directly makes it fork and then segfault22:19
maldoes strace or gdb reveal anything?22:23
malfor gdb HYBRIS_ENABLE_LINKER_DEBUG_MAP=1 env var is helpful22:23
ecrnhm, it didn't segfault after forking, just exited immediately22:26
ecrnI mistaken logcat entry for the restarted service22:26
malwhat does logcat say?22:26
ecrnnothing about the manually started file22:27
ecrnbut about the init service there are repeating segfaults as it tries to restart it22:27
ecrnhttps://pastebin.k4be.pl/view/raw/b3e6572122:29
malstrace with manual start?22:29
ecrnthe gdb does in fact show something interesting22:30
malok22:30
ecrnBFD: /android/system/lib64/libnetd_client.so: unknown type [0x13] section `.relr.dyn'22:30
ecrnwarning: `/android/system/lib64/libnetd_client.so': Shared library architecture unknown is not compatible with target architecture aarch64.22:30
ecrnand others like22:30
malmaybe try updating libhybris22:31
ecrnbut does it even come into play in the container itself?22:32
malI have no idea how that container works22:32
ecrnrunning /vendor/bin/hw/android.hardware.graphics.composer\@2.4-service through lxc-attach worked and gave segfault22:36
ecrnrunning without the lxc-attach with the immediate exit seems to origin from it trying to open framebuffer devices and then failing, probably some environment issues, which is understandable22:37

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