View Single Post
Posts: 7 | Thanked: 3 times | Joined on Aug 2008
#3
Thank you very much for your quick reply - I am new to Maemo and did not know about the repository. The source works perfectly, I can recompile the module without any errors and can insert it and everything works fine.
OK, so now I did the next step and patched it for the wireless extensions and that also worked. I recompiled wpa_supplicant for Diablo and voila - I can log into our network! Now everything works nicely - on the command-line. I can ssh into our machines here and so forth, but once I start a gui application, everything falls apart. The gui does not realize that I am connected and scans for APs, breaking my own connection in the process. I know about the Dummy-IAPs and tried the gconftool trick mentioned in the wiki, but had no success under Diablo (it worked for me under Chinook). I can see the DEFAULT connection in the connetivity settings / connection dialog, but not in the select connection box. Any idea how I can get the last step to work?

EDIT:
OK, this seems to be a known bug in Diablo, see also https://bugs.maemo.org/show_bug.cgi?id=3306
I found the following workaround with the ad-hoc network:
http://www.internettablettalk.com/wi...667&oldid=2662
which makes my wpa_supplicant solution now fully functional at least for our network here :-)

Last edited by atarixl; 2008-08-15 at 00:24.
 

The Following User Says Thank You to atarixl For This Useful Post: