Tuesday, 2021-02-02

mighty17oh i get error 7 when installing sfos....05:17
mighty17it seems it cant mount storage 🤔05:17
mighty17is it coz fixup-mountpoints are not proper? or the fstab?05:51
MightyDoes noone hve any idea? Is says `mount: failed to mount /dev/block/platform/omap_hsmmc.1/by-name/DATAFS at /data: `07:43
MightyNo such file or directory07:44
T42<birdzhang> is your /data encrypted07:44
MightyNope i don't think so07:46
MightyShould I do a format?07:46
Mightybirdzhang even after format and using twrp 3.2 I get /data: Device or resource busy07:57
mighty17I cant get any solution on the internet :( is my build broken? (ps my device is espresso3g)08:48
T42<birdzhang> mighty17: "Device or resource busy" is okay08:49
electro575@elros34 : hi elros, i have installed LineageOS and SailfishOS on my device t0lte.08:53
electro575telnet start with port 23 not 232308:54
electro575so when i do continue, i have a kernel panic, i don't know how to solve it08:54
electro575/proc/cmdline -> https://dpaste.org/22cz08:55
electro575selinux = 0 audit = 008:55
electro575dmesg -> https://dpaste.org/rsUP08:55
electro575if you have a solution08:55
mighty17<T42 "<birdzhang> mighty17: "Device or"> but it dosent boot to sailfishos! it boots into lineageOS09:01
mighty17as it ends with ERROR 709:09
electro575mighty17, before install LineageOS and SailfishOS09:13
electro575in TWRP, umount DATA partition09:13
mighty17oooh i will try that thanks09:13
electro575juste keep "cache" and "sd_card" mount09:13
electro575format all partition before flash too09:14
mighty17ok just to be very clear about what is to be done09:14
mighty17clear dalvik,system,cache,data -> keep only cache and sdcard mounted -> flash lineage -> flash sailfishos correct?09:15
mighty17yay it worked! thanks a lot09:28
mighty17electro575: it shows error 709:39
electro575don't know, send an image if you can09:40
* mighty17 uploaded an image: IMG_2021-02-02-15-24-06-480.jpg (80KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/YxwAzzMklyXaGnDTyAwKExPM/IMG_2021-02-02-15-24-06-480.jpg >09:54
mighty17electro575 ^^^09:54
electro575strange, i don't know anymore09:55
electro575i never had this issue09:55
mighty17is my build broken?09:56
mighty17anyone else who can help me?11:19
T42<elros34> grepping irclogs.sailfishos.org should be your first action if you stuck11:37
mighty17elros34 do u have any idea?11:39
mighty17i am getting error7 on flashing sfos11:43
T42<elros34> yeah, second link in google search "error 7 site:irclogs.sailfishos.org" contains 3 solutions11:52
mighty17elros34 i tried everything, downgraded twrp, formatted /data even removed assert line11:57
T42<elros34> what twrp version have you tried?11:58
mighty173.0, 3.2, 3.411:58
mighty17as with older 2.x twrps android 7 wont install11:58
T42<elros34> did you check exact error you get in twrp log? If none of version works then try other workarounds12:01
mighty17<mighty17 "IMG_2021-02-02-15-24-06-480.jpg"> this image is what i get in twrp i have yet to check the twrp log12:03
mighty17oh okay now i have a different error unknown command[]]12:16
mighty17ok so i consider it works except now i only get a screen with backlight on... i can telnet into the device as well :) next what to do?12:44
mighty17https://pastebin.ubuntu.com/p/nDN9mMcc9X/ heres the log12:49
mighty17@elros34 sorry for the trouble can u find any issues?12:59
T42<elros34> what android base do you use?13:00
mighty17i used android 7.1.2 (los 14.1)13:08
mighty17`[Tue Feb  2 16:59:05 2021] usb 1-1.1: Product: Failed to boot init in real rootfs` i get this on dmesg on my pc13:08
T42<elros34> so you are in telnet 23 not 2323?13:10
mighty17`SerialNumber: Mer Debug telnet on port 23 on rndis0 #####(i havent shown ip) - also running udhcpd`13:10
T42<elros34> so https://github.com/mer-hybris/hadk-faq/pull/6/files and this https://github.com/mer-hybris/mer-kernel-check/pull/27/files13:11
mighty17so change them and rebuild sfos??13:12
T42<elros34> add repo and follow advice from mer-kernel-check then rebuild13:13
mighty17add repo?13:14
T42<elros34> did you read what is wrote in mentioned PRs13:15
mighty17`Add repository with patched glibc to droid-configs/sparse like here: https://github.com/elros34/droid-config-moto_msm8960_jbbl/blob/master/sparse/usr/share/ssu/features.d/glibc2.ini` yes i did13:16
T42<elros34> repo=repository13:18
mighty17yup i know that, but there is no usr folder in sparse so i created all that and added glibc2.ini file as told13:19
mighty17now repo sync or smth? or direct build (ie check kernel config)13:20
T42<elros34> if you changed anything in droid-configs then you need to rebuild it: build_packages.sh -c. Usage of mer-kernel-check is explained in hadk, you need to disable selinux via bootparam13:21
mighty17okay i understood the build_packages.sh, but i didnt get `disable selinux via bootparam`13:22
mighty17also mer-kernel-check gives no errors13:23
mighty17oh i cant find it in PR my bad13:26
mighty17so basically edit .config file with CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0, run build_packages.sh -c and then build_packages.sh --mic13:30
T42<elros34> not at all13:31
T42<elros34> edit your defconfig file according to hadk not .config file, then build kernel: make hybris-hal then confirm with mer-kernel-check (.config) everything is as expected, next build droid-hal. Be aware kernel config have dependencies so you also need CONFIG_SECURITY_SELINUX_BOOTPARAM13:33
mighty17and CONFIG_SECURITY_SELINUX_BOOTPARAM should be=y right?13:34
T42<elros34> yes13:35
mighty17edit your defconfig file according to hadk not .config file, but mer-kernel-check checks the .config file acc to hadk13:35
mighty17`hybris/mer-kernel-check/mer_verify_kernel_config ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config13:36
mighty17 * `hybris/mer-kernel-check/mer_verify_kernel_config ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config`13:36
mighty17ahh okay my bad13:36
mighty17sorry and thanks a lotfor the help13:36
mighty17any idea why CONFIG_IP6_NF_MATCH_RPFILTER and CONFIG_IP6_NF_MATCH_RPFILTER dont seem to get enabled in .config? i have them in the defconfig but do they depend on smth?14:43
mighty17they depend on CONFIG_IP6_NF_MATCH_RPFILTER which is =y still those errors 😕 can i manually add them to .config and run make?14:55
mighty17i followed this https://irclogs.sailfishos.org/logs/%23sailfishos-porters/%23sailfishos-porters.2020-01-24.log.html ping me if i am doing wrong15:01
mighty17ie just changed mer-kernel-config to set those to warnings instead of errors15:02
mighty17btw https://en.wikipedia.org/wiki/Sailfish_OS#Version_history needs to be updated :D15:50
mighty17@elros34 i did what you told but still its the same16:43
mighty17here is /init.log -> https://pastebin.com/dAUvJs3D16:44
T42<elros34> mounting /dev/block/platform/omap_hsmmc.1/by-name/DATAFS on /data failed: No such file or directory16:45
T42<elros34> did you create correct fixup-mountpoints16:46
mighty17they were already present16:46
mighty17and i matched them with the device and are correct16:47
T42<elros34> compare with fstab entries16:48
mighty17fstab dosent have mmcblkxpy16:49
mighty17oh wait ig something is wrong16:51
mighty17no its all fine16:56
mighty17elros34 https://github.com/mer-hybris/hybris-boot/blob/master/fixup-mountpoints#L805-L813 it seems correct16:59
mighty17https://pastebin.com/SBMDzRhg <- adb shell16:59
mighty17<electro575 "juste keep "cache" and "sd_card""> i did this to install sfos...17:01
mighty17@elros34ok so i mounted system and data again... here is new init.log -> https://pastebin.com/zh3cBJU717:13
mighty17same issue17:13
mighty17weird thing :/17:14
mighty17Someone help :(17:26
T42<elros34> for me your fstab and fixup doesnt match17:56
mighty17/dev/block/platform/omap_hsmmc.1/by-name/ and block/platform/omap/omap_hsmmc.1/by-name/ which is correct? the /dev one right?17:57
T42<elros34> fixup-mountpoints is just a sed script which takes fstab and init*rc files and replace by-name path with direct path to block device.18:01
mighty17so is my init.espresso wrong?!18:04
mighty17 * so is my fstab.espresso wrong?! sorry im confused18:05
T42<elros34> your fixup-mountpoints replace block/platform/omap/omap_hsmmc.1/by-name/DATAFS with mmcblk0p10 but there is no such a path in your fstab right? It must be block/platform/omap_hsmmc.1/by-name/DATAFS instead18:06
T42<elros34> I guess current fixup is from older android base and something change in your current android base18:08
mighty17well then how does my device have a working sfos (old) port18:08
mighty17ya its from cm12.218:08
mighty17 * ya its from cm12.118:08
mighty17and im using los14.118:08
T42<ankaos> mighty: open recovery.18:09
mighty17ok im in twrp18:09
T42<ankaos> ls -l /dev/block/platform/*/by-name/18:10
T42<ankaos> or ls -l /dev/block/platform/*/*/by-name18:11
mighty17both of them work18:11
T42<ankaos> than look fstab18:11
T42<ankaos> ı dont open pastebin :(18:11
mighty17any other site? can i paste it here?18:12
T42<ankaos> @mighty17 [any other site? can i paste it here?], paste ubuntu18:12
T42<ankaos> add fstab?18:13
T42<ankaos> read fstab file18:14
T42<ankaos> your device name?18:15
mighty17Samsung Galaxy Tab 2 (it has 2 variants espresso3g and espressowifi)18:16
mighty17and fstab.espresso18:16
mighty17is common for both :)18:16
T42<ankaos> https://pastebin.ubuntu.com/p/Rj8vX8VbYT/18:16
T42<ankaos> ı asked :)18:17
mighty17oh thats the fixup-mount points18:17
T42<ankaos> https://pastebin.ubuntu.com/p/5pCC2FxBM4/18:17
T42<ankaos> ı asked :)18:17
T42<ankaos> @mighty17 [oh thats the fixup-mount points], yes :)18:18
mighty17??? its literally the same xD18:18
T42<ankaos> I find.18:18
T42<ankaos> :)18:18
mighty17p3xxx or p5xxx are the devices like this tab has many variants xD18:18
T42<ankaos> XD18:19
mighty17there is 3g,wifi,7 inch,10 inch and all their combinations18:20
mighty17<T42 "<ankaos> I find."> ah okay.... but whats the solution :(18:20
T42<ankaos> but I can't solve my own problem.  😢18:20
mighty17whats that :o18:20
T42<ankaos> @ankaos [https://pastebin.ubuntu.com/p/5pCC2FxBM4/], add your fixup-mountpoints18:20
mighty17but they are already there... the sed is the same18:22
T42<ankaos> hmm idk18:22
mighty17ok here is something even confusing18:23
T42<ankaos> hybris-boot folder open18:23
T42<ankaos> android.mk open18:23
T42<ankaos> edit line 71-7218:23
mighty17<T42 "<ankaos> edit line 71-72"> okay wait18:24
T42<ankaos> error -> warning18:24
T42<ankaos> and you are build :D18:24
mighty17<T42 "<ankaos> error -> warning"> it is already a warning18:24
mighty17$(warning ********************* /boot appears to live on $(HYBRIS_BOOT_PART))18:25
mighty17$(warning ********************* /data appears to live on $(HYBRIS_DATA_PART))18:25
T42<ankaos> error is finish bild.18:25
T42<ankaos> @mighty17 [$(warning ********************* /data appears …], good :D18:25
mighty17it was already a warning18:25
T42<ankaos> not problem.18:25
T42<ankaos> build finish :)18:25
mighty17<T42 "<ankaos> build finish :)"> no it was already warning on the build before and it give error18:26
mighty17> <@freenode_T42:matrix.org> <ankaos> build finish :)18:26
mighty17 * no it was already warning on the build before and it give error of mount: mounting /dev/block/platform/omap_hsmmc.1/by-name/DATAFS on /data failed: No such file or directory18:26
mighty17should i use old fstab?18:27
mighty17<mighty17 "https://pastebin.ubuntu.com/p/Yr"> see this18:28
T42<ankaos> I do not believe that18:30
mighty17https://pastebin.ubuntu.com/p/8bZ7Sy4SQ2/ see log for yourself @ankaos18:32
electro575@elros34 : Can you help me about kernel panic ? After echo "continue" with telnet port 2318:33
electro575@mal maybe have you a solution ?18:37
malright after that or after a moment? is the rootfs correctly mounted?18:41
electro575not again18:42
electro575correctly mount18:42
electro575i have just telnet port 2318:44
attahpiggz: did you have a chance to try the fastboot hack?18:46
electro575@mal, https://dpaste.org/tOud#L193,19518:46
piggzattah: i havnt18:47
attahOk, np. It works great for getvar for me, but i'm not sold on reflash my spare XA2 that is all set up, so can't try quite end to end18:49
attahAnd Xperia X doesn't seem to have the issue18:49
malelectro575: why does it stop to telnet 23?18:49
malelectro575: that log says you have incorrect fixupmountpoints18:50
mal+ mount /dev/block/platform/dw_mmc/by-name/USERDATA /data18:50
malmount: mounting /dev/block/platform/dw_mmc/by-name/USERDATA on /data failed: No such file or directory18:50
mighty17Fixup mount points seem to be really confusing18:55
mighty17<mighty17 "https://pastebin.ubuntu.com/p/Yr"> Well I can ls -l to /data but sfos gives an error18:56
T42<elros34> the are quite simple, you take by-name path from fstab and use ls -l "path from fstab" inw twrp to get mapping between blockdevice and partition label18:59
mighty17well exactly i did that and it is the proper path :D19:01
mighty17it seems that fixup-mountpoints is of cm12.1 and my fstab is of los14.1 so im trying with older fstab19:01
T42<elros34> what? no you seems to still don't understand how it works so just replace block/platform/omap/omap_hsmmc.1/by-name/ with block/platform/omap_hsmmc.1/by-name in fixup-mountpoints19:03
mighty17okay will try thanks19:05
electro575@mal, have you a solution ?20:33

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!