wpa_driver_priv_driver_cmd calls ioctl "SIOCSIWPRIV" which is not supported
in kernel.




On Thu, Jan 28, 2010 at 4:07 PM, ZhangJieJing <kzj...@gmail.com> wrote:

>
>  On Thu, Jan 28, 2010 at 8:29 AM, linux newbie 
> <linux.newbi...@gmail.com>wrote:
>
>> The issue is still there. But I can establish the connection with SSID.
>>
>> I enabled wpa_supplicant and dhcpcd as service in init.rc. Then from GUI
>> on selecting WIFI, I can able to connect to SSID. But all the time
>> wpa_driver_priv_driver_cmd failed is keep on displaying (in logcat).
>>
>
> What command failed  ?
> I think your wpa_driver_xxx.c or your wifi driver is have some command not
> matched.
>
> you maybe need dump the private command in wpa_supplicant  & kernel wifi
> driver to figure out which command is failed.
>
>
>>
>> If I go to static IP settings window, then bang "dhcpcd" fails and my
>> target is not connecting to SSID. :(
>>
>>
>>
>>  On Wed, Jan 27, 2010 at 8:26 PM, Richard Chang <
>> richard.chan...@gmail.com> wrote:
>>
>>> Hi:
>>>
>>>   I have the same problem, "wpa_driver_priv_driver_cmd failed".
>>>   Did you resolve it?
>>>
>>> Thanks,
>>>
>>>
>>> On Jan 22, 7:34 am, linux newbie <linux.newbi...@gmail.com> wrote:
>>> > Hi,
>>> >
>>> > Any suggestions?
>>> >
>>> > Thanks
>>> >
>>> > On Thu, Jan 21, 2010 at 5:33 PM, linux newbie <
>>> linux.newbi...@gmail.com>wrote:> Hi,
>>>
>>>  >
>>> > > I modified wifi.c but still couldnt get the UI to display the desired
>>> > > results. This time logcat shows the following error. As I have
>>> started the
>>> > > supplicant as service, it is associated to AP.
>>> >
>>> > > If I do ifconfig eth1 it shows the static IP address assigned.
>>> >
>>> > > I set the following in init.rc file after making modifications in
>>> wifi.c
>>> > > accordingly
>>> > > setprop wifi.interface "eth1"
>>> > > setprop wlan.driver.status "ok" (as driver is built in kernel instead
>>> of
>>> > > module)
>>> > > setprop init.svc.wpa_supplicant "running" (as it is started as
>>> service)
>>> >
>>> > > service wpa_supplicant /system/bin/wpa_supplicant \
>>> > >            -D wext -i eth1 -c /system/etc/wpa_supplicant.conf
>>> > >            group wifi
>>> >
>>> > > When I select WIFI in GUI, my association with AP disconnects.
>>> Following is
>>> > > the logcat. Help me to resolve this issue.
>>> >
>>> > > I/wpa_supplicant(  913): CTRL-EVENT-STATE-CHANGE id=0 state=4
>>> > > V/WifiMonitor( 2286): Event [CTRL-EVENT-STATE-CHANGE id=0 state=4]
>>> > > I/wpa_supplicant(  913): Associated with 00:23:ab:be:90:70
>>> > > I/wpa_supplicant(  913): CTRL-EVENT-STATE-CHANGE id=0 state=5
>>> > > V/WifiStateTracker( 2286): Changing supplicant state: ASSOCIATING ==>
>>> > > ASSOCIATED
>>> > > D/NetworkStateTracker( 2286): setDetailed state, old =CONNECTING and
>>> new
>>> > > state=CONNECTING
>>> > > V/WifiMonitor( 2286): Event [Associated with 00:23:ab:be:90:70]
>>> > > V/WifiMonitor( 2286): Event [CTRL-EVENT-STATE-CHANGE id=0 state=5]
>>> > > V/WifiStateTracker( 2286): Changing supplicant state: ASSOCIATED ==>
>>> > > FOUR_WAY_HANDSHAKE
>>> > > D/NetworkStateTracker( 2286): setDetailed state, old =CONNECTING and
>>> new
>>> > > state=AUTHENTICATING
>>> > > D/ConnectivityService( 2286): ConnectivityChange for WIFI:
>>> > > CONNECTING/AUTHENTICATING
>>> > > I/wpa_supplicant(  913): CTRL-EVENT-STATE-CHANGE id=0 state=5
>>> > > V/WifiMonitor( 2286): Event [CTRL-EVENT-STATE-CHANGE id=0 state=5]
>>> > > I/wpa_supplicant(  913): CTRL-EVENT-STATE-CHANGE id=0 state=6
>>> > > V/WifiStateTracker( 2286): Changing supplicant state:
>>> FOUR_WAY_HANDSHAKE
>>> > > ==> FOUR_WAY_HANDSHAKE
>>> > > V/WifiMonitor( 2286): Event [CTRL-EVENT-STATE-CHANGE id=0 state=6]
>>> > > V/WifiStateTracker( 2286): Changing supplicant state:
>>> FOUR_WAY_HANDSHAKE
>>> > > ==> GROUP_HANDSHAKE
>>> > > D/NetworkStateTracker( 2286): setDetailed state, old =AUTHENTICATING
>>> and
>>> > > new state=AUTHENTICATING
>>> > > W/ResourceType( 2286): Failure getting entry for 0x7f020080 (t=1
>>> e=128) in
>>> > > package 0: 0xffffffb5
>>> > > I/wpa_supplicant(  913): CTRL-EVENT-STATE-CHANGE id=0 state=6
>>> > > I/wpa_supplicant(  913): WPA: Key negotiation completed with
>>> > > 00:23:ab:be:90:70 [PTK=TKIP GTK=TKIP]
>>> > > I/wpa_supplicant(  913): CTRL-EVENT-STATE-CHANGE id=0 state=7
>>> > > I/wpa_supplicant(  913): CTRL-EVENT-CONNECTED - Connection to
>>> > > 00:23:ab:be:90:70 completed (reauth) [id=0 id_str=]
>>> > > V/WifiMonitor( 2286): Event [CTRL-EVENT-STATE-CHANGE id=0 state=6]
>>> > > V/WifiStateTracker( 2286): Changing supplicant state: GROUP_HANDSHAKE
>>> ==>
>>> > > GROUP_HANDSHAKE
>>> > > V/WifiMonitor( 2286): Event [WPA: Key negotiation completed with
>>> > > 00:23:ab:be:90:70 [PTK=TKIP GTK=TKIP]]
>>> > > V/WifiMonitor( 2286): Event [CTRL-EVENT-STATE-CHANGE id=0 state=7]
>>> > > V/WifiStateTracker( 2286): Changing supplicant state: GROUP_HANDSHAKE
>>> ==>
>>> > > COMPLETED
>>> > > V/WifiMonitor( 2286): Event [CTRL-EVENT-CONNECTED - Connection to
>>> > > 00:23:ab:be:90:70 completed (reauth) [id=0 id_str=]]
>>> > > V/WifiStateTracker( 2286): New network state is CONNECTED
>>> > > D/NetworkStateTracker( 2286): setDetailed state, old =AUTHENTICATING
>>> and
>>> > > new state=OBTAINING_IPADDR
>>> > > D/ConnectivityService( 2286): ConnectivityChange for WIFI:
>>> > > CONNECTING/OBTAINING_IPADDR
>>> > > D/Searchables( 2286): Checking component
>>> > >
>>> ComponentInfo{com.google.android.providers.enhancedgooglesearch/com.google.android.providers.enhancedgooglesearch.Launcher}
>>> > > D/dalvikvm( 2286): GREF has increased to 201
>>> > > D/dalvikvm( 2360): GC freed 3196 objects / 236944 bytes in 341ms
>>> > > I/ActivityThread( 2360): Publishing provider
>>> > > com.android.googlesearch.SuggestionProvider:
>>> > > com.android.googlesearch.SuggestionProvider
>>> > > I/ActivityThread( 2360): Publishing provider call_log:
>>> > > com.android.providers.contacts.CallLogProvider
>>> > > I/ActivityThread( 2360): Publishing provider user_dictionary:
>>> > > com.android.providers.userdictionary.UserDictionaryProvider
>>> > > I/WifiStateTracker( 2286): DhcpHandler: DHCP request failed: Timed
>>> out
>>> > > waiting for dhcpcd to start
>>> > > E/wpa_supplicant(  913): wpa_driver_priv_driver_cmd failed
>>> > > I/wpa_supplicant(  913): CTRL-EVENT-STATE-CHANGE id=0 state=8
>>> > > V/WifiMonitor( 2286): Event [CTRL-EVENT-STATE-CHANGE id=0 state=8]
>>> > > V/WifiStateTracker( 2286): Changing supplicant state: COMPLETED ==>
>>> DORMANT
>>> > > D/WifiStateTracker( 2286): Deconfiguring interface and stopping DHCP
>>> > > I/ActivityManager( 2286): Displayed activity
>>> > > com.android.launcher/.Launcher: 10516 ms (total 10516 ms)
>>> > > D/HomeLoaders( 2360):   ----> items cloned, ready to refresh UI
>>> > > E/WifiStateTracker( 2286): Could not stop DHCP
>>> > > D/NetworkStateTracker( 2286): setDetailed state, old
>>> =OBTAINING_IPADDR and
>>> > > new state=FAILED
>>> > > E/wpa_supplicant(  913): wpa_driver_priv_driver_cmd failed
>>> > > E/wpa_supplicant(  913): wpa_driver_priv_driver_cmd failed
>>> > > D/ConnectivityService( 2286): ConnectivityChange for WIFI:
>>> > > DISCONNECTED/FAILED
>>> > > V/ConnectivityService( 2286): Attempt to connect to WIFI failed.
>>> > > I/wpa_supplicant(  913): CTRL-EVENT-STATE-CHANGE id=-1 state=2
>>> > > V/WifiMonitor( 2286): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
>>> > > W/wpa_supplicant(  913):* Failed to initiate AP scan.*
>>> >
>>> > > On Thu, Jan 21, 2010 at 12:49 PM, linux newbie <
>>> linux.newbi...@gmail.com>wrote:
>>>
>>> >
>>> > >> yea feiyang, I am doing that. As I already loaded the driver, I
>>> believe I
>>> > >> need to make changes in it.
>>> >
>>> > >> let me try and get back to you guys.
>>> >
>>> > >> Thanks
>>> >
>>>  > >> On Thu, Jan 21, 2010 at 12:45 PM, feiyang yun <csd...@gmail.com>
>>> wrote:
>>> >
>>> > >>> hi
>>> > >>> you can check hardware/libhardware_legency/wifi/
>>> >
>>> > >>> 2010/1/21 linux newbie <linux.newbi...@gmail.com>
>>>
>>> >
>>> > >>> Hi,
>>> >
>>> > >>>> Thanks for your suggestions.
>>> >
>>> > >>>> I went through the source code and modified wpa_supplicant
>>> configuration
>>> > >>>> file and then I enabled it as service in init.rc file and its
>>> > >>>> working.(verified on viewing the log of router).
>>> >
>>> > >>>> service wpa_supplicant /system/bin/wpa_supplicant \
>>> > >>>>            -D wext -i eth1 -c /system/etc/wpasup.conf
>>> > >>>>            group wifi
>>> >
>>> > >>>> From Android GUI, if I select Wi-Fi, logcat still says "Failed to
>>> load
>>> > >>>> driver".
>>> > >>>> How the Android GUI communicates with wpa_supplicant? I believe
>>> GUI
>>> > >>>> communicates with supplicant in order to get scan results or
>>> set/get network
>>> > >>>> settings. correct me if I am wrong.
>>> >
>>> > >>>> Thanks
>>> >
>>>  > >>>> On Wed, Jan 20, 2010 at 6:57 PM, ZhangJieJing <kzj...@gmail.com>
>>> wrote:
>>> >
>>> > >>>>> can you do this ?
>>> >
>>> > >>>>> # touch /data/misc/wifi/wpa_supplicant
>>> >
>>> > >>>>> can you give more log about *chown[ctrl_interface]: Operation not
>>> > >>>>> permitted ?
>>> >
>>> > >>>>> *
>>> > >>>>> you may should check which process do the chown operation and
>>> which
>>> > >>>>> user of this process,
>>> > >>>>> maybe search the source code will be helpful, but I can't do this
>>> since
>>> > >>>>> the log infomation is too few.
>>> >
>>> > >>>>> **
>>> > >>>>> ---
>>> > >>>>> Best regards,
>>> > >>>>> Zhang Jiejing
>>> >
>>> > >>>>> On Wed, Jan 20, 2010 at 8:02 AM, linux newbie <
>>>    > >>>>> linux.newbi...@gmail.com> wrote:
>>> >
>>> > >>>>>> how you mount your /data dir?
>>> >
>>> > >>>>>> As I copied the entire root file system of android into
>>> USB(ext2) and
>>> > >>>>>> booting using "chroot /mnt /init", I commented out mount yaffs2
>>> line in
>>> > >>>>>> init.rc file.
>>> >
>>> > >>>>>> i.e commented following lines in default init.rc file
>>> > >>>>>> #mount yaffs2 m...@system /system
>>> > >>>>>> #mount yaffs2 m...@system /system ro remount
>>> > >>>>>> #mount yaffs2 m...@userdata /data nosuid nodev
>>> > >>>>>> #mount yaffs2 m...@cache /cache nosuid nodev
>>> >
>>> > >>>>>> also made rootfs as "rw" i.e mount rootfs rootfs / rw remount
>>> >
>>> > >>>>>> *ls -l /*
>>> > >>>>>> drwxrwx--x system   system            1970-01-01 00:08 data
>>> > >>>>>> -rw-r--r-- root     root          118 2010-01-19 02:18
>>> default.prop
>>> > >>>>>> drwxr-xr-x root     root              1970-01-01 00:14 dev
>>> > >>>>>> -rwxr-xr-x root     root       103164 2010-01-19 02:18 init
>>> > >>>>>> -rw-r--r-- root     root         1677 2010-01-19 02:18
>>> > >>>>>> init.goldfish.rc
>>> > >>>>>> lrwxrwxrwx root     root              1970-01-01 00:01 etc ->
>>> > >>>>>> /system/etc
>>> > >>>>>> -rw-r--r-- root     root        12692 1970-01-01 00:02 init.rc
>>> > >>>>>> dr-xr-xr-x root     root              1970-01-01 00:00 proc
>>> > >>>>>> drwxr-xr-x root     root              2010-01-19 02:18 sbin
>>> > >>>>>> drwxr-xr-x root     root              1970-01-01 00:00 sys
>>> > >>>>>> drwxr-xr-x root     root              2010-01-19 02:18 system
>>> > >>>>>> lrwxrwxrwx root     root              1970-01-01 00:01 d ->
>>> > >>>>>> /sys/kernel/debug
>>> > >>>>>> d--------- system   system            1970-01-01 00:01 sdcard
>>> > >>>>>> drwxrwx--- system   cache             1970-01-01 00:01 cache
>>> > >>>>>> dr-x------ root     root              1970-01-01 00:01 config
>>> > >>>>>> drwxrwxrwt root     root              1970-01-01 00:09
>>> > >>>>>> sqlite_stmt_journals
>>> >
>>> > >>>>>> *# ls -l /data*
>>> > >>>>>> drwxr-x--- root     log               1970-01-01 00:01 dontpanic
>>> > >>>>>> drwxrwx--t system   misc              1970-01-01 00:01 misc
>>> > >>>>>> drwxrwx--x shell    shell             1970-01-01 00:01 local
>>> > >>>>>> drwxrwx--x system   system            1970-01-01 00:08 data
>>> > >>>>>> drwxrwx--x system   system            1970-01-01 00:01
>>> app-private
>>> > >>>>>> drwxrwx--x system   system            1970-01-01 00:01 app
>>> > >>>>>> drwx------ root     root              1970-01-01 00:01 property
>>> > >>>>>> drwxrwx--x system   system            1970-01-01 00:14
>>> dalvik-cache
>>> > >>>>>> drwxrwx--- root     root              1970-01-01 00:01
>>> lost+found
>>> > >>>>>> drwxr-xr-x system   system            1970-01-01 00:02
>>> tombstones
>>> > >>>>>> drwxrwx--x system   system            1970-01-01 00:06 anr
>>> > >>>>>> drwxrwxr-x system   system            1970-01-01 00:14 system
>>> > >>>>>> drwx------ system   system            1970-01-01 00:08 backup
>>> >
>>> > >>>>>> *# ls -l /data/misc*
>>> > >>>>>> drwxrwx--- bluetooth bluetooth          1970-01-01 00:01
>>> bluetoothd
>>> > >>>>>> drwx------ keystore keystore          1970-01-01 00:01 keystore
>>> > >>>>>> drwxrwx--- system   system            1970-01-01 00:01 vpn
>>> > >>>>>> drwxrwxrwx wifi     wifi              1970-01-01 00:01 wifi
>>> >
>>> > >>>>>> On Tue, Jan 19, 2010 at 6:42 PM, ZhangJieJing 
>>> > >>>>>> <kzj...@gmail.com>wrote:
>>>
>>>
>>> >
>>> > >>>>>>> how you mount your /data dir?
>>> >
>>> > >>>>>>> what is outputs?
>>> > >>>>>>> # ls -l /data
>>> > >>>>>>> # ls -l /data/misc/
>>> >
>>> > >>>>>>> ---
>>> > >>>>>>> Best regards,
>>> > >>>>>>> Zhang Jiejing
>>> >
>>> > >>>>>>> On Tue, Jan 19, 2010 at 1:53 PM, linux newbie <
>>>  > >>>>>>> linux.newbi...@gmail.com> wrote:
>>> >
>>> > >>>>>>>> ls -l /data/misc/wifi/wpa_supplicant *is empty*
>>> >
>>> > >>>>>>>> # mount
>>> > >>>>>>>> rootfs / rootfs rw 0 0
>>> > >>>>>>>> /dev/root / jffs2 rw 0 0
>>> > >>>>>>>> none /proc proc rw 0 0
>>> > >>>>>>>> none /proc/bus/usb usbfs rw 0 0
>>> > >>>>>>>> none /dev/pts devpts rw,mode=600 0 0
>>> > >>>>>>>> tmpfs /dev/shm tmpfs rw 0 0
>>> > >>>>>>>> tmpfs /tmp tmpfs rw 0 0
>>> > >>>>>>>> /dev/sda1 / ext2 rw,errors=continue 0 0
>>> > >>>>>>>> tmpfs /dev tmpfs rw,mode=755 0 0
>>> > >>>>>>>> devpts /dev/pts devpts rw,mode=600 0 0
>>> > >>>>>>>> proc /proc proc rw 0 0
>>> > >>>>>>>> sysfs /sys sysfs rw 0 0
>>> > >>>>>>>> tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
>>> >
>>> > >>>>>>>> On Tue, Jan 19, 2010 at 3:30 PM, ZhangJieJing <
>>> kzj...@gmail.com>wrote:
>>>
>>> >
>>> > >>>>>>>>> can you mail output of
>>> >
>>> > >>>>>>>>> # ls -l /data/misc/wifi/wpa_supplicant
>>> > >>>>>>>>> # mount
>>> >
>>> > >>>>>>>>> ---
>>> > >>>>>>>>> Best regards,
>>> > >>>>>>>>> Zhang Jiejing
>>> >
>>> > >>>>>>>>>   On Tue, Jan 19, 2010 at 5:36 AM, linux newbie <
>>>  > >>>>>>>>> linux.newbi...@gmail.com> wrote:
>>> >
>>> > >>>>>>>>>>  Any suggestions?
>>> >
>>> > >>>>>>>>>> On Mon, Jan 18, 2010 at 6:26 PM, linux newbie <
>>>  > >>>>>>>>>> linux.newbi...@gmail.com> wrote:
>>> >
>>> > >>>>>>>>>>> Hi,
>>> >
>>> > >>>>>>>>>>> I build the system for "generic" product and booted our
>>> target
>>> > >>>>>>>>>>> with wpa_supplicant.
>>> >
>>> > >>>>>>>>>>> On the Android command prompt, If I enable wpa_supplicant,
>>> it
>>> > >>>>>>>>>>> says following error
>>> > >>>>>>>>>>> *chown[ctrl_interface]: Operation not permitted*
>>> > >>>>>>>>>>> **
>>> > >>>>>>>>>>> ctrl_interface=/data/misc/wifi/wpa_supplicant is set in
>>> > >>>>>>>>>>> wpa_supplicant.conf file and the folder is created in
>>> init.rc file
>>> >
>>> > >>>>>>>>>>> Can anyone let me know, how to overcome this issue?
>>> >
>>> > >>>>>>>>>>> Thanks
>>> >
>>> > >>>>>>>>>> --
>>> > >>>>>>>>>> unsubscribe: 
>>> > >>>>>>>>>> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
>>> <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com>>
>>>
>>>
>>> > >>>>>>>>>> website:http://groups.google.com/group/android-porting
>>> >
>>> > >>>>>>>>> --
>>> > >>>>>>>>> unsubscribe: 
>>> > >>>>>>>>> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
>>> <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com>>
>>>
>>>
>>> > >>>>>>>>> website:http://groups.google.com/group/android-porting
>>> >
>>> > >>>> --
>>> > >>>> unsubscribe: 
>>> > >>>> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
>>> <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com>>
>>>
>>>
>>> > >>>> website:http://groups.google.com/group/android-porting
>>> >
>>> > >>> --
>>> > >>> unsubscribe: 
>>> > >>> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
>>> <android-porting%2bunsubscr...@googlegroups.com<android-porting%252bunsubscr...@googlegroups.com>>
>>>
>>>
>>>  > >>> website:http://groups.google.com/group/android-porting
>>>
>>
>> --
>> unsubscribe: 
>> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
>> website: http://groups.google.com/group/android-porting
>>
>
> --
> unsubscribe: 
> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
> website: http://groups.google.com/group/android-porting
>

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to