starting wpa_supplicant: failed (brcmfmac)

[Mapamann]

Preliminary Docs

I confirm that I have read the CONTRIBUTING guide before opening this issue.

I confirm that I have read the FAQ before opening this issue.

motionEye Version | 0.41rc1 Motion Version | 4.2.2 OS Version | motionEyeOS dev20190820

I am running motionEyeOS version: (insert your version here, e.g. 20180314).

Raspberry PI 3B+ I am using the following board/model: (insert your board model here, e.g. Raspberry PI 3B+).

MMAL Camera I am using the following type of camera: (choose from V4L2, MMAL, Network Camera, Fast Network Camera and Simple MJPEG Camera).

My camera model is: (insert your camera model, e.g. Logitech C290).

Network Connection

My motionEyeOS unit is connected to the network via: (choose your network connection, e.g. WiFi, Ethernet).

Peripherals

I am using the following peripherals that I consider relevant to this issue:

• (e.g. USB WiFi adapter)
• (e.g. External Hard Disk)

Log Files

I consider the following log files relevant to this issue:

• (attach e.g. motioneye.log)
• (attach e.g. boot.log)

Hello,

I tried everything what came to my mind to try to get my PI 3+ to connect to my wireless network.

With the latest stable release 20190427 it connects to my wifi (tried 5Ghz and 2.4Ghz) But with the last two pre-releases and the same wpa_supplicant.conf that works on 20190427 i get the starting wpa_supplicant: failed (brcmfmac) message on startup.

When i connect the cable and log in to the web interface i even can see under the wireless settings that it filled the SSID and key out of my wpa_supplicant.conf but it will not connect to the Wifi on startup.

I even set up a Raspean and did copy the wpa_supplicant.conf from there but same result.

Can anybody help me how to fix this?

[Mapamann]

Nobody any idea?

[jarakangas]

Same problem here. Ethernet is OK. But with wifi I also get "failed (brcfmac)" error.

[barneycoles]

Same problem too. Ethernet is OK. But with wifi I also get "failed (brcfmac)" error.

[CoolHandMike]

I had the same issue with the same Pi. This is how I fixed it:

1. Load fresh image (20190911) onto the micro SD card with Balena Etcher.
2. Open notepad++. Set to UNIX mode: Edit-->EOL Conversion-->UNIX (LF)
3. This is what's in my wpa_supplicant file (yes, keep the quotation marks):

country=us
update_config=1
ctrl_interface=/var/run/wpa_supplicant

network={
scan_ssid=1
key_mgmt=WPA-PSK
psk= "mywifipassword"
ssid= "mywifissid"
}

I had to confirm my scan_ssid channel by looking at my wifi config on my router. It's set to channel 1. I'm also using WPA2, so key_mgmt gets set to WPA-PSK.

4. In the notepad++ dropdown for "Save as type:" scroll up one and select All. Save it as wpa_supplicant.conf. I saved it to my desktop so I could copy/paste from there.
5. Open up your newly flashed micro SD card. Ignore Windows telling you it needs to be formatted. You should still be able to access the boot partition and see some files there.
6. Copy your wpa_supplicant file from your desktop and paste it into the SD card boot drive.
7. Use the taskbar to safely eject the SD card.
8. Install the card in your Pi and see if it works. It should say Starting wpa_supplicant: done if you were successful.

Unfortunately it may take some trial and error to get the settings just right. Each time you change something in the conf file, it's better to perform the whole procedure as I have outlined from start to finish since I think the wpa_supplicant file is only accessed during first boot, then becomes read only.

Good luck!

[reinst]

If the above is still not working try this: My background, I used ethernet for the original setup and from other posts I read I needed to setup wifi pre-boot. I got wifi working anyways.

After the wifi was not working I got an error: starting wpa_supplicant: failed (brcmfmac) <-- this will be different based on your wifi driver.

1. Pull the micro sd out and mount back on your regular computer:

2. Open 2nd partition (should be the remaining size of your micro sd card)

2a. As admin - open /etc/wpa_supplicant.conf: edit

country=US
update_config=1
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
network={
    scan_ssid=1
    ssid="wifi_ssd_name" <- enter yours 
    psk="password" <- enter your pass
}

2b. Save

As you can see I did not save any wpa_supplicant.conf file in my main partition OR did I save one in my /boot (not shown)

[Roozeppe]

Thanks, @reinst. This works for me.

[danschimpf]

I tried all of the solutions mentioned above on my mac, with no success.

boot up would see the file, then indicate "failed (brcfmac)" error. (I was changing the extension to .conf, otherwise during boot up would not indicate "Starting wpa_supplicant: " and would try to boot a wired connection)

Then I tried downloading, editing and saving the file on my PC (just my specific info added to the template no additional verbiage) ..and it worked 1st time.

perhaps something with the formate of a mac txt file was unreadable.

on the PC, I saved the file as an ANSI file

not saying this is the solution, just adding what appears to have worked for me

[LEONIDAS-0117]

I have being trying to connect to a 5GHz network that only admits WPA2 as Encryption method and CCMP as Cipher for the past few days. This is the wpa_supplicant.conf that worked for me:

country=US
update_config=1
ctrl_interface=/var/run/wpa_supplicant
        
network={
    scan_ssid=1
    ssid="network-name"
    psk="password"
    proto=RSN
    key_mgmt=WPA-PSK
    pairwise=CCMP
    group=CCMP
    auth_alg=OPEN
}

If not sure what Cipher is being used you can edit:

pairwise=CCMP
group=CCMP

to

pairwise=CCMP TKIP
group=CCMP TKIP

[Normanras]

Tried setting up motioneyeOS a few days and failed and I was just able to connect it to a monitor and lo, the same issue. Anyone who solved with the above suggestions - has anyone used a mac? My PC is currently unavailable.

I tried using Atom to convert the line-endings to Unix (LF), but it still didn't work.

I'm also wondering why any other distro for RaspberryPi I've used, has worked without an issue. I use Text Edit, make the file with proper code, save it as wpa_supplicant.conf, add a second empty file called ssh and I'm in on first boot. Strange that motioneye specifically is the issue here!

[starbasessd]

Can you post your wpa_supplicant.conf file here? What Pi board are you using? Which version of motionEyeOS are you using?

On Mon, Mar 15, 2021 at 6:16 PM Normanras @.***> wrote:

Tried setting up motioneyeOS a few days and failed and I was just able to connect it to a monitor and lo, the same issue. Anyone who solved with the above suggestions - has anyone used a mac? My PC is currently unavailable.

I tried using Atom to convert the line-endings to Unix (LF), but it still didn't work.

I'm also wondering why any other distro for RaspberryPi I've used, has worked without an issue. I use Text Edit, make the file with proper code, save it as wpa_supplicant.conf, add a second empty file called ssh and I'm in on first boot. Strange that motioneye specifically is the issue here!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2060#issuecomment-799791072, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHP6AXZIYJ5SL5AOHOTTD2BLNANCNFSM4IOELGAA .

-- Thanks

Kevin Shumaker

Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel

N38° 19' 56.52" W85° 45' 8.56"

Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?

[RainNB08]

none of the solution above works for my raspberry pi 0 with the latest version of motion eye

[starbasessd]

Which PiZero do you have? On the back of the board, under the GPIO pins, it has 2 lines of text, Please post them here.

[RainNB08]

PiZero W

[starbasessd]

Which PiZero do you have? On the back of the board, under the GPIO pins, it has 2 lines of text, Please post them here.

[RainNB08]

[starbasessd]

This was a link back to this issue...

[RainNB08]

Is there any thing i can do now?

[starbasessd]

Which PiZero do you have? On the back of the board, under the GPIO pins, it has 2 lines of text, Please post them here.

[RainNB08]

[starbasessd]

Use the dev20201026 image for PiZero DO NOT USE Raspi-Imager, use Etcher or Win32DiskImager to create the SDCard. Raspi-Imager will corrupt settings within motionEyeOS Use a wpa_supplicant.conf with the format:

---

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 country=US

network={ ssid="SSID" psk="password" }

---

Substitute your SSID and password for your network, and your country...

[RainNB08]

it still failed same error failed(brcmfmac)

[starbasessd]

Can you post the text of your wpa_supplicant.conf file here? How did you create it and how do you copy it to the /boot partition before first boot?

[RainNB08]

i copied the code you have sent directly into the wpa_supplicant.conf file, and fill in my own ssid and passcode. I just opened a new file my D drive along with overlay and other files

[starbasessd]

Do you have "View Extensions" turned on in File Explorer? If not, it may be creating wpa_supplicant.conf.txt instead of wpaq_supplicant.conf You should not be using Notepad to create the file. It is better to use Notepad++ or other Linux friendly text file editor.

[RainNB08]

yes i have, i am sure that the wpa_supplicant.conf is correctly named and I am using the notepad++

[starbasessd]

Do you have a 2nd PiZeroW to test with, or a 2nd SDCard? I've just tested 2 PiZeroWs and 3 SDCards, and all work interchangeably.

[RainNB08]

i have tried two sd card, but on the same PiZeroW, is there anyother cause that might lead to this failure?

[starbasessd]

Other than a defective PiZeroW, the only other thing(s) I can think of would be a wifi password or ssid with a disallowed character, or a wifi with a 5GHz name that is the same as a 2.4GHz name (11AC same as 11G or 11N) and it's trying to connect to the 5GHz access point instead of the 2.4GHz access point...

[RainNB08]

I am positive that my PiZero W is not malfunctioning because the raspberry pi os run perfectly beside lagging, but hwo should i deal with the wifi situation

[RainNB08]

also, somehow my /boot does not have loader.bin in it