From: "John" <jdowd@slashdevslashnull.org>
To: "John" <jdowd@slashdevslashnull.org>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] PREFERRED_VERSION not being populated onto the rootfs image
Date: Thu, 13 Feb 2025 14:21:23 -0800 [thread overview]
Message-ID: <26374.1739485283805608205@lists.yoctoproject.org> (raw)
In-Reply-To: <18350.1739468984755588893@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
And now I have a working raspberrypi Zero 2 W with wifi (comes up automatically) and probably a working Bluetooth (not of importance to me right now but there appears to be an interface for it).
With the addition of the dhcpcd s/w shown above I had a working wpa-supplicant as it replaced the 2.11 version with the 2.9 version. My next problem was to get the wifi to start automatically. This was done by creating my own "interfaces" file under "init-updown" in the recipes-connectivity right here:
>
> ./recipes-core/init-ifupdown/init-ifupdown-1.0/raspberrypi0-64-wf/interfaces
>
>
This file will be installed to /etc/network.
Somewhere I ran across this setup in which you can just override a generic file by placing the same file in a sub-directory prefixed with the machine name you are using. This will prioritise this version of the file. In that file I removed some of the references to "eth0" and "eth1" and made sure "wlan0" was set to auto.
So I consider my issue all closed and then some.
Cheers!!
[-- Attachment #2: Type: text/html, Size: 1229 bytes --]
next prev parent reply other threads:[~2025-02-13 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 19:57 PREFERRED_VERSION not being populated onto the rootfs image John
2025-02-13 8:57 ` [yocto] " Alexander Kanavin
2025-02-13 14:59 ` John
2025-02-13 15:09 ` John
2025-02-13 15:11 ` Alexander Kanavin
2025-02-13 16:25 ` John
2025-02-13 17:49 ` John
2025-02-13 22:21 ` John [this message]
2025-02-19 17:15 ` John
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=26374.1739485283805608205@lists.yoctoproject.org \
--to=jdowd@slashdevslashnull.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.