| nightishaman | yep its stopping before the kernel modules | 00:05 |
|---|---|---|
| nightishaman | I did one after loadkernelmodules | 00:05 |
| mal | nightishaman: so reboot before load modules works but not after it? | 00:16 |
| nightishaman | i gotta try | 00:19 |
| nightishaman | it instantly reboots | 00:28 |
| mal | ok, so what is happening in module loading then | 00:31 |
| mal | why does it get stuck there | 00:31 |
| nightishaman | we could get funny creative, check if /dev/fb0 works, draw 50 different images and push a different based on how many modules loaded | 00:34 |
| mal | heh | 00:36 |
| mal | I don't think framebuffer usually works in android kernel | 00:38 |
| nightishaman | alternatively, does this device have ramps? | 00:38 |
| nightishaman | ramoops? | 00:38 |
| mal | usually pstore can be read | 00:40 |
| nightishaman | im booting into recovery and will check it out | 00:40 |
| mal | yeah, causing a kernel panic and then reading pstore in recovery it should contain kernel logs | 00:41 |
| nightishaman | when I tried to port the Sony Xperia 5 IV, I had used that to find a bug in a driver | 00:41 |
| nightishaman | to ubuntu touch | 00:41 |
| nightishaman | pstore might not be enabled | 00:42 |
| mal | but debugging with that is a bit difficult also since we can't know which module loading is causing the issue | 00:42 |
| nightishaman | what do you suggest? | 00:44 |
| mal | not sure really, other than very slow test of incrementally loading modules one by one and seeing when it hangs | 00:45 |
| nightishaman | oof | 00:45 |
| mal | so first loading the first module in modules.load list, then two and so on | 00:45 |
| nightishaman | better idea, binary searching | 00:45 |
| mal | sure | 00:45 |
| nightishaman | cut half the modules and try again | 00:45 |
| mal | faster that way probably | 00:46 |
| nightishaman | i just gotta figure out where the modules.load is defined | 00:46 |
| mal | you don't need to know that | 00:47 |
| mal | just edit the init-script load function to have a counter and set the limit number in each test | 00:47 |
| mal | like load 20 first modules and break the loop once counter is 20 | 00:48 |
| nightishaman | my bash skills arent that good, or lets say almost 0 | 00:49 |
| mal | btw how long does that make hybris-init_boot take for you? | 00:49 |
| nightishaman | approximately 20 seconds | 00:49 |
| mal | ok, then that is not a problem | 00:49 |
| nightishaman | the most part is android soong before starting ninja | 00:50 |
| mal | I just thought if the whole make is slow then there are other ways to edit the init_boot image | 00:50 |
| nightishaman | i got a ryzen 5800x3d and its on an nvme | 00:51 |
| nightishaman | running fedora linux | 00:52 |
| nightishaman | i got this now: https://pastebin.com/Za2hryk2 | 01:00 |
| nightishaman | the module seems to be in the first half | 01:05 |
| nightishaman | first quarter | 01:09 |
| nightishaman | the module is in the 2nd eigth | 01:13 |
| nightishaman | above 25, less than 51 | 01:13 |
| nightishaman | above 25, less than 37 | 01:15 |
| nightishaman | above 25, less than 31 | 01:19 |
| Solrac[m]1 | This is slightly off topic, but I wanted to ask, [@_oftc_mal:matrix.org](https://matrix.to/#/@_oftc_mal:matrix.org) do you have fp4 Hailium source? Do you think I can use it to test droidian? | 01:19 |
| nightishaman | Solrac[m]1 ask in the ubuntu touch telegram group, halium is their system | 01:21 |
| nightishaman | above 25, less than 28 | 01:21 |
| nightishaman | im gonna do -1 steps now | 01:21 |
| Solrac[m]1 | nightishaman: Their Hailium is based on a much older Hailium, for some, some networks do not work proper. I tired the official a11 and then flashed sfos, and had no connectivity,any version older than ofw was, didn't have this issue. I've yet to try e/OS for Hailium instead | 01:23 |
| nightishaman | sailfishos uses hybris | 01:24 |
| mal | Solrac[m]1: is a11 the latest official for fp4? | 01:25 |
| mal | Solrac[m]1: I didn't quite understand what the problem is | 01:25 |
| nightishaman | i think they want to use the boot system of halium for other os or somehow port it | 01:26 |
| nightishaman | mal: its module at index 26, max 26 it hangs, max 25 it doesnt | 01:26 |
| nightishaman | 0 indexed | 01:26 |
| mal | nightishaman: what is number 26? | 01:26 |
| nightishaman | mal: extra/private/google-modules/soc/gs/drivers/soc/google/debug/exynos-coresight-etm.ko | 01:29 |
| mal | nightishaman: ok, I suspected that when you said above 25, less than 28 | 01:29 |
| mal | so as a test add a hacky condition to the loop to skip that | 01:30 |
| Solrac[m]1 | nightishaman: That's pretty much it. Basically, I can't use Ubuntu Touch Helium because it requires a much older version of Android and 11 specifically, and the latest build had some issues with some carriers on mine included. So, I figured, instead of using that old version, maybe I could use the Helium version that's used for sfos and try porting Droidian. | 01:32 |
| Solrac[m]1 | Since Mobian and Postmarket OS are using a kernel that is not feature complete yet. | 01:32 |
| mal | Solrac[m]1: sailfish on fp4 doesn't use halium | 01:33 |
| nightishaman | while ubuntu touch uses the same base, their init system is different to Sailfish OS, you can't use that | 01:33 |
| mal | nightishaman: some sailfish ports use halium but not many | 01:33 |
| Solrac[m]1 | mal: Wait what, really? | 01:34 |
| mal | Solrac[m]1: I use the sailfish way of porting meaning building patched parts of android and so on | 01:34 |
| Solrac[m]1 | nightishaman: The problem with helium is that it's very dependent on the version of Android that you're using, and in my case, Android 11 gives sobre carrier issues | 01:34 |
| mal | Solrac[m]1: which android version is ok for you? | 01:35 |
| Solrac[m]1 | mal: Part in my ignorance since I haven't tried porting this OS to a device yet. Is this similar to what pmOS is doing? as in apply the relevant patches to a seemingly mainline kernel? | 01:36 |
| mal | Solrac[m]1: no, we use android hal for some things like graphics and other hw features | 01:36 |
| mal | Solrac[m]1: so you had issues when you tried sailfish os? you know before you install sailfish you can have android 14 or maybe even newer one on the device | 01:37 |
| mal | the fp4 sailfish port is actually using android 14 as base for the hardware parts | 01:39 |
| nightishaman | mal: I'll look into enabling pstore, because for some reason, it doesnt reboot at 25 anymore | 01:44 |
| Solrac[m]1 | mal: Do you might remember that I had some network issues, but that was when I flashed the first time. When I flashed it the next time I had no network issues at all. That was because I was using the wrong Android version the first time | 02:01 |
| Solrac[m]1 | s/Do/You/, s/you// | 02:02 |
| mal | yeah, to that second time you probably had some newer android on the device before sailfish | 02:02 |
| Solrac[m]1 | mal: Also, do part in my ignorance. I have only tried porting via Hailium once before. My understanding is that haleum uses whatever system and then bridges it to whatever kernel to boot. But how does hal work? | 02:03 |
| mal | sailfish on fp4 doesn't care that much about the android version since it only use some firmware etc from the android that was there before | 02:03 |
| Solrac[m]1 | mal: I had used official Android 11 and the second time I used eOS with Android 14. | 02:03 |
| Solrac[m]1 | mal: Ahh | 02:04 |
| nightishaman2 | mal: ok bad thing, my znc host is down | 02:04 |
| nightishaman2 | pstore is enabled and unfortunately emtpy | 02:04 |
| mal | Solrac[m]1: have you tried some halium installation but without reflashing everything from a11 for example, only flashing super partition content (system, vendor etc), I assume it probably needs those but the other parts probably can be from newer android version | 02:06 |
| nightishaman | mal: do you know which syntax the sh interpreter that is running the init script supports? | 02:09 |
| nightishaman | because maybe my counter is bugged or not interpreted correctly, although i find it weird that it rebooted one time | 02:09 |
| mal | not fully sure but maybe avoid bash stuff | 02:13 |
| nightishaman | mal: ok it fails even loading the first module | 02:35 |
| nightishaman | which is zsmalloc | 02:35 |
| Solrac[m]1 | mal: I used boot.img only, but the reason why I asked was to try porting Mobian, if it needs a custom setup, I imagine its better off starting from scratch | 02:37 |
| mal | nightishaman: very odd | 02:41 |
| nightishaman | should i try disabling module signature check? | 02:43 |
| mal | maybe | 02:44 |
| mal | but how would that cause modprobe to hang | 02:44 |
| mal | I need some sleep again | 02:45 |
| nightishaman | im gonna go soon too | 02:45 |
| nightishaman | claude says modules without signature cant access modules with signature | 02:45 |
| nightishaman | CONFIG_MODULE_SIG=y | 02:46 |
| nightishaman | CONFIG_MODULE_SIG_PROTECT=y | 02:46 |
| nightishaman | mal: im gonna test this hypothesis tomorrow, but it might be that when i flashed the kernel with additional flags, i didnt flash vendor_kernel_boot and the kernel is rejecting the modules. no idea why it hangs then tho | 03:43 |
| *** Nokius7 is now known as Nokius | 03:55 | |
| T42 | <elros34> you should try with clean kernel without any sfos related changes | 10:15 |
| T42 | <elros34> also same question did you check check_kernel_config function? Did you format /data and you are 100% sure there is no encyption there? | 10:27 |
| rinigus | mal and b100dian : I wrote down eSIM case as an issue: https://forum.sailfishos.org/t/enabling-esim-modem-prevents-lipstick-login/29652 . Sorry for long text, but I hope it has sufficient details to trace the origin. | 15:22 |
| rinigus | it seems to me that lipstick and PinQueryAgent interaction together with minimal ofono dbus properties for eSIM leads to such case | 15:23 |
| rinigus | I've included dbus data as well as results of tracing this bug in lipstick. unfortunately, I've hit closed-source wall and need someone behind it to check it out :) | 15:23 |
| mal | rinigus: thanks, I'll check that | 15:48 |
| rinigus | mal: thanks! | 15:48 |
| T42 | <b100dian> rinigus: wow! thanks for the thoroughness:) | 16:02 |
| mal | rinigus: in settings it shows the esim slot as if there is sim present all the time | 16:13 |
| rinigus | mal: is this a question or statement? in my case, I have to disable under multisim settings the second sim. then I can boot | 16:18 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!