**** BEGIN LOGGING AT Sat Oct 26 02:59:57 2019 Oct 26 05:56:09 Isn't it regarding to loopback device support? Oct 26 05:57:13 config_blk_dev_loop Oct 26 07:57:16 Ok, will try that Akatsu. Oct 26 07:57:34 @Akatsu . [Isn't it regarding to loopback device support?], I guess so. Oct 26 07:59:46 @Akatsu . [config_blk_dev_loop], "CONFIG_BLK_DEV_LOOP=y … CONFIG_BLK_DEV_LOOP_MIN_COUNT=8" Oct 26 08:00:01 @Akatsu . [config_blk_dev_loop], [Edit] "CONFIG_BLK_DEV_LOOP=y … CONFIG_BLK_DEV_LOOP_MIN_COUNT=8" This is how it's in defconfig. Oct 26 08:00:36 @rixchy [Could this "kernel BUG at /home/rixchy_/halium/kernel/samsung/exynos5420/drivers …], And that line 205 in the loopback is: "BUG_ON(dev->ifindex != LOOPBACK_IFINDEX);" Oct 26 08:09:31 I dug around my defconfig and found this "# CONFIG_RC_LOOPBACK is not set" Oct 26 08:32:15 tomasz1486 was added by: tomasz1486 Oct 26 10:13:31 hey, guys. I have a android6 bsp. I copy vendor directory to halium source director /device. Oct 26 10:14:34 hey, guys. I have a android6 bsp. … 1: I copy vendor directory to halium source director /device. … 2: lunch and choose new target … 3: mka mkbootimg … then I got errors: … halium/hybris-boot/Android.mk:69: ********************* /boot appears to live on … halium/hybris-boot/Android.mk:70: ********************* /data appears to live on Oct 26 10:14:34 /dev/block/by-name/UDISK … halium/hybris-boot/Android.mk:73: *** There should be a one and only one device entry for HYBRIS_BOOT_PART and HYBRIS_DATA_PART. Stop. … make: Leaving directory '/root/halium' Oct 26 10:14:59 what should I do now. Oct 26 10:17:17 @gagamali [hey, guys. I have a android6 bsp. … 1: I copy vendor directory to halium source …], I think it's "mka hybris-boot" not "mka mkbootimg". Oct 26 10:17:32 IDK, maybe I am wrong, but I think it's "mka hybris-boot". Oct 26 10:18:05 thanks, let me try Oct 26 10:18:48 still same result. Oct 26 10:18:54 Hm. :/ Oct 26 10:19:23 @gagamali [hey, guys. I have a android6 bsp. … 1: I copy vendor directory to halium source …], Did you set up fixup-mountpoints? Oct 26 10:19:42 It appears that there are some parititon issues... Oct 26 10:19:54 I'm very new to Android, There is my first time to compile android related things. Are there any very basic doucument for me to build halium? Oct 26 10:20:05 Yeah!! Oct 26 10:20:21 http://docs.halium.org/en/latest/porting/first-steps.html Oct 26 10:20:24 Just google it. xD Oct 26 10:21:36 thanks. I read it many times. still in wondering. Oct 26 10:21:50 Did you follow exactly as it said in the guide? Oct 26 10:22:33 Yes, I need to take harder about it. Oct 26 10:22:41 Hm. Oct 26 10:23:20 @gagamali [hey, guys. I have a android6 bsp. … 1: I copy vendor directory to halium source …], So, I guess we understand that something somewhere is declaring HYBRIS_BOOT_PART and HYBRIS_DATA_PART twice... Oct 26 10:24:11 @gagamali [hey, guys. I have a android6 bsp. … 1: I copy vendor directory to halium source …], It is a common error, fix is shown in the docs. http://docs.halium.org/en/latest/porting/common-system-build-errors.html#hybris-boot-part-and-hybris-data-part Oct 26 10:24:19 Try that. Oct 26 10:26:02 Oh, thanks very much. Oct 26 10:26:17 Did that do the trick? Oct 26 10:28:28 not yet, trying to do Oct 26 10:28:37 Alright. Oct 26 10:30:30 by the way. How to know the version of halium. I don't remember which version I downloaded Oct 26 10:31:00 Hm, I don't know either.. let me check. Oct 26 10:33:41 (Photo, 498x197) https://irc.ubports.com/q9VWJMth.png wow, when i lunch again. I don't know what happened. list only one item left. Oct 26 10:34:05 Try "breakfast " Oct 26 10:34:19 Replace with your device's codename. Oct 26 10:35:25 breakfast works Oct 26 10:35:31 Yay. Oct 26 10:37:41 but i got same errors as before. let me google again😅 Oct 26 10:38:23 (Photo, 1175x733) https://irc.ubports.com/HWYCTByI.png Oct 26 10:38:39 You have halium-5.1 BTW. Oct 26 10:38:55 yes. i saw it Oct 26 10:39:05 @gagamali [yes. i saw it], Oh, I am glad. xD Oct 26 10:39:29 😁 Oct 26 10:39:30 @gagamali [], The same error... You sure ran in ~/halium direcotry "source build/envsetup.sh"? Oct 26 10:39:40 yes Oct 26 10:40:38 I'm sure Oct 26 10:40:58 Hm, pastebin fstab and fixup-mountpoints, please. Could you? Oct 26 10:41:15 I wanna make sure you set them up correctly. Oct 26 10:42:15 sorry, I can't understand your point clearly. May be I need to check google first. Oct 26 10:42:42 You go to pastebin.com, open fixup-mountpoints then paste in pastebin... Oct 26 10:43:02 And press button "create the paste" button on the bottom of the page and copy the URL. Oct 26 10:45:09 are there any document about mountpoints related to hybris? Oct 26 10:45:35 Yeah, you are supposed to setup mountpoints (in the docs). Oct 26 10:45:58 http://docs.halium.org/en/latest/porting/build-sources.html#include-your-device-in-fixup-mountpoints Oct 26 10:48:31 Sorry, my faulty. I forgot that because i can't understand it. Let me read this document once again. Oct 26 10:49:03 Sorry, my faulty. I forgot that because i couldn't understand it. Let me read this document once again. Oct 26 10:49:29 Oh, that's ok. Just read it more carefully, and I am sure you will understand that part! Oct 26 10:50:17 Thanks. Oct 26 10:52:20 NP. Oct 26 11:04:30 Thanks for you. Because fixed sound error Oct 26 11:04:41 No problem. Oct 26 11:47:27 https://medium.com/@quantvc/running-debian-on-android-device-natively-73545c9b0757 how dangerous is this Oct 26 12:43:00 Guys!! I just fixed rebooting issue on my device! Oct 26 12:43:15 Wi-fi works, vibrator works. Didn't check others yet. Graphics definitely don't work. Oct 26 12:43:47 AA "wlan0 wifi connected CENSORED" Oct 26 12:44:38 Tried testing Wi-Fi "root@localhost:~# ping 8.8.8.8 … socket: Permission denied" Vibrator works. Graphics don't work. Oct 26 12:46:48 rixchy: What was the issue with rebooting? Oct 26 12:47:04 There was a kernel bug in loopback.c line 205. Oct 26 12:47:16 "[ 12.944908] [B1: (ostnamed): 865] kernel BUG at /home/rixchy_/halium/kernel/samsung/exynos5420/drivers/net/loopback.c:205!" Oct 26 12:47:25 Removed that line, system booted up. Oct 26 12:47:34 Wifi partly works. Doesn't ping. Oct 26 12:47:38 Vibration works. Oct 26 12:47:45 Graphics on the other side, don't. Oct 26 13:01:03 @rixchy [Wifi partly works. Doesn't ping.], Wi-fi connects. Tried to ping, didn't work. "root@localhost:~# ping 8.8.8.8 … socket: Permission denied" Applied the patch, still the same.. Oct 26 13:02:03 Graphics give me this: "root@localhost:~# test_egl … library "libgui.so" wasn't loaded and RTLD_NOLOAD prevented it … cannot locate symbol "__popcountsi2" referenced by "/system/vendor/lib/egl/libGLES_mali.so"..." Oct 26 13:21:04 There are things not working. (Lights, Graphics, partly Wi-Fi) Could please someone check the logs? https://pastebin.com/QSsFrPQ6 Oct 26 14:39:13 I got SSH connectivity, and ran lxc-checkconfig. Oct 26 14:39:36 "CONFIG_PACKET_DIAG: missing … CONFIG_NETLINK_DIAG: missing … CONFIG_IP6_NF_TARGET_MASQUERADE: missing Oct 26 14:40:06 [Edit] "CONFIG_PACKET_DIAG: missing … CONFIG_NETLINK_DIAG: missing … CONFIG_IP6_NF_TARGET_MASQUERADE: missing CONFIG_NF_NAT_IPV4: missing … CONFIG_NF_NAT_IPV6: missing Vlan: missin Oct 26 14:40:06 g" Oct 26 14:42:00 Does anyone have any idea how to fix this? Oct 26 14:51:03 @rixchy [Graphics give me this: "root@localhost:~# test_egl … library "libgui.so" wasn't lo …], Test_egl is not so meaningful if used without HWCOMPOSER env variable. You find it in porting docs Oct 26 14:52:02 @Flohack [Test_egl is not so meaningful if used without HWCOMPOSER env variable. You find …], This patch? http://docs.halium.org/en/latest/porting/debug-build/graphics.html#test-hwcomposer-failure-on-aarch64-device-with-armhf-rootfs Oct 26 14:53:12 No, just the cmdline that you should use Oct 26 14:53:45 You meant this one: "EGL_PLATFORM=hwcomposer test_hwcomposer"? Oct 26 14:54:13 Well that returns nothing, nothing appears on the device, just a blinking cursor. Oct 26 14:57:31 @rixchy [You meant this one: "EGL_PLATFORM=hwcomposer test_hwcomposer"?], Thats the only one you will and should need yes ;) Oct 26 14:57:45 @Flohack [Thats the only one you will and should need yes ;)], Yeah but it returned nothing. Oct 26 14:57:51 Try to debug logcat Oct 26 14:57:58 Okay. Oct 26 14:58:00 @rixchy [Yeah but it returned nothing.], Porting is hard, yes. Oct 26 15:00:15 @Flohack [Try to debug logcat], logcat read failure Oct 26 15:49:39 @rixchy [logcat read failure], Is your container even running? Oct 26 15:49:45 @Flohack [Is your container even running?], LXC? Oct 26 15:49:47 whats lcx-info -n android Oct 26 15:49:56 @Flohack [whats lcx-info -n android], Hm, BRB. Oct 26 15:51:32 @Flohack [whats lcx-info -n android], -bash: lcx-info: command not found Oct 26 15:55:47 lxc-* Oct 26 15:55:50 some of those ^ Oct 26 15:55:53 lxc-status? Oct 26 15:55:58 Hm, let me see.. Oct 26 15:58:29 @Flohack [whats lcx-info -n android], Name: android … State: STOPPED Oct 26 15:58:46 @rixchy [Name: android … State: STOPPED], not good Oct 26 15:58:50 No wonder nothing works ^ Oct 26 15:58:55 you gotta fix that Oct 26 15:58:55 Haha. Oct 26 15:59:00 @Flohack [you gotta fix that], How? Oct 26 15:59:14 How can I know what to fix? Oct 26 16:22:58 @rixchy ["CONFIG_PACKET_DIAG: missing … CONFIG_NETLINK_DIAG: missing … CONFIG_IP6_NF_TARGET_M …], Does anyone have any idea how to fix atleast one of these? Oct 26 16:26:11 @rixchy [How can I know what to fix?], Well we all struggle with that. You can try to start the container manually and see any errors maybe Oct 26 16:26:17 lxc-start -n android Oct 26 16:26:36 @Flohack [lxc-start -n android], Does nothing. Oct 26 16:26:41 Blinking cursor in terminal. Oct 26 16:27:25 @Flohack [lxc-start -n android], "lxc-start: tools/lxc_start.c: main: 366 The container failed to start. … lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode. … lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options." Oct 26 16:30:21 Ok, I ran "lxc-start -n android -F" and it started spitting errors in the terminal window. Oct 26 16:31:21 yeah Oct 26 16:31:24 there you go Oct 26 16:32:44 At this point, IDK what to fix, how to fix. Google came up with almost no sources of the fixes. Oct 26 16:32:56 There are some threads and articles, but no valid answers. Oct 26 18:01:30 Device's rebooting again. Made changes to defconfig, changed back. Still rebooting. But log is different than last time, will post the log in a moment. Oct 26 18:01:56 https://pastebin.com/RMwvykeh Oct 26 18:02:20 If you don't know what caused the error, then send the line to me which you think caused the kernel panic. Thanks!~ Oct 26 18:54:48 You havent really removed bug, you have just made kernel ignore bug Oct 26 18:55:18 BUG_ON(dev->ifindex != LOOPBACK_IFINDEX); this BUG_ON kills process and print registers Oct 26 18:55:45 and it does it if ifindex!=LOOPBACK_IFINDEX Oct 26 18:57:33 you can always revert last commit and see if it changes anything Oct 26 19:00:12 LOOPBACK_IFINDEX is equal to 1 Oct 26 19:08:02 So, what do I do then? Oct 26 19:12:15 @rixchy [So, what do I do then?], Well we all are just explorers. Android is a big mess and not all phones can be ported. Those which can sometimes need months of hacking. I hope you got patience Oct 26 19:12:39 This is not done on a weekend ;) Oct 26 19:12:43 @Flohack [Well we all are just explorers. Android is a big mess and not all phones can be …], Well, alright. This makes me start over the whole port. xD Oct 26 19:13:10 Just one change.. to the defconfig.. and BOOM, system won't boot anymore. Oct 26 19:13:12 I started already 3 times on S3 Neo so yes ;) Oct 26 19:13:18 @Flohack [I started already 3 times on S3 Neo so yes ;)], Haha. Oct 26 19:14:09 But if the container cannot start its probably kernel config Oct 26 19:14:25 @Flohack [But if the container cannot start its probably kernel config], Defconfig? Oct 26 19:14:26 Lxc can be tricky Oct 26 19:14:39 @Flohack [Lxc can be tricky], Then that makes me sad. ;) Oct 26 19:14:57 Yes but once it runs its rock solid Oct 26 19:15:59 I think this everything is going on because this is a 3.4 kernel. Oct 26 19:19:05 @rixchy [I think this everything is going on because this is a 3.4 kernel.], No its because your vendor f*ed up the kernel Oct 26 19:19:29 If this would be vanilla kernel 3.4 it would work easily. Many other devices are.on 3.4 Oct 26 19:19:40 But noooo they need to.patch it Oct 26 19:19:48 THANKS SAMSUNG! 👍 Oct 26 19:19:49 Sometimes they just delete stuff from.it Oct 26 19:20:39 If you turn on feature flags that Samsung turned off you are likely to crash Oct 26 19:21:10 @Flohack [But noooo they need to.patch it], The same I think about download mode. Oct 26 19:21:10 Because they did not know what to do to fix the bug.other than turning off features until it works or so^^ Oct 26 19:21:21 That is lazy, I think. Oct 26 19:21:39 Well download mode is fine in general Oct 26 19:21:42 @rixchy [The same I think about download mode.], I mean, I hate download mode. I would like fastboot or sm like that. Oct 26 19:22:07 @Flohack [Well download mode is fine in general], Well, yeah. But for example, a little thing. What if you want to use "fastboot boot [image]"? Oct 26 19:22:43 The only different thing from fastboot is the fact, that it has a —repartition thing. Oct 26 19:22:56 But you need a .pit file for that. Oct 26 19:23:12 @rixchy [That is lazy, I think.], No, they are phone vendors and nit kernel hackers. Google throws new stuff into each release and they need to make it work with a hard deadline Oct 26 19:23:12 So they dont want to waste money and time on fixing kernel problems Oct 26 19:23:12 Heck some of them dont even know what a kernel is probably xd Oct 26 19:23:27 xD Oct 26 19:23:41 @rixchy [But you need a .pit file for that.], Dont do this during porting, it can break stuff easily :) Oct 26 19:23:48 Yeah, I know. Oct 26 19:24:05 I tried to install halium-boot, it was too big. So I tried to repartition, but it didn't work. Oct 26 19:24:40 Should I delete my defconfig and recover it or should I better delete the whole kernel folder and the defconfig? **** ENDING LOGGING AT Sun Oct 27 02:59:57 2019