**** BEGIN LOGGING AT Thu May 27 02:59:56 2021 May 27 04:50:34 @just_carlod [https://github.com/ubports/porting-notes/wiki/GitLab-CI-builds-for-devices-based …], How to setup this May 27 05:36:01 paezl467 was added by: paezl467 May 27 06:25:57 The question is how do you build this with gitlab runner without issues. Such as tmp/tmp no file or directory? Or maybe there's something wrong with the .yaml or build sh? May 27 06:25:57 Fwd from just_carlod: https://github.com/ubports/porting-notes/wiki/GitLab-CI-builds-for-devices-based-on-halium_arm64-(Halium-9) May 27 06:48:03 (Photo, 1280x224) https://irc.ubports.com/YlsuEXlf.png first step, i will clone beryllium and adapt it to my device, correct? May 27 06:50:58 Yes May 27 06:51:11 then edit device info May 27 06:51:23 Yes May 27 06:51:33 then what's the command to use to build May 27 06:52:05 Hang on, theres more place you need to add your device May 27 06:52:28 oh okay May 27 06:53:30 Then from there I anyway made a repository on git lab May 27 06:55:23 And then tried to build it there but I keep failing so someone else may know what there talking about May 27 06:57:43 (Photo, 1280x949) https://irc.ubports.com/ZGIy3v1j.png there are some beryllium mentioned in yml as well; so i'm not sure where to edit May 27 07:03:13 Yes just change that to your device codename? May 27 07:05:19 The I don't know, I cd to the folder and ran ./build sh May 27 07:05:32 okay then where to read the log May 27 07:05:36 when it fail May 27 07:05:39 Built fine but on gitlab failed May 27 07:06:27 It will show you while when it stops building, gitlab has a note after it fails May 27 07:07:12 okay May 27 07:07:16 i'll try thank u May 27 07:17:04 @Ryan Maldonado [Built fine but on gitlab failed], First Fork berrylium repo May 27 07:17:08 @Ryan Maldonado [Built fine but on gitlab failed], [Edit] First Fork berrylium repo? May 27 07:18:25 (Photo, 1280x106) https://irc.ubports.com/hg6CSE6I.png wat to edit in this part May 27 07:21:06 I added my cmdline May 27 07:21:40 You have this kernel running on your phone? May 27 07:21:48 yes i have port kernel running May 27 07:21:56 how to get this info May 27 07:23:03 There's a few ways to get it but you can run dmesg and it should show somewhere at the top of the log May 27 07:23:34 okay May 27 08:20:43 (Photo, 1280x115) https://irc.ubports.com/tePMaCYj.png shall i copy the whole thing there or some part we don't need May 27 08:21:45 Whole thing May 27 08:31:29 how to run in gitlab, sorry, first time using gitlab May 27 08:31:50 @Ryan Maldonado [There's a few ways to get it but you can run dmesg and it should show somewhere …], Flash halium-boot and take it's cmdline ? cat /proc/cmdline ?? May 27 08:39:21 @pagnchanak [], no, it's better to extract cmdline from existing image May 27 08:39:36 @NotKit [no, it's better to extract cmdline from existing image], how to do that May 27 08:39:36 the parts in resulting cmdline come from bootloader May 27 08:39:54 any command can be done via adb shell in twrp May 27 08:40:35 run lineage-17/system/core/mkbootimg/unpack_bootimg.py --boot_img boot.img on PC May 27 08:40:49 (you probably need to download that script separately) May 27 08:41:11 ok May 27 08:59:13 @NotKit , btw the process is correct? fork beryllium, edit deviceinfo and run build.sh? May 27 08:59:15 that's it? May 27 08:59:37 or are there other files to edit before running build May 27 09:32:01 dima19051997 was added by: dima19051997 May 27 09:32:19 @pagnchanak [@NotKit , btw the process is correct? fork beryllium, edit deviceinfo and run bu …], yep, let me commit some changes May 27 09:42:48 (Photo, 1280x418) https://irc.ubports.com/8QaLJNOo.png May 27 09:43:09 could you give the link to full log? May 27 09:43:21 doesn't show the actual error May 27 09:44:31 https://gitlab.com/xperseus/xiaomi-beryllium/-/commit/b39f3c6c641f5487cf25396e8e9653fd161b65c5 May 27 09:45:11 sorry trying to find link to full log May 27 09:45:11 lolz May 27 09:45:15 i'm dumb May 27 09:45:49 https://gitlab.com/xperseus/xiaomi-beryllium/-/jobs/1297715683 May 27 09:47:21 which toolchain did you use to compile kernel manually? May 27 09:48:38 (Photo, 1280x428) https://irc.ubports.com/kzQWHLux.png so the error is here May 27 09:49:16 @NotKit [which toolchain did you use to compile kernel manually?], https://github.com/ubports/porting-notes/wiki/Halium-9 May 27 09:51:49 ok i think i understand the message, will fix indentation May 27 09:54:39 you probably need to use clang-4691093 like https://gitlab.com/ubports/community-ports/android9/motorola-sdm660/motorola-lake/-/blob/master/build.sh#L48 here, but let me try locally first May 27 09:56:29 okay.. i flag clang=true in deviceinfo as check BoardConfigCommon.mk is required May 27 10:12:14 @pagnchanak seems to build with clang-4691093 for me, apply those lines then May 27 10:12:29 @NotKit [@pagnchanak seems to build with clang-4691093 for me, apply those lines then], yes, already did, running now May 27 10:17:16 @NotKit [@pagnchanak seems to build with clang-4691093 for me, apply those lines then], thank u, passing that error now May 27 11:00:34 @NotKit , build succeed on gitlab, so i need to build it locally? May 27 11:01:10 you can download the artifacts May 27 11:01:30 rebase on latest beryllium repo, that has devel-flashable job May 27 11:01:58 then you should get boot.img and system.img that can be fastboot flashed May 27 11:02:33 okay let me try, dun understand much, i'm so illiterate May 27 11:03:18 (Photo, 462x290) https://irc.ubports.com/tvvBbzpr.png run flashable, is it correct? May 27 11:05:13 (Photo, 1280x397) https://irc.ubports.com/x0Lwk70w.png what??? 1.56MB? May 27 11:06:20 @NotKit [rebase on latest beryllium repo, that has devel-flashable job], pls explain me more.. May 27 11:06:42 no, flashable won't work until device is added to OTA server May 27 11:08:12 where is devel-flashable May 27 11:09:24 https://gitlab.com/ubports/community-ports/android9/xiaomi-poco-f1/xiaomi-beryllium/-/commit/eb4f62a408120053e4008611f49cfa829ad7b242 - cherry-pick this commit May 27 11:16:52 y i dont have this commit in my fork git May 27 12:14:03 pls help check my error: … https://gitlab.com/xperseus/xiaomi-beryllium/-/jobs/1298137276 May 27 12:14:10 [Edit] pls help check my error: @NotKit … https://gitlab.com/xperseus/xiaomi-beryllium/-/jobs/1298137276 May 27 12:19:38 forgot to +x .sh May 27 12:20:00 so the build.sh will have to re-run every commit? 🙁 May 27 12:57:15 @pagnchanak [so the build.sh will have to re-run every commit? 🙁], yes, but there are easier way to test smaller changes if you do not need to rebuild kernel May 27 13:02:41 (Photo, 766x586) https://irc.ubports.com/xOe7kYxX.png i have build locally as wanting to test fast, gitlab taking too long, what images to flash? May 27 13:04:24 @NotKit May 27 13:04:52 how large is system.img? May 27 13:05:07 try to flash boot.img + system.img May 27 13:05:33 and remove rootfs.img/android-rootfs.img from data partition if they are still there May 27 13:05:53 2.4GB for system May 27 13:05:57 3.1 for rootfs May 27 13:06:07 so i need to flash boot.img, system.img and vbmeta.img? May 27 13:06:28 ignore vbmeta for the moment, try boot and system May 27 13:06:33 okay May 27 13:06:35 got it May 27 13:07:38 btw, you do not seem to have systempart=... in kernel cmdline yet (deviceinfo_kernel_cmdline) May 27 13:08:06 if you did not add that, ignore what I said about flashing system.img, but instead mv rootfs.img ubuntu.img and push ubuntu.img to /data May 27 13:10:26 G May 27 13:18:03 oh May 27 13:18:40 but i can also flash rootfs.img to system instead of data? May 27 13:18:56 if system size fits May 27 13:19:35 btw, for my kernel, i need to use this patch to boot, will it still apply? … If device crashed to "Failed to boot" on networks, flash Halium-boot_no_console_patch May 27 13:20:51 @pagnchanak [btw, for my kernel, i need to use this patch to boot, will it still apply? … If d …], probably yes, but the usual solution without patch is to add console=tty0 to cmdline May 27 13:21:24 @pagnchanak [but i can also flash rootfs.img to system instead of data?], right, that's what generated system.img for, but booting from system partition requires systempart=/dev/disk/by-partlabel/system in kernel cmdline May 27 13:21:39 okay May 27 13:22:03 can u check anything else i need to add in cmdline? May 27 13:23:21 pls help check in this link instead: … https://gitlab.com/xperseus1/xiaomi-beryllium/-/blob/master/deviceinfo May 27 13:28:50 do i need all of these? or only systempart? … systempart=/dev/disk/by-partlabel/system … selinux=0 … apparmor=1 … security=apparmor May 27 13:44:41 @NotKit how to fix invalid sparse, can we add sth to the script? May 27 13:45:14 what file is invalid sparse? May 27 13:45:19 rootfs May 27 13:45:25 or system will be fine? May 27 13:45:27 use system.img May 27 13:45:32 it's converted from rootfs May 27 13:45:40 oh okay, i will use system after fix systempart May 27 13:45:48 @pagnchanak [do i need all of these? or only systempart? … systempart=/dev/disk/by-partlabel/sy …], how abt this @NotKit May 27 13:46:07 @pagnchanak [do i need all of these? or only systempart? … systempart=/dev/disk/by-partlabel/sy …], I think only systempart if you enabled AppArmor by default already May 27 13:47:31 alright i'll fix it and let it build on CI May 27 13:47:56 btw boot.img and rootfs.img to userdata, bootlooping now May 27 14:00:36 name rootfs.img as ubuntu.img May 27 14:00:39 no USB network? May 27 14:14:18 @NotKit [name rootfs.img as ubuntu.img], Oh u meant push May 27 14:14:23 I flashed May 27 14:14:26 Duh… May 27 14:14:45 Will try again May 27 15:08:09 @NotKit so I have forked beryllium, modified deviceinfo, add systempart, and modified clang, everything built successfully on CI, I got two img artifacts, boot and system, flashed them, and end up in bootloop, MI logo flashes again and again nonstop. What could have been wrong? … Devel-flashable log: … https://gitlab.com/xperseus1/xiao May 27 15:08:10 mi-beryllium/-/jobs/1298636346 May 27 15:10:28 could you send previous boot.img that booted to compare? May 27 15:12:28 Okay can I send here? May 27 15:13:17 yes May 27 15:17:06 i have to flash no console patch on top of this boot img. May 27 15:17:09 (Document) https://irc.ubports.com/knCL6E4e.null May 27 15:26:50 @pagnchanak [], Source: https://github.com/pagnchanak/android_kernel_xiaomi_sdm845/tree/halium-9.0 May 27 15:27:01 If that helps May 27 15:31:20 I don't see anything obviously different regarding image structure May 27 15:32:05 😖 May 27 15:32:53 Could be rootfs issue? I flash old boot with new system, also not booting, but usb work May 27 15:33:50 halium-boot should create USB network and expose telnet interface if rootfs is missing May 27 15:34:35 So what to do now? I really want to add my device to ota May 27 15:39:31 let's try to reduce the scope of what exactly could be wrong May 27 15:40:14 if it works, it should stop with "Failed to boot" and telnet network on USB May 27 15:40:27 (Document) https://irc.ubports.com/XRLgX04B.null May 27 15:40:54 Okay May 27 15:41:41 @NotKit [], so i'll flash this with the new system right? May 27 15:41:53 doesn't matter about system, just flash boot May 27 15:41:57 ok May 27 15:43:14 flashed now May 27 15:43:17 usb working May 27 15:43:20 what's next May 27 15:44:54 @NotKit May 27 15:45:15 (Document) https://irc.ubports.com/xdR2fgwI.null May 27 15:47:56 @NotKit [], not working, boot loop May 27 15:50:23 ok, so something is different either with kernel or dtb May 27 15:50:59 (Document) https://irc.ubports.com/f0gmbBXN.null May 27 15:53:01 @NotKit [], booting into system now May 27 15:53:15 so problem is kernel, then my source could be the problem? May 27 15:55:12 either source (but it's same as the previous build, right?) or there is some magic with appended DTB we do wrong May 27 15:56:27 i will push my local source into new git, and try to rebuild boot; as my working boot i built locally, but then i redo it on forked kernel to keep track of my commit, so i might did sth wrong May 27 15:58:30 then we will know May 27 16:51:48 Hi All, May 27 16:52:29 after installing anbox my screen went black and cant boot to the system May 27 16:52:51 also I've tried to connect through adb/flashboot in the bootloader and the device is not being recognized May 27 16:52:56 any hint? May 27 17:08:35 if I start my phone normally I get the black screen but I can still ssh it May 27 17:15:37 @Cochi1984 [after installing anbox my screen went black and cant boot to the system], same for me May 27 17:17:17 can you access to the bootloader? May 27 17:17:27 are you able to perform an ADB devices? May 27 17:18:32 I wish to reinstall everything from scratch but since I dont see the device from the cmputer I cannot boot to twrp May 27 17:21:15 I believe that something of what we have done to install anbox ruinned the adb access May 27 17:23:37 I'll try to uninstall anbox and reboot May 27 17:24:24 on GSI, anbox didn't work for me.. but on CI it is working May 27 17:24:58 the problem is that I cannot reinstall things since I dont have access to adb anymore May 27 17:25:05 dky May 27 17:39:12 actually fastboot recognizes my device but does not allow me to boot into twrp img May 27 17:41:46 there we go! May 27 17:42:46 hı. how fix this error? https://paste.ubuntu.com/p/vTvDFM2dd2/ May 27 17:44:30 char ctx[crypto_shash_descsize(apparmor_tfm)]; seems that the value inside of [] should be a constant maybe assign that to a contant variable and call that inside of the [] May 27 17:45:09 @ankaos [hı. how fix this error? https://paste.ubuntu.com/p/vTvDFM2dd2/], https://github.com/moto-SDM660/android_kernel_motorola_sdm660/commit/23181296d539d9bfd66ae68571c2905d0b977287#diff-acbef244e74545d425e4b1804a0a1fa23f05200496ecea102534557150ece659 … follow this commit, will fix this issue May 27 17:46:49 @ankaos [hı. how fix this error? https://paste.ubuntu.com/p/vTvDFM2dd2/], highly likely u might face issue with file domain.c as well; mine these two issues came together, in that case, follow this commit: … https://github.com/moto-SDM660/android_kernel_motorola_sdm660/commit/db25fd660a86ee05e78a4f7ff8a2136b1e90bf22#diff-acbef244e74545 May 27 17:46:49 d425e4b1804a0a1fa23f05200496ecea102534557150ece659 May 27 17:53:08 @pagnchanak [highly likely u might face issue with file domain.c as well; mine these two issu …], ı rebuild :). ı am waiting May 27 17:54:05 @ankaos [ı rebuild :). ı am waiting], u will pass it, but will face other errors (highly likely) lolz May 27 17:55:56 @NotKit [either source (but it's same as the previous build, right?) or there is some mag …], confirm the issue was due to my kernel source. after using proper kernel source (which i used to build my working boot), now boot normal after build in CI and flash system and boot... so next step, need to fix errors. one thing notice rightawa May 27 17:55:56 y in GSI my display brightness works normally, now brightness at maximum and cannot control. May 27 17:58:35 @pagnchanak [confirm the issue was due to my kernel source. after using proper kernel source …], dmesg for your reference: https://paste.ubuntu.com/p/VjgsxzHdNm/ May 27 18:09:18 @pagnchanak [confirm the issue was due to my kernel source. after using proper kernel source …], see xiaomi-willow repo May 27 18:09:31 I commited a config for that May 27 18:12:15 @NotKit [I commited a config for that], okay will go through May 27 18:17:19 btw @NotKit , can i request to add device to ubports, what's the criteria... May 27 18:38:54 @pagnchanak [u will pass it, but will face other errors (highly likely) lolz], https://paste.ubuntu.com/p/6PddCWy9qF/ how fix? May 27 18:39:02 halium-boot build :) May 27 18:39:37 @ankaos [https://paste.ubuntu.com/p/6PddCWy9qF/ how fix?], u will need to search, i haven't faced this one May 27 18:39:53 @pagnchanak [u will need to search, i haven't faced this one], ı dont found answer :( May 27 18:44:57 @pagnchanak [btw @NotKit , can i request to add device to ubports, what's the criteria...], I don't think there is a particular criteria, but adding device to system-image.ubports.com requires some manual intervention from either Dalton or Florian May 27 18:47:28 can merge my repo to community ports? May 27 18:50:28 yes, I will create those May 27 18:51:15 (@ubports_porting is probably more relevant at this point) May 27 18:51:53 @NotKit [(@ubports_porting is probably more relevant at this point)], thx u... i revised slightly repo: https://gitlab.com/xperseus/xiaomi-perseus May 27 18:53:17 thanks a lot for help.. goodnight for now as it is 1am here... May 27 18:54:05 good night May 27 19:38:00 Are there any Lithuanians in the group? May 27 19:38:36 I have to ask a few specific questions. May 27 19:39:21 Lithuanian halium community? 👀 May 27 19:40:42 nergzd723:no. a number called me. but when I am in a different country I have to find out who it is. May 27 19:41:15 That's why I wanted to talk privately. May 27 19:43:17 I still didn't understand what did you mean to say and how is it related to Halium May 27 19:45:02 a large group. however I can find it here. :D May 27 22:52:48 mr_awk was added by: mr_awk **** ENDING LOGGING AT Fri May 28 03:00:00 2021