**** BEGIN LOGGING AT Fri Feb 23 03:00:01 2018 Feb 23 04:22:44 I'm trying to build ubports-boot, but I am stuck at this: https://hastebin.com/exodaligos.go Do I have to disable a config option to get it working? Feb 23 04:31:35 https://paste.kde.org/pqznq4iba … Anyone had this error? Feb 23 04:31:53 Basically, `bt_hci_bdroid.h` not found Feb 23 04:32:53 I'm sure it's flouride ( https://android.googlesource.com/platform/system/bt/+/android-7.1.1_r58 ) but I don't know where and how to put it Feb 23 04:36:55 https://github.com/LineageOS/android_system_bt .. I think you need to add this to repo manifest.. Feb 23 04:41:04 ah, thanks Feb 23 04:59:00 @bhushanshah do you know why that error is happening? I followed the kernel check that ubports provided Feb 23 04:59:01 https://hastebin.com/exodaligos.go Feb 23 05:01:49 um not really Feb 23 05:08:12 Oh, okay Feb 23 05:08:53 I didn't run into it when building halium, so I think it has something to do with the config changes in ubports Feb 23 08:47:29 @bshah, do you remember the udev rule to ignore mmcblk0 as removable device? Feb 23 08:47:38 I've seen something like this in PM, but can't find it now **** ENDING LOGGING AT Fri Feb 23 10:01:45 2018 **** BEGIN LOGGING AT Fri Feb 23 10:01:45 2018 **** ENDING LOGGING AT Fri Feb 23 10:01:49 2018 **** BEGIN LOGGING AT Fri Feb 23 10:05:07 2018 Feb 23 10:39:13 ChillarAnand was added by: ChillarAnand Feb 23 10:40:17 ``` Feb 23 10:40:46 [Edit] ```./halium/devices/setup athene … The given device is not supported. :(``` Feb 23 10:41:08 I am trying to build for athene and it fails at this step http://docs.halium.org/en/latest/porting/get-sources.html#sync Feb 23 10:42:28 Did you already create the manifest for your device? Feb 23 10:42:52 Make sure it's in the right place, then the script should find it Feb 23 10:44:04 http://docs.halium.org/en/latest/porting/get-sources.html#adding-your-device-specific-source Feb 23 10:52:25 Yes, there was confusion with the path. Moved xml to right place. Feb 23 12:01:27 At this step http://docs.halium.org/en/latest/porting/build-sources.html#for-halium-7-1, breakfast fails with `Trying dependencies-only mode on a non-existing device tree?`. Output: https://pastebin.com/raw/CRcn6mtJ Feb 23 12:04:29 It doesn't fail. That's just a regular warning. Your build is now configured and you only need to start it Feb 23 13:34:59 i must reinstall my system, is ubuntu 17.0.1 recommended ? Feb 23 13:35:30 [Edit] i must reinstall my system, is ubuntu 17.10.1 recommended ? Feb 23 13:44:00 For building Halium? Any recent debian or ubuntu based distro should work equally good Feb 23 13:49:26 Thanks @JBBgameich. Feb 23 13:49:28 `mka mkbootimg` fails with https://pastebin.com/raw/nH4MxzNB Feb 23 13:50:56 SettingsLib is a java library. You have to remove it from your device tree as Halium doesn't contain any java based code Feb 23 13:57:28 It was present in `./overlay/frameworks/base/packages/SettingsLib`. I deleted the folder and ran `mka mkbootimg` again. It is still throwing the same error. Feb 23 13:58:04 you need to remove it from a makefile in device/motorola/athene/ Feb 23 13:58:11 probably device.mk Feb 23 14:05:54 Do we need to regenerate any files? `grep -i settings device/motorola/athene/*.mk` returns empty Feb 23 14:07:02 Got it. Found it in cmactions. Feb 23 15:06:19 Yea the error said cmactioms line 37 Feb 23 15:14:06 `mka ubports-boot` failed with https://pastebin.com/raw/zE6i5DQV Feb 23 15:14:43 thats exactly the part of the log that doesn't contain the error 😆 Feb 23 15:14:51 Can you please paste the full log? Feb 23 15:16:15 Oh, full log https://pastebin.com/raw/dDu59izx Feb 23 15:16:50 First error looms like a ninja_wrapper error, second one looms like a kernel error Feb 23 15:19:28 Yea second is a msm8952 kernel error, fs I'm guessing is telling its a filesystem error, the ninja_wrapper error I don't know what causes that Feb 23 15:24:23 Any suggestions on how to fix it? Feb 23 15:26:31 Start with looking at the makefile on the line that the error shows, then work backwards till you find the error Feb 23 15:27:31 :13 means the makefile, line 13 Feb 23 15:28:48 ninja_wrapper not sure cause seems to randomly happen Feb 23 15:29:25 ninja_wrapper always fails if a subtarget (in this case the kernel) failed Feb 23 17:04:00 @JBBgameich, I've had a failure that was just ninja_wrapper before, I disable no ja and build finishes no issues Feb 23 17:05:51 @ChillarAnand, Any luck tracking down your error? Feb 23 19:30:56 @UniversalSuperBox considering the way initrd is built, is there a way to include resize2fs in halium-boot/ Feb 23 19:31:51 It isn't? Feb 23 19:32:11 Are you sure? Feb 23 19:32:47 https://github.com/Halium/initramfs-tools-halium/blob/halium/hooks/halium Feb 23 19:32:54 doesn't look like this Feb 23 19:33:03 Are you sure it isn't in busybox already? Feb 23 19:33:16 The halium script is written to resize /data if it's smaller than the physical partition Feb 23 19:33:44 Boot with `debug=top` and play with the shell Feb 23 19:33:48 no Feb 23 19:33:53 `break=top` Feb 23 19:54:00 what are the kernel config requirements for anbox? Feb 23 20:40:56 I checked initramfs Feb 23 20:41:00 no resize2fs inside Feb 23 20:41:21 so I guess there is the script, but not the tool yet Feb 23 20:49:06 I built initramfs from JBB's script and at the end of the operation, it was reported the following: `Calling hook klibc-utils … /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable … /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable … /usr/share/initramfs-tools/scripts/init-bottom/OR Feb 23 20:49:06 DER ignored: not executable … /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not executable … depmod: ERROR: Bad version passed touch-armhf … Building cpio /boot/initrd.img-touch-armhf.new initramfs` Feb 23 20:49:40 I think that this are normal errors. If there's something in the out folder, everything should be fine Feb 23 20:49:44 is it really an error? Feb 23 20:49:56 [Edit] I think that this are normal errors / warnings. If there's something in the out folder, everything should be fine Feb 23 20:50:24 It seems to: `guf@Guf-Book:/media/HALIUM/halium/initramfs-tools-halium$ ll out/initrd.img-touch-armhf … -rw-r--r— 1 root root 3985338 feb 23 21:44 out/initrd.img-touch-armhf … ` Feb 23 20:52:37 looks fine Feb 23 20:53:36 oki, thanks. I am trying to re-build halium-boot from scratch, since I couldn't find the issue that made my system loop at boot Feb 23 21:32:17 when in issue #55 it is said to remove `console=` form KERNEL_CMDLINE, is it meant both occurrencies? `BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_ Feb 23 21:32:17 uart,0x78B0000` in my case Feb 23 21:33:14 I mean `console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0` Feb 23 21:35:16 or only the first part (`console=ttyHSL0,115200,n8`) Feb 23 21:36:26 @stefanomelchior, remove all Feb 23 22:05:12 thnx Feb 24 00:28:50 @pablomancera, Thanks Pablo. My question was more about at what time and how to set the flags/options - when making the systemimageor hybris-boot? as part of a file? Thanks again Feb 24 02:14:36 You have to edit the file of you you device, that should be in arch/arm/configs/, that after launching lunch or breakfast, but I think following that order is not necessary Feb 24 02:15:38 Edit it using a normal text editor like emacs, vim or sublime text Feb 24 02:33:03 [Edit] You have to edit the file of you you device, that should be in BUILDLDDIR/kernel/arch/arm/configs/, that after launching lunch or breakfast, but I think following that order is not necessary **** ENDING LOGGING AT Sat Feb 24 03:00:00 2018