**** BEGIN LOGGING AT Sun Oct 28 03:00:00 2018 Oct 28 08:23:35 I should have ask it here first does halum support miuze pro 5? Oct 28 08:23:39 *meizu Oct 28 09:27:16 These are the modules in my halium build. could one of them be wifi?root@localhost:~# ls /system/lib/modules/ … ansi_cprng.ko br_netfilter.ko qca_cld Oct 28 09:38:39 when i try to load qca_cld_wlan.ko module i get the error: invalid module format Oct 28 09:38:59 it is a precompiled module provided bu the vendor Oct 28 09:46:50 what could be wrong here? Oct 28 13:06:17 Hi there Oct 28 13:07:22 hello Tofe Oct 28 13:07:34 Maybe some of you know: on my Xiaomi A1 device, I have continuous crashes of qseeproxydaemon: 'CANNOT LINK EXECUTABLE "/system/vendor/bin/qseeproxydaemon": library "libandroid_runtime.so" not found' Oct 28 13:08:20 Should I try to bring libandroid_runtime.so in my halium image ? get rid of qseeproxydaemon ? Oct 28 13:10:10 umm I think we brought libandroid-runtime.so in build already Oct 28 13:10:23 ok, then I'll look in that direction Oct 28 13:11:33 this device is still WIP, so it could be something's wrong with the repos Oct 28 13:11:49 @mariogrip ping Oct 28 13:12:07 Did we ever commit patch to libandroid_runtime we discussed while ago? Oct 28 13:18:41 Neptvne was added by: Neptvne Oct 28 13:19:47 Hello have anyone tried building halim for Huawei p8 lite 2015 edition? Oct 28 13:23:24 bshah: libandroid_runtime seems to bring quite a bunch of stuff... Oct 28 13:23:39 yeah.. we had wip patch IIRC (me and @mariogrip) Oct 28 13:23:42 I can't seem to find it Oct 28 13:24:39 it brings libpdfium, libimg, harfbuzz_ng, etc Oct 28 14:08:45 I just gave up building libandroid_runtime; after bringing in all the necessary dependencies, it turns the source code itself for that module is broken... Oct 28 14:09:06 lol Oct 28 14:09:14 So if you find back that patch, I'm interested, otherwise I'll live without qseeproxydaemon :) Oct 28 14:09:53 for now you can disable qseeproxydaemon then Oct 28 14:10:19 yes, at least it won't spam my logcat :) Oct 28 15:00:25 ```systemd[1]: Failed to determine whether /sys is a mount point: Bad file descriptor … systemd[1]: Failed to determine whether /proc is a mount point: Bad file descriptor … systemd[1]: Failed to determine whether /dev is a mount point: Bad file descriptor … systemd[1]: Freezing execution``` … Systemmd refuses to start, anyone seen Oct 28 15:00:25 this? Oct 28 17:30:38 Hammerhead kernel have a backport for this I believe Oct 28 17:31:33 @minlexx, https://github.com/Halium/android_kernel_lge_hammerhead/commit/25437b2a54dd619a96e268ecaf303b089aa785e4 Oct 28 17:32:43 ( @minlexx sorry for ot, but is your t-shirt reference to kde2-under-freebsd joke?) Oct 28 17:33:34 @bhushanshah, yeah, it says "I patch KDE for FreeBSD" Oct 28 17:34:34 Haha Oct 28 17:36:01 @bhushanshah, I checked, I seem to already have this included - https://github.com/minlexx/android_kernel_samsung_msm8974/blob/halium-7.1/fs/proc/base.c#L1888 … Now I'm rebuilding systemd to try maybe add some debug prints here and there and see what's happening 😞 Oct 28 17:38:29 Weird... Uhm Oct 28 17:38:46 Your kernel is super strange Oct 28 17:38:49 😶 Oct 28 17:39:01 It worked other day, no? Oct 28 17:39:32 Or is it broken with bionic rootfs like this? Oct 28 17:39:48 I'm trying bionic rootfs Oct 28 17:40:17 Hm Oct 28 17:40:54 But xenial rootfs should've also failed similarly 😟 Oct 28 17:40:57 It boots with xenial rootfs, at least I always get ssh Oct 28 17:41:15 It was failing at first too, even with halium reference Oct 28 17:41:55 I think I fixed it by compiling kernel with selinux support (and disabling it via kernel command line) Oct 28 17:42:13 Do you have full dmesg of this one? From recovery? Oct 28 17:42:13 but that might not be what fixed it :D it's strange, yes Oct 28 17:48:35 https://paste.ubuntu.com/p/t8vsXZdfdK/ … It is not very helpful, systemd just dies and that causes kernel to panic … Not leaving any logs about why Oct 28 17:50:18 Can you in some way confirm that kernel you're building is indeed what you're booting? Because I am somehow finding this suspicious Oct 28 17:50:21 Also Oct 28 17:50:44 Your kernel seems to be having some more commits backported to that file Oct 28 17:50:52 Maybe something broke there Oct 28 17:50:53 Dunno Oct 28 17:52:00 @bhushanshah, (that file being fs/proc/base.c) Oct 28 17:53:29 I modified hybris-boot init-script to start systemd like this (instead of just /sbin/init): … ```exec switch_root /target "/lib/systemd/systemd --system --crash-reboot=no --dump-core=no --show-status=no --log-target=kmsg --log-level=debug --log-color=yes --log-location=yes" >> /target/data/systemd_logs 2>&1``` … and of course `/tar Oct 28 17:53:29 get/data/systemd_logs` does not appear because exec and switch_root replace current busybox image I guess and no shell script can be executed Oct 28 17:54:17 @minlexx, No, it's too late to sync logs to filesystem as kernel just panics :-( Oct 28 17:55:13 Can't you just hack something else in place of systemd mounts temporarily Oct 28 17:55:18 [Edit] Can't you just hack something else in place of systemd mounts temporarily? Oct 28 17:55:43 mount should be more verbose on what is happening than that crapware is Oct 28 17:56:05 But pseudofilesystems Oct 28 17:56:06 Hmm Oct 28 17:56:37 @minlexx, Try to boot hybris-recovery which provides you telnet, and check /proc/version Oct 28 17:58:23 I alway have telnet on boot because I have `/init_enter_debug` file in `/target` :) Oct 28 17:58:36 Right. Oct 28 17:58:39 `Linux version 3.4.113-halium-gbfcc9e6 (halium_dev@55f3e6c98101) (gcc version 4.9 20150123 (prerelease) (GCC) ) #5 SMP PREEMPT Sun Oct 28 16:35:09 UTC 2018` Oct 28 17:59:06 Which sounds good. Oct 28 17:59:08 Okay Oct 28 17:59:09 built roughly half an hour ago Oct 28 17:59:14 Yeah right Oct 28 17:59:30 [Edit] I always have telnet on boot because I have `/init_enter_debug` file in `/target` :) Oct 28 18:00:08 those messages about `/sys` and `/proc` I get when I also place `/init-debug` in `/target` Oct 28 18:00:22 and it gets started instead of systemd Oct 28 18:00:54 and then I do `echo "exec /lib/systemd/systemd ...." > /init-ctl/stdin` Oct 28 18:01:22 I see that systemd becomes PID 1 and can look into dmesg Oct 28 18:01:48 [Edit] and it gets started instead of systemd after chroot into `/target` Oct 28 18:02:26 at that moment `/sys /dev` and `/proc` are mounted by init script, yes Oct 28 18:03:20 As they should be yes Oct 28 18:09:32 Well, I rebuilt systemd with some custom printf and this inded seems to be a problem...) https://paste.ubuntu.com/p/pJVCYv2jSs/ Oct 28 18:10:22 [Edit] Well, I rebuilt systemd with some custom printf and this inded seems to be a problem...) https://paste.ubuntu.com/p/pJVCYv2jSs/ … ¯\_(ツ)_/¯ Oct 28 18:12:19 I probably can just comment out those checks on pseudo fs' from systemd code 😂 **** ENDING LOGGING AT Mon Oct 29 03:00:00 2018