**** BEGIN LOGGING AT Wed Oct 23 02:59:58 2019 Oct 23 04:43:08 Matti Laine was added by: Matti Laine Oct 23 05:59:11 Darn. So the best option would be to build postmarketOS with the GUI I'd want Oct 23 07:11:43 Do Replicant OS & Halium have something in common regarding what they aim/require to do n accomplish? … (sry, i dont understand quite comprehensively what part these two aim to do - HALium wanna do Open HALs and Replicant wanna strip proprietary software at the core... so are these 2 things same??) … Ref: https://en.wikipedia.org Oct 23 07:11:43 /wiki/Replicant_(operating_system) (via @wiki) Oct 23 07:13:26 [Edit] Do Replicant OS & Halium have something in common regarding what they aim/require to do n accomplish? … (sry, i dont understand quite comprehensively what part these two aim to do - HALium wanna do Open HALs and Replicant wanna strip proprietary software at the core... so aren't these 2 things same atleast for HALs??) … Re Oct 23 07:13:26 f: https://en.wikipedia.org/wiki/Replicant_(operating_system) (via @wiki) Oct 23 07:14:20 [Edit] Do Replicant OS & Halium have something in common regarding what they aim/require to do n accomplish? … (sry, i dont understand quite comprehensively what part these two aim to do - HALium wanna do Open HALs and Replicant wanna strip proprietary software at the core... so aren't these 2 things same, atleast for HALs??) … R Oct 23 07:14:20 ef: https://en.wikipedia.org/wiki/Replicant_(operating_system) (via @wiki) Oct 23 07:16:41 [Edit] Do Replicant OS & Halium have something in common regarding what they aim/require to do n accomplish? If yes, then will it be a common good for both if they work together? … (sry, i dont understand quite comprehensively what part these two aim to do - HALium wanna do Open HALs and Replicant wanna strip proprietary software Oct 23 07:16:41 at the core... so aren't these 2 things same, atleast for HALs??) … Ref: https://en.wikipedia.org/wiki/Replicant_(operating_system) (via @wiki) Oct 23 07:20:38 The difference is replicant uses Android as Os and replace some parts. Halium tries to minimise what's needed by android at all. So in halium is only a small lxc android container started to talk with the propietary hardware drives Oct 23 07:52:32 of course, when replicant manages to "free" a driver, a halium port is probably happy to use it - but in the end, if the drivers are freed, the OS' Oct 23 07:52:52 [Edit] of course, when replicant manages to "free" a driver, a halium port is probably happy to use it - but in the end, if the drivers are freed, the OS-es that use halium would rather use mainlin Oct 23 09:37:44 What are namespaces in LXC? If I disable them in defconfig will I still get some hardware to test? Oct 23 09:38:11 @rixchy [The culprit was CONFIG_NAMESPACES=y], This was bootlooping my device. (Turns on, reboots,) Oct 23 09:39:30 @rixchy [What are namespaces in LXC? If I disable them in defconfig will I still get some …], Are they on the required flags for Halium/systemd list? ^^ Oct 23 09:39:44 Not sure. Oct 23 09:40:14 which kernel config checker did you use? from halium docs or from ubports Oct 23 09:40:29 From halium docs. The mer-kernel check. Oct 23 09:42:01 @rixchy namespaces are kernel support for containers Oct 23 09:42:05 lxc won't work without namespaces Oct 23 09:42:23 But it was bootlooping my device, how can I debug the reason, then? Oct 23 09:42:26 Well lxc will work without user ones Oct 23 09:42:54 These which we disable to resolve kernel compile errors Oct 23 09:43:23 Config_users_ns or how it was Oct 23 09:44:35 Wait, so I am confused now. Oct 23 09:45:00 test_lights will won't work too without namespaces, right? Oct 23 09:45:44 "root@localhost:~# /system/bin/logcat … logcat read failure" Oct 23 09:46:30 @rixchy [test_lights will won't work too without namespaces, right?], Its not using the lxc container, yes Oct 23 09:46:58 Can you give me a tip/push on what to do at this moment? Oct 23 09:47:07 Well whats your kernel version? Oct 23 09:47:12 3.4. Oct 23 09:47:21 3.4.113 probably Oct 23 09:47:21 I think this was the culprit, but the goal is UT. Oct 23 09:47:48 Something is conflicting this setting. ALl Android kernels are broken in some way, unfortunately. You do the smallest possible change and it crashes. You could ask in the lxc IRC channel if they know how to debug. Is there any dmesg log for it? Oct 23 09:48:15 Wait, BRB. Just used dmesg in SSH. Oct 23 09:48:46 Well wasn't namespaces responsible for kernel fault? Oct 23 09:48:51 Without lxc running? Oct 23 09:49:15 We wanted to see if it's kernel fault or lxc Oct 23 09:49:43 @Akatsu . [Well wasn't namespaces responsible for kernel fault?], I don't really know, but when CONFIG_NAMESPACES=y is configured in defconfig, sometimes a get SSH for a second or two. That means that the device boots into rootfs. Oct 23 09:50:14 Here is the dmesg log from SSH if you wanna look at it: https://pastebin.com/JKRtUzWJ Oct 23 09:51:33 @Flohack any idea how can I debug phone reboot after few 30s? Oct 23 09:51:52 I bet it's android in lxc which fail on some hardware Init Oct 23 09:52:10 Because getting android image off made phone to boot rootfs just fine Oct 23 09:52:41 @Akatsu . [@Flohack any idea how can I debug phone reboot after few 30s?], 2 options: YOur kernel gets stuck and the watchdog kills it, or the kernel encounters a kernel panic and reboots after 15s or so. 30s seems a bit long. Maybe its watchdog idk. In any case, you need dmesg logs or the newer ones from the other location which I always Oct 23 09:52:41 forget ^1 Oct 23 09:53:01 @Akatsu . [@Flohack any idea how can I debug phone reboot after few 30s?], connect.py -p ssh -u root ? Oct 23 09:53:07 And read dmesg maybe? Oct 23 09:53:08 Dmesg is pretty dead Oct 23 09:53:17 I mean it ends on audio Init logs Oct 23 09:53:22 When alsa is initialized Oct 23 09:53:33 @rixchy [Here is the dmesg log from SSH if you wanna look at it: https://pastebin.com/JKR …], This was running for over 200 seconds? Oct 23 09:53:44 No. More like 2 seconds. Oct 23 09:54:05 If its watchdog, maybe disabling it in defconfig? Oct 23 09:54:47 Well I tried yesterday switching values to n on defconfig and I narrowed down that the CONFIG_NAMESPACES was the culprit. Oct 23 09:54:50 CONFIG_WATCHDOG_NOWAYOUT=y Oct 23 09:54:56 This one? Oct 23 09:55:28 Yeah, try setting that to n Oct 23 09:55:45 I have introduced it myself Oct 23 09:55:52 I mean this option Oct 23 09:56:06 Should I log lxc-checkconfig? Oct 23 09:56:15 @Akatsu . [I have introduced it myself], Meaning you put it in? Oct 23 09:56:25 Yup Oct 23 09:56:57 Ok, try setting it to n, see if you get same behaviour Oct 23 09:57:18 Set the CONFIG_NAMESPACES to y or leave it on n? Oct 23 10:05:50 @Shakendo [Ok, try setting it to n, see if you get same behaviour], What is this option about? If I read it names it gives me impression that it makes kernel to panic Oct 23 10:06:05 If error appear Oct 23 10:07:37 Well its supposed to kill whatever crashes (like alsamixer using 100% kernel for too long) setting to n shouldnt hurt anything Oct 23 10:08:50 https://cateee.net/lkddb/web-lkddb/WATCHDOG.html Oct 23 10:10:44 Hmm Oct 23 10:10:48 It sounds right Oct 23 10:11:15 I remember from tizen docs there is issue with alsa and cpu optimization Oct 23 10:11:24 On 410 Oct 23 10:11:30 One of these days Im gonna go through and document every flag in my defconfig, but thats a side project Oct 23 10:12:49 @Shakendo [One of these days Im gonna go through and document every flag in my defconfig, b …], Woooow😂😂😂 Oct 23 10:13:21 lul. Oct 23 10:13:36 For me its a curiosity exercise Oct 23 10:16:46 CONFIG_WATCHDOG_NOWAYOUT=n and CONFIG_MANESPACES=y. Device still reboots in a loop. Oct 23 10:16:58 @rixchy which rootfs are you running? Oct 23 10:17:12 probably LXC startup causes a kernel panic Oct 23 10:17:37 The halium reference ones. Oct 23 10:18:05 try UBPorts one + halium-boot instead Oct 23 10:18:13 reference is too unmaintained by now Oct 23 10:18:35 But my device is ARM 32 bit, they published 64 bit one. Oct 23 10:18:55 armhf is 32-biy one Oct 23 10:18:59 [Edit] armhf is 32-bit one Oct 23 10:19:05 ...let me look. Oct 23 10:19:54 "Next we’ll need to download the rootfs (root filesystem) that’s appropriate for your device. Right now, we only have one available. Simply download ubports-touch.rootfs-xenial-armhf.tar.gz from our CI server. If you have a 64-bit ARM (aarch64) device, this same rootfs should work for you. If you have an x86 device, let us know. We do not Oct 23 10:19:54 have a rootfs available for these yet." Oct 23 10:20:00 I have a 32 bit device. Oct 23 10:20:16 Oh. Oct 23 10:20:25 I just understood, I apologize. Oct 23 10:20:29 Let me try to install. Oct 23 10:23:07 Halium boot requires more parameters Oct 23 10:23:25 I men kernel config Oct 23 10:28:58 @NotKit [try UBPorts one + halium-boot instead], "Uploading BOOT … 100% … ERROR: Failed to confirm end of file transfer sequence! … ERROR: BOOT upload failed!" Oct 23 10:30:14 boot image is too large? Oct 23 10:30:15 Redo Oct 23 10:30:18 Have you ran check kernel config from halium? Oct 23 10:30:41 Isn't boot.img like 12MB? Oct 23 10:30:50 Wait let me check. BRB. Oct 23 10:36:30 @rixchy ["Uploading BOOT … 100% … ERROR: Failed to confirm end of file transfer sequence! … ERR …], No, you are wrong Oct 23 10:36:39 @Mattia990 [No, you are wrong], Hm? Oct 23 10:36:52 @NotKit [try UBPorts one + halium-boot instead], He suggested halium-boot.. Oct 23 10:37:03 So I executed mka halium-boot and tried to flash it. Oct 23 10:37:06 Where was I wrong? Oct 23 10:37:22 @rixchy [Wait let me check. BRB.], You need to use another script to modify the defconfig, build halium-boot and redo the halium install with ut armhf rootfs Oct 23 12:04:54 Well lxc changes will persist Oct 23 12:04:54 That's good Oct 23 12:04:54 Less stuff to care anout Oct 23 12:04:54 So, what is that script? Oct 23 12:04:54 I do not know such script. Oct 23 12:04:54 Kernel check config inside halium-boot Oct 23 12:04:54 if he can't flash boot, kernel config does not matter at all Oct 23 12:04:54 It has - w parametr to fix config Oct 23 12:04:54 He flashed mer one already Oct 23 12:04:54 what are you suggesting will cause more issues at this moment, better start with known working config Oct 23 12:04:54 Will it boot with mer settings? Oct 23 12:04:54 @Akatsu . [He flashed mer one already], but halium-boot is few mbs larger than hybris-boot due to ramdisk, so if it is larger than his boot partiton, it is a problem Oct 23 12:04:54 Welp, now I am confsued. Oct 23 12:04:54 @Akatsu . [Will it boot with mer settings?], it should Oct 23 12:04:54 Resize boot partition😂 **** BEGIN LOGGING AT Wed Oct 23 12:06:06 2019 Oct 23 12:09:30 [Edit] I indeed have kernel 3.4, but I do have Exynos processor. Oct 23 12:11:58 @rixchy: For 3.4 kernel you would need to apply some patches probably. We needed for QualComm ones. I suspect for Exynos as well. Oct 23 12:13:24 Ok, can you guide me please? Oct 23 12:13:28 @rixchy: See https://github.com/Halium/android_kernel_lge_hammerhead/commits/halium-5.1 and specifically: https://github.com/Halium/android_kernel_lge_hammerhead/commit/25437b2a54dd619a96e268ecaf303b089aa785e4, https://github.com/Halium/android_kernel_lge_hammerhead/commit/5754614eb43dea44a99e54898e3b83d4d96d8b83, https://github.com/Halium/android_kernel_lge_hammerhead/commit/bd221854de33b75 Oct 23 12:13:28 db7a7fa01cb34274b62a7cbf8 and https://github.com/Halium/android_kernel_lge_hammerhead/commit/17a8d0630b424d66981900e701ae2a452d4b8726 Oct 23 12:14:02 I think I did those patches already..... Oct 23 12:14:05 Most other commits are "LuneOS" specific since we use newer GCC toolkit (7 or 8) to build the kernel v.s. GCC 4.8/4.9 used by Halium and Android. Oct 23 12:14:44 Should I make a GitHub repo with all the build files I have? Oct 23 12:14:44 There seem to be various variants of https://github.com/Halium/android_kernel_lge_hammerhead/commit/17a8d0630b424d66981900e701ae2a452d4b8726 floating around for various 3.4 kernel versions. Rest should be pretty generic Oct 23 12:15:04 @rixchy: Yes that's a good approach. For the original kernel you use and apply the patches there Oct 23 12:15:18 Okay.. Oct 23 12:18:50 Where is this file located? https://github.com/Halium/android_kernel_lge_hammerhead/commit/5754614eb43dea44a99e54898e3b83d4d96d8b83 Oct 23 12:20:38 This isn't going to fix anything, since those patches are already applied on my build. Oct 23 12:23:20 Patches are already made, yup. Oct 23 12:24:55 Edit. This patch wasn't applied. -> https://github.com/Halium/android_kernel_lge_hammerhead/commit/17a8d0630b424d66981900e701ae2a452d4b8726 Oct 23 12:25:13 Going to rebuild hybris-boot again with CONFIG_NAMESPACES set to y. Oct 23 12:25:21 That one is more for systemd > 233, but doesn't hurt to have Oct 23 12:25:32 Alright. Oct 23 12:25:40 Where was that fix, in the docs? Oct 23 12:31:23 rixchy: the fix was backported from newer kernel; we found it with some tedious try & debug sessions Oct 23 12:31:55 @rixchy [/home/rixchy_/halium/kernel/samsung/exynos5420/fs/stat.c:65:17: note: each undec …], Do you know how to fix this one? Oct 23 12:32:49 please use a pastebin, I don't see the message you're talking about Oct 23 12:33:00 Oh, sorry! Oct 23 12:33:46 https://pastebin.com/3dDYTZfk Oct 23 12:36:12 mmh this might be a mismatch between more recent code and an old patch; for hammerhead we just use fput: https://github.com/Halium/android_kernel_lge_hammerhead/blob/17a8d0630b424d66981900e701ae2a452d4b8726/fs/stat.c#L65 Oct 23 12:36:30 Ok, I will check the patch in a sec. Oct 23 12:38:18 on tenderloin (HP Touchpad, old kernel too) we had to revert a problematic commit: https://github.com/shr-distribution/linux/commit/01141a353241d545a2aaf9addaa32afe39a98562 Oct 23 12:45:21 @Tofe [mmh this might be a mismatch between more recent code and an old patch; for hamm …], Did the trick. 👍 Oct 23 12:49:54 @rixchy: 3.4 is a bit tricky at times. It's really at it's last legs to be honest. There will be a point where it will be not possible to patch it anymore. But for now with minimal patches it's workable. Oct 23 12:50:30 @Herrie [@rixchy: 3.4 is a bit tricky at times. It's really at it's last legs to be hones …], Wonderful, now I am getting a "heimdall detect … ERROR: Failed to detect compatible download-mode device." error. Oct 23 12:50:35 Great! Oct 23 12:51:52 Heimdall, I'll pass, I don't know anything about that bootloader Oct 23 12:51:59 Same here ;) Oct 23 12:52:07 It's okay. Oct 23 12:52:22 I have a Samsung device, so I have to keep up with that. xD Oct 23 12:53:55 :) Oct 23 13:00:09 Hm. The device isn't rebootin- It rebooted. Oct 23 13:00:18 It is rebooting again. Oct 23 13:00:35 Why is the namespaces interfering with this?! Oct 23 13:00:54 If I set CONFIG_NAMESPACE to n in defconfig, it works! If it's y, then it is rebooting. Oct 23 13:02:48 Can you get a last_kmsg via a recovery? Oct 23 13:02:59 Sure, please wait. BRB. Oct 23 13:03:57 (Document) https://irc.ubports.com/8kYk5BCk.txt Oct 23 13:05:35 looks like the real error are the mount issues just before the crash Oct 23 13:06:00 The mountpoint 21? Oct 23 13:06:18 and loop0 Oct 23 13:06:35 Alright. Mountpoint 21 is userdata. But why. Oct 23 13:06:46 I reformatted it, because I had the same issue yesterday. Oct 23 13:07:04 Tho I have no idea what loop0 is. Oct 23 13:07:05 ACL ? journal ? Oct 23 13:07:13 ? Oct 23 13:07:28 loop0 is when halium mounts a .img, ramdisk for instance Oct 23 13:07:49 Ok. Oct 23 13:08:15 (or system rootfs; it depends on how you've put it in the userdata partition) Oct 23 13:08:40 Alright. Oct 23 13:12:54 Do you have any tips for me to do? Oct 23 13:14:22 you could check your defconfig, see if ACL are enabled, for instance; also compare with a working defconfig like hammerheads Oct 23 13:14:52 Could you explain to me, what ACL is. Oct 23 13:18:48 Access control list Oct 23 13:20:24 CONFIG_NFS_ACL_SUPPORT? Oct 23 13:21:03 Or CONFIG_NFS_V3_ACL? Oct 23 13:29:53 yes, I was just more thinking about the ones for ext4: https://github.com/Halium/android_kernel_lge_hammerhead/blob/533a628f03d4d0be2f1c4e969aa1c6d7a7e564bb/arch/arm/configs/cyanogenmod_hammerhead_defconfig#L3060 (and next lineà Oct 23 13:29:54 ) Oct 23 13:30:35 but I said ACL at random; it just seems related to some FS capability Oct 23 13:33:17 but I might be wrong, as it crashes in the loopback network device init, not in the loop fs driver Oct 23 13:33:30 (I misread the crash stack :) ) Oct 23 13:37:47 Maybe boot to hybris recovery and then mount 21 and then rootfs.img Oct 23 13:38:06 Can you mount? ls inside? Oct 23 13:38:28 @dohniks [Maybe boot to hybris recovery and then mount 21 and then rootfs.img], Can I do this in TWRP? Oct 23 13:38:56 Better hybris. Oct 23 13:39:15 We want to see whether your kernel can handle them Oct 23 13:39:43 There was some way to force hybris-boot into recovery ... Oct 23 13:40:01 Otherwise flash hybris-recovery Oct 23 13:40:13 Alright.. Oct 23 13:42:55 (Photo, 1280x719) https://irc.ubports.com/4k6x1dCd.png hybris-recovery just spammed my screen. Oct 23 13:43:02 @rixchy [], Can someone explain this log to me? It has no "booting linux" and it races from 0s to 12s without doing much ... it looks very very "unlinuxy" to me Oct 23 13:44:24 @rixchy [], Its normal that it shows you all partitions it can find, can be a lot. Also maybe your cable is faulty? Oct 23 13:44:45 No, it always does that when it is in kernel/hybris-recovery. Oct 23 13:44:51 I don't know why. Oct 23 13:51:55 @dohniks [Maybe boot to hybris recovery and then mount 21 and then rootfs.img], Alright, I got in telnet now. Oct 23 13:52:23 How do you mount userdata and rootfs in telnet? Oct 23 13:53:12 Can i somehow find which dtb is my phone using? Oct 23 13:53:33 somehow cmdline isnt respected Oct 23 13:53:41 and i want to append it in dtsi Oct 23 13:54:48 ok will try it in msm8916.dtsi Oct 23 13:58:55 @rixchy [How do you mount userdata and rootfs in telnet?], http://docs.halium.org/en/latest/porting/debug-build/logging-in.html#logging-in Oct 23 13:59:26 `mount /data` Oct 23 14:04:36 Thank you. Oct 23 14:05:25 ~ # mount /userdata … mount: can't find /userdata in /etc/fstab … ~ # mount /data … mount: can't find /data in /etc/fstab Oct 23 14:05:29 Uhm. Oct 23 14:06:25 That was the issue all along? Oct 23 14:06:42 No way that is an issue in mountpoints. Oct 23 14:06:46 mount /dev/mmcbla/blub /data Oct 23 14:07:01 ~ # mount /dev/mmcbla/blub /data … mount: mounting /dev/mmcbla/blub on /data failed: No such file or directory Oct 23 14:07:08