Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Wifi not working - raspberrypi3_defconfig
Date: Mon, 17 Dec 2018 11:22:34 +0100	[thread overview]
Message-ID: <20181217112234.7147783d@gmx.net> (raw)
In-Reply-To: <CAPru4TVQx0p1vifynJcqHGdph8vXqWdAa2_p_NzTKyOW7YBX1g@mail.gmail.com>

Hello Ola,

On Mon, 17 Dec 2018 07:50:41 +0000, Ola Oni <oniola@gmail.com> wrote:

> Hi Peter,
> 
> Thanks for your reply. I will try and configure later on today and report
> back.
> 
> May I add that when I use "ps" command wpa_supplicant process seem to be
> listed as one of the process running so I assumed that "This is a giving"

Seems you have BR2_PACKAGE_WPA_SUPPLICANT already enabled...

> 
> So I must have assumed wrong ?

....so you did not use plain raspberrypi3_defconfig (or made already some
changes to it)...., from your given examples I suspect your followed this
receipe [1]? Please provide next time your .config/defconfig (after
savedefconfig) files...

I see no 'brcmfmac' lines in your dmesg output, maybe BR2_PACKAGE_RPI_WIFI_FIRMWARE
not enabled? Or your did not change to BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV?

Or something with your config files, make sure to only use plain spaces (after copying
from your email I got no plain spaces as indent but some UTF-8 spaces)...

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

Regards,
Peter

[1] https://rohitsw.wordpress.com/2016/12/17/building-a-linux-filesystem-on-raspberry-pi-3/

> 
> Regards
> Ola
> 
> On Mon, 17 Dec 2018 at 07:16, Peter Seiderer <ps.report@gmx.net> wrote:
> 
> > Hello Ola,
> >
> > On Sun, 16 Dec 2018 20:17:30 +0000, Ola Oni <oniola@gmail.com> wrote:
> >  
> > > Hi Martin,
> > >
> > > I was advised to email you about my issue of not been able to get Wifi
> > > working on raspberry pi 3 using buildroot 2018.11
> > >
> > > Below are the entry in my two files [/etc/network/interfaces and
> > > /etc/wpa_supplicant.conf]
> > >
> > > # /etc/wpa_supplicant.conf <- filename
> > > ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
> > > ctrl_interface_group=0
> > > update_config=1
> > >
> > >      network={
> > >              ssid="myssid"
> > >              psk="mypassword"
> > >              proto=WPA
> > >              key_mgmt=WPA-PSK
> > >              pairwise=CCMP
> > >              auth_alg=OPEN
> > >      }
> > >
> > > ########################################
> > > # /etc/network/interfaces <- filename
> > > # 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
> > >          wireless-essid "myssid"
> > >          wireless-key "mypassword"
> > >          pre-up wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -B
> > >          post-down killall -q wpa_supplicant
> > >
> > > Attached to this is email is the output from dmesg.  
> >
> > Not much info, Wifi will definitely not work with raspberrypi3_defconfig
> > out of the box (e.g. package BR2_PACKAGE_WPA_SUPPLICANT not enabled)...
> >
> > Regards,
> > Peter
> >  
> > >
> > > Regards
> > >
> > > onio
> > >
> > >
> > >  
> >
> >  

  parent reply	other threads:[~2018-12-17 10:22 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 [this message]
2018-12-17 20:31       ` Ola Oni
2018-12-17 21:25         ` Peter Seiderer
2018-12-17 23:12           ` Ola Oni

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=20181217112234.7147783d@gmx.net \
    --to=ps.report@gmx.net \
    --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