Re: Connman-0.67 Crashes and/or Hangs on Start-up
On 1/30/11 2:46 PM, Samuel Ortiz wrote: > On Sun, Jan 30, 2011 at 01:37:30PM -0800, Grant Erickson wrote: >> The requested log output is as follows. It would seem that the wifi.so >> plug-in and the wpa_supplicant are not even communicating: > > Correct. > >> # /sbin/wpa_supplicant -ddd -t -u & >> 1296422968.146540: Providing DBus service 'fi.epitest.hostap.WPASupplicant'. > > Your wpa_supplicant is built to only provide the legacy D-Bus interface, which > is why the wifi.so plugin doesn't talk to it. > > I don't know if you build your wpa_supplicant yourself, but you can build it > so that it supports both interfaces. (which is why I was asking for your > wpa_supplicant .config file, i.e. the build config file wpa_supplicant uses). Thanks for the clarification on which '.config' file was intended. I do build wpa_supplicant from source, the .config for which is: DBUS_INCLUDE := $(DBUSCFLAGS) DBUS_LIBS := $(DBUSLDFLAGS) DBUS_VERSION := $(DBUSVERSION) CFLAGS += $(OPENSSLCFLAGS) $(NETLINKCFLAGS) $(LINUXCFLAGS) wpa_supplicant: LIBS += $(DBUSLDFLAGS) $(OPENSSLLDFLAGS) $(NETLINKLDFLAGS) wpa_passphrase: LDFLAGS += $(OPENSSLLDFLAGS) CONFIG_DRIVER_WEXT=y CONFIG_DRIVER_NL80211=y CONFIG_DRIVER_WIRED=y CONFIG_LIBNL20=y CONFIG_IEEE8021X_EAPOL=y CONFIG_EAP_MD5=y CONFIG_EAP_MSCHAPV2=y CONFIG_EAP_TLS=y CONFIG_EAP_PEAP=y CONFIG_EAP_TTLS=y CONFIG_EAP_GTC=y CONFIG_EAP_OTP=y CONFIG_EAP_LEAP=y CONFIG_PKCS12=y CONFIG_CTRL_IFACE=y CONFIG_DEBUG_SYSLOG=y CONFIG_BACKEND=file CONFIG_PEERKEY=y CONFIG_CTRL_IFACE_DBUS=y CONFIG_DEBUG_FILE=y When last I'd tried setting CONFIG_CTRL_IFACE_DBUS_NEW=y around the connman-0.63 time frame, it caused wpa_supplicant to segment fault so I turned it off as it didn't seem necessary. I'll give it another go with connman-0.68 and the non-legacy wifi.so and see what happens. Thanks for the tip. Would it make sense, from a debugging perspective, to have the Wi-Fi plug-in emit some log message if it cannot find the new D-Bus interface? Best, Grant ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Connman-0.67 Crashes and/or Hangs on Start-up
Hi Grant, On Sun, Jan 30, 2011 at 01:37:30PM -0800, Grant Erickson wrote: > The requested log output is as follows. It would seem that the wifi.so > plug-in and the wpa_supplicant are not even communicating: Correct. > # /sbin/wpa_supplicant -ddd -t -u & > 1296422968.146540: Providing DBus service 'fi.epitest.hostap.WPASupplicant'. Your wpa_supplicant is built to only provide the legacy D-Bus interface, which is why the wifi.so plugin doesn't talk to it. I don't know if you build your wpa_supplicant yourself, but you can build it so that it supports both interfaces. (which is why I was asking for your wpa_supplicant .config file, i.e. the build config file wpa_supplicant uses). Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Connman-0.67 Crashes and/or Hangs on Start-up
On 1/28/11 4:51 PM, Samuel Ortiz wrote: > On Fri, Jan 28, 2011 at 02:52:36PM -0800, Grant Erickson wrote: >> With the wired Ethernet issue debugged and patched, I've done more >> investigation on the wireless issue. The results are as follows: >> >> -- >> Version / Plugin wifi.so wifi_legacy.so >> == >> connman-0.67 FAILS SUCCEEDS >> -- >> connman-b1db3cb FAILS N/A >> == >> >> So, it would appear that the non-legacy wifi plugin has issues with wireless >> extension devices. >> > I'm testing this with my iwlagn chipset forced to run in wext mode only and > that seems to work fine. > > Would you mind sharing the output of wpa_supplicant -ddd -t -u when running > connmand on top of it ? Also could you please show us what your wpa_supplicant > .config look like ? Samuel: As promised, the contents of /etc/wpa_supplicant.conf file is, as expected, empty. The contents of /etc/dbus-1/system.d/wpa_supplicant.conf is: http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> The requested log output is as follows. It would seem that the wifi.so plug-in and the wpa_supplicant are not even communicating: # /sbin/wpa_supplicant -ddd -t -u & 1296422968.146540: Providing DBus service 'fi.epitest.hostap.WPASupplicant'. # /usr/sbin/connmand -n -d connmand[303]: Connection Manager version 0.67 connmand[303]: connman-0.67/src/storage.c:__connman_storage_init() connmand[303]: connman-0.67/src/element.c:__connman_element_init() connmand[303]: connman-0.67/src/element.c:connman_element_create() element 0x5cfd0 connmand[303]: connman-0.67/src/element.c:__connman_element_initialize() element 0x5cfd0 connmand[303]: connman-0.67/src/technology.c:__connman_technology_init() connmand[303]: connman-0.67/src/notifier.c:__connman_notifier_init() connmand[303]: connman-0.67/src/service.c:__connman_service_init() connmand[303]: connman-0.67/src/storage.c:connman_storage_register() storage 0x53ff8 name service connmand[303]: connman-0.67/src/provider.c:__connman_provider_init() connmand[303]: connman-0.67/src/notifier.c:connman_notifier_register() notifier 0x5412c name provider connmand[303]: connman-0.67/src/network.c:__connman_network_init() connmand[303]: connman-0.67/src/element.c:connman_driver_register() driver 0x53ca0 name network connmand[303]: connman-0.67/src/device.c:__connman_device_init() connmand[303]: connman-0.67/src/storage.c:connman_storage_register() storage 0x53c74 name device connmand[303]: connman-0.67/src/element.c:connman_driver_register() driver 0x53c58 name device connmand[303]: connman-0.67/src/agent.c:__connman_agent_init() connmand[303]: connman-0.67/src/iptables.c:__connman_iptables_init() connmand[303]: connman-0.67/src/tethering.c:__connman_tethering_init() connmand[303]: connman-0.67/src/counter.c:__connman_counter_init() connmand[303]: connman-0.67/src/notifier.c:connman_notifier_register() notifier 0x5423c name ondemand connmand[303]: connman-0.67/src/manager.c:__connman_manager_init() connmand[303]: connman-0.67/src/notifier.c:connman_notifier_register() notifier 0x53cf0 name manager connmand[303]: connman-0.67/src/profile.c:__connman_profile_init() connmand[303]: connman-0.67/src/storage.c:connman_storage_register() storage 0x53f6c name profile connmand[303]: connman-0.67/src/config.c:__connman_config_init() connmand[303]: connman-0.67/src/config.c:read_configs() connmand[303]: connman-0.67/src/stats.c:__connman_stats_init() connmand[303]: connman-0.67/src/resolver.c:__connman_resolver_init() connmand[303]: connman-0.67/src/resolver.c:connman_resolver_register() resolver 0x54144 name resolvfile connmand[303]: connman-0.67/src/ipconfig.c:__connman_ipconfig_init() connmand[303]: connman-0.67/src/rtnl.c:__connman_rtnl_init() connmand[303]: connman-0.67/src/task.c:__connman_task_init() connmand[303]: connman-0.67/src/proxy.c:__connman_proxy_init() connmand[303]: connman-0.67/src/detect.c:__connman_detect_init() connmand[303]: connman-0.67/src/rtnl.c:connman_rtnl_register() rtnl 0x54158 name detect connmand[303]: connman-0.67/src/session.c:__connman_session_init() connmand[303]: connman-0.67/src/timeserver.c:__connman_timeserver_init() connmand[303]: connman-0.67/src/plugin.c:__connman_plugin_init() connmand[303]: Checking loopback interface settings connmand[303]: System hostname is salmon.local connmand[303]: System domainname is domain.actdsltmp connmand[303]: connman-0.67/src/utsname.c:connman_utsname_driver_register() driver 0x40390340 name loopback connmand[303]: connman-0.67/src/network.
Re: Connman-0.67 Crashes and/or Hangs on Start-up
On 1/30/11 1:52 AM, Kalle Valo wrote: > Grant Erickson writes: >> Between you and Samuel, it's good to hear that both the Atheros AR242x and >> Intel IWLAGN work well with 0.68/b1db3cb under wireless extensions with the >> non-legacy Wi-Fi plug-in. Would I be correct in assuming that both you and >> Samuel are using a Core iX or Atom platform? Against what kernel version are >> you running? >> >> In my case, it's linux-2.6.32, armv7l and TI WLAN 127x, their TIWLAN WiLink >> 6.1.0.2.144 driver and firmware 6.1.0.0.335. > > TI's WiLink driver might behave oddly and simply have bugs in it's wext > interface. I strongly recommend to use the proper upstream driver > wl12xx: > > http://linuxwireless.org/en/users/Drivers/wl12xx > > In the long run you will save a lot of trouble. For example, it will > work with wpasupplicant and connman out of box, thanks to mac80211 > stack. Out-of-tree drivers are always pain, avoid them like the plague. Kalle: Thanks for the link and recommendation. I am in 100% agreement with you on out-of-tree drivers and between connman and power management, I've first-hand experience that the proprietary driver has not been without issue. Best, Grant ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Connman-0.67 Crashes and/or Hangs on Start-up
Hi Grant, Grant Erickson writes: > Between you and Samuel, it's good to hear that both the Atheros AR242x and > Intel IWLAGN work well with 0.68/b1db3cb under wireless extensions with the > non-legacy Wi-Fi plug-in. Would I be correct in assuming that both you and > Samuel are using a Core iX or Atom platform? Against what kernel version are > you running? > > In my case, it's linux-2.6.32, armv7l and TI WLAN 127x, their TIWLAN WiLink > 6.1.0.2.144 driver and firmware 6.1.0.0.335. TI's WiLink driver might behave oddly and simply have bugs in it's wext interface. I strongly recommend to use the proper upstream driver wl12xx: http://linuxwireless.org/en/users/Drivers/wl12xx In the long run you will save a lot of trouble. For example, it will work with wpasupplicant and connman out of box, thanks to mac80211 stack. Out-of-tree drivers are always pain, avoid them like the plague. -- Kalle Valo ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
