Hi! I'm trying to construct myself a small rootfs that would boot up and connect to my (open) WLAN. For this I'd very much like to avoid any unneccesary and/or closed bits, so I thought no prob, I'll just install wireless-tools there and put few commands to my bootup script.
Alas, things didn't go that easily. For whatever reason, the wlan0 interface (although seemingly up & running) refuses to take on the essid I set with iwconfig, or any other command I try. When I boot to the ITOS, the wireless-tools commands seem to work like they should. So, the question is, is there some special setup needed for the wlan0 to come to life or do I really need to bring in the likes of wlancond (whatever it's role in this might be)? What I'm seeing in dmesg is the following line: <4>[ 11.625122] sm_drv_transmit: sm_frame_tx returned error -9 reported multiple times, but I guess this could be just the dhclient trying to talk over non-connected interface. Any hints? -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
