>== Clean up this page ==

I do not want to remove useful information, but I think there are two solutions worth remaining: ndiswrapper and the native driver. Maybe this page should take care about these two exclusively. Someone wanting to do this? Otherwise I'm doing a rewrite when I get some spare time in a few weeks. -- Svenska 10:04, 4 September 2009 (UTC)

---

Problem

I'm having some issues here with the ndiswrapper and wpa_supplicant. I'm using debian stock kernel 2.6.25.2 patched for a110. Everything seems fine so far. I get "disconnect" events in wpa_supplicant as son as I do dhcp or tcp stuff like surfing a webpage. If I just start wpa_supplicant and connect to the AP and do nothing, I stay connected. Anybody else with this problem? --Yorn 20:22, 6 June 2008 (UTC)

This problem occours not only with WPA here. I'm able to scan for networks, but at the moment I want to connect, the thing gets broken (forever in some configs). With ndiswrapper I'm able to connect to the net with the current Sidux kernel (2.6.25 or so, that should be very much like a slightly modified Debian-SID one). Most other kernels that I tried will not do it, even with a clean ndiswrapper installation. Btw. it is the same behaviour as with the native drivers for me - but when using ndiswrapper I was still able to scan networks after a failed connection, what was broken otherwise with the native drivers. --Helmar Wodtke 20:34, 6 June 2008 (UTC)

This is getting very intersting here... My problem seems to be the router, not my box. I'm actually killing the wireless interface of the router when I use anything with tcp stack. The problem is _not_ ndiswrapper and wpa_supplicant. I'd guess they work perfect (they did the whole day until now... btw.). I have trouble getting the other drivers to work. I can scan, but that's all (using this approach: http://www.a110wiki.de/wiki/Wireless#Port_for_2.6.25). I need a new router... ^^ --Yorn 22:51, 6 June 2008 (UTC)

One binary kernel notes

Non-wireless-related notes following the instructions here:

If you now reboot the A110, you will notice that both the SD slot and the wireless driver is working, however, there seems to be a bug in squashfs support, so you will probably be unable to mount usr.sqfs. This can be solved with usr on a seperate partition, however, this is not a very good approach to the problem, so compiling your own kernel is probably better.

The Binary Kernel from One uses an older squashfs support. When you want to "squash" a System that uses the one binary kernel you'll need to use squashfs-tools < 3.3. I used a version without lzma patch. And it works.

The one binary kernel has no unionfs support built in. But to make up with that theres aufs compiled into the kernel. Enabling aufs is the same as with unionfs. In fstab just exchange "unionfs" with "aufs" and all should work like its supposed to. --Mryoung 17:21, 4 June 2008 (UTC)

WPA2

I cannot connect with WPA2-personal password with builtin WLAN. But I can connect with a NETGEAR WLAN stick and same WPA2-personal. --Franka 14:20, 20 June 2008 (UTC)

wpa_supplicant

I'm using kernel 2.6.25.8 with card reader patch and the rtl8187b driver along with the patch as proposed here. However, I unfortunately can't get the wireless running; wpa_supplicant (the version shipped along with the driver) repeatable causes a full crash (complete freeze, "A"-led behind keyboard blinking). Logfiles do not contain any entries related to this..

As I'm not familiar with wpa_supplicant, I'd absolutely appreciate some more details on how exactly wireless is used with wpa_supplicant and maybe what else has to be considered to get this running (kernel configuration?). Thanks in advance!

Activate card

Help, please! I've tried for hours to get this thing to work!

How do I actually ACTIVATE the card?

I installed the ndiswrapper driver, but

• lshw says: network DISABLED ...
• ndiswrapper -l says: net8187b : driver installed device (0BDA:8189) present
• iwlist scan says: wlan0 no scan results
• the WLAN LED is blinking every 4 seconds
• fn-F2 show no effect
• the BIOS has no activate option (it has very little options at all)

Maybe something is damaged? I dropped it recently. -- Nichtich 20:06, 23 September 2009 (UTC)