**** BEGIN LOGGING AT Thu Jan 03 02:59:57 2019 Jan 03 09:51:12 Does anyone know why is this problem/warning? … http://pastebin.com/n8Fs9u1G Jan 03 09:52:13 I edited already the fixup-mountpoints Jan 03 09:53:01 [Edit] I edited already the fixup-mountpoints and I have some problem with ninja Jan 03 09:59:42 On both reference chroot and plasma mobile it stays on HTC logo, ssh works, graphic tests fail, is this normal or should I be seeing something on the screen Jan 03 10:08:10 (Photo, 1280x314) https://irc.ubports.com/IgneiCdE.png But if I type 'export USE_NINJA=false' … Works... Jan 03 10:11:39 ok finally kinda getting somewhere. any idea what configs I need to change? … https://paste.ubuntu.com/p/YK9STxD6rG/ Jan 03 10:56:11 Hi all Jan 03 10:56:31 Who knows why I get this error? Jan 03 10:56:39 13: expected newline, got '|' Jan 03 11:05:27 https://paste.ubuntu.com/p/GN42xwjZxr/ Jan 03 11:05:36 how can I get more info about this Jan 03 12:28:20 Guys ... is there a rootfs that's more up-to-date than the 2017 one on the Wiki? Jan 03 12:30:54 @Sergobot Well, it's a pretty good idea actually. (Using your port) Jan 03 12:32:45 @Sergobot Do I need to delete everything and start over? … Or is there something else possible? Jan 03 12:36:19 @WaseemAlkurdi, Restore my manifest and then run setup again iirc Jan 03 12:37:21 Okay ... doing just that! Jan 03 12:37:45 No need to "remove" anything downloaded from Google's repos? Jan 03 12:37:58 May be you will need to delete paths such as device/google/marlin and same for kernel Jan 03 12:38:13 Done! Jan 03 12:41:13 Nice :) Jan 03 12:46:16 I'm trying to use USB network tethering, I edited /etc/resov.conf to get dns, I can ping websites but apt still fails to resolve repos Jan 03 12:47:01 I had to get WiFi working before my port could use apt Jan 03 12:49:17 I have no clue what's wrong with wifi, but I read a suggestion to someone in relation to the error … EGL_PLATFORM=hwcomposer test_hwcomposer … cannot locate symbol "android_create_namespace" referenced by "/system/lib/libgui.so"... … test_hwcomposer: test_hwcomposer.cpp:179: int main(int, char**): Assertion `err == 0' failed. … Abo Jan 03 12:49:17 rted … that it might be because libhyris is too old and it might be resolved by adding CAF repo and upgrading it Jan 03 12:50:18 for wifi I have no wlan in /sys/module and nothing in /system/lib/modules Jan 03 12:51:17 Yea, that might need to get fixed at some point, as far as why USB networking isn't working what happens if you ping google.com Jan 03 12:51:27 works normally Jan 03 12:51:48 OK so it says pinging and shows an IP? Jan 03 12:52:25 ping google.com … PING google.com (172.217.16.110) 56(84) bytes of data. … 64 bytes from prg02s12-in-f14.1e100.net (172.217.16.110): icmp_seq=1 ttl=44 time=103 ms … 64 bytes from prg02s12-in-f14.1e100.net (172.217.16.110): icmp_seq=2 ttl=44 time=103 ms Jan 03 12:52:40 Does "sudo apt-get update" give useful info in its error? Jan 03 12:53:34 hold on I think I might've found the issue Jan 03 12:55:19 nope Jan 03 12:55:24 Temporary failure resolving 'ports.ubuntu.com' Jan 03 12:55:29 nothing useful Jan 03 12:59:07 any idea what the issue with wifi could be? I don't think it's a broadcom chip Jan 03 13:02:17 @Nebrassy, You may have precompiled wifi module in vendor repository, Jan 03 13:02:29 @Nebrassy, [Edit] You may have precompiled wifi module in vendor repository, check this out Jan 03 13:06:22 @Dzmitry Sankouski, nope, only libraries Jan 03 13:08:16 There should be some wifi module declarations in device repo, check it in both common and device specific Jan 03 13:08:35 [Edit] There should be some wifi module declarations in device repo makefiles, check it in both common and device specific Jan 03 13:10:12 @Nebrassy, comment out _apt in /etc/passwd Jan 03 13:11:47 @Dzmitry Sankouski, yup … # WLAN firmware … etc/firmware/fw_bcm4335_apsta_b0.bin … etc/firmware/fw_bcm4335_b0.bin … etc/firmware/fw_bcm4335_p2p_b0.bin Jan 03 13:13:50 this is a firmware - not kernel module, try to find something related to kernel module Jan 03 13:14:47 @NotKit, this worked, thanks Jan 03 13:25:49 @Dzmitry Sankouski, can't find anything Jan 03 13:26:17 @Nebrassy, about this, does it make any sense, how can I do that? Jan 03 13:38:56 [Edit] I have no clue what's wrong with wifi, but I read a suggestion to someone in relation to the error … EGL_PLATFORM=hwcomposer test_hwcomposer … cannot locate symbol "android_create_namespace" referenced by "/system/lib/libgui.so"... … test_hwcomposer: test_hwcomposer.cpp:179: int main(int, char**): Assertion `err == 0' failed Jan 03 13:38:56 . … Aborted … that it might be because libhybris is too old and it might be resolved by adding CAF repo and upgrading it Jan 03 13:40:01 @Nebrassy, according to https://wireless.wiki.kernel.org/en/users/drivers/brcm80211 your wlan module was mainlined in 3.10 kernel Jan 03 13:40:46 @Dzmitry Sankouski, I believe my kernel is 3.04 Jan 03 13:41:01 Backports time! Jan 03 13:42:30 @Nebrassy, it's 3.4.113 Jan 03 13:42:44 Oops I'm retarded Jan 03 13:43:30 dpkg: warning: 'ldconfig' not found in PATH or not executable … dpkg: warning: 'start-stop-daemon' not found in PATH or not executable … dpkg: error: 2 expected programs not found in PATH or not executable … Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin … W: No sandbox user '_apt' on the system, can Jan 03 13:43:30 not drop privileges … E: Sub-process /usr/bin/dpkg returned an error code (2) Jan 03 13:43:43 Trying to upgrade libhybris Jan 03 13:44:00 `. /etc/environment` Jan 03 13:44:28 Damit I keep forgetting that Jan 03 13:49:20 Graphic tests still fail, so far only vibrator and usb tethering works, the main problem is graphics but I have no idea what the problem is Jan 03 13:51:26 @Dzmitry Sankouski, Check your kernel configuration related to BCMA module in lineage / halium maybe there is some differences? Jan 03 13:51:55 (drivers/bcma) Jan 03 13:52:33 Check your kernel configuration related to BCMA in lineage and halium Jan 03 13:54:32 in m7_defconfig … CONFIG_BCMA_POSSIBLE=y … # … # Broadcom specific AMBA … # … # CONFIG_BCMA is not set Jan 03 13:58:37 @Nebrassy, The graphics tests failed on my port with the reference roots as well, I decided to just try halium-boot and the edge rootfs on my device anyways cause worse case I had a headless system, as long as your android container is running you might be able to do the same Jan 03 13:58:58 I'll try building with … CONFIG_MODULES=y … CONFIG_BCMDHD=m Jan 03 13:59:46 @Tygerpro Tygerpro, I'll test plasma mobile next, haven't tested it after I fixed the android container Jan 03 14:01:51 I never tested PM on my device, hybris-boot takes 20+ minutes to boot on my device while halium-boot is a few seconds, that's also part of why I just went straight to halium-boot even if the graphics didn't work, waiting 20+ minutes just to find out a test causes the port to crash is very angering lol Jan 03 14:03:10 thankfully it only takes a few minutes for me Jan 03 14:04:06 Lucky Jan 03 14:06:45 @Nebrassy, BTW, where this error occured? Jan 03 14:07:14 you wheere trying to load wifi module manually? Jan 03 14:07:24 @Dzmitry Sankouski, yeah Jan 03 14:10:44 I guess this (CONFIG_BCMDHD_4335_MCC=y) means that wifi driver is compiled into kernel Jan 03 14:15:06 It must be as there are no references to any modules Jan 03 14:42:24 @Nebrassy, after doing so, there's bcmdhd.ko and scsi_wait_scan.ko in /system/lib/modules Jan 03 14:42:36 root@localhost:/system/lib/modules# insmod /system/lib/modules/bcmdhd.ko … insmod: ERROR: could not insert module /system/lib/modules/bcmdhd.ko: Invalid module format Jan 03 14:43:20 documentation says I should add … insmod /system/lib/modules/bcmdhd.ko … to init.rc, where's that? Jan 03 14:43:54 If you don't have the module, you don't need to insert it Jan 03 14:43:55 anywhere Jan 03 14:44:50 @UniversalSuperBox, after building with … CONFIG_MODULES=y … CONFIG_BCMDHD=m … I have the module Jan 03 14:57:08 Tofe, are you here + available for PMs? Jan 03 14:58:44 though don't know why I'm getting invalid module format, I have flashed both boot and system image Jan 03 14:59:28 I really don't know. If you have the room for the driver in the kernel, though, I'm not sure why you'd want the module instead! Jan 03 14:59:35 replace ! with ? Jan 03 15:02:52 UnivrslSuprBox: yup Jan 03 15:05:07 @UniversalSuperBox, because I don't have wlan in /sys/module and with … nmcli d … wlan0 is unavailable Jan 03 15:05:20 I don't think those things are the same problem Jan 03 15:05:30 It isn't in `/system/lib/modules` because it's not a module Jan 03 15:05:33 It's built in to the kernel Jan 03 15:06:14 yes, I get that, the reason why I went through all this is because I can't activate wlan Jan 03 15:06:36 @Nebrassy, have you tried `cat /proc/deferred_initcalls` ? Jan 03 15:07:37 @minlexx, cat: /proc/deferred_initcalls: No such file or directory Jan 03 15:07:56 With the driver built in to the kernel Jan 03 15:08:15 on 3.4.113 kernel I've built-in bcmdhd and wifi works after calling deferred_initcalls Jan 03 15:09:49 @UniversalSuperBox, so I should change back … CONFIG_MODULES=y … CONFIG_BCMDHD=m … and rebuild then try that? Jan 03 15:09:57 Yep Jan 03 15:10:22 alright, got a power outage now will continue at night Jan 03 15:10:24 thanks Jan 03 17:13:42 (Photo, 720x1280) https://irc.ubports.com/Qaz4t0xy.png Jan 03 17:13:46 Forking progress mates Jan 03 17:13:52 [Edit] Foking progress mates Jan 03 17:23:21 Though touch input doesn't work, are there any specifics to getting pm to work? Jan 03 17:56:19 I never tried PM, I just went straight to UT cause I heard PM was fickle with CAF device (at that time) Jan 03 17:57:19 I've rebuilt, still can't get wifi to work … cat: /proc/deferred_initcalls: No such file or directory Jan 03 17:57:55 @Tygerpro Tygerpro, I want to get halium stuff working first then I'll maybe try UT Jan 03 17:59:14 EGL_PLATFORM=hwcomposer test_hwcomposer … this works on PM, other test result in … library "libgui.so" wasn't loaded and RTLD_NOLOAD prevented it … Segmentation fault Jan 03 17:59:25 [Edit] EGL_PLATFORM=hwcomposer test_hwcomposer … this works on PM, other tests result in … library "libgui.so" wasn't loaded and RTLD_NOLOAD prevented it … Segmentation fault Jan 03 19:13:37 fckthsshtbth was added by: fckthsshtbth Jan 03 19:13:40 hi) Jan 03 19:13:58 how to fixthis Jan 03 19:13:59 halium-install -p halium halium-rootfs-20170630-151006.tar.gz system.img … qemu-arm-static not found in $PATH Jan 03 19:22:42 Hey, it's me again. I am still unable to launch Plasma. … Launching "kwin_wayland --hwcomposer plasma-phone" or kwrapper yields: … Error: could not determine $DISPLAY … FATAL ERROR: backend failed to initialize, exiting now … I am unsure if this is even the right way to launch PM but booting just sends me to command line login promp Jan 03 19:22:42 t. (Is it supposed to autoboot into PM?) … Any ideas highly appreciated. Jan 03 19:33:48 how to fix Jan 03 19:33:52 Please enter a new password for the 'root' user: … chroot: failed to run command ‘passwd’: Exec format error … Failed, please try again Jan 03 19:34:17 chroot: failed to run command ‘passwd’: Exec format error Jan 03 19:36:52 You miss qemu-arm Jan 03 19:49:52 qemu-arm not in database of installed binary formats Jan 03 19:50:04 i have installed qemu Jan 03 20:15:21 @fckthsshtbth which distro? Jan 03 20:15:55 https://wiki.debian.org/QemuUserEmulation Jan 03 20:26:06 @Daniel, the simplelogin systemd service should start plasma at boot. You could install htop to conviniently see what it starts Jan 03 20:26:40 First of all, does lxc start properly now? Jan 03 20:38:48 @Nebrassy, What do you mean can't activate wlan? Start right from here, because seems you have a lineage port with wifi working well... Jan 03 20:39:07 Oh... ok! Ill check that out. … Yes, LXC does start up properly (more or less, some services still crash, but test_hwcomposer runs fine). Jan 03 20:40:48 @JBBgameich, Oh... ok. Ill check that out. … Yes, LXC is starting properly now (more or less, some services still do crash, but test_hwcomposer is running fine). … Thank for the input! Jan 03 20:41:38 @Dzmitry Sankouski, With nmcli d, wlan0 is unavailable, and with nmtui I can't see it Jan 03 20:43:01 what about /dev/wcnss_wlan and /sys/module/wlan/parameters/fwpath ?? … Is this files present on your device? Jan 03 20:43:31 @Dzmitry Sankouski, No Jan 03 20:46:58 @JBBgameich, One more thing (off topic): I am not sure if it's just me (on x86 or whatever), but I get a lot of complains in logcat that Android is unable to access cpusets. It seems that this might have something to do with the way the cpusets are mounted. See https://github.com/lxc/lxc/issues/2509 for further info on this iss Jan 03 20:46:58 ue. … However using "mount -o noprefix cpuset none /dev/cpuset" in init.rc fixed it for me. Jan 03 20:47:38 @Nebrassy, I dealing with a similar problem, except its my cellular modem and nmyui sees it but can't activate it Jan 03 20:47:53 @Nebrassy, [Edit] I dealing with a similar problem, except its my cellular modem and nmtui sees it but can't activate it Jan 03 20:50:28 @Tygerpro Tygerpro, I think I've done enough with reference roots, at least I got lxc working, tomorrow I'll build UT and see how it goes Jan 03 20:51:40 Good luck, I basically have mine using hybris-boot's defconfig with apparmor enabled and selinux disabled Jan 03 21:15:47 vilmarkde was added by: vilmarkde Jan 03 21:17:55 @Tygerpro Tygerpro, @Sergobot In Tygerpro Tygerpro 's case, hybris-boot works and provides graphics while halium-boot doesn't provide them. … Could our problem on the 1st gen Pixel be possibly related to this? Jan 03 21:19:17 Halium-boot gives me graphics, hybris-boot does not Jan 03 21:19:40 I used the same config as hybris-boot only added apparmor for UT Jan 03 21:19:50 @Tygerpro Tygerpro, Oh ... so it's the wrong way round😅 … I apologize! Jan 03 21:20:05 Its OK, but it could be related Jan 03 21:20:22 Our problem is that we can't use hybris-boot (A/B device) and halium-boot doesn't provide graphucs Jan 03 21:20:26 Graphics* Jan 03 21:21:23 I had that issue as well, in my case it was the container not starting initially, and now I have to use a older rootfs cause the new one doesn't seem to work for my device Jan 03 21:22:19 @Tygerpro Tygerpro, Does that old one happen to be the one from May 2017, linked to on the official Wiki? Jan 03 21:24:15 The reference rootfs that I tried with hybris-boot? That failed all the graphics tests but other stuff worked which is why I moved to UT Jan 03 21:24:25 xd Jan 03 21:24:43 @Tygerpro Tygerpro, Ah, so Ubuntu Touch's rootfs worked better in your case? Jan 03 21:26:10 Yea, I have to use the edge rootfs from December 8th 2018, I haven't tested any from that date to the end of the year when they added the caf and ofono stuff to the regular rootfs Jan 03 21:26:51 Fredrik_Kempe was added by: Fredrik_Kempe Jan 03 21:27:29 @Tygerpro Tygerpro, Will do ... thanks for the heads-up!😍 Jan 03 21:29:30 Bear in mind this is specific to my device and does not mean it will be the same experience on yours, but it is worth trying Jan 03 21:30:32 @Tygerpro Tygerpro, That's the rationale ... Might work, if not, nothing lost! Jan 03 21:30:50 True Jan 03 23:20:53 frzifus was added by: frzifus **** ENDING LOGGING AT Fri Jan 04 02:59:56 2019