Hello, On Mon, 25 Feb 2008 09:06:59 -0600 Harmon Seaver <[EMAIL PROTECTED]> wrote:
> Paul Sokolovsky wrote: > > Hello, > > > > On Sun, 24 Feb 2008 23:16:30 -0600 > > Harmon Seaver <[EMAIL PROTECTED]> wrote: > > > >> So I've got angstrom-x11-image installed on my h2200 and I'm > >> trying to get wifi working. I've got a Hawking prism2 card (worked > >> okay in familiar and windoze) and it loads the hostap drivers > >> alright, but never is able to get an ip because when it can't seem > >> to use WEP. Here's what I see in dmesg: > >> > >> <7>[ 2952.140000] ieee80211_crypt_wep: could not allocate crypto > >> API arc4 <4>[ 2952.150000] wlan0: could not initialize WEP: load > >> module hostap_crypt_wep.o > >> > >> And, of course, there is no such module. Or at least not with the > >> distro. Nor do I see one in the feed, or at least not in searching > >> the web package finder. > > > > That message is misleading, hostap_crypt_wep.o reference is leftover > > from dark times ;-). It complains about arc4, kernel-module-arc4 is > > being built for h2200, and should be in the feed. > > > > The reason it's not installed in the image is that h2200 doesn't > > have *builtin* WiFi, so some people will never use WiFi at all, and > > burdening image with WiFi stuff for everyone is not a good thing (at > > least that's Angstrom idea so far - to provide with the image only > > support for builtin hardware, anything else is ipkg away). > > > > Actually, something else must be wrong, because even though I > manually load the arc4 module (and then even tried *all* the modules > in the crypt directory), I still get the same message. I noticed also > in dmesg this: > > wifi0: defaulting to host-based encryption as a workaround for > firmware bug in Host AP mode WEP > <7>[38946.370000] wifi0: defaulting to bogus WDS frame as a workaround > for firmware bug in Host AP mode WDS > > Don't know if that helps. Also, if wifi isn't builtin -- why is > hostap there? 8-) Yes, as Marcin pointed out, all stuff for WiFi+WEP+WPA is included for devices with CF, my info was old. So yes, something else is wrong, and that wrong is in hostap driver. > Another thing I notice is that when I run ifconfig, I get this: > > wlan0 Link encap:Ethernet HWaddr 00:02:DD:30:57:81 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 B) TX bytes:6478 (6.3 KiB) > Interrupt:30 > > wlan0:ava Link encap:Ethernet HWaddr 00:02:DD:30:57:81 > inet addr:169.254.6.46 Bcast:169.254.255.255 > Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:30 > > > What is this "wlan0:ava" and where is that ip coming from? There > is no access point nearby with that name or ip range, and nothing > static in the /etc/network/interfaces like that. That's avahi's shadow device, created dynamically. Avahi is zeroconf implementation, Angstrom bundles it by default, even though we lack good manual section describing how to get most out of it. > > -- > Harmon Seaver -- Best regards, Paul mailto:[EMAIL PROTECTED] _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
