| T42 | <hacker12455> yes touched the file | 00:00 |
|---|---|---|
| T42 | <hacker12455> eh let me quickly check that before restoring | 00:01 |
| T42 | <hacker12455> yep works | 00:04 |
| T42 | <hacker12455> what would be the best way to run these commands? | 00:05 |
| T42 | <hacker12455> systemd service? | 00:05 |
| T42 | <elros34> yeah similar to one you linked | 00:08 |
| T42 | <rodrisola> Hello | 18:04 |
| T42 | <rodrisola> I have a error on resolv_gold_test | 18:05 |
| T42 | <rodrisola> https://www.toptal.com/developers/hastebin/izocihuyam.less | 18:05 |
| T42 | <rodrisola> I remove? | 18:05 |
| mal | which android base? | 19:22 |
| T42 | <rodrisola> android 11, | 19:41 |
| mal | if I looked at the code correctly that should be in packages/modules/DnsResolver/tests/Android.bp which should be in manifest | 19:48 |
| T42 | <rodrisola> failed | 19:53 |
| T42 | <rodrisola> FAILED: ninja: 'minimediaservice', needed by 'droidmedia', missing and no known rule to make it | 19:53 |
| mal | have you cloned droidmedia repo as mentioned in faq | 19:54 |
| mal | wait, droidmedia is by default in manifest, how can you get that error if you used correct manifest | 19:55 |
| T42 | <rodrisola> mmm but clone hybris-18.1 | 19:59 |
| T42 | <rodrisola> would it have something to do with the problem? | 19:59 |
| mal | check if you have external/droidmedia folder | 20:10 |
| T42 | <rodrisola> droidmedia is found | 20:55 |
| T42 | <rodrisola> this is a log | 20:56 |
| T42 | <rodrisola> ls in droidmedia folder | 20:57 |
| T42 | <rodrisola> https://www.toptal.com/developers/hastebin/zunotazigu.rb | 20:57 |
| mal | and you still get same error? | 21:14 |
| mal | did you apply patches as mentioned in faq? | 21:18 |
| T42 | <rodrisola> but only on 17.1 | 21:33 |
| T42 | <rodrisola> https://github.com/mer-hybris/hadk-faq#hybris-17-1 | 21:33 |
| T42 | <rodrisola> I didn't apply them because I can't find hybris-18.1, or what patches are they, could you give me the link? | 21:34 |
| T42 | <elros34> what excatly you can't find? patches should be in same place and they are applied same way | 21:51 |
| T42 | <elros34> in hybris-16 section you have instrction how to apply them | 21:52 |
| T42 | <hacker12455> so here's a weird issue | 21:59 |
| T42 | <hacker12455> I gave the rootfs I have to someone to test | 21:59 |
| T42 | <hacker12455> but they get into the same failed to boot init in real rootfs issue as I had | 21:59 |
| T42 | <hacker12455> the mountpoints are fixed | 22:00 |
| T42 | <hacker12455> they use the same hybris-boot.img that I tested boots | 22:00 |
| T42 | <hacker12455> no device in ip a | 22:00 |
| T42 | <b100dian> wait, you’re porting to a device > 1 people have? :p | 22:02 |
| T42 | <hacker12455> lol | 22:02 |
| T42 | <elros34> are they? unpack initramfs and check whether DATA_PARTITION variable is correct | 22:03 |
| T42 | <hacker12455> told them to modify them manually | 22:03 |
| T42 | <hacker12455> both system_root and vendor | 22:03 |
| T42 | <hacker12455> and I checked that they point to correct partitions | 22:03 |
| T42 | <elros34> system is irrelevant if you are in initramfs, Why cant you just make your fixup-mountpoints correct, it's really easy | 22:05 |
| T42 | <elros34> show you fstab and fixup-mountpoints | 22:05 |
| T42 | <hacker12455> checked it (re @elros34: are they? unpack ini...) | 22:07 |
| T42 | <hacker12455> DATA_PARTITION=/dev/mmcblk0p54 | 22:07 |
| T42 | <hacker12455> which is correct | 22:08 |
| T42 | <elros34> so what was thet reason for switch root failure? diagnosis.log? | 22:08 |
| T42 | <hacker12455> https://irc.thaodan.de/.imgstore/affad354/fstab.qcom | 22:09 |
| T42 | <hacker12455> https://irc.thaodan.de/.imgstore/9d072d31/fixup_mountpoints | 22:09 |
| T42 | <hacker12455> where should it be? (re @elros34: so what was thet rea...) | 22:09 |
| T42 | <elros34> in / in intramfs | 22:09 |
| T42 | <hacker12455> can't see it anywhere | 22:11 |
| T42 | <elros34> so init.log should have something | 22:12 |
| T42 | <hacker12455> it's not there either | 22:13 |
| T42 | <hacker12455> checked both in / and in /data/.stowaways/sailfishos | 22:13 |
| T42 | <elros34> you are mixing things: "failed to boot init in real rootfs" means you are in initramfs and you can only find these logs in initramfs, they are not in sailfish root | 22:15 |
| T42 | <hacker12455> it doesn't expose a network device | 22:16 |
| T42 | <hacker12455> so no telnet | 22:16 |
| T42 | <rodrisola> @elros34 i apply patch from hybris-17.1 | 22:16 |
| T42 | <hacker12455> even with init_enter_debug2 | 22:16 |
| T42 | <elros34> @rodrisola why? didn't you use hybris-18 branch? | 22:17 |
| T42 | <rodrisola> but i have this error /bin/bash: external/audioflingerglue/detect_build_targets.sh: No such file or directory | 22:17 |
| T42 | <rodrisola> @elros34 My device came out with original android 11, there is no android 10 for the phone | 22:18 |
| T42 | <elros34> init_enter_debug2 is useless because you did not switch to sfos rootfs, you are still in initramfs. init_enter_debug could be useful but only if data is really mounted | 22:18 |
| T42 | <hacker12455> should I try init_enter_Debug? | 22:18 |
| T42 | <hacker12455> should I try init_enter_debug? (edited) | 22:18 |
| T42 | <elros34> or hybris-recovery | 22:18 |
| T42 | <elros34> @rodrisola so use correct patches for hybris-18, not 17 | 22:19 |
| T42 | <hacker12455> gonna try hybris-recovery | 22:20 |
| T42 | <rodrisola> in the selection of faq, there is no hybris18 section, or if you could give me a link | 22:21 |
| T42 | <elros34> there is such a section because hybris-18 is work in progress but steps are similar to hybris-17 and 16 | 22:22 |
| T42 | <elros34> there is no* | 22:22 |
| T42 | <hacker12455> still nothing (re @elros34: or hybris-recovery) | 22:23 |
| T42 | <hacker12455> would try again on my device but that would need to be tomorrow | 22:23 |
| T42 | <elros34> I am confused. How can you not have any network device if you "Failed to boot init in real rootfs" in dmesg. You can lose it but for sure it is available at least for a second | 22:27 |
| T42 | <hacker12455> it doesn't even mention it in dmesg | 22:27 |
| T42 | <hacker12455> normally it would mention it in dmesg that it binds a device | 22:28 |
| T42 | <hacker12455> unless there is something broken with his device/computer | 22:28 |
| T42 | <elros34> so I have no idea what you were talking about here: https://irclogs.sailfishos.org/logs/%23sailfishos-porters/%23sailfishos-porters.2021-11-15.log.html#t2021-11-15T21:59:57 | 22:28 |
| T42 | <hacker12455> that's the same device | 22:29 |
| T42 | <hacker12455> and hybris-boot doesn't mention anything about a network device in dmesg in that case either | 22:30 |
| T42 | <hacker12455> on my device it worked | 22:30 |
| T42 | <hacker12455> not sure if it was because of any changes or what | 22:30 |
| T42 | <hacker12455> see here from his dmesg | 22:32 |
| T42 | <hacker12455> https://bpa.st/SSIA | 22:32 |
| T42 | <rodrisola> i apply cd $ANDROID_ROOT/external | 22:33 |
| T42 | <rodrisola> git clone --recurse-submodules https://github.com/mer-hybris/libhybris.git | 22:33 |
| T42 | <rodrisola> cd $ANDROID_ROOT | 22:33 |
| T42 | <rodrisola> hybris-patches/apply-patches.sh --mb | 22:33 |
| T42 | <elros34> @hacker12455 so nice error from hybris-boot, at the same time ifconfig should show usb0 or something else | 22:35 |
| T42 | <hacker12455> it should | 22:36 |
| T42 | <hacker12455> but ip a shows nothing | 22:36 |
| T42 | <hacker12455> eh I'll end it for now | 22:38 |
| T42 | <hacker12455> will check on my device tomorrow and update | 22:39 |
| T42 | <hacker12455> just to rule out any device issues | 22:39 |
| T42 | <hacker12455> shoukd probably fix fixup-mountpoints too... | 22:40 |
| T42 | <elros34> no idea how usb- can be missing but error is most likely result of either wrong partition block or filesystem (ext4 vs f2fs) or missing /data/.stowaways/sailfishos/init-debug | 22:41 |
| T42 | <hacker12455> init-debug was there | 22:41 |
| T42 | <hacker12455> /data is formatted to ext4 | 22:42 |
| T42 | <hacker12455> anyway will try to replicate on my phone again | 22:42 |
| T42 | <elros34> and formated just before sfos flash/ not encryped? | 22:43 |
| T42 | <hacker12455> yes | 22:43 |
| T42 | <rodrisola> any help, | 23:10 |
| T42 | <rodrisola> this error is normal? | 23:10 |
| T42 | <rodrisola> https://www.toptal.com/developers/hastebin/ofawifeyat.rb | 23:10 |
| T42 | <elros34> so how top of the libc/include/sys/_system_properties.h looks like, do you try to apply patches second time? | 23:16 |
| T42 | <rodrisola> the file exist | 23:22 |
| T42 | <rodrisola> https://www.toptal.com/developers/hastebin/teqiwaqoge.rb | 23:22 |
| T42 | <rodrisola> in second time i remove bionic/.git/revase_directory | 23:23 |
| T42 | <rodrisola> but same error | 23:23 |
| T42 | <elros34> the point is what it contains, you can't apply same patches twice | 23:24 |
| T42 | <rodrisola> ok. then they are already applied, excuse me | 23:25 |
| T42 | <elros34> did you apply them before first make hybris-hal? | 23:27 |
| mal | just mentioning, in case of such failure I suggest going to the folder where the error happened and running "git am --abort" in this case bionic folder | 23:32 |
| mal | also in case there is at any time need to remove the patches and apply changed patches you can remove the patches using "repo sync -l", just make sure you don't have any local changes to repos like kernel or device repos as those could get lost when doing repo sync | 23:33 |
| mal | so always good to keep backup of any hybris changes to device specific repos | 23:40 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!