Hi Tomasz, On Thu, Nov 04, 2010 at 11:25:30PM +0100, Tomasz Sterna wrote: > Dnia 2010-11-03, śro o godzinie 18:43 +0100, Samuel Ortiz pisze: > > > No matter when I load the module - ConnMan does not "see" this > > interface > > > at all. > > Could you please load the module, and then tell me what connmand -d -n > > tells ? > > [r...@localhost ~]# connmand -d -n > Name already in use > > After killing the running connman, but it brought down my usb > networking :) and I lost shell. BTW, why does ConnMan bring down the > interface set up manually by separate init.d script not by connmand? > > Anyway, after commenting out connman from rc.sysinit: > http://pastebin.com/D36yUNbE According to these logs: - Your eth0 device is detected, as a wifi one. - The supplicant plugin is started, but for some reasons the actual wpa_supplicant binary is not. - Since wpa_supplicant is not started, the ConnMan wifi device driver is not registered properly, which causes your wifi device to not be enabled.
So the problem is around wpa_supplicant not auto-starting on D-Bus introspection. Could you verify that your fi.epitest.hostap.WPASupplicant.service file is correctly installed, pointing at the right wpa_supplicant binary ? Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
