**** BEGIN LOGGING AT Wed Mar 13 02:59:57 2019 Mar 13 07:21:37 Morning! Mar 13 07:22:00 I am also Mar 13 07:22:35 Seeing a screen blanking issue on Tissot, by the way. Mar 13 07:24:09 If the screen goes blank - by timeout or by power button - that's it. It's blank and I don't know a way to turn it back on. Mar 13 08:51:58 Morning! Mar 13 08:52:29 elvispre: My mako is dead (red led issue). Don't remember what happened though anymore. I think my repair that went wrong. Mar 13 08:58:18 Been a while since I looked at it. Just found it yesterday while searching for some other things in some boxes. Mar 13 09:02:32 Probably recoverable, however not really my priority at the moment. Mar 13 09:29:06 Morning Mar 13 12:11:29 o/ Mar 13 12:11:43 btw. my error from a couple of days ago: Mar 13 12:11:44 ERROR: luneos-dev-package-1.0.2+gitAUTOINC+12c8eb4d79-r0 do_deploy: Required base image is not available as tar.gz image! /src/LuneOS/webos-ports-env/webos-ports/tmp-glibc/deploy/images/intel-corei7-64/luneos-dev-image-intel-corei7-64.tar.gz doesn't exist. Mar 13 12:11:44 ERROR: luneos-dev-package-1.0.2+gitAUTOINC+12c8eb4d79-r0 do_deploy: Function failed: do_deploy (log file is located at /src/LuneOS/webos-ports-env/webos-ports/tmp-glibc/work/intel_corei7_64-webos-linux/luneos-dev-package/1.0.2+gitAUTOINC+12c8eb4d79-r0/temp/log.do_deploy.8367) Mar 13 12:11:44 ERROR: Logfile of failure stored in: /src/LuneOS/webos-ports-env/webos-ports/tmp-glibc/work/intel_corei7_64-webos-linux/luneos-dev-package/1.0.2+gitAUTOINC+12c8eb4d79-r0/temp/log.do_deploy.8367 Mar 13 12:11:44 ERROR: Task (/src/LuneOS/webos-ports-env/webos-ports/meta-webos-ports/meta-luneos/recipes-core/images/luneos-dev-package.bb:do_deploy) failed with exit code '1' Mar 13 12:11:53 and this time the initrd looks a lot different Mar 13 12:11:59 so any one knows what's missing ? Mar 13 12:12:14 i think if i generate an iso this time ithnk it will build Mar 13 12:12:52 the hdd image the ext4 image of the rootfs have been generated Mar 13 12:27:29 saidinesh5: it looks like you would just have to add an image type to your machine conf file Mar 13 12:27:52 but i don't have a machine conf file... i mean i was using meta-intel Mar 13 12:28:09 https://github.com/Tofee/meta-smartphone-1/blob/sumo/meta-lg/conf/machine/hammerhead.conf#L49 Mar 13 12:28:14 ah, mmh Mar 13 12:28:27 So i have no option but to create meta-intel-luneos Mar 13 12:28:41 although Tofe could you suggest a name for my layer? Mar 13 12:28:51 like the work would be for mostly cherrytrail tablets Mar 13 12:28:58 but maybeuseful for a lot of other devices Mar 13 12:29:34 not all intel-based devices ? Mar 13 12:30:36 i don't know. i mean older tablets before this one need the 32bit efi thing. so they are out of the window. this may also work on those intel chromebooks, 2-in-1 devices etc.. though Mar 13 12:31:18 if it's generic enough, then meta-intel-luneos seems quite good for a name Mar 13 12:32:33 and machine name? Mar 13 12:33:22 ah, mmmh Mar 13 12:33:36 what's the codename of your device? Does it have one? Mar 13 12:33:59 not even sure actually it is a nuvision 8 inch but it is one of the bazillion clones out there Mar 13 12:34:22 let me google a bit for the specs Mar 13 12:36:10 would that be cherrytrail-x64 only ? or would the image also work as-is on baytrail-x64, etc ? Mar 13 12:36:13 tm800w610l Mar 13 12:36:28 model number that is Mar 13 12:36:55 I'm looking at https://en.wikipedia.org/wiki/Atom_(system_on_chip) Mar 13 12:38:26 ah it's a baytrail actually Mar 13 12:38:37 http://ark.intel.com/products/87383/ this one Mar 13 12:38:40 oh? Mar 13 12:38:44 cherrytrail i think Mar 13 12:39:00 https://www.amazon.com/gp/product/B01MYZEPGP/ref=ox_sc_act_title_2?smid=A12LTVP7KBAA4&psc=1&pldnSite=1 Mar 13 12:39:30 oh, ahah, I found https://www.amazon.com/NuVision-8-inch-Touchscreen-Quad-Core-Processor/dp/B01H3B17R8 , what a mess these devices... Mar 13 12:40:17 ok, but let's try cherrytrail.conf then Mar 13 12:40:32 it's always 64bit anyway so let's drop that part Mar 13 12:41:41 Ah it is cherrytrail but it will work for all subsequent intel devices too Mar 13 12:43:16 mmh Mar 13 12:44:30 There's often an upward compatibility anyway with intel, so we'll have to choose... Mar 13 12:44:57 I just hesitate: cherrytrail ? airmont ? cherryview ? Mar 13 12:45:30 * saidinesh5 checks Mar 13 12:45:36 intel64tablet ? Mar 13 12:46:04 like the machine i currently use is: intel-corei7-64 Mar 13 12:46:14 so maybe intel64-tablet ? Mar 13 12:46:18 oooh wait Mar 13 12:46:33 there one more point: the machines should also have the same display Mar 13 12:46:48 Ahh Mar 13 12:46:54 which in this case means a very specific name Mar 13 12:47:07 then it would probably mean intel-cherrytrail-tablet i think Mar 13 12:47:44 but how would you do this for raspberry pi then? Mar 13 12:47:46 but they don't always have the same display size & DPI Mar 13 12:47:50 they don't have the same display right? Mar 13 12:48:04 right, let's see Mar 13 12:48:18 it's mainly the luna-next that is affected Mar 13 12:48:22 Ahh Mar 13 12:48:30 shouldn't luna-next be resolution independent? Mar 13 12:49:43 yes but at some point you have to choose one Mar 13 12:50:02 that's done in luna-platform.conf, which is machine dependant Mar 13 12:50:20 interesting... Mar 13 12:50:31 but for rpi you have a point Mar 13 12:51:07 plus this one even has an hdmi out.. so can't exactly select one display Mar 13 12:52:25 https://github.com/webOS-ports/meta-webos-ports/blob/pyro/meta-luneui/recipes-luneui/luna-next/luna-next-conf/raspberrypi2/environment.conf#L4 Mar 13 12:53:10 I see Mar 13 12:54:00 can't this query the display physical size from driver or something/ Mar 13 12:54:50 $ xdpyinfo | grep dimensions Mar 13 12:54:50 dimensions: 3440x1440 pixels (910x381 millimeters) Mar 13 12:54:52 on my desktop Mar 13 12:55:25 yes, on modern screens the EDID can be retrieved... and is correct Mar 13 12:55:41 but on embedded screens, I have some doubts Mar 13 12:56:09 Though it could be an interesting improvement to have these settings more dynamic Mar 13 12:56:19 And just propose a default resolution Mar 13 12:56:21 Ahh but this is technically a "modern screen" yeah Mar 13 13:00:20 ok let's try intel64-tablet, or cherrytrail-tablet. We'll configure it to fit your device for now, and later we'll try to devise a more dynamic way of configuring the display Mar 13 13:01:05 Aye Mar 13 13:02:37 in worst case we'll just rename it "nuvision8" :) Mar 13 13:03:39 yep Mar 13 13:04:04 Can i somehow base my machine on top of the intel-corei7-64 ? Mar 13 13:04:12 instead of having to define this all over Mar 13 13:04:18 is there a .inc ? Mar 13 13:04:52 2. include the following line in the machine configuration file Mar 13 13:04:52 require conf/machine/include/meta-intel.inc Mar 13 13:05:18 voilĂ  Mar 13 13:06:16 you could try a "require intel-corei7-64.conf", but not sure if bb will accept this Mar 13 13:06:22 Ahh Mar 13 13:11:06 btw. what is .wic file? Mar 13 13:11:21 never saw that one before Mar 13 13:11:51 IMAGE_FSTYPES += "wic" Mar 13 13:11:51 WKS_FILE ?= "${@bb.utils.contains_any("EFI_PROVIDER", "systemd-boot rmc-boot", "systemd-bootdisk-microcode.wks", "grub-bootdisk-microcode.wks", d)}" Mar 13 13:14:41 looks like a partitionned image Mar 13 13:15:09 btw. what is this for? Mar 13 13:15:10 https://github.com/Tofee/meta-smartphone-1/blob/sumo/meta-lg/conf/machine/hammerhead.conf#L32 Mar 13 13:15:18 PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg" Mar 13 13:15:23 Ahh Mar 13 13:15:26 "All that wic does is assemble a disk image with partitions specified in kickstart file." Mar 13 13:15:33 i removed the partitioned image then Mar 13 13:15:50 IMAGE_FSTYPES += "tar.gz ext4 iso" ? Mar 13 13:15:54 http://lists.openembedded.org/pipermail/openembedded-core/2016-November/128749.html Mar 13 13:15:55 (i need a bootable iso) Mar 13 13:16:16 yes, looks fine; though I don't know how bootable it'll be Mar 13 13:16:29 lol Mar 13 13:18:05 WARNING: Layer intel-luneos should set LAYERSERIES_COMPAT_intel-luneos in its conf/layer.conf file to list the core layer names it is compatible with. Mar 13 13:18:06 WARNING: Layer intel-luneos should set LAYERSERIES_COMPAT_intel-luneos in its conf/layer.conf file to list the core layer names it is compatible with. Mar 13 13:18:09 any fix for that? Mar 13 13:19:36 Ahh Mar 13 13:19:37 1 sec Mar 13 13:19:42 need a layer.conf Mar 13 13:19:52 try to copycat https://github.com/webOS-ports/meta-rpi-luneos/blob/pyro/conf/layer.conf Mar 13 13:25:04 https://bpaste.net/show/492a9ad52789 Mar 13 13:25:22 added that from intel itself Mar 13 13:26:06 it is repackaging all the existing packages for this machine.. nice Mar 13 13:26:11 there's an issue Mar 13 13:26:16 layer.conf btw. Mar 13 13:26:17 oh? Mar 13 13:26:45 meta-intel-luneos should appear above meta-intel, not below: you want to specialize meta-intel, not the opposite Mar 13 13:27:20 Oh.. Mar 13 13:27:33 how do i fix it? Mar 13 13:27:57 BBFILE_PRIORITY_intel = "5" <-- what is your priority? Mar 13 13:28:11 so should i change it to 6? Mar 13 13:28:14 or 4? Mar 13 13:28:25 https://bpaste.net/show/eac3e8fe9836 my layer.conf Mar 13 13:29:15 put "10", just for a little margin Mar 13 13:30:05 and it should be _intel-luneos, not _intel Mar 13 13:30:25 same for COLLECTIONS Mar 13 13:30:34 (iirc) Mar 13 13:30:43 https://bpaste.net/show/f4de3c1134e8 ? Mar 13 13:30:45 oh Mar 13 13:31:22 https://bpaste.net/show/024407ed08cc Mar 13 13:31:35 yep, looks good Mar 13 13:32:15 starting another build then Mar 13 13:34:41 https://bpaste.net/show/df66d419c05f Mar 13 13:34:59 still the same Mar 13 13:35:20 oh btw. forgot to mention.. I think the chromium build used in webosose has those intel optimisations i was looking for Mar 13 13:36:01 mmmh what could it be here... Mar 13 13:37:33 dunno Mar 13 13:38:30 JaMa: ^ any idea ? Mar 13 13:38:40 * Tofe tries invocation... Mar 13 13:40:44 I think you can drop LAYERDEPENDS and LAYERRECOMMENDS in your layer Mar 13 13:41:04 but that won't help much for the current issue Mar 13 13:44:01 i think tomorrow my ram will double.. so these odd freezes should disappear Mar 13 13:44:25 do "bitbake-layers show-layers " ? Mar 13 13:44:57 umm in 3-5 minutes.. it is stuck compiling kernel Mar 13 13:45:25 task 6147 out of 6190 Mar 13 13:56:26 ERROR: luneos-dev-package-1.0.2+gitAUTOINC+12c8eb4d79-r0 do_deploy: Required kernel image is not available as zImage fastboot image! /src/LuneOS/webos-ports-env/webos-ports/tmp-glibc/deploy/images/intel64-tablet/bzImage-intel64-tablet.fastboot doesn't exist. Mar 13 13:56:26 ERROR: luneos-dev-package-1.0.2+gitAUTOINC+12c8eb4d79-r0 do_deploy: Function failed: do_deploy (log file is located at /src/LuneOS/webos-ports-env/webos-ports/tmp-glibc/work/intel64_tablet-webos-linux/luneos-dev-package/1.0.2+gitAUTOINC+12c8eb4d79-r0/temp/log.do_deploy.29650) Mar 13 13:56:26 ERROR: Logfile of failure stored in: /src/LuneOS/webos-ports-env/webos-ports/tmp-glibc/work/intel64_tablet-webos-linux/luneos-dev-package/1.0.2+gitAUTOINC+12c8eb4d79-r0/temp/log.do_deploy.29650 Mar 13 13:56:29 bah Mar 13 13:57:26 okay.. Mar 13 13:59:01 There seems to be an issue between what KERNEL_IMAGETYPE specifies and what your kernel recipe produces Mar 13 14:00:51 btw. https://bpaste.net/show/91d4c5414a76 Mar 13 14:00:58 the bitbake-layers one Mar 13 14:03:38 it quite doesn't like your tar.gz ! Mar 13 14:05:40 can you paste your intel64-tablet.conf ? Mar 13 14:06:15 1 sec Mar 13 14:07:47 https://bpaste.net/show/a1e218f244d4 Mar 13 14:08:27 mmh where does the tar.gz come from? Mar 13 14:09:27 (and your "APPEND" line is weird, are you sure it's the right variable?) Mar 13 14:10:03 (ah, it comes directly from http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/conf/machine/intel-corei7-64.conf?h=master#n36 ... weird.) Mar 13 14:10:48 So i add the tar.gz? Mar 13 14:14:07 no, it's already there, but I just don't know where it comes from Mar 13 14:16:33 ahhj Mar 13 14:17:08 or it could be I misunderstood completely the error. It's the first time I see it... Mar 13 17:47:30 bshah: ping Mar 13 17:48:32 bshah: I wondered, what kind of rasterizer do you use on mainline hammerhead? swrast ? I just can't get it to work... Mar 13 17:51:34 ah, nevermind, I just found https://gitlab.com/postmarketOS/pmaports/commit/8a158f6fe80cf70755ba3957d37d49374e33a5f3 Mar 13 20:45:32 suprise! https://www.dropbox.com/s/l8ocij8mk015wog/hammerhead-homescreen.jpg?dl=0 Mar 13 20:49:38 bshah: ^ and that's with Mesa 17.3 Mar 13 20:51:41 Now the only thing that I didn't put into recipes are the adreno firmwares; I just copied them from our Halium image Mar 13 20:52:27 Also, it's super-unstable: luna-next often crashes Mar 13 21:26:25 wow.. luna-next boots foryou already!? Mar 13 21:26:49 sweet Mar 13 21:36:26 yep ! I was faster, hehe Mar 13 21:37:19 saidinesh5: https://github.com/Tofee/meta-webos-ports/commit/84ce7d19a6e578232f0193b94ec919b0ee5bcb81 this might be useful for you too, at some point -- even if you don't use freedreno Mar 13 21:38:04 ^ I'll try to move most of it into meta-smartphone, where it rightly belongs Mar 13 21:43:21 Ahh Mar 13 21:52:03 this thing needs a lot of hard drive space doesn't it **** ENDING LOGGING AT Thu Mar 14 02:59:57 2019