piggz | in ofono.service, user is set to root, but its actually running as radio, how does that happen? | 09:50 |
---|---|---|
piggz | spiiroin: afternoon :) | 13:56 |
Mister_Magister | poor piggz getting ignored | 13:56 |
piggz | can anyone think why I might be hitting this https://github.com/sailfish-on-dontbeevil/ofono-new/blob/branch-1.34-qmi/ofono/src/slot-manager-dbus.c#L421 | 13:56 |
T42 | <foxclore> @elros34 regarding that usb issue: any ideas why init-script doesn't create any /init.log file? | 17:21 |
SebastianoGaleazzo[m] | So I've successfully built (finally) SailfishOS installable zip... Problem is that I can't flash because of the following error: | 17:25 |
SebastianoGaleazzo[m] | https://pastebin.com/K6K4MP3R | 17:25 |
SebastianoGaleazzo[m] | Of course I've done something wrong but I don't know what. Is it related to SELinux contexts missing? | 17:25 |
T42 | <elros34> @foxclore because you are still in initramfs, not in sailfish. Same script is in sfos rootfs and it's executed after initramfs pass | 19:37 |
T42 | <elros34> so switching to configfs in init-scipt doesn't help? | 19:37 |
T42 | <elros34> SebastianoGaleazzo[m] I do not know how to solve this but as workaround you can flash hybris-boot, telnet and then unpack sfos rootfs manually to /data/.stowaways/sailfishos/ | 19:52 |
SebastianoGaleazzo[m] | <T42> "<elros34> Sebastiano Galeazzo..." <- Ok I've tried flashing hybris-recovery.img using "fastboot flash boot path/to/hybris-recovery.img" (since my device doesn't use separate recovery) but command fails with: | 20:08 |
SebastianoGaleazzo[m] | https://pastebin.com/zj7sy4b8 | 20:08 |
SebastianoGaleazzo[m] | That's strange | 20:08 |
T42 | <elros34> I always wonder why people hide commands they execute. BTW flashing recovery is really pointless for you | 20:10 |
T42 | <elros34> check what active slot you have now | 20:11 |
SebastianoGaleazzo[m] | Currently I'm on slot b... | 20:46 |
SebastianoGaleazzo[m] | <T42> "<elros34> I always wonder why..." <- Anyway I've not pasted the command I've executed because I've written it in the above message if it's that what you meant | 20:49 |
T42 | <Ayman_rgab> @elros34 hi, do you have any idea why changing usb mode requires restarting usb-moded service ? | 20:50 |
T42 | <elros34> can you flash lineage boot? | 20:52 |
T42 | <elros34> SebastianoGaleazzo[m]^ | 20:52 |
SebastianoGaleazzo[m] | Yes just tried... Btw I've noticed that hybris-boot.img and boot.img inside out folder differ in sizes: first is around 64mb second one is just 24mb | 20:54 |
SebastianoGaleazzo[m] | s/64mb/24mb/, s/24mb/64mb/ | 20:55 |
T42 | <elros34> they are not same thing, IIRC boot.img contains android initramfs | 20:56 |
SebastianoGaleazzo[m] | Hmm ok just thinking fastboot was refusing it because of something was missing inside | 20:57 |
T42 | <edp_17> I have the same issue too on some of my ports. (re @Ayman_rgab: @elros34 hi, do you ...) | 21:00 |
T42 | <elros34> the only way to figure out this is to debug udev events and usb-moded | 21:06 |
SebastianoGaleazzo[m] | Really don't know how to solve this... I'm searching around... | 21:12 |
T42 | <elros34> so you have this error only when you flash hybris-boot.img but not when flashing boot.img from out/ or lineage boot.img? | 21:14 |
mal | to bt sure the kernel contains reasonably sized initramfs you can compare hybris-boot and kernel in out/ | 21:14 |
SebastianoGaleazzo[m] | Yes... Los and boot.img from out work | 21:15 |
mal | if the sizes are very close then it might be there is some issue | 21:15 |
T42 | <elros34> then use abootimg to check hybris-boot.img and compare with boot.img | 21:15 |
mal | SebastianoGaleazzo[m]: which android base are you using? | 21:16 |
SebastianoGaleazzo[m] | Android base is LineageOS 18.1, Stock is Motorola firmware based on Android 11 | 21:17 |
mal | did you apply patches as mentioned in faq? | 21:17 |
T42 | <elros34> and you did install cpio in habuild? | 21:17 |
SebastianoGaleazzo[m] | mal: I applied patches with "hybris-patches/apply-patches.sh --mb" | 21:19 |
mal | good | 21:19 |
SebastianoGaleazzo[m] | T42: you mean having cpio installed in PlatformSDK? | 21:19 |
T42 | <elros34> no in HABUILD | 21:20 |
T42 | <elros34> like explained in hadk-hot | 21:20 |
T42 | <elros34> little trap for new porters to not make porting too easy | 21:21 |
SebastianoGaleazzo[m] | So I'm dumb... I think you have found what is going wrong here... Sorry didn't see that point in hadk-hot | 21:21 |
T42 | <elros34> should be in hadk but.. | 21:22 |
SebastianoGaleazzo[m] | Ok now I install it and I make hybris-hal and droidmedia | 21:23 |
SebastianoGaleazzo[m] | Do I have to rebuild packages too or is it enough making hybris-hal and droidmedia and then creating zip file with --mic? | 21:26 |
T42 | <elros34> it's enough to make hybris-hal and flash hybris-boot | 21:27 |
SebastianoGaleazzo[m] | Unfortunately same error while flashing through fastboot | 21:30 |
mal | did the size of hybris-boot change? | 21:31 |
T42 | <elros34> then compare working with not working image: abootimg or bnetter unpack_bootimg.py | 21:31 |
SebastianoGaleazzo[m] | mal: yes a few | 21:32 |
mal | SebastianoGaleazzo[m]: what exact error message you get when flashing hybris-boot? | 21:32 |
SebastianoGaleazzo[m] | T42: i was just doing it... i'm pasting results to pastebin... | 21:32 |
mal | SebastianoGaleazzo[m]: just a hint, T42 is a bot, you should mention the nick after it, like this @elros34 | 21:33 |
SebastianoGaleazzo[m] | mal: same as before: | 21:34 |
SebastianoGaleazzo[m] | https://pastebin.com/21SDch9r | 21:34 |
SebastianoGaleazzo[m] | mal: lol haha | 21:34 |
mal | SebastianoGaleazzo[m]: can you post output of "fastboot getvar all" you can remove any serial numbers etc from the output | 21:35 |
mal | which device is that btw? | 21:36 |
SebastianoGaleazzo[m] | so @elros34 below there is the output of abooimg: | 21:36 |
SebastianoGaleazzo[m] | https://pastebin.com/2r71nmVJ | 21:36 |
SebastianoGaleazzo[m] | mal: output of fastboot getvar all: | 21:39 |
SebastianoGaleazzo[m] | https://pastebin.com/ZHwQ5F0E | 21:39 |
SebastianoGaleazzo[m] | It is Motorola One Vision (exynos9609 in practice identical to exynos9610) | 21:39 |
T42 | <elros34> rounded image to 64MB? | 21:39 |
T42 | <elros34> try unpack_bootimg.py, it contains more details | 21:39 |
mal | SebastianoGaleazzo[m]: can you try another usb port on your computer just in case | 21:40 |
mal | I see some mentions on various forums that sometime the error you get can happen if the usb port is somehow incompatible | 21:40 |
mal | I remember some issues with usb3 ports, it might also depend on fastboot version etc | 21:41 |
SebastianoGaleazzo[m] | @elros34 output of unpack_bootimg.py: | 21:44 |
SebastianoGaleazzo[m] | https://pastebin.com/BvTtfCrd | 21:44 |
SebastianoGaleazzo[m] | @mal I've tried but got same error | 21:45 |
mal | do you have another usb cable to test? | 21:46 |
SebastianoGaleazzo[m] | can be this related to "second bootloader" missing in hybris-boot.img? | 21:46 |
SebastianoGaleazzo[m] | mal: yes i try | 21:47 |
mal | hybris-boot.img contains quite simple initramfs | 21:47 |
T42 | <elros34> see if you are missing any of this offsets when hybris-boot.img is created: https://github.com/LineageOS/android_device_motorola_exynos9610-common/blob/lineage-18.1/BoardConfigCommon.mk#L69 | 21:48 |
SebastianoGaleazzo[m] | mal: ok just tried but fastboot still refusing it | 21:49 |
T42 | <elros34> do you have some second stage file extracted form unpack_bootimg.py? | 21:49 |
mal | @elros34 but fastboot should not fail in such cases, usually it doesn't check for validity of the kernel afaik | 21:50 |
T42 | <elros34> probably but then why boot.img can be flashed without issues? | 21:52 |
SebastianoGaleazzo[m] | @elros34 so yes extracting lineage boot.img I got "kernel", "ramdisk" and "second" (could it be second bootloader related?), while extracting hybris-boot.img gives only "kernel" and "ramdisk" | 21:54 |
mal | @elros34 good point | 21:55 |
T42 | <elros34> try recreating lineage and then hybris to see if you can reproduce/fix issue | 21:55 |
T42 | <elros34> I wonder what is in "second" | 21:56 |
mal | one option to try is to recreate the hybris-boot by extracting both boot and hybris-boot and then using the command of boot.img to assemble a hybris-boot.img with the second thing | 21:57 |
SebastianoGaleazzo[m] | i was just asking this haha... ok so I try repackinig hybris-boot.img adding "second" file? | 21:58 |
SebastianoGaleazzo[m] | * "second" file taken from los boot? | 21:58 |
mal | those commands to extract kernel usually give a command to reassemble it | 21:59 |
T42 | <elros34> could be also that second is not even needed but --second_offset is | 22:01 |
SebastianoGaleazzo[m] | ok so i think "second" refer to "second bootloader" since in out folder there is a file called "2ndbootloader" which has same size of the one inside los boot.img... 2ndbootloader is built since inside BoardConfig.mk there is this line: | 22:04 |
SebastianoGaleazzo[m] | https://github.com/LineageOS/android_device_motorola_exynos9610-common/blob/ba6e28ee7abd16d8485dc6a750be606eea0e922a/BoardConfigCommon.mk#L72 | 22:04 |
SebastianoGaleazzo[m] | @elros34 @mal details of I've done: | 22:21 |
SebastianoGaleazzo[m] | https://pastebin.com/KmZKejEK | 22:21 |
SebastianoGaleazzo[m] | Nothing changes same error is thrown | 22:24 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!