| osum4est | yea keep getting "Skipping build of hybris-updater-script since HYBRIS_BOOT_PART is not specified" do i need to fix this by changing one of the fstabs or is there a different way to fix it? | 00:16 |
|---|---|---|
| r0kk3rz | you need to pick one | 00:50 |
| r0kk3rz | or specify both and flash boot.img to both | 00:50 |
| osum4est | got it. just add one of them to the fstab then? is there an example fstab somewhere that i can look at? i'm not sure what type, mnt_flags, options, and fs_mgr_flags should be | 00:52 |
| r0kk3rz | check out the xa2 adaptation, that does a and b boot stuff | 00:57 |
| T4 | <Hound77> https://pastebin.com/aHw4kMqt … Is there something wrong with this manifest ? | 02:11 |
| r0kk3rz | what makes you think there is? | 02:15 |
| T4 | <birdzhang> you may need vendor source | 02:15 |
| T4 | <Hound77> When I ran repo sync I see an error to fetch device kernel. | 02:16 |
| r0kk3rz | so why didnt you say that :P | 02:16 |
| T4 | <austenite> @Hound77 see device revision | 02:16 |
| T4 | <austenite> its 1ineage | 02:16 |
| T4 | <austenite> XD | 02:17 |
| T4 | <birdzhang> @austenite 👍 | 02:17 |
| T4 | <Hound77> I have mentioned lineage-15.1 | 02:17 |
| r0kk3rz | seems correct - https://github.com/LineageOS/android_kernel_motorola_msm8998/tree/lineage-15.1 | 02:21 |
| r0kk3rz | whats the error? | 02:21 |
| r0kk3rz | generally you want to fork those repos though | 02:21 |
| r0kk3rz | so you should do that, and point to your fork | 02:22 |
| T4 | <Hound77> Do I want to do that and rerun repo sync ? | 02:22 |
| T4 | <Hound77> Do | 02:22 |
| r0kk3rz | go for it | 02:22 |
| T4 | <Hound77> Do I need to add this ? https://github.com/moto-SDM660/proprietary_vendor_motorola_payton | 02:23 |
| r0kk3rz | you will need that yeah | 02:23 |
| r0kk3rz | and possibly others | 02:23 |
| r0kk3rz | like this one https://github.com/LineageOS/android_device_motorola_payton/blob/lineage-15.1/lineage.dependencies | 02:25 |
| T4 | <Hound77> What exactly do I need to add ? | 02:35 |
| T4 | <Hound77> Just the vendor blobs. | 02:36 |
| r0kk3rz | lol. | 02:39 |
| r0kk3rz | they are a set of repos, you need the whole set | 02:40 |
| r0kk3rz | its different for practically every device | 02:40 |
| T4 | <Hound77> I am being a idiot. | 02:40 |
| r0kk3rz | common ones are always device,kernel,vendor | 02:40 |
| r0kk3rz | and then there might be assorted others that are also needed | 02:41 |
| r0kk3rz | you'll soon know if something is missing, because hybris-hal wont build | 02:41 |
| T4 | <Hound77> I'm for https://github.com/mer-hybris/local_manifests/blob/hybris-12.1/onyx.xml to build my manifest. | 02:42 |
| r0kk3rz | ? | 02:42 |
| T4 | <Hound77> refering for onyx | 02:43 |
| T4 | <Hound77> refering from onyx | 02:43 |
| r0kk3rz | why? | 02:44 |
| r0kk3rz | onyx has nothing to do with your device | 02:44 |
| T4 | <Hound77> I'm using it as a example to create local-manifest for my device. | 02:45 |
| r0kk3rz | dont | 02:45 |
| T4 | <Hound77> So what repos do I have to mention on my local-manifest ? | 02:46 |
| r0kk3rz | figure it out :P | 02:47 |
| T4 | <Hound77> I think I have fustrated you with my lame chat. | 02:48 |
| r0kk3rz | slightly, but im not interested in telling you which keys to press, and which buttons to click | 02:50 |
| r0kk3rz | but i will tell you generally what you need to do and look for | 02:51 |
| r0kk3rz | all the things you need are part of the lineage os build process for that device | 02:51 |
| r0kk3rz | all of that is open source | 02:51 |
| r0kk3rz | so start digging | 02:51 |
| osum4est | i finally got my zip file built and flashed, but it is boot-looping. it shows the vendors splash screen for ~30 seconds then reboots. how can i troubleshoot this? i'm not sure where to look for logs | 02:52 |
| r0kk3rz | osum4est: plug in usb, check dmesg in host pc, maybe try getting on to telnet if it shows | 02:52 |
| osum4est | r0kk3rz: no changes in dmesg during the boot loops | 02:55 |
| r0kk3rz | nothing at all about usb devices? must be looping quite early then | 02:57 |
| osum4est | nope. i'm honestly not 100% it installed correctly and copied all the files where they are supposed to go to the correct partitions. i booted into twrp, adb shell, and looked at the system partition. theres stuff in there, but there is nothing in the data partition. are there supposed to be files there? | 02:59 |
| r0kk3rz | yup | 03:05 |
| r0kk3rz | sounds wrong | 03:05 |
| r0kk3rz | data is like, the whole rootfs | 03:06 |
| osum4est | oh. well uh, then thats probably my problem | 03:06 |
| r0kk3rz | its certainly not going to help | 03:07 |
| r0kk3rz | but should should normally see stuff in usb / telnet before then | 03:07 |
| r0kk3rz | you did flash the base image right? | 03:10 |
| r0kk3rz | so you flash lineageos, dont wipe anything, flash sfos.zip | 03:10 |
| osum4est | yep. the a/b slots are also confusing things. gimme a sec, i want to make sure i can flash just lineage and see my data partition | 03:12 |
| r0kk3rz | good idea | 03:12 |
| osum4est | since i have a/b, do i need to install lineage, reboot, then install sfos? or all at once? | 03:13 |
| r0kk3rz | you shouldnt need to reboot, but you can boot lineage first to check | 03:14 |
| r0kk3rz | you should also double check which boot partition is active | 03:16 |
| osum4est | which boot partition is active? and do you know, does the lineage/sfos installer write to the current slot or the other slot? | 03:16 |
| r0kk3rz | not sure, ive not worked with one of these devices | 03:18 |
| r0kk3rz | but since there is two, it must choose one to boot from | 03:19 |
| osum4est | right, right. i need to make sure that both zips install to a and that i'm selected on a, since i setup the boot partition to boot_a | 03:20 |
| r0kk3rz | you can also flash the boot.img manually | 03:25 |
| osum4est | r0kk3rz: thanks! alright, reset everything, installed lineage (data appeared after reboot, and booted into lineage), then installed sfos. checked the data partition, and the stuff from lineage was there but didnt notice anything new (is there an sfos specific file i can look for?). i also flashed the boot img to boot_a manually but i'm still getting the same boot loop and no output in dmesg | 03:37 |
| r0kk3rz | the sfos stuff is in .stowaways under the home folder | 03:45 |
| osum4est | perfect. well i have a /data/.stowaways/sailfishos folder with a bunch of folders, including the nemo home folder, bin with a bunch of programs, etc. so it looks l like that part worked. is there a way to mount my boot partition in twrp to make sure it got installed correctly? | 03:48 |
| r0kk3rz | it flashed ok didnt it? | 03:55 |
| osum4est | it should have. just rewrote the hybris-boot.img to both boot_a and boot_b but still no dice. i also have aboot_a, and aboot_b partitions if i should try using those instead | 03:58 |
| T4 | <birdzhang> do not touch aboot | 03:59 |
| r0kk3rz | try doing a fastboot boot boot.img | 03:59 |
| T4 | <birdzhang> it's bootloader partitions | 03:59 |
| osum4est | oh shoot, thanks for the warning. definitely wont touch those then. and good idea! didnt realize that fastboot boot just boots a regular boot image | 04:00 |
| osum4est | alright tried booting it with fastboot and the exact same thing is happening. must be something wrong with my boot image | 04:04 |
| osum4est | not sure what it could be though since it doesnt connect over usb at all | 04:06 |
| osum4est | is it most likely going to be a bad setting in the kernel config? | 04:10 |
| r0kk3rz | possibly, its not always that easy to tell | 04:16 |
| r0kk3rz | check for a kernel dump log | 04:16 |
| r0kk3rz | i think some newer devices needed some new things to get the usb up and running | 04:17 |
| osum4est | where is that? | 04:17 |
| r0kk3rz | if pstore is enabled in your kernel config, there might be a pstore-ramoops file | 04:20 |
| osum4est | found it, thanks. is there anything specific i should look for? i'm not sure how to differentiate between hybris logs and twrp logs (unless its all hybris) | 04:33 |
| osum4est | https://pastebin.com/iVBuXbM4 | 04:34 |
| T4 | <m_aurel> Our potential ODM offered us an alternative model with a Mediatek chipset MTK MT6761 Quad Core 2.0 GHz. The PCBA board vendor adapted Android Pie. So it's still challenging, because there is no experience with Android Pie for Sailfish OS. Maybe Hardware Adaption is easier for Mediatek than the Octa-Core SC9863 of Spreadtrum? Jolla confirm | 09:02 |
| T4 | ed a high risk an more efford of HA for the last one. | 09:02 |
| r0kk3rz | yeah definitely stay away from that first one | 09:04 |
| r0kk3rz | mediatek based ports have been successful before | 09:05 |
| r0kk3rz | just to put it in perspective, the hisilicon based phones that huawei makes, nobody has successfully made a port for those phones | 09:06 |
| T4 | <m_aurel> Thanks for your recommendation. We won't work with Huawai. | 09:18 |
| T4 | <NotKit> I would prefer MT6761 to SC9863 for sure | 09:19 |
| T4 | <NotKit> both due to performance and MediaTek chips being more explored | 09:20 |
| T4 | <m_aurel> Really? It has only 4 instead of 8 cxores. I was hesitating to choose that option becuase of this fact. | 09:21 |
| r0kk3rz | 8 cores wont do you any good if you cant get it to work | 09:26 |
| T4 | <NotKit> I was wrong actually, SC9863 might be more performant in multicore. See http://browser.geekbench.com/geekbench3/8759694 vs https://browser.geekbench.com/geekbench3/8736836 | 09:26 |
| T4 | <NotKit> but Redmi 6A Antutu score is higher than of Doogee with SC9863A: https://www.kimovil.com/en/xiaomi-redmi-6a/antutu vs https://www.kimovil.com/en/doogee-y7/antutu | 09:29 |
| T4 | <m_aurel> Thanks for the links. HA estimation for Spreadtrum is 25 MM. For any Qualcomm chipset, that is listed at Code Aurora, about 10 MM. What do you think about the effort for Mediatek? Something in between? | 09:31 |
| T4 | <NotKit> Likely. There is Gemini which is Helio X25 and Cosmo will have Helio P70 | 09:33 |
| masha11 | mal: I get the following error in telnet dmesg: "F2FS-fs (sda20): Can't find valid F2FS filesystem in 1th superblock" https://pastebin.com/4G5FTiQt | 10:11 |
| masha11 | And I get the error in /init.log: mount: mounting /dev/sda20 on /data failed: Invalid argument https://pastebin.com/QCDMBLbj | 10:12 |
| masha11 | My fstab.qcom has two lines with /userdata (sda20). It is normal? https://pastebin.com/UeQCRirY | 10:13 |
| masha11 | How can I solve these problems? | 10:14 |
| NeoChapay | masha11: you must format you data to ext2/ext3 | 10:33 |
| masha11 | @NeoChapay I have to do it, being in telnet or twrp? | 10:35 |
| NeoChapay | masha11: all ways is possible :) | 10:35 |
| masha11 | @NeoChapay Why format not in ext4, but ext2/ext3? | 10:36 |
| NeoChapay | masha11: if you can - format to ext4 not in all recovery we have mkfs tools for ext4 | 10:37 |
| masha11 | @NeoChapay From telnet: # mkfs -t ext3 /dev/sda20 Error: /bin/sh: mkfs: not found | 10:42 |
| mal | ext4 is the one to use, nothing else | 10:44 |
| mal | fastboot can be often used to format also | 10:44 |
| masha11 | @mal @NeoChapay thanks | 10:46 |
| T4 | <austenite> @masha11 is your data encrypted | 12:43 |
| masha11 | @austenite I don't now. How to check it? | 12:45 |
| T4 | <austenite> in android, most likely it sia not encrypted by default in lineage.. | 12:47 |
| masha11 | I am confused by the mounting partition /data : /dev/block/dm-0 /data ext4. why dm-0 and not sda20? TWRP Recovery adb shell $mount: https://pastebin.com/xMy32P0n | 12:49 |
| Nokius | new chapter to start soon native port :D | 19:23 |
| osum4est | hello, i still haven't been able to figure out why sfos keeps bootlooping early enough that it doesn't connect over usb. i found the kernel log at /sys/fs/pstore/console-ramoops but im not sure how to differentiate between hybris logs and twrp logs (unless its all hybris) https://pastebin.com/iVBuXbM4 | 19:27 |
| mal | how quickly does it bootloop? | 19:29 |
| osum4est | it shows the vendors splash screen for about 30 seconds, then shows a black screen for about 5-10 then shows the vendor screen again. checking dmesg shows no devices connecting during the reboots. | 19:30 |
| mal | which device and android base? | 19:31 |
| osum4est | marlin, lineage-15.1 base | 19:31 |
| osum4est | sfos 3.0.2.8 | 19:31 |
| osum4est | here's my defconfig if that helps: https://hastebin.com/anofeqiyaz.shell i've disabled selinux, enabled the selinux_bootparam and added selinux=0 to my kernel parameters | 20:06 |
| osum4est | i got rid of all the errors using the tool, and tried to get rid of all the warnings (even after fixing them the tools that they are still the old value?) | 20:07 |
| T4 | <elros34> it's recomended to disable selinux via bootparam (read comment in CONFIG_AUDIT in mer-kernel-checker) | 20:12 |
| vknecht | and if that's not enough, try with disabling Yama | 20:13 |
| osum4est | got it, i had CONFIG_AUDIT as no. should i leave CONFIG_SECURITY_SELINUX as yes then, and just make sure to have those kernel params? | 20:16 |
| T4 | <elros34> yes | 20:17 |
| osum4est | thanks, ill give that a shot | 20:18 |
| mal | osum4est: another hint https://github.com/mer-hybris/android_kernel_sony_msm/blob/hybris-sony-aosp-8.1.0_r52_20190206/arch/arm64/configs/aosp_nile_pioneer_defconfig#L276 | 20:28 |
| mal | if the device has secure boot enabled sfos might need it off | 20:29 |
| mal | like that | 20:29 |
| osum4est | mal: thanks! ill try that as well | 20:32 |
| osum4est | is there a sailfish specific directory in system that i can check for? dealing with the a/b slots is a pain and im still trying to make sure that both lineage and sfos are writing to the correct slot | 20:57 |
| mal | what do you mean sailfish specific directory, all sailfish stuff is in userdata partition in .stowaways/sailfishos folder | 21:00 |
| osum4est | ah, so all sailfish writes is data and the boot image | 21:00 |
| osum4est | so it shouldnt matter what slot im on as long i specified the correct boot slot partition | 21:00 |
| mal | well it matters that you mount correct partitions in sailfish and that kernel goes to correct slow | 21:02 |
| mal | *slot | 21:02 |
| mal | also some a/b devices need a service to tell the system that boot was successful | 21:03 |
| osum4est | ma: alright, added the verity config settings (and fixed the selinux ones, added selinux=0 and audit=0 to my kernel params) but still no dice. running make hybris-boot and then fastbooting to it should be enough to test changes right? i shouldn't have to reinstall the data partition? | 21:13 |
| mal | did you use fastboot boot or flash it? | 21:14 |
| osum4est | fastboot boot | 21:14 |
| mal | some device are picky about fastboot boot and require signed boot images | 21:14 |
| osum4est | weird, in that case, adb pushing it, then manually writing to the boot partition should work | 21:15 |
| osum4est | ? | 21:15 |
| mal | or just fastboot flash boot hybris-boot.img | 21:16 |
| mal | and then fastboot reboot | 21:16 |
| osum4est | ... oh thats much easier. the guide used dd, didnt realize you could flash like that | 21:17 |
| piggz | evening | 21:20 |
| osum4est | well still same thing happens :/ would the log at /sys/fs/pstore/console-ramoops be able to tell me whats wrong? i have pstore logging enabled in my config | 21:20 |
| T4 | <elros34> you could dump logs to sdcard or just write something to kmsg (echo " " > /dev/kmsg) somewhere here: https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L345 to make sure it even reach that state | 21:54 |
| mal | assuming it even reaches that far | 21:54 |
| mal | it could even fail to run the init | 21:55 |
| mal | PSA: hybris-15.1 is now rebased, I didn't have time to test it properly but it builds at least | 22:00 |
| osum4est | thanks for the idea, ill try that in a bit. and nice! although i might have done something wrong since i was able to build everything on 15.1... not sure what was broken before | 22:02 |
| mal | some people had issues building it, not sure if it was device specific | 22:02 |
| osum4est | elros32: mal: tried echoing there, but didnt find my message in kmsg. is there a way to view kmsg from fastboot? i've boot booting into twrp, adb shell in, and view it from there. at the beginning of the script i see that it logs some info to init.log. where would that be stored? the boot partition? | 22:31 |
| T4 | <elros34> if you write something to /dev/kmsg you should see msg in console-ramoops provided kernel crash/reboots straight to twrp. You can't view kernel logs in fastboot you need serial port (uart) but that is usualy unavailable. | 22:41 |
| T4 | <elros34> of course you can manually try to save init.log from the first stage (initramfs) to sdcard | 22:45 |
| osum4est | it does not reboot straight to twrp, i've gotta hold down power+voldown to get to bootloader again. save the init.log from inside the init-script? | 22:48 |
| T4 | <elros34> if you turn off device it doesn't make sense to read console-ramops because kernel log from last boot is saved in RAM. Like I said earlier first just make sure script is even run | 22:51 |
| osum4est | elros34: sorry for all the dumb questions... but how do i actually dump those logs to /sdcard? i tried changing the init.log to be on the sd card, (exec > /sdcard/init.log 2>&1) but i doubt the init script even has that mounted. | 23:28 |
| r0kk3rz | youd need to tell it to mount it | 23:30 |
| T4 | <elros34> yes something like that should be enough (line 345): mkdir /sd; mount /dev/mmcblk0p1 /sd; touch /sd/iamalive | 23:32 |
| T4 | <elros34> or mmcblk1p1 it depends on the device | 23:36 |
| osum4est | can i just mount my data partition and write there instead? i don't have that partiton/an sd card (physically, at least) | 23:37 |
| r0kk3rz | you can do whatever you like in the script | 23:38 |
| r0kk3rz | one of my favourite tricks is turning on the notification led at certain stages | 23:39 |
| osum4est | oo that'd be pretty nice! should probably just write a file first :P but then i might find the right file for doing that | 23:39 |
| r0kk3rz | these were the paths for my sony https://github.com/r0kk3rz/hybris-boot/blob/sony-recovery/init-script#L32-L34 | 23:40 |
| r0kk3rz | i was trying to get the sony fotakernel recovery working | 23:42 |
| osum4est | ok well it looks like boot script isn't being run, mounted my data directory and created a file there, and confirmed it didnt exist... | 23:45 |
| r0kk3rz | or it cant mount the data partition | 23:48 |
| r0kk3rz | which is a common enough issue in early stage boot failures | 23:49 |
| osum4est | oh, is there somewhere more reliable? i dont see any sdcard partitions | 23:51 |
| r0kk3rz | it still bootloops? | 23:57 |
| osum4est | yes | 23:58 |
| r0kk3rz | time it, and then slam in like a sleep 120 in the script at the start | 23:58 |
| osum4est | man that is a much better idea that trying to mount stuff lol | 23:59 |
| r0kk3rz | getting the actual log would be quite useful | 23:59 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!