Bug 92345 - mmcli is not detecting my 4G dongle, ZTE device Vendor ID:: 19d2, Product ID: 1225
Summary: mmcli is not detecting my 4G dongle, ZTE device Vendor ID:: 19d2, Product ID...
Status: RESOLVED MOVED
Alias: None
Product: ModemManager
Classification: Unclassified
Component: mmcli (show other bugs)
Version: 1.4
Hardware: Other All
: medium normal
Assignee: ModemManager bug user
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-08 11:46 UTC by Rajasekhar
Modified: 2018-06-10 09:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
mmcli logs (101.93 KB, text/plain)
2015-10-08 11:46 UTC, Rajasekhar
Details
ModemManager debug logs (27.43 KB, text/plain)
2015-10-08 14:43 UTC, Rajasekhar
Details
ModemManager debug logs (30.79 KB, text/plain)
2015-10-09 09:27 UTC, Rajasekhar
Details

Description Rajasekhar 2015-10-08 11:46:37 UTC
Created attachment 118758 [details]
mmcli logs

mmcli is not detecting my 4G Dongle. 
Dongle:: ZTE device, Vendor ID:: 19d2,  Product ID: 1225 
Please find the entire logs file "mmcli_logs_8_oct" attachment. 

Log file contains the output of below commands.
1) uname -r
2) uname -a
3) dpkg -l | grep -e modemmanager -e network-manager -e uuid
4) ps -A | grep Manager
5) lsusb
6) cat /var/log/syslog
7) dmesg
8) ls -a1 /dev/ttyU*
9) ls  /dev/tty*
10) mmcli -L
11) mmcli -m 3
12) mmcli -m /org/freedesktop/NetworkManager/Devices/3
13) mmcli -S

Logs::
=======
root@lappc-HP-xw4600-Workstation:/home/lappc# mmcli -L

No modems were found

root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# mmcli -L

No modems were found

root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# mmcli -m 3
error: couldn't find modem at '/org/freedesktop/ModemManager1/Modem/3'
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# mmcli -m /org/freedesktop/NetworkManager/Devices/3
error: invalid path or index string specified: '/org/freedesktop/NetworkManager/Devices/3'
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# mmcli -S
successfully requested to scan devices
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# mmcli -L

No modems were found

root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# lsusb
Bus 002 Device 006: ID 19d2:1225 ZTE WCDMA Technologies MSM 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 008 Device 002: ID 17ef:6019 Lenovo 
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@lappc-HP-xw4600-Workstation:/home/lappc# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 008 Device 002: ID 17ef:6019 Lenovo 
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@lappc-HP-xw4600-Workstation:/home/lappc# lsusb
Bus 002 Device 007: ID 19d2:1403 ZTE WCDMA Technologies MSM 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 008 Device 002: ID 17ef:6019 Lenovo 
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@lappc-HP-xw4600-Workstation:/home/lappc# lsusb
Bus 002 Device 007: ID 19d2:1403 ZTE WCDMA Technologies MSM 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 008 Device 002: ID 17ef:6019 Lenovo 
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc#
Comment 1 Aleksander Morgado 2015-10-08 11:56:54 UTC
Looks like the modem is not getting modeswitched properly. Do you have usb-modeswitch installed?

Not sure if they will be useful, but if you want to get debug logs you should get them from the "ModemManager" program, not from mmcli, see:
http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
Comment 2 Rajasekhar 2015-10-08 14:42:47 UTC
Thanks Aleksander for quick reply.

Yes, usb-modeswitch is installed. Please check below output. Mode switching is happening. If you see the "lsusb" output the product ID has got changed from "1225" to "1403". Even in syslog output also usb_modeswitch is applied on the device.

After Dongle is inserted then the file "/org/freedesktop/NetworkManager/Devices/3" is created under NetworkManager directory. But mmcli is looking for "/org/freedesktop/ModemManager/Devices/3" under ModemManager directory.

One more point is Dongle has not created "ttyUSB" files.

I have enabled ModemManager debug flags but not able to enable NetworkManager debug flags due to some error. Please find the attached file "ModemManager_debug_logs".

 
Logs::
=======
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# dpkg -l | grep -e usb-mode
ii  usb-modeswitch                                       2.2.0+repack0-2ubuntu1                   amd64        mode switching tool for controlling "flip flop" USB devices
ii  usb-modeswitch-data                                  20140529-1                               all          mode switching data for usb-modeswitch
root@lappc-HP-xw4600-Workstation:/home/lappc# 
 
syslog::
========
Oct  8 16:42:07 lappc-HP-xw4600-Workstation usb_modeswitch[2979]: usb_modeswitch: switched to 19d2:1225 on 2/6
Oct  8 16:42:08 lappc-HP-xw4600-Workstation usb_modeswitch[2979]: usb_modeswitch: add device ID 19d2:1225 to driver option
Oct  8 16:42:08 lappc-HP-xw4600-Workstation usb_modeswitch[2979]: usb_modeswitch: please report the device ID to the Linux USB developers!
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.188298] usb 2-2: USB disconnect, device number 6
Oct  8 16:42:11 lappc-HP-xw4600-Workstation colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.616033] usb 2-2: new high-speed USB device number 7 using ehci-pci
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.768595] usb 2-2: New USB device found, idVendor=19d2, idProduct=1403
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.768597] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.768600] usb 2-2: Product: ZTE WCDMA Technologies MSM
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.768601] usb 2-2: Manufacturer: ZTE,Incorporated
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.768603] usb 2-2: SerialNumber: MF8250ZTED000000
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.787925] rndis_host 2-2:1.0 eth2: register 'rndis_host' at usb-0000:00:1d.7-2, RNDIS device, 34:4b:50:b7:ef:4a
Oct  8 16:42:11 lappc-HP-xw4600-Workstation mtp-probe: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2"
Oct  8 16:42:11 lappc-HP-xw4600-Workstation mtp-probe: bus: 2, device: 7 was not an MTP device

ttyUSB files::
==============
root@lappc-HP-xw4600-Workstation:/home/lappc# ls -a1 /dev/ttyU*
ls: cannot access /dev/ttyU*: No such file or directory
root@lappc-HP-xw4600-Workstation:/home/lappc# 
root@lappc-HP-xw4600-Workstation:/home/lappc# ls  /dev/tty*
/dev/tty    /dev/tty16  /dev/tty24  /dev/tty32  /dev/tty40  /dev/tty49  /dev/tty57  /dev/tty8       /dev/ttyS14  /dev/ttyS22  /dev/ttyS30
/dev/tty0   /dev/tty17  /dev/tty25  /dev/tty33  /dev/tty41  /dev/tty5   /dev/tty58  /dev/tty9       /dev/ttyS15  /dev/ttyS23  /dev/ttyS31
/dev/tty1   /dev/tty18  /dev/tty26  /dev/tty34  /dev/tty42  /dev/tty50  /dev/tty59  /dev/ttyprintk  /dev/ttyS16  /dev/ttyS24  /dev/ttyS4
/dev/tty10  /dev/tty19  /dev/tty27  /dev/tty35  /dev/tty43  /dev/tty51  /dev/tty6   /dev/ttyS0      /dev/ttyS17  /dev/ttyS25  /dev/ttyS5
/dev/tty11  /dev/tty2   /dev/tty28  /dev/tty36  /dev/tty44  /dev/tty52  /dev/tty60  /dev/ttyS1      /dev/ttyS18  /dev/ttyS26  /dev/ttyS6
/dev/tty12  /dev/tty20  /dev/tty29  /dev/tty37  /dev/tty45  /dev/tty53  /dev/tty61  /dev/ttyS10     /dev/ttyS19  /dev/ttyS27  /dev/ttyS7
/dev/tty13  /dev/tty21  /dev/tty3   /dev/tty38  /dev/tty46  /dev/tty54  /dev/tty62  /dev/ttyS11     /dev/ttyS2   /dev/ttyS28  /dev/ttyS8
/dev/tty14  /dev/tty22  /dev/tty30  /dev/tty39  /dev/tty47  /dev/tty55  /dev/tty63  /dev/ttyS12     /dev/ttyS20  /dev/ttyS29  /dev/ttyS9
/dev/tty15  /dev/tty23  /dev/tty31  /dev/tty4   /dev/tty48  /dev/tty56  /dev/tty7   /dev/ttyS13     /dev/ttyS21  /dev/ttyS3
root@lappc-HP-xw4600-Workstation:/home/lappc#
Comment 3 Rajasekhar 2015-10-08 14:43:51 UTC
Created attachment 118768 [details]
ModemManager debug logs
Comment 4 Aleksander Morgado 2015-10-08 14:48:54 UTC
(In reply to Rajasekhar from comment #3)
> Created attachment 118768 [details]
> ModemManager debug logs

Looks like your device is exposing a RNDIS interface. Is this one of these "MiFi" devices? If so, can you try to run dhclient on that interface directly?
Comment 5 Rajasekhar 2015-10-08 15:04:14 UTC
This is not "MiFi" device. This is Airtel 4G LTE USB Dongle. This is detecting as RNDIS interface and created an ethernet interface (eth3).


Logs::
======
ct  8 16:42:11 lappc-HP-xw4600-Workstation mtp-probe: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2"
Oct  8 16:42:11 lappc-HP-xw4600-Workstation mtp-probe: bus: 2, device: 7 was not an MTP device
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.788381] usb-storage 2-2:1.2: USB Mass Storage device detected
Oct  8 16:42:11 lappc-HP-xw4600-Workstation kernel: [ 2691.788488] scsi9 : usb-storage 2-2:1.2
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2:1.0/net/eth3, iface: eth3)
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2:1.0/net/eth3, iface: eth3): no ifupdown configuration found.
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <warn> failed to allocate link cache: (-26) Protocol mismatch
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <info> (eth3): carrier is OFF
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <info> (eth3): new Ethernet device (driver: 'rndis_host' ifindex: 5)
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <info> (eth3): exported as /org/freedesktop/NetworkManager/Devices/3
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <info> (eth3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <info> (eth3): bringing up device.
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <info> (eth3): carrier now ON (device state 20)
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <info> (eth3): preparing device.
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <info> (eth3): deactivating device (reason 'managed') [2]
Oct  8 16:42:11 lappc-HP-xw4600-Workstation NetworkManager[780]: <info> NetworkManager state is now DISCONNECTED
Comment 6 Rajasekhar 2015-10-09 09:26:03 UTC
Modemmanager is not supporting this device. Please find the logs below.

Logs::
=======
ModemManager[5965]: <debug> [1444376866.092130] [mm-plugin-manager.c:739] mm_plugin_manager_find_device_support(): (Plugin Manager) [/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2] Checking device support...
ModemManager[5965]: <debug> [1444376866.092198] [mm-plugin.c:212] apply_pre_probing_filters(): (Wavecom) [eth3] filtered by subsystem
ModemManager[5965]: <debug> [1444376866.092213] [mm-plugin.c:326] apply_pre_probing_filters(): (X22X) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.092224] [mm-plugin.c:212] apply_pre_probing_filters(): (Telit) [eth3] filtered by subsystem
ModemManager[5965]: <debug> [1444376866.092235] [mm-plugin.c:212] apply_pre_probing_filters(): (Motorola) [eth3] filtered by subsystem
ModemManager[5965]: <debug> [1444376866.092247] [mm-plugin.c:380] apply_pre_probing_filters(): (Ericsson MBM) [eth3] filtered by udev tags
ModemManager[5965]: <debug> [1444376866.092259] [mm-plugin.c:326] apply_pre_probing_filters(): (Cinterion) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.092271] [mm-plugin.c:326] apply_pre_probing_filters(): (Novatel) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.092282] [mm-plugin.c:326] apply_pre_probing_filters(): (Altair LTE) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.092293] [mm-plugin.c:253] apply_pre_probing_filters(): (Sierra) [eth3] filtered by drivers
ModemManager[5965]: <debug> [1444376866.092304] [mm-plugin.c:212] apply_pre_probing_filters(): (Longcheer) [eth3] filtered by subsystem
ModemManager[5965]: <debug> [1444376866.092314] [mm-plugin.c:326] apply_pre_probing_filters(): (Pantech) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.092325] [mm-plugin.c:253] apply_pre_probing_filters(): (Option High-Speed) [eth3] filtered by drivers
ModemManager[5965]: <debug> [1444376866.092336] [mm-plugin.c:212] apply_pre_probing_filters(): (Iridium) [eth3] filtered by subsystem
ModemManager[5965]: <debug> [1444376866.092346] [mm-plugin.c:326] apply_pre_probing_filters(): (Huawei) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.092357] [mm-plugin.c:212] apply_pre_probing_filters(): (Nokia) [eth3] filtered by subsystem
ModemManager[5965]: <debug> [1444376866.092392] [mm-plugin.c:212] apply_pre_probing_filters(): (Linktop) [eth3] filtered by subsystem
ModemManager[5965]: <debug> [1444376866.092423] [mm-plugin.c:253] apply_pre_probing_filters(): (Gobi) [eth3] filtered by drivers
ModemManager[5965]: <debug> [1444376866.092475] [mm-plugin.c:326] apply_pre_probing_filters(): (AnyDATA) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.092525] [mm-plugin.c:326] apply_pre_probing_filters(): (Nokia (Icera)) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.092580] [mm-plugin.c:326] apply_pre_probing_filters(): (Novatel LTE) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.097693] [mm-plugin.c:326] apply_pre_probing_filters(): (Samsung) [eth3] filtered by vendor/product IDs
ModemManager[5965]: <debug> [1444376866.097836] [mm-plugin.c:212] apply_pre_probing_filters(): (Option) [eth3] filtered by subsystem
ModemManager[5965]: <debug> [1444376866.097908] [mm-plugin.c:212] apply_pre_probing_filters(): (Via CBP7) [eth3] filtered by subsystem
ModemManager[5965]: <debug> [1444376866.098525] [mm-plugin-manager.c:640] build_plugins_list(): (Plugin Manager) [eth3] Found '2' plugins to try...
ModemManager[5965]: <debug> [1444376866.098568] [mm-plugin-manager.c:644] build_plugins_list(): (Plugin Manager) [eth3]   Will try with plugin 'ZTE'
ModemManager[5965]: <debug> [1444376866.098606] [mm-plugin-manager.c:644] build_plugins_list(): (Plugin Manager) [eth3]   Will try with plugin 'Generic'
ModemManager[5965]: <debug> [1444376866.098650] [mm-plugin.c:689] mm_plugin_supports_port(): (ZTE) [eth3] probing deferred until result suggested
ModemManager[5965]: <debug> [1444376866.098752] [mm-plugin-manager.c:569] plugin_supports_port_ready(): (Plugin Manager) [eth3] deferring support check until result suggested
ModemManager[5965]: <debug> [1444376867.969005] [mm-plugin-manager.c:710] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2] Minimum probing time consumed
ModemManager[5965]: <debug> [1444376867.969065] [mm-plugin-manager.c:368] suggest_single_port_probe_result(): (Plugin Manager) [eth3] deferred task cancelled, no suggested plugin
ModemManager[5965]: <debug> [1444376867.969123] [mm-plugin-manager.c:195] port_probe_context_finished(): (Plugin Manager) [eth3] not supported by any plugin
ModemManager[5965]: <debug> [1444376867.969175] [mm-device.c:357] mm_device_ignore_port(): Fully ignoring port 'net/eth3' from now on
ModemManager[5965]: <debug> [1444376867.969202] [mm-plugin-manager.c:316] port_probe_context_finished(): (Plugin Manager) 'eth3' port probe finished, last one in device
ModemManager[5965]: <debug> [1444376867.969228] [mm-plugin-manager.c:138] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2] device support check finished in '1.877059' seconds
ModemManager[5965]: <warn>  [1444376867.969266] [mm-base-manager.c:153] find_device_support_ready(): Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2': not supported by any plugin
Comment 7 Rajasekhar 2015-10-09 09:27:40 UTC
Created attachment 118774 [details]
ModemManager debug logs
Comment 8 Aleksander Morgado 2015-10-09 10:25:18 UTC
The problem seems to be that the modem isn't being modeswitched to any "modem" mode; i.e. there are no control ports to use, just a net port. ModemManager won't work with a setup like that.

Could you ask in the usb modeswitch forum to see what they say there?
Comment 9 Rajasekhar 2015-10-09 14:18:40 UTC
Thanks Aleksander. I will check with usb_modeswitch forum and come back.
Comment 10 Rajasekhar 2015-10-12 11:30:38 UTC
Hi Aleksander,

          I checked with usb_modeswitch team and I got the below reply. Please check the link "http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=2408&p=15831#p15831" for more info.

REPLY::
There is no other mode to switch the dongle into, it is designed with only one functional net interface and without any serial interfaces.

It is a netdevice which should be handled by NetworkManager not by ModemManager (mmcli) or wvdial.
It can not do serial ppp dialup!

Show Aleksander the output from lsusb -v -d 19d2:1403 and he will understand.
       

Logs::
======
root@lappc-HP-xw4600-Workstation:/home/lappc# lsusb -v -d 19d2:1403

Bus 002 Device 007: ID 19d2:1403 ZTE WCDMA Technologies MSM 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x19d2 ZTE WCDMA Technologies MSM
  idProduct          0x1403 
  bcdDevice           f0.7c
  iManufacturer           2 ZTE,Incorporated
  iProduct                3 ZTE WCDMA Technologies MSM
  iSerial                 4 MF8250ZTED000000
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           98
    bNumInterfaces          3
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass        224 Wireless
      bFunctionSubClass       1 Radio Frequency
      bFunctionProtocol       3 RNDIS
      iFunction               7 RNDIS
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol    255 Vendor Specific (MSFT RNDIS?)
      iInterface              5 RNDIS Communications Control
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x00
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              6 RNDIS Ethernet Data
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              1 Mass Storage
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)
root@lappc-HP-xw4600-Workstation:/home/lappc# lsusb
Bus 002 Device 007: ID 19d2:1403 ZTE WCDMA Technologies MSM 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 008 Device 002: ID 17ef:6019 Lenovo 
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@lappc-HP-xw4600-Workstation:/home/lappc#
Comment 11 Aleksander Morgado 2015-10-12 11:49:49 UTC
Yep, so that's what I was assuming. If we get only a net interface, then somehow that interface needs to be configured to give you IP connection. If dhclient doesn't work, there's likely some default static IP to configure, plus, very likely, a built-in "website" to allow configuring the modem connection details. ModemManager is out of the loop with those devices.

Could you see how the modem gets connected in a Windows environment? E.g. check which IP details you get set in the device using ZTE's drivers and connection tools. Also, you could look for specific firmare for your device labeled as "QMI" or "MBIM" or "Windows 8 mode"; if you can flash any of those then we may be able to do something in ModemManager.
Comment 12 Rajasekhar 2015-10-13 14:06:17 UTC
Thanks Aleksander for the info. 

I am not sure how to check the firmare for device labeled as "QMI" or "MBIM" or "Windows 8 mode".

One more thing, I have seen many linux forums that they are able to create ttyUSB devices. Please see the link below for one such example. 
In the logs below they have the drivers "option1" and "cdc_ether". So they are able to create ttyUSB devices.

In my case, I have only "cdc_ether" but I don't have "option1" drivers in Ubuntu PC. If I have "option1" drivers installed in Ubuntu then I think ttyUSB devices can be created. 

Could you please let me know your opinion.


Link:: http://boundarydevices.com/cellular-mod ... x6-boards/

Logs from the link::
===========
ubuntu@trusty-dev:/$ lsusb
Bus 001 Device 006: ID 12d1:1573 Huawei Technologies Co., Ltd. 
Bus 001 Device 005: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 004: ID 1bcf:0005 Sunplus Innovation Technology Inc. 
Bus 001 Device 003: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ubuntu@trusty-dev:/$ ls -a1 /dev/ttyU*
/dev/ttyUSB0
/dev/ttyUSB1
/dev/ttyUSB2
/dev/ttyUSB3
/dev/ttyUSB4

ubuntu@trusty-dev:/$ mmcli -L
Found 1 modems:
/org/freedesktop/ModemManager1/Modem/0 [Huawei Technologies Co., Ltd.] MU609
ubuntu@trusty-dev:/$

ubuntu@trusty-dev:/$ mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id '2431657b772fc128a660f7b8c0587c213129ca8f')
-------------------------
Hardware | manufacturer: 'Huawei Technologies Co., Ltd.'
| model: 'MU609'
| revision: '12.105.29.00.00'
| supported: 'gsm-umts'
| current: 'gsm-umts'
| equipment id: '357784046035976'
-------------------------
System | device: '/sys/devices/soc0/soc.1/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.3'
| drivers: 'option1, cdc_ether' =================================================>
| plugin: 'Huawei'
| primary port: 'ttyUSB2'
| ports: 'eth1 (net), ttyUSB1 (qcdm), ttyUSB2 (at), ttyUSB3 (gps), ttyUSB4 (at), ttyUSB0 (at)'
-------------------------
Numbers | own : 'unknown'
-------------------------
Status | lock: 'none'
| unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)'
| state: 'disabled'
| power state: 'on'
| access tech: 'unknown'
| signal quality: '0' (cached)
-------------------------
Modes | supported: 'allowed: 3g; preferred: none
| allowed: 2g; preferred: none
| allowed: 2g, 3g; preferred: none'
| current: 'allowed: 2g, 3g; preferred: none'
-------------------------
Bands | supported: 'unknown'
| current: 'unknown'
-------------------------
IP | supported: 'ipv4'
-------------------------
3GPP | imei: '357784046035976'
| enabled locks: 'none'
| operator id: 'unknown'
| operator name: 'unknown'
| subscription: 'unknown'
| registration: 'unknown'
-------------------------
SIM | path: '/org/freedesktop/ModemManager1/SIM/0'
-------------------------
Bearers | paths: 'none'





Ubuntu PC::
========
root@lappc-HP-xw4600-Workstation:/sys/bus/usb-serial/drivers# ls
generic
root@lappc-HP-xw4600-Workstation:/sys/bus/usb-serial/drivers#
Comment 13 Aleksander Morgado 2016-11-17 09:58:08 UTC
(In reply to Rajasekhar from comment #12)
> Thanks Aleksander for the info. 
> 
> I am not sure how to check the firmare for device labeled as "QMI" or "MBIM"
> or "Windows 8 mode".
> 
> One more thing, I have seen many linux forums that they are able to create
> ttyUSB devices. Please see the link below for one such example. 
> In the logs below they have the drivers "option1" and "cdc_ether". So they
> are able to create ttyUSB devices.
> 

I don't think your issue is due to the lack of drivers. The firmware in your device is not allowing any AT-based control of the device, and therefore no AT TTYs are exposed. Not much we can do in MM in that mode, at least until we allow auto-connected devices where the control port is the net interface itself.
Comment 14 GitLab Migration User 2018-06-10 09:03:05 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/32.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.