Re: [yocto] wpa_supplicant on Raspberry Pi 2B

2015-10-03 Thread Daniel. 
2015-10-02 18:37 GMT-03:00 Edward Vidal :
> Hi all,
> Still no success getting wifi working.
> Any and all help appreciated.
>
> Created a new image which installed 46 new rpms linux-firmware see below.
>
> ps -ax | grep wpa_supplicant
>   503 ?S  0:00 /usr/sbin/wpa_supplicant -u
>   704 pts/0R+ 0:00 grep wpa_supplicant
>
Well wpa_supplicant is running here with -u option. Did you have
connman installed? What image you're using? I don't have a rasp2 so I
can only test with raspB.

Best regards,


> root@raspberrypi2:~# wpa_cli stat
> Failed to connect to non-global ctrl_ifname: (nil)  error: Success
> root@raspberrypi2:~# wpa_cli stat
> Failed to connect to non-global ctrl_ifname: (nil)  error: Success
>
> root@raspberrypi2:~# wpa_supplicant -ddd -B  -i wlan0 -D nl80211 -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' 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=1 hard=0
> rfkill: WLAN soft blocked
> 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 0x5a6e68
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68
> match=06
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68
> match=0a07
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68
> match=0a11
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68
> match=1101
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68
> match=1102
> nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68
> match=0505
> nl80211: Could not yet enable interface 'wlan0' due to rfkill
> netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5
> (IF_OPER_DORMANT)
> nl80211: driver param='(null)'
> Add interface wlan0 to a new radio phy0
> nl80211: Regulatory information - country=00
> nl80211: 2402-2472 @ 40 MHz 20 mBm
> nl80211: 2457-2482 @ 40 MHz 20 mBm (no IR)
> nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
> nl80211: 5170-5250 @ 160 MHz 20 mBm (no IR)
> nl80211: 5250-5330 @ 160 MHz 20 mBm (DFS) (no IR)
> nl80211: 5490-5730 @ 160 MHz 20 mBm (DFS) (no IR)
> nl80211: Added 802.11b mode based on 802.11g information
> wlan0: Own MAC address: 40:a5:ef:05:4d:01
> wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0
> set_tx=0 seq_len=0 key_len=0
> nl80211: set_key failed; err=-100 Network is down)
> wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1
> set_tx=0 seq_len=0 key_len=0
> nl80211: set_key failed; err=-100 Network is down)
> wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2
> set_tx=0 seq_len=0 key_len=0
> nl80211: set_key failed; err=-100 Network is down)
> wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3
> set_tx=0 seq_len=0 key_len=0
> nl80211: set_key failed; err=-100 Network is down)
> wlan0: RSN: flushing PMKID list in the driver
> nl80211: Flush PMKIDs
> wlan0: Setting scan request: 0.10 sec
> wlan0: WPS: UUID based on MAC address: 50fb4973-c5e3-5899-b3c0-27a64501d294
> GnuTLS: Library version 3.3.14 (runtime) - 3.3.14 (build)
> EAPOL: SUPP_PAE entering state DISCONNECTED
> EAPOL: Supplicant port status: Unauthorized
> nl80211: Skip set_supp_port(unauthorized) while not associated
> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> Using existing control interface directory.
> ctrl_interface_group=0
> wlan0: Added interface wlan0
> wlan0: State: DISCONNECTED -> DISCONNECTED
> nl80211: Set wlan0 operstate 0->0 (DORMANT)
> netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5
> (IF_OPER_DORMANT)
> Daemonize..
>
> root@raspberrypi2:~# wpa_cli stat
> Selected interface 'wlan0'
> wpa_state=INTERFACE_DISABLED
> address=40:a5:ef:05:4d:01
> uuid=50fb4973-c5e3-5899-b3c0-27a64501d294
>
> root@raspberrypi2:~# ifconfig wlan0
> wlan0

Re: [yocto] wpa_supplicant on Raspberry Pi 2B

2015-10-02 Thread Philip Balister 
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
>   
> lono wireless extensions.
> 
> eth0  no wireless extensions.
> Thanks in advance.  Any help is appreciated.
> 
>  Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpa_supplicant on Raspberry Pi 2B

2015-10-02 Thread Daniel. 
What `wpa_cli stat' returns?

Regards,


2015-10-02 11:56 GMT-03:00 Philip Balister :
> 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
>>
>> lono wireless extensions.
>>
>> eth0  no wireless extensions.
>> Thanks in advance.  Any help is appreciated.
>>
>>  Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613
>>
>>
>>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Do or do not. There is no try"
  Yoda Master
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpa_supplicant on Raspberry Pi 2B

2015-10-02 Thread Edward Vidal 
 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@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


--

Message: 3
Date: Fri, 2 Oct 2015 08:02:49 -0400
From: Trevor Woerner <twoer...@gmail.com>
To: Karim ATIKI <karim_at...@hotmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [yocto] [linux-yocto] [raspberryp2] Error during the
    build of linux kernel
Message-ID: <560e7269.6090...@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 + (UTC)
From: Edward Vidal <devel...@sbcglobal.net>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: [yocto] wpa_supplicant on Raspberry Pi 2B
Message-ID:
    <1006153332.270433.1443796078701.javamail.ya...@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 devel...@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 <phi...@balister.org>
To: Edward Vidal <devel...@sbcglobal.net>,    "yocto@yoctoproject.org"
    <yocto@yoctoproject.org>
Subject: Re: [yocto] wpa_supplicant on Raspberry Pi 2B
Message-ID: <560e9b25.5030...@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

Re: [yocto] wpa_supplicant on Raspberry Pi 2B

2015-10-02 Thread Daniel. 
mbedded-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@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
>
> --
>
> Message: 3
> Date: Fri, 2 Oct 2015 08:02:49 -0400
> From: Trevor Woerner <twoer...@gmail.com>
> To: Karim ATIKI <karim_at...@hotmail.com>
> Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
> Subject: Re: [yocto] [linux-yocto] [raspberryp2] Error during the
> build of linux kernel
> Message-ID: <560e7269.6090...@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 + (UTC)
> From: Edward Vidal <devel...@sbcglobal.net>
> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
> Subject: [yocto] wpa_supplicant on Raspberry Pi 2B
> Message-ID:
> <1006153332.270433.1443796078701.javamail.ya...@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.?

Re: [yocto] wpa_supplicant on Raspberry Pi 2B

2015-10-02 Thread Daniel. 
t; 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@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
>
> --
>
> Message: 3
> Date: Fri, 2 Oct 2015 08:02:49 -0400
> From: Trevor Woerner <twoer...@gmail.com>
> To: Karim ATIKI <karim_at...@hotmail.com>
> Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
> Subject: Re: [yocto] [linux-yocto] [raspberryp2] Error during the
> build of linux kernel
> Message-ID: <560e7269.6090...@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 + (UTC)
> From: Edward Vidal <devel...@sbcglobal.net>
> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
> Subject: [yocto] wpa_supplicant on Raspberry Pi 2B
> Message-ID:
> <1006153332.270433.1443796078701.javamail.ya...@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 devel...@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 <phi...@balister.org>
> To: Edward Vidal <devel...@sbcglobal.net>,"yocto@yoctoproject.org"
> <yocto@yoctoproject.org>
> Subject: Re: [yocto] wpa_supplicant on Raspberry Pi 2B
> Message-ID: <560e9b25.5030...@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 wirel

Re: [yocto] wpa_supplicant on Raspberry Pi 2B

2015-10-02 Thread Edward Vidal 
Hi all,Still no success getting wifi working.Any and all help appreciated.
Created a new image which installed 46 new rpms linux-firmware see below.
 
ps -ax | grep wpa_supplicant
  503 ?    S  0:00 /usr/sbin/wpa_supplicant -u
  704 pts/0    R+ 0:00 grep wpa_supplicant

root@raspberrypi2:~# wpa_cli stat
Failed to connect to non-global ctrl_ifname: (nil)  error: Success
root@raspberrypi2:~# wpa_cli stat
Failed to connect to non-global ctrl_ifname: (nil)  error: Success

root@raspberrypi2:~# wpa_supplicant -ddd -B  -i wlan0 -D nl80211 -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' 
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=1 hard=0
rfkill: WLAN soft blocked
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 0x5a6e68
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 
match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 
match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 
match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 
match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 
match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 
match=0505
nl80211: Could not yet enable interface 'wlan0' due to rfkill
netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 
(IF_OPER_DORMANT)
nl80211: driver param='(null)'
Add interface wlan0 to a new radio phy0
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 2457-2482 @ 40 MHz 20 mBm (no IR)
nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
nl80211: 5170-5250 @ 160 MHz 20 mBm (no IR)
nl80211: 5250-5330 @ 160 MHz 20 mBm (DFS) (no IR)
nl80211: 5490-5730 @ 160 MHz 20 mBm (DFS) (no IR)
nl80211: Added 802.11b mode based on 802.11g information
wlan0: Own MAC address: 40:a5:ef:05:4d:01
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 
set_tx=0 seq_len=0 key_len=0
nl80211: set_key failed; err=-100 Network is down)
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 
set_tx=0 seq_len=0 key_len=0
nl80211: set_key failed; err=-100 Network is down)
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 
set_tx=0 seq_len=0 key_len=0
nl80211: set_key failed; err=-100 Network is down)
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 
set_tx=0 seq_len=0 key_len=0
nl80211: set_key failed; err=-100 Network is down)
wlan0: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlan0: Setting scan request: 0.10 sec
wlan0: WPS: UUID based on MAC address: 50fb4973-c5e3-5899-b3c0-27a64501d294
GnuTLS: Library version 3.3.14 (runtime) - 3.3.14 (build)
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
nl80211: Skip set_supp_port(unauthorized) while not associated
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Using existing control interface directory.
ctrl_interface_group=0
wlan0: Added interface wlan0
wlan0: State: DISCONNECTED -> DISCONNECTED
nl80211: Set wlan0 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 
(IF_OPER_DORMANT)
Daemonize..

root@raspberrypi2:~# wpa_cli stat
Selected interface 'wlan0'
wpa_state=INTERFACE_DISABLED
address=40:a5:ef:05:4d:01
uuid=50fb4973-c5e3-5899-b3c0-27a64501d294

root@raspberrypi2:~# ifconfig wlan0
wlan0 Link encap:Ethernet  HWaddr 40:A5:EF:05:4D:01  
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Thanks
+linux-firmware-0.0+git0+3161bfa479-r0.all
+linux-firmware-ar3k-0.0+git0+3161bfa479-r0.all