**** BEGIN LOGGING AT Sun Dec 31 03:00:02 2017 Dec 31 08:45:16 Morning Dec 31 08:59:34 elvispre: morning! Dec 31 09:01:09 Herrie: The onyx kernel itself didn't make it onto webos-ports.org. I got one locally so I expect there's just a typo somewhere. Dec 31 09:02:21 Herrie: More interestingly, can I try booting my device with it (and how)? Dec 31 10:01:13 elvispre: Yes you can Dec 31 10:01:47 You need the .fastboot file that's created by the build Dec 31 10:47:45 elvispre: YOu want to have a recovery on it (TWRP or CWM) Dec 31 10:48:08 Boot into fastboot mode, then "fastboot flash boot myfile.fastboot" Dec 31 10:48:10 Then reboot Dec 31 10:48:15 It'll most likely bootloop Dec 31 10:48:26 Then go into recovery and pull the logfile Dec 31 10:49:09 Logfile can be pulled with "adb pull /sys/fs/pstore/console-ramoops" Dec 31 11:01:04 Herrie: So I have a kernel and associated .fastboot file on my LuneOS build VM and a root file system on my android build VM. Surely I want both of them on the device Dec 31 11:03:41 No just kernel for now Dec 31 11:03:46 * elvispre thinks, I suppose I could just try booting my kernel on top of the LineageOS filesystems Dec 31 11:03:52 The fastboot that is Dec 31 11:08:11 YOu could technically build teh whole onyx image Dec 31 11:08:54 Herrie: Right, but one step at a time, eh? :-) Dec 31 11:27:15 elvispre: Worst case it would still bootloop :P Dec 31 11:27:29 BEst case it'd boot (99,99999% it won't though) Dec 31 11:28:33 Herrie: pong, Merry Christmas to you & yours Dec 31 11:28:47 Herrie: So (right now) I have just done "fastboot boot " and LineageOS is up as normal. (No flashing required.) Dec 31 11:29:16 novaldex: You too Dec 31 11:29:52 Herrie: thanks! are you all set for new year? Dec 31 11:29:54 novaldex: I noticed that the halium irc log isn't creating the daily archives Dec 31 11:30:02 It just appends in halium.txt Dec 31 11:30:14 Could be some minor issue somewhere? Dec 31 11:30:26 probably, it was a new channel setup, i'll take a look Dec 31 11:30:27 elvispre: Well if you don't flash boot it could be it failed first time and then booted 2nd time Dec 31 11:30:38 we are getting all the content though, it's just not separating into dailies? Dec 31 11:31:54 Herrie: Build number on device says 'onyx-userdebug', but I suppose LineageOS may use those words too. Dec 31 11:34:22 novaldex: COrrect Dec 31 11:34:31 elvispre: WE build userdebug too ;) Dec 31 11:35:17 thanks Herrie, sounds logrotate related Dec 31 11:35:22 Herrie: That's what I mean. I am trying to establish if it is my built kernel that is running. Dec 31 11:35:50 elvispre: Then again it should run really Dec 31 11:36:14 Since we didn't update any defconfig yet that would be required Dec 31 11:37:06 It was rather vanilla cm-14.1 branch kernel. Dec 31 11:42:19 Hmm. It looks to me like this is running a kernel built in October; not mine. Dec 31 11:49:33 Herrie: Thought I'd update my kernel build, but 'MACHINE=onyx bb linux-oneplus-onyx' won't work. It doesn't like MACHINE=onyx. Please remind me what I am missing. Dec 31 11:53:33 elvispre: You need to add the meta-oneplus layer to bblayers Dec 31 11:53:35 Let me find it Dec 31 11:54:14 Similar to: https://github.com/webOS-ports/webos-ports-setup/commit/ab5eea3b82ade63d58e60b934d281db2ce6a5ff8 Dec 31 11:54:18 Herrie: Sorry. I put everything back like it was. Dec 31 11:54:21 Just add meta-oneplus Dec 31 12:03:09 elvispre: Let me add them to webos-ports-setup Dec 31 12:07:32 elvispre: Ok it's there now Dec 31 12:07:59 Herrie: Thanks. It will save me remembering! Dec 31 12:19:38 If you follow building steps and do the make update etc it should pick up the new layers Dec 31 12:19:43 I.e. $ make update-conffiles && make update Dec 31 12:21:45 Herrie: bitbake is pretending to build things that I know should not build (vanilla onyx cm-14.1, for example) so I am going "scorched earth" on it and starting again from scratch. Dec 31 12:23:20 Hehe LOL Dec 31 12:23:54 Have you noticed that make update often suggests to run update-conffiles but then turns out to have done it itself? Dec 31 12:24:29 So make update && make update is much the same thing. Dec 31 12:26:08 Herrie: think halium should be sorted, will (hopefully) check it tomorrow to confirm they've been rotate correctly Dec 31 12:47:48 novaldex: Thnx Dec 31 12:47:55 elvispre: Yeah bb sometimes is a bit weird Dec 31 12:50:33 elvispre: Doing the onyx here locally too Dec 31 12:50:40 So in case you have issues I can help ;) Dec 31 12:51:38 Herrie: Thanks. Fair warning though: I haven't finished reading my paper yet so I may go and do that shortly. Dec 31 13:30:34 elvispre: OK ;) Dec 31 13:30:41 Kernel failing with missing header file for gcc6 Dec 31 13:30:44 That makes sense Dec 31 13:31:09 Since I use the Halium one without patches Dec 31 13:31:58 Let me fix that properly, not your hacky way :P Dec 31 13:32:07 And PR patches upstream to Halium Dec 31 13:35:03 * elvispre is outraged! Dec 31 13:35:19 :-) Dec 31 14:14:02 elvispre: LOL ;) Well we just have a standard set of patches we apply, so it's good to keep them consistent :P Dec 31 19:23:04 Herrie: So I got my boot loop but your adb pull command does not pull anything that exists. /sys/fs does not contain a folder called pstore. Dec 31 19:38:11 elvispre: Hmmz ah could be it uses the last_kmesg Dec 31 19:38:37 You have something in /proc/last_kmsg ? Dec 31 19:38:57 Android 6+ should have /sys/fs normally Dec 31 19:39:06 AS per https://sites.google.com/site/zhuoweisite/blog/newlocationoflastkmsgonandroid60andabovesysfspstoreconsole-ramoops Dec 31 19:44:01 Herrie: I have /sys/fs but not that content. /proc/last_kmsg does not exist either. I am inclined to think that this may be because this is TWRP not the android system proper. Dec 31 19:45:02 elvispre: Well if your kernel was loaded it should populate /sys/fs Dec 31 19:45:09 Unless we have the kernel addresses etc wrong Dec 31 19:46:30 Which might be the case: https://github.com/shr-distribution/meta-smartphone/blob/pyro/meta-oneplus/recipes-kernel/linux/linux-oneplus-onyx_git.bb#L12 Dec 31 19:46:31 Let me check Dec 31 19:46:32 Herrie: I have five other folders in there; just no pstore folder. Dec 31 19:46:45 elvispre: It's the kernel offset addresses, pretty sure Dec 31 19:46:48 I had the same with my mido Dec 31 19:47:03 Seems I didn't push the correct values to meta-oneplus & meta-xiaomi Dec 31 19:47:07 Let me find them Dec 31 19:47:11 Herrie: Sounds not unlikely ;-) Dec 31 19:48:13 Ah no, it seems OK for OnePlus Dec 31 19:48:22 Not sure where the 8000 value comes frm but all have it Dec 31 19:48:39 https://github.com/LineageOS/android_device_oneplus_onyx/blob/cm-14.1/BoardConfig.mk#L45 Dec 31 19:48:42 So it seems fine Dec 31 19:52:26 Herrie: OK. Well, it's not bricked, so that's a start :-) Dec 31 19:58:46 elvispre: Yes Dec 31 19:58:53 You have CM 14.1 or Android 7.1 on it? Dec 31 19:59:16 I remember I had no logs, turned out I had Android 6 instead of 7 and was trying CM 14.1 which is Android 7.1 based :P Dec 31 20:12:30 Herrie: It is LineageOS. So I think that means CM 14.1 Dec 31 20:34:14 Yup Dec 31 20:34:28 I just had this MIUI on the Redmi Note 4 Dec 31 20:34:46 And they have their own numbering... Ie MIUI 8 = Android 6, MIUI 9 = Android 7 :P Dec 31 20:40:18 OnePlus do OxygenOS. I already established that I can easily flash between that and LineageOS. **** ENDING LOGGING AT Mon Jan 01 03:00:00 2018