AWEXT driver on ICS for older Wifi cards

[StefanS]

Dear developers,

I have resolved some issues that prevented older WiFi card like the intel 2200bg series from working on ICS. The problem is that this and possibly other drivers don't support the nl80211 interface from wpa_supplicant, and thus wpa_supplicant fails with "driver doesn't support association/authentication commands".
I then tried to use the old 0.6.x wpa_supplicant with awext (since awext is not yet ported to 0.8.x) which mostly worked with both new and old cards (tested with ipw2200 and ath9k), but it didn't show the connection in the status bar.

I have then backported the "STATUS_POLL" function into the 0.6.x awext driver, because ICS uses this to determine the link strength and subsequently shows it in the status bar.

So I would like to ask if I can commit this change to the wpa_supplicant_6 x86/ics-x86 tree. Since most devices will use the 0.8.x version, it will not affect them.

The only problem is that the wpa_supplicant service is defined in the init.rc, where the driver is hard coded. I have removed the "-Dnl80211" from the wpa_supplicant definition. I'm not sure if removing the "-D..." option completely will also work for the nl80211 driver, it does for the awext, that would be a very good solution.

Stefan
P.S.: Using the old wpa_supplicant is done by setting
> WPA_SUPPLICANT_VERSION := VER_0_6_X
> BOARD_WPA_SUPPLICANT_DRIVER := AWEXT
> BOARD_WPA_SUPPLICANT_PRIVATE_LIB :=
in BoardConfig.mk

[StefanS]

Ok, sorry, I did now test it and yes, the "-D..." argument to wpa_supplicant can be safely removed with both awext 0.6.x and nl80211 0.8.x drivers. I guess it's because always there's only one driver available, so wpa_supplicant uses it.

Stefan

[Christopher Hrabia]

Could you please provide a patch with your changes in wpa-supplicant 0.6? It seems I have the same problems.

Thank you!

2012/2/18 StefanS <and...@stefanseidel.info>

Ok, sorry, I did now test it and yes, the "-D..." argument to wpa_supplicant can be safely removed with both awext 0.6.x and nl80211 0.8.x drivers. I guess it's because always there's only one driver available, so wpa_supplicant uses it.

Stefan

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/tb8XkuTP-4UJ.

To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

--
Mit freundlichen Grüßen

Christopher Hrabia

(c.hr...@gmail.com)

[StefanS]

Yes, here it is attached. Apply in external/wpa_supplicant_6.

---
wpa_supplicant/ctrl_iface.c | 21 ++++++++++++++++++++
wpa_supplicant/src/drivers/driver.h | 18 +++++++++++++++++
wpa_supplicant/src/drivers/driver_awext.c | 30 +++++++++++++++++++++++++++++
wpa_supplicant/wpa_supplicant_i.h | 8 +++++++
4 files changed, 77 insertions(+), 0 deletions(-)
---

Stefan

[fuzzy7k]

Nice work, this is also needed for the current state of wl.ko.

One notice however, my network does not show up. Looking at the log,
it seems to scan and find my AP, but says "No suitable AP found." I
can connect to it if I choose add network and enter it manually.

D/wpa_supplicant( 1133): Received 171 bytes of scan results (1 BSSes)
D/wpa_supplicant( 1133): New scan results available
D/wpa_supplicant( 1133): No suitable AP found.

I double checked to make sure the SSID was being broadcast, and it is.
I was wondering if anyone else is seeing this?

Thanks,
Kyle

On Feb 19, 8:08 am, StefanS <andr...@stefanseidel.info> wrote:
> Yes, here it is attached. Apply in external/wpa_supplicant_6.
>
> ---
>  wpa_supplicant/ctrl_iface.c               |   21 ++++++++++++++++++++
>  wpa_supplicant/src/drivers/driver.h       |   18 +++++++++++++++++
>  wpa_supplicant/src/drivers/driver_awext.c |   30 +++++++++++++++++++++++++++++
>  wpa_supplicant/wpa_supplicant_i.h         |    8 +++++++
>  4 files changed, 77 insertions(+), 0 deletions(-)
> ---
>
> Stefan
>

> On Sun, Feb 19, 2012 at 09:06, Christopher Hrabia <c.hra...@gmail.com> wrote:
> > Could you please provide a patch with your changes in wpa-supplicant 0.6? It
> > seems I have the same problems.
>
> > Thank you!
>

> > 2012/2/18 StefanS <andr...@stefanseidel.info>

>
> >> Ok, sorry, I did now test it and yes, the "-D..." argument to
> >> wpa_supplicant can be safely removed with both awext 0.6.x and nl80211 0.8.x
> >> drivers. I guess it's because always there's only one driver available, so
> >> wpa_supplicant uses it.
>
> >> Stefan
>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Android-x86" group.
> >> To view this discussion on the web visit
> >>https://groups.google.com/d/msg/android-x86/-/tb8XkuTP-4UJ.
>
> >> To post to this group, send email to andro...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> android-x86...@googlegroups.com.
> >> For more options, visit this group at
> >>http://groups.google.com/group/android-x86?hl=en.
>
> > --
> > Mit freundlichen Grüßen
> > Christopher Hrabia

> > (c.hra...@gmail.com)

>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Android-x86" group.
> > To post to this group, send email to andro...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > android-x86...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/android-x86?hl=en.
>
>
>

>  wpa6.diff
> 6KViewDownload

[Chih-Wei Huang]

Nice work.
Yes, please push it.

2012/2/19 StefanS <and...@stefanseidel.info>:

Probably.
Indeed hardcoding wpa driver is not good.
I'm considering add a property for it
to make it configurable.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[StefanS]

On Monday, February 20, 2012 7:13:49 AM UTC+1, Chih-Wei Huang wrote:

Nice work.
Yes, please push it.

It's in the repo now.
 

2012/2/19 StefanS <and...@stefanseidel.info>:
> Ok, sorry, I did now test it and yes, the "-D..." argument to wpa_supplicant
> can be safely removed with both awext 0.6.x and nl80211 0.8.x drivers. I
> guess it's because always there's only one driver available, so
> wpa_supplicant uses it.

Probably.
Indeed hardcoding wpa driver is not good.
I'm considering add a property for it
to make it configurable.

If I saw it correctly, then in the current build situation there is  no possibility of defining two wpa_supplicant drivers, so wouldn't it be the easiest to just remove the driver from the service and let wpa_supplicant choose for itself?

Stefan

[Chih-Wei Huang]

2012/2/20 StefanS <and...@stefanseidel.info>:

>> Probably.
>> Indeed hardcoding wpa driver is not good.
>> I'm considering add a property for it
>> to make it configurable.
>
> If I saw it correctly, then in the current build situation there is  no
> possibility of defining two wpa_supplicant drivers, so wouldn't it be the
> easiest to just remove the driver from the service and let wpa_supplicant
> choose for itself?

Hmm, sounds good.
Let me verify it.

[Christopher Hrabia]

@ Stefan

Is it also necessary to make some changes in init.rc to get version 6 working in ics? Or how looks your init.rc for wpa_supplicant?

2012/2/20 Chih-Wei Huang <cwh...@android-x86.org>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

--
Mit freundlichen Grüßen

Christopher Hrabia

(c.hr...@gmail.com)

[StefanS]

The current version of init.rc already has the -Dnl80211 entry
removed, so if you are in sync with the repo, there's nothing to be
done.

Currently there's a minor bug that if no networks are configured then
the initial scan for networks fails with some cards. If you add a
bogus network then it works fine. I'm investigating.

Stefan

[Chih-Wei Huang]

2012/2/24 Christopher Hrabia <c.hr...@gmail.com>:

> @ Stefan
>
> Is it also necessary to make some changes in init.rc to get version 6
> working in ics? Or how looks your init.rc for wpa_supplicant?

I've changed that as StefanS suggested.
That is, just remove the -D option.

[Christopher Hrabia]

Ok thanks, I will try!

2012/2/24 Chih-Wei Huang <cwh...@android-x86.org>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Christopher Hrabia]

so I have tested it and it works like you described it after adding some fake network first. But I detected that the new driver from 0_8 works either after I corrected some mistake in my kernel configuration.

But I will do some further testing to get out which version works better.

2012/2/24 Christopher Hrabia <c.hr...@gmail.com>

[StefanS]

On Mon, Feb 27, 2012 at 18:25, Christopher Hrabia <c.hr...@gmail.com> wrote:
> so I have tested it and it works like you described it after adding some
> fake network first. But I detected that the new driver from 0_8 works either
> after I corrected some mistake in my kernel configuration.

Yes, if your driver supports lib80211 then it's fine. Some wireless
drivers however don't support it, that's why they need the wext/awext
wpa_supplicant. One could update the kernel drivers to support
lib80211, but that's too much for me :)

> But I will do some further testing to get out which version works better.

In general, if 0.8 works, go for it. I think many options like
powersave mode etc. do not work in the old driver, afaik only the
basic features are implemented and 0.8 added lots of new features as
well.

Stefan

[Christopher Hrabia]

Ok Stefan,

Thanks for the advice!

2012/2/27 StefanS <and...@stefanseidel.info>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

2012/2/20 fuzzy7k <kva...@gmail.com>:

> Nice work, this is also needed for the current state of wl.ko.
> One notice however, my network does not show up. Looking at the log,
> it seems to scan and find my AP, but says "No suitable AP found." I
> can connect to it if I choose add network and enter it manually.
>
>  D/wpa_supplicant( 1133): Received 171 bytes of scan results (1 BSSes)
>  D/wpa_supplicant( 1133): New scan results available
>  D/wpa_supplicant( 1133): No suitable AP found.
>
> I double checked to make sure the SSID was being broadcast, and it is.
> I was wondering if anyone else is seeing this?

Hmm, I'm trying wpa_supplicant_6 and found the same issue.
Any progress?

[StefanS]

Haven't found anything yet, quite hard to analyze. Does it work for you if you add a network (any network will do)?

Stefan
>
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.

[Chih-Wei Huang]

2012/3/6 StefanS <and...@stefanseidel.info>:

> On Mar 5, 2012 5:33 PM, "Chih-Wei Huang" <cwh...@android-x86.org> wrote:
>> Hmm, I'm trying wpa_supplicant_6 and found the same issue.
>> Any progress?
>
> Haven't found anything yet, quite hard to analyze. Does it work for you if
> you add a network (any network will do)?

Ah, indeed. After creating a dummy ap, it can scan normally.
Interesting...

[StefanS]

On Mar 7, 2012 5:24 PM, "Chih-Wei Huang" <cwh...@android-x86.org> wrote:
>
> 2012/3/6 StefanS <and...@stefanseidel.info>:
> > On Mar 5, 2012 5:33 PM, "Chih-Wei Huang" <cwh...@android-x86.org> wrote:
> >> Hmm, I'm trying wpa_supplicant_6 and found the same issue.
> >> Any progress?
> >
> > Haven't found anything yet, quite hard to analyze. Does it work for you if
> > you add a network (any network will do)?
>
> Ah, indeed. After creating a dummy ap, it can scan normally.
> Interesting...

Ok good to know you have the same issue. It's easier to hunt one phantom than two :)

Stefan

>
> --
> Chih-Wei
> Android-x86 project
> http://www.android-x86.org
>

[jay sam nuel hechanova]

i found this link http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide#Driver_Configuration and i tried the instruction there on how to get WiFi worked in a custom Android build but cannot finished the build because of this error make: *** No rule to make target `out/target/product/generic_x86/obj/STATIC_LIBRARIES/lib_driver_cmd_wl12xx_intermediates/lib_driver_cmd_wl12xx.a', needed by `out/target/product/generic_x86/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant'. Stop.

please any help on this.

[ward...@gmail.com]

How do I use this wpa6.diff file? I have a SONY VAIO laptop that the WIFI doesnt work it uses the same Intel 2200 chip. How do I use this file to get the WIFI to work?