Friday, 2021-04-16

*** kiwi_29 <kiwi_29!> has joined #yocto00:14
*** kiwi_29 <kiwi_29!> has quit IRC00:19
*** kpo_ <kpo_!> has quit IRC00:37
*** gpanders <gpanders!> has joined #yocto01:00
*** vineela <vineela!~vtummala@> has quit IRC01:25
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:51
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:51
*** nvmd <nvmd!~nvmd@> has quit IRC01:51
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC02:06
*** sakoman <sakoman!~steve@> has quit IRC02:17
*** Spooster <Spooster!> has quit IRC02:26
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC02:40
*** armpit <armpit!~armpit@2601:202:4180:a5c0:c6a:9ade:28ad:18c> has quit IRC02:41
*** armpit <armpit!~armpit@2601:202:4180:a5c0:c04b:7c7a:dc8:bb2> has joined #yocto02:47
*** ahadi <ahadi!> has quit IRC02:58
*** ahadi <ahadi!> has joined #yocto03:04
*** prabhakarlad <prabhakarlad!> has quit IRC03:41
*** camus <camus!~Instantbi@> has joined #yocto04:58
*** kaspter <kaspter!~Instantbi@> has quit IRC04:58
*** camus is now known as kaspter04:58
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:ed2d:51fd:a423:7329> has joined #yocto05:03
*** vineela <vineela!~vtummala@> has joined #yocto05:04
*** AndersD <AndersD!> has joined #yocto05:23
*** vineela <vineela!~vtummala@> has quit IRC05:25
*** AndersD_ <AndersD_!> has joined #yocto05:25
*** Spooster <Spooster!> has joined #yocto05:26
*** AndersD <AndersD!> has quit IRC05:28
*** grumble <grumble!~Thunderbi@freenode/staff/grumble> has quit IRC05:31
vdl$systemd_system_unitdir points to /usr/lib/systemd/system. Which one points to /etc/systemd/system?05:33
*** jobroe <jobroe!> has joined #yocto05:49
*** jobroe_ <jobroe_!> has joined #yocto05:54
*** jobroe <jobroe!> has quit IRC05:55
*** Spooster <Spooster!> has quit IRC06:00
*** dreyna_ <dreyna_!> has quit IRC06:00
*** Spooster <Spooster!> has joined #yocto06:01
*** Spooster <Spooster!> has quit IRC06:05
*** SinthuRaja <SinthuRaja!dfba4046@> has joined #yocto06:07
*** kiwi_29 <kiwi_29!> has joined #yocto06:16
*** kiwi_29 <kiwi_29!> has quit IRC06:20
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto06:25
*** jobroe_ <jobroe_!> has quit IRC06:30
*** jobroe <jobroe!> has joined #yocto06:31
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto06:31
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto06:32
LetoThe2ndyo dudX06:32
*** kaspter <kaspter!~Instantbi@> has quit IRC06:39
*** camus <camus!~Instantbi@> has joined #yocto06:40
*** w00die <w00die!~w00die@> has quit IRC06:41
*** camus is now known as kaspter06:42
*** w00die <w00die!~w00die@> has joined #yocto06:43
*** skskjaks <skskjaks!677f17cd@> has joined #yocto06:45
skskjaksi added some packages in my yocto build and i want to boost it via sd card. so i have to just add .rootfs.tar.gz in rootfs partition of my sd card? or i have to dd all the zImage and oftree again? thanks06:47
LetoThe2ndskskjaks: it depends. i presume that you are already booting from the sd card? or are we talking about changing the whole boot strategy?06:52
*** SinthuRaja <SinthuRaja!dfba4046@> has quit IRC07:05
skskjaksyes i am already booting from sd card07:16
*** caiortp <caiortp!> has joined #yocto07:16
*** andycooper <andycooper!uid246432@gateway/web/> has quit IRC07:20
*** prabhakarlad <prabhakarlad!> has joined #yocto07:26
*** skskjaks <skskjaks!677f17cd@> has quit IRC07:33
*** Jonek <Jonek!> has joined #yocto07:35
*** TPRoberts <TPRoberts!~TPRoberts@2a00:23c6:7494:8700:f09e:7cf5:58f5:b52a> has joined #yocto07:36
*** tnovotny <tnovotny!> has joined #yocto07:37
LetoThe2ndand what form does the current rootfs have on sdcard?07:41
LetoThe2ndusually one does not use a tar.gz, but it being expanded to a partition.07:42
*** mckoan|away is now known as mckoan07:44
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto07:44
*** oberstet <oberstet!~oberstet@> has joined #yocto07:49
yannzeddii: did you have any time for kernel bsp ?07:53
*** goliath <goliath!> has joined #yocto08:35
*** dreyna_ <dreyna_!> has joined #yocto08:35
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:36
dl9pfscott is fixing already08:51
*** armpit <armpit!~armpit@2601:202:4180:a5c0:c04b:7c7a:dc8:bb2> has quit IRC08:53
*** alephan <alephan!andreicubi@gateway/shell/> has quit IRC09:00
*** TPRoberts <TPRoberts!~TPRoberts@2a00:23c6:7494:8700:f09e:7cf5:58f5:b52a> has quit IRC09:13
*** Jonek <Jonek!> has quit IRC09:16
*** mischief <mischief!> has quit IRC09:18
*** tnovotny <tnovotny!> has quit IRC09:21
*** mischief <mischief!> has joined #yocto09:22
*** caiortp <caiortp!> has quit IRC09:22
*** mischief is now known as Guest7593009:23
*** TPRoberts <TPRoberts!~TPRoberts@> has joined #yocto09:26
*** armpit <armpit!> has joined #yocto09:32
*** Guest75930 is now known as mischief09:34
*** harunn <harunn!> has joined #yocto09:44
harunnHello, how can I create an initramfs and add it to a .wic image?09:45
harunnI have tried it, although the wic image is larger now. The Kernel is not booting with it.09:45
harunnThis is my initramfs image
harunnI have included these variables to machine.conf:09:45
harunnINITRAMFS_IMAGE = "image-initramfs"09:45
harunnIMAGE_BOOT_FILES_append = " ${KERNEL_IMAGETYPE}-initramfs-${MACHINE}.bin09:45
*** prabhakarlad <prabhakarlad!> has quit IRC09:56
*** dreyna_ <dreyna_!> has quit IRC09:58
*** harunn <harunn!> has quit IRC10:00
*** harunn <harunn!> has joined #yocto10:00
rob_wis the initrd missing or is the boot crashing ??10:00
rob_wharunn, ^^10:01
harunnIt is booting, but theres is no initrd in /boot10:02
harunnPrior I had no  initrd, maybe both kernels are in the wic images?10:03
harunnWith both, I main the bundled and the "default" one10:03
rob_wnever used them wic but its good question if you expsect the initrd to be bundled to the kernel image or as separete file10:05
qschulzI don't remember if we have examples for npm recipes? Basically my use case is a local build with npm that has dependencies in the registry10:08
rob_whow to you reference it at your kernel boot cmd ?10:08
harunnI have not referenced it in the kernel boot cmd.10:10
harunnShouldn't the kernel "just start it" when it is bundled with the initrd?10:10
rob_wyes thats what INITRAMFS_IMAGE_BUNDLE so do10:11
rob_wwasnt there a extra kernel option to  make this work in the first place10:14
*** yann|work <yann|work!~yann@> has joined #yocto10:17
rob_wdid you rebuild your kernel harunn ?10:17
rob_wso what is in your /boot ? the kernel with initrd should be named differntly10:18
rob_wand that would be the one you refrence in u-boot either directly or symlinks or such10:19
*** camus <camus!~Instantbi@> has joined #yocto10:20
*** yann <yann!~yann@> has quit IRC10:20
*** kaspter <kaspter!~Instantbi@> has quit IRC10:21
*** camus is now known as kaspter10:21
harunnyes, in /boot are only u-boot, the zImage and a few symlinks.10:22
*** goliath <goliath!> has quit IRC10:22
rob_wwell i bet zImag is a symlink .. but to which kernel10:22
harunnTo the unbundled kernel.10:24
harunnThere has to be a "fat kernel" right?10:24
rob_wthat doesnt sound right , does it ?10:24
harunnno, but why?^^10:24
rob_wis the name telling you which kernel is which .. but yeah the "fatter" one is likely the one with the initrd appended10:24
rob_wdunno who sets the default zImage symlink in the scripts , sorry10:25
*** suniel <suniel!724fbc13@> has joined #yocto10:26
sunielHello all10:26
sunielI am trying to secure boot linux. My hardware is a freescale arm64 i.MX8M mini SOC based platform.10:26
sunielI am using meta-security/meta-integrity to sign my rootfs. For some reason my keys are not getting10:26
sunielloaded by linux integrity subsystem:10:26
sunielintegrity: Loading X.509 certificate: /etc/keys/x509_ima.der10:26
sunielintegrity: Problem loading X.509 certificate -12610:26
sunielany pointers/suggestions ? Thank you10:27
harunnrob_w: yes, I can distinguish them10:28
rob_wharunn, so we have to fix the symlink in your case ,,10:29
harunnI see10:30
*** harunn <harunn!> has quit IRC10:41
*** Jonek <Jonek!> has joined #yocto10:42
*** harunn <harunn!> has joined #yocto10:51
*** suniel <suniel!724fbc13@> has quit IRC10:56
*** suniel <suniel!724fbc13@> has joined #yocto11:03
*** escalion <escalion!> has joined #yocto11:10
escalionAfternoon all11:10
*** tnovotny <tnovotny!> has joined #yocto11:15
*** Jonek <Jonek!> has quit IRC11:30
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto11:34
*** suniel <suniel!724fbc13@> has quit IRC11:49
*** suniel <suniel!724fbc13@> has joined #yocto11:50
escalionqschulz: I looked into SPLASH_IMAGES again, turns out I had it set in my bbappend by: SPLASH_IMAGES_append = " file://psplash-img.png;outsuffix=test" This subsequently oe-pkgdata-util find-path '/usr/bin/psplash-test', but it still does not end up installed on the rootfs. More digging inbound11:51
escalionIn other news I fixed the annoying white flash of blinding light when loading chromium and also disabled cursor on weston when a cursor plane is available (but not used)11:52
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:ed2d:51fd:a423:7329> has quit IRC11:52
escalionI'm starting to get the hang of yocto :) (I migrated from buildroot)11:53
*** yannholo <yannholo!> has joined #yocto11:55
*** prabhakarlad <prabhakarlad!> has joined #yocto11:58
qschulzescalion: you probably need to add the package returned by oe-pkgdata-util find-path to your image recipe?12:03
escalionIt's already added, that's the head scratcher12:04
qschulzescalion: yup, that seems like it, RDEPENDS_${pn}-test will be set to ${PN} automatically but that's about it12:05
escalionI compiled with IMAGE_INSTALL_append += " psplash psplash-test"12:05
escalionI need to add some debugging to the recipe and see whats happening. Computer tied up with another chromium build now12:06
escalionBecause I need to get ICECC set up to work with clang somehow :312:07
*** wooosaiiii <wooosaiiii!> has quit IRC12:08
*** savolla <savolla!~savolla@> has joined #yocto12:21
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC12:43
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto12:44
*** Spooster <Spooster!> has joined #yocto12:52
iopaniukhi everyone. Is there any way to somehow specify offset in bytes in wks file (instead of kbytes) ? (
yatespart of the toolchain build includes a gcc-runtime package. where do the files for this package come from?13:01
yatesi do not see the typical "git" folder in the <build>/tmp/work/<arch>/gcc-runtime13:02
iopaniukI've tried already partial values, like 32.5 (I have to write cust meta-data to offset 0x8200), it's neither supported, bitbake just reports ERROR: ../sdimage-imx8-spl-sota.wks:17: argument --offset: Invalid size: '32.5'13:03
yatescorrection: i do not see the typical "git" folder in the <build>/tmp/work/<arch>/gcc-runtime/<PR>/13:04
yateskhem: ?13:05
yatesany thoughts?13:05
* yates listens to some Deep Purple13:12
yatesiopaniuk: i haven't looked, but you might try looking at
escalioniopaniuk: under the hood the wks is using mkfs.FSTYPE - so any option that you can use with mkfs should be accepted. Source in poky/scripts/lib/wic/partition.py13:19
*** BobPungartnik <BobPungartnik!~BobPungar@> has joined #yocto13:44
*** BobPungartnik <BobPungartnik!~BobPungar@> has quit IRC13:47
*** roussinm1 <roussinm1!> has quit IRC13:56
*** jobroe <jobroe!> has quit IRC14:00
*** sakoman <sakoman!~steve@> has joined #yocto14:02
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:ed2d:51fd:a423:7329> has joined #yocto14:26
*** geheimnis` <geheimnis`!~geheimnis@> has quit IRC14:28
*** geheimnis` <geheimnis`!~geheimnis@> has joined #yocto14:29
*** AndersD_ <AndersD_!> has quit IRC14:48
*** kaspter <kaspter!~Instantbi@> has quit IRC14:58
*** harunn <harunn!> has quit IRC15:02
*** thekappe <thekappe!c65a42b1@> has joined #yocto15:13
thekappehello guys, I'm running yocto (thud) and I have installed kpartx in the rootfs15:13
thekappeif I try to list the partition inside the generated wic image on the target:15:14
*** thekappe <thekappe!c65a42b1@> has left #yocto15:14
*** tnovotny <tnovotny!> has quit IRC15:14
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto15:21
*** TPRoberts <TPRoberts!~TPRoberts@> has quit IRC15:27
*** goliath <goliath!> has joined #yocto15:42
*** NiniC0c0 <NiniC0c0!> has joined #yocto15:46
*** dev1990 <dev1990!> has quit IRC15:48
NiniC0c0Hello dear Yocto Wozard! What is the best (if possible) to configure a recipe according the image name ? The purpose is to build differently the "apps" recipe based on some variable set inside the image recipe or maybe be I have to use IMAGE_FEATURES but to sure to choose the best option... If someone can point me the best direction. Thank you!15:49
escalionNiniC0c0: You can define applications to install for a specific image using IMAGE_INSTALL in the image definition15:52
escalionA nice out of tree example:
qschulzNiniC0c0: Yocto chant #115:56
qschulzNiniC0c0: recipe data is local15:56
qschulzconf data is global15:56
qschulzso no, you cannot modify a recipe from another recipe (and image recipes are... recipes :) )15:56
*** thekappe <thekappe!c65a42b1@> has joined #yocto15:57
*** thekappe <thekappe!c65a42b1@> has left #yocto15:57
qschulzso either you go for a different distro, or you create multiple recipes per possible configuration and add the appropriate configuration in your IMAGE_INSTALL15:57
qschulzI think that would work only if your package recipe is a top-level recipe for you image recipe (meaning, explicitly added to IMAGE_INSTALL for example, not in ANY DEPENDS or RDEPENDS)15:58
NiniC0c0qschulz always the best, Thx for support !16:00
escalionI personally use a custom python script on top of bitbake that pulls multiple configurations from directories and stitches them together based on an images declaration file16:00
escalionMy system is to build application sets onto different targets (and cross-targets) - it looks like this:
*** thekappe <thekappe!c65a42b1@> has joined #yocto16:03
thekappehello guys, it's advisable to use squasfs and uinonfs nowadays ?16:04
escalionsquashfs is nice if you only need a read only filesystem because it can be mounted directly and has a high compression rate16:04
thekappeit seems to be an itneresting solution but at the same not so popular16:05
*** andycooper <andycooper!uid246432@gateway/web/> has joined #yocto16:05
*** w00die <w00die!~w00die@> has quit IRC16:05
thekappeescalion, I want to create an image with a rootfs and a partition that can be rw by the user16:05
escalionthekappe: then a squashfs system would work - but only use it if space is a premium16:06
escalionOtherwise go with straight ext4 in ro mode and a overlay partition with rw16:06
*** w00die <w00die!~w00die@> has joined #yocto16:06
thekappeescalion, in my case the buns is that the user won't be able to mess uo with the shipped rfs16:07
escalionjust mount the ext4 read-only16:07
escalionand overlay on /home16:08
thekappesound interesting too16:08
escalionIt'll be much easier that way.16:08
escalionIf you want updates etc too, then rauc is pretty nice (and ships bundles with a squashfs)16:09
thekapperauc ?16:09
escalionrauc, meta-rauc16:10
thekappei'll search for it16:10
escalionBasically there are advantages and disadvantages of going the squashfs/unionfs route - it all depends really on the use case16:12
thekappe@escalion thanks16:14
thekappeim just evaluating all the possibilities16:14
escalionJust remember that squashfs saves space at the tradeoff of a small drop in performance16:14
thekappebasically I'll need something robust and updatable16:14
thekappehaving a ro fs with overlay capabilities sounds interesting16:15
escalionIt's exactly what I've just done for a project. Using rauc for A/B rootfs updates too16:15
thekappeI've searched a little bit and I got to squashfs and unionfs16:15
thekappethat would be probably my case16:16
thekappeI just call them rootfsA and rootfsB16:16
*** rpcme <rpcme!> has joined #yocto16:17
escalionexactly. go take a look at rauc I think it could help with what you want16:18
qschulzescalion: that ain't built into bitbake/Yocto though, but I guess it is a valid scenario too. To each their own :)16:19
escalionqschulz: it isn't but it has been certainly helpful for me to leverage yocto & bitbake to my use case16:20
*** yannholo <yannholo!> has quit IRC16:23
escalionAnyway, I'm off - thanks for the fish! o716:23
*** escalion <escalion!> has quit IRC16:24
*** rpcme <rpcme!> has quit IRC16:28
thekappeqschulz, what do you think about rauc ?16:30
*** lucaceresoli <lucaceresoli!~lucaceres@> has quit IRC16:31
*** ecdhe <ecdhe!~ecdhe@unaffiliated/ecdhe> has quit IRC16:43
*** caiortp <caiortp!> has joined #yocto16:48
*** dreyna <dreyna!~dreyna@2601:646:4201:e280:ac49:3996:c60c:7067> has joined #yocto16:49
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC16:51
*** vineela <vineela!~vtummala@> has joined #yocto16:55
*** ecdhe <ecdhe!~ecdhe@unaffiliated/ecdhe> has joined #yocto17:04
*** kpo <kpo!> has quit IRC17:07
*** roussinm <roussinm!> has joined #yocto17:23
*** snikulov <snikulov!> has joined #yocto17:37
*** nvmd <nvmd!~nvmd@> has joined #yocto17:47
*** vineela <vineela!~vtummala@> has quit IRC18:09
*** kpo_ <kpo_!> has joined #yocto18:12
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:ed2d:51fd:a423:7329> has quit IRC18:27
vdlDid you ever package a multiconfig image recipe?18:32
vdlI'd like to pre install a container image in my rootfs18:33
vdlI can maybe add a task which depends on the multiconfig image to deploy its rootfs into the main image rootfs, but maybe a simple multiconfig image -> package recipe translation would be simpler? this way you could even use SYSTEMD_SERVICE to enable the machine at boot.18:34
*** ayoung <ayoung!~ayoung@2601:19c:4680:ee30::2f1d> has joined #yocto18:37
smurrayvdl: I've not tested it recently, but I did a couple of presentations on doing that, sample at:
vdlsmurray: thank you. "container" image types require packagegroup-core-boot?18:47
smurrayvdl: no18:48
vdlsmurray: you added it in build-container.bb18:49
smurrayvdl: I'd have to dig a bit to see why I did that, it's not a hard requiremnt18:50
vdlsmurray: btw for the volatile issue (machinectl start foo failed for me as well because /var/log/ was non existent), setting VOLATILE_LOG_DIR = "no" in my (container) distro conf fixes it. Not sure if that can be applied in the container image recipe itself.18:50
*** vineela <vineela!~vtummala@> has joined #yocto18:50
smurrayvdl: as I said, I've not tried it since last Feb, it's possible stuff has changed in gatesgarth and later18:51
vdlsmurray: ok. I'm currently using a dedicated machine configuration for the containers, because I use linux/dummy for them, but it does not make a lot of sense since a container must be build for the same architecture as the host... Do you know if PREFERRED_PROVIDER_virtual/kernel = "linux/dummy" can be set in the (container) image recipe?18:55
vdlotherwise a container distro configuration might be enough I suppose.18:55
smurrayyou can't set it in the image recipe.  I've done both setting it in a tweaked machine for the container or in the multiconfig .conf18:57
smurraycontainer distro also works18:58
vdlmaybe the multiconfig is better to centralize these common machine/distro tweaks while still sharing the same machine and distro definitions.19:00
vdlsmurray: long term for this would be having dynamic packages (similar to kernel module packages) for images of "container" fstype, so one could IMAGE_INSTALL += "container-<image pn>" and eventually bbappend the package to override the install path or install/enable an .nspawn file.19:05
*** dev1990 <dev1990!> has joined #yocto19:16
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC19:19
*** kpo_ <kpo_!> has quit IRC19:37
*** kiwi_29 <kiwi_29!> has joined #yocto19:39
*** xtron <xtron!~sahm@> has joined #yocto19:40
*** RobertBerger <RobertBerger!> has quit IRC19:55
*** kpo_ <kpo_!> has joined #yocto20:00
*** kiwi_29 <kiwi_29!> has quit IRC20:06
*** kiwi_29 <kiwi_29!> has joined #yocto20:07
*** kiwi_29 <kiwi_29!> has quit IRC20:23
*** kiwi_29 <kiwi_29!> has joined #yocto20:28
*** xtopher <xtopher!uid495823@gateway/web/> has joined #yocto20:32
ecdheI am bringing a kernel 2.6 into yocto (the exact source tree that a vendor provided)20:33
ecdheOstensibly, the code is 2.6.35, and I'd like to diff it with source from to see how much mucking around the vendor did.  But shows 9 revisions for that, from to
*** xtopher <xtopher!uid495823@gateway/web/> has left #yocto20:35
ecdheIf I download all nine of them, unpack them, and commit them to a repo in series, is there a quick way to find out which commit has the least edit-distance to the vendor-provided source tree I have?20:35
*** Spooster <Spooster!> has quit IRC20:36
ecdheFor only nine commits this is something I could do manually, but I'm wondering if there's any tooling that would do this kind of task more automatically before I write my own20:37
*** Wouter0100 <Wouter0100!> has quit IRC20:41
ecdheThe script I would write would commit the vendor source tree into another branch, seperate from the successive commits.  Then I'd call 'git diff vendor_branch kernelorg_commit_hash' for each commit hash, then save the diff into a text file with the name of the commit.  The smallest text file (by lines?) probably means the fewest differences and should indicate whether the vendor started20:41
ecdhewith or .35.7.  Then I could rebase the improvements in the later revisions onto the vendor branch.20:41
*** kiwi_29 <kiwi_29!> has quit IRC20:42
khemyates: gcc builds are a bit special, where it shared same source tree with many gcc related recipes, so sources are under work-shared20:47
khemowned by gcc-source recipe usually20:47
*** Scorpi <Scorpi!> has left #yocto20:50
*** yates <yates!> has quit IRC20:56
*** oberstet <oberstet!~oberstet@> has quit IRC20:56
*** dev1990 <dev1990!> has quit IRC21:19
*** dev1990 <dev1990!> has joined #yocto21:27
*** vineela <vineela!~vtummala@> has quit IRC21:34
*** xtron <xtron!~sahm@> has quit IRC21:38
*** xtron <xtron!~sahm@> has joined #yocto21:44
*** kiwi_29 <kiwi_29!> has joined #yocto21:44
*** kiwi_29 <kiwi_29!> has quit IRC21:47
*** Spooster <Spooster!> has joined #yocto21:48
*** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has quit IRC21:58
*** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has joined #yocto21:59
*** xtron <xtron!~sahm@> has quit IRC22:10
*** nvmd <nvmd!~nvmd@> has quit IRC22:17
*** snikulov <snikulov!> has quit IRC22:17
*** sakoman <sakoman!~steve@> has quit IRC22:18
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC22:20
*** sakoman <sakoman!~steve@> has joined #yocto22:23
*** vineela <vineela!~vtummala@> has joined #yocto22:38
*** savolla <savolla!~savolla@> has quit IRC22:39
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC22:47
*** ayoung <ayoung!~ayoung@2601:19c:4680:ee30::2f1d> has quit IRC23:03
jonesv[m]I'm struggling a bit with my rpi4 and wifi. Does somebody here know which kernel module needs to be started for that? I tried `modprobe b43`, but no wifi interface appears in `ip l` after that...23:04
*** thekappe <thekappe!c65a42b1@> has quit IRC23:08
*** Spooster <Spooster!> has quit IRC23:10
*** Spooster <Spooster!> has joined #yocto23:10
*** Spooster <Spooster!> has quit IRC23:15
*** vineela <vineela!~vtummala@> has quit IRC23:19
*** angolini <angolini!uid62003@gateway/web/> has quit IRC23:23
*** leon-anavi <leon-anavi!~Leon@> has quit IRC23:25
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC23:32
*** kiwi_29 <kiwi_29!> has joined #yocto23:48
*** theodiem <theodiem!> has joined #yocto23:53
*** kiwi_29 <kiwi_29!> has quit IRC23:55
*** tangofoxtrot <tangofoxtrot!~jon@unaffiliated/tangofoxtrot> has quit IRC23:56

Generated by 2.17.2 by Marius Gedminas - find it at!