**** BEGIN LOGGING AT Fri Mar 22 02:59:57 2019 Mar 22 04:13:56 Oh I guess it's not logging anything to the device cause its not mounting anything at this point Mar 22 07:08:56 Enes was added by: Enes Mar 22 08:14:43 @powderedtoastman9000, Can you try the /proc/last_kmsg in recovery? Or the alternate one probably for newer kernels. It should give you some message toi where the boot has come Mar 22 12:35:17 @powderedtoastman9000, boot to recovery and see in data folder there is any folder named system-*, if rootfs well mounted you can see log in system-*/var/log Mar 22 13:09:11 Hi everyone I'm trying to build an halium-boot.img anyone knows what shuold be the value of CONFIG_INITRAMFS_SOURCE="" ? Mar 22 13:11:24 Is it mandatory th have a succesful build ? Mar 22 16:51:54 What version of Ubuntu should I use to get rootfs-builder to work? I tried 16.04 and 18.10, and I remember reading not all Ubuntu versions have a compatible version of packages Mar 22 16:52:07 Why are you using rootfs-builder? Mar 22 16:53:24 @UniversalSuperBox trying to get an aarch64 rootfs Mar 22 16:54:00 As much as I hate to say it, an arm64 rootfs won't help you much Mar 22 16:54:34 I'd suggest running armhf until your port is working with that, then try to help resolve the problems everyone has with arm64 Mar 22 16:55:03 I read the last person to worked on s7 said they thought it might be related to their problems Mar 22 16:55:15 Like Mar 22 16:56:03 Something about lack of hardware support, not an issue I'm dealing with yet, I'll take your advice and use 32 bit Mar 22 17:40:03 By the way the reference rootfs does not much on my arm64 device except not properly starting the container and throwing floating point errors all over the place. **** ENDING LOGGING AT Sat Mar 23 03:00:16 2019