Unable to load Wi-Fi driver

by linux newbie » Tue, 19 Jan 2010 08:19:36 GMT

Sponsored Links

I downloaded the Android source, compiled for "generic" product (with
Wpa_supplicant) and booted it on our target hardware.

I modified the default init.rc to include wpa_supplicant service.
service wpa_supplicant -D wext -i eth1 -c /system/etc/wpasup.conf

When the system booted, it can able to Associate with Access Point (verified
by looking into the log file of the Access Point).


Apart from above mentioned changes in init.rc, do I need to make further
modifications? If Yes, is there any documentation that explains the steps.


Unable to load Wi-Fi driver

by linux newbie » Tue, 19 Jan 2010 09:54:37 GMT

 In my wpasup.conf file, I didnt set ctrl_interface.

If I set ctrl_interface = /data/misc/wifi/wpa_supplicant, wpa_supplicant
throws *chown[ctrl_interface]: Operation not permitted *error.



Sponsored Links

Other Threads

1. android: building for dream fails

I followed the instructions at 
and the build failed with the following error:

make: *** No rule to make target `vendor/htc/dream/proprietary/akmd',
needed by`out/target/product/dream/system/bin/akmd'.  Stop.

Is something broken or did I miss a step?

Ultimately, I'm trying to determine how to add another vendor's target
into the android build system and was trying to use the dream build as
an example.  Is there documentation regarding how to properly add
another vendor's target to the build system, or might an android team
member be able to shed some light on the proper way to achieve this?


unsubscribe: android-porting+unsubscr...@googlegroups.com

2. About the libhardware and overlay hardware interface.

The hardware interface is continue changeing in cupcake branch.

The hardware overlay interface has some changes now .


Sample Code :

# The main change list:
1.  overlay_device are separated as overlay_control_device and
2.  Data path : remove the  swapBuffers , getOffset and  getMemory
                         Add the dequeueBuffer and overlay_buffer_t !

The old interface  is designed for using for pmem, which is like a fb

The new interface is more nature for using v4l2 output driver.

Do it mean v4l2 output driver will be the common item for Android ?


3. How to create blur surface from android.view.Surface?

4. Unique ID for contacts?

5. How to make OpenGL ES hw accelerator device node.

6. Not allowing horizontal spacing between grid view item

7. Not allowing horizontal spacing between grid view item