**** BEGIN LOGGING AT Sun Dec 09 03:00:02 2018
Dec 09 07:05:51 <Herrie|Laptop> JaMa/elvispre: I suspect systemd 234 is the culprit
Dec 09 07:06:05 <Herrie|Laptop> Usually it's systemd which causes headaches on Yocto upgrades
Dec 09 07:06:35 <Herrie|Laptop> Because systemd guys don't care about embedded/mobile socs and assume every runs a 4.x kernel
Dec 09 07:07:12 <Herrie|Laptop> Easiest would be to create a build with systemd 232 from Pyro
Dec 09 07:27:24 <JaMa> elvispre: Herrie|Laptop: thanks
Dec 09 07:28:09 <JaMa> Herrie|Laptop: lets see with Rocko first
Dec 09 07:29:03 <JaMa> unfortunately bonaire builder went down
Dec 09 07:29:05 <JaMa> SSH Connection failed with IOException: "No route to host (Host unreachable)".
Dec 09 07:29:12 <JaMa> novaldex|away: ^ any idea why?
Dec 09 07:40:33 <Herrie|Laptop> JaMa: Usually a systemd downgrade fixes things, but not always
Dec 09 07:52:53 <JaMa> pyro 232, rocko 234, sumo 237, thud 239
Dec 09 07:53:01 <JaMa> that's why I want to try rocko with 234 first
Dec 09 07:53:21 <JaMa> but for that we need to get the builder back online
Dec 09 07:53:39 <JaMa> the builds I've triggered yesterday all failed (for some reason)
Dec 09 07:57:13 <Herrie|Laptop> JaMa: Didn't the images that elvispre tested already have 234?
Dec 09 07:57:34 <Herrie|Laptop> Ah that was Sumo
Dec 09 07:57:37 <Herrie|Laptop> Need more coffee :P
Dec 09 09:15:07 <elvispre> :-)
Dec 09 09:34:37 <JaMa> need to fix rocko as well ERROR: Layer qt5-layer is not compatible with the core layer which only supports these series: rocko (layer is compatible with sumo thud)
Dec 09 10:00:40 <Tofe> Morning
Dec 09 10:01:13 <Tofe> Herrie|2: did you manage to adb into the black-screen-touchpad ? On my side I don't get life sign at all
Dec 09 10:01:30 <Tofe> It seems to be blocked in the ramdisk
Dec 09 10:01:51 <Tofe> but I just can't get the output...
Dec 09 11:07:13 <Herrie|2> Tofe: Same here
Dec 09 11:22:38 <Tofe> Herrie|2: it's quite inconvenient. I'll try with a Decaf uImage, just in case.
Dec 09 11:29:00 <Tofe> ok, Decaf boots
Dec 09 11:30:08 <Tofe> but the testing image I had from back in May already didn't boot (with the same kernel), so it must be a ramdisk change
Dec 09 11:31:35 <nizovn> anything useful in last_kmsg?
Dec 09 11:31:49 <Tofe> nizovn: I don't know yet
Dec 09 11:39:52 <Tofe> got it! https://bpaste.net/show/9a9d7366828b
Dec 09 11:40:39 <Tofe> it looks like everything goes wrong
Dec 09 11:41:12 <Tofe> "initrd: WARNING: Android system image not found" is probably the root cause
Dec 09 11:41:35 <elvispre> That does sound like a bit of a show stopper :)
Dec 09 11:41:44 <Tofe> and if it tries to find it in /dev/mapper/store-media, it'll fail indeed
Dec 09 11:41:59 <Tofe> in my case, it's in /dev/mapper/store-luneos-root
Dec 09 11:43:09 <Tofe> looks like we've overlook that part when migrating our init.sh script to Halium
Dec 09 12:00:51 <Tofe> Ok, I think I found the possible cause: in Halium's init they changed the $syspart variable name to $_syspart
Dec 09 12:01:08 <Tofe> but we set that variable ourselves for tenderloin, just the wrong name, so...
Dec 09 12:04:25 <Tofe> proposal (non tested yet): https://github.com/shr-distribution/meta-smartphone/pull/90
Dec 09 12:08:35 <Tofe> JaMa: ^ I think we can merge that one, it's tenderloin specific and the latter is already broken anyway
Dec 09 12:09:00 <Tofe> that way we can start a tenderloin build, and everyone can try the new uImage
Dec 09 12:35:56 <Tofe> ok it works better, but not perfect still
Dec 09 12:43:30 <Herrie|2> Tofe: Better as in it boots but other issues?
Dec 09 13:11:01 <Tofe> Herrie|2: better as in I can get to adb
Dec 09 13:11:37 <Tofe> but I still get an abnormal log for Halium's boot
Dec 09 13:48:55 <Tofe> oh, no, my TP ran out of battery just when I wanted to test an image...
Dec 09 13:52:50 <Tofe> could someone test https://www.dropbox.com/s/1dwjopg6vlt1o4n/uImage--3.4.106%2Bgitr7%2Bece92940da-r0.3-tenderloin-20181209133428-0-0.bin?dl=0 ? md5sum = f0e7c877066c63f6c9fd8fe8cda2f0e7
Dec 09 13:53:21 <Tofe> otherwise, well, we'll just wait for my TP to recharge :)
Dec 09 14:09:41 <Tofe> ok, it works :)
Dec 09 14:10:01 <Tofe> Could we push that file somewhere where it can be pointed by our wiki ?
Dec 09 14:11:15 <Tofe> https://github.com/webOS-ports/meta-webos-ports/pull/308 <-- this is the second part of the fix.
Dec 09 14:11:41 <Tofe> I had a luna-service2 bump in the pipe, it's unexpected -- let me see what it is...
Dec 09 14:13:12 <Tofe> ah, yes, it's weird that it's not already there
Dec 09 23:41:43 * elvispre rolls his eyes
Dec 09 23:42:16 <elvispre> Having disabled the qcom time_daemon and got ubports timekeeper onto tissot
Dec 09 23:42:39 <elvispre> now I find that timesync is working after all.
Dec 09 23:43:40 <elvispre> A combination of systemd-timesyncd and phone network, I suppose.
Dec 09 23:45:12 <elvispre> (OK. There is timekeeper. Time seems to be correct. But I haven't run it yet!)
Dec 09 23:47:28 <elvispre> This is webOS OSE-based LuneOS, by the way, so this is very much a good thing.
**** ENDING LOGGING AT Mon Dec 10 03:00:00 2018