| T42 | <btchdRPR> @elros34 Thanks - I missed that :P | 17:12 |
|---|---|---|
| T42 | <btchdRPR> | 17:12 |
| T42 | <btchdRPR> I get to a Sailfish OS logo!!! | 17:12 |
| T42 | <btchdRPR> | 17:12 |
| T42 | <btchdRPR> The device however restarts after ~15-20s, and I can't get on telnet. | 17:12 |
| mal | might be that droid-hal-init is failing and causing a reboot | 17:15 |
| T42 | <btchdRPR> persistant journal time? | 17:15 |
| mal | first thing to try is to mask droid-hal-init, if you can do that in recovery | 17:17 |
| T42 | <btchdRPR> sure | 17:17 |
| mal | if you keep having issues with telnet then maybe also mask usb-moded | 17:17 |
| mal | I mean after masking droid-hal-init first | 17:18 |
| T42 | <elros34> create /init_enter_debug2 so you can stop using recovery and read journal directly | 17:19 |
| T42 | <btchdRPR> I still get a reboot after masking droid-hal-init | 17:20 |
| T42 | <btchdRPR> @elros34: with init_enter_debug2 I get no SFOS logo, and a device, but nada on telnet | 17:21 |
| T42 | <elros34> are you sure? ifconfig -a doesn't show new device? | 17:22 |
| T42 | <btchdRPR> I get a device, but no IP assigned | 17:22 |
| T42 | <elros34> assign it | 17:22 |
| T42 | <btchdRPR> ah yeah got back in. weird. | 17:24 |
| T42 | <btchdRPR> dhcp USED to work :P | 17:24 |
| T42 | <btchdRPR> what to do now? can gt a telnet in the new root | 17:25 |
| T42 | <btchdRPR> ahh got it in hadk_hot | 17:26 |
| mal | I have also had that issue with non-working dhcp on some devices, not sure what causes it | 17:30 |
| T42 | <elros34> it's common, would be great if that can be fixed | 17:32 |
| mal | yeah | 17:32 |
| mal | hopefully I can find some time to debug it | 17:33 |
| T42 | <btchdRPR> i'm unsure what to do from now, i cannot seemingly logcat, i can continue but even with droid-hal-init masked i get a reboot after ~15s | 17:33 |
| mal | logcat is only possible if droid-hal-init is working | 17:33 |
| T42 | <btchdRPR> yes, I have unmasked it for now | 17:33 |
| mal | do you have persistent journal? | 17:34 |
| mal | check what you see in journal | 17:34 |
| T42 | <elros34> if not then even /sys/fs/pstore/console-ramops | 17:34 |
| T42 | <elros34> oo* | 17:35 |
| T42 | <btchdRPR> it's a samsung device, so last_kmsg, and that unfortunately doesn't reveal anything | 17:35 |
| T42 | <elros34> dmesg -w? something must be in logs. | 17:36 |
| T42 | <btchdRPR> droid-load-firmware is failing | 17:36 |
| T42 | <btchdRPR> ``` | 17:37 |
| T42 | <btchdRPR> Feb 18 17:36:46 localhost firmware[2097]: Failed to find firmware abox_tplg.bin for /devices/platform/18c50000.abox/0.abox-tplg/firmware/abox_tplg.bin | 17:37 |
| T42 | <btchdRPR> Feb 18 17:36:46 localhost kernel: firmware abox_tplg.bin: firmware_loading_store: unexpected value (0) | 17:37 |
| T42 | <btchdRPR> Feb 18 17:36:46 localhost systemd-udevd[2094]: Process '/usr/bin/droid/droid-load-firmware.sh' failed with exit code 1.``` | 17:37 |
| T42 | <btchdRPR> hmm. i wonder if some mounts are failig | 17:37 |
| T42 | <btchdRPR> hmm. i wonder if some mounts are failing (edited) | 17:37 |
| T42 | <elros34> show full logs | 17:38 |
| T42 | <btchdRPR> oh god, there's a lot of failing symlinks lol | 17:39 |
| T42 | <btchdRPR> https://katb.in/veqazohatix | 17:40 |
| T42 | <btchdRPR> and it's in vendor... | 17:41 |
| T42 | <btchdRPR> | 17:41 |
| T42 | <btchdRPR> ``` | 17:41 |
| T42 | <btchdRPR> 130|z3s:/ # find / | grep abox_tplg.bin | 17:41 |
| T42 | <btchdRPR> /vendor/firmware/abox_tplg.bin``` | 17:41 |
| T42 | <btchdRPR> i wonder how it's even reaching splash, lol | 17:41 |
| T42 | <elros34> is that dmesg or what? | 17:43 |
| T42 | <btchdRPR> it's journal | 17:43 |
| T42 | <elros34> Please follow instruction and include full command you use https://sailfishos.wiki/books/hadk/page/hadk-hot#bkmrk-2022.07.31%3A-generati. Did you enable watchdog_nowayout in kernel config? | 17:48 |
| T42 | <btchdRPR> yes, I did. | 17:49 |
| T42 | <btchdRPR> | 17:49 |
| T42 | <btchdRPR> for the journal, I continued boot and simply ran journalctl. I'll get persistent just in case if something happened after usb died | 17:49 |
| T42 | <btchdRPR> 🤦♂️ | 17:51 |
| T42 | <btchdRPR> | 17:51 |
| T42 | <btchdRPR> it failed to mount odm at the end, and that's why it rebooted | 17:51 |
| T42 | <elros34> I thought you have it already enabled like mal said if not then do it and revert this nowayout change | 17:51 |
| T42 | <btchdRPR> let me grab you the full logs | 17:51 |
| T42 | <btchdRPR> https://katb.in/ziruwiziwan | 17:51 |
| T42 | <btchdRPR> reverting nowayout now | 17:52 |
| T42 | <elros34> dont you have anything more than that in dmesg -w? | 17:57 |
| T42 | <btchdRPR> i don't think so. let me check it out. got nowayout reverted. | 17:58 |
| T42 | <btchdRPR> https://katb.in/okewiwumexa -> dmesg -w | 18:00 |
| T42 | <btchdRPR> i cut the devicetree probe stuff and early boot out | 18:00 |
| T42 | <btchdRPR> seems like it's still failing on firmware | 18:00 |
| T42 | <elros34> not sure about that but you can mask user@100000. dmesg vs journal is slightly different there is 20s more. what about journal -f. Do you even have /sys/fs/pstore? | 18:12 |
| T42 | <elros34> most importatn do you have this reboot even if you are not continue booting? | 18:13 |
| T42 | <btchdRPR> elros: I don't have pstore. The system doesn't reboot if i don't continue | 18:14 |
| T42 | <elros34> can you show your kenrel sources? | 18:17 |
| T42 | <elros34> this logs seems to be a little bit inconsistence to me: in first one you have droid-load-firmware but not in later | 18:26 |
| T42 | <btchdRPR> elros: all I did was restart the device a few times :P | 20:53 |
| T42 | <elros34> no, you use different command. That is why I asked for journal -f | 20:57 |
| T42 | <elros34> also masking firmware load service could be good idea | 20:58 |
| T42 | <elros34> and make sure you really masked droid-hal-init | 21:06 |
| T42 | <Umeaman> Just out of curiosity, is the HADK PDF file updated with the latest hybris branches available? | 22:36 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!