Re: [yocto] Opkg cannot find anything to satisfy 'kernel-module-iwlmvm'

[Worik Stanton]

If anybody else has the problem of their kernel config being rewritten by
the yocto build process when configuring a iwlwifi chip I have the answer.
Not the reason, just the answer.

On Tue, 14 May 2024 at 14:51, Worik Stanton via lists.yoctoproject.org
 wrote:

>
>
> On Mon, 13 May 2024 at 19:14, Alexander Kanavin 
> wrote:
>
>> You need to look into build logs and build directory for the kernel
>> recipe to see what modules are being built and packaged.
>>
>
> Rightio.  (I found that the failure is logged in the "do_rootfs" recipe,
> but concentrating on the kernel recipe):
>
> I found a problem, straight away:  The kernel recipe includes in its
> SRC_URI a file that (looks like) it sets kernel configuration to load the
> iwlwifi modules.
> However when I build it and boot it and examine /proc/config.gz none of
> the configuration from the kernel recipe are there
>

If anybody cares, the problem with the kernel configuration being rewritten
was solved by adding "CONFIG_WLAN_VENDOR_INTEL=y" to the config.

On the face of it this makes no sense because this is the documentation
from https://www.kernelconfig.io/config_wlan_vendor_intel

---
If you have a wireless card belonging to this class, say Y.

Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all the
questions about these cards. If you say Y, you will be asked for
your specific card in the following questions.
---

Now I am moving on to getting the firmware installed by Yocto.  I find if I
add the firmware by hand the wireless chip is working well, which

ATM it looks as if the opkg error I started with was a red herring.  I
still have no explanation for it.

I am disturbed that the kernel config is getting rewritten, and the answer
is a "magic incantation".   I am sure there are sensible reasons, and it is
not magic.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63104): https://lists.yoctoproject.org/g/yocto/message/63104
Mute This Topic: https://lists.yoctoproject.org/mt/106063799/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Opkg cannot find anything to satisfy 'kernel-module-iwlmvm'

[Worik Stanton]

On Mon, 13 May 2024 at 19:14, Alexander Kanavin 
wrote:

> You need to look into build logs and build directory for the kernel
> recipe to see what modules are being built and packaged.
>

Rightio.  (I found that the failure is logged in the "do_rootfs" recipe,
but concentrating on the kernel recipe):

I found a problem, straight away:  The kernel recipe includes in its
SRC_URI a file that (looks like) it sets kernel configuration to load the
iwlwifi modules.
However when I build it and boot it and examine /proc/config.gz none of the
configuration from the kernel recipe are there

Grepping around for the configuration options I found this file in my build
section:
build/tmp/work-shared/apalis-imx8/kernel-source/.kernel-meta/cfg/merge_config_build.log
It is not updated on each build, but has been updated today, so I am unsure
on when and how it was created.

It says (in part)


#
# configuration written to .config
#
make[1]: Leaving directory
'/home/yocto/build/tmp/work/apalis_imx8-tdx-linux/linux-toradex/5.15.77+gitAUTOINC+458ba358fc-r0/build'
Value requested for CONFIG_CFG80211 not in final .config
Requested value:  CONFIG_CFG80211=y
Actual value: CONFIG_CFG80211=m

Value requested for CONFIG_MAC80211 not in final .config
Requested value:  CONFIG_MAC80211=y
Actual value: CONFIG_MAC80211=m

Value requested for CONFIG_IWLWIFI not in final .config
Requested value:  CONFIG_IWLWIFI=m
Actual value:

Value requested for CONFIG_IWLWIFI_LEDS not in final .config
Requested value:  CONFIG_IWLWIFI_LEDS=y
Actual value:

Value requested for CONFIG_IWLMVM not in final .config
Requested value:  CONFIG_IWLMVM=m
Actual value:



The kernel recipe from:
meta-tirotech/recipes-kernel/linux/linux-toradex_%.bbappend

FILESEXTRAPATHS:prepend := "${THISDIR}/files:"

SRC_URI += "\
file://tirotech.dts \
file://intel-wireless.cfg \
file://0001-Add-missing-M40-UART-clock-to-resource-table.patch \
"
KERNEL_DEVICETREE += "freescale/tirotech.dtb"

do_patch:append () {
cp -f ${WORKDIR}/tirotech.dts
${S}/arch/arm64/boot/dts/freescale/tirotech.dts
echo 'dtb-$(CONFIG_ARCH_MXC) += tirotech.dtb' >> \
${S}/arch/arm64/boot/dts/freescale/Makefile
}


The file  intel-wireless.cfg:


CONFIG_CFG80211=y
CONFIG_MAC80211=y
CONFIG_IWLWIFI=m
CONFIG_IWLWIFI_LEDS=y
CONFIG_IWLMVM=m


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63082): https://lists.yoctoproject.org/g/yocto/message/63082
Mute This Topic: https://lists.yoctoproject.org/mt/106063799/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Opkg cannot find anything to satisfy 'kernel-module-iwlmvm'

[Worik Stanton]

Friends

Where in a yocto build can I find the definition of a package for opkg?

I am building an image for a Toradex NXP.
I have to replace the WiFi chip with a iwlwifi Intel chip
When it is building my core image recipe it fails with the message:

* opkg_prepare_url_for_install: Couldn't find anything to satisfy
'kernel-module-iwlmvm'

I have a working build for an Intel Nuc that uses this chip and builds with
no problems.

In both builds the IMAGE_INSTALL has kernel-module-iwlmvm and
kernel-module-iwlwifi added

I looked into the opkg package list and there is no "kernel-module-iw*",
there is "kmod-iwlwifi" so I switched to that, but the error I got was:

"ERROR: Nothing RPROVIDES 'kmod-iwlwifi"

I searched all of the files, (on both systems) I have and I cannot find
where "kernel-module-iwlmvm" is defined as a package for opkg.  The fact
that changing "kernel-module-iwlwifi" to "kmod-iwlwifi" indicates it is
defined somewhere.

IMAGE_INSTALL += " \
sentinel \
gdb \
strace \
packagegroup-boot \
packagegroup-basic \
packagegroup-base-tdx-cli \
packagegroup-machine-tdx-cli \
packagegroup-wifi-tdx-cli \
packagegroup-wifi-fw-tdx-cli \
packagegroup-fsl-gpu-libs \
udev-extraconf \
storage-mount \
root-key \
terminal-server \
ubx \
lbtool \
iw \
kernel-module-iwlwifi \


kernel-module-iwlmvm \


"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63074): https://lists.yoctoproject.org/g/yocto/message/63074
Mute This Topic: https://lists.yoctoproject.org/mt/106063799/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Warning about "no-recipes"

[Worik Stanton]

Thank you for everybodies' help

Following the suggestions I made the (in hindsight) obvious discovery that
the warning is generated in a recipe from somewhere else, namely
"meta-toradex-nxp".  The person who built this system has pinned
meta-toradex-nxp to a particular commit from 2021.  I do not know what they
were thinking, I am fairly confident they knew what they were doing.

I will leave it there as this is a warning.  While it is an otherwise clean
build, and I crave clean builds, there are actually problems that are real
roadblocks that I need to fix (another subject)

Next time I hope I can provide the necessary information faster.  It is
difficult to know what to provide as I am diving into the middle of two
large projects that use different styles.

Once again thank you for your help.

Worik




> I expect it is that latter directory my warning is originating from.
>
> The warning is:
> WARNING: No recipes in default available for:
>
> /home/yocto/thisbuild-yocto/layers/openembedded-core/../meta-thisbuild-nxp/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.20.0.imx.bbappend
>
> What this means is bitbake is looking for recipe file called
> gstreamer1.0-plugins-base_1.20.0.imx.bb and can't find it anywhere in
> configured layers. This can happen for multiple reasons:
>
> 1. That recipe file used to be available, but someone updated the
> layer containing it to a different revision where the file was either
> removed or updated to a different version (which is encoded into the
> filename). You need to find out whether that has happened, and either
> revert to the original revision, or rename the bbappend to match. Try
> using 'find' command with a generous wildcard expression to see what
> would roughly match in the overall tree.
>
>
>
Yes, this:

yocto@toradex-build:~/toradex-yocto$ find . -name
"gstreamer*-plugins-base*.bb"
./layers/openembedded-core/meta/recipes-multimedia/gstreamer/
gstreamer1.0-plugins-base_1.20.5.bb
./layers/meta-freescale/recipes-multimedia/gstreamer/
gstreamer1.0-plugins-base_1.20.3.imx.bb

My naive view is that I need to find where it is requiring
"recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.20.0.imx.bb" and
change that to "recipes-multimedia/gstreamer/
gstreamer1.0-plugins-base_1.20.5.imx.bb"

This is in somebody else's repository, we import it with a recursive git
clone pinned at a particular commit (it is using a git idiom

3. The file is not available in any of the layers. You need to go over
> the list of required layers in documentation for meta-this-build-nxp,
> and find everything you can about layers it depends on, and perhaps
> look at commit history for bbappend as well to find out
> which layer it's meant to be used with.
>
>
"thisbuild-nxp" is "toradex-nxp.

Reading the Readme it depends on:

yocto@toradex-build:~/toradex-yocto$ grep URI
layers/meta-toradex-nxp/README
  URI: git://git.openembedded.org/bitbake
  URI: git://git.openembedded.org/openembedded-core
  URI: git://git.yoctoproject.org/meta-freescale
  URI: https://github.com/Freescale/meta-freescale-3rdparty.git
  URI: git://git.toradex.com/meta-toradex-bsp-common

Is that where I start with "layers it depends on"?

The commit history seems to indicate "gstreamer1.0-plugins-base" is the
layer if is supposed to be used with:

yocto@toradex-build:~/toradex-yocto/layers/meta-toradex-nxp$ git log --
recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.20.0.imx.bbappend
commit bd7f3d8596e984d42afa1c9b30fd635fb02fc040
Author: Max Krummenacher 

Date:   Mon Sep 19 14:20:44 2022 +0200




gstreamer1.0-plugins-base: follow version change



The code the patch removes is still present, keep the patch also

with the new version.



Related-to: ELB-4665

Signed-off-by: Max Krummenacher 



Without a specific look at your setup it's hard to say much more.
>
> Alex
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63069): https://lists.yoctoproject.org/g/yocto/message/63069
Mute This Topic: https://lists.yoctoproject.org/mt/105973256/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Some dead links

[Worik Stanton]

The terms of service that you are supposed to read to sign up for the Wiki
is https://www.yoctoproject.org/about/terms-of-service  and is a 404

>From the page: https://wiki.yoctoproject.org/wiki/Newcomers

"Rudi Streif gave a great talk 
at the Embedded Linux Conference in 2015."

The link to the talk is a youtube page saying "This video isn't available
any more"


Worik

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63068): https://lists.yoctoproject.org/g/yocto/message/63068
Mute This Topic: https://lists.yoctoproject.org/mt/106010777/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Warning about "no-recipes"

[Worik Stanton]

> > The "whomever" has gone away, and I am on my own!
> >
> > Where do I start resolving a dependency like this?
>
> It's hard to help you with the information you have shared so far.
> Maybe you can describe in detail about your
> setup and what release you are using and machines being targeted etc.
>
>
Forgive me I am in the deep end with not much knowledge.  What I need is
pointers to the sorts of files I should be looking in to diagnose this sort
of problem.  I have been through the documentation and I have built a
custom, fresh, Yocto for another board.  But I am feeling very lost among a
huge number of files, which is natural considering my position (a lack of
knowledge trying to maintain a system built by an expert who has abandoned
me)

I am targeting a Toradex processor on a custom board.

What are the pertinent details  about   my setup?

The system (before a build) has two subdirectories:

* layers: Consists of "meta-*" directories, and "openembedded-core" all
git repositories pinned to particular commits
* meta-mybuild: Consisting of "recipies-*" and a "conf" directories

I expect it is that latter directory my warning is originating from.

Worik

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63057): https://lists.yoctoproject.org/g/yocto/message/63057
Mute This Topic: https://lists.yoctoproject.org/mt/105973256/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Warning about "no-recipes"

[Worik Stanton]

>
>
>> fudged unto single repository. AFAICT
>>> gstreamer1.0-plugins-base_1.20.0.imx.bb should be
>>> coming from meta-freescale or meta-imx and if you have a unified
>>> metadata tree then this bb file should be somewhere, if not, that
>>>
>>
>> Which "bb"?   "gstreamer1.0-plugins-base_1.20.0.imx.bb"?
>>
>> I have: layers/openembedded-core/meta/recipes-multimedia/gstreamer/
>> gstreamer1.0-plugins-base_1.20.5.bb
>>
>> The suffix is different. (1.20.5.bb V. 1.20.0.bb)
>>
>> That looks like the problem.  Should I rename this file?
>>
>
> No, that won’t help whoever has put this together for you would be the
> person to help and regenerate it for you including right dependencies
>
>>
>>

The "whomever" has gone away, and I am on my own!

Where do I start resolving a dependency like this?

Worik


> Worik
>>
>>
>> means the project missed adding this layer
>>> to your build system.
>>>
>>> if you dont need this recipe then you can ignore failing on bbappends by
>>> adding
>>>
>>> BB_DANGLINGAPPENDS_WARNONLY = "1" to yout local.conf
>>>
>>> > ```
>>> >
>>> > The file in mentioned  (gstreamer1.0-plugins-base_1.20.0.imx.bbappend)
>>> contains:
>>> >
>>> > ```
>>> > FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
>>> >
>>> > SRC_URI:append = "
>>> file://0001-glupload-don-t-reject-non-RGBA-output-format-in-_dir.patch"
>>> > ```
>>> >
>>> > And the file:
>>> "layers/meta-thisbuild-nxp/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0001-glupload-don-t-reject-non-RGBA-output-format-in-_dir.patch"
>>> exists.
>>> >
>>> > What can I do about this?
>>> >
>>> > Worik
>>> >
>>> >
>>> >
>>>
>>
>> 
>>
>>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63049): https://lists.yoctoproject.org/g/yocto/message/63049
Mute This Topic: https://lists.yoctoproject.org/mt/105973256/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Warning about "no-recipes"

[Worik Stanton]

On Wed, 8 May 2024 at 13:39, Khem Raj  wrote:


> > I am getting a warning as I build a yocto build I inherited.  Forgive me
> I know very little about Yocto
> >
> > ```
> > WARNING: No recipes in default available for:
> >
>  
> /home/yocto/thisbuild-yocto/layers/openembedded-core/../meta-thisbuild-nxp/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.20.0.imx.bbappend
>
> how did you build your project metadata ? it seems some layers are
>

It builds from several directories under "meta-*"  I am unsure how I should
answer that.


> fudged unto single repository. AFAICT
> gstreamer1.0-plugins-base_1.20.0.imx.bb should be
> coming from meta-freescale or meta-imx and if you have a unified
> metadata tree then this bb file should be somewhere, if not, that
>

Which "bb"?   "gstreamer1.0-plugins-base_1.20.0.imx.bb"?

I have: layers/openembedded-core/meta/recipes-multimedia/gstreamer/
gstreamer1.0-plugins-base_1.20.5.bb

The suffix is different. (1.20.5.bb V. 1.20.0.bb)

That looks like the problem.  Should I rename this file?

Worik


means the project missed adding this layer
> to your build system.
>
> if you dont need this recipe then you can ignore failing on bbappends by
> adding
>
> BB_DANGLINGAPPENDS_WARNONLY = "1" to yout local.conf
>
> > ```
> >
> > The file in mentioned  (gstreamer1.0-plugins-base_1.20.0.imx.bbappend)
> contains:
> >
> > ```
> > FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
> >
> > SRC_URI:append = "
> file://0001-glupload-don-t-reject-non-RGBA-output-format-in-_dir.patch"
> > ```
> >
> > And the file:
> "layers/meta-thisbuild-nxp/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0001-glupload-don-t-reject-non-RGBA-output-format-in-_dir.patch"
> exists.
> >
> > What can I do about this?
> >
> > Worik
> >
> > 
> >
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63047): https://lists.yoctoproject.org/g/yocto/message/63047
Mute This Topic: https://lists.yoctoproject.org/mt/105973256/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Warning about "no-recipes"

[Worik Stanton]

I am getting a warning as I build a yocto build I inherited.  Forgive me I
know very little about Yocto

```
WARNING: No recipes in default available for:

/home/yocto/thisbuild-yocto/layers/openembedded-core/../meta-thisbuild-nxp/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.20.0.imx.bbappend
```

The file in mentioned  (gstreamer1.0-plugins-base_1.20.0.imx.bbappend)
contains:

```
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"

SRC_URI:append = "
file://0001-glupload-don-t-reject-non-RGBA-output-format-in-_dir.patch"
```

And the file:
"layers/meta-thisbuild-nxp/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0001-glupload-don-t-reject-non-RGBA-output-format-in-_dir.patch"
exists.

What can I do about this?

Worik

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63045): https://lists.yoctoproject.org/g/yocto/message/63045
Mute This Topic: https://lists.yoctoproject.org/mt/105973256/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Yocto Project Quick Build - MACHINE

[Worik Stanton]

>
>
> Is there a part of the manual I can read that explains what this is?
>
>
The intel-meta README

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62707): https://lists.yoctoproject.org/g/yocto/message/62707
Mute This Topic: https://lists.yoctoproject.org/mt/104799797/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Yocto Project Quick Build - MACHINE

[Worik Stanton]

Thanks for the help.

The system is telling me it succeeded,  I used intel-corei7-64

I have a directory: build/tmp/deploy/images/intel-corei7-64 that has a lot
of artifacts in it, and  I am unsure of how to test it.

The yocto system I was working with created a single image file.  I am
looking at a lot of parts here.

Is there a part of the manual I can read that explains what this is?



On Fri, 8 Mar 2024 at 13:57, Worik Stanton via lists.yoctoproject.org
 wrote:

>
>> Hi,
>> did you add meta-altera here?
>>
>> build/conf/bblayers.conf
>>
>>
> Thank you, no.  It was right there in the documentation: "bitbake-layers
> add-layer ../meta-altera"
>
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62706): https://lists.yoctoproject.org/g/yocto/message/62706
Mute This Topic: https://lists.yoctoproject.org/mt/104799797/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Yocto Project Quick Build - MACHINE

[Worik Stanton]

>
>
> Hi,
> did you add meta-altera here?
>
> build/conf/bblayers.conf
>
>
Thank you, no.  It was right there in the documentation: "bitbake-layers
add-layer ../meta-altera"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62705): https://lists.yoctoproject.org/g/yocto/message/62705
Mute This Topic: https://lists.yoctoproject.org/mt/104799797/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Yocto Project Quick Build - qemu

[Worik Stanton]

>
> > What I see in my terminal is:
> >
> > runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e  ...
> > runqemu - INFO - Continuing with the following parameters:
> > KERNEL: [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage]
> > MACHINE: [qemux86-64]
> > FSTYPE: [ext4]
> > ROOTFS:
> [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4]
> > CONFFILE:
> [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.qemuboot.conf]
> >
> > runqemu - INFO - Using preconfigured tap device tap0
> > runqemu - INFO - If this is not intended, touch
> /tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0.
> > runqemu - INFO - Network configuration: ip=192.168.7.2::192.168.7.1
> :255.255.255.0::eth0:off:8.8.8.8 net.ifnames=0
> > runqemu - INFO - Running
> /home/yocto/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0/recipe-sysroot-native/usr/bin/qemu-system-x86_64
> -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev
> tap,id=net0,ifname=tap0,script=no,downscript=no -object
> rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0
> -drive
> file=/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4,if=virtio,format=raw
> -usb -device usb-tablet -usb -device usb-kbd   -cpu IvyBridge -machine
> q35,i8042=off -smp 4 -m 512 -serial mon:vc -serial null -device virtio-vga
>  -display sdl,show-cursor=on  -kernel
> /home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage -append
> 'root=/dev/vda rw  ip=192.168.7.2::192.168.7.1:255.255.255.0::eth0:off:8.8.8.8
> net.ifnames=0 oprofile.timer=1 tsc=reliable no_timer_check
> rcupdate.rcu_expedited=1 swiotlb=0 '
> >
> > runqemu - INFO - Host uptime: 3820.75
>
> You should be able to ssh to root@192.168.7.2
>
>
I see!  I have built the wrong build?  "sato" is a mobile build, does it
include a SSH server?

Worik

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62703): https://lists.yoctoproject.org/g/yocto/message/62703
Mute This Topic: https://lists.yoctoproject.org/mt/104799142/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Quick Build - MACHINE

[Worik Stanton]

Progressing I am at the stage:

Customizing Your Build for Specific Hardware

I have unpacked the `meta-altera` repository as instructed

I edited my build/conf/local.conf

MACHINE ??= "cyclone5"

I get the error:

MACHINE=cyclone5 is invalid. Please set a valid MACHINE in your local.conf,
environment or other configuration file.

Thrashing around a little I re-ran "source oe-init-build-env" but that did
not help

What have I done wrong?
W

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62702): https://lists.yoctoproject.org/g/yocto/message/62702
Mute This Topic: https://lists.yoctoproject.org/mt/104799797/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Quick Build - qemu

[Worik Stanton]

Friends

I am starting from first principles and following Yocto Project Quick Build.

I am at the step: Simulate Your Image Using QEMU:

I am unfamiliar with qemu.  But it has started up (I watched it spin its
wheels in top) but there is nothing to show for it.

I am running in a Debian Bullseye LXC container as I have had trouble
building Yocto builds in Bookworm.  Was that a bad decision?

I am unsure if I have failed or succeeded!

What I see in my terminal is:

runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e  ...
runqemu - INFO - Continuing with the following parameters:
KERNEL: [/home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage]
MACHINE: [qemux86-64]
FSTYPE: [ext4]
ROOTFS:
[/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4]
CONFFILE:
[/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.qemuboot.conf]

runqemu - INFO - Using preconfigured tap device tap0
runqemu - INFO - If this is not intended, touch
/tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0.
runqemu - INFO - Network configuration:
ip=192.168.7.2::192.168.7.1:255.255.255.0::eth0:off:8.8.8.8
net.ifnames=0
runqemu - INFO - Running
/home/yocto/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0/recipe-sysroot-native/usr/bin/qemu-system-x86_64
-device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev
tap,id=net0,ifname=tap0,script=no,downscript=no -object
rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0
-drive
file=/home/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.rootfs-20240307220730.ext4,if=virtio,format=raw
-usb -device usb-tablet -usb -device usb-kbd   -cpu IvyBridge -machine
q35,i8042=off -smp 4 -m 512 -serial mon:vc -serial null -device virtio-vga
 -display sdl,show-cursor=on  -kernel
/home/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage -append
'root=/dev/vda rw  ip=192.168.7.2::192.168.7.1:255.255.255.0::eth0:off:8.8.8.8
net.ifnames=0 oprofile.timer=1 tsc=reliable no_timer_check
rcupdate.rcu_expedited=1 swiotlb=0 '

runqemu - INFO - Host uptime: 3820.75

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62700): https://lists.yoctoproject.org/g/yocto/message/62700
Mute This Topic: https://lists.yoctoproject.org/mt/104799142/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Introduction and my first query: Resources for learning

[Worik Stanton]

> >
> > I do not feel ready to pester you folks with queries until I have done
> > more reading and have moved along the learning curve.   I am hoping
> > for some meta advice about where I can look for guidance for problems
> > like that.
>
>
> Happy to help too when we can!
> I guess you also found the Yocto and BitBake manuals:
> https://docs.yoctoproject.org/
>
>
Thank you, yes that is very useful.

But not long after my email yesterday I found this:
https://youtu.be/zNLYanJAQ3s

It was very helpful.  Having spent many days bashing at this Yocto project
and wearing out the index of the Yocto book, that screencast made a lot of
sense and straightened out a lot of my misconceptions and clarified a lot I
was wondering about

thank you
Worik

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62689): https://lists.yoctoproject.org/g/yocto/message/62689
Mute This Topic: https://lists.yoctoproject.org/mt/104732863/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Introduction and my first query: Resources for learning

[Worik Stanton]

Kia ora

I am Worik Stanton, from Dunedin New Zealand.  I am new to Yocto, and to
this list, with many decades experience programming computers.

My question is about what are the best resources for learning how to adapt
and maintain a Yocto system  I am responsible for.

I have recently become responsible for a collection of Yocto "builds" (I am
unsure how I should describe them) that I must learn how to maintain,
adapt, and extend.  Adapt and extend to new hardware and to new software
that we are writing.

The author of the system is available only sporadically and is cleary
moving to greener pastures and is unable to offer much help.

I have the "Embedded Linux Systems with the Yocto Project" and it is
helpful.  However the systems I am working with are, I fear, quite
idiosyncratic and highly developed.

The example  of the sort of  problem I have faced and solved  is I needed
"lsblk" in my build.  I found that by adding the name of the Debian package
to a variable IMAGE_INSTALL  "IMAGE_INSTALL += util_linux" essentially,
places "lsblk" in the root file system.

I have no idea why I used the name of a Debian package!

I do not feel ready to pester you folks with queries until I have done more
reading and have moved along the learning curve.   I am hoping for some
meta advice about where I can look for guidance for problems like that.

Worik

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62676): https://lists.yoctoproject.org/g/yocto/message/62676
Mute This Topic: https://lists.yoctoproject.org/mt/104732863/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-