**** BEGIN LOGGING AT Tue Dec 12 03:00:01 2017 Dec 12 06:13:29 Morning Dec 12 06:13:46 A new pstore output: https://bpaste.net/show/53fa1c1ee8d6 Dec 12 06:28:09 last kmesg still empty btw Dec 12 10:17:09 Morning! Dec 12 10:18:43 Morning! Dec 12 10:33:14 Tofe: Is there a way to just test the kernel without the whole image? Dec 12 10:34:33 fastboot boot myboot.img Dec 12 10:34:43 (when in fastboot menu) Dec 12 10:38:35 Tofe: OK\ Dec 12 10:38:42 Then I should at least get a kmesg right? Dec 12 10:39:21 I should take the .fastboot file? Dec 12 10:41:08 Herrie|Laptop: no, take the .bin (there should be a xxx-fastboot.bin iirc) Dec 12 10:41:17 ah no wait, you're right Dec 12 10:41:47 I have a .bin and a .fastboot Dec 12 10:41:56 .fastboot is a bit bigger Dec 12 10:42:02 yes, that's the good one, sorry :) Dec 12 10:42:31 you'll eventually get a kmsg, but you'll only see it when rebooting in recovery as a last_kmsg Dec 12 10:54:33 Tofe: FAILED (remote: dtb not found) Dec 12 10:54:38 That might explain a lot Dec 12 10:59:02 Seems I might need to set KERNEL_DEVICETREE Dec 12 10:59:20 Ah for pyro still include this: https://github.com/openembedded/openembedded-core/blob/pyro/meta/recipes-kernel/linux/linux-dtb.inc Dec 12 11:00:20 Seems this gives some hints: https://stackoverflow.com/questions/37347808/how-to-use-an-own-device-tree-and-modified-kernel-config-in-yocto Dec 12 11:45:28 Herrie|Laptop: the N5 kernel is also a dtb kernel, if that helps Dec 12 11:45:57 Tofe: Hmmz let me check Dec 12 14:23:54 Tofe: Seems I need a Image.gz-dtb instead of Image :P Dec 12 14:23:57 As per https://github.com/piggz/android_kernel_xiaomi_msm8953/blob/pgz-14.1-eb8/arch/arm64/Kconfig#L955 Dec 12 14:24:03 That might help Dec 12 14:26:49 Tofe: How do I come up with fstab & udev rules for a target? Dec 12 14:32:12 fstab I did it by hand; udev rules I quite don't remember, maybe I copied it from someone else at SFOS Dec 12 14:46:03 Tofe: OK Dec 12 16:56:38 Tofe: OK got a new file to play with when home Dec 12 16:56:50 \Ehm I can play with it now, just cannot pull logs due to vendor keys Dec 12 16:57:03 Not sure how to fix that Dec 12 16:57:24 VENDOR KEYS in ADB that is Dec 12 16:57:36 I.e. I approved my home PC in Android while I still had Android on it, but not my laptop Dec 12 16:57:43 So cannot ADB on my laptop into it it seems :P Dec 12 18:08:46 Herrie|2: if you can boot on android, you could authorize adb logging from there, maybe? Dec 12 18:32:14 Tofe: Need to flash Android back for that Dec 12 18:32:16 :P Dec 12 20:07:41 Herrie|2: you just need the kernel image, and you can boot it with fastboot ;) Dec 12 20:37:53 Tofe: Ah OK Dec 12 20:38:06 Tofe: Hmmz my /proc/last_kmsg still empty Dec 12 20:38:50 The /sys/fs/pstore/dmesg-ramoops-0 seems some binary file Dec 12 20:38:53 Any ideas? Dec 12 20:38:58 It seems to boot and reboot Dec 12 20:39:02 So it does something Dec 12 20:39:04 I..e bootloops Dec 12 20:39:14 But nothing in /proc/last_kmsg :S Dec 12 20:39:31 I shouldn't need to specify offsets etc when I do fastboot boot right? Dec 12 20:59:05 I mean fastboot manual says: https://bpaste.net/show/f311d4f749ef Dec 12 21:00:05 I do "fastboot boot Image.gz-dtb-mido.fastboot". It says downloading 'boot.img'..., OKAY, booting... Dec 12 21:00:17 Then after some seconds it boots Dec 12 21:00:34 Then it fails and reboots and I hold volume up to go into TWRP Dec 12 21:00:46 And try to pull /proc/last_kmsg from there? Dec 12 21:48:27 Tofe: Or maybe I miss a step somewhere? But I understood that's how it should be done & pulled? **** ENDING LOGGING AT Wed Dec 13 03:00:01 2017