| nightishaman | mal: https://paste.centos.org/view/9c38941c | 00:06 |
|---|---|---|
| mal | comment out "Requires: gstreamer1.0-droid" from patterns in droid-config repo | 00:10 |
| mal | which should be in hybris/droid-configs/patterns/patterns-sailfish-device-adaptation-$DEVICE.inc | 00:11 |
| mal | then build_packages.sh -c again | 00:11 |
| mal | nightishaman: while at it check that you have correct version in droid-config spec | 00:12 |
| mal | like this but the version you have in use which I understood is 16 https://github.com/mlehtima/droid-config-fp5/blob/master/rpm/droid-config-fp5.spec#L7 | 00:12 |
| nightishaman | also gmp-droid | 00:12 |
| nightishaman | ? | 00:12 |
| mal | yes, gmp-droid can go also | 00:13 |
| nightishaman | I wonder whether my esim will work | 00:21 |
| nightishaman | its still saved in the phone, it survived across reflashes | 00:21 |
| nightishaman | its finished | 00:24 |
| nightishaman | now I just need to boot into recovery mode and apply the zip file from add? | 00:24 |
| nightishaman | adb? | 00:24 |
| mal | something like that | 00:31 |
| nightishaman | hmm | 00:32 |
| nightishaman | it couldn't flash because it couldn't mount userdata | 00:32 |
| nightishaman | i have to recheck the paths | 00:32 |
| nightishaman | the paths exist | 00:39 |
| mal | is userdata in correct format? | 00:40 |
| mal | we want it to be ext4 | 00:41 |
| nightishaman | probably not | 00:41 |
| nightishaman | I can use adb shell for that | 00:41 |
| mal | I need to get some sleep now | 00:44 |
| nightishaman | okay | 00:44 |
| nightishaman | mal: once you wake up, the install process fails because the recovery environment has no bzip2 support | 01:26 |
| T42 | <elros34> common issue, use gzip instead https://sailfishos.wiki/link/20#bkmrk-%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0-%2A-twrp-is-kn | 01:47 |
| rinigus | Mister_Magister: look for system apk's that can be of interest. At some point I decompiled a large bunch of them and just grepped for info | 05:20 |
| mal | Mister_Magister: I had a bit of a look at the refresh rate things in hwc, there are two things, setting a specific refresh rate and then the variable refresh rate in which it can change all the time based on content or something | 13:12 |
| Mister_Magister | mal: yeah the latter would be the best i think | 13:19 |
| Mister_Magister | and the hardest xd | 13:19 |
| Mister_Magister | so far i have one port that's locked to 120Hz and i locked my new port to 120Hz as well | 13:20 |
| Mister_Magister | but obviously if we could drop that when there's nothing happening on the screen it'd save power | 13:20 |
| Mister_Magister | just i think we'd need to implement hwc3 no? | 13:21 |
| mal | yeah, we could consider forcing lower also in case someone wants to save power | 13:21 |
| mal | we basically have hwc3 already, in the compat code | 13:21 |
| Mister_Magister | or like if low power mode is enabled (sfos has one idk how much it does) | 13:21 |
| mal | we just haven't named it hwc3 | 13:22 |
| Mister_Magister | it'd be smart to limit it to 60Hz in low poer mode | 13:22 |
| Mister_Magister | gotcha | 13:22 |
| Mister_Magister | well it's something that I think should be implemented going forwards cause literally nobody makes 60Hz only phones anymore | 13:22 |
| mal | afaik we just need to extend the hwc3_compatibility_layer | 13:22 |
| Mister_Magister | and like the new oleds can go as low as 5Hz or something | 13:23 |
| mal | forcing lower refresh rate should be quite simple in hwc level, just need to think how to get the info from UI level | 13:24 |
| Mister_Magister | how about higher refresh rate? :P cause default is often 60Hz and losing 120Hz would be a shame | 13:24 |
| mal | well same thing is used for both | 13:25 |
| Mister_Magister | ye | 13:25 |
| Mister_Magister | mine has 48, 60, 90, 120Hz | 13:25 |
| Mister_Magister | https://github.com/VerdandiTeam/android_kernel_motorola_sm6375/commit/77fbb7f9861b17582d8d21edcacf2eb31cfc4958#diff-e75ed31b62dcf37090b02f434beaf1a7c9eb1703d6bd0659fc4b5a7804464631L372-L387 | 13:26 |
| mal | PSA: any porters testing 5.1, you need at least qt5-qpa-hwcomposer-plugin 5.6.2.26 for suspend to work, also a note that 5.6.2.27 requires update of the libhybris hwc2 compat module in hybris-hal build (i.e. in droid-hal packages) | 14:03 |
| T42 | <CRK_11755> Are any of you boys and girls running this on fairphone 4 | 15:19 |
| Mister_Magister | in fact the guy who ported sfos on fp4 is right above you | 15:20 |
| mal | @CRK_11755 I haven't yet tested fairphone devices with 5.1, I know some things that need to be fixed already though | 16:10 |
| T42 | <CRK_11755> Okay great thank you | 16:28 |
| nightishaman | mal: I flashed all the img files yesterday to the device and extracted the rootfs to /data/.stowaways/sailfishos, but when booting now, it stays at the Google logo for 30 seconds and then reboots. How can I debug this? | 17:30 |
| mal | nightishaman: do you see anything host dmesg? | 17:33 |
| nightishaman | nope | 17:33 |
| nightishaman | the last entry was from fastboot | 17:33 |
| mal | you flashed 4 images? | 17:33 |
| mal | boot, init_boot, dtbo and vendor_boot | 17:34 |
| mal | assuming you have all of those | 17:34 |
| nightishaman | I flashed from out/target/product/panther: boot, init_boot, dtbo, vendor_boot and vendor. I flashed from device/google/pantah-kernels/6.1/: vendor_dlkm and vendor_kernel_boot | 17:35 |
| mal | hmm, what are those last ones | 17:36 |
| nightishaman | vendor_dlkm is kernel modules | 17:36 |
| nightishaman | vendor_kernel_boot no idea | 17:36 |
| mal | but aren't those in super partition usually | 17:36 |
| mal | I mean vendor_dlkm | 17:36 |
| mal | that is too high levelfor current debugging anyway, current target is to get telnet into init | 17:37 |
| nightishaman | they are, I flashed in fastbootd in LineageOS recovery | 17:38 |
| mal | do you have rndis functionfs stuff enabled in defconfig? | 17:38 |
| mal | but 30 seconds is too short for usb related issues which would trigger at 60 seconds | 17:38 |
| mal | I suspect it somehow doesn't like the boot images | 17:39 |
| mal | I wonder if it wants signed boot images or not | 17:39 |
| nightishaman | before I didn't flash vendor_boot, only boot. then it would restart immediately, so I guess not | 17:40 |
| nightishaman | which config is rends? | 17:41 |
| nightishaman | rndis? | 17:41 |
| mal | something like these https://github.com/mlehtima/android_kernel_fairphone_qcm6490/blob/hybris-23.2/arch/arm64/configs/vendor/fp5-qgki_defconfig#L1031 | 17:42 |
| mal | are the sizes of the boot images reasonable looking+ | 17:43 |
| mal | hmm, so you extracted the rootfs, I just wonder how far it actually boots | 17:49 |
| mal | without rootfs in userdata it would always stop in init telnet | 17:50 |
| nightishaman | I can delete the userdata | 17:54 |
| nightishaman | also Rndis is not set | 17:55 |
| mal | enable rndis and see if anything changes | 17:59 |
| nightishaman | I just have to flash boot img then, the kernel is on that, correct? | 18:23 |
| mal | vendor_boot also probably since it might affect module layout or something | 18:24 |
| nightishaman | vendor_kernel_boot too I think | 18:24 |
| nightishaman | https://source.android.com/docs/setup/build/building-pixel-kernels?hl=de#update-the-vendor-ramdisk | 18:24 |
| nightishaman | vendor_kernel_boot might contain kernel artifacts | 18:24 |
| mal | hmm, wait | 18:24 |
| mal | was that pixel 7 you have? | 18:25 |
| nightishaman | yes | 18:25 |
| mal | so that section doesn't apply to it | 18:25 |
| nightishaman | just the warning it says there | 18:25 |
| mal | I need to check a bit what kind of partition setup your device has | 18:25 |
| nightishaman | that pixel 7 and up split vendor_boot into vendor_boot and vendor_kernel_boot | 18:26 |
| mal | I need to read that to know what changes we might need | 18:26 |
| nightishaman | Important: Skip this section for Pixel 7 and later devices. Only Pixel 6, Pixel 6 Pro, and Pixel 6a devices need to update the vendor ramdisk. Pixel 7 and later devices split the vendor_boot partition into two partitions -- vendor_boot and vendor_kernel_boot -- where the kernel artifacts are fully contained by the vendor_kernel_boot image. | 18:26 |
| nightishaman | I have to find out how to mount the images on my host system, to check out what's in there | 18:27 |
| mal | you don't have to mount them, I can tell how to get the content | 18:27 |
| nightishaman | ill be back in half an hour | 18:27 |
| mal | https://android.googlesource.com/platform/system/tools/mkbootimg/+/refs/heads/main this has unpack_bootimg.py which can be used to extract the content of boot images, clone that and use the tool | 18:28 |
| mal | the extracted ramdisks are there but usually don't have file extension correctly so copy the ramdisks and rename to something.cpio.lz4 after which those can be decompressed more easily | 18:29 |
| nightishaman | mal: jannikmueller@fedora:~/hadk/image$ ls | 19:07 |
| nightishaman | bootconfig dtb vendor_ramdisk00 vendor-ramdisk-by-name | 19:07 |
| nightishaman | it contains the vendor ramdisk | 19:07 |
| mal | what does your vendor_boot contain? | 19:13 |
| nightishaman | okay the ramdisk contains modules | 19:14 |
| nightishaman | only modules, the dtb and bootconfig | 19:14 |
| mal | ok | 19:14 |
| mal | so the init side of the ramdisk is probably in vendor_boot then | 19:14 |
| mal | that just means both need to be flashed | 19:15 |
| mal | the modules are the more important part | 19:15 |
| nightishaman | vendor_boot seems to be the init ramdisk | 19:18 |
| nightishaman | https://paste.centos.org/view/c8718556 | 19:18 |
| mal | what is in init_boot? | 19:21 |
| mal | does the device even use init_boot | 19:22 |
| mal | if init is in vendor_boot | 19:22 |
| mal | I mean that file init | 19:23 |
| nightishaman | init_boot contains kernel and Ramdisk, which contains init | 19:24 |
| nightishaman | kernel is an empty file | 19:25 |
| mal | yes, empty kernel there is normal | 19:26 |
| mal | that vendor_boot is a bit of question | 19:26 |
| mal | if the init there a file or a symlink? | 19:26 |
| mal | also in init_boot | 19:26 |
| nightishaman | init_boot is a normal file | 19:27 |
| nightishaman | vendor_boot was a symlink | 19:27 |
| mal | do you happen to have init_boot from a normal android build available? | 19:27 |
| mal | I think you could get it from lineage builds | 19:28 |
| nightishaman | i have lineage local yes | 19:28 |
| mal | just to see what it contains | 19:28 |
| nightishaman | jannikmueller@fedora:~/lineage/out/vrd_extracted$ ls | 19:29 |
| nightishaman | debug_ramdisk dev first_stage_ramdisk init metadata mnt proc second_stage_resources sys system | 19:29 |
| mal | is that init a normal file | 19:30 |
| nightishaman | init is a file, the rest are folders | 19:30 |
| mal | ok | 19:30 |
| nightishaman | jannikmueller@fedora:~/lineage/out/vrd_extracted$ file init | 19:30 |
| nightishaman | init: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, for Android 36, BuildID[md5/uuid]=d7c8c6c70ea911cf6c4daed50d405649, stripped | 19:30 |
| nightishaman | i flashed the kernel with rndis enabled, im gonna try to boot it | 19:30 |
| mal | I just had a look that bootloader should copy init_boot over vendor_boot ramdisk during boot so we should be getting the correct init into use | 19:30 |
| mal | just to be sure, you flashed hybris-init_boot.img? | 19:31 |
| nightishaman | fuck | 19:31 |
| nightishaman | I knew I forgot something | 19:31 |
| mal | to init_boot | 19:31 |
| nightishaman | not booting | 19:34 |
| nightishaman | im back into fastboot | 19:34 |
| mal | hmm | 19:35 |
| mal | and you flashed also boot image | 19:35 |
| nightishaman | vendor_kernel_boot, vendor_boot, init_boot and boot | 19:35 |
| mal | does it behave differently with init_boot.img and hybris-init_boot.img? assuming you have both | 19:36 |
| nightishaman | I only have hybrid-init_boot | 19:37 |
| nightishaman | I could flash lineage init_boot | 19:37 |
| nightishaman | https://pastebin.com/zpLGfbhW | 19:38 |
| nightishaman | i have those images | 19:38 |
| mal | ok | 19:38 |
| mal | how did it behave in that last boot? same 30 second delay to reboot or directly to fastboot? | 19:40 |
| nightishaman | 30 second delay then black screen and then I pressed fast boot key combination | 19:41 |
| T42 | <elros34> did you ever check for init.log existence? | 19:42 |
| nightishaman | nvm | 19:42 |
| nightishaman | it was 60 seconds | 19:42 |
| nightishaman | I just measured | 19:42 |
| mal | ok, that could be then usb issue | 19:43 |
| mal | https://github.com/mer-hybris/hybris-boot/blob/a16/init-script#L307 just for our information | 19:43 |
| mal | *your | 19:43 |
| mal | but nothing in host dmesg still? | 19:43 |
| T42 | <b100dian> did you flash boot or hybris-boot to boot partition? | 19:44 |
| nightishaman | only the bootloader | 19:44 |
| mal | there are some cases where the usb related udc handling is done in a way that is not supported in our init script | 19:45 |
| nightishaman | boot.img, hybris-boot.img is never created, that was just boot.img that I copied earlier as mal told me I can use the boot.img from the kernel build | 19:45 |
| nightishaman | it only contains the kernel anyway | 19:45 |
| mal | @b100dian would not matter in this case since boot img only contains kernel anyway | 19:45 |
| nightishaman | would the init.log be on user data @elros43 | 19:46 |
| T42 | <b100dian> ah, so the rest is in hybris-init_boot. Ok ;) | 19:46 |
| nightishaman | yes, the init ramdisk is in init_boot and vendor_boot | 19:46 |
| nightishaman | kernel modules in vendor kernel boot | 19:46 |
| T42 | <elros34> yes https://sailfishos.wiki/link/20#bkmrk-%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0-%2A-if-your-de-1 | 19:48 |
| nightishaman | ok ill boot into recovery | 19:48 |
| T42 | <hraj9258> !notes | 19:48 |
| nightishaman | no init.log | 19:55 |
| nightishaman | Which ramdisk should contain the init-script? | 20:01 |
| nightishaman | the vendor_boot init symlinks points to system/bin/init | 20:02 |
| nightishaman | https://pastebin.com/y1fZPB9v | 20:03 |
| T42 | <hraj9258> which android base i can use to get started with porting sailfish os to my device ? | 20:10 |
| T42 | <hraj9258> | 20:10 |
| T42 | <hraj9258> my device alredy support lineage os 23.2 | 20:10 |
| T42 | <hraj9258> | 20:10 |
| T42 | <hraj9258> i also got halium based kernel running on my phoenix (POCO X2/ redmi k30), | 20:11 |
| mal | nightishaman: as I mentioned earlier based on what I found is that init_boot overrides anything in vendor_boot so the init in init_boot should be the one used | 20:12 |
| mal | nightishaman: that link earlier about init.log is only relevant if you have rootfs in place | 20:13 |
| nightishaman | hmm | 20:18 |
| nightishaman | ok the init is the hybris oe | 20:18 |
| nightishaman | one | 20:18 |
| mal | can you check in android recovery a couple of things | 20:19 |
| T42 | <elros34> @hraj9258 you can use it: https://irclogs.sailfishos.org/logs/%23sailfishos-porters/2026/%23sailfishos-porters.2026-05-13.log.html#t2026-05-13T23:59:28 | 20:20 |
| nightishaman | yes | 20:23 |
| nightishaman | what should I check | 20:23 |
| T42 | <hraj9258> @elros34 thanyou | 20:25 |
| mal | nightishaman: what do you have under /sys/class/udc/ | 20:28 |
| nightishaman | 1|panther:/ # ls /sys/class/udc | 20:28 |
| nightishaman | 11210000.dwc3 | 20:28 |
| mal | ok, then what does this show: cat /sys/class/udc/11210000.dwc3/device/../mode | 20:29 |
| nightishaman | https://pastebin.com/NqaSQhrq | 20:33 |
| mal | I wonder if that is the reason | 20:36 |
| mal | can you check /sys/devices/platform/soc/ if there are any paths with that 11210000 | 20:36 |
| nightishaman | 1|panther:/ # ls /sys/devices/platform/soc | 20:40 |
| nightishaman | ls: /sys/devices/platform/soc: No such file or directory | 20:40 |
| mal | hmm, or elsewhere there under /sys/devices/ | 20:42 |
| mal | maybe do this: find /sys/devices -name '*11210000*' | 20:42 |
| mal | or this: find /sys/devices -name mode | 20:43 |
| nightishaman | https://pastebin.com/ux0vu0cw | 20:44 |
| mal | check under /sys/devices/platform/11210000.usb/ | 20:46 |
| nightishaman | panther:/ # ls /sys/devices/platform/11210000.usb/ | 20:46 |
| nightishaman | 11210000.dwc3 dwc3_exynos_otg_state supplier:i2c:13-0025 | 20:46 |
| nightishaman | driver force_speed supplier:phy:phy-11200000.phy.9 | 20:46 |
| nightishaman | driver_override modalias supplier:platform:11200000.phy | 20:46 |
| nightishaman | dwc3_exynos_extra_delay new_data_role supplier:platform:18062080.pd-hsi0 | 20:46 |
| nightishaman | dwc3_exynos_gadget_state of_node supplier:platform:1e080000.clock-controller | 20:46 |
| nightishaman | dwc3_exynos_otg_b_sess power uevent | 20:46 |
| nightishaman | dwc3_exynos_otg_id subsystem usb_data_enabled | 20:46 |
| mal | what does that usb_data_enabled contain? | 20:48 |
| nightishaman | 130|panther:/ # cat /sys/devices/platform/11210000.usb/usb_data_enabled | 20:49 |
| nightishaman | enabled | 20:49 |
| nightishaman | i have a feeling we have to enable that | 20:50 |
| mal | nightishaman: does this work cat /sys/class/udc/11210000.dwc3/device/../usb_data_enabled | 20:51 |
| T42 | <elros34> disable and see what will happen:P | 20:51 |
| mal | I suspect we need to add write to that next to this https://github.com/mer-hybris/hybris-boot/blob/a16/init-script#L251C11-L251C43 | 20:52 |
| mal | but we'll if can use the same method | 20:52 |
| nightishaman | panther:/ # cat /sys/class/udc/11210000.dwc3/device/../usb_data_enabled | 20:53 |
| nightishaman | enabled | 20:53 |
| mal | ok, so edit hybris/hybris-boot/init-script in the place where I just linked, add new line with this: write /sys/class/udc/"$udc"/device/../usb_data_enabled 1 | 20:54 |
| mal | then in the same enviroment you build hybris-hal run make hybris-init_boot | 20:55 |
| mal | then flash the hybris-init_boot.img you get | 20:55 |
| nightishaman | in which function its best? | 20:57 |
| mal | https://github.com/mer-hybris/hybris-boot/blob/a16/init-script#L251C11-L251C43 after that line | 20:57 |
| nightishaman | mal: still reboots, maybe it uses android_usb | 21:43 |
| T42 | <elros34> maybe I am missing something but why do you even care about it now, init-scripts shouldn't stop unless for example you have missing some kernel config or some problems with init-debug script. It's much easier to debug init-debug (it's same copy of script) because you can pull init.log logs via recovery | 21:57 |
| nightishaman | im not getting any init.log logs tho | 21:58 |
| T42 | <elros34> but you have reboot after 60s? | 21:59 |
| nightishaman | yes | 22:00 |
| T42 | <elros34> do you have all this correct: https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L346 | 22:00 |
| mal | maybe then disable the code that cause it to reboot and see if gets further | 22:00 |
| nightishaman | you mean at line 318 | 22:02 |
| mal | https://github.com/mer-hybris/hybris-boot/blob/a16/init-script#L308 | 22:04 |
| T42 | <elros34> no L346 check_kernel_config function | 22:04 |
| mal | nightishaman: one thing to check in the vendor_kernel_boot you extracted, does it contain modules.load.recovery or something in /lib/modules/ | 22:05 |
| nightishaman | hmm, it still rebooted after 1 minute | 22:07 |
| nightishaman | mal: only modules.load | 22:10 |
| mal | ok, then that is a problem | 22:10 |
| mal | because as you can see init-script only tries to use modules.load.recovery, try changing that | 22:11 |
| mal | https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L143 | 22:11 |
| mal | I wonder if that modules.load loads enough usb things | 22:11 |
| nightishaman | its also not at lib/modules | 22:11 |
| mal | where is it? | 22:12 |
| nightishaman | lib/modules/6.1.145-android14-11-g2ea333278635 | 22:12 |
| nightishaman | if uname -r gives the correct string, then it maybe is | 22:12 |
| mal | ok, then fix that module loading in the init-script | 22:12 |
| mal | can you show the modules.load file you have | 22:13 |
| nightishaman | wait no, the symlink is created that lib/modules/uname -r points to lib/modules | 22:13 |
| nightishaman | https://pastebin.com/uJCUksK1 | 22:14 |
| nightishaman | I switched it around | 22:14 |
| mal | the symlink is not needed in your case | 22:15 |
| mal | the point of it was it make sure there is /lib/modules/$(uname -r)/ | 22:15 |
| mal | hmm | 22:15 |
| mal | nightishaman: just to be sure, you are checking this in the extracted vendor_kernel_boot and not in recovery or anything | 22:16 |
| nightishaman | yes | 22:16 |
| nightishaman | jannikmueller@fedora-2:~/hadk/out_vendor_kernel_boot/vrd_extracted/lib/modules/6.1.145-android14-11-g2ea333278635$ | 22:17 |
| mal | ok, check the modules.load file for usb related configs | 22:17 |
| mal | but maybe just test what happens with that modified module loading | 22:18 |
| nightishaman | https://pastebin.com/KAtxWj0R | 22:19 |
| nightishaman | well it didn't reboot yet | 22:19 |
| mal | anything in host dmesg? | 22:19 |
| nightishaman | nope | 22:20 |
| mal | and this was with the reboot removed? | 22:20 |
| nightishaman | yes | 22:20 |
| nightishaman | i also added to setup android usb the code to enable usb_data | 22:20 |
| nightishaman | and the modules file path | 22:20 |
| nightishaman | so unless uname -r tells the wrong string, it is correct | 22:21 |
| nightishaman | im gonna force reboot it to recovery and check out data | 22:21 |
| mal | there are more complex ways to debug also, like writing debug logging to sdcard in init-script etc | 22:22 |
| nightishaman | if I had an sdcard slot | 22:22 |
| nightishaman | or an sdcard | 22:22 |
| mal | oh, it doesn't have that anymore? | 22:22 |
| nightishaman | nope | 22:23 |
| nightishaman | ok, maybe I have to hard code the path | 22:24 |
| nightishaman | panther:/ # uname -r | 22:24 |
| nightishaman | 6.1.145-android14-11-gec45f20f38ea-ab15260282 | 22:24 |
| nightishaman | it uses the same kernel and has an additional string in the back | 22:24 |
| mal | but vendor_kernel_boot has different string? | 22:24 |
| nightishaman | the path yes | 22:24 |
| mal | then there is some mismatch in the images you use | 22:25 |
| nightishaman | well this is the lineageos recovery | 22:25 |
| mal | ah | 22:25 |
| nightishaman | I can't test my kernel since we not having usb | 22:25 |
| nightishaman | but im gonna test the hard coding | 22:25 |
| mal | it seems that device has recovery in different partition | 22:26 |
| nightishaman | i have lingoes recovery on a slot and sailfishos on b slot | 22:26 |
| mal | in case the device is stuck in the ramdisk init, then one way would to be write to the /data partition some logs from there | 22:26 |
| mal | and see if you can see the logs | 22:27 |
| mal | did you check that the partition info is correct in the init_boot you extracted? | 22:28 |
| mal | https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L29 | 22:28 |
| mal | that value | 22:28 |
| mal | it's written during build | 22:28 |
| mal | so check the hybris-init_boot.img ramdisk content | 22:29 |
| nightishaman | DATA_PARTITION=/dev/sda31 | 22:29 |
| mal | ok | 22:29 |
| nightishaman | once im back in recovery im gonna check the symlink whether it is correct | 22:30 |
| mal | if you want to try writing to /data do it here https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L302 just write dmesg content to /data/ and copy /init.log content also | 22:31 |
| mal | that would give some information if that works | 22:31 |
| nightishaman | lrwxrwxrwx 1 root root 16 2026-05-16 22:32 userdata -> /dev/block/sda31 | 22:34 |
| nightishaman | ok its correct | 22:34 |
| nightishaman | no output | 22:40 |
| mal | in where? | 22:40 |
| nightishaman | data | 22:40 |
| nightishaman | ill move it out of the if block | 22:41 |
| mal | I wonder if the module loading works | 22:41 |
| mal | what is the final module loading code you used? | 22:42 |
| nightishaman | CFG_FILE="/lib/modules/6.1.145-android14-11-g2ea333278635/modules.load" | 22:42 |
| mal | I mean the rest of it | 22:42 |
| nightishaman | https://pastebin.com/ky4xVEvP | 22:42 |
| mal | ok, should be ok | 22:44 |
| mal | could you check one thing, the kernel file you have in boot image, run "strings kernel | grep 6.1.145" | 22:48 |
| mal | just to see if the version in kernel file matches that of module folder | 22:48 |
| nightishaman | jannikmueller@fedora-2:~/hadk/out_boot$ strings kernel | grep 6.1.145 | 22:52 |
| nightishaman | 6.1.145- | 22:52 |
| nightishaman | *6.1.145-android14-11-g2ea333278635 SMP preempt mod_unload | 22:52 |
| nightishaman | 6.1.145-android14-11-g2ea333278635 (build-user@ | 22:52 |
| nightishaman | 6.1.145-android14-11-g2ea333278635A | 22:52 |
| mal | seems ok then | 22:52 |
| nightishaman | run_debug_session doesn't even seem to get called or the data is not mounted | 22:53 |
| nightishaman | i dient get any output | 22:53 |
| nightishaman | should I put outputs to data somewhere else | 22:56 |
| nightishaman | maybe before usb_setup or before kernel_config? | 22:56 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!