Sunday, 2024-07-07

T42_<vilez0> @elros34, i did a completely clean build16:48
T42_<vilez0> now the config is fine but it still doesnt boot16:48
T42_<vilez0> init.log:
T42_<vilez0> diagnosis.log:(simply 1 line: `CONFIG_AUTOFS4_FS=y not found in /proc/config.gz)`16:48
T42_<vilez0> kernel_config (pulled from device, not from my host):
T42_<vilez0> but it still doesnt boot16:48
T42_<vilez0> still telnet doesnt work16:53
T42_<vilez0> btw CONFIG_AUTOFS4_FS is defined in the config but init.log says its not16:54
T42_<vilez0> btw the phone is shown in ifconfig output but it doesnt have an ip:17:59
T42_<elros34> don't copy initramfs init.log to /target/init.log. This file is used when you boot to rootfs.  I really don't believe this kernel_config is pulled from device. If it's really now only missing autofs4_fs and everything else is ok then remove this config check from init script, it's useless in this place anyway18:09
T42_<elros34> about ip, there is intruction how to get it in hadk-hot18:10
T42_<vilez0> this is what i was looking into, how this can happen (re @elros34: don't copy initramfs...)18:12
T42_<vilez0> i even deleted the kernel_config from recovery to be sure that the file that i will copy its the latest one18:13
T42_<elros34> AFAIK .config.gz doesn't have random comments and always sort configs, yours looks like defconfig so unless something changed with recent kernels or this one is broken for me  file doesn't looks like /proc/config.gz. About log I told you to copy initramfs init.log to /target/initramfs.log to avoid confusion. There are 2 copy of init-script: in initramfs and rootfs and both redirects output to /init.log but first in initramfs /, second in roo18:18
T42_<vilez0>` `this ss is from my host, and as you can see there is comments there (re @elros34: AFAIK .config.gz doe...)19:31
T42_<vilez0> how can i mask usb-moded? i dont have any access to shell/init19:33
T42_<vilez0> speaking about why it fails with AUTOFS4_FS although it defined, looks like there is a space after y in definition19:38
T42_<vilez0> and this is the problem:
malso fix it19:45
T42_<vilez0> i did, waiting a build19:46
T42_<vilez0> *the build19:46
T42_<elros34> it's irrelevant config, comment it out and move on. Did you managed to get real init.log (not copied from initramfs)?20:03
T42_<vilez0> no, it does not appear there20:05
T42_<vilez0> `[    6.815775] exFAT-fs (sda36): invalid boot record signature20:06
T42_<vilez0> [    6.815788] exFAT-fs (sda36): failed to read boot sector20:06
T42_<vilez0> [    6.815793] exFAT-fs (sda36): failed to recognize exfat type`20:06
T42_<vilez0> this is from dmesg20:06
T42_<vilez0> latest lines20:06
T42_<vilez0> full dmesg20:07
T42_<elros34> why it's exfat? is sda36 your data partition?20:07
T42_<vilez0> yes20:11
T42_<vilez0> I just checked again from recovery20:11
T42_<vilez0> `/dev/block/by-name/userdata -> /dev/block/sda36`20:11
T42_<elros34> So your device reboots or what is happening?20:11
T42_<vilez0> no, just waiting on bootloader (even after 5 minutes)20:12
T42_<elros34> How can you not have /data/.stowaways/sailfishos/init.log if you clear DBG_REASON. Do you have /data/.stowaways/sailfishos/init-debug?20:13
T42_<elros34> didn't you make same mistake in init-script?20:14
T42_<elros34> run 'ls -al /data/.stowaways/sailfishos/'20:15
T42_<vilez0> i dont have /data (tg://bot_command?command=data)/.stowaways/sailfishos/init-debug20:15
T42_<vilez0> `` (re @elros34: run 'ls -al /data/.s...)20:16
T42_<vilez0> (edited) (re @elros34: run 'ls -al /data/.s...)20:16
T42_<elros34> cmon you didn't even install sailfishos, no wonder it doesn't work20:16
T42_<vilez0> i flashed the zip, generated via mic20:17
T42_<vilez0> isnt it enough?20:17
T42_<elros34> it is unless you for example format data partition after that20:17
T42_<vilez0> i dont format any part after format20:20
T42_<vilez0> but let me flash it again to be sure20:20
T42_<elros34> whole sailfish is installed to /data/.stowaways/sailfishos/ provided you follow regular hadk pdf instruction. First thing executed is mentioned /init-debug20:23
T42_<vilez0> i will try to extract the archive by hand20:25
T42_<vilez0> seams like my recovery doesnt have bzip220:34
T42_<vilez0> and that is the problem, this is why it is not extracted20:34
T42_<vilez0> okay, looks like now we have init.log20:45
T42_<vilez0> Anyway, it's very late here, I'll continue tomorrow20:46

Generated by 2.17.1 by Marius Gedminas - find it at!