All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:49:44 -0800	[thread overview]
Message-ID: <18350.1739468984755588893@lists.yoctoproject.org> (raw)
In-Reply-To: <13254.1739463914284453219@lists.yoctoproject.org>

[-- Attachment #1: Type: text/plain, Size: 808 bytes --]

So, I added "dhcpcd" to this line in my local.conf file:

> 
> IMAGE_INSTALL:append = " linux-firmware-bcm43430 bluez5 i2c-tools
> wpa-supplicant dhcpcd"
> 

and voila, I have my wpa_supplicant v2.9 installed.... so any ideas why this worked?

And with that, I ran the wpa_supplicant and I now have wifi working on a raspberry Pi Zero 2 W running a Yocto 64-bit image.

The negative is that wpa-supplicant 2.9 doesn't take a passphrase that's encoded so I have a clear text PSK in the file. That will need to be fixed. I guess the patch that causes the issues with 2.11 needs to be identified and removed. I'm sure that will be tedious.

Any tests or information about my build that is requested will certainly be done if you think it will be constructive and helpful to the cause.

Cheers!!

[-- Attachment #2: Type: text/html, Size: 965 bytes --]

  reply	other threads:[~2025-02-13 17:49 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 [this message]
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=18350.1739468984755588893@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.