From: Ola Oni <oniola@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Wifi not working - raspberrypi3_defconfig
Date: Mon, 17 Dec 2018 23:12:58 +0000 [thread overview]
Message-ID: <874112de-fdc3-990f-1bac-522d2aeb2a1a@gmail.com> (raw)
In-Reply-To: <20181217222558.1005458c@gmx.net>
On 17/12/2018 21:25, Peter Seiderer wrote:
> Hello Ola,
>
> On Mon, 17 Dec 2018 20:31:43 +0000, Ola Oni <oniola@gmail.com> wrote:
>
>>>
>>> raspberrypi3_defconfig with the following changes works for me:
>>>
>>> +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
>>>
>>> +BR2_PACKAGE_RPI_WIFI_FIRMWARE=y
>>> +BR2_PACKAGE_DHCPCD=y
>>> +BR2_PACKAGE_WPA_SUPPLICANT=y :
>>
>> Hi Peter,
>>
>> I am rebuilt the raspberry pi 3 buildroot image which has now allowed me
>> to see wlan0 when I issue ifconfig but still can't seems to connect to
>> WiFi network.
>>
>> Attached is a file which I have appended my current rpi3_defconfig and
>> other outputs. Many thanks in advance.
>
> - configs/rpi3_defconfig: looks good
> - dmesg: looks good (brcmfmac messages exist)
> - my /etc/network/interfaces (no wireless-... entries):
>
> # interface file auto-generated by buildroot
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet dhcp
> pre-up /etc/network/nfs_check
> wait-delay 15
> hostname $(hostname)
>
> auto wlan0
> iface wlan0 inet dhcp
> pre-up wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -B
> post-down killall -q wpa_supplicant
>
> - my /etc/wpa_supplicant.conf (only the bare minimum):
>
> network={
> ssid="my ssid"
> psk="my password"
> }
>
>
> Run wpa_supplicant with debug enabled (-dd)...double check ssid/psk?
>
> Regards,
> Peter
>
>>
>> Regards
>> Ola
>
>
Hi Peter,
WiFi is now working. Enabling the wpa_supplicant in debug mode revealed
that there was an old file /var/run/wpa_supplicant/wlan0 that it wanted
me to "delete" which I simply renamed.
I then proceed to running again but then I realized that I forgot to
kill the original wpa_supplicant which was automatically started.
Killing this process and issuing the wpa_supplicant directly from the
command line kicked things into life.
Thank you for your support highly appreciated.
Regards
Ola
prev parent reply other threads:[~2018-12-17 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 20:17 [Buildroot] Wifi not working - raspberrypi3_defconfig Ola Oni
2018-12-17 7:16 ` Peter Seiderer
2018-12-17 7:50 ` Ola Oni
2018-12-17 10:18 ` Martin Bark
2018-12-17 10:20 ` Ola Oni
2018-12-17 10:22 ` Peter Seiderer
2018-12-17 20:31 ` Ola Oni
2018-12-17 21:25 ` Peter Seiderer
2018-12-17 23:12 ` Ola Oni [this message]
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=874112de-fdc3-990f-1bac-522d2aeb2a1a@gmail.com \
--to=oniola@gmail.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox