| T42_ | <vilez0> hi | 09:40 |
|---|---|---|
| T42_ | <vilez0> hi | 11:12 |
| T42_ | <vilez0> i placed the rootfs and did some troubleshooting | 11:12 |
| T42_ | <vilez0> now i can access telnet via port 2323 | 11:12 |
| T42_ | <vilez0> but stil there is no ui/it does not even pass mi logo from the bootloader | 11:12 |
| mal | you need to provide logs, at least "journalctl -b --no-pager" | 11:14 |
| T42_ | <vilez0> (i will send the logs, just 1 min= | 11:14 |
| T42_ | <vilez0> init.log: https://paste.medip.dev/p/nhDJCG | 11:19 |
| T42_ | <vilez0> initramfs.log: https://paste.medip.dev/p/iqOnY2 | 11:19 |
| T42_ | <vilez0> journalctl -b --no-pager: https://paste.medip.dev/p/31drIO | 11:20 |
| mal | hmm, journal log is not complete, maybe try enabling persisten journal log as mentioned in faq, and get the log relatively soon after boot so it is likely to contain all logs | 11:28 |
| mal | init.log is not useful anymore when in port 2323 | 11:28 |
| mal | also you could check output of "systemctl" to see which services fail | 11:29 |
| T42_ | <vilez0> @mal journal: https://paste.medip.dev/p/PzxwF2.log | 11:35 |
| T42_ | <vilez0> systemctl --failed: https://paste.medip.dev/p/kwEr39 | 11:36 |
| T42_ | <vilez0> could be because mount errors? | 11:58 |
| mal | yes | 12:46 |
| mal | check why those mounts fail | 12:47 |
| mal | maybe fixup-mountpoints was not correct or something else is wrong | 12:47 |
| T42_ | <elros34> don't forget to revert all unneeded changes you did to init-script during debugging | 12:51 |
| T42_ | <vilez0> 👍 | 12:54 |
| T42_ | <vilez0> looks like that is my vendor (and other parts) are dm devices (/dev/block/dm-0, dm-1 etc.) and not shown in sfos | 16:06 |
| T42_ | <vilez0> so, how can i/how should i mount them under sailfishos? | 16:06 |
| T42_ | <elros34> super partition? Are you sure? how your android's fstab looks like? | 16:09 |
| T42_ | <vilez0> https://paste.medip.dev/p/8gaVPL | 16:11 |
| T42_ | <vilez0> this is from recovery | 16:11 |
| T42_ | <elros34> what about device repo | 16:12 |
| T42_ | <elros34> instruction for dynamic partitions is in hadk-hot | 16:12 |
| T42_ | <vilez0> https://github.com/Pulkit077/device_xiaomi_sweet_k6a/blob/lineage-21/rootdir/etc/fstab.qcom (re @elros34: what about device re...) | 16:13 |
| T42_ | <vilez0> okay, i will look to hadk-hot | 16:13 |
| T42_ | <vilez0> how should i include the files from sparse/? | 18:14 |
| T42_ | <vilez0> looks like building the packages again didnt include them | 18:16 |
| T42_ | <vilez0> ok, i was flashing the old rootfs by mistake | 18:27 |
| T42_ | <vilez0> https://paste.medip.dev/p/u7usDj | 18:32 |
| T42_ | <vilez0> Jul 10 20:32:19 RedmiNote12Pro4G sh[3442]: /bin/sh: can't open '/usr/bin/droid/droid-hal-early-init.sh': No such file or directory | 18:33 |
| T42_ | <vilez0> Jul 10 20:32:19 RedmiNote12Pro4G sh[3443]: nohup: can't execute '/sbin/droid-hal-init': Too many levels of symbolic links | 18:33 |
| T42_ | <vilez0> | 18:33 |
| T42_ | <vilez0> These are the ones that caught my eye | 18:33 |
| T42_ | <vilez0> `# ls /usr/bin/droid/ | 18:35 |
| T42_ | <vilez0> dmsetup.sh droid-hal-startup.sh droid-load-firmware.sh get_partition.sh | 18:35 |
| T42_ | <vilez0> droid-hal-shutdown.sh droid-init-done.sh droid-reclaim-memory.sh` | 18:35 |
| T42_ | <vilez0> btw, 2 units fail | 18:35 |
| T42_ | <vilez0> `● droid-hal-init.service loaded failed failed droid-hal-init ● droid-late-start.service loaded failed failed droid-late-start` | 18:35 |
| T42_ | <vilez0> https://paste.medip.dev/p/LjJfnq | 18:48 |
| T42_ | <vilez0> (changed storage to automatic in the conf) (re @vilez0: https://paste.medip....) | 18:48 |
| mal | just to be sure, did you device in droid-configs spec the correct android version with something like this: %define android_version_major 13 | 20:10 |
| mal | *define | 20:10 |
| T42_ | <vilez0> No I didn't | 20:20 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!