<div dir="ltr"><div>Hello Alexander and people in the list,</div><div><br></div><div>Let me provide some additional information and new test log messages.</div><div><br></div><div>The problem I reported is improved one setp. Originally it was like:</div><div> root at LEDE:~# mmcli -L<br> error: couldn't create manager: Timeout was reached<br></div><div><br></div><div>Now it is like:</div><div> root@LEDE:~# mmcli -L<br> No modems were found<br></div><div><br></div><div>I had to enable "dbus-utils" under "Utilities" of openwrt make menuconfig. So it seems that now mmcli talks with ModemManager at last. The problem now belongs to ModemManager not in the mmcli.</div><div><br></div><div><br></div><div>And I created the rule file you provided:</div><div><br></div><div># vim /lib/udev/rules.d/78-mm-custom.rules to fit to my modem:<br>ACTION!="add|change|move", GOTO="mm_custom_end"<br>DEVPATH=="/sys/devices/platform/1a0c0000.usb/usb2/2-1",<br>ENV{ID_MM_TTY_BAUDRATE}="115200"<br>DEVPATH=="/sys/devices/platform/1a0c0000.usb/usb2/2-1",<br>ENV{ID_MM_TTY_FLOW_CONTROL}="xon-xoff"<br>LABEL="mm_custom_end" <br></div><div><br></div><div>I wonder if these rule files are supposed to be provided from the modem provider. In my case, it is Hucom wireless.</div><div>Can I ask them to provide this file?</div><div><br></div><div>My modem is supposed to operate with this configs:</div><div><br></div><div>device : /dev/ttyUSB1</div><div>baudrate : 115200,</div><div>parity : none,</div><div>data : 8,</div><div>stop : 1,</div><div>flow : xon_xoff</div><div><br></div><div>And I added config section like shown below in the /etc/config/network:</div><div><br></div><div>config interface 'broadband'<br> option device '/sys/devices/platform/1a0c0000.usb/usb2/2-1'<br> option proto 'modemmanager'<br> option apn '<a href="http://5g-internet.sktelecom.com">5g-internet.sktelecom.com</a>'<br> option username ''<br> option password ''<br> option pincode ''<br> option lowpower '1'<br></div><div><br></div><div>I don't know the username and password, but maybe it wouldn't be needed at all. the pincode... I have no idea with this..</div><div><br></div><div>And also I added "--debug" in the start script /etc/rc.d/S70modemmanager:</div><div><br></div><div>procd_set_param command /usr/sbin/ModemManager --debug<br></div><div><br></div><div>And with these conditions, I rebooted my linux box and after the reboot is done, maybe 5 minutes later I captured log message:</div><div>logread > logread_last.log</div><div><br></div><div>And I attached it in this email. Please find the log message and see it through.</div><div><br></div><div>And you wanted to know what modem is mine:</div><div>The modem is HUCOM HM-900
</div><div><br></div><div>Kernel message related to the hucom modem:</div><div><div>==== [hucom_wwan_bind] : HUCOM HM9xx ====<br>qmi_wwan_hucom 2-1:1.2: cdc-wdm0: USB WDM device<br>HUCOM usbnet bind here<br>qmi_wwan_hucom 2-1:1.2 wwan0: register 'qmi_wwan_hucom' at usb-1a0c0000.usb-1, HUCOM wwan/QMI device, a2:25:55:58:dd:dd<br>==== [hucom_wwan_bind] : HUCOM HM9xx ====<br>ahci 1a200000.sata: couldn't get PHY in node sata: -517<br>qmi_wwan_hucom: probe of 2-1:1.3 failed with error -22<br>==== [hucom_wwan_bind] : HUCOM HM9xx ====<br>qmi_wwan_hucom: probe of 2-1:1.4 failed with error -22<br>usbcore: registered new interface driver qmi_wwan_hucom<br>l2tp_ppp: PPPoL2TP kernel driver, V2.0<br>usbcore: registered new interface driver option<br>usbserial: USB Serial support registered for GSM modem (1-port)<br>option 2-1:1.0: GSM modem (1-port) converter detected<br>usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0<br>option 2-1:1.1: GSM modem (1-port) converter detected<br>ahci 1a200000.sata: couldn't get PHY in node sata: -517<br>usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1<br>option 2-1:1.3: GSM modem (1-port) converter detected<br>ahci 1a200000.sata: couldn't get PHY in node sata: -517<br>option 2-1:1.4: GSM modem (1-port) converter detected<br>ahci 1a200000.sata: couldn't get PHY in node sata: -517<br>option 2-1:1.5: GSM modem (1-port) converter detected<br>ahci 1a200000.sata: couldn't get PHY in node sata: -517<br>usb 2-1: GSM modem (1-port) converter now attached to ttyUSB4<br>ahci 1a200000.sata: couldn't get PHY in node sata: -517<br>kmodloader: done loading kernel modules from /etc/modules.d/*<br></div><div></div></div><div><br></div><div><br></div><div>My system environement(HW/SW) :</div><div><br></div><div><div>Target Model : MediaTek MT7622 AC4300rfb1 board<br></div><div>Firmware Version : LEDE Reboot 17.01-SNAPSHOT unknown / LuCI</div><div>Kernel Version : 4.4.124</div><div>Modem : HUCOM HM-900<br></div><div>ModemManager<br></div><div>Version : 1.12.8<br></div><div>menuconfig : (QMI on, MBIM off)</div></div><div><br></div><div>It is QMI device.</div><div><div>qmichannel : /dev/cdc-wdm0</div><div>usbnet_adapter : /sys/class/net/wwan0</div><div>/sys/bus/usb/devices/2-1/manufacturer : QCOM<br></div><div>/sys/bus/usb/devices/2-1/idVendor :05C6</div><div>/sys/bus/usb/devices/2-1/idProduct :90db</div><div>/sys/bus/usb/devices/2-1/speed :5000</div><div>/sys/bus/usb/devices/2-1/product :SDXPRAIRIE-MTP _SN:B02CE51B</div><div>/sys/bus/usb/devices/2-1/version :3.20</div><div>/sys/bus/usb/devices/2-1:1.2/net/wwan0<br></div><div><div>/sys/bus/usb/devices/2-1:1.2/net/wwan0/device/driver<br></div><div><div>/sys/bus/usb/devices/2-1:1.2/net/wwan0/device</div></div><div></div></div><div><div><div>/sys/bus/usb/devices/2-1:1.2/usbmisc/cdc-wdm0<br></div><div><div></div></div></div><div>/sys/devices/platform/1a0c0000.usb/usb2/2-1/2-1:1.2<br></div><div></div></div><div><br></div><div>Kernel modules watched via lsmod</div><div>cdc_wdm 8821 1 qmi_wwan<br></div><div>qmi_wwan 6252 0<br></div><div>usbcore 153512 20 option,usb_wwan,qmi_wwan,cdc_ncm,cdc_ether,usbserial,usbnet,usblp,cdc_wdm,cdc_acm,usb_storage,xhci_mtk,xhci_plat_hcd,xhci_pci,xhci_hcd,uhci_hcd,ohci_platform,ohci_hcd,ehci_platform,ehci_hcd<br></div><div>usbnet 19027 3 qmi_wwan,cdc_ncm,cdc_ether</div></div><div><br></div><div>And usbnet adapter kernel module : qmi_wwan.c
written by Bjørn Mork
</div><div>USB serial driver option.c written by Matthias Urlichs</div><div><br></div><div>Do I miss anything?</div><div><br></div><div>F.Y.I. the modemmanager was not included in my OpenWRT source code. I copied it from <a href="https://github.com/openwrt/packages">https://github.com/openwrt/packages</a> and I just enabled it via openwrt make menuconfig.</div><div><br></div><div>Thank you very much in advance!</div><div><br></div><div>Jeonghum</div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2020년 5월 6일 (수) 오전 12:22, Aleksander Morgado <<a href="mailto:aleksander@aleksander.es" target="_blank">aleksander@aleksander.es</a>>님이 작성:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hey Jeonghum,<br>
<br>
> Thank you for the very kind message!<br>
> I tried "mmcli -L" and received an error message:<br>
> root at LEDE:~# mmcli -L<br>
> error: couldn't create manager: Timeout was reached<br>
><br>
<br>
This is extremely weird, and it would show some issue with your setup,<br>
maybe with how DBus is installed/running in the system. mmcli should<br>
never fail in that way; if the ModemManager daemon owns the<br>
well-known-name in DBus, a manager object should be created; and if<br>
there is no MM daemon running, mmcli would just return with a<br>
different error (couldn't find the ModemManager process in the bus).<br>
The fact that you're getting a timeout when trying to talk to the DBus<br>
server is not expected at all.<br>
<br>
> I added "--debug" option into the ModemManager start command.<br>
> I used device path: "/sys/devices/platform/1a0c0000.usb/usb2/2-1" in the /etc/config/network.<br>
><br>
> And I got an logread output file.<br>
> I will attach it to this email.<br>
><br>
> I already posted this question to the ModemManager maillist also:<br>
> <a href="https://lists.freedesktop.org/archives/modemmanager-devel/2020-May/007798.html" rel="noreferrer" target="_blank">https://lists.freedesktop.org/archives/modemmanager-devel/2020-May/007798.html</a><br>
><br>
> So now I'm waiting Alexander's reply message about my problem.<br>
<br>
I'm also in this mailing list :D<br>
<br>
> But, If you have any idea, please let me know.<br>
><br>
<br>
Did you try with the suggestion to configure baudrate and flow control<br>
settings? Looking at the kind of modem you're working with, I highly<br>
doubt those port settings will have any effect at the end, as you're<br>
really a device that exposes the TTY via USB port, and it also looks<br>
like you have a cdc-wdm+wwan pair (QMI? MBIM?). What modem<br>
manufacturer/model is this?<br>
<br>
--<br>
Aleksander<br>
<a href="https://aleksander.es" rel="noreferrer" target="_blank">https://aleksander.es</a><br>
</blockquote></div></div>