Wpa_supplicant デーモン

Technical Support
, , ,
1

imx6ull の無線なしを使用しています。
systemctl is-enabled wpa_supplicantがdisabledにもかかわらず、
軌道時にデーモンがスタートする。maskしないとダメか？

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I’d be glad to help with your wpa_supplicant daemon issue! To provide the most accurate guidance, could you let me know which OS and version you are using?

For example, are you using:

  • Torizon OS (and which version?)
  • Yocto BSP (and which version?)

You can get this information by running the tdx-info command on your device. More details about this command can be found at: https://developer.toradex.com/software/development-resources/tdx-info/

Background Information

The Colibri iMX6ULL comes in several variants, including versions without Wi-Fi(1). If you’re using a non-Wi-Fi version but wpa_supplicant is still starting, this could be due to:

  1. Default system configuration - The service might be enabled by other mechanisms
  2. Dependency chains - Other services might be triggering wpa_supplicant startup
  3. Socket activation - systemd might be starting the service on-demand

Potential Solutions

While I wait for your OS version details, here are some general approaches:

Option 1: Masking the Service

sudo systemctl mask wpa_supplicant

Option 2: Check for Socket Units

systemctl list-units --type=socket | grep wpa

Option 3: Review Dependencies

systemctl list-dependencies --reverse wpa_supplicant

Once you provide your OS version information, I can give you more specific guidance tailored to your exact setup.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.