| T42 | <vsvoid> @elros34 Am failing to understand how my device not being able to find any partitions while still in initrd relates to errors in the fixup-mountpoints, to my understanding the fixup-mountpoints are needed once sailfish rootfs has been loaded not so? | 11:46 |
|---|---|---|
| T42 | <elros34> but also for initramfs. | 11:56 |
| T42 | <elros34> is this by-name path excatly the same (copy and ctrl + f relevant part)you used in fixup-mountpoints? | 11:59 |
| T42 | <elros34> https://github.com/Redmi-MT6768/android_device_xiaomi_mt6768-common/blob/lineage-18.1/rootdir/etc/fstab.mt6768#L23 | 11:59 |
| T42 | <elros34> Explanation is also simple: as in early boot, initramfs also do not have udev and this by-name symlinks aare invalid so you need real block device /dev/mmcblk or /dev/sdx | 12:01 |
| T42 | <vsvoid> Yes it exactly the same | 12:02 |
| T42 | <elros34> Dontt believe yo, sow both files in same paste | 12:05 |
| T42 | <elros34> Show* | 12:05 |
| T42 | <vsvoid> https://pastebin.com/UKPJtawm | 12:13 |
| T42 | <elros34> run make hybris-hal and chek output line: boot/data appears to live. Are the correct with by-name paths? Then package droid-hal and confirm that init script somewhere in out/ is correct | 12:45 |
| T42 | <vsvoid> Unfortunatly the say the appear on /boot and /data which is confusing, as if they can't find the fstab file | 12:46 |
| T42 | <vsvoid> @elros34 | 14:17 |
| T42 | <vsvoid> https://pastebin.com/ePTXgGUE | 14:17 |
| T42 | <elros34> @vis | 21:18 |
| T42 | <elros34> @vsvoid looks good | 21:18 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!