**** BEGIN LOGGING AT Sat Mar 31 03:00:02 2018 **** BEGIN LOGGING AT Sat Mar 31 06:47:32 2018 Mar 31 09:59:32 it's the first time halium-7 and UT xenial sudoku work, its boot slowly but goot at all Mar 31 10:00:06 @UniversalSuperBox for halium-7 any UT rootfs should work, or only sudoku ? Mar 31 12:26:42 @JBBgameich for halium-7 , how can i build UT recovery image ? Mar 31 12:28:14 Afaik nobody did it yet. .. but you could try applying the UBports patches from android_bootable_recovery to the version in the Halium tree. Mar 31 12:33:00 ok, i installed UT xenial sudoku(r45) with halium-7, i check for update (r46), system download it and asking for reboot to recovery Mar 31 15:15:17 @UniversalSuperBox, tellnet works when I use break=top but with this IP Mar 31 15:15:23 https://github.com/mer-hybris/hybris-boot Mar 31 15:15:30 Yep, it does that Mar 31 15:15:42 telnet 192.168.2.15 Mar 31 15:15:53 But why are you stopping boot now? Mar 31 15:17:12 because of loopboot Mar 31 15:17:31 How long after it boots? Mar 31 15:18:01 7 seconds I guess Mar 31 15:18:20 or less hahahah Mar 31 15:18:35 Okay, what kernel version do you have Mar 31 15:18:44 3.4 Mar 31 15:18:48 3.4.0 Mar 31 15:19:04 Let it reboot, boot it to recovery, and take the log from `/proc/last_kmsg` Mar 31 15:20:20 wow nice tip Mar 31 15:20:22 thanks Mar 31 15:21:02 It's in the docs since twenty minutes ago too. http://docs.halium.org/en/latest/porting/debug-build/early-init.html Mar 31 15:21:11 Thanks kllp, wherever you are Mar 31 15:27:10 @UniversalSuperBox for halium-7 any UT rootfs should work, or only sudoku ? Mar 31 15:27:24 Depends. Is your device CAF or not Mar 31 15:53:46 wow thanks @UniversalSuperBox "wcnss_8960: crash shutdown : 0" Mar 31 15:53:53 do you have any idea? Mar 31 15:57:40 I think it's related to wifi Mar 31 16:00:55 @Ismaelbonato, i don't think this is the error, this message is generated when kernel crash, but not sure is wifi issue Mar 31 16:16:35 https://pastebin.com/MRAdS8Q8 Mar 31 16:19:23 [ 4.876098 / 03-31 15:18:41.332] initrd: mounting /root/var/lib/lxc/android/system.img as /root/android/system … [ 4.963500 / 03-31 15:18:41.422] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 Mar 31 16:25:31 @Ismaelbonato, your data partition is ext4 ? also check your fstab remove inline_xattr options Mar 31 16:31:04 (Photo, 1280x253) https://irc.ubports.com/RsroI82p.png I need to remove that option? Mar 31 16:31:10 (Photo, 1280x253) https://irc.ubports.com/Zfovv4V0.png do I need to remove that option? Mar 31 16:34:05 try , remove it and see if it work, also data partition must ext4 Mar 31 16:34:32 [ 4.690673 / 03-31 15:18:41.141] EXT4-fs (mmcblk0p24): Unrecognized mount option "inline_xattr" or missing value Mar 31 16:34:38 this error from your log Mar 31 16:34:50 I need to update the docs to use halium-boot ASAP Mar 31 16:35:04 ubports-boot needs to die Mar 31 16:36:15 @Ismaelbonato, why you two data partition mount Mar 31 16:36:23 (Sticker, 512x512) https://irc.ubports.com/nvmzXqYc.webp Mar 31 16:36:47 @Walid, It's like that whe I see firt time Mar 31 16:37:12 do you think I can delete this duplicated lines? Mar 31 16:38:31 yes remove the first line and see if it work Mar 31 16:38:31 [Edit] do you think I can delete these duplicated lines? Mar 31 16:39:14 cache is also duplicate can I delete the first line? Mar 31 16:39:26 first one or second one? Mar 31 16:40:02 remove first andd Mar 31 16:40:09 thanks Mar 31 17:35:40 https://pastebin.com/YxFpfZb4 Mar 31 17:35:47 no lucky! the same problem Mar 31 17:36:41 " (mmcblk0p24): Unrecognized mount option "inline_xattr" or missing value" I think this problem is not related to /userdata because data is 36 Mar 31 17:41:26 anyway I think it's related to CONFIG_PID_NS! Mar 31 18:10:56 I create an issue on halium github Mar 31 18:11:00 https://github.com/Halium/projectmanagement/issues/70 Mar 31 18:11:50 what's the best place to put my kernel repository? Mar 31 18:18:37 Just use github's fork button on LineageOS' kernel repository Mar 31 18:20:16 like that? https://github.com/ismaelbonato/android_kernel_lge_v500 Mar 31 18:20:35 ow my face sorry! Mar 31 18:40:50 Looks fine. Now create a new halium-7.1 branch using git and commit your defconfig changes Mar 31 20:29:18 https://github.com/ismaelbonato/android_kernel_lge_v500/tree/halium-7.1 Mar 31 20:29:24 Done! :) Mar 31 20:31:47 Cool! About the halium-devices PR, how is the codename of your device? Mar 31 20:31:55 [Edit] Cool! About the halium-devices PR: how is the codename of your device? Mar 31 20:36:01 V500? Mar 31 20:36:40 okay. Mar 31 20:37:27 please name the manifest lge_v500.xml then Mar 31 20:41:16 there is some confusion from me, because device/lge/gpad83-common was the first repo that I have added on this manifest for the sake of that I named this manifest like that! Mar 31 20:42:19 the manifest should be called like the device codename, so `./halium/devices/setup $codename` finds it Mar 31 20:43:03 @JBBgameich, Done Mar 31 20:43:08 Thank you Mar 31 20:44:18 You might also want to switch it to your own kernel repository. Mar 31 20:45:05 I already did it! I changed on .git/config Mar 31 20:45:18 I was talking about the manifest Mar 31 20:45:22 OK Mar 31 20:48:55 one question! Do I need only fork kernel or can I fort device from lineageOS repo? Mar 31 20:49:45 Forking the device repository as well does probably make sense, because it's likely that you will have to do changes there later too. Mar 31 20:52:35 I forked all repositories heheheh Mar 31 20:52:49 vendor is not neccesary, and I don't recommend forking it Mar 31 20:53:37 The vendor binaries are proprietary and it's not clear whether it's allowed to host them or not. That's the reason why LineageOS uses the TheMuppets org instead of their own. Mar 31 20:58:17 and now what do you think? Mar 31 21:00:24 One more thing: you could also create a halium-7.1 branch on the device tree repository, so you don't need to change the manifest later when you change something on the device tree. Mar 31 21:00:40 That would also remove the need for the revision override Mar 31 21:00:46 OK Mar 31 21:00:55 After that I can merge it :) Mar 31 21:01:39 but I have two devices repository maybe I do it in both of them Mar 31 21:01:54 Okay, makes sense Mar 31 21:04:40 it's ease from github I don't need to clone and etc.. hahhaah Mar 31 21:05:35 [Edit] it's pretty easy from github I don't need to clone and etc.. hahhaah Mar 31 21:08:33 done! Mar 31 21:09:38 One more question: Is this neccesary? https://github.com/Halium/halium-devices/pull/81/commits/fc1c84169d3c6e97decd1acd749dd33cb737d3ab#diff-5891d0b0327614d6604e8c0e4908b569R11 Mar 31 21:09:54 I thought cm-14.1 is already the default for the them remote? Mar 31 21:10:56 I don't know if you want I can delete this revision Mar 31 21:11:21 I'll test it locally, I'll delete it if it's not neccesary. Mar 31 21:11:50 OK perfect Mar 31 21:15:46 tell me if it works :) Mar 31 21:16:10 I'll do. My connection is just not very fast, so downloading the repository takes time ... Mar 31 21:17:10 don't worry! You need to enjoy the easter. take time to it hahahah Mar 31 22:59:32 using recovery and adb shell I can't find this img /root/var/lib/lxc/android/system.img but I can find it in ./data/system.img Mar 31 22:59:45 -rw-rw-rw- 2 root root 2.0G Mar 31 16:54 ./data/system.img Mar 31 22:59:50 it's normal? Mar 31 23:01:15 [Edit] is it normal? Mar 31 23:01:41 and in the same folder -rw-rw-rw- 2 root root 2.0G Mar 31 16:54 ubuntu.img **** ENDING LOGGING AT Sun Apr 01 03:00:01 2018