**** BEGIN LOGGING AT Tue Oct 30 02:59:59 2018 Oct 30 04:14:09 @UniversalSuperBox, Sounds good to me **** BEGIN LOGGING AT Tue Oct 30 06:24:04 2018 **** BEGIN LOGGING AT Tue Oct 30 06:51:22 2018 **** BEGIN LOGGING AT Tue Oct 30 08:35:23 2018 Oct 30 18:37:26 Could someone have a look at https://github.com/Halium/halium-devices/pull/124 and eventually merge it if there's no obvious problem? Oct 30 18:38:24 it's just a change of source trees, which now work better Oct 30 18:56:33 bshah: ^ Oct 30 19:50:23 dtkid was added by: dtkid Oct 30 22:33:41 @minlexx are you having issues with systemd on the samsung klte? I think I have the same problem, I tried various rootfs but without success, it always reboot after the switch_root Oct 30 22:34:19 drebrez: yes, old kernel requires older systemd Oct 30 22:34:46 That's the conclusion I came to today Oct 30 22:35:13 This is a problem (no solution there) - https://forum.armbian.com/topic/4710-systemd-failed-to-boot-bad-file-descriptor/ Oct 30 22:35:32 https://archlinuxarm.org/forum/viewtopic.php?f=47&t=9225 this gives some thoughts about incompatibility Oct 30 22:40:28 @bshah do you still have some halium reference rootfs with older systemd? Oct 30 22:41:21 @minlexx how old should be? I see bshah's rootfs is halium-rootfs-20170630-151006.tar.gz Oct 30 22:42:28 2nd link suggests systemd-221 Oct 30 22:42:50 xenial had 229 I think... Oct 30 22:43:24 But it worked with hammerhead 😐 Oct 30 22:43:32 Same 3.4 kernel Oct 30 22:47:33 @minlexx is this related maybe? https://github.com/dan-and/linux-sunxi/issues/3 Oct 30 22:49:12 wasn't complaining about that mount (`/sys/fs/cgroup/systemd`) Oct 30 22:49:52 Oh oh Oct 30 22:52:09 While ago, in the hybris-boot there was this mkdir call Oct 30 23:03:18 Can someone download https://images.plasma-mobile.org/halium/hammerhead/20170623-085147/boot.img and extract init script and pastebin it please? Oct 30 23:03:24 I'm on mobile Oct 30 23:05:40 https://pastebin.com/DfF9gEZF Oct 30 23:10:27 L288 Oct 30 23:11:35 Can you try to add it to your hybris-boot and see if it helps Oct 30 23:22:02 I can try it tomorrow (after 7pm utc) **** ENDING LOGGING AT Wed Oct 31 02:59:58 2018