ModemManager-1.6.2: does not work with Huawei E3372h ??? -153
Martin MOKREJŠ
mmokrejs at gmail.com
Fri Jan 13 10:58:24 UTC 2017
Hi Aleksander,
Aleksander Morgado wrote:
> Hey,
>
>>>
>>> I am a little bit surprised that the modem uses the ppp-interface in your
>>> case. When I read your logfiles right, then you have a device which is sold
>>> under the name "Speedsick LTE V" in Germany.
https://www.alza.cz/huawei-e3372h-d4474721.htm?catid=18851781
Inside there is a sticker label Huawei E3372h-153. On the paper box was just E3372h I think.
>>
>> How do you achieve non-PPP option in nm-applet? Whenever I select "Mobile broadband" there are these option driver-based and PPP-based fields. Should I use "Ethernet" instead?
>>
>
> This is transparent to the user; the user doesn't know whether the
> connection will be through PPP or a WWAN network interface. The
> PPP-based fields are always there, but they won't apply if the
> connection goes through a WWAN network interface. This is not ideal,
> but right now there's no way for NM to know the type of interface that
> will be used for the connection later on; only when it has been
> already established.
Great. It you would find a find to tell users through nm-applet that they should not panic, it would be comfortable. Also, the Setup wizard of "Add new connection" could show some hints along the "Mobile broadband" versus "Ethernet" items. So I infer is correctly picked up the "Mobile broadband" item and in an ideal word, MM should have used the huawei_cdc_ncm-enabled port of my system.
>
>>>
>>> This device should use the wwan-device by huawei_cdc_ncm.
>>
>> I am glad to hear that as well, but can you tell me if ModemManager realizes that wwan0 was renamed by OpenRC to wwp0s29u1u2i2 ? Does that interfere anyhow?
>>
>
> That won't interfere no, as long as the network interface renaming
> rules are run before MM's own udev rules.
>
>> Can you tell if ModemManager should run "usb_modeswitch -J -v 0x12d1 -p 0x14fe" automagically (I have v.2.4.0 of usb_modeswitch")?
>>
>
> ModemManager doesn't run any usb_modeswitch command itself.
> usb_modeswitch is usually run way before the MM rules are applied.
OK, I will need to study the error message about non-existing hwdb.bin of my dmesg. usb_modeswitch is being run for my other modem E3131 so I should check whether the E3372h-153 is already recognized or not yet.
>
>>>
>>> I know three different kinds of this device
>>>
>>> E3372 hilink-mode (cdc_ether) direct from huawei
>>> E3372 - Telekom - huawei_cdc_ncm
>>> K5160 - Vodafone -mbim/cdc_ether
>>>
>>> In no case a fallback to ppp should be needed.
>>
>> That is what I also thought, especially because Alexander asked me in the beginning of the thread if I have the CDC_NCM or CDC_NCM_HUAWEI enabled.
>>
>
> Does the list of ports in the "mmcli -m [N]" output show any "cdc-wdm" port?
Aha, another case for the EXAMPLES in the manual page. ;-)
# mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id '8535cb325128fbfaf101bd4f13c94eb41c4fb88b')
-------------------------
Hardware | manufacturer: 'huawei'
| model: 'E3372'
| revision: '21.200.07.00.55'
| supported: 'gsm-umts'
| current: 'gsm-umts'
| equipment id: 'xxxxxxxxxxxxxxxx'
-------------------------
System | device: '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2'
| drivers: 'option1, huawei_cdc_ncm'
| plugin: 'Huawei'
| primary port: 'ttyUSB0'
| ports: 'ttyUSB0 (at), ttyUSB1 (at), wwp0s29u1u2i2 (net)'
-------------------------
Numbers | own : 'unknown'
-------------------------
Status | lock: 'none'
| unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)'
| state: 'connected'
| power state: 'on'
| access tech: 'lte'
| signal quality: '41' (recent)
-------------------------
Modes | supported: 'allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g, 4g; preferred: none'
| current: 'allowed: 2g, 3g, 4g; preferred: none'
-------------------------
Bands | supported: 'unknown'
| current: 'unknown'
-------------------------
IP | supported: 'ipv4'
-------------------------
3GPP | imei: 'xxxxxxxxxxxxxx'
| enabled locks: 'none'
| operator id: '23001'
| operator name: 'T-Mobile CZ'
| subscription: 'unknown'
| registration: 'home'
-------------------------
SIM | path: '/org/freedesktop/ModemManager1/SIM/0'
-------------------------
Bearers | paths: '/org/freedesktop/ModemManager1/Bearer/0'
#
Why is the driver called option1 instead of just option?
# grep OPTION /usr/src/linux-4.9.2/.config
# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set
CONFIG_USB_SERIAL_OPTION=m
#
>
>> I have compiled:
>>
>> # grep CONFIG_USB_NET_ /usr/src/linux-4.9.2/.config
>> CONFIG_USB_NET_DRIVERS=y
>> # CONFIG_USB_NET_AX8817X is not set
>> # CONFIG_USB_NET_AX88179_178A is not set
>> CONFIG_USB_NET_CDCETHER=m
>> # CONFIG_USB_NET_CDC_EEM is not set
>> CONFIG_USB_NET_CDC_NCM=y
>> CONFIG_USB_NET_HUAWEI_CDC_NCM=y
>> CONFIG_USB_NET_CDC_MBIM=y
>> # CONFIG_USB_NET_DM9601 is not set
>> # CONFIG_USB_NET_SR9700 is not set
>> # CONFIG_USB_NET_SR9800 is not set
>> # CONFIG_USB_NET_SMSC75XX is not set
>> # CONFIG_USB_NET_SMSC95XX is not set
>> # CONFIG_USB_NET_GL620A is not set
>> CONFIG_USB_NET_NET1080=m
>> CONFIG_USB_NET_PLUSB=m
>> # CONFIG_USB_NET_MCS7830 is not set
>> CONFIG_USB_NET_RNDIS_HOST=m
>> CONFIG_USB_NET_CDC_SUBSET=m
>> # CONFIG_USB_NET_ZAURUS is not set
>> # CONFIG_USB_NET_CX82310_ETH is not set
>> # CONFIG_USB_NET_KALMIA is not set
>> CONFIG_USB_NET_QMI_WWAN=m
>> # CONFIG_USB_NET_INT51X1 is not set
>> # CONFIG_USB_NET_CH9200 is not set
>> # CONFIG_USB_NET_RNDIS_WLAN is not set
>>
>
> Ok, huawei-cdc-ncm is enabled.
>
> But how about the cdc-wdm driver (CONFIG_USB_WDM)?
# grep CONFIG_USB_WDM /usr/src/linux-4.9.2/.config
CONFIG_USB_WDM=y
#
Martin
More information about the ModemManager-devel
mailing list