**** BEGIN LOGGING AT Wed Apr 10 02:59:57 2019
**** BEGIN LOGGING AT Wed Apr 10 06:46:19 2019
Apr 10 10:57:21 <ubptgbot> <nanu_c> There is no documenation on how to backport apparmor3?
Apr 10 10:57:53 <ubptgbot> <Flohack> @nanu_c [There is no documenation on how to backport apparmor3?], There is but its complicated.
Apr 10 10:58:06 <ubptgbot> <Flohack> I can tell you what to do in our session and maybe we can describe it better.
Apr 10 11:00:33 <ubptgbot> <nanu_c> how can i check the aa version 😝😝
Apr 10 11:32:57 <ubptgbot> <Flohack> @nanu_c [how can i check the aa version 😝😝], Thats the fun part. According to what I see, apparmor 3 is still not officially released. BTW this is the official howto: https://wiki.ubuntu.com/SecurityTeam/AppArmorForPreviousKernels
Apr 10 11:33:22 <ubptgbot> <Flohack> Basically take a security/apparmor folder which is guaranteed to be apparmor3, copy it over your kernel folder and see if you got changes
Apr 10 11:33:44 <ubptgbot> <nanu_c> 😝😝
Apr 10 11:34:43 <ubptgbot> <nanu_c> At least ut starts in only 10-15 seconds and the jade diamond browser is unconfined, so i can browse the internet
Apr 10 17:21:28 <ubptgbot> cvstr was added by: cvstr
Apr 10 17:22:40 <ubptgbot> <Flohack> I dont get it, in every of my port experiments I am unable to get the kernel cmdline from BoardConfig.mk into the kernel
Apr 10 17:22:58 <ubptgbot> <Flohack> I am now suspicious that any of the kernel options from the checker might influence this
Apr 10 17:23:13 <ubptgbot> <Flohack> Because, e.g. the TWRP I am using has exactly the parameters form board config
Apr 10 17:23:20 <ubptgbot> <Flohack> But my build cannot pass them in
Apr 10 17:23:46 <ubptgbot> <Flohack> Thats a huge problem for 6P as I need to turn off CPU 4-7 for booting
Apr 10 17:24:00 <ubptgbot> <Flohack> Its a systematic hardware issue with 810 boards
Apr 10 17:24:09 <ubptgbot> <vanyasem> @Flohack [Its a systematic hardware issue with 810 boards], Same as with 5x?
Apr 10 17:24:15 <ubptgbot> <vanyasem> Or something unique to 810?
Apr 10 17:24:58 <ubptgbot> <Flohack> Could be on 5X as well, it was a bug that lets those devices bootloop. let me search the article
Apr 10 17:25:21 <ubptgbot> <vanyasem> @Flohack [Could be on 5X as well, it was a bug that lets those devices bootloop. let me se …], A bug in the cpu or a physical hardware issue!
Apr 10 17:25:23 <ubptgbot> <vanyasem> ?
Apr 10 17:25:47 <ubptgbot> <vanyasem> 5x had its big cores get unsealed from the motherboard and it was an issue from the manufacturer
Apr 10 17:25:55 <ubptgbot> <vanyasem> Which is why all 5xes eventually brick
Apr 10 17:26:12 <ubptgbot> <Flohack> https://lucaberton.it/blog/nexus-5x-and-nexus-6p-bootloop-fix/
Apr 10 17:26:13 <ubptgbot> <Flohack> Same
Apr 10 17:26:24 <ubptgbot> <vanyasem> Yep, I get it now. Thanks
Apr 10 17:26:28 <ubptgbot> <vanyasem> Didn’t know 6p was affected
Apr 10 17:26:39 <ubptgbot> <Flohack> A true mess for Google and Huawei
Apr 10 17:27:14 <ubptgbot> <Flohack> The workaround is basically to add boot_cpus=0-3 maxcpus=4 to the kernel cmdline
Apr 10 17:27:24 <ubptgbot> <Flohack> And some stuff in init.rc
Apr 10 17:28:00 <ubptgbot> <Flohack> I booted this beauty with hybris-boot and mer checker, was working. Now for UBports I fail to do this
Apr 10 17:30:08 <ubptgbot> <Flohack> My boardconfig is now in sync with LOS upstream, so the boot error must be fixed there. Otherwise LOS would not work. So only chance is that we mess up the kernel cfg
Apr 10 17:30:28 <ubptgbot> <Flohack> I will reset kernel dir now and see if it works.
Apr 10 17:40:06 <ubptgbot> <vanyasem> @Flohack [The workaround is basically to add boot_cpus=0-3 maxcpus=4 to the kernel cmdline], That doesn’t fix it for all devices actually
Apr 10 17:40:25 <ubptgbot> <Flohack> @vanyasem [That doesn’t fix it for all devices actually], hmmm
Apr 10 17:40:26 <ubptgbot> <vanyasem> Some of the phones are permanently broken with all cores misbehaving - even the small ones
Apr 10 17:40:30 <ubptgbot> <Flohack> yeah true
Apr 10 17:40:35 <ubptgbot> <vanyasem> My 5x is totally broken for example
Apr 10 17:40:40 <ubptgbot> <vanyasem> Well, the first one ..
Apr 10 17:40:44 <ubptgbot> <Flohack> I read this. Then someone played with the PLL timing and made them going again for some time
Apr 10 17:43:54 <ubptgbot> <vanyasem> @Flohack [I read this. Then someone played with the PLL timing and made them going again f …], Huh?
Apr 10 17:46:40 <ubptgbot> <Flohack> ```@XCnathan32 see . / drivers / clk / qcom / clock-cpu-8994.c … The pll lock bit is defined as BIT(31), which is the MSB of register pll->status_reg. … On the log you posted, pll->status_reg is 0xca000100 with MSB set, this suggests the pll has locked by the time that debug message has set. … Conclusion: the cpu is not giving the pll eno
Apr 10 17:46:40 <ubptgbot> ugh time to lock. … Suggested possible solution: change line 53 in clock-pll.c from #define ENABLE_WAIT_MAX_LOOPS 200 to #define ENABLE_WAIT_MAX_LOOPS 100000 to give the pll 100ms to attempt a lock. ``` e.g.
Apr 10 17:48:18 <ubptgbot> <vanyasem> @Flohack [@XCnathan32 see . / drivers / clk / qcom / clock-cpu-8994.c … The pll lock bit is …], So this might theoretically unbrick some of the totally bricked 5x/6p devices?
Apr 10 17:49:00 <ubptgbot> <Flohack> Maybe yes. But as the poster states, it might make them unstable also because the random success on the PLL lock does not mean the hardware problem is gone.
Apr 10 17:49:51 <ubptgbot> <Flohack> (Photo, 636x800) https://irc.ubports.com/6twYzSh4.png How I love ASCII art!
Apr 10 17:50:18 <ubptgbot> <K31j0> @Flohack [<reply to media>], is that an in-kernel comment?
Apr 10 17:50:43 <ubptgbot> <Flohack> @K31j0 [is that an in-kernel comment?], Yes its in the clock driver 😆
Apr 10 17:51:07 <ubptgbot> <K31j0> looks cool but idk how to interpret it really XD
Apr 10 17:51:21 <ubptgbot> <Flohack> hehe more of a braindump of the coder
Apr 10 18:03:33 <ubptgbot> <Flohack> @vanyasem [So this might theoretically unbrick some of the totally bricked 5x/6p devices?], LOL its clear now, boot.img is not regenerated - has date from yesterday
Apr 10 18:03:40 <ubptgbot> <Flohack> how can this happen
Apr 10 18:03:55 <ubptgbot> <Flohack> I dont want to always clean the whole out dir
Apr 10 18:04:03 <ubptgbot> <K31j0> make clobber and try again maybe buildsystem commited deathspacito
Apr 10 18:04:13 <ubptgbot> <vanyasem> @Flohack [LOL its clear now, boot.img is not regenerated - has date from yesterday], Nice try xD
Apr 10 18:04:36 <ubptgbot> <Flohack> smth fishy in halium-boot
Apr 10 18:04:55 <ubptgbot> <UniversalSuperBox> @Flohack [LOL its clear now, boot.img is not regenerated - has date from yesterday], Halium-boot.img
Apr 10 18:04:59 <ubptgbot> <UniversalSuperBox> boot.img is nothing
Apr 10 18:05:03 <ubptgbot> <Flohack> oh true
Apr 10 18:05:12 <ubptgbot> <Flohack> what I am flashing 😆waaait
Apr 10 18:05:18 <ubptgbot> <Flohack> cout
Apr 10 18:05:29 <ubptgbot> <UniversalSuperBox> Nice
Apr 10 18:06:13 <ubptgbot> <Flohack> hmm who tf created a boot.img yesterday here
Apr 10 18:06:27 <ubptgbot> <UniversalSuperBox> It comes with default make or something
Apr 10 18:06:32 <ubptgbot> <UniversalSuperBox> It doesn't really matter
Apr 10 18:06:38 <ubptgbot> <Tygerpro> Doesnt every port create a boot.img?
Apr 10 18:07:15 <ubptgbot> <Flohack> it must be from systemimage
Apr 10 18:08:35 <ubptgbot> <Flohack> Ok now we are talking
Apr 10 18:27:15 <ubptgbot> <Flohack> @vanyasem [Nice try xD], BAM it booted!
Apr 10 18:29:02 <ubptgbot> <Flohack> But why I am in telnet
Apr 10 18:29:04 <ubptgbot> <Flohack> only
Apr 10 18:30:46 <ubptgbot> <Flohack> @vanyasem [So this might theoretically unbrick some of the totally bricked 5x/6p devices?], Its so sad to see the octa-core cut off: ```[    0.030774] Brought up 4 CPUs … [    0.030790] SMP: Total of 4 processors activated.```
Apr 10 18:36:38 <ubptgbot> <Flohack> Hmm @UniversalSuperBox master of bind mounts, what is wrong when I get ```[    5.475612] initrd: Normal boot … [    5.476829] mkdir: can't create directory '/root/android': Read-only file system```
Apr 10 18:36:53 <ubptgbot> <UniversalSuperBox> Create the directory /android on your image
Apr 10 18:37:27 <ubptgbot> <Flohack> eh? in the systemimage?
Apr 10 18:37:35 <ubptgbot> <UniversalSuperBox> in the rootfs
Apr 10 18:37:45 <ubptgbot> <Flohack> ahh ok its arm64 fail then
Apr 10 18:37:54 <ubptgbot> <UniversalSuperBox> Which rootfs are you using
Apr 10 18:38:10 <ubptgbot> <Flohack> the manually triggered build by marius some weeks ago
Apr 10 18:38:18 <ubptgbot> <UniversalSuperBox> ok
Apr 10 18:45:42 <ubptgbot> <Flohack> lol samer for userdata
Apr 10 18:46:11 <ubptgbot> <nanu_c> @Flohack [I dont want to always clean the whole out dir], use not `mka` but `cmka` -> `- cmka:     Cleans and builds using mka.`
Apr 10 18:46:35 <ubptgbot> <Flohack> @nanu_c [use not mka but cmka -> - cmka:     Cleans and builds using mka.], Takes too long ^^ I am lazy. Want not wait ages just for changes of kernel cmdline ^^
Apr 10 18:47:07 <ubptgbot> <Tygerpro> Why not just use "mka kernel"
Apr 10 18:47:30 <ubptgbot> <UniversalSuperBox> No, the kernel is made and only the bootimg needs to be rebuilt
Apr 10 18:47:37 <ubptgbot> <UniversalSuperBox> But the point is moot, he was using the wrong image
Apr 10 18:47:45 <ubptgbot> <Flohack> @UniversalSuperBox [in the rootfs], Can I see somewhere all default folders needed?
Apr 10 18:48:28 <ubptgbot> <Tygerpro> Ahh ok, i do have a question, in my port for my note 4, i have a boot and recovery.img file, can I just flash those or do I have to do something with them first
Apr 10 18:48:35 <ubptgbot> <UniversalSuperBox> @Flohack [Can I see somewhere all default folders needed?], Are you using this? https://ci.ubports.com/job/xenial-rootfs-arm64/
Apr 10 18:48:41 <ubptgbot> <UniversalSuperBox> @Tygerpro [Ahh ok, i do have a question, in my port for my note 4, i have a boot and recove …], Those probably don't do anything
Apr 10 18:48:50 <ubptgbot> <Flohack> @UniversalSuperBox [Are you using this? https://ci.ubports.com/job/xenial-rootfs-arm64/], yes
Apr 10 18:49:07 <ubptgbot> <Tygerpro> Well arent they the files for the ubports recovery and bootloader?
Apr 10 18:49:22 <ubptgbot> <UniversalSuperBox> @Flohack [yes], That's 2 months old now. Are you sure you want it?
Apr 10 18:49:45 <ubptgbot> <UniversalSuperBox> Maybe this is closer to what you want: https://ci.ubports.com/job/xenial-hybris-edge-rootfs-arm64/
Apr 10 18:49:48 <ubptgbot> <Flohack> @UniversalSuperBox [That's 2 months old now. Are you sure you want it?], No 😆but I am not sure it will change when I trigger it manually. Can try ofc
Apr 10 18:50:00 <ubptgbot> <Flohack> @UniversalSuperBox [Maybe this is closer to what you want: https://ci.ubports.com/job/xenial-hybris- …], Do I trust edge channel?
Apr 10 18:50:06 <ubptgbot> <UniversalSuperBox> I don't know, do you?
Apr 10 18:53:46 <ubptgbot> <Flohack> Hmmm ^^
Apr 10 18:58:54 <ubptgbot> <Flohack> Ill give it a try. The old one barfs with lots of missing folders
Apr 10 19:12:27 <ubptgbot> <Flohack> @UniversalSuperBox [Create the directory /android on your image], the folder android is also not there in the 32bit rootfs. where should they come from?
Apr 10 19:15:26 <ubptgbot> <UniversalSuperBox> Oh. It's done by your install script then.
Apr 10 19:15:55 <ubptgbot> <Flohack> Hmm or not
Apr 10 19:16:11 <ubptgbot> <Flohack> I am using halium-install from JBB maybe thats a mistake?
Apr 10 19:16:25 <ubptgbot> <UniversalSuperBox> Are you using -p ut
Apr 10 19:17:16 <ubptgbot> <Flohack> No, because that breaks with chroot not found or wrong bittage... 😆
Apr 10 19:17:25 <ubptgbot> <Flohack> See my post from yesterday
Apr 10 19:17:44 <ubptgbot> <Flohack> Fwd from Flohack: cool chroot throws a segfault
Apr 10 19:17:47 <ubptgbot> <Flohack> that
Apr 10 19:19:25 <ubptgbot> <Flohack> Ok will check install steps for ut and do it manually
Apr 10 19:20:21 <ubptgbot> <Flohack> Maybe it works with edge though
Apr 10 19:44:27 <ubptgbot> <Flohack> Hmm not very successful. I tried to follow the manual steps there but still I get this: ```[    5.512410] run-init: opening console: No such device … [    5.512564] Target filesystem doesn't have requested /sbin/init.```
Apr 10 19:45:20 <ubptgbot> <UniversalSuperBox> Remove console=
Apr 10 19:45:29 <ubptgbot> <Flohack> hmm I specifically added it ^^
Apr 10 19:45:39 <ubptgbot> <Flohack> but the error was there before I think
Apr 10 19:46:03 <ubptgbot> <UniversalSuperBox> No, that's an error. Panic is right after that, right?
Apr 10 19:47:12 <ubptgbot> <Flohack> more or less yes
Apr 10 19:47:31 <ubptgbot> <UniversalSuperBox> Not opening the console is a fatal error
Apr 10 19:47:54 <ubptgbot> <Flohack> @UniversalSuperBox [Remove console=], add console then?
Apr 10 19:48:13 <ubptgbot> <UniversalSuperBox> Lack of a console is your goal
Apr 10 19:48:44 <ubptgbot> <UniversalSuperBox> Or check to make sure the rootfs is actually mounted. It better be at that poibt but I don't judge
Apr 10 19:49:30 <ubptgbot> <Flohack> Think so: ```[    5.489777] initrd: moving Android system to /android/system … [    5.495081] mount: mounting /root/android/system/lib/modules on /root/lib/modules failed: No such file or directory … [    5.497233] Begin: Running /scripts/local-bottom ... done. … [    5.497399] done. … [    5.502737] Begin: Running /scripts/nfs-bottom ...
Apr 10 19:49:30 <ubptgbot>  done. … [    5.502999] Begin: Running /scripts/init-bottom ... done. … [    5.512410] run-init: opening console: No such device```
Apr 10 19:50:20 <ubptgbot> <nanu_c> @Flohack [Thats the fun part. According to what I see, apparmor 3 is still not officially …], The git repositorie from this manual  doesn't exist anymore and they are talking about a canonical apparmor version that is partly upstreamed, but who knows. Was this done on one of the core devices in ut and can i copy the aa from there?
Apr 10 19:51:39 <ubptgbot> <Flohack> Well you can copy it if its the same kernel version which will be hard with 3.18
Apr 10 19:52:01 <ubptgbot> <Flohack> @UniversalSuperBox [Or check to make sure the rootfs is actually mounted. It better be at that poibt …], `console=NULL` says the bootloader, my old friend.
Apr 10 19:52:35 <ubptgbot> <UniversalSuperBox> NULL definitely doesn't exist
Apr 10 19:52:40 <ubptgbot> <Flohack> hahaha I know ^^
Apr 10 19:55:57 <ubptgbot> <Flohack> @UniversalSuperBox [NULL definitely doesn't exist], Shall I try to also kill androidboot.console=ttyHSL0 ??
Apr 10 19:56:33 <ubptgbot> <UniversalSuperBox> Nope
Apr 10 19:57:01 <ubptgbot> <Flohack> Hmm  my options are limited, I can again apply my cmdline killer patch ofc and set console=
Apr 10 20:19:14 <ubptgbot> <UniversalSuperBox> If you add your own `console=`, does it use yours
Apr 10 20:19:47 <ubptgbot> <Flohack> only with CONFIG_CMDLINE_EXTEND=y and my special patch, you might remember I put this in the old wiki
Apr 10 20:19:50 <ubptgbot> <Flohack> Trying that now
Apr 10 20:20:00 <ubptgbot> <Flohack> thats a mess
Apr 10 20:35:33 <ubptgbot> <nanu_c> Okey, the problem with custom canonical apparmor and every device with a newer kernel is the same if i understand it right. Can we drop the canonical aa and use the upstream version?
Apr 10 20:38:46 <ubptgbot> Adriano Angelucci was added by: Adriano Angelucci
Apr 10 20:38:59 <ubptgbot> <nanu_c> or is it meant that `Apparmor3 in the phablet kernels is based on the upstream backport kernels of apparmor3. ` using this patches https://gitlab.com/apparmor/apparmor/tree/master/kernel-patches
Apr 10 20:39:28 <ubptgbot> <Adriano Angelucci> Fwd from Adriano Angelucci: Hi everyone I am a lover of Linux, my wife at Christmas gave me a 10-inch Alcatel Tablet with 3g model 9010X phone card, I would like to install Ubuntu touch on the Tablet is it possible according to you? If you tell me which one to choose on ubport
Apr 10 20:39:28 <ubptgbot> <Adriano Angelucci> (Photo, 720x1280) https://irc.ubports.com/OIFSIZCA.png
Apr 10 20:57:23 <ubptgbot> <nanu_c> @Adriano Angelucci [Hi everyone I am a lover of Linux, my wife at Christmas gave me a 10-inch Alcate …], every phone needs a proper port to work with ut. If it's not in the list, then someone (maybe you ;) has to do the porting.
Apr 10 20:58:45 <ubptgbot> <nanu_c> Your phone has a Lineage OS 14.1 port so it may work. To get you started please read the docs http://docs.halium.org/en/latest/
Apr 10 20:59:12 <ubptgbot> <Adriano Angelucci> how it's done is the first time I try to install Ubuntu on Tablet
Apr 10 21:00:40 <ubptgbot> <nanu_c> @Adriano Angelucci [how it's done is the first time I try to install Ubuntu on Tablet], It's not ported, so you have to port it and in the documentation of hallium is the manual how to port: http://docs.halium.org/en/latest/ but i will say it takes at least 4-8 weeks to do it
Apr 10 21:02:41 <ubptgbot> <Adriano Angelucci> Damn so much I should start putting my hand together to see
Apr 10 21:04:05 <ubptgbot> <nanu_c> But maybe you have luck and it just works. But for me it took a while to learn the vocabulary, have you ever built a linux kernel?
Apr 10 21:08:32 <ubptgbot> <Adriano Angelucci> No I never did it I honestly don't know where to start here it would take 😂😂MrRobot
Apr 10 21:44:31 <ubptgbot> <Flohack> @UniversalSuperBox [If you add your own console=, does it use yours], I give up, in arm64 my patch cannot be used anymore, and I am too stupid to patch the new one in drivers/of/fdt.c
Apr 10 21:44:52 <ubptgbot> <Flohack> Thats a problem. Why can´t we get rid of the console in a different way? Lots of bootloaders to that setting
Apr 10 22:05:51 <ubptgbot> <vince1171> @Flohack [Its so sad to see the octa-core cut off: [    0.030774] Brought up 4 CPUs … [    0 …], I fixed it on Oneplus2 like this … https://github.com/Vince1171/android_device_oneplus_oneplus2/commit/9ff9ea16eb0108aa89abdad0bef9715be23b8943
Apr 10 22:06:19 <ubptgbot> <Flohack> hmmm
Apr 10 22:06:40 <ubptgbot> <Flohack> strange
Apr 10 22:06:44 <ubptgbot> <Flohack> why that would work
Apr 10 22:06:56 <ubptgbot> <vince1171> And now it use all of the 8 cores
Apr 10 22:09:08 <ubptgbot> <vince1171> @Flohack [why that would work], I have no idea to be honest xD … I remember have seen this fix somewhere, but I can't remember where ^^
Apr 10 22:09:57 <ubptgbot> <vince1171> @Flohack [why that would work], [Edit] I have no idea to be honest xD … I remember have seen this fix somewhere in on a forum, but I can't remember where ^^
Apr 10 22:20:11 <ubptgbot> <vince1171> @Flohack [why that would work], [Edit] I have no idea to be honest xD … I've change it like that to revert this commit and force to use the 8 core with the kernel parameter … https://github.com/Vince1171/android_device_oneplus_oneplus2/commit/a3b50cd3b929e6e487be06c6c992729051872c63
Apr 10 22:20:58 <ubptgbot> <Flohack> Well ok now I understand, this works of course except on the affected google devices. You dont have the hardware bug, when I enable this immediately I bootloop
Apr 10 22:21:12 <ubptgbot> <Flohack> Its nothing in general that I see here just a specific bug
Apr 10 22:21:37 <ubptgbot> <Flohack> I am already 1 step further, trying to boot halium correctly
Apr 10 22:23:15 <ubptgbot> <vince1171> Oh sorry for fake hope... :(
**** ENDING LOGGING AT Thu Apr 11 02:59:58 2019