Friday, 2017-01-20

*** thaytan <thaytan!~jan@> has quit IRC00:04
*** thaytan <thaytan!~jan@> has joined #yocto00:06
-YoctoAutoBuilder- build #1023 of build-appliance is complete: Failure [failed BuildImages_1] Build details are at
*** manuel_ <manuel_!~manuel@> has quit IRC00:12
*** nighty <nighty!> has quit IRC00:16
*** thaytan <thaytan!~jan@> has quit IRC00:27
*** JordonWu <JordonWu!~quassel@> has joined #yocto00:33
*** NU-Slacker_ <NU-Slacker_!180d4a9e@gateway/web/freenode/ip.> has joined #yocto00:41
*** thaytan <thaytan!~jan@> has joined #yocto00:41
*** Son_Goku <Son_Goku!> has joined #yocto00:45
*** scottrif <scottrif!> has left #yocto00:45
bluelightninghmm, I was wrong, it's a recent change to the test... testing a fix right now00:45
*** JordonWu <JordonWu!~quassel@> has quit IRC00:54
*** JordonWu <JordonWu!~quassel@> has joined #yocto00:55
-YoctoAutoBuilder- build #1058 of nightly-multilib is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1 BuildImages_4] Build details are at
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC01:02
*** thaytan <thaytan!~jan@> has quit IRC01:03
-YoctoAutoBuilder- build #1056 of nightly-ppc is complete: Failure [failed BuildImages Running ESDK Sanity Tests] Build details are at
*** thaytan <thaytan!~jan@> has joined #yocto01:05
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC01:17
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto01:20
*** thaytan <thaytan!~jan@> has quit IRC01:25
*** JaMa <JaMa!~martin@> has joined #yocto01:31
*** nighty <nighty!> has joined #yocto01:37
*** manuel_ <manuel_!> has joined #yocto01:38
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto01:42
*** rob_w_ <rob_w_!> has joined #yocto01:48
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC01:49
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC01:52
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC01:56
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto02:04
*** thaytan <thaytan!~jan@> has joined #yocto02:05
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC02:25
*** behanw <behanw!uid110099@gateway/web/> has quit IRC02:31
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto02:38
*** morphis_ <morphis_!> has joined #yocto02:40
*** morphis <morphis!> has quit IRC02:44
*** thaytan <thaytan!~jan@> has quit IRC03:09
*** thaytan <thaytan!~jan@> has joined #yocto03:11
*** behanw <behanw!uid110099@gateway/web/> has joined #yocto03:25
*** robert_yang <robert_yang!~lyang1@> has quit IRC04:00
*** robert_yang <robert_yang!~lyang1@> has joined #yocto04:01
*** NU-Slacker_ <NU-Slacker_!180d4a9e@gateway/web/freenode/ip.> has quit IRC04:01
*** thaytan <thaytan!~jan@> has quit IRC04:05
-YoctoAutoBuilder- build #1062 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at
*** thaytan <thaytan!~jan@> has joined #yocto04:39
*** stephano <stephano!~stephano@> has joined #yocto04:50
*** hamis <hamis!~irfan@> has joined #yocto04:51
-YoctoAutoBuilder- build #689 of nightly-deb-non-deb is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #1139 of nightly is complete: Failure [failed] Build details are at
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC05:29
-YoctoAutoBuilder- build #1014 of nightly-ipk is complete: Success [build successful] Build details are at
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto05:31
-YoctoAutoBuilder- build #799 of nightly-oe-selftest is complete: Failure [failed Running oe-selftest] Build details are at
*** Snert___ <Snert___!~snert_@> has joined #yocto05:33
*** Snert_ <Snert_!~snert_@> has quit IRC05:35
*** benjamirc <benjamirc!~besquive@> has quit IRC05:35
*** stephano <stephano!~stephano@> has quit IRC05:35
*** sgw_ <sgw_!sgw_@nat/intel/x-ffsmxzatdjhxorju> has quit IRC05:35
*** stwcx_ <stwcx_!~stwcx@> has quit IRC05:35
*** stwcx <stwcx!~stwcx@> has joined #yocto05:35
*** tripzero_ <tripzero_!~tripzero@> has quit IRC05:35
*** sgw_ <sgw_!~sgw_@> has joined #yocto05:36
*** Snert__ <Snert__!> has quit IRC05:36
*** Circuitsoft <Circuitsoft!4b92a52b@gateway/web/freenode/ip.> has quit IRC05:39
*** Snert <Snert!> has joined #yocto05:39
*** rewitt <rewitt!~rewitt@> has quit IRC05:39
*** rewitt <rewitt!~rewitt@> has joined #yocto05:40
*** benjamirc <benjamirc!~besquive@> has joined #yocto05:40
*** tripzero <tripzero!~tripzero@> has joined #yocto05:41
*** thaytan <thaytan!~jan@> has quit IRC05:44
-YoctoAutoBuilder- build #995 of nightly-deb is complete: Success [build successful] Build details are at
*** Hauke <Hauke!> has quit IRC06:09
*** seebs <seebs!> has quit IRC06:10
*** Hauke <Hauke!> has joined #yocto06:22
*** redengin <redengin!~redengin@2601:600:9200:a356:9593:9709:1d43:dfa1> has quit IRC06:40
*** rob_w_ <rob_w_!> has quit IRC06:48
*** g0ne <g0ne!af649372@gateway/web/freenode/ip.> has joined #yocto06:50
g0neI am building minimal image for Odroid-C1 with custom meta layer. Board boot without error with standalone linux build. But when i use uImage build using yocto, kernel gets crash and there is not log after starting kernel.06:52
*** linulin <linulin!> has quit IRC06:52
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has joined #yocto06:52
g0neI check, standalone linux build and yocto kernel build both have same dtb and .config file. I check diff there is no difference.06:52
g0neyocto uImage and standalone uImage have different file size. What can be difference between two image, except toolchain ?06:53
*** pohly <pohly!> has joined #yocto06:57
*** qt-x <qt-x!~Thunderbi@> has joined #yocto07:00
*** seebs <seebs!> has joined #yocto07:00
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC07:05
-YoctoAutoBuilder- build #1057 of nightly-ppc is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #1090 of nightly-x86-64 is complete: Success [build successful] Build details are at
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto07:07
*** open-nandra <open-nandra!> has joined #yocto07:07
*** agust <agust!> has joined #yocto07:10
*** qt-x <qt-x!~Thunderbi@> has quit IRC07:12
*** qt-x <qt-x!~Thunderbi@> has joined #yocto07:14
-YoctoAutoBuilder- build #593 of nightly-wic is complete: Success [build successful] Build details are at
*** pauldevguy <pauldevguy!~pauldevgu@> has quit IRC07:19
*** redengin <redengin!~redengin@2601:600:9200:a356:8495:fe0d:b43b:9c90> has joined #yocto07:27
*** pauldevguy <pauldevguy!~pauldevgu@> has joined #yocto07:28
*** avalluri <avalluri!~avalluri@> has joined #yocto07:30
*** manuel_ <manuel_!> has quit IRC07:34
*** linulin <linulin!> has joined #yocto07:36
-YoctoAutoBuilder- build #1043 of nightly-x86-lsb is complete: Success [build successful] Build details are at
*** rewitt1 <rewitt1!~rewitt@> has joined #yocto07:44
*** dl9pf_ <dl9pf_!> has joined #yocto07:44
*** tf <tf!> has quit IRC07:45
*** groleo <groleo!> has quit IRC07:46
*** sveinse_ <sveinse_!> has joined #yocto07:47
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC07:48
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto07:49
*** tf <tf!> has joined #yocto07:50
*** rewitt <rewitt!~rewitt@> has quit IRC07:51
*** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has quit IRC07:51
*** sveinse <sveinse!> has quit IRC07:51
-YoctoAutoBuilder- build #1064 of nightly-x86 is complete: Success [build successful] Build details are at
*** eduardas_m <eduardas_m!~eduardas_@> has joined #yocto07:58
*** jku <jku!~jku@> has joined #yocto08:00
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC08:00
*** robert_yang <robert_yang!~lyang1@> has quit IRC08:02
*** robert_yang <robert_yang!~lyang1@> has joined #yocto08:03
*** poor-man <poor-man!d97eb626@gateway/web/freenode/ip.> has joined #yocto08:06
*** groleo <groleo!> has joined #yocto08:07
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto08:07
*** nrossi <nrossi!uid193926@gateway/web/> has joined #yocto08:07
pohlyqemu-native no longer builds for me. SRC_URI joins to distinct entries together -> SRC_URI="
pohlyThere's a missing space at the end of _prepend: SRC_URI_prepend = "${BP}.tar.bz2"08:14
pohlyBut the existing SRC_URI starts with a space, so why is it breaking?08:14
pohlyFull bitbake -e history here:
*** AndersD <AndersD!> has joined #yocto08:16
*** ernstp <ernstp!uid168075@gateway/web/> has joined #yocto08:22
*** T_UNIX <T_UNIX!d4d3bd3c@gateway/web/freenode/ip.> has joined #yocto08:27
eduardas_mhello, where can I check at what memory location of sd card image u-boot was put when generating image via bitbake?08:27
eduardas_mI need this to define "Device offset" parameter to make fw_printenv of u-boot-fw_utils work08:28
*** fl0v0 <fl0v0!> has joined #yocto08:29
nrossieduardas_m: what are you using to generate the sd image?08:29
nrossieduardas_m: as in layer/machine/imagefstype/etc?08:29
*** erbo_ <erbo_!> has quit IRC08:30
*** erbo <erbo!> has joined #yocto08:30
eduardas_mnrossi, I just do a "bitbake fsl-image-qt5" and get an .sdcard file08:30
*** TobSnyder <TobSnyder!> has joined #yocto08:30
*** _william1 <_william1!> has quit IRC08:30
*** zibri <zibri!~zibri@2a01:7e01::f03c:91ff:febb:9538> has quit IRC08:31
*** _william_ <_william_!> has joined #yocto08:31
*** zibri <zibri!~zibri@2a01:7e01::f03c:91ff:febb:9538> has joined #yocto08:32
nrossieduardas_m: which fsl target? mx<?>?08:33
eduardas_mnrossi, these are the layers used:
eduardas_mmachine is Variscite DART6UL with imx6UL chip08:34
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:34
nrossieduardas_m: Ok, all the magic is in this file:
eduardas_mnot sure where to look for imagefstype08:34
nrossieduardas_m: Or the u-boot magic address are
nrossieduardas_m: If its using SPL, u-boot should start 69K from start of file. Without SPL it should be 1K. If i am reading it right08:36
*** Kakounet <Kakounet!> has joined #yocto08:36
*** kjlk <kjlk!4e0b08f9@gateway/web/freenode/ip.> has joined #yocto08:38
eduardas_mnrossi, thank you...however 69K is 0x11400 in hexadecimal... if I write that as Device offset in fw_env.config, it still does not work08:38
nrossieduardas_m: are you using u-boot SPL? or just u-boot?08:39
eduardas_mnrossi, using SPL08:39
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has quit IRC08:39
*** kjlk <kjlk!4e0b08f9@gateway/web/freenode/ip.> has quit IRC08:39
eduardas_mnrossi, perhaps I don't understand something and Device offset means something else08:40
nrossieduardas_m: wait, doesn't fw_printenv work on the environment, not the bootloader image?08:41
eduardas_mnrossi, yes it does... I have googled around a bit... but still not sure where there is documentation of "Device offset"08:42
nrossieduardas_m: Device offset refers to the offset for the device storing the environment. Im not sure what the default device is for you board is. Its likely to be in mtd though (aka spi flash)08:43
*** smartin_ is now known as smartin08:44
eduardas_mnrossi, my device is SD card (/dev/mmcblk0)08:44
eduardas_mMy config line is: /dev/mmcblk0 0x11400 0x1FFC08:45
eduardas_mI am pretty sure of the environment size (second parameter) because that is easy to get via u-boot printenv08:46
*** sameo <sameo!samuel@nat/intel/x-fbvbnlzqmjseoeib> has joined #yocto08:49
nrossieduardas_m: Sorry had to dive around to find the u-boot source for you machine. Looks like this is the magic define you are after :)
eduardas_mnrossi, it might be CONFIG_ENV_OFFSET ... will try now08:53
eduardas_mnrossi, there is #define CONFIG_ENV_OFFSET (8 * SZ_64K) for MMC so I set Device offset to 0x80000, still does not work08:57
*** joshuagl <joshuagl!joshuagl@nat/intel/x-ruznpbaveahqhjew> has joined #yocto08:58
nrossieduardas_m: When you start the machine, and U-Boot prints out its info before booting. What does it say about the environment?08:59
*** graphiqs <graphiqs!> has joined #yocto09:00
*** Biliogadafr <Biliogadafr!> has joined #yocto09:00
eduardas_mnrossi, actually, it does not seem to say anythin useful:
*** john2 <john2!> has joined #yocto09:01
nrossieduardas_m: if you run "saveenv" in the u-boot prompt does it save anything?09:02
eduardas_mSaving Environment to MMC...09:03
eduardas_mWriting to MMC(0)=SD... done09:03
eduardas_mthat is all09:03
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC09:03
nrossieduardas_m: ok, so its at least saving to MMC. Have you tried fw_printenv after doing a manual saveenv?09:03
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC09:04
eduardas_mIf I run printenv, the environment size info is Environment size: 1990/8188 bytes09:04
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC09:04
eduardas_mnrossi, will try now09:04
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto09:04
*** toscalix <toscalix!~toscalix@> has joined #yocto09:05
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto09:05
*** ed2 <ed2!~Adium@> has joined #yocto09:06
eduardas_mnrossi, does not help... neither for values 0x80000 or 0x11400 of device offset09:06
*** ed2 <ed2!~Adium@> has quit IRC09:10
-YoctoAutoBuilder- build #1059 of nightly-multilib is complete: Success [build successful] Build details are at
nrossieduardas_m: Hmmm, im out of ideas. Maybe you should query the layer mailing list if not one else here has any ideas ?09:11
*** erbo <erbo!> has quit IRC09:13
*** erbo <erbo!> has joined #yocto09:14
*** viengelm <viengelm!viengelm@nat/digia/x-gupjzusyujqdgutz> has quit IRC09:16
*** viengelm <viengelm!viengelm@nat/digia/x-xffbmgmyleoablir> has joined #yocto09:19
*** dl9pf_ is now known as dl9pf09:19
*** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has joined #yocto09:19
*** behanw <behanw!uid110099@gateway/web/> has quit IRC09:21
*** rubdos <rubdos!~rubdos@2a02:2788:1036:172f::1> has quit IRC09:21
*** rubdos <rubdos!~rubdos@2a02:2788:1036:172f::1> has joined #yocto09:22
*** erbo <erbo!> has quit IRC09:23
*** erbo <erbo!> has joined #yocto09:23
*** Kakounet <Kakounet!> has quit IRC09:23
*** ZubairLK <ZubairLK!~Thunderbi@unaffiliated/zubairlk> has quit IRC09:26
*** grma <grma!~gruberm@> has joined #yocto09:27
*** ZubairLK <ZubairLK!~Thunderbi@unaffiliated/zubairlk> has joined #yocto09:27
*** ed2 <ed2!~Adium@> has joined #yocto09:27
*** botman <botman!d97eb626@gateway/web/freenode/ip.> has joined #yocto09:29
*** JordonWu <JordonWu!~quassel@> has quit IRC09:29
eduardas_mnrossi, so thanks to agust in u-boot IRC I got it working09:30
eduardas_mit seems Env. size has to be whatever the maximu size printenv gives + 4 bytes (CRC32)09:30
eduardas_mso 0x1FFC + 0x4 = 0x200009:30
eduardas_malso, Device offset has to be the same as CONFIG_ENV_OFFSET in mx6ul_var_dart.h09:31
eduardas_mand not the actual offset of u-boot in image09:31
eduardas_mhonestly, these are gotchas that are not apparent to me from u-boot documentation or any kind of other documentation09:33
-YoctoAutoBuilder- build #369 of nightly-musl is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #1069 of nightly-arm is complete: Success [build successful] Build details are at
*** joseppc <joseppc!> has joined #yocto09:39
*** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto09:39
botmanHi everyone! I've just downloaded the basic Yocto and added the meta-openembedded layer, and beneath it, meta-oe, meta-python and lots of other layers. I want to create my own image and I added the layers to bblayer.conf, do I need to build all the recipes included in the layers? There's any way to bitbake all of them in one step? thanks09:39
*** Kakounet <Kakounet!> has joined #yocto09:42
pohlyRP: about the qemu-native SRC_URI issue ( - I managed to track it down to adding something in my local.conf: SRC_URI_remove_pn-linux-yocto = "git://;type=kmeta;name=meta;branch=yocto-4.8;destsuffix=kernel-meta"09:44
*** Cubi_ <Cubi_!> has joined #yocto09:45
ernstpbotman: it's basically like apt-get install, if you build the top level (ie. core-image-minimal) it will build all dependencies first09:45
*** nighty <nighty!> has quit IRC09:45
pohlyHow can it be that something entirely unrelated ends up removing spaces from SRC_UR?09:45
RPpohly: I don't think its unrelated. You're relying on the space before git:// and I suspect the removal code removes the space09:46
rburtoniirc removal code does a split, remove, join09:47
pohlyRP: but the recipe is qemu-native. Why does it even use SRC_URI_remove_pn-linux-yocto?09:47
RPpohly: that isn't right, is it09:48
RPpohly: I think I understand looking at the code. Fancy trying to change something?09:49
jkujoshuagl: you added alsa-state recipe years ago, any recollection? I think the postinst has never worked, and I'm not sure I understand what it's for...09:49
pohlyrburton: I agree that SRC_URI_prepend = "${BP}.tar.bz2" in is broken. But I'm worried that something else isn't quite as it should be, hence the question.09:49
pohlyRP: sure, shoot.09:49
RPpohly: bitbake/lib/bb/, there is a line,  filtered = filter(lambda v: v not in removes, around like 78409:50
RPpohly: I think that piece of code needs to be conditional on removes not being empty09:50
RPpohly: if you look at the code you'll see that match=True doesn't happen in this case (since the overrides aren't active) but it does mess the value around anyway09:52
RPpohly: the re joining of that string would swallow the leading space09:52
joshuagljku: hmm, a copy/paste recipe from oe-classic to persist alsa mixer settings. Not sure if it's still used/useful. Used to be that bsps would rely on it to ensure the volume wasn't 0 on new devices.09:53
pohlyRP: yes, that's it.09:54
*** phatina <phatina!> has quit IRC09:54
jkujoshuagl: ah so some other layer would contain a "asound.state" that actually had something in it09:54
zeenixI'm getting: lshw-02.16-r1 do_package_qa: QA Issue: No GNU_HASH in the elf binary: '/mnt/storage/zeenix/GDP/genivi-dev-platform-qemu-x86_64/gdp-src-build/tmp/work/core2-64-poky-linux/lshw/02.16-r1/packages09:54
zeenix-split/lshw/usr/sbin/lshw' [ldflags]09:54
zeenixany clues?09:54
joshuagljku: right!09:54
pohlyRP: I'm a bit surprised that _remove seems to run  before _append, though.09:54
rburtonzeenix: the build of lshw isn't respecting $LDFLAGS09:55
pohlyI thought _remove was always done last?09:55
RPpohly: _append is applied further up in that function09:55
*** phatina <phatina!> has joined #yocto09:55
pohlyWait, it's a _prepend in qemu.09:56
rburtondamnit i broke the selftest again09:56
RPjku: could you glance at, the epiphany failure, any idea what would break like that?09:56
rburton"Fatal Python error: getentropy() failed"09:56
RPThe nss failure is also odd :(09:56
jkuI'll take a look09:57
RPrburton: we need more randomness!09:57
rburtonRP: don't appreciate more randomness right now09:57
RPjku: also failed the same way so I think its something on the rss branch09:57
RPrburton: I did see an irony there09:58
jkunow hiring: person to wiggle the mouse at autobuilder.yocto.io09:58
*** arkver <arkver!> has joined #yocto09:58
rburtonjku: hhahaha09:58
RPjku: actually, that second one is clearer, missing intltool-native depends?09:59
RPjku: :D09:59
rburton| configure: error: GNU gettext tools not found; required for intltool sounds like a missing gettext dependency/inherit09:59
RPjku: or gettext-native depends?09:59
joshuagljku: we need a lego mindstorms kit in OSUOSL09:59
rburtoni'll take point on that10:00
* rburton expenses a full mindstorm set10:00
rburtonjoshuagl: have you seen the new mini-mindstorm?10:00
rburtoni spy next years christmas present to "the kids"10:00
RPThe one that is puzzling me is
RPwe're seeing a load of those10:01
rburtonnice log10:01
rburtonreally useful10:01
RPrburton: on the AB the log is much more helpful10:02
RPtar: ./usr/src/debug/nativesdk-pseudo/1.8.1-r0/recipe-sysroot/opt/poky/2.2+snapshot/sysroots/i686-pokysdk-linux/usr/include/sqlite3.h: file changed as we read it10:02
RPdpkg-deb: error: subprocess tar -cf returned error exit status 110:02
*** fitzsim <fitzsim!> has quit IRC10:03
*** fitzsim <fitzsim!> has joined #yocto10:03
arkverHi. Anyone know how to make "smart" package manager be verbose and show the output from a package post install script? Using 'smart reinstall --log-level=debug <packname>' doesn't do it.10:03
RParkver: I know at rootfs time, setting ROOTFS_RPM_DEBUG = "1" does this10:04
RParkver: you could see what options that passes to rpm/smart10:04
rburtonRP: huh10:05
pohlyRP: adding some debug output confirms that the line you called out gets executed before the SRC_URI_prepend. But removal works, so it seems to get executed multiple times? Does that right to you?10:05
arkverIs smart used at rootfs build time?10:05
rburtonif you're using rpms, yes10:05
arkverok,t a10:05
arkverAye, that just adds "--log-level=debug"10:06
pohlyIt's not wrong per se from a semantic point of view (_remove is meant to run last, so doing it multiple times doesn't change the semantic), it might just be slower.10:06
RPpohly: yes, we have an "on demand" data store now10:07
arkverI'll just get the script to redirect to a log file.10:07
RPpohly: so values are commuted on the fly10:07
RParkver: I think it adds something to rpm as well, that is the key10:07
pohlyMeaning _remove gets applied multiple time?10:07
RPpohly: meaning we never store the finalised value, it gets recomputed each time10:08
RPpohly: I suspect that is what you're seeing10:08
pohlyPerhaps. Still sounds a bit weird to compute some intermediate state (initial value + _remove) before applying the _prepend, but I take your word that it's meant to be that way ;-}10:09
RPpohly: I can't say for sure without poking at this in detail and I really don't have time right now but I'm not unduly worried10:10
RPpohly: the datastore is a bit weird/tricky10:11
*** behanw <behanw!uid110099@gateway/web/> has joined #yocto10:11
RPpohly: actually, cna you check something. Is the parsing input parameter set?10:12
RPpohly: I do have to wonder if you're right and the remove block shouldn't be triggering when parsing is set10:13
*** john3 <john3!> has joined #yocto10:13
*** john2 <john2!> has quit IRC10:14
RPpohly: you'll note that append and prepend are dependent on that variable10:14
* RP dreads you asking what it means10:14
*** JoiF <JoiF!~jofr@> has joined #yocto10:17
arkverRP: I think it changes the scriptlet invocation and content dump runes, but I don't see anything to make it dump the script output itself. I think this is shown if the script fails, but not if it succeeds.10:18
RParkver: ok, I thought there was something in there but perhaps not, sorry10:20
*** AndersD <AndersD!> has quit IRC10:21
*** pauldevguy <pauldevguy!~pauldevgu@> has quit IRC10:23
arkvernp, thanks. I'll go for the redirect within the script option.10:23
pohlyRP: yes, parsing=True.10:23
RPpohly: I think you're right and that could be a bug10:24
*** graphiqs <graphiqs!> has quit IRC10:25
RPpohly: There is an alarm bell going off that I've been here before though. Would be interesting to change it and see it bitbake-selftest still passes and OE still parses10:25
pohlySo add a "not parsing" to "if value and flag == "_content" and local_var is not None and "_remove" in local_var"?10:26
RPpohly: I think so10:26
RPpohly: As I said, I just can't help think there may have been a reason not to do this10:27
*** nighty <nighty!> has joined #yocto10:27
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto10:27
*** graphiqs <graphiqs!> has joined #yocto10:27
pohlyLet me file a bug and then we can investigate when the time is better.10:28
RPpohly: ok, fair enough10:28
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC10:40
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto10:41
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto10:42
*** hamis_lt_u_ <hamis_lt_u_!~irfan@> has joined #yocto10:43
botmanernstp: I'm getting an error because it doesn't find layer.conf in meta-openembedded, but there's no such directory or file on the tree
rburtonmeta-openembedded isn't a layer10:44
rburtonits a collection of layers10:44
rburtonyou need to add the layers you want, such as meta-oe or meta-python10:44
botmanthey are already in10:44
botmanbut that happend when I try to use bitbake on a recipe inside meta-python10:46
rburtonwhat's the actual error please10:47
botmanERROR: Unable to parse /home/bec_1/Yocto/poky/meta-openembedded/conf/layer.conf: [Errno 2] file /home/bec_1/Yocto/poky/meta-openembedded/conf/layer.conf not found10:48
joshuaglmeta-openembedded is a folder of layers, don't add that to BBLAYERS add some of its children10:48
rburtonyeah that10:48
botmanjoshuagl: ok, give me a sec10:49
botmanthanks btw10:49
botmanit's working now, aparently10:50
botmanERROR: Nothing PROVIDES ''  :-(10:52
rburtonjust use python-pip10:52
*** g0ne <g0ne!af649372@gateway/web/freenode/ip.> has quit IRC10:53
botmanrburton: compiling10:55
-YoctoAutoBuilder- build #1024 of build-appliance is complete: Success [build successful] Build details are at
*** berton <berton!~berton@> has joined #yocto11:05
eduardas_mI would like to ask what the preferred storage is for embedded systems these days? Is there any kind of advantage to gain by choosing NAND over eMMC for a SoM?11:07
LetoThe2ndeduardas_m: "depends" (TM)11:08
eduardas_mPersonally I am going with eMMC at this time just because it looks to be like an integrated SD card and I am more familiar with those11:09
eduardas_mI may be oversimplifying things though11:09
LetoThe2ndeduardas_m: without context/usecase/requirements, the whole discussion is pretty much pointless, don't you think?11:09
LetoThe2ndi mean, you didn't even state if you are talking about volatile or nonvolatile storage :)11:10
eduardas_mLetoThe2nd, ok...then lets say it is a handheld measurement device... similar to a handheld oscilloscope11:10
LetoThe2ndeduardas_m: that is a usecase, but does not include requirements11:11
eduardas_mLetoThe2nd, nonvolatile of course :)11:11
LetoThe2ndeduardas_m: well why "of course"? my preferred memory is ddr, in a couple of contexts.11:11
eduardas_mLetoThe2nd, not sure what kind of embedded linux systems manage without some kind of nonvolatile storage... what are the usecases when one can manage with ddr only? when booting via network?11:14
LetoThe2ndeduardas_m: and even for your handheld scope i easily can see 3 totally different storage contexts: 1) some rom for the application 2) some ram for holding the measurement data 3) some other nv storage for logging.11:15
LetoThe2ndeduardas_m: and read again, i never stated that my use case is "ddr only". i only said it is my "preferred memory"11:16
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:17
eduardas_mLetoThe2nd, why not just have bootloader + kernel + sysroot + logging in single eMMC instead of two instances of nonvolatile storage (points 1 and 3)?11:18
LetoThe2ndeduardas_m: "depends". maybe one wants 1) to be totally RO, and higher quality than 3)? maybe one does wnat 3) to be removable?11:20
LetoThe2ndeduardas_m: i'm just trying to show you that your understanding of the question already contains way too many assumptions and inherent decisions for anybody else to give you valuable input.11:21
eduardas_mLetoThe2nd, yes, I suppose there is a valid point here, so I'll try to narrow it down...11:24
LetoThe2ndeduardas_m: :-)11:24
eduardas_mLets say I decide to go with one particular SoM:
eduardas_mand there is an SLC NAND and and eMMC option for nonvolatile storage11:25
RPpohly: were you going to send a patch for that first issue (unnecessary manipulation of the string)?11:25
LetoThe2ndeduardas_m: thats what the overview on the webpage says, yes.11:25
eduardas_moptions are 128 - 512 MB for SLC NAND and 4 - 32 GB for eMMC11:25
pohlyRP: no, I intended to defer it so that it can be tested together with that other, more invasive change.11:26
pohlyI will send the fix for qemu, though.11:26
RPpohly: ok, I have a patch for that which I might queue. I'm happy enough that bit is safe/correct/a good idea11:26
pohlyRP: sure, your call.11:26
eduardas_mLetoThe2nd, device will probably have removable SD card for data storage, so NAND or eMMC is required for kernel, sysroot and application basically11:27
eduardas_malso I need to implement a two image update system with reliable fallback11:27
eduardas_mbut either storage technology allows for enough memory for me to implement that11:28
eduardas_mthe main thing that might make me switch from one to the other is if one of those allowed for faster reads/writes and thus faster bootup11:29
*** Snert_ <Snert_!> has joined #yocto11:29
LetoThe2ndeduardas_m: thats right. so the question is more like: "should i use emmc or slc nand as my application rom when i need a realiable two-image update mechanism". right?11:29
*** clopez <clopez!> has quit IRC11:29
eduardas_mLetoThe2nd, pretty much so11:29
RPpohly: is what I'm thinking11:30
RPpohly: it will have a performance impact which is why I'd like to fix it11:30
LetoThe2ndeduardas_m: and in that case, i would say: evaluate the requirements by the updating mechanism that you have chosen. some have direct support for ubifs, which makes slc a viable option. others rely on pure fs functionality, in which case i would probably opt for emmc.11:31
*** Snert <Snert!> has quit IRC11:31
RPrburton: I assume you're ok with -next going in even if the build isn't done?11:32
pohlyRP: in my tests I still had the "if expand and var in self.expand_cache" block active. But I agree, skipping that too seems to make sense (value already in cache and not changed, I suppose).11:32
RPpohly: right, it only needs to do that if it changed someting11:33
*** clopez <clopez!> has joined #yocto11:34
pohlyrburton: how do you feel about reverting the flex version update, as it currently prevents merging the UEFI/OVMF patch series?11:35
pohlyDo we have any flex experts around here perhaps who could help?11:36
jkurburton: any ideas on what could lead  "$(AM_V_GEN) $(GLIB_MKENUMS) \" to expand to " \" in a epiphany
jkuglib-mkenums should be in glib-2.0-dev -- I'd expect that to be present...11:38
jkuI mean glib-2.0-native obviously11:39
eduardas_mLetoThe2nd, thank you for your opinions. It seems that it is relatively easy to overwrite unused FAT boot partition and unused ext4 rootfs partition in case of eMMC using generic linux tools (what you call pure fs functionality), so it seems like the way to go. But then again can one not have multiple ubifs partitions on single chip and just dd the unused one? I am not familiar with this file system so thats when I'm asking.11:41
rburtonjku: hm no11:42
rburtonRP: yes11:46
RPjku: this is recipe specific sysroots so there is no gurantee that glib-2.0-native is present11:48
RPjku: does it DEPENDS on it?11:48
jkudamn, it doesn't. I was sure it would have...11:50
RPjku: I suspect a gettext-native issue in there as well :/11:51
kanavinjku: maybe we should have a class for that?11:51
jkuRP: yup that's definitely missing11:51
*** caiortp <caiortp!~inatel@> has joined #yocto11:51
jkuRP, so how did glib-2.0-native end up in recipe-sysroot-native when I built epiphany?11:53
jku(still building lib32-epiphany, not sure what happens there)11:54
*** arkver <arkver!> has quit IRC11:55
RPjku: I think it peeks though and sees host tools which aren't on some AB workers11:56
RPjku: I'd guess your host has a GLIB_MKENUMS11:56
LetoThe2ndeduardas_m: when using ubi, direct access to the memory is a no-go, as ubi takes care of wear levelling and bad blacks11:57
jkuRP: no, I'm looking at recipe-sysroot-native/ for epiphany: glib-2.0-native is in sysroot-providers11:57
LetoThe2ndeduardas_m: you can have one ubi partition, containing several ubifs.11:57
RPjku: that is odd11:57
jkuso is gettext-native11:58
LetoThe2ndeduardas_m: which works very well for us - we have an updating system that is ubi aware, and hence takes care of wear levelling, bad blocks and such when rewriting the iamge.11:58
eduardas_mLetoThe2nd, also when you said your prefered storage is ddr, did you mean you prefer to run your systems and applications in initrd?11:59
LetoThe2ndeduardas_m: no, i meant that for archieving certain pieces of functionality, i need relatively large amounts of ram. hence i prefer having much ddr.12:00
eduardas_mLetoThe2nd, this ubi - aware updating system does not happen to be open source?12:00
LetoThe2ndeduardas_m: it does happen. see meta-swupdate by sbabic :)12:00
RPpokybuild@debian-testing:~/yocto-autobuilder/yocto-worker/nightly-world/build/build/tmp/work/i586-poky-linux/epiphany/3.22.3-r0/recipe-sysroot-native$ ls sysroot-providers/g*12:00
RPsysroot-providers/gcc-cross-i586  sysroot-providers/gettext-minimal-native  sysroot-providers/gmp-native  sysroot-providers/gnu-config-native  sysroot-providers/gzip-native12:00
RPjku: ^^^ shows that machine does not have those things installed in the native sysroot12:00
eduardas_mLetoThe2nd, have already played around with meta-swupdate... just was not aware of ubi -related functionality12:01
RPjku: its possible something is racing here and that some later task depends on them12:02
RPjku: can you look at the timestamps, see when they were installed compared to when configure ran?12:02
eduardas_mLetoThe2nd, I actually could build the swupdate-image for my system, but ran into the problem described  here:!topic/swupdate/O2VdV7SBVr012:03
RPjku: for example, qemu-native may be needed during do_package and that links to glib-2.0-native, hence it could be installed then12:03
eduardas_msw-description does not get fetched for me for some reason12:03
RP(i'm not saying that specific example is true but something like it)12:03
RPjku: the best test would be "bitbake epiphany -c configure" (clean epiphany first)12:04
eduardas_mLetoThe2nd, so basically the place where I got stuck was that I could not generate compound images for updates12:06
RPrburton: I think I'm seeing things. - what does that say to you?12:07
jkuRP: I'll try configure, the timestamps are confusing -- probably looking at wrong stamp12:08
*** arkver <arkver!~arkver@> has joined #yocto12:08
RPjku: ok. It did this for lib32 and non-multilib so I think it affects both12:08
arkverRP: fyi: smart -o rpm-log-level=debug <command> <args> shows all the rpm verbosity.12:09
RParkver: cool, I thought there had to be a way!12:10
LetoThe2ndeduardas_m: well of course i don't know your specifics, but we genereate single swu images which we can hand to swupdate.12:11
eduardas_mLetoThe2nd, I pretty much like the idea of SWUpdate from the documentation I have read, but I find it lacking in some places...12:13
eduardas_mI can not make an swu although I try to follow the beaglebone black example12:13
eduardas_mwhich is the only one provided12:13
LetoThe2ndeduardas_m: if it fit your needs is something that you have to evaluate for yourself, of course. i can only tell you that it works fine for one of mine, using ubi on slc :)12:14
eduardas_malso, I do not like how meta-swupdate expects your BSP to have the newest bootloader12:14
*** istarilucky <istarilucky!~rlucca@> has joined #yocto12:14
eduardas_mif you don't it breaks u-boot-fw-utils recipe with patches for example12:14
LetoThe2ndeduardas_m: we certainly do not have the newest bootloader. but you're right, it needs a bit of massaging to work12:15
LetoThe2ndeduardas_m: another option might be mender.io12:15
LetoThe2ndeduardas_m: or resin os12:15
LetoThe2ndit really depends, there is no silver bullet.12:15 does not support local or at least is not oriented to IIRC12:16
eduardas_mand we basically only need local updates12:16
eduardas_mlike from an archive on a USB key that one attaches to device12:16
LetoThe2ndthe only thing i can really give as strong advice: do *not* try and roll your own.12:16
mborzeckieduardas_m: fyi mender does support locally applied updates12:17
eduardas_mLetoThe2nd, that is exactly what I am trying to do right now... and that is because SWUpdate does not work for me12:17
LetoThe2ndeduardas_m: do not do. the long term pains will exceed any trouble that you might have initially with a preexising solution by orders of magnitude.12:18
jkuRP: you're correct. glib-2.0-native and gettext-native are missing during configure...12:19
LetoThe2ndeduardas_m: and if you're using a specific SoM, you can always ask the vendor if they support some specific solution, for example.12:20
*** behanw <behanw!uid110099@gateway/web/> has quit IRC12:21
*** arkver <arkver!~arkver@> has quit IRC12:24
eduardas_mLetoThe2nd, I am aware of the danger... but sometimes for an embedded linux novice like me the problem lies here: there are no funds to hire expensive foreign experts to massage SWUpdate or some other solution into place for the BSP we are using12:25
LetoThe2ndeduardas_m: well you always have to pay in either time or money. and if you don't have money, you have to invest time.12:26
eduardas_mI would actually prefer to have some paid consulting or support for what I am doing, but the problem is again : money12:26
LetoThe2ndeduardas_m: i'm just saying: "do not invest your time in rolling your own quick-hack solution, as it will give you pains. invest your time in understanding and using a preexisting solution"12:27
LetoThe2ndeduardas_m: and sad to say, but rolling a product always requires some money, especially if hardware is involved.12:27
jkuso can intltool-native ever work without gettext-native ?12:33
jkurburton maybe ^12:33
LetoThe2ndeduardas_m: anyways, i'm off. if you feel like discussing more, find me here on monday :)12:34
eduardas_mLetoThe2nd, thank you very much for your time...12:34
LetoThe2ndeduardas_m: np, have fun.12:35
*** arkver <arkver!> has joined #yocto12:41
*** mdnneo <mdnneo!~umaucher@> has joined #yocto12:43
jkuRP: let me know if you just want a patch for epiphany ASAP: I'm still trying to understand how this works and whether there are other dependency issues like this12:44
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC12:44
jkufor example, why doe "bitbake -cconfigure vte" results in gettext-native being in recipe-sysroot-native/ even though the recipe does not depend on gettext-native12:45
RPjku: is there a depends from the gettext class?12:48
RPjku: I do agree we need to figure this out, a patch would be good in the meantime though please12:49
jkuRP: there is, but e.g. vte does not inherit (not directly anyway)12:50
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC12:53
RPjku: have a look at the do_prepare_recipe_sysroot task logs, that might give clues about where it comes from12:57
*** arkver <arkver!> has quit IRC12:57
pohlyrburton: has lots of issues about "flex 2.6.3 breaks compiling xyz".12:58
RPjku: looking at my logs, gettext-native is added as a dependency of glib-2.0-native12:58
pohlyI should be able to come up with a hotfix for compiling acpica, but I am really wondering whether we should really upgrade to 2.6.3 at this time.12:58
*** qt-x <qt-x!~Thunderbi@> has quit IRC12:59
RPjku: i.e. it looks like a glib-2.0 depends is enough to pull in gettext12:59
RP(which does make sense)12:59
*** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has quit IRC13:02
jkuRP can you walk me through that: ? How do you see the dependency logic from there13:03
*** sandsmark <sandsmark!~sandsmark@kde/sandsmark> has joined #yocto13:04
*** mdnneo <mdnneo!~umaucher@> has quit IRC13:04
jkubut yeah, confirming that : glib-2.0-native does pull gettext-native in13:05
kanavin\0/ it's taken a bit, but now also core-image-sato builds and boots (to GUI) with dnf :)13:06
kanavinI guess that's the end of the '90%'13:07
RPjku: trick it to work backwards. Start by finding "Adding dependency on gettext-native"13:07
kanavinnow come the other 90%13:07
RPjku: line above is considering dependency: ['glib-2.0-native', 'do_populate_sysroot'] which means that was the dependency which triggered the addition13:07
RPjku: welcome to the world of sstate setscene reverse logic13:08
*** arkver <arkver!~arkver@> has joined #yocto13:10
*** dv_ <dv_!> has quit IRC13:11
*** dv_ <dv_!~quassel@> has joined #yocto13:11
hydeHi, I have an .ipk, originating from meta-qt5 layer, with file name libqt5svg5_5.4.2+git0+ccae23961e-r0_cortexa9hf-vfp-neon.ipk13:12
hydeI can install it manually with opkg, and a QML app which uses svgs works after that (not without)13:13
hydeI have been unable to figure out how to get it installed in an image recipe though13:13
hydeso, if I have an .ipk produced by bitbake, and I want to find out how I would add it to image recipe, how should I go about it?13:14
hydeI have grepped for the packge name and various parts of it, but haven't yet figured out where the .ipk even comes from (other than it must be from meta-qt5 layer)13:14
hydeany suggestions?13:15
rburtonpohly: ok that takes it from "acapi breaks" to "everyone breaks", i'll revert.  thanks for digging.13:16
*** psadro <psadro!~Thunderbi@> has quit IRC13:17
pohlyrburton: well, I'm not sure whether it breaks "everyone" in OE.13:18
rburtonokay, 'lots'13:19
pohlyFor example, binutils, gdb master and grub are getting mentioned.13:19
pohlyThose must have been built successfully in OE, right? So it's perhaps not that bad in OE core itself (for whatever reason), but yes, it doesn't look good overall.13:20
*** JosePerez <JosePerez!~jgperezc@> has joined #yocto13:20
rburtonwell, binutils is sufficiently tricky to build that we may be using pregenerated files for that13:20
pohlyHmm, could it be that gdb for the target wasn't even using flex-native?13:21
pohlyNo, it's in pn-buildlist of "bitbake -g gdb".13:21
jkuhyde: how do you know it's from meta-qt5?13:22
pohlyrburton: how do you want to proceed? I have a workaround for acpica ready.13:22
rburtonpohly: the binutils bug says 2.6.2 works13:22
pohlyBut we updated to 2.6.3...13:23
rburtonmy patch was to 2.6.213:23
pohlyOoops, we didn't.13:23
pohlyI got confused because the latest upstream code that I checked out had 2.6.313:23
pohlyOkay, let's keep 2.6.2, work around this in acpica, and revisit once we know better whether it affects others and what upstream flex says about my bug report (
*** hamis_lt_u_ <hamis_lt_u_!~irfan@> has quit IRC13:28
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC13:29
*** hamis <hamis!~irfan@> has quit IRC13:29
*** marka <marka!> has joined #yocto13:31
*** CTtpollard <CTtpollard!> has quit IRC13:32
*** lamego <lamego!jose@nat/intel/x-jibknkzawcswxtrt> has joined #yocto13:39
rburtonpohly: is the secureboot something that was scheduled for m2?13:39
rburtoni guess its got new bits so sooner rather than later is good13:40
pohlyWhich Secure Boot thing? The UEFI/OVMF patches? That doesn't have an official Bugzilla entry, so no.13:40
pohlyBut I agree, getting them in sooner than later would be better.13:42
pohlyI've ping Ricardo again to check out the revised patches, just in case that you were waiting for someone to double-check them.13:42
rburtonsomeone else checking them would be good13:42
rburtonjust hecking if theres a greater need for them to be in *now*13:43
pohlyOther than me struggling with keeping all of my pending patches available while building locally, no ;-}13:43
rburtonyeah thats a pain i think we all understand13:44
* rburton has 47 local branches13:44
pohlyI need a "merge all pending git series into a working branch" helper script.13:44
rburtonno idea what percentage of them actually rebase to master13:45
pohlyI like that "git series" maintains clean patch series, but compared to accumulating all pending patches in a branch it's harder when your actual work depends on more than one series.13:46
*** arkver <arkver!~arkver@> has quit IRC13:50
*** botman <botman!d97eb626@gateway/web/freenode/ip.> has quit IRC13:57
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC14:00
*** Son_Goku <Son_Goku!> has quit IRC14:01
*** poor-man <poor-man!d97eb626@gateway/web/freenode/ip.> has quit IRC14:01
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto14:02
*** arkver <arkver!~arkver@> has joined #yocto14:03
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:72f3:95ff:fe1d:9866> has joined #yocto14:06
*** mdnneo <mdnneo!~umaucher@> has joined #yocto14:08
*** open-nandra <open-nandra!> has quit IRC14:09
RPjku: I think I have my other issues fixed for another rss test run, do you have a fix I could add in ?14:13
*** arkver <arkver!~arkver@> has quit IRC14:15
*** manuel_ <manuel_!> has joined #yocto14:18
RPed2: The wic series seems good thanks. Do you want me to mail that to the list (dependent on the rss patches)?14:23
*** paulg <paulg!> has joined #yocto14:25
*** AndersD <AndersD!> has joined #yocto14:26
*** ash_charles <ash_charles!~acharles@2607:fad8:4:6:5aac:892e:cbe9:f7fc> has joined #yocto14:27
*** arkver <arkver!~arkver@> has joined #yocto14:28
jkuRP, oh I sent an epiphany patch to list earlier , sorry I didn't ping you14:32
jkuno idea about the nss package_write_deb failure14:33
RPjku: its ok, I have that one14:33
RPjku: thanks!14:33
ernstplots of epiphany activity? is it the best option these days?14:34
rburtonernstp: epiphany activity in here because its part of oe-core14:35
jkuernstp: depends what you need it for. It's pretty good at failing to build for example14:35
ernstpjku: that is not currently on the requirements list :-)14:36
*** gtristan <gtristan!~tristanva@> has joined #yocto14:36
*** arkver <arkver!~arkver@> has quit IRC14:37
* RP quietly sobs at new ways the rss code breaks after the last fix14:37
*** arkver <arkver!~arkver@> has joined #yocto14:37
ernstpusing chromium right now, the back/forward swipe gestures you get out of the box is pretty neat14:38
ernstpalso, you can use compiling chromium/webkit for heating your office14:44
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC14:52
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto14:56
*** manuel_ <manuel_!> has quit IRC15:00
*** arkver <arkver!~arkver@> has quit IRC15:03
*** jku <jku!~jku@> has quit IRC15:05
*** NU-Slacker <NU-Slacker!~NU-Slacke@> has joined #yocto15:06
*** berton <berton!~berton@> has quit IRC15:07
-YoctoAutoBuilder- build #1140 of nightly is complete: Success [build successful] Build details are at
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto15:07
*** T_UNIX <T_UNIX!d4d3bd3c@gateway/web/freenode/ip.> has quit IRC15:08
*** adca <adca!~adca@> has quit IRC15:09
*** manuel_ <manuel_!> has joined #yocto15:11
*** manuel_ <manuel_!> has quit IRC15:11
*** stephano <stephano!~stephano@> has joined #yocto15:15
*** arkver <arkver!> has joined #yocto15:18
*** john4 <john4!> has joined #yocto15:18
*** john3 <john3!> has quit IRC15:19
*** berton <berton!~berton@> has joined #yocto15:22
*** AndersD <AndersD!> has quit IRC15:24
*** manuel_ <manuel_!~manuel@> has joined #yocto15:27
*** csanchezdll <csanchezdll!> has left #yocto15:32
*** manuel__ <manuel__!~manuel@> has joined #yocto15:33
*** paulbarker <paulbarker!~quassel@2a01:4f8:c17:626::2> has joined #yocto15:33
*** manuel_ <manuel_!~manuel@> has quit IRC15:36
*** manuel__ is now known as manuel_15:36
*** alimon <alimon!~alimon@> has joined #yocto15:41
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC15:44
davishas anyone seen an error with wic where it says  Partition  internal size is not an integer. This a bug in source plugin rawrootfs and needs to be fixed.15:45
*** TobSnyder <TobSnyder!> has quit IRC15:51
*** groleo <groleo!> has quit IRC15:52
*** mdnneo <mdnneo!~umaucher@> has quit IRC15:57
*** marka <marka!> has quit IRC16:00
*** marka <marka!> has joined #yocto16:00
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC16:06
*** sameo <sameo!samuel@nat/intel/x-fbvbnlzqmjseoeib> has quit IRC16:06
joshuaglcc ed2: ^^16:08
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC16:09
*** sameo <sameo!samuel@nat/intel/x-mrncsgcujzkirzog> has joined #yocto16:09
*** ed2 <ed2!~Adium@> has quit IRC16:10
*** ed2 <ed2!~Adium@> has joined #yocto16:11
ed2davis: never seen it. can you create bug?16:11
davisyes, it happens every time I do the wic step. btw, I've been using wic for sometime now, but not taken time to look into it.16:13
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto16:13
Strike5150I wrote a recipe which inherits module.  It builds correctly but when I try to install on the system has a dependancy on  kernel-module-stream-bus-sbc. Can someone explain?
davisis it something to do with Windows Image configurator or is that just a coincidence?16:14
Strike5150I don't know how to install the dependancy and I don't understand where it comes from16:14
ed2davis: just a coincidence I believe.16:15
davisok many thanks16:15
davisdo you know of a ref online for wic?16:15
davised2: many thanks. i appreciate it.16:17
*** JoiF <JoiF!~jofr@> has quit IRC16:17
ed2davis: if you're ok with local ref you can also run wic help overview|kickstart|plugins16:18
davisahh that is cool. many thanks16:19
ed2davis: I wouldn't suggest to look at the code though. It's a messy java-like stream of bytes.16:19
ed2davis: I'm trying to refactor it at the moment, so I speak from experience :)16:20
davistip of the hat to you.16:20
davisi'll be happy if I can understand how to use it16:20
*** eduardas_ <eduardas_!~eduardas_@> has joined #yocto16:21
*** ntl <ntl!> has joined #yocto16:21
ed2davis: the best way to use it is to create .wks file, set WKS_FILE variable, add 'wic' to IMAGE_FSTYPES and run bitbake <image>16:22
*** eduardas_m <eduardas_m!~eduardas_@> has quit IRC16:22
*** eduardas_ <eduardas_!~eduardas_@> has quit IRC16:22
*** eduardas_m <eduardas_m!~eduardas_@> has joined #yocto16:23
davismy colleague set this up for me. I'm hoping to talk to him about this error, but in the meantime i'll read your reference. Its been awhile since I've made a sata img.16:23
ed2davis: feel free to ask questions about wic. I'll be happy to answer.16:23
davisthe usb img wic step still works.16:23
daviswe do have a wks file16:23
davisand when i first got the error, i looked at it. I don't see any fractional numbers.16:24
davisso i am not sure why the error has occured.16:24
ed2davis: ok, can you show it here? which machine do you use, btw?16:24
davisError: Partition  internal size is not an integer. This a bug in source plugin rawrootfs and needs to be fixed.16:24
ed2davis: i mean wks file16:25
davisits for atom16:25
davisim using a custom wks file16:25
davisit has entries which look like attributes for each partition16:25
ed2davis: I'm afraid this is not enough for me to reproduce and fix this. I need more details.16:26
daviswe have three different wks files for sata. possibly for differnt rootfs types. the sizes look same but the bootloader cmd line varies between files.16:26
davisthat makes sense16:26
ed2davis: if you can tell me which MACHINE do you use, show your wks file and your bblayers.conf I might be able to reproduce the issue.16:27
ed2davis: it's better to do in bugzilla, I believe.16:28
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC16:28
davisone sec16:28
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC16:28
*** rus <rus!c5d67462@gateway/web/freenode/ip.> has joined #yocto16:29
davisim getting waits on github gist. heh entire company must be watching the innaugration16:31
JaMaor the internet started to fail already16:37
rushi ,i have a siemens iot 2020 running yocto 4.4.13 , I am trying to access ttyUSB0 , but get permission denied , how can I fix this?16:39
*** rcw <rcw!~rwoolley@> has joined #yocto16:39
*** JaMa <JaMa!~martin@> has quit IRC16:39
*** eduardas_m <eduardas_m!~eduardas_@> has quit IRC16:40
rburtonzeddii: have you changed the linux-libc-headers 4.9 upgrade since you submitted it first?16:43
rburtoni can't reproduce my connman/musl/4.9 headers failure anymore!16:43
zeddiinope. it is still 4.9. I was going to bump it to a -stable variant eventually but was holding on that.16:44
davisthere is a third wks file, but I don't think its being used during that invocation ive shown16:44
*** joseppc <joseppc!~josep@linaro/joseppc> has quit IRC16:45
davisin terms of machine, i do an export MACHINE=buts its a product name and not somthing like x86 or beaglebone, etc. but I think it steers towards an atom based cpu/board16:46
rburtonzeddii: huh. thanks.16:48
ed2davis: can you reproduce the issue on genericx86* or qemu machines?16:49
davisi dont use qemu. i've used in the past but not on this system.16:50
davisi can look into it though. that will take some time.16:51
*** stephano <stephano!~stephano@> has quit IRC16:53
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC16:56
*** zeddii <zeddii!~bruce@> has quit IRC16:57
*** zeenix <zeenix!~zeenix@> has quit IRC16:59
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has joined #yocto17:02
ed2davis: can you give names to your partitions in .wks. you'll see which partition wic complains about.17:08
davised2: how to do that?17:10
davisthe bit in ""?17:10
davisok one sec17:10
halsteadRP, Locking is broken on debian-testing now. But the build isn't stuck yet.17:11
davishmm. makes a python stacktrace17:13
*** Cubi_ <Cubi_!> has quit IRC17:14
ed2davis: what's rawrootfs plugin?17:15
ed2davis: looks like custom17:15
ed2davis: I don't see it among standard wic plugins.17:16
RPhalstead: :(. Any idea what is breaking? I was hoping the completed build meant you'd fixed it?17:16
*** dv_ <dv_!~quassel@> has quit IRC17:17
*** stephano <stephano!~stephano@> has joined #yocto17:17
halsteadRP, It's the out of sequence error in the logs again. I don't think we've seen it on debian-testing before. It might be a new trigger for the old problem.17:18
*** dv_ <dv_!> has joined #yocto17:18
*** nighty <nighty!> has quit IRC17:21
*** john1 <john1!~john@> has joined #yocto17:23
*** john4 <john4!> has quit IRC17:24
*** hyde <hyde!uid25660@gateway/web/> has quit IRC17:25
*** lemagoup <lemagoup!~lemagoup@> has quit IRC17:25
*** john2 <john2!> has joined #yocto17:26
*** sameo <sameo!samuel@nat/intel/x-mrncsgcujzkirzog> has quit IRC17:27
*** nighty <nighty!> has joined #yocto17:27
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC17:27
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto17:27
*** john1 <john1!~john@> has quit IRC17:28
*** stephano <stephano!~stephano@> has quit IRC17:29
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto17:32
*** Snert___ <Snert___!~snert_@> has quit IRC17:34
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC17:35
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto17:36
*** rus <rus!c5d67462@gateway/web/freenode/ip.> has quit IRC17:40
RPhalstead: not good :/17:48
*** graphiqs <graphiqs!> has quit IRC17:50
-YoctoAutoBuilder- build #1025 of build-appliance is complete: Failure [failed BuildImages_1] Build details are at
halsteadRP, I got it to recover without interrupting anything. So this build might be okay at least.17:52
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC17:52
*** fl0v0 <fl0v0!> has quit IRC17:53
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC17:55
*** Kakounet <Kakounet!> has quit IRC17:55
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto17:55
RPhalstead: how did you do that out of interest?17:57
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC17:58
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto17:59
*** Snert__ <Snert__!~snert_@> has joined #yocto18:00
*** stephano <stephano!~stephano@> has joined #yocto18:04
*** toscalix <toscalix!~toscalix@> has quit IRC18:04
-YoctoAutoBuilder- build #690 of nightly-deb-non-deb is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
* RP has posted the recipe specific sysroot patch for review18:05
*** cdleonard <cdleonard!> has joined #yocto18:06
*** diego_r <diego_r!> has quit IRC18:14
*** manuel__ <manuel__!~manuel@> has joined #yocto18:16
*** manuel_ <manuel_!~manuel@> has quit IRC18:16
*** manuel__ is now known as manuel_18:16
RPhalstead: thanks for keeping it running, I'm hoping for good things from that build!18:19
RP(its the final rss patchset)18:19
*** ftonello <ftonello!~felipe@> has quit IRC18:20
*** zeddii_home <zeddii_home!> has left #yocto18:22
*** ernstp <ernstp!uid168075@gateway/web/> has quit IRC18:28
*** zeddii_home <zeddii_home!> has joined #yocto18:31
*** grma <grma!~gruberm@> has quit IRC18:34
*** peacememories <peacememories!> has joined #yocto18:35
*** rewitt1 <rewitt1!~rewitt@> has quit IRC18:37
*** morphis_ <morphis_!> has quit IRC18:37
*** rewitt1 <rewitt1!~rewitt@> has joined #yocto18:38
*** manuel_ <manuel_!~manuel@> has quit IRC18:40
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto18:41
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto18:46
lpappkhem: you there?18:47
lpappis there really no better way than this? I do need pam support for my openssh server.18:48
*** manuel_ <manuel_!~manuel@> has joined #yocto18:50
*** peacememories <peacememories!> has quit IRC18:51
halsteadRP, I kind of brute forced it.  umount -l /srv/autobuilder &&  systemctl restart nfs-utils && mount  /srv/autobuilder18:55
*** scottrif <scottrif!scottrif@nat/intel/x-cwvatycvwlsaqnma> has joined #yocto18:55
halsteadRP, I ran lsof /srv/autobuilder/ to try to make sure nothing would be interrupted by it first.18:57
*** istarilucky <istarilucky!~rlucca@> has quit IRC19:01
-YoctoAutoBuilder- build #769 of nightly-world-lsb is complete: Failure [failed BuildImages SendErrorReport] Build details are at
*** gtristan <gtristan!~tristanva@> has quit IRC19:06
*** dmoseley <dmoseley!> has quit IRC19:06
-YoctoAutoBuilder- build #1015 of nightly-ipk is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC19:23
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto19:33
-YoctoAutoBuilder- build #996 of nightly-deb is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
*** joshuagl <joshuagl!joshuagl@nat/intel/x-ruznpbaveahqhjew> has quit IRC19:37
*** berton <berton!~berton@> has quit IRC19:38
*** JosePerez <JosePerez!~jgperezc@> has quit IRC19:41
*** nrossi <nrossi!uid193926@gateway/web/> has quit IRC19:43
*** JosePerez <JosePerez!jgperezc@nat/intel/x-qnumfhyhqhkjtkzq> has joined #yocto19:44
*** pohly <pohly!> has quit IRC19:44
*** ed2 <ed2!~Adium@> has quit IRC19:49
*** manuel_ <manuel_!~manuel@> has quit IRC19:53
kanavin_homeRP: congratulations, I guess :)19:54
rburtonwebkit build was OOMed on the autobuilder19:56
kanavin_homeI hope to come out with the dnf work before the end of the month, I'm getting tired of working in isolation on it19:56
kanavin_homeI should ask WR team (that has offered to help) to run the current patchset through their systems, and report specific issues19:57
*** ntl <ntl!> has quit IRC19:59
rburtonyes, definitely20:03
kanavin_homerburton: some of the things I'm doing there are controversial20:04
kanavin_homerburton: db 6.x is removed, rpm5 is removed, a bunch of complicated barely penetrable logic around rpm5 that may or may not serve real purpose is also removed20:05
rburtonprobably worth mailing a link to the branch to the list as work in progress for feedback20:06
kanavin_homerburton: yeah, i just want to get the most obvious omissions fixed first - sdk generation is at the moment broken for instance20:07
kanavin_homerburton: but images build and boot :)20:07
*** bluelightning <bluelightning!~paul@> has joined #yocto20:09
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:09
themikenicholsonIs this the right place to ask bitbake questions?20:20
kergothhere or #oe, yes. either one20:24
-YoctoAutoBuilder- build #1065 of nightly-x86 is complete: Failure [failed BuildImages_1 Running ESDK Sanity Tests] Build details are at
themikenicholsonExcellent.  I'm trying to maintain a local mirror of all of our source pacakges and I'd like to run with BB_FETCH_PREMIRRORONLY and I have that workign fine.  The only thing I'd like to add is the ability to "whitelist" an internal Gitlab server so I can still fetch directly from that20:27
kergothsee BB_ALLOWED_NETWORKS20:28
*** caiortp <caiortp!~inatel@> has quit IRC20:30
themikenicholsonkergoth: Thanks! I was looking at an old version of the bb user manual. My mistake20:32
kergothit's ideal for limiting to internal servers like that20:32
*** adelcast <adelcast!~adelcast@> has quit IRC20:34
*** adelcast <adelcast!~adelcast@> has joined #yocto20:37
themikenicholsonkergoth: Its exactly what I was looking for. Huge thanks.20:39
-YoctoAutoBuilder- build #1063 of nightly-x86-64-lsb is complete: Failure [failed BuildImages_1] Build details are at
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC20:43
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto20:45
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC20:46
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto20:48
*** adelcast <adelcast!~adelcast@> has quit IRC20:50
*** lamego <lamego!jose@nat/intel/x-jibknkzawcswxtrt> has quit IRC20:50
*** ntl <ntl!> has joined #yocto20:55
-YoctoAutoBuilder- build #1011 of nightly-arm-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at
*** adelcast <adelcast!~adelcast@> has joined #yocto21:05
-YoctoAutoBuilder- build #1070 of nightly-arm is complete: Failure [failed Running ESDK Sanity Tests] Build details are at
*** jamesp <jamesp!~jamesp@> has joined #yocto21:31
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC21:31
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto21:36
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC21:37
-YoctoAutoBuilder- build #1044 of nightly-x86-lsb is complete: Failure [failed BuildImages_1] Build details are at
*** rstreif_ <rstreif_!> has quit IRC21:41
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto21:44
-YoctoAutoBuilder- build #371 of nightly-musl is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
*** scottrif <scottrif!scottrif@nat/intel/x-cwvatycvwlsaqnma> has left #yocto21:58
*** manuel_ <manuel_!~manuel@> has joined #yocto22:01
-YoctoAutoBuilder- build #672 of nightly-arm64 is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images_1] Build details are at
*** pauldevguy <pauldevguy!~pauldevgu@> has joined #yocto22:02
*** stephano_ <stephano_!~stephano@> has joined #yocto22:10
*** stephano_ <stephano_!~stephano@> has quit IRC22:11
*** stephano <stephano!~stephano@> has quit IRC22:12
*** alimon <alimon!~alimon@> has quit IRC22:13
*** JosePerez <JosePerez!jgperezc@nat/intel/x-qnumfhyhqhkjtkzq> has quit IRC22:14
*** marka <marka!> has quit IRC22:16
*** stephano <stephano!~stephano@> has joined #yocto22:18
*** stephano <stephano!~stephano@> has quit IRC22:18
*** stephano <stephano!~stephano@> has joined #yocto22:18
*** stephano <stephano!~stephano@> has quit IRC22:23
*** kanavin_home <kanavin_home!> has quit IRC22:26
RPhalstead: we're seeing this a lot on the new cluster in recent builds: - seems the PR server can't cope :(22:26
RPhalstead: probably not your problem to fix but I thought I'd flag it22:26
halsteadRP, So. In my continued research the advice I see over and over is to reduce load on the system and see if NFS errors continue. Could high load also cause issues with the PR server?22:27
*** kanavin_home <kanavin_home!> has joined #yocto22:27
RPhalstead: absolutely22:30
*** rcw <rcw!~rwoolley@> has quit IRC22:30
RPhalstead: just looking at and the second failure at least is resource problems22:30
RPhalstead: also could be resource issues, was the same machine22:30
halsteadRP, Is there a good way to reduce the number of threads we start? Or we could just switch to 2 workers per box for a bit.22:31
RPhalstead: we'd set BB_NUMBER_THREADS lower22:32
*** arkver <arkver!> has quit IRC22:32
*** stephano <stephano!~stephano@> has joined #yocto22:37
*** stephano <stephano!~stephano@> has quit IRC22:38
*** stephano_ <stephano_!~stephano@> has joined #yocto22:40
*** Snert__ is now known as Snert22:41
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC22:41
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto22:42
*** pauldevguy <pauldevguy!~pauldevgu@> has quit IRC22:42
*** stephano_ <stephano_!~stephano@> has quit IRC22:43
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC22:43
halsteadRP, So we have BB_NUMBER_THREADS=16 on the stable cluster and BB_NUMBER_THREADS=48 on the unstable cluster. Can you recommend a good value in between?22:43
RPhalstead: try 24?22:44
* halstead nods.22:44
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto22:45
halsteadRP, I'll reload the controller when/if these last builds wrap up.22:45
RPhalstead: I run 144 locally :)22:45
halsteadRP, On how many cores?22:46
RPhalstead: not often with many in parallel though22:46
RPhalstead: 7222:46
RPhalstead: I mainly do this to stress things rather than it being fast22:47
halsteadOkay so we have 28 cores with hyperthreading that is 56. And we are running 48 threads * 3 workers so 144 as well.22:47
RPhalstead: this is 36 cores with HT in addition to that22:48
RPhalstead: the builds can't really leverage 144 much of the time anyway22:48
RPhalstead: 24 seems like a reasonable number to try and see if it calms things down22:48
halsteadSounds good.22:49
*** fmeerkoetter <fmeerkoetter!> has quit IRC23:01
*** bfederau <bfederau!> has quit IRC23:01
*** bfederau <bfederau!> has joined #yocto23:01
*** fmeerkoetter <fmeerkoetter!> has joined #yocto23:01
*** manuel_ <manuel_!~manuel@> has quit IRC23:06
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC23:09
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto23:14
*** dmikulin <dmikulin!~dmikulin@> has joined #yocto23:18
RPhalstead: if you need a test once you've changed that, master-next should be good (it contains rss but will be a full rebuild due to a tweak)23:18
halsteadRP, Excellent.23:19
dmikulinIs there someone on here that can help me and my team understand how to make a bootable X86 PC out of the Yocto artificats? We have been unsuccessful with everything we have tried to date.23:19
dmikulinWe want to create (at least to start) a boot partition and a root partition with grub2 as a bootloader. Eventually we'll have two boots and two roots (for current and next version) for upgrades.23:20
*** dyang <dyang!4c4d4102@gateway/web/freenode/ip.> has joined #yocto23:21
*** stephano <stephano!~stephano@> has joined #yocto23:23
RPdmikulin: I'm sure there are people here who've done it and the project can certainly do that. There are a lot of specifics to your environment there to get right though of which we know nothing. I'd try and ask more specific questions and give more information (e.g. you did what exactly and how exactly did it fail?)23:24
dmikulinRP: Specifics: target is a core i7 industrial PC. Using Ubuntu as a development host.23:25
dmikulinIf we "dd" the .hddimg to a SSD it boots. We have been able to boot using PXE putting the bzImage in a TFTP directory and the root file system in an NFS directory.23:26
dmikulinRP: We've tried 'dd'ing the .wic file to a HDD and it doesn't boot. Should it?23:27
RPdmikulin: do you weren't entirely unsuccessful23:27
RPdmikulin: I was about to suggest that wic should be able to combine things together in a way that would do what you need23:28
RPdmikulin: sadly I'm not a wic expert and the one I do know is in Europe and gone for the weekend but if you write up a decent summary on the mailing list its possible he can spot the problem23:29
dmikulinRP: We have about a combined 100 MB kernel + RFS, but are installing image onto a 128 GB disk where the 127+ GB will be reserved for logging. We don't want to have to create and store 128 GB wic files.23:29
RPdmikulin: the wic files should be sparse if I remember correctly23:29
dmikulinRP: Should the .wic file boot if copied to a disk? Does legacy / EFI come into the picture?23:30
dmikulinRP: .wic dd'd to disk, not just copied.23:30
kergothall you should ahve to do is dd the .wic to the disk23:31
RPdmikulin: I'd have expected dd, copied to what would be the question otherwise. You need someone who knows wic more23:31
kergothi'd suggest comparing your working and non-working disk image. examine the partition tables. mount the partitions with loopback and compare their contents23:31
* kergoth has had to do that before23:31
dmikulinRP: Does the default core-image-minimal expect legacy MBR or EFI? I wonder if it is not booting just because of a BIOS setting?23:32
dmikulinRP: We get the error message "Please insert a bootable media" type message.23:33
RPdmikulin: entirely possible, I'd suggest what kergoth mentions, compare the disk working and not working and see what the partition tables look like23:34
dmikulinRP: The working .hddimage has no partitions and the .wic has three partitions. So, they are very different.23:34
kergothcan also read the .wks to see what it's doing (use bitbake -e to examine WKS_FILE)23:34
kergoththat really doesn't make sense. how exactly would you boot a disk image without a partition table?23:34
dmikulinkergoth: Sorry, .hddimg has a single partition.23:35
dmikulinkergoth / RP: What is the most appropriate #yocto mailing list to ask this question on?23:36
RPdmikulin: yocto@23:37
sgw_dmikulin: what wks file are you using to create your image?23:38
RPdmikulin: as kergoth said, look at the wks file for an idea of what its doing. hddimg is certianly legacy23:38
RPdmikulin: and sgw_ does this more than I do23:38
RPKind of makes me sad I don't get to play with real hardware that much now23:38
*** Biliogadafr <Biliogadafr!> has quit IRC23:39
dmikulinSGW_ We haven't created our wks file. We are simply creating core-image-minimal at this point with a few extra packages added. Nothing special. So, it's whatever the default file is for machine type intel core i723:40
dmikulinSGW_ Default .wks file that is. BTW, we followed the same process for Beaglebone and the resultant .wic file from the build did boot on the Beaglebone.23:41
RPhalstead: if it helps, kill the current cluster build and start a new master-next one, I think it broke enough the result doesn't matter so much and its nowhere near even starting selftest23:41
RPhalstead: I'll take the results of the new build23:41
sgw_dmikulin: So your using the meta-intel BSP (intel-corei7-64) or genericx86-64 or custom? Default WKS might depend on which EFI_PROVIDER you have set also23:41
halsteadRP, Ah. Thank you. I didn't really look forward to waiting to kill it.23:41
sgw_dmikulin: I assume it's EFI or PCBIOS?23:42
dmikulinSGW_ We are using meta-intel BSP intel-corei7-64.23:42
RPhalstead: I can't tell if some of those failures are rss bugs or not. I suspect the eSDK one on nightly arm is though :(23:43
*** agust <agust!> has quit IRC23:43
sgw_dmikulin: Which release of Yocto Project/Poky?23:43
dmikulinSGW_ Hot off the press - we just put the same SSD into another PC and it boots, so it must be a BIOS setting or EFI option. We are trying to boot on Advantec ARK 3500.23:44
dmikulinMorty (Yocto 2.2)23:44
sgw_dmikulin: Ok, not familiar with ARK 3500, do you know if it's PCBIOS or EFI?23:45
halsteadRP, Do you want artifacts generated?23:47
dmikulinsgw_ Not sure ourselves. But considering the .wic looks to be EFI and it works on PC where UEFI is enabled and not on the ARK 3500, I have to assume PCBIOS.23:47
RPhalstead: no, I don't need them thanks23:47
dmikulinsgw: Is intel-corei7-64 default to generate .wic that needs EFI?23:47
dmikulinsgw_ Looking... the wks file specifies --source bootimg-efi. What is the corresponding option for PCBIOS?23:49
sgw_dmikulin: yes, currently wic images are assumed to be EFI23:49
sgw_you can try directdisk-bootloader-config (in scripts/lib/wic/canned-wks23:51
-YoctoAutoBuilder- build #1141 of nightly is complete: Failure [failed] Build details are at
sgw_dmikulin: I have not worked with that recently23:51
dmikulinsgw_ Okay, we will take a look at that.23:52
sgw_dmikulin: you can also look atdirectdisk-gpt any other directdisk in that directly23:53
sgw_dmikulin: we are working to create a new wks that actaully replaces the hddimg, but not there yet.23:53
sgw_dmikulin: hopefully that gets you going23:54
* sgw_ has to bolt to mentor a High School Roborics team have a good weekend all23:54
dmikulinsgw_, kergoth, RP: Thanks guys - you have been very helpful!23:54
RPdmikulin: hopefully you're heading in a good direction now :)23:56
* RP should sleep23:56
*** manuel_ <manuel_!> has joined #yocto23:57

Generated by 2.11.0 by Marius Gedminas - find it at!