Re: Broadcom's proprietary wl driver detected as ethernet
Raghavendra. S raghavendra.akkas...@gmail.com writes: [Raghu]: I too met with this some time back. Assuming you enbled wifi during compilation, following was the issue in my case. When I killed connman. for some reason plugins directory (/usr/lib/connman/ plugins/*) was getting deleted. So next time when I started connman it started without throwing any error. Because of this connman detected wifi interface as ethernet interface and all wifi functionalities were disabled for the interface. So you better check once whether you have /usr/lib/connman/plugins/*. Otherwise reinstall and try. Thanks but this wasn't the issue because wifi was working with an usb stick using ar9170. -- Kalle Valo ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Broadcom's proprietary wl driver detected as ethernet
Hi Samuel, I noticed that with the latest connman git version Broadcom's proprietary wl driver is detected as an ethernet device, not a wifi device. This was working few weeks back and my main suspect is the udev removal. Could you please pull the latest ConnMan bits and check if it's working with the wl crap^Wdriver ? the wireless directory inside the network sysfs object can be not compiled in btw. Just some funny side notes here. However can you please add a big connman_error() in the code if the uevent DEVTYPE=wlan is missing and wireless directory is present. I wanna warn about this stupid binary only drivers. Regards Marcel ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Broadcom's proprietary wl driver detected as ethernet
Hi Marcel, On Fri, Oct 15, 2010 at 10:17:24AM +0300, Marcel Holtmann wrote: Hi Samuel, I noticed that with the latest connman git version Broadcom's proprietary wl driver is detected as an ethernet device, not a wifi device. This was working few weeks back and my main suspect is the udev removal. Could you please pull the latest ConnMan bits and check if it's working with the wl crap^Wdriver ? the wireless directory inside the network sysfs object can be not compiled in btw. Just some funny side notes here. Yes, I'm aware of that. If DEVTYPE is not set, I also thought about checking for SIOCGIWNAME in order to check for wext support. Would you prefer that solution ? Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Broadcom's proprietary wl driver detected as ethernet
Hi Samuel, I noticed that with the latest connman git version Broadcom's proprietary wl driver is detected as an ethernet device, not a wifi device. This was working few weeks back and my main suspect is the udev removal. Could you please pull the latest ConnMan bits and check if it's working with the wl crap^Wdriver ? the wireless directory inside the network sysfs object can be not compiled in btw. Just some funny side notes here. Yes, I'm aware of that. If DEVTYPE is not set, I also thought about checking for SIOCGIWNAME in order to check for wext support. Would you prefer that solution ? I am fine either way. I just want ConnMan complaining if wireless directory exists and no DEVTYPE. So we have an error in the logs. Regards Marcel ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Broadcom's proprietary wl driver detected as ethernet
Hi Kalle, On Thu, Oct 14, 2010 at 08:25:17PM +0300, Kalle Valo wrote: Hi, I noticed that with the latest connman git version Broadcom's proprietary wl driver is detected as an ethernet device, not a wifi device. This was working few weeks back and my main suspect is the udev removal. Could you please pull the latest ConnMan bits and check if it's working with the wl crap^Wdriver ? Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Broadcom's proprietary wl driver detected as ethernet
Hi, I noticed that with the latest connman git version Broadcom's proprietary wl driver is detected as an ethernet device, not a wifi device. This was working few weeks back and my main suspect is the udev removal. [Raghu]: I too met with this some time back. Assuming you enbled wifi during compilation, following was the issue in my case. When I killed connman. for some reason plugins directory (/usr/lib/connman/plugins/*) was getting deleted. So next time when I started connman it started without throwing any error. Because of this connman detected wifi interface as ethernet interface and all wifi functionalities were disabled for the interface. So you better check once whether you have /usr/lib/connman/plugins/*. Otherwise reinstall and try. -- Kalle Valo ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
