From: "John" <jdowd@slashdevslashnull.org>
To: "Alexander Kanavin" <alex.kanavin@gmail.com>,
yocto@lists.yoctoproject.org
Subject: Re: [yocto] PREFERRED_VERSION not being populated onto the rootfs image
Date: Thu, 13 Feb 2025 06:59:19 -0800 [thread overview]
Message-ID: <873.1739458759066142451@lists.yoctoproject.org> (raw)
In-Reply-To: <CANNYZj-oJA0qnr9+Djg94gN469cJJ18ym_nf2Bu3wph+_3RNig@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1193 bytes --]
Alexander,
Thanks for your reply.
I've attached my new configure file that lives in: poky/meta-raspberrypi/conf/machine
Mea Culpa: I created this configure file and am using the MACHINE ??= "raspberrypi0-64-wf.conf" in my local.conf file.
Since the raspberrypi Zero support does not work out of the box. There is an issue in that it has to build as a 64 bit image or Raspberry Pi's boot loader won't load it. And then, the kernel modules are missing... and then the WIFI isn't installed completely and doesn't work anyways... etc... I created my own machine configuration file.
My current state has the image booting, I have a serial connection and through it I can try to bring up wifi by hand but the wpa-supplicant won't connect. My searches have found some information that it is a recent patch that has a side effect of not letting wpa-supplicant work with some raspberry Pi's. I gather an older version (2.9) does work so that's why I'm doing this.
I have no idea where the log file you referred to is or how to make bitbake generate it.
I did do a:
>
> $ bitbake -c cleanall wpa-supplicant
>
I can see that the correct version is referenced.
Cheers!!
[-- Attachment #1.2: Type: text/html, Size: 1637 bytes --]
[-- Attachment #2: raspberrypi0-64-wf.conf --]
[-- Type: application/octet-stream, Size: 503 bytes --]
#@TYPE: Machine
#@NAME: RaspberryPi0 2 Wifi Development Board
#@DESCRIPTION: Machine configuration for the RaspberryPi0 2 Wifi in 64 bits mode
MACHINEOVERRIDES =. "raspberrypi3-64:"
include conf/machine/raspberrypi3-64.conf
PREFERRED_VERSION_wpa-supplicant = "2.9"
MACHINE_EXTRA_RRECOMMENDS += "\
linux-firmware-rpidistro-bcm43436 \
linux-firmware-rpidistro-bcm43436s \
bluez-firmware-rpidistro-bcm43430b0-hcd \
"
RPI_KERNEL_DEVICETREE = " \
broadcom/bcm2710-rpi-zero-2.dtb \
"
next prev parent reply other threads:[~2025-02-13 14:59 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 [this message]
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
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=873.1739458759066142451@lists.yoctoproject.org \
--to=jdowd@slashdevslashnull.org \
--cc=alex.kanavin@gmail.com \
--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.