[yocto] wpa_supplicant on Raspberry Pi 2B
Daniel.
danielhilst at gmail.com
Fri Oct 2 12:50:00 PDT 2015
This seems weird to me:
"Could not set interface wlan0 flags (UP): No such file or directory"
Are you running this as root? What wifi card are you using? I had to
install linux-firmware to get wifi working but this wasn't on raspberry so
I didn't know what is triggering this NSFOD error. My guess was permission,
but...
The wpa_supplicant.conf seems fine to me. The `wpa_cli stat' returns what?
2015-10-02 16:08 GMT-03:00 Edward Vidal <develone at sbcglobal.net>:
> Hi Daniel,
> You are right wpa_supplicant is not running.
> I tried the following no success.
> wpa_supplicant -ddd -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -D
> nl80211,wext -c /etc/wpa_supplicant.conf
> wpa_supplicant v2.4
> random: Trying to read entropy from /dev/random
> Successfully initialized wpa_supplicant
> Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver
> 'nl80211,wext' ctrl_interface 'N/A' bridge 'N/A'
> Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
> Reading configuration file '/etc/wpa_supplicant.conf'
> ctrl_interface='/var/run/wpa_supplicant'
> ctrl_interface_group='0'
> update_config=1
> Line: 5 - start of a new network block
> scan_ssid=1 (0x1)
> ssid - hexdump_ascii(len=10):
> 41 54 54 39 78 32 78 39 6a 37 ATT9x2x9j7
> PSK (ASCII passphrase) - hexdump_ascii(len=12): [REMOVED]
> proto: 0x1
> key_mgmt: 0x2
> PSK (from passphrase) - hexdump(len=32): [REMOVED]
> Priority group 0
> id=0 ssid='ATT9x2x9j7'
> rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
> nl80211: Supported cipher 00-0f-ac:1
> nl80211: Supported cipher 00-0f-ac:5
> nl80211: Supported cipher 00-0f-ac:2
> nl80211: Supported cipher 00-0f-ac:4
> nl80211: Using driver-based off-channel TX
> nl80211: interface wlan0 in phy phy0
> nl80211: Set mode ifindex 3 iftype 2 (STATION)
> nl80211: Subscribe to mgmt frames with non-AP handle 0x8f8eb8
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
> nl_handle=0x8f8eb8 match=06
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
> nl_handle=0x8f8eb8 match=0a07
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
> nl_handle=0x8f8eb8 match=0a11
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
> nl_handle=0x8f8eb8 match=1101
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
> nl_handle=0x8f8eb8 match=1102
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
> nl_handle=0x8f8eb8 match=0505
> Could not set interface wlan0 flags (UP): No such file or directory
> nl80211: Could not set interface 'wlan0' UP
> nl80211: deinit ifname=wlan0 disabled_11b_rates=0
> nl80211: Remove monitor interface: refcount=0
> netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6
> (IF_OPER_UP)
> nl80211: Set mode ifindex 3 iftype 2 (STATION)
> nl80211: Unsubscribe mgmt frames handle 0x88070631 (mode change)
> wlan0: Failed to initialize driver interface - try next driver wrapper
> WEXT: cfg80211-based driver detected
> wext: interface wlan0 phy: phy0
> rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
> Could not set interface wlan0 flags (UP): No such file or directory
> WEXT: Could not set interface 'wlan0' UP
> wlan0: Failed to initialize driver interface
> Failed to add interface wlan0
> wlan0: Cancelling scan request
> wlan0: Cancelling authentication timeout
>
> Is this correct for the wpa_supplicant.conf?
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> update_config=1
>
> network={
> scan_ssid=1
> ssid="ATT9x2x9j7"
> psk="2%699656433d"
> proto=WPA
> key_mgmt=WPA-PSK
> }
>
> Any ideas?
>
> Thanks
>
> Edward Vidal Jr. e-mail develone at sbcglobal.net 915-595-1613
>
>
>
> On Friday, October 2, 2015 12:18 PM, Daniel. <danielhilst at gmail.com>
> wrote:
>
>
> It seems that your wpa_supplicant isn't being started at boot. Can you see
> it with `ps | grep wpa_supplicant'? You may start it by hand with something
> like `wpa_supplicant -B -iwlan0 -c /etc/wpa_supplicant.conf' and try
> `wpa_cli stat' stat again...
>
> Regards,
>
> 2015-10-02 12:34 GMT-03:00 Edward Vidal <develone at sbcglobal.net>:
>
> Hi Philip & Daniel,
> I modified interface
> diff -u interfaces.orig interfaces
> --- interfaces.orig 2015-09-15 04:53:28.759998719 +0000
> +++ interfaces 2015-09-15 04:54:16.999998700 +0000
> @@ -8,8 +8,8 @@
> iface wlan0 inet dhcp
> wireless_mode managed
> wireless_essid any
> - wpa-driver wext
> - wpa-conf /etc/wpa_supplicant.conf
> + wpa-driver nl80211
> + wpa-conf /etc/wpa_supplicant.conf
>
> iface atml0 inet dhcp
> Also ran the wpa_cli stat
> root at raspberrypi2:/etc/network# wpa_cli stat
> Failed to connect to non-global ctrl_ifname: (nil) error: Success
> and
> wpa_cli -i wlan0
> wpa_cli v2.4
> Copyright (c) 2004-2015, Jouni Malinen <j at w1.fi> and contributors
>
> This software may be distributed under the terms of the BSD license.
> See README for more details.
>
>
>
> Interactive mode
>
> Could not connect to wpa_supplicant: wlan0 - re-trying
> Still no success.
> Thanks
> Edward Vidal Jr. e-mail develone at sbcglobal.net 915-595-1613
>
>
>
> On Friday, October 2, 2015 9:09 AM, "yocto-request at yoctoproject.org" <
> yocto-request at yoctoproject.org> wrote:
>
>
> Send yocto mailing list submissions to
> yocto at yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-request at yoctoproject.org
>
> You can reach the person managing the list at
> yocto-owner at yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
>
>
> Today's Topics:
>
> 1. Release Candidate Build for yocto-2.0.rc1.rc1 now available.
> (Poky Build User)
> 2. Re: Safely cleaning 'downloads' (Laurentiu Palcu)
> 3. Re: [linux-yocto] [raspberryp2] Error during the build of
> linux kernel (Trevor Woerner)
> 4. wpa_supplicant on Raspberry Pi 2B (Edward Vidal)
> 5. Re: wpa_supplicant on Raspberry Pi 2B (Philip Balister)
> 6. Re: wpa_supplicant on Raspberry Pi 2B (Daniel.)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 02 Oct 2015 07:04:04 +0000
> From: "Poky Build User" <pokybuild at fedora21.osl.yoctoproject.org>
> To: yocto at yoctoproject.org
> Cc: otavio at ossystems.com.br
> Subject: [yocto] Release Candidate Build for yocto-2.0.rc1.rc1 now
> available.
> Message-ID: <20151002070407.D2B43E00D10 at yocto-www.yoctoproject.org>
> Content-Type: text/plain; charset=us-ascii
>
>
> A release candidate build for yocto-2.0.rc1 is now available at:
>
>
> http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.rc1
>
>
> Please begin QA on this build as soon as possible.
>
>
> Build hash information:
> meta-intel : 84c049b9cb80b50fd32b716c2ae97e3f0d4e3cd7
> meta-fsl-arm : 10471566d2868b07f8ac832b94d5e98a463826ba
> meta-minnow : 9c965ef5252e383843d796cd8b50c61b3034b6ae
> meta-qt3 : 5233565c80db869f6f539f37f26ea6662d9dc5f6
> meta-fsl-ppc : 59fc0c33d2de5db65af4c09c4d28fd78fa0f7b4f
> poky : eac61f37e36099f74485dab398b57f3812826d17
>
>
> This is an automated message from
> The Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder
> Email: elizabeth.flanagan at intel.com
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 2 Oct 2015 14:43:37 +0300
> From: Laurentiu Palcu <laurentiu.palcu at intel.com>
> To: Gary Thomas <gary at mlbassoc.com>
> Cc: Yocto Project <yocto at yoctoproject.org>
> Subject: Re: [yocto] Safely cleaning 'downloads'
> Message-ID: <20151002114337.GG15509 at lpalcu-desk>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Garry,
>
> It's probably a little late (I'm not reading the Yocto mailing lists
> very often now) but sometime ago I ran out of space myself and I wrote
> this script that I sent out on oe-core mailing list. It did the job for
> me. For some reason it didn't make it in master but maybe you find it
> useful.
>
> I didn't test it since then though. Maybe things changed, I don't know.
> Give it a try if you wish. If you want to play safe, I recommend making
> a copy of your downloads directory (if you have space left). :)
>
>
> http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106026.html
>
> laurentiu
>
> On Wed, Sep 30, 2015 at 06:13:39AM -0600, Gary Thomas wrote:
> > Over time, I tend to build in the same build tree many, many
> > times. This leads to some really big trees as many things are
> > duplicated, especially in the 'downloads' directory.
> >
> > I use local mirrors and hence my 'downloads' directory is
> > _mostly_ populated with symbolic links. However, there are
> > also expanded SCM packages, e.g. git2/xxx
> >
> > How can I safely clean up the 'downloads' directory? I already
> > copy any created tarballs (I use BB_GENERATE_MIRROR_TARBALLS="1"
> > to preclude unneeded downloads) to my mirror, but I'd like to
> > periodically clean out the whole directory (without disturbing
> > my builds of course). I've found out the hard way that just
> > emptying seems to be unsafe, at least for some recipes like
> > the [RaspberryPi] Linux kernel recipe which once built seems
> > to expect the expanded git2/xxx tree to remain.
> >
> > Just trying to find ways to recover my lost GB...
> >
> > Thanks for any ideas
> >
> > --
> > ------------------------------------------------------------
> > Gary Thomas | Consulting for the
> > MLB Associates | Embedded world
> > ------------------------------------------------------------
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 2 Oct 2015 08:02:49 -0400
> From: Trevor Woerner <twoerner at gmail.com>
> To: Karim ATIKI <karim_atiki at hotmail.com>
> Cc: "yocto at yoctoproject.org" <yocto at yoctoproject.org>
> Subject: Re: [yocto] [linux-yocto] [raspberryp2] Error during the
> build of linux kernel
> Message-ID: <560E7269.6090903 at gmail.com>
> Content-Type: text/plain; charset=windows-1252
>
> On 10/02/15 07:58, Karim ATIKI wrote:
> > Hello Trevor,
> >
> > Thanks for your feedback.
> > You really think that "Fido" is an older release ?
>
> Sorry, I didn't mean to imply it was "old" and therefore should be
> avoided, I meant to point out that it was something that was released
> before the switch to gcc5 by default :-)
>
> > Is the 1.9 release of Yocto stable enough yet ? And will this pb be
> > fixed as well ?
>
> I think the next release will be 2.0. Whether or not it is stable enough
> is something you will have to evaluate for yourself :-) I'm rather
> certain this issue is already fixed in master, therefore it should be
> available for the next release.
>
> >
> > Karim
>
> Did you really mean to reply personally? I've re-CC'ed the list, hope
> you don't mind.
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 2 Oct 2015 14:27:58 +0000 (UTC)
> From: Edward Vidal <develone at sbcglobal.net>
> To: "yocto at yoctoproject.org" <yocto at yoctoproject.org>
> Subject: [yocto] wpa_supplicant on Raspberry Pi 2B
> Message-ID:
> <1006153332.270433.1443796078701.JavaMail.yahoo at mail.yahoo.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello all,I am using a Wi-Pi wireless adapter.?
> My image has the following packages installed.
> wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> Do I need any additional packages?
> My wired eth0 works okay.
> Which document has the most current information on setting up wireless
> networking?From the information at
> http://trac.gateworks.com/wiki/Yocto/Wireless
>
> I modified my /etc/wpa_supplicant.conf as below without success.
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> update_config=1
>
> network={
> ??????? scan_ssid=1
> ??????? ssid="myssid"
> ??????? psk="mypsk"
> ??????? proto=WPA
> ??????? key_mgmt=WPA-PSK
> }Below is the results I get when I run iwconfig.
> iwconfig
> wlan0???? IEEE 802.11bgn? ESSID:off/any?
> ????????? Mode:Managed? Access Point: Not-Associated?? Tx-Power=0 dBm??
> ????????? Retry short limit:7?? RTS thr:off?? Fragment thr:off
> ????????? Encryption key:off
> ????????? Power Management:off
> ?????????
> lo??????? no wireless extensions.
>
> eth0????? no wireless extensions.
> Thanks in advance.? Any help is appreciated.
>
> Edward Vidal Jr. e-mail develone at sbcglobal.net 915-595-1613
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.yoctoproject.org/pipermail/yocto/attachments/20151002/a3a81a97/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 5
> Date: Fri, 2 Oct 2015 10:56:37 -0400
> From: Philip Balister <philip at balister.org>
> To: Edward Vidal <develone at sbcglobal.net>, "yocto at yoctoproject.org"
> <yocto at yoctoproject.org>
> Subject: Re: [yocto] wpa_supplicant on Raspberry Pi 2B
> Message-ID: <560E9B25.5030303 at balister.org>
> Content-Type: text/plain; charset=windows-1252
>
>
> On 10/02/2015 10:27 AM, Edward Vidal wrote:
> > Hello all,I am using a Wi-Pi wireless adapter.
> > My image has the following packages installed.
> > wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> > wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> > wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> > wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> > wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> > Do I need any additional packages?
> > My wired eth0 works okay.
> > Which document has the most current information on setting up wireless
> networking?From the information at
> > http://trac.gateworks.com/wiki/Yocto/Wireless
> >
> > I modified my /etc/wpa_supplicant.conf as below without success.
> > ctrl_interface=/var/run/wpa_supplicant
> > ctrl_interface_group=0
> > update_config=1
> >
>
> Try modifying /etc/network/interfaces like this:
>
>
> https://github.com/EttusResearch/meta-ettus/commit/da86e76d116798e386d073a18453aabb6179a09a#diff-063964fa6e41065c7868b13b1b1644eaR11
>
> it seems wireless extensions are deprecated and you should use the
> nl80211 driver now.
>
> Philip
>
>
> > network={
> > scan_ssid=1
> > ssid="myssid"
> > psk="mypsk"
> > proto=WPA
> > key_mgmt=WPA-PSK
> > }Below is the results I get when I run iwconfig.
> > iwconfig
> > wlan0 IEEE 802.11bgn ESSID:off/any
> > Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
> > Retry short limit:7 RTS thr:off Fragment thr:off
> > Encryption key:off
> > Power Management:off
> >
> > lo no wireless extensions.
> >
> > eth0 no wireless extensions.
> > Thanks in advance. Any help is appreciated.
> >
> > Edward Vidal Jr. e-mail develone at sbcglobal.net 915-595-1613
> >
> >
> >
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 2 Oct 2015 12:08:28 -0300
> From: "Daniel." <danielhilst at gmail.com>
> Cc: "yocto at yoctoproject.org" <yocto at yoctoproject.org>
> Subject: Re: [yocto] wpa_supplicant on Raspberry Pi 2B
> Message-ID:
> <CAF3SDA7kvgNsTB7RM_wZgDUkz5b8msv7r7=3B1kCHVqR35aEbA at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
>
> What `wpa_cli stat' returns?
>
> Regards,
>
>
> 2015-10-02 11:56 GMT-03:00 Philip Balister <philip at balister.org>:
> > On 10/02/2015 10:27 AM, Edward Vidal wrote:
> >> Hello all,I am using a Wi-Pi wireless adapter.
> >> My image has the following packages installed.
> >> wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> >> wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> >> wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> >> wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> >> wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon
> >> Do I need any additional packages?
> >> My wired eth0 works okay.
> >> Which document has the most current information on setting up wireless
> networking?From the information at
> >> http://trac.gateworks.com/wiki/Yocto/Wireless
> >>
> >> I modified my /etc/wpa_supplicant.conf as below without success.
> >> ctrl_interface=/var/run/wpa_supplicant
> >> ctrl_interface_group=0
> >> update_config=1
> >>
> >
> > Try modifying /etc/network/interfaces like this:
> >
> >
> https://github.com/EttusResearch/meta-ettus/commit/da86e76d116798e386d073a18453aabb6179a09a#diff-063964fa6e41065c7868b13b1b1644eaR11
> >
> > it seems wireless extensions are deprecated and you should use the
> > nl80211 driver now.
> >
> > Philip
> >
> >
> >> network={
> >> scan_ssid=1
> >> ssid="myssid"
> >> psk="mypsk"
> >> proto=WPA
> >> key_mgmt=WPA-PSK
> >> }Below is the results I get when I run iwconfig.
> >> iwconfig
> >> wlan0 IEEE 802.11bgn ESSID:off/any
> >> Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
> >> Retry short limit:7 RTS thr:off Fragment thr:off
> >> Encryption key:off
> >> Power Management:off
> >>
> >> lo no wireless extensions.
> >>
> >> eth0 no wireless extensions.
> >> Thanks in advance. Any help is appreciated.
> >>
> >> Edward Vidal Jr. e-mail develone at sbcglobal.net 915-595-1613
> >>
> >>
> >>
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
>
>
> --
> "Do or do not. There is no try"
> Yoda Master
>
>
> ------------------------------
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> End of yocto Digest, Vol 61, Issue 8
> ************************************
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>
> --
> *"Do or do not. There is no try"*
> *Yoda Master*
>
>
>
--
*"Do or do not. There is no try"*
*Yoda Master*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151002/513a464f/attachment.html>
More information about the yocto
mailing list