($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: yocto@lists.yoctoproject.org, worik.stanton@tirotech.co.nz
Subject: Re: [yocto] Opkg cannot find anything to satisfy 'kernel-module-iwlmvm'
Date: Mon, 13 May 2024 09:13:52 +0200	[thread overview]
Message-ID: <CANNYZj8zTegW8tnHoKrkDDKKaQPmvY36FVQpGxzsbvjCJisKeQ@mail.gmail.com> (raw)
In-Reply-To: <CANuMBWHvmSZ1xuEuSW=aUy3ig93ckw7o+Zb6Wd_4hDm=_tscnQ@mail.gmail.com>

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


Alex

On Mon, 13 May 2024 at 02:02, Worik Stanton via lists.yoctoproject.org
<worik.stanton=tirotech.co.nz@lists.yoctoproject.org> wrote:
>
> 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/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


  reply	other threads:[~2024-05-13  7:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13  0:02 Opkg cannot find anything to satisfy 'kernel-module-iwlmvm' Worik Stanton
2024-05-13  7:13 ` Alexander Kanavin [this message]
2024-05-14  2:51   ` [yocto] " Worik Stanton
     [not found]   ` <17CF3B3BCDD18A8E.29130@lists.yoctoproject.org>
2024-05-15 21:15     ` Worik Stanton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANNYZj8zTegW8tnHoKrkDDKKaQPmvY36FVQpGxzsbvjCJisKeQ@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=worik.stanton@tirotech.co.nz \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).