**** BEGIN LOGGING AT Sun Feb 11 03:00:01 2018 Feb 11 05:17:37 thejsa: vve-goudenleeuw.nl/luneos-dev-package-athene-20180210211703-0-0.zip Feb 11 05:18:02 Expect dragons on a first try but it's good to get logs etc to see what needs fixing Feb 11 10:04:11 4:55AM... ouch... Feb 11 10:04:14 Morning! Feb 11 10:52:28 Tofe: 4:55 what :P? Feb 11 10:53:59 Morning BTW Feb 11 10:56:19 "Herrie: [04:55:33] Expect dragons" Feb 11 10:57:54 I think it was a bit later but well :P Someone decided that 5:45 was a nice time to wake up on a Sunday... Been like this whole week :P Feb 11 10:58:07 Anywhere between 4:30 and 6:00 :P Feb 11 10:59:17 hehe :) Feb 11 10:59:43 Seems my builder has issues again :'( Feb 11 10:59:54 I guess it'll be time for a new one sometime... Feb 11 11:00:41 It's stuffed away and normally can VNC in, but doesn't work now... So should hook it up to a screen and kb it seems :P Feb 11 11:02:30 Already tried some reboots but little luck so far... Feb 11 11:02:52 Guess I'll hook it up later when I get a chance :) Feb 11 11:26:59 Herrie: About to flash - should it be over Lineage 14.1, I assume? Feb 11 11:40:40 thejsa: Yup Feb 11 11:40:54 Alright Feb 11 11:43:31 "Installation completed, please reboot!" looks good so far (: Feb 11 11:43:55 Fastboot errors out Feb 11 11:44:32 Fastboot errors? Feb 11 11:44:33 Herrie: "Error: failed to load kernel!" Feb 11 11:44:33 "Fastboot Reason: Fall-through from normal boot mode" Feb 11 11:45:09 I wiped system, data, cache, flashed latest Lineage 14.1 and then immediately flashed the luneos zip you sent earlier today Feb 11 11:51:21 (Using twrp - I'll try flashing the boot.img using fastboot now) Feb 11 11:54:11 thejsa: You need to adb sideload the zip from twrp Feb 11 11:54:25 Then reboot Feb 11 11:54:25 That should work Feb 11 11:54:40 I'm a little confused Feb 11 11:54:45 I had the zip on an SD Feb 11 11:55:58 The rootfs flashed fine though (: /data/luneos Feb 11 11:56:26 oh I see, one second Feb 11 11:58:04 In case it bootloops, go back into twrp and pull console-ramoops with adb pull /sys/fs/pstore/console-ramoops Feb 11 11:58:34 Should I wipe sys data cache and start again with fresh Lineage Feb 11 11:58:41 then sideload luneos Feb 11 11:58:57 Shouldn't be necessary really Feb 11 11:59:00 okay Feb 11 12:02:34 yeah still failed to load kernel after sideloading luneos instead of flashing Feb 11 12:02:59 What you mean by failed to load kernel? Feb 11 12:03:15 The bootloader gives me an error saying "failed to load kernel" Feb 11 12:03:25 It doesn't like the boot image maybe Feb 11 12:03:55 Hmmz Ok Feb 11 12:04:15 It could be I have some of the offsets wrong somehow Feb 11 12:04:24 Anything I can do here to assist? Feb 11 12:05:03 You could extract boot.img and in fastboot do a fastboot boot boot.img Feb 11 12:05:20 But suspect that'll give same result Feb 11 12:05:25 It does, yeah Feb 11 12:06:02 I suppose it wouldn't hurt to try a stock lineage boot.img c: Feb 11 12:06:34 You can always try Feb 11 12:07:24 If it hard fails on kernel could be I have some offsets wrong Feb 11 12:07:25 okay so it accepts that Feb 11 12:07:31 a stock android boot.imd will just boot your android install Feb 11 12:07:42 yeah I imagine so Feb 11 12:07:45 it's just booting lineage Feb 11 12:16:00 thejsa: I'd need to check boot.img offsets I guess Feb 11 12:16:15 Would a stock boot.img help ? Feb 11 12:16:19 You could compare the LineageOS ones with ourss Feb 11 12:16:22 Yeah Feb 11 12:16:33 There are some tools that can help Feb 11 12:16:37 I also have a sailfish hybris boot img Feb 11 12:16:46 Tofe: mkbootimg right? Feb 11 12:16:59 Yeah I guess we could analyze those Feb 11 12:17:05 right Feb 11 12:20:03 http://files.muffinti.me/LuneOS/ Feb 11 12:20:55 Herrie: uploaded the boot images there Feb 11 13:09:38 thejsa: Thnx, got some guests now, will check later Feb 11 13:09:46 okay, have fun Feb 11 13:10:07 offsets seem to match btw so guessing it's something else Feb 11 13:14:43 thejsa: Could be cmdline then I guess Feb 11 13:15:07 looking at dt.img at the moment since I can't seem to repack a working lineage boot.img Feb 11 13:28:40 Herrie: for when you get back, issue is that the boot.img doesn't include the dt.img Feb 11 13:28:56 yourkernelsources/scripts/dtbTool -s 2048 -o arch/arm/boot/dt.img -p scripts/dtc/ arch/arm/boot/ Feb 11 13:52:26 thejsa: the output image type isn't "dtb" ? Feb 11 13:52:46 I mean, in the machine conf Feb 11 13:52:57 There isn't a machine.conf present in the rootfs either Feb 11 13:52:59 init fails Feb 11 13:53:12 got it booting to that stage though so Feb 11 13:54:05 (by substituting in Lineage's dtb, using luneos kernel - it works but bootloops after init fails since it can't find machine.conf) Feb 11 13:54:46 https://github.com/Herrie82/meta-smartphone/blob/herrie/huawei/meta-huawei/conf/machine/angler.conf#L38 weird, it's that one isn't it ? Feb 11 13:54:58 motorola/athene Feb 11 13:55:04 oh, oops :) Feb 11 13:55:25 :) Feb 11 13:55:32 https://github.com/Herrie82/meta-smartphone/blob/herrie/huawei/meta-motorola/conf/machine/athene.conf#L38 ok that one is wrong, then Feb 11 13:55:55 I'll make a pr Feb 11 13:55:57 zImage-dtb Feb 11 13:56:00 yep Feb 11 13:56:02 thanks Feb 11 13:56:38 meanwhile what should machine.conf contain ? Feb 11 13:57:16 hold on wait that's weird Feb 11 13:57:40 I am silly Feb 11 13:57:48 :p Feb 11 13:59:01 I'll pull console-ramoops Feb 11 13:59:08 it bootloops at this point Feb 11 14:01:09 this is probably because I'm using the 'wrong' dt.img tbh Feb 11 14:03:04 https://gist.github.com/thejsa/d4b9a2dd373003a2c9cf57ce23938f4d ramoops logs Feb 11 14:06:58 can't find /init Feb 11 16:13:43 * elvispre is trying out his new build machine. Turns out the build breaks if you haven't configured git first. Feb 11 16:21:52 thejsa: Thanks for this! Feb 11 16:21:57 I'll try to fix some things Feb 11 16:21:57 np Feb 11 16:22:50 there's a PR on your meta-smartphone fork to fix the kernel image type Feb 11 16:34:33 thejsa: I guess you could suffice with a new fastboot image ;) Feb 11 16:34:37 THat's a lot smaller :) Feb 11 16:34:49 certainly (: Feb 11 16:35:01 although it can't find init, haha Feb 11 16:35:08 Hmmz my builder is really acting up... Shutting down all the time... Feb 11 16:35:19 thejsa: Well that could be because of your franken file ;) Feb 11 16:35:23 init issues are probably due to the frankenstein boot.img I used yeah Feb 11 16:35:34 fun fun fun Feb 11 16:56:48 In theory, it should be possible to have LuneOS coexist with Android by simply switching the boot.img right? Feb 11 17:15:09 Herrie: I had to stop using regular Ubuntu 16.04 for builds because X (or Wayland?) was dying all the time and dumping me back at the login screen. Feb 11 17:15:39 Herrie: Switching to 16.04 MATE worked around that. Feb 11 17:17:22 thejsa: Yes Feb 11 17:17:40 okay, that's good Feb 11 17:18:26 perhaps this is something that could be automated Feb 11 17:20:13 thejsa: For this multirom exists Feb 11 17:20:28 We'd neeed to do some work to support that Feb 11 17:21:48 thejsa: http://vve-goudenleeuw.nl//zImage-dtb-athene.fastboot Feb 11 17:25:03 that's a boot.img right? Feb 11 17:25:24 I'll try to run that in a moment Feb 11 17:25:36 fastboot flash boot fastbootname Feb 11 17:25:48 or even fastboot boot image Feb 11 17:25:50 Then fastboot boot fastbootname Feb 11 17:25:57 Yeah Feb 11 17:30:18 booting now Feb 11 17:30:28 let's see how far this gets us Feb 11 17:31:10 is currently stuck at the manufacturer logo screen but it could well just be booting Feb 11 17:35:11 You could try to adb shell in Feb 11 17:35:15 With me that didn't work Feb 11 17:35:28 But you could also reboot to TWRP and pull the console-ramoops again Feb 11 17:35:39 one moment, it's acting different to expected Feb 11 17:37:46 just flashed it , don't know what it was doing before when it started booting (I guess loading the lineage boot.img?) but now it just says failed to load kernel Feb 11 17:40:31 I'll try repacking it as I've done before Feb 11 17:43:38 Herrie: I don't see a dtb in there for some reason Feb 11 17:43:53 do you have a dt.img file somewhere? Feb 11 17:44:24 or a dtb set in your source tree Feb 11 17:44:34 should be in arch/arm/boot/ Feb 11 17:59:47 thejsa: Weird, setting this in the image should sort it really Feb 11 18:00:00 That's why I prefer to flash boot ;) Feb 11 18:00:12 Because when it doesn't boot it acts unpredictable a bit ;) Feb 11 18:00:21 I.e. boots your previous one which can be confusing Feb 11 18:00:33 so I see :) Feb 11 18:01:50 Seems I got an Angler kernel booting as well! Feb 11 18:02:02 s/booting/building Feb 11 18:02:10 fun :) Feb 11 18:05:24 okay so it needs to be a qcdt format dtb Feb 11 18:11:19 I need to see how to do that in Yocto Feb 11 18:11:44 so basically what happens is all the dtb files are appended to the end of the boot.img file it seems Feb 11 18:11:51 Normally we take the image type from boardconfig.mk like https://github.com/piggz/android_device_xiaomi_mido/blob/pgz-14.1/BoardConfig.mk#L43 Feb 11 18:14:12 https://github.com/sonyxperiadev/mkqcdtbootimg Feb 11 18:15:10 also https://github.com/LineageOS/android_device_motorola_athene/blob/cm-14.1/dtbtool/dtbtool.c Feb 11 18:15:23 it seems that you need to basically use a custom dtbtool Feb 11 18:35:14 Can have a look at the AsteroidOS guys, they might have something for a Moto Watch that uses somethingsimilar Feb 11 18:35:52 trying to make the file manually Feb 11 18:36:25 well that very quickly not-worked Feb 11 18:37:07 (bootloop but very rapid cycle) Feb 11 18:40:48 Okay that's interesting Feb 11 18:41:13 I get a 'usb device not recognised' popup in Windows now (stuck at logo.bin display) Feb 11 18:43:08 adb shell? Feb 11 18:43:20 console-ramoops helps too Feb 11 18:43:36 haven't got an adb shell Feb 11 18:43:56 don't seem to be getting ramoops but I'll try again to see if one pops up Feb 11 18:44:22 yeah no console-ramoops dump Feb 11 18:44:35 just a bootloop, probably the way I built the image is messed up Feb 11 18:45:00 i'll try using the kernel from the old zImage-only build and appending the dtb Feb 11 18:54:56 nope still no console-ramoops Feb 11 19:36:19 * elvispre can now build a mako image from scratch in around 2:15 :-O Feb 11 19:38:26 thejsa: Kids will be in be soon, can look then ;) Feb 11 20:41:14 elvispre: Ooh nice! Feb 11 20:42:10 Herrie: It wasn't cheap! Feb 11 20:42:36 It's my birthday next week :-) Feb 11 20:59:59 Ah :D Feb 11 21:00:07 You got a nice new machine to build? Feb 11 21:00:10 I might do the same ;) Feb 11 21:00:33 This one is from 2010 I think, so might need an upgrade Feb 11 21:00:38 Though it works fine most of the time Feb 11 21:05:50 Herrie: I thought my i5-750 was still fairly good, but it was dawning on me that 13+ hours for a build was *not* good. Feb 11 21:07:20 Herrie: I took Tofe's advice that an SSD makes a big difference and threw in an extravagant number of cores (12 hyperthreaded ones). Feb 11 21:07:39 It's a monster! Feb 11 21:22:51 elvispre: Ah OK Feb 11 21:22:58 Well I got a 500GB SSD in mine Feb 11 21:23:00 And 8GB of RAM Feb 11 21:23:12 But it's an old AMD Phenom X6 1055 Feb 11 21:23:17 So not that quick Feb 11 21:23:35 But it's Mini ITX so nice and small Feb 11 21:24:28 Herrie: My CPU cooler may be nearly as big as your PC Feb 11 21:24:41 LOL in this PC too ;) Feb 11 21:25:55 Some Noctua ;) Feb 11 21:26:39 This one is a NH-D15 Feb 11 21:58:48 Got a NH-D14 on mine Feb 11 21:58:59 :) Feb 11 21:59:57 They look more or less the same. **** ENDING LOGGING AT Mon Feb 12 03:00:00 2018