LetoThe2nd changed the topic of #yocto to: Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Community: https://www.yoctoproject.org/community | IRC logs: http://irc.yoctoproject.org/irc/ | Having difficulty on the list, with someone on the list or on IRC, contact Yocto Project Community Manager Letothe2nd | CoC: https://www.yoctoproject.org/community/code-of-conduct
reatmon_ has quit [Remote host closed the connection]
reatmon_ has joined #yocto
qschulz has quit [Read error: Connection reset by peer]
qschulz has joined #yocto
<MattWeb82> I'm looking into using katacontainers from meta-virt and noticed some "broken, patches accepted". Figured I ask here while we dig for more details / fix it
tgamblin__ has joined #yocto
tgamblin_ has quit [Ping timeout: 248 seconds]
Jones42__ has joined #yocto
Jones42_ has quit [Ping timeout: 265 seconds]
jclsn has quit [Ping timeout: 252 seconds]
jclsn has joined #yocto
Jones42_ has joined #yocto
Jones42__ has quit [Ping timeout: 248 seconds]
xmn has joined #yocto
|Xagen has joined #yocto
Xagen_ has joined #yocto
Xagen has quit [Ping timeout: 248 seconds]
Xagen has joined #yocto
Xagen__ has joined #yocto
Xagen___ has joined #yocto
|Xagen has quit [Ping timeout: 248 seconds]
|Xagen has joined #yocto
Xagen_ has quit [Ping timeout: 272 seconds]
Xagen has quit [Ping timeout: 248 seconds]
Vonter has joined #yocto
Xagen has joined #yocto
Xagen__ has quit [Ping timeout: 272 seconds]
Xagen_ has joined #yocto
Xagen___ has quit [Ping timeout: 272 seconds]
Xagen__ has joined #yocto
Xagen___ has joined #yocto
|Xagen has quit [Ping timeout: 272 seconds]
|Xagen has joined #yocto
Xagen has quit [Ping timeout: 248 seconds]
Xagen has joined #yocto
Xagen_ has quit [Ping timeout: 248 seconds]
Xagen__ has quit [Ping timeout: 252 seconds]
Xagen_ has joined #yocto
Xagen___ has quit [Ping timeout: 248 seconds]
Xagen__ has joined #yocto
Xagen___ has joined #yocto
|Xagen has quit [Ping timeout: 272 seconds]
|Xagen has joined #yocto
Xagen has quit [Ping timeout: 258 seconds]
Xagen_ has quit [Ping timeout: 252 seconds]
Xagen has joined #yocto
Xagen__ has quit [Ping timeout: 252 seconds]
Xagen_ has joined #yocto
Xagen___ has quit [Ping timeout: 258 seconds]
Xagen__ has joined #yocto
|Xagen has quit [Ping timeout: 252 seconds]
|Xagen has joined #yocto
Xagen___ has joined #yocto
Xagen has quit [Ping timeout: 258 seconds]
Xagen_ has quit [Ping timeout: 252 seconds]
Xagen has joined #yocto
Xagen__ has quit [Ping timeout: 252 seconds]
|Xagen has quit [Ping timeout: 258 seconds]
Xagen_ has joined #yocto
Xagen___ has quit [Ping timeout: 252 seconds]
Xagen has quit [Ping timeout: 252 seconds]
Articulus has joined #yocto
Minvera has quit [Ping timeout: 272 seconds]
rob_w has joined #yocto
rob_w has quit [Ping timeout: 252 seconds]
BenBE has quit [Ping timeout: 252 seconds]
rob_w has joined #yocto
xmn has quit [Quit: ZZZzzz…]
m4h0 has joined #yocto
khem has quit [Quit: WeeChat 4.4.0]
m4h0 has quit [Ping timeout: 265 seconds]
goliath has joined #yocto
BenBE has joined #yocto
ehussain has joined #yocto
mckoan_ has joined #yocto
ahussain has joined #yocto
ehussain has quit [Ping timeout: 248 seconds]
ahussain is now known as ehussain
mckoan|away has quit [Ping timeout: 248 seconds]
mhomuth has joined #yocto
alessioigor has joined #yocto
frieder has joined #yocto
mvlad has joined #yocto
zpfvo has joined #yocto
mckoan_ is now known as mckoan
<mckoan> good morning
dmoseley has quit [Ping timeout: 252 seconds]
dmoseley has joined #yocto
<alessioigor> mckoan: to you
mhomuth has quit [Ping timeout: 276 seconds]
ecdhe has quit [Ping timeout: 272 seconds]
Kubu_work has joined #yocto
ecdhe has joined #yocto
Haxxa has quit [Remote host closed the connection]
Haxxa has joined #yocto
mbulut has joined #yocto
dmoseley has quit [Ping timeout: 265 seconds]
dmoseley has joined #yocto
florian has joined #yocto
zeddii has quit [Ping timeout: 272 seconds]
zeddii has joined #yocto
ehussain has quit [Ping timeout: 260 seconds]
ehussain has joined #yocto
lexano has quit [Ping timeout: 258 seconds]
dmoseley_ has joined #yocto
dmoseley has quit [Ping timeout: 244 seconds]
lexano has joined #yocto
ahussain has joined #yocto
ehussain has quit [Ping timeout: 276 seconds]
ahussain is now known as ehussain
zpfvo has quit [Ping timeout: 265 seconds]
zpfvo has joined #yocto
frieder has quit [Remote host closed the connection]
florian_kc has joined #yocto
Alonesoul has joined #yocto
Alonesoul has quit [Client Quit]
yocti` has joined #yocto
yocti has quit [Killed (NickServ (GHOST command used by yocti`))]
yocti` is now known as yocti
zpfvo has quit [Ping timeout: 255 seconds]
fotte has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
Jones42_ has quit [Ping timeout: 252 seconds]
<landgraf> is docs.y.o down?
<landgraf> HTTP request sent, awaiting response...
<landgraf> s/down/veeeery slow/
mihai has joined #yocto
<mckoan> landgraf: fast as usual here
Jones42 has joined #yocto
zpfvo has joined #yocto
<fotte> mckoan: mcfrisk: Just in case anotherone asks the same question: The solution to get the devicetree into the rootfs (and therefor into the image), was a simpel IMAGE_INSTALL:append = " kernel-devicetree" - in my case.
RP has quit [Server closed connection]
<mckoan> fotte: thank you for sharing it
RP has joined #yocto
frieder has joined #yocto
wojci has joined #yocto
<landgraf> mckoan: and https://docs.yoctoproject.org/dev/ref-manual/variables.html?highlight=preferred_version ? both browser and wget take ages to open (tested from two different locations)
<landgraf> in fact wget is trying to download the page for more than 20 minutes now variables.html?highlight=preferred_version 6%[+===> ] 63.48K --.-KB/s eta 3h 1m
Guest13 has joined #yocto
<Guest13> hi. assuming i have to build a yocto image for a system that has different requirements (e.g, different services running, configurations, etc...) X and Y.
<Guest13> is there any standard way of handling this? is creating separate layers for those the right approach?
mbulut_ has joined #yocto
mbulut has quit [Ping timeout: 245 seconds]
<mckoan> landgraf: no problems here
<mckoan> Guest13: depends (TM)
<mckoan> Guest13: usually different services running, configurations, etc... can/should be in the same layer
<mckoan> Guest13: usually a new layer is needed when you have a new set of features with the same purpose
<Guest13> And what is the preferred method of "controlling" which services I am gonna run? Is there some sort of tool for "profiles" ?
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
prabhakalad has quit [Ping timeout: 272 seconds]
prabhakalad has joined #yocto
leon-anavi has joined #yocto
<rber|res> @flotte Yes this works, but then again it is most likely machine dependent, so you might want to have a look at my blog here: https://reliableembeddedsystems.com/blog/yocto-project-kernel-modules-not-showing-up-in-the-rootfs/
<rber|res> @Guest13 I would say that different services running/packages installed should be a an image recipe, configurations depends what you mean by that
Marmottus11 has quit [Server closed connection]
<Guest13> rber|res but do all software modules go into the image? how do you control what is running at runtime? my goal is to be able to switch from X to Y (so everything has to be in the image)
Marmottus11 has joined #yocto
<rber|res> @Guest13 if you install a package it typically contains also the startup scripts. You could have different images with different packages installed.
cambrian_invader has quit [Server closed connection]
cambrian_invader has joined #yocto
<rber|res> @Guest13 All software modules you define an your image recipe go into the image. At least at this point you should know which services should run. Typically if you install a service it is started by default.
<rber|res> @Guest13 You mean you want one image and then configure it manually? That's not quite the idea, but it is possible.
<rber|res> @Guest13 do you have an example for switching from X to Y?
<Guest13> Well yes and no. X services can be enabled by default. But if I want, I should be able to switch to profile Y so i can re-use the board computer for another purpose if needed
<Guest13> If that makes sense
<rber|res> @Guest13 With the Yocto Project you create your own custom distro, so you can do whatever you like, but typically you would ONLY install the packages, which are needed on your target.
<rber|res> @Guest13 This would probably mean that if your target board is used for different project, than you create 2 different images.
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
ehussain has quit [Quit: ehussain]
wCPO has quit [Server closed connection]
wCPO has joined #yocto
dmoseley_ has quit [Ping timeout: 258 seconds]
dmoseley has joined #yocto
<fotte> slides
Bardon_ has quit [Server closed connection]
Bardon has joined #yocto
RobertBerger has joined #yocto
rber|res has quit [Ping timeout: 255 seconds]
Xagen_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Minvera has joined #yocto
olani has quit [Remote host closed the connection]
wojci has quit [Remote host closed the connection]
rob_w has quit [Remote host closed the connection]
xmn has joined #yocto
Jones42 has quit [Ping timeout: 248 seconds]
Jones42 has joined #yocto
olani has joined #yocto
jmd has joined #yocto
Xagen has joined #yocto
<MattWeb82> I'm looking into using katacontainers from meta-virt and noticed some "broken, patches accepted". Figured I ask here while we dig for more details / fix it
dgriego has joined #yocto
fotte has quit [Quit: Leaving]
dgriego has quit [Client Quit]
goliath has quit [Quit: SIGSEGV]
dgriego has joined #yocto
Guest13 has quit [Quit: Client closed]
usvi has quit [Server closed connection]
usvi has joined #yocto
svuorela has quit [Server closed connection]
svuorela has joined #yocto
Ch^W has quit [Server closed connection]
Ch^W has joined #yocto
khem has joined #yocto
<khem> denix: https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/4058/steps/15/logs/stdio says ftgl is failing to build you touched it last time do we still need this recipe
Articulus has quit [Quit: Leaving]
frieder has quit [Remote host closed the connection]
risca has quit [Server closed connection]
risca has joined #yocto
leon-anavi has quit [Remote host closed the connection]
BenBE has quit [Ping timeout: 258 seconds]
<khem> pep-517 created implicit dep on cython which means .c files will be regenerated no matter if one want to use release tarballs and use the bundled .c files and cython offers no option like --sysroot so it happily encodes absolute paths into .c files, what a mess
florian has quit [Quit: Ex-Chat]
<khem> It would have helped if the logic in backend would sense the existence of .c files and not rebuild them if user wanted to do so
crazy_imp has quit [Server closed connection]
crazy_imp has joined #yocto
florian_kc has quit [Ping timeout: 276 seconds]
tgamblin__ is now known as tgamblin
<rfs613> a bit surprising to me: switching from SSD (SATA III 6gps) to NVMe (PCIe x4) did not change my yocto build times at all. I figured it would be at least partly I/O bound, but evidently not.
Kubu_work has quit [Quit: Leaving.]
ecdhe has quit [*.net *.split]
Perflosopher has quit [*.net *.split]
tec has quit [*.net *.split]
wicki4 has quit [*.net *.split]
Shaun has quit [*.net *.split]
fray has quit [*.net *.split]
fray has joined #yocto
ecdhe has joined #yocto
Shaun has joined #yocto
wicki4 has joined #yocto
tec has joined #yocto
Perflosopher has joined #yocto
Kubu_work has joined #yocto
<qschulz> rfs613: did you benchmark both?
<qschulz> also which gen of PCIe
<qschulz> and are you sure the link is negotiated on 4 lanes?
<rfs613> qschulz: the drive is GEN4 but perhaps my mobo doesn't have all lanes enabled or working
<rfs613> I ran the same build on both (keeping the downloads directory, but wiping everything else sstate-cache, tmp-myboard, etc)
jmd has quit [Remote host closed the connection]
<rfs613> mobo document says it supports PCIe x4/x2
<qschulz> rfs613: you can benchmark your disks with fio
<qschulz> rfs613: which gen on the mobo AND CPU :) ?
<qschulz> lspci -vv and look for LnkSta:
<rfs613> ah i was just digging into the "nvme" tool
<qschulz> rfs613: be careful with fio, it can be run on block devices too, like dd, and thus be destructive
mckoan is now known as mckoan|away
<rfs613> qschulz: LnkSta: Speed 8GT/s (ok), Width x4 (ok)
<qschulz> gen4 4 lanes then
<qschulz> maybe the nvme isn't a good one? you can try to benchmark with fio
<rfs613> hmm, i have another one though, that's only 2.5GT/s and x1
Kubu_work has quit [Quit: Leaving.]
<rfs613> now i have to figure out which one is which ;-)
zpfvo has quit [Remote host closed the connection]
alessioigor has quit [Remote host closed the connection]
jmd has joined #yocto
<khem> rfs613: linux does good use of using ram as buffer, how much ram do you have ?
<khem> secondly, which filesystem did you put on them hopefully same
<rfs613> khem: both ext4, both 1 TB total, both made with same mkfs.ext4 command
<rfs613> khem: machine has 32G and yes, about 27G of that shows up as buffer/cache typically
<rfs613> qschulz: did quick read test with hdparm -t, shows 535 MB/s for SATA (about what you'd expect) and about 2400 MB/s for the NVMe
mbulut_ has quit [Ping timeout: 252 seconds]
florian_kc has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
florian_kc has quit [Ping timeout: 252 seconds]
<JaMa> zeddii: around? https://git.yoctoproject.org/meta-virtualization/commit/?id=a940a0e873f9163d4585555b3f3d38e99400d237 doesn't seem to wrok well when PREFERRED_VERSION is set to e.g. "6.6.%", you remove the '%' but not the trailing dot and ERROR: Nothing PROVIDES 'yocto-cfg-fragments-6.6.-native'. Close matches: yocto-cfg-fragments-6.10-native yocto-cfg-fragments-6.6 yocto-cfg-fragments-6.6-native
florian_kc has joined #yocto
frieder has joined #yocto
frieder has quit [Remote host closed the connection]
florian_kc has quit [Ping timeout: 255 seconds]
<mischief> is there such a thing as combined features for machine+image?
florian_kc has joined #yocto
mvlad has quit [Remote host closed the connection]
<JaMa> machine+distro=combined
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
mbulut_ has joined #yocto
Haxxa has quit [Quit: Haxxa flies away.]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
Kubu_work has joined #yocto
Haxxa has joined #yocto
mbulut has joined #yocto
Kubu_work has quit [Ping timeout: 252 seconds]
<mbulut> i have sth weird going on with one of my kernel append recipes: the recipe hierarchy is linux-imx_5.15.bbappend -> linux-imx_5.15.bbappend -> linux-imx_5.15.bb, where the middle one is in some intermediate layer
<mbulut> in my append i provide a defconfig which i specify in SRC_URI and same goes for FILESEXTRAPATHS -- business as usual
<mbulut> however when I try to access my defconfig via ${WORKDIR}/defconfig it's not there!?
<mbulut> and when i inspect WORKDIR in the file system, the file is indeed not there? any idea how i could have managed to break something that fundamental?
prabhakalad has quit [Ping timeout: 248 seconds]
prabhakalad has joined #yocto
Kubu_work has joined #yocto
<mbulut> inspecting the output of `bitbake -e linux-imx | grep ^FILESPATH` i can see my recipe folder
jmd has quit [Remote host closed the connection]
rber__ has joined #yocto
RobertBerger has quit [Ping timeout: 260 seconds]
mbulut_ has quit [Ping timeout: 276 seconds]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<JaMa> mbulut: latest oe-core? if yes, then check UNPACKDIR not WORKDIR
<mbulut> no, it's kirkstone
<mbulut> 4.0.2
<JaMa> did you check with bitbake-getvar or bitbake e, that it's in SRC_URI?
<mbulut> yeah i did
<JaMa> read log.do_unpack
<mbulut> see my previous message, the folder is in FILESPATH
<mbulut> what shall i look for in log.do_unpack?
<mbulut> my recipe basically just provides some kernel config delta files to the linux-imx recipe
<mbulut> the delta files are provided using SRC_URI and FILESEXTRAPATHS + a DELTA_KERNEL_DEFCONFIG variable that tells the upstream recipe "here are my deltas"
<mbulut> but it can't find them in WORKDIR, although as said, i've done the usual things to do when adding files to a recipe
<mbulut> i've put bb logs in the upstream recipe and my delta files just don't exist in that context (heck, they don't even exist in my bbappend when i try to access them from there)
<mbulut> ohhhh fuck, no they aren't
<mbulut> i had only checked FILESEXTRAPATHS
<mbulut> they indeed aren't in SRC_URI
<mbulut> is something overwriting SRC_URI?
<JaMa> bitbake-getvar will tell you
<mbulut> JaMa, thx mate that helped a ton! i didn't know about that command
Kubu_work has quit [Quit: Leaving.]
<mbulut> i see 9 operations on the variable and if i assume correct to read it from top to bottom, some .inc file just = assigns to it so my stuff is gone
<mbulut> but shouldn't my bbappend be processed last? how is that even possible?
<JaMa> depends where the .inc file is included or if it uses some override etc, you can also use :append to defer appending your SRC_URI entries later, "bitbake -e" shows the same information as bitbake-getvar
<JaMa> but you won't see if if you just grep for the variable (that's why in most cases I store the output in file, because you never know what next variable you might get interested in while reading the variable history)
<mbulut> isn't :append equivalent to += except for the convenience space in the latter?
<JaMa> no
<mbulut> oh!
<mbulut> i thought they were -- good to know
<mbulut> changed it to append and i see my files now! at least in the variable
<mbulut> dude
<mbulut> thx a huge ton man
<mbulut> i was going almost nuts on this
<JaMa> learn to use bitbake-getvar every time something seems wrong with metadata, it's always right and helps with trivial cases like this or even with more complicated ones (or forgotten modifications in some long forgotten file)
florian_kc has quit [Ping timeout: 252 seconds]
<mbulut> yeah thx, i'll definitely stick that behind my ears
<mbulut> i was using bitbake -e already (though i didn't know about the bitbake-getvar) but as you said, i almost always used it followed by a grep ^MYVAR as i didn't know that the output revealed information about the modification history of a given variable
<mbulut> that's very useful to know
mbulut has quit [Ping timeout: 245 seconds]
josch91 has joined #yocto
<josch91> JPEW, tlwoerner: what is the current status of bmaptool? The last activity from you seems to have been in May. I'd like to contribute but would need some feedback for the 4 pull requests I filed. Thank you!
Xagen has joined #yocto