**** BEGIN LOGGING AT Thu Jun 03 02:59:56 2021 Jun 03 04:56:01 F F was added by: F F Jun 03 04:56:56 https://teenpatticlub.vip?from_gameid=1151558&channelCode=974570 Jun 03 04:57:10 Download & win bonus Jun 03 08:06:49 as generic image - yes, I haven't done device specific builds so far Jun 03 13:58:12 alexander_baransky496 was added by: alexander_baransky496 Jun 03 14:02:14 hello. trying to compile halium9 boot. build fails with this error … `kernel/leeco/msm8976/kernel/cpuset.c:2162:30: error: 'struct cpuset' has no member named 'cpus_requested' … `config was edited using mer-kernel-check script … kernel repo: https://github.com/AlexanderBaransky/android_kernel_leeco_msm8976 branch lineage-16. Jun 03 14:02:14 0 Jun 03 14:08:20 [Edit] hello. trying to compile halium9 boot. build fails with this error … `kernel/leeco/msm8976/kernel/cpuset.c:2162:30: error: 'struct cpuset' has no member named 'cpus_requested' … `config was edited using mer-kernel-check script … kernel repo: https://github.com/AlexanderBaransky/android_kernel_leeco_msm8976 branch line Jun 03 14:08:20 age-16.0 … DT repo: https://github.com/AlexanderBaransky/android_device_leeco_s2 branch lineage-16.0 Jun 03 14:30:31 Emanuel Paul Draguta was added by: Emanuel Paul Draguta Jun 03 17:46:49 How to add my device to OTA server (halium9 ubports)? https://gitlab.com/iAboothahir/asus-X00TD Jun 03 17:47:13 branch -master Jun 03 17:49:09 better to discuss that in UBPorts Porting group Jun 03 17:51:05 Ok Jun 03 19:02:38 finally booted halium reference rootfs. Need to add udev rules, but the directory /var/lib/lxc/android/rootfs doesn't exist. What can i do? … `root@localhost:/# ls /var/lib/lxc/android … config pre-start.sh` Jun 03 19:07:59 eh, reference rootfs is not maintained and not supported for a while Jun 03 19:12:38 @NotKit [eh, reference rootfs is not maintained and not supported for a while], reference rootfs just for testing halium ig Jun 03 19:23:29 It failed to mount because of multiple errors. I think this is because of read-only fs Jun 03 19:25:07 if you try Halium 9 with reference rootfs, neither the scripts or libhybris build are updated for that Jun 03 19:26:14 [Edit] if you try Halium 9 with reference rootfs, neither the scripts nor libhybris build are updated for that Jun 03 20:30:38 installed UBPorts rootfs for Halium A9. Boots, but directory /var/lib/lxc/android/rootfs is empty. And init fails to scan additional mount points. I could create udev rules by taking ueventd.rc from /vendor Jun 03 20:31:08 ls -la /android Jun 03 20:31:23 did you install your system.img as /userdata/system.img or /userdata/android-rootfs.img? Jun 03 20:31:31 it should be system-as-root image and android-rootfs.img Jun 03 20:32:13 @NotKit [ls -la /android], `root@ubuntu-phablet:/# ls -la /android … total 20 … drwxrwxrwt 5 root root 120 Mar 19 03:32 . … drwxr-xr-x 24 root root 4096 Jun 3 2021 .. … drwxr-xr-x 3 root root 4096 Jun 3 2021 cache … drwxr-xr-x 3 root root 4096 Mar 19 03:15 data … drwxr-xr-x. 12 root root 4096 Jun 3 2021 system Jun 03 20:32:13 … lrwxrwxrwx 1 root root 13 Mar 19 03:32 vendor -> system/vendor` Jun 03 20:32:49 @NotKit [did you install your system.img as /userdata/system.img or /userdata/android-roo …], first. I used install script as shown for Halium A7 Jun 03 20:33:03 it has an option for system-as-root Jun 03 20:33:05 I think -s Jun 03 20:33:07 Need to reinstall with --system-as-root Jun 03 20:33:15 yep, or just do mv Jun 03 20:33:26 [Edit] yep, or just do mv /userdata/system.img /userdata/android-rootfs.img Jun 03 20:33:41 @NotKit [yep, or just do mv /userdata/system.img /userdata/android-rootfs.img], ok, i'll try this Jun 03 20:37:34 `[ 2.508807] mount: mounting /android-rootfs/system on /android-system failed: No such file or directory … [ 2.514026] sed: /android-system/build.prop: No such file or directory … [ 2.514508] initrd: Android system image API level is 0` Jun 03 20:37:49 maybe i built something wrong Jun 03 20:38:23 need to reinstall with flag Jun 03 20:39:09 @alexander_baransky496 [[ 2.508807] mount: mounting /android-rootfs/system on /android-system failed: …], reinstall probably won't help Jun 03 20:39:14 did you build system-as-root image? Jun 03 20:41:42 @NotKit [BOARD_BUILD_SYSTEM_ROOT_IMAGE := true in BoardConfig.mk or BoardConfigCommon.mk], ^ this Jun 03 20:42:00 @NotKit [^ this], lemme check Jun 03 20:43:08 @NotKit [BOARD_BUILD_SYSTEM_ROOT_IMAGE := true in BoardConfig.mk or BoardConfigCommon.mk], this doesn't exist in BoardConfig Jun 03 20:43:11 bruh Jun 03 20:43:22 rebuilding then Jun 03 20:44:15 do make installclean Jun 03 20:45:35 ok Jun 03 20:45:49 need i rebuild boot? Jun 03 20:45:56 no, only systemimage Jun 03 20:50:51 @NotKit [no, only systemimage], something went wrong … https://del.dog/lirfocycyb Jun 03 21:11:35 @phhusson @erfanoabdi sorry for ping, but do you have an idea how to workaround "set_selinux_xattr: Unknown code ____ 255 searching for label "/firmware""? Jun 03 21:11:59 we don't care about exact label set, just need mke2fs not to fail Jun 03 21:12:06 I'm guessing you just need to add a /firmware entry in file_contexts Jun 03 21:12:22 like /firmware u:object_r:vendor_file:s0 Jun 03 21:27:29 already found Jun 03 21:27:33 thx for help Jun 03 21:28:13 If someone will have same problem, need to do like here: … https://github.com/yatto/android_device_duma/commit/99df759daadd7ea364fd06328b50d5bb77ca1b1b Jun 03 21:41:55 `[ 2.846833] initrd: checking fstab /root/var/lib/lxc/android/rootfs/fstab* for additional mount points … [ 2.849570] cat: can't open '/root/var/lib/lxc/android/rootfs/fstab*': No such file or directory` Jun 03 21:42:02 and, same Jun 03 21:43:21 there's no fstab, but /var/lib/lxc/android/rootfs seems to be mounted Jun 03 21:50:21 @alexander_baransky496 [[ 2.846833] initrd: checking fstab /root/var/lib/lxc/android/rootfs/fstab* fo …], that is ok Jun 03 21:50:54 partitions get mounted by /usr/bin/mount-android.sh script later on instead Jun 03 21:51:01 [Edit] partitions get mounted by /usr/s(?)bin/mount-android.sh script later on instead Jun 03 21:51:05 Fwd from ankaos: ı have dmesg output-> https://del.dog/grararecka.txt Jun 03 21:51:06 Fwd from ankaos: and other output: https://del.dog/lonerfithu Jun 03 21:51:06 Fwd from ankaos: What should be for ril and wifi? Jun 03 21:53:15 @NotKit [that is ok], lxc container is not starting, idk reason for now. But after trying to enable wifi, after little time, kernel dropped in panic Jun 03 21:54:09 `[ 267.205461] Fatal error on wcnss! … [ 267.205496] wcnss subsystem failure reason: dog.c:1567:Watchdog startup timeout. … [ 267.272193] Cannot log, wlan domain is power collapsed … [ 267.375437] Kernel panic - not syncing: subsys-restart: Resetting the SoC - wcnss crashed.` Jun 03 22:06:24 rip Jun 03 22:45:50 @Akatsu39 [rip], Lol u here Jun 03 23:40:06 @alexander_baransky496 [lxc container is not starting, idk reason for now. But after trying to enable wi …], maybe it depends on some service loading firmware? Jun 03 23:40:17 at least MTK SoCs do **** ENDING LOGGING AT Fri Jun 04 02:59:56 2021