With latest karmic, this is what I see with modem-manager and networkmanager in debug mode, and with usbserial modprobed with proper vendor and product IDs:
The probing seems to last forever since modem-manager tries to probe ttyUSB[1-3] which don't respond. ttyUSB0 responds immediately as can be seen. It takes nearly 5 min for ttyUSB0 to be recognised as a CDMA modem and exported. NetworkManager still refuses to enlist this modem:
naveen@naveen-desktop:~$ sudo NetworkManager --no-daemon
NetworkManager: <info> starting...
NetworkManager: <info> modem-manager is now available
NetworkManager: SCPlugin-Ifupdown: init!
NetworkManager: SCPlugin-Ifupdown: update_system_hostname
NetworkManager: SCPluginIfupdown: management mode: unmanaged
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1e.0/0000:02:05.0/net/eth0, iface: eth0)
NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1e.0/0000:02:05.0/net/eth0, iface: eth0): no exported connection
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no exported connection
NetworkManager: SCPlugin-Ifupdown: end _init.
NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
NetworkManager: <info> Wireless now enabled by radio killswitch
NetworkManager: SCPlugin-Ifupdown: (140234016) ... get_connections.
NetworkManager: SCPlugin-Ifupdown: (140234016) ... get_connections (managed=false): return empty list.
NetworkManager: Ifupdown: get unmanaged devices count: 0
NetworkManager: <info> (eth0): new Ethernet device (driver: 'skge')
NetworkManager: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
NetworkManager: <info> (eth0): now managed
NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2)
NetworkManager: <info> (eth0): bringing up device.
NetworkManager: <info> (eth0): preparing device.
NetworkManager: <info> (eth0): deactivating device (reason: 2).
NetworkManager: Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:1e.0/0000:02:05.0/net/eth0
NetworkManager: <WARN> default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
NetworkManager: Could not get device: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Note the last message there - that seems to coincide with the cdma modem being exported by modem-manager.
So, two issues to resolve:
- modem-manager probing un-needed ports and timing out
- NetworkManager throwing an error that's not quiet useful to figure out whats happening.
With latest karmic, this is what I see with modem-manager and networkmanager in debug mode, and with usbserial modprobed with proper vendor and product IDs:
naveen@ naveen- desktop: ~$ sudo /usr/sbin/ modem-manager --debug manager: 4969): DEBUG: (ttyUSB2): probe requested by plugin 'ZTE' manager: 4969): DEBUG: (ttyUSB1): probe requested by plugin 'ZTE' manager: 4969): DEBUG: (ttyUSB0): probe requested by plugin 'ZTE' manager: 4969): DEBUG: (ttyUSB3): probe requested by plugin 'ZTE' manager: 4969): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>' manager: 4969): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>' manager: 4969): DEBUG: (ttyUSB0): --> 'AT+GCAP<CR>' manager: 4969): DEBUG: (ttyUSB3): --> 'AT+GCAP<CR>' manager: 4969): DEBUG: (ttyUSB0): <-- 'AT+GCAP< CR><CR> <LF>+GCAP: +CIS707-A, CIS-856, +MS, +ES, +DS, +FCLASS< CR><LF> <CR><LF> OK<CR>< LF>' manager: 4969): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>' manager: 4969): DEBUG: (ttyUSB2): --> 'AT+GCAP<CR>' pci0000: 00/0000: 00:1d.3/ usb5/5- 1 claimed port ttyUSB0 manager: 4969): DEBUG: Added modem /sys/devices/ pci0000: 00/0000: 00:1d.3/ usb5/5- 1 manager: 4969): DEBUG: Exported modem /sys/devices/ pci0000: 00/0000: 00:1d.3/ usb5/5- 1 as /org/freedeskto p/ModemManager/ Modems/ 0 manager: 4969): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>' manager: 4969): DEBUG: (ttyUSB3): --> 'AT+GCAP<CR>' manager: 4969): DEBUG: (ttyUSB2): --> 'ATI<CR>' manager: 4969): DEBUG: (ttyUSB1): --> 'AT+GCAP<CR>' manager: 4969): DEBUG: (ttyUSB3): --> 'AT+GCAP<CR>'
** Message: Loaded plugin Option
** Message: Loaded plugin Huawei
** Message: Loaded plugin Generic
** Message: Loaded plugin Option High-Speed
** Message: Loaded plugin MotoC
** Message: Loaded plugin Sierra
** Message: Loaded plugin Novatel
** Message: Loaded plugin Gobi
** Message: Loaded plugin ZTE
** Message: Loaded plugin Nokia
** Message: Loaded plugin Ericsson MBM
** Message: (ttyUSB2) opening serial device...
** (modem-
** Message: (ttyUSB1) opening serial device...
** (modem-
** Message: (ttyUSB0) opening serial device...
** (modem-
** Message: (ttyUSB3) opening serial device...
** (modem-
** (modem-
** (modem-
** (modem-
** (modem-
** (modem-
** (modem-
** Message: (ttyUSB0) closing serial device...
** (modem-
** Message: (ZTE): CDMA modem /sys/devices/
** (modem-
** (modem-
** (modem-
** (modem-
** (modem-
** Message: (ttyUSB2) closing serial device...
** (modem-
** (modem-
** Message: (ttyUSB1) closing serial device...
** Message: (ttyUSB3) closing serial device...
The probing seems to last forever since modem-manager tries to probe ttyUSB[1-3] which don't respond. ttyUSB0 responds immediately as can be seen. It takes nearly 5 min for ttyUSB0 to be recognised as a CDMA modem and exported. NetworkManager still refuses to enlist this modem:
naveen@ naveen- desktop: ~$ sudo NetworkManager --no-daemon system_ hostname pci0000: 00/0000: 00:1e.0/ 0000:02: 05.0/net/ eth0, iface: eth0) pci0000: 00/0000: 00:1e.0/ 0000:02: 05.0/net/ eth0, iface: eth0): no exported connection virtual/ net/lo, iface: lo) virtual/ net/lo, iface: lo): no exported connection p/NetworkManage r/Devices/ 0 pci0000: 00/0000: 00:1e.0/ 0000:02: 05.0/net/ eth0 adapter_ cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
NetworkManager: <info> starting...
NetworkManager: <info> modem-manager is now available
NetworkManager: SCPlugin-Ifupdown: init!
NetworkManager: SCPlugin-Ifupdown: update_
NetworkManager: SCPluginIfupdown: management mode: unmanaged
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/
NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/
NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/
NetworkManager: SCPlugin-Ifupdown: end _init.
NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
NetworkManager: <info> Wireless now enabled by radio killswitch
NetworkManager: SCPlugin-Ifupdown: (140234016) ... get_connections.
NetworkManager: SCPlugin-Ifupdown: (140234016) ... get_connections (managed=false): return empty list.
NetworkManager: Ifupdown: get unmanaged devices count: 0
NetworkManager: <info> (eth0): new Ethernet device (driver: 'skge')
NetworkManager: <info> (eth0): exported as /org/freedeskto
NetworkManager: <info> (eth0): now managed
NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2)
NetworkManager: <info> (eth0): bringing up device.
NetworkManager: <info> (eth0): preparing device.
NetworkManager: <info> (eth0): deactivating device (reason: 2).
NetworkManager: Added default wired connection 'Auto eth0' for /sys/devices/
NetworkManager: <WARN> default_
NetworkManager: Could not get device: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Note the last message there - that seems to coincide with the cdma modem being exported by modem-manager.
So, two issues to resolve:
- modem-manager probing un-needed ports and timing out
- NetworkManager throwing an error that's not quiet useful to figure out whats happening.
- Naveen