ndec changed the topic of #yocto to: "Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Join us or Speak at Yocto Project Summit (2022.05) May 17 - 19, more: https://yoctoproject.org/summit | Join the community: https://www.yoctoproject.org/community | IRC logs available at https://www.yoctoproject.org/irc/ | Having difficulty on the list or with someone on the list, contact YP community mgr ndec"
nemik has quit [Ping timeout: 252 seconds]
sakoman has quit [Quit: Leaving.]
rber|res has joined #yocto
rber__ has quit [Ping timeout: 252 seconds]
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #yocto
camus has quit [Ping timeout: 256 seconds]
camus has joined #yocto
vvn has quit [Quit: WeeChat 3.6]
sakoman has joined #yocto
Estrella has quit [Remote host closed the connection]
Estrella_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
Estrella has joined #yocto
nemik has joined #yocto
sakoman has quit [Quit: Leaving.]
olani has quit [Ping timeout: 268 seconds]
rber|res has quit [Read error: Connection reset by peer]
amitk has joined #yocto
<LetoThe2nd> yo dudX
beneth has quit [Read error: Connection reset by peer]
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
alessioigor has joined #yocto
mvlad has joined #yocto
alessioigor has quit [Quit: alessioigor]
adrian__ has joined #yocto
goliath has quit [Quit: SIGSEGV]
adrian__ has quit [Remote host closed the connection]
pbergin has joined #yocto
frieder has joined #yocto
leon-anavi has joined #yocto
zpfvo has joined #yocto
goliath has joined #yocto
zpfvo has quit [Quit: Leaving.]
zpfvo has joined #yocto
ptsneves has joined #yocto
florian has joined #yocto
zeddii has quit [Ping timeout: 248 seconds]
frieder has quit [Ping timeout: 248 seconds]
zeddii has joined #yocto
frieder has joined #yocto
zpfvo has quit [Ping timeout: 252 seconds]
Juanosorio94 has joined #yocto
<LetoThe2nd> RDEPENDS supports version requirements like >= and such, but DEPENDS doesn't seem to. Is this accurate? If so, why? Any specific rationale?
zpfvo has joined #yocto
<Juanosorio94> Hey everyone, I am struggling for quite a while now trying to build a kernel module. I always get "nothing PROVIDES <module>" I tried copying the meta-skeleton hello-mod to my layer and doing bitbake hello-mod, I get the same error "nothing PROVIDES hello-mod", does anyone know what this could be? google hasnt been very helpful
<qschulz> Juanosorio94: what's the name of your recipe?
<Juanosorio94> I just took a better look at the layer.conf file, I was not putting it into a recipes-*/FOLDER/recipe.bb, the FOLDER was missing
<Saur[m]> LetoThe2nd: I am guessing a bit here, but: DEPENDS is handled by bitbake, while RDEPENDS is handled by rpm & co. Bitbake cannot handle multiple versions of a recipe, you have to choose one if multiple are available (e.g., by setting PREFERRED_VERSION). For rpm and the othe package managers on the other side, there may be multiple versions of the same package available if you use a package feed that you build up over time. Then it makes sense to be
<Saur[m]> able to specify package version requirements.
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<LetoThe2nd> Saur[m]: interesting take, thanksQ
zpfvo has quit [Ping timeout: 252 seconds]
nemik has quit [Ping timeout: 248 seconds]
zpfvo has joined #yocto
nemik has joined #yocto
zpfvo has quit [Ping timeout: 248 seconds]
zpfvo has joined #yocto
Schlumpf has joined #yocto
Juanosorio94 has quit [Ping timeout: 252 seconds]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
rber|res has joined #yocto
starblue has quit [Ping timeout: 252 seconds]
starblue has joined #yocto
camus1 has joined #yocto
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
kanavin has quit [Remote host closed the connection]
frieder has quit [Ping timeout: 255 seconds]
frieder has joined #yocto
kanavin has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<agherzan> zeddii: We have a small issue on https://git.yoctoproject.org/yocto-kernel-cache/tree/cfg/efi.cfg
<agherzan> The ACPI dependency there doesn't apply for arm32 and will generate a warning when used as such
davidinux has joined #yocto
<agherzan> Not even arm64 has that dependency. We don't get that warning though because it defaults to y with ARCH_SUPPORTS_ACPI
<agherzan> So long story short we need to lose the ACPI dependency on arm arch
<agherzan> On a second thought I would just drop it altogether. Because x86 also selects ARCH_SUPPORTS_ACPI which in turn enables ACPI by default for X86.
<agherzan> But that would not default to y on arm64 sadly.
seninha has joined #yocto
rperier has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
rperier has joined #yocto
florian has quit [Ping timeout: 268 seconds]
florian has joined #yocto
paowz_ has quit [Ping timeout: 244 seconds]
Guest7 has joined #yocto
<Guest7> Hello Community, short question, when using Exfat kernel drivers since kernel 5.7 (i.e. no longer the fuse drivers), the exfat-utils package is replace with the exfatprogs package. However I cannot find a recipe for the later one. Does anyone know if there is a reason for this?
<Guest7> *Cannot find a yocto recipe in the recipe index for exfatprogs
florian_kc has joined #yocto
<qschulz> Guest7: https://layers.openembedded.org/layerindex/branch/master/recipes/?q=exfat does not return anything interesting
<qschulz> So I guess you'll need to create your own recipe
dmoseley has quit [Quit: ZNC 1.8.2 - https://znc.in]
dmoseley has joined #yocto
paowz_ has joined #yocto
<pbergin> Guest7: https://github.com/openembedded/meta-openembedded/tree/master/meta-filesystems/recipes-utils/exfat-utils recipe for exfat-utils is present in meta-openembedded
<seninha> Hi, how can I get the path to the recipe for the linux kernel of a given bitbake target
<pbergin> Guest7: sorry. you probably looked for exfatprogs. read too quick
kscherer has joined #yocto
Ad0 has quit [Ping timeout: 252 seconds]
Ad0 has joined #yocto
zpfvo has quit [Ping timeout: 252 seconds]
<Guest7> qschulz thanks! Exactly, exfatprogs. I am more curious if I am overlooking something and maybe simply don't need the more recent package :-)
zpfvo has joined #yocto
Estrella has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
sakoman has joined #yocto
<Guest7> qschulz and who it might interest, I have a Gatesgarth based image, kernel 5.10.0, exfat support works combined with package exfat-utils_1.3.0.bb :-)   Have a great day!
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
Estrella has joined #yocto
camus has quit [Quit: camus]
<qschulz> Guest7: cool! have a nice day too
camus has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
Guest7 has quit [Quit: Client closed]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
pbergin has quit [Quit: Leaving]
goliath has quit [Quit: SIGSEGV]
DvorkinDmitry has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
frieder has quit [Remote host closed the connection]
Minvera has joined #yocto
amitk has quit [Ping timeout: 252 seconds]
Schlumpf has quit [Quit: Client closed]
amitk has joined #yocto
xmn has joined #yocto
Guest87 has joined #yocto
<Guest87> is there a clean way to get a recipe to fail if a certain variable is defined with 1?
<landgraf> Guest87: bb.error ?
<landgraf> see systemd_250.5.bb
<landgraf> for example
goliath has joined #yocto
florian has quit [Quit: Ex-Chat]
florian_kc has quit [Ping timeout: 268 seconds]
zpfvo has quit [Ping timeout: 268 seconds]
zpfvo has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #yocto
zpfvo has quit [Ping timeout: 248 seconds]
zpfvo has joined #yocto
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #yocto
zpfvo has quit [Quit: Leaving.]
sgw has joined #yocto
creich has joined #yocto
florian has joined #yocto
sgw has quit [Ping timeout: 255 seconds]
sakoman has quit [Quit: Leaving.]
leon-anavi has quit [Quit: Leaving]
goliath has quit [Quit: SIGSEGV]
adams[1] has joined #yocto
sakoman has joined #yocto
amitk has quit [Ping timeout: 268 seconds]
vvn has joined #yocto
ptsneves has quit [Ping timeout: 268 seconds]
Guest87 has quit [Quit: Connection closed]
<smurray> khem: I do see a boot delay wrt /dev/hwrng now with my AGL testing against master, is there something in flight wrt that?
<khem> smurray: I have a patch here https://git.yoctoproject.org/poky-contrib/log/?h=yoe/mut
<khem> I still need to test a bit more
<smurray> khem: okay, I can try it here once my current build finishes
<jonmason> Is it just my setup or is the new gdk-pixbuf_2.42.9.bb not happy at all (refusing to compile on every platform in poky)?
<smurray> khem: the jitter entropy stuff does seem a bit of a mess indeed. We configure a virtio-rng device in the default AGL configuration so we might sidestep some of that, but I'm not sure, tbh
<kekiefer[m]> khem tagging kernel hw_random in udev (patch to systemd's udev rules file) lets the rng-tools startup find the /dev/hwrng device for systems that do have hwrandom, if it's desirable to create a `Wants=dev-hwrng.device` dependency for systems that do have hardware rng
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
<sotaoverride> Can someone walk me through version-going-backwards QA error. Trying to figure out what causes them.
xmn has quit [Quit: xmn]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
Ad0 has quit [Ping timeout: 252 seconds]
Ad0 has joined #yocto
<sotaoverride> whats the right way of removing previously written packes to get rid of version-going-backwards errors?
<JPEW> sotaoverride: You need to delete (or disable) buildhistory.bbclass IIRC
<JPEW> sotaoverride: Err, don't delete the class, delete the data it creates :)
<sotaoverride> ummmm ok
<sotaoverride> what dir is that usually
<JPEW> ${BUILDHISTORY_DIR} ?
<sotaoverride> cool, thanks. Ill look at the bbclass too.
<JPEW> sotaoverride: I think that class is the one that generates the error in the first place
<sotaoverride> cool, yeah I was just taking a look t it to get to the path
<JPEW> sotaoverride: You can also make the warning non-fatal if you don't really care; we do this a lot for recipes that include the git-sha1 in the version since those aren't orderable
<sotaoverride> how do u do that?
<JPEW> `ERROR_QA:remove = "version-going-backwards"` and if you want to keep it as a warning `WARN_QA:append = "version-going-backwards"`
<sotaoverride> hmm, ok. I put that in the conf somewhere or my image recipe?
<JPEW> sotaoverride: local.conf... we put it in our custom distro
mvlad has quit [Remote host closed the connection]
<sotaoverride> cool! thanks!
<JPEW> Won't do any good in the image recipe because it needs to be global
<sotaoverride> makes sense
* JPEW LetoThe2nd has memorable saying for that.... that I can't recall ATM :)
xmn has joined #yocto
<smurray> khem: for what it's worth your tweak to the dependencies in that yoe-mut change gets my AGL test image booting w/o the delay, and rngd is started
dmoseley has quit [Quit: ZNC 1.8.2 - https://znc.in]
dmoseley has joined #yocto
dmoseley has quit [Remote host closed the connection]
<khem> smurray: can you post the journal logs of rng-tools.service somewhere
<khem> there was a dependency cycle that RP observed on AB
dmoseley has joined #yocto
<khem> I have tried to address it but not tested on my end yet other than on a rv64 qemu
<smurray> that's me running with kvm, though
<smurray> which might make a difference, maybe
<khem> oh nice .. it that with -x jitter ?
<smurray> no, that's with your patch as is
Minvera has quit [Remote host closed the connection]
<khem> yeah kvm will paravirtualize rng
sgw has joined #yocto
<smurray> khem: I would have thought the use of virtio-rng in the default QB_RNG definition would help for non-kvm, as you'd hope qemu is effectively passing through the host /dev/urandom
<smurray> khem: but I'm just guessing
<khem> virtio-rng helps with kvm too
<smurray> khem: output is the same if I drop kvm, but it's noticeable that the jitter init takes some time, like 25s
<khem> yeah for non hwrng case we should perhaps add haveged to images
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
<khem> 25s is perhaps not that bad
<smurray> I thought the theory was the jitterentropy stuff in rngd effectively replaces haveged? Or am I misremembering
<smurray> or is it that the startup behavior of haveged is just more forgiving?
<khem> yeah jitterentropy had issues in past
<khem> maybe its better now
<khem> I think HRT are needed for it to work reliably IIRC
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
DvorkinDmitry has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
<DvorkinDmitry> why it is not recommended to pre-generate /etc/ssh/keys at the image build time ? I have slow CPU and my first ssh connection takes about 1 min
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
olani has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
kevinrowland has joined #yocto
olani has quit [Ping timeout: 252 seconds]
florian has quit [Ping timeout: 248 seconds]
olani has joined #yocto
Tokamak has joined #yocto
tlwoerner has quit [Read error: Connection reset by peer]
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
kscherer has quit [Quit: Konversation terminated!]
sgw has quit [Ping timeout: 248 seconds]
tlwoerner has joined #yocto
sgw has joined #yocto
Tokamak has quit [Ping timeout: 256 seconds]
Tokamak has joined #yocto