Packages: Modemmanager: EM7455 not coming out of LPM
Maintainer: @nickberry17 @aleksander0m
Environment: (x86_64, x86, OpenWrt version: snapshot)
Description:
Using a previously compiled (modemmanager 1.8.0-1) from a year ago with 18.06.1, works with the EM7455. Now, trying to build a snapshot with the included modemmanager 1.12.0-1 is keeping the EM744 in low-power mode. If I switch back to the previous (my 18.06.1 image), everything works so the modem appears to be setup ok.
I didn't see anything standing out in dmesg or at boot log.
wicadmin
All 64 comments
current fw version: 02.33.03.00
current carrier name: GENERIC
current config name: GENERIC_002.072_000
current subpri index: 000'
wicadmin
on 17 Nov 2019
Further investigation appears that 'Mobile Data' (or modemmanager if that is what it should be now) does not show up as a Protocol for an interface.
wicadmin
on 17 Nov 2019
wicadmin
on 17 Nov 2019
This is how it looks in the old working image:
wicadmin
on 17 Nov 2019
WARNING: Makefile 'package/feeds/luci/luci-app-cifsd/Makefile' has a dependency on 'cifsd-tools', which does not exist
WARNING: Makefile 'package/feeds/luci/luci-proto-modemmanager/Makefile' has a dependency on 'modemmanager', which does not exist
tmp/.config-package.in:104620:error: recursive dependency detected!
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:104620:symbol PACKAGE_nfs-kernel-server depends on NFS_KERNEL_SERVER_V4
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
feeds/packages/net/nfs-kernel-server/Config.in:4:symbol NFS_KERNEL_SERVER_V4 depends on PACKAGE_nfs-kernel-server
predators46
on 18 Nov 2019
@nickberry17 @aleksander0m OP forgot to add maintainer ;)
micmac1
on 18 Nov 2019
@wicadmin what do you mean it's kept in low-power mode?
Could you run MM with --debug (i.e. edit /etc/init/modemmanager to add --debug) and get the system logs while reproducing the issue?
aleksander0m
on 22 Nov 2019
General | dbus path: /org/freedesktop/ModemManager1/Modem/0
| device id: <redact>
--------------------------------
Hardware | manufacturer: Sierra Wireless, Incorporated
| model: EM7455
| firmware revision: SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30
| carrier config: default
| h/w revision: 1.0
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: <redact>
--------------------------------
System | device: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4
| drivers: qcserial, qmi_wwan
| plugin: Sierra
| primary port: cdc-wdm0
| ports: ttyUSB0 (qcdm), ttyUSB1 (gps), ttyUSB2 (at),
| cdc-wdm0 (qmi), wwan0 (net)
--------------------------------
Numbers | own: <redact>
--------------------------------
Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)
| state: disabled
| power state: low
| signal quality: 0% (cached)
--------------------------------
Modes | supported: allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 3g, 4g; preferred: 3g
| allowed: 3g, 4g; preferred: 4g
| current: allowed: 4g; preferred: none
--------------------------------
Bands | supported: utran-1, utran-3, utran-4, utran-5, utran-8, utran-2,
| eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7, eutran-8,
| eutran-12, eutran-13, eutran-20, eutran-25, eutran-26, eutran-41
| current: eutran-25
--------------------------------
IP | supported: ipv4, ipv6, ipv4v6
--------------------------------
3GPP | imei: <redact>
--------------------------------
3GPP EPS | ue mode of operation: csps-2
--------------------------------
SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0
@aleksander0m - end of debug log. Let me know where you want me to upload the full log:
<<<<<< RAW:
<<<<<< length = 20
<<<<<< data = 01:13:00:80:02:02:02:0F:00:40:00:07:00:02:04:00:01:00:47:00
[/dev/cdc-wdm0] received generic response (translated)...
<<<<<< QMUX:
<<<<<< length = 19
<<<<<< flags = 0x80
<<<<<< service = "dms"
<<<<<< client = 2
<<<<<< QMI:
<<<<<< flags = "response"
<<<<<< transaction = 15
<<<<<< tlv_length = 7
<<<<<< message = "UIM Get CK Status" (0x0040)
<<<<<< TLV:
<<<<<< type = "Result" (0x02)
<<<<<< length = 4
<<<<<< value = 01:00:47:00
<<<<<< translated = FAILURE: InvalidQmiCommand
<debug> [1574489734.692440] Couldn't query facility 'corp-pers' status, assuming disabled
<debug> [1574489734.692458] Retrieving PIN status to check for enabled PIN
[/dev/cdc-wdm0] sent message...
<<<<<< RAW:
<<<<<< length = 13
<<<<<< data = 01:0C:00:00:02:02:00:10:00:2B:00:00:00
[/dev/cdc-wdm0] sent generic request (translated)...
<<<<<< QMUX:
<<<<<< length = 12
<<<<<< flags = 0x00
<<<<<< service = "dms"
<<<<<< client = 2
<<<<<< QMI:
<<<<<< flags = "none"
<<<<<< transaction = 16
<<<<<< tlv_length = 0
<<<<<< message = "UIM Get PIN Status" (0x002B)
[/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<< length = 20
<<<<<< data = 01:13:00:80:02:02:02:10:00:2B:00:07:00:02:04:00:01:00:47:00
[/dev/cdc-wdm0] received generic response (translated)...
<<<<<< QMUX:
<<<<<< length = 19
<<<<<< flags = 0x80
<<<<<< service = "dms"
<<<<<< client = 2
<<<<<< QMI:
<<<<<< flags = "response"
<<<<<< transaction = 16
<<<<<< tlv_length = 7
<<<<<< message = "UIM Get PIN Status" (0x002B)
<<<<<< TLV:
<<<<<< type = "Result" (0x02)
<<<<<< length = 4
<<<<<< value = 01:00:47:00
<<<<<< translated = FAILURE: InvalidQmiCommand
<debug> [1574489734.756443] Couldn't query PIN status, assuming SIM PIN is disabled
<debug> [1574489734.756495] loading UE mode of operation for EPS...
<debug> [1574489734.756521] (ttyUSB2) device open count is 2 (open)
<debug> [1574489734.756577] (ttyUSB2): --> 'AT+CEMODE?<CR>'
<debug> [1574489734.773502] (ttyUSB2): <-- '<CR><LF>+CEMODE: 2<CR><LF><CR><LF>OK<CR><LF>'
<debug> [1574489734.773992] (ttyUSB2) device open count is 1 (close)
<debug> [1574489734.774047] Couldn't initialize interface: 'USSD not supported'
[/dev/cdc-wdm0] sent message...
<<<<<< RAW:
<<<<<< length = 24
<<<<<< data = 01:17:00:00:10:01:00:01:00:43:00:0B:00:10:01:00:05:01:04:00:03:00:00:00
[/dev/cdc-wdm0] sent generic request (translated)...
<<<<<< QMUX:
<<<<<< length = 23
<<<<<< flags = 0x00
<<<<<< service = "loc"
<<<<<< client = 1
<<<<<< QMI:
<<<<<< flags = "none"
<<<<<< transaction = 1
<<<<<< tlv_length = 11
<<<<<< message = "Get Server" (0x0043)
<<<<<< TLV:
<<<<<< type = "Server Address Type" (0x10)
<<<<<< length = 1
<<<<<< value = 05
<<<<<< translated = ipv4, url
<<<<<< TLV:
<<<<<< type = "Server Type" (0x01)
<<<<<< length = 4
<<<<<< value = 03:00:00:00
<<<<<< translated = umts-slp
[/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<< length = 20
<<<<<< data = 01:13:00:80:10:01:02:01:00:43:00:07:00:02:04:00:00:00:00:00
[/dev/cdc-wdm0] received generic response (translated)...
<<<<<< QMUX:
<<<<<< length = 19
<<<<<< flags = 0x80
<<<<<< service = "loc"
<<<<<< client = 1
<<<<<< QMI:
<<<<<< flags = "response"
<<<<<< transaction = 1
<<<<<< tlv_length = 7
<<<<<< message = "Get Server" (0x0043)
<<<<<< TLV:
<<<<<< type = "Result" (0x02)
<<<<<< length = 4
<<<<<< value = 00:00:00:00
<<<<<< translated = SUCCESS
[/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<< length = 30
<<<<<< data = 01:1D:00:80:10:01:04:01:00:43:00:11:00:01:04:00:00:00:00:00:02:04:00:03:00:00:00:12:00:00
[/dev/cdc-wdm0] received generic indication (translated)...
<<<<<< QMUX:
<<<<<< length = 29
<<<<<< flags = 0x80
<<<<<< service = "loc"
<<<<<< client = 1
<<<<<< QMI:
<<<<<< flags = "indication"
<<<<<< transaction = 1
<<<<<< tlv_length = 17
<<<<<< message = "Get Server" (0x0043)
<<<<<< TLV:
<<<<<< type = "Indication Status" (0x01)
<<<<<< length = 4
<<<<<< value = 00:00:00:00
<<<<<< translated = success
<<<<<< TLV:
<<<<<< type = "Server Type" (0x02)
<<<<<< length = 4
<<<<<< value = 03:00:00:00
<<<<<< translated = umts-slp
<<<<<< TLV:
<<<<<< type = "URL" (0x12)
<<<<<< length = 0
<<<<<< value = (NULL)
<<<<<< translated =
[/dev/cdc-wdm0] sent message...
<<<<<< RAW:
<<<<<< length = 13
<<<<<< data = 01:0C:00:00:10:01:00:02:00:36:00:00:00
[/dev/cdc-wdm0] sent generic request (translated)...
<<<<<< QMUX:
<<<<<< length = 12
<<<<<< flags = 0x00
<<<<<< service = "loc"
<<<<<< client = 1
<<<<<< QMI:
<<<<<< flags = "none"
<<<<<< transaction = 2
<<<<<< tlv_length = 0
<<<<<< message = "Get Predicted Orbits Data Source" (0x0036)
[/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<< length = 20
<<<<<< data = 01:13:00:80:10:01:02:02:00:36:00:07:00:02:04:00:00:00:00:00
[/dev/cdc-wdm0] received generic response (translated)...
<<<<<< QMUX:
<<<<<< length = 19
<<<<<< flags = 0x80
<<<<<< service = "loc"
<<<<<< client = 1
<<<<<< QMI:
<<<<<< flags = "response"
<<<<<< transaction = 2
<<<<<< tlv_length = 7
<<<<<< message = "Get Predicted Orbits Data Source" (0x0036)
<<<<<< TLV:
<<<<<< type = "Result" (0x02)
<<<<<< length = 4
<<<<<< value = 00:00:00:00
<<<<<< translated = SUCCESS
[/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<< length = 20
<<<<<< data = 01:13:00:80:10:01:04:02:00:36:00:07:00:01:04:00:01:00:00:00
[/dev/cdc-wdm0] received generic indication (translated)...
<<<<<< QMUX:
<<<<<< length = 19
<<<<<< flags = 0x80
<<<<<< service = "loc"
<<<<<< client = 1
<<<<<< QMI:
<<<<<< flags = "indication"
<<<<<< transaction = 2
<<<<<< tlv_length = 7
<<<<<< message = "Get Predicted Orbits Data Source" (0x0036)
<<<<<< TLV:
<<<<<< type = "Indication Status" (0x01)
<<<<<< length = 4
<<<<<< value = 01:00:00:00
<<<<<< translated = general-failure
<warn> [1574489735.012486] couldn't load supported assistance data types: 'LOC service: general failure'
<debug> [1574489735.012797] Messaging capabilities supported
<debug> [1574489735.012899] Supported storages loaded:
<debug> [1574489735.012913] mem1 (list/read/delete) storages: 'sm, me'
<debug> [1574489735.012926] mem2 (write/send) storages: 'sm, me'
<debug> [1574489735.012938] mem3 (reception) storages: 'sm, me'
<debug> [1574489735.012987] (ttyUSB2) device open count is 2 (open)
<debug> [1574489735.013031] (ttyUSB2): --> 'AT+CPMS?<CR>'
<debug> [1574489735.027085] (ttyUSB2): <-- '<CR><LF>+CPMS: "SM",0,0,"SM",0,0,"SM",0,0<CR><LF><CR><LF>OK<CR><LF>'
<debug> [1574489735.027241] Current storages initialized:
<debug> [1574489735.027262] mem1 (list/read/delete) storages: 'sm'
<debug> [1574489735.027278] mem2 (write/send) storages: 'sm'
<debug> [1574489735.027295] Current storages initialized
<debug> [1574489735.027519] (ttyUSB2) device open count is 3 (open)
<debug> [1574489735.027566] (ttyUSB2) device open count is 2 (close)
<debug> [1574489735.027613] (ttyUSB2): --> 'AT+CTZU=1<CR>'
<debug> [1574489735.042689] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1574489735.042823] (ttyUSB2): --> 'AT+CCLK?<CR>'
<debug> [1574489735.055294] (ttyUSB2): <-- '<CR><LF>+CCLK: "80/01/06,00:00:07-20"<CR><LF><CR><LF>OK<CR><LF>'
<debug> [1574489735.055631] Extended signal capabilities supported
<debug> [1574489735.055665] (ttyUSB2) device open count is 1 (close)
<debug> [1574489735.055966] OMA capabilities not supported
<debug> [1574489735.056011] Couldn't initialize interface: 'OMA not supported'
<debug> [1574489735.056310] (ttyUSB2) device open count is 2 (open)
<debug> [1574489735.056371] (ttyUSB2): --> 'ATH<CR>'
<debug> [1574489735.064454] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1574489735.064559] (ttyUSB2) device open count is 3 (open)
<debug> [1574489735.064599] (ttyUSB2) device open count is 2 (close)
<debug> [1574489735.064645] (ttyUSB2): --> 'AT+CLCC=?<CR>'
<debug> [1574489735.077808] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1574489735.078025] periodic call list polling will be used if supported
<debug> [1574489735.078251] (ttyUSB2) device open count is 1 (close)
<info> [1574489735.078441] Modem: state changed (unknown -> disabled)
<debug> [1574489735.078543] modem properly initialized
<debug> [1574489735.079940] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4] exported modem at path '/org/freedesktop/ModemManager1/Modem/0'
<debug> [1574489735.079963] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4] plugin: Sierra
<debug> [1574489735.079978] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4] vid:pid: 0x1199:0x9071
<debug> [1574489735.080011] (ttyUSB2) device open count is 0 (close)
<debug> [1574489735.080029] (ttyUSB2) closing serial port...
<debug> [1574489735.080454] (ttyUSB2) serial port closed
Hi @aleksander0m
It seems in the current working one (details below 18.06.1), the simple connect is called whereas the new one nothing else happens:
<info> [1574804604.614955] Modem: state changed (unknown -> disabled)
<debug> [1574804604.615046] modem properly initialized
<debug> [1574804604.616274] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4] exported modem at path '/org/freedesktop/ModemManager1/Modem/0'
<debug> [1574804604.616305] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4] plugin: Sierra
<debug> [1574804604.616328] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4] vid:pid: 0x1199:0x9071
<debug> [1574804604.616366] (ttyUSB2) device open count is 0 (close)
<debug> [1574804604.616393] (ttyUSB2) closing serial port...
<debug> [1574804604.616779] (ttyUSB2) serial port closed
<info> [1574804605.001727] Simple connect started...
<debug> [1574804605.001744] PIN: unspecified
<debug> [1574804605.001752] Operator ID: unspecified
<debug> [1574804605.001759] Allowed roaming: yes
<debug> [1574804605.001766] APN: r.ispsn
<debug> [1574804605.001774] IP family: ipv4
<debug> [1574804605.001781] Allowed authentication: unspecified
<debug> [1574804605.001788] User: unspecified
<debug> [1574804605.001795] Password: unspecified
<debug> [1574804605.001802] Number: unspecified
<info> [1574804605.001808] Simple connect state (3/8): Enable
<info> [1574804605.001839] Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
<debug> [1574804605.002025] Skipping modem initialization: device hotplugged
<debug> [1574804605.002042] (ttyUSB2) opening serial port...
<debug> [1574804605.002306] (ttyUSB2): setting up baudrate: 57600
<debug> [1574804605.002328] (ttyUSB2): port attributes not fully set
<debug> [1574804605.002353] (ttyUSB2) device open count is 1 (open)
<debug> [1574804605.002363] (ttyUSB2): running init sequence...
<debug> [1574804605.002387] (ttyUSB0) opening serial port...
<debug> [1574804605.002467] (ttyUSB0) device open count is 1 (open)
<debug> [1574804605.002477] Flashing primary AT port before enabling...
<debug> [1574804605.002491] (ttyUSB2): port attributes not fully set
<debug> [1574804605.002520] (ttyUSB2): --> 'ATE0<CR>'
<debug> [1574804605.011386] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1574804605.011450] (ttyUSB2): --> 'ATV1<CR>'
<debug> [1574804605.017443] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1574804605.017537] (ttyUSB2): --> 'AT+CMEE=1<CR>'
<debug> [1574804605.029203] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1574804605.029280] (ttyUSB2): --> 'ATX4<CR>'
<debug> [1574804605.036727] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1574804605.036843] (ttyUSB2): --> 'AT&C1<CR>'
<debug> [1574804605.044801] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1574804605.103165] Getting device operating mode...
@wicadmin could you test with the following branch? https://github.com/openwrt/packages/pull/10597
aleksander0m
on 27 Nov 2019
@aleksander0m - I was waiting for that PR, actively looking at it up to yesterday....sure, I can try and make a build but not sure if I have to wait for imagebuilder to get updated?
wicadmin
on 27 Nov 2019
UPDATE: Yes, snapshot still on: modemmanager_1.12.0-3_x86_64.ipk. I believe the latest is 1.12.0-8. Will hopefully be picked up in next snapshot build.
wicadmin
on 27 Nov 2019
BTW - I thought 19.07 was still open for new packages? Doesn't seem MM is in there: / releases / 19.07-SNAPSHOT / packages
wicadmin
on 27 Nov 2019
@wicadmin feel free to suggest it for 19.07 :D
aleksander0m
on 27 Nov 2019
@aleksander0m - I believe since it is actually at rc1 it may not accept anything new which is a shame not to get this in. Perhaps @feckert may be able to help.
wicadmin
on 27 Nov 2019
BTW - is luci-proto-modemmanager broken or working with this?
wicadmin
on 27 Nov 2019
OK, it is now in Snapshot. I'll go ahead and make a build.
wicadmin
on 28 Nov 2019
@aleksander0m - Well, no dice. It did not work. Modem still in LPM:
mmcli -m 0 --command='!gstatus?'
response: '!GSTATUS:
Current Time: 25 Temperature: 39
Reset Counter: 8 Mode: LOW POWER MODE '
Why is the fcc auth not working in the newer builds? I believe this feature was introduced since mm v1.6.
wicadmin
on 28 Nov 2019
@aleksander0m - I believe since it is actually at rc1 it may not accept anything new which is a shame not to get this in. Perhaps @feckert may be able to help.
I think it is not only done with porting the modemmanger also the dependencies and the toolchain must be cherrypicked.
So I think as I know openwrt-19.07 is feature complete.
Only bugfixes should get backported.
Modemmager is a new package.
feckert
on 29 Nov 2019
These are the packages pertaining to this which are in snapshot which are not in 19.07.0-rc1:
- mbim-utils.
- qmi-utils.
- libmbim.
- libqmi.
- modemmanager.
- luci-proto-modemmanager.
I don't know if the snapshot ipks are standalone without any necessary dependencies and therefore can be applied to 19.07.0-rc1.
wicadmin
on 29 Nov 2019
@aleksander0m - I built 18.06.5 and same issue. I even compiled MM and the accompanying packages from source (libmbim, libqm, luci-proto-modemmanager).
BTW - on this build, luci-proto-modemmanager does give a new error: Unknown error (INVALID_PROTO)
wicadmin
on 1 Dec 2019
@wicadmin Hey, Are you using the LuCI master branch? https://github.com/openwrt/luci/blob/master/protocols/luci-proto-modemmanager/htdocs/luci-static/resources/protocol/modemmanager.js luci-proto-modemmanager is only officially in master.
If you are on 18.xx you would be using the older LuCI branch. luci-proto-modemmanager didn't make it into 18, but you can compile it and install it yourself using this: https://github.com/nickberry17/luci-proto-modemmanager
nickberry17
on 2 Dec 2019
Hi @nickberry17 - yes, I complied it from there (https://github.com/nickberry17/luci-proto-modemmanager) to build a 18.05.6 image. But got the INVALID_PROTO unknown error.
wicadmin
on 2 Dec 2019
Can you list the contents of /usr/lib/lua/luci/model/network/ on your device? You should see proto_modemmanager.lua there.
nickberry17
on 2 Dec 2019
ls -l /usr/lib/lua/luci/model/network
total 32K
-rw-r--r-- 1 root root 1.7K Nov 29 04:01 proto_4x6.lua
-rw-r--r-- 1 root root 1.1K Nov 29 04:01 proto_6x4.lua
-rw-r--r-- 1 root root 401 Nov 29 04:01 proto_dhcpv6.lua
-rw-r--r-- 1 root root 410 Nov 29 04:01 proto_hnet.lua
-rwxrwxr-x 1 root root 1.6K Nov 5 09:12 proto_modemmanager.lua
-rw-r--r-- 1 root root 2.2K Nov 29 04:01 proto_ppp.lua
-rw-r--r-- 1 root root 1.5K Nov 29 04:01 proto_qmi.lua
-rw-r--r-- 1 root root 870 Nov 29 04:01 proto_wireguard.lua
Looks like it is installed but LuCI is not able to use it. Can you please verify you are using LuCI 18, and not some other branch? Run cat /usr/lib/lua/luci/version.lua
nickberry17
on 2 Dec 2019
luciname = "LuCI openwrt-18.06 branch"
luciversion = "git-19.332.23140-f01d93b"
wicadmin
on 2 Dec 2019
I think the problem is than in master we moved to client side javascripting and in openwrt-18.06 this part is missing. So you should update to openwrt-19.06 or master to have all needed dependencies.
feckert
on 2 Dec 2019
@wicadmin the FCC auth step is not even being tried, because there is no request to put the modem in online mode, as far as I can tell. That request should come from the MM protocol handler in netifd, as part of the simple connect procedure, and as you saw, looks like that is not being done.
I'm wondering whether you could try to test the setup without luci-proto-modemmanager. I've been too lazy and I have never tried that myself... I should! Anyway, if you can configure the modem settings for netifd in /etc/config/network manually, using /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4 as device option (see https://github.com/openwrt/packages/blob/master/net/modemmanager/README.md), we could rule out whether it's some issue in the luci package or in the real protocol handler. While doing that test, try to gather syslog to check the netifd logs.
aleksander0m
on 2 Dec 2019
@feckert - openwrt-19.06? You mean 19.07?
What I did was to use 18.06 and compiled these from their source with 18.06 SDK and imagebuilder. I also used the previous lua luci-proto-modemmanager as indicated by @nickberry17
- mbim-utils
- qmi-utils
- libmbim
- libqmi
- modemmanager
- luci-proto-modemmanager
Shouldn't the above work?
wicadmin
on 2 Dec 2019
@wicadmin It should, it's working for me; but maybe there is some difference we haven't spotted yet. I'll do some more investigating today.
nickberry17
on 2 Dec 2019
What is the point to have luci-proto-modemmanager in 19.07, mark it as @BROKEN instead of adding modemmanager into 19.07?
wicadmin
on 3 Dec 2019
luci-proto-modemmanager slipped into 19.07 because LuCI got synced with master. It was subsequently marked broken because modemmanger is unavailable there. I can drop the LuCI package entirely if this is preferable.
jow-
on 3 Dec 2019
luci-proto-modemmanagerslipped into 19.07 because LuCI got synced with master. It was subsequently marked broken because modemmanger is unavailable there. I can drop the LuCI package entirely if this is preferable.
No reason to have it there IMO if MM is not there with it.
nickberry17
on 3 Dec 2019
Well, be nice and preferable to slip modemmanager into 19.07 as for all intents and purposes it is stable to be in there and badly needed.
wicadmin
on 4 Dec 2019
Please just drop it. I wish there's no dependency warning on stable point release. modemmanager also has its own dependencies and we'll need to backport several packages if we choose that way.
mans0n
on 6 Dec 2019
Op 27 nov. 2019, om 16:30 heeft Aleksander Morgado notifications@github.com het volgende geschreven:
@wicadmin feel free to suggest it for 19.07 :D
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Indeed !
+1
poranje
on 7 Dec 2019
@mans0n - I have already listed the dependencies which all work with 19.07. There is no further dependencies and nothing to backport as they all compile on 19.07 as-is. I do not understand the incompetence here as more connectivity and IoT uses are requiring LTE modem and OpenWrt is refusing to adopt a proven package. We have the frontend part already in there, what is wrong with adding the backend?
wicadmin
on 8 Dec 2019
@wicadmin Sorry for the annoyance. I haven't read all the previous comments.
I don't really have objection to adding modemmanager to 19.07. But modemmanager needs libmbim and libqmi, and these packages also should be backported. I thought that removing just one luci package would be much easier, but if there's much demand on modemmanager, then it would be preferable to backport it. All I want is just to clear the dependency warnings before the 19.07.0 release.
mans0n
on 8 Dec 2019
@mans0n, first, apologies for my tone earlier. It has just been fustrating having this capability excluded again. Lots of efforts were done by the authors and maintainers to have this excluded at this point. I hope someone can add it in as all the dependencies should have a clean build.
Thank you.
wicadmin
on 8 Dec 2019
@wicadmin a good way forward to keep on discussing on the backport of MM to 19.07 would be to try to do the port yourself and suggest it as a PR to the 19.07 branch, and keep on discussing that in the PR. I have no idea what the process is to backport packages when the list has already been closed, but that would be a good and positive start. Complaining about this in an unrelated bug report is definitely not useful. I'm not an openwrt maintainer, but I'd suggest to keep a good and positive tone in all these discussions; using strong words and a bad tone doesn't help your cause ;)
aleksander0m
on 10 Dec 2019
I'm wondering whether you could try to test the setup without luci-proto-modemmanager. I've been too lazy and I have never tried that myself... I should! Anyway, if you can configure the modem settings for netifd in /etc/config/network manually, using
/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4asdeviceoption (see https://github.com/openwrt/packages/blob/master/net/modemmanager/README.md), we could rule out whether it's some issue in the luci package or in the real protocol handler. While doing that test, try to gather syslog to check the netifd logs.
@wicadmin were you able to try the setup without using the luci package, i.e. manually configuring /etc/config/network yourself?
aleksander0m
on 10 Dec 2019
@wicadmin are you by chance selecting the kernel modules for your modem? In the newer package I don't believe we are selecting all kernel modules by default. You can reference the help text in menuconfig for more information, but the gist is that you may need to go to Kernel Modules > USB > and select the appropriate kmods for your modem, such as kmod-usb-net-* and kmod-usb-serial-*
nickberry17
on 12 Dec 2019
@aleksander0m - I do have the settings already in /etc/config/network
@nickberry17 - I do have those modules too
These are the compiled packages:
wicadmin
on 15 Dec 2019
<<<<<< QMUX:
<<<<<< length = 19
<<<<<< flags = 0x80
<<<<<< service = "loc"
<<<<<< client = 1
<<<<<< QMI:
<<<<<< flags = "indication"
<<<<<< transaction = 2
<<<<<< tlv_length = 7
<<<<<< message = "Get Predicted Orbits Data Source" (0x0036)
<<<<<< TLV:
<<<<<< type = "Indication Status" (0x01)
<<<<<< length = 4
<<<<<< value = 01:00:00:00
<<<<<< translated = general-failure
<warn> [1576391153.059066] couldn't load supported assistance data types: 'LOC service: general failure'
<debug> [1576391153.059387] Messaging capabilities supported
<debug> [1576391153.059518] Supported storages loaded:
<debug> [1576391153.059532] mem1 (list/read/delete) storages: 'sm, me'
<debug> [1576391153.059545] mem2 (write/send) storages: 'sm, me'
<debug> [1576391153.059558] mem3 (reception) storages: 'sm, me'
<debug> [1576391153.059608] (ttyUSB2) device open count is 2 (open)
<debug> [1576391153.059654] (ttyUSB2): --> 'AT+CPMS?<CR>'
<debug> [1576391153.073183] (ttyUSB2): <-- '<CR><LF>+CPMS: "SM",0,0,"SM",0,0,"SM",0,0<CR><LF><CR><LF>OK<CR><LF>'
<debug> [1576391153.073343] Current storages initialized:
<debug> [1576391153.073364] mem1 (list/read/delete) storages: 'sm'
<debug> [1576391153.073381] mem2 (write/send) storages: 'sm'
<debug> [1576391153.073398] Current storages initialized
<debug> [1576391153.073586] (ttyUSB2) device open count is 3 (open)
<debug> [1576391153.073632] (ttyUSB2) device open count is 2 (close)
<debug> [1576391153.073679] (ttyUSB2): --> 'AT+CTZU=1<CR>'
<debug> [1576391153.088485] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1576391153.088623] (ttyUSB2): --> 'AT+CCLK?<CR>'
<debug> [1576391153.101078] (ttyUSB2): <-- '<CR><LF>+CCLK: "80/01/06,00:00:07-20"<CR><LF><CR><LF>OK<CR><LF>'
<debug> [1576391153.101409] Extended signal capabilities supported
<debug> [1576391153.101443] (ttyUSB2) device open count is 1 (close)
<debug> [1576391153.101728] OMA capabilities not supported
<debug> [1576391153.101771] Couldn't initialize interface: 'OMA not supported'
<debug> [1576391153.102079] (ttyUSB2) device open count is 2 (open)
<debug> [1576391153.102139] (ttyUSB2): --> 'ATH<CR>'
<debug> [1576391153.110150] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1576391153.110265] (ttyUSB2) device open count is 3 (open)
<debug> [1576391153.110304] (ttyUSB2) device open count is 2 (close)
<debug> [1576391153.110351] (ttyUSB2): --> 'AT+CLCC=?<CR>'
<debug> [1576391153.123343] (ttyUSB2): <-- '<CR><LF>OK<CR><LF>'
<debug> [1576391153.123544] periodic call list polling will be used if supported
<debug> [1576391153.123796] (ttyUSB2) device open count is 1 (close)
<info> [1576391153.123973] Modem: state changed (unknown -> disabled)
<debug> [1576391153.124074] modem properly initialized
<debug> [1576391153.125460] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4] exported modem at path '/org/freedesktop/ModemManager1/Modem/0'
<debug> [1576391153.125482] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4] plugin: Sierra
<debug> [1576391153.125496] [device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4] vid:pid: 0x1199:0x9071
<debug> [1576391153.125522] (ttyUSB2) device open count is 0 (close)
<debug> [1576391153.125540] (ttyUSB2) closing serial port...
<debug> [1576391153.125947] (ttyUSB2) serial port closed
Only other warning of note (but just could be unsupported feature:
<warn> [1576391151.459450] couldn't load carrier config: 'Cannot send message: QMI service 'pdc' version '1.15' required, got version '1.0''
@wicadmin can you please share your /etc/config/network and the output of "mmcli -m 0"?
For some reason, netifd and the protocol handler are not "matching" the device settings in /etc/config/network with the modem exposed by ModemManager. That match is done based on the device id, as exposed in the Device property in mmcli -m 0 output.
aleksander0m
on 16 Dec 2019
Only other warning of note (but just could be unsupported feature:
<warn> [1576391151.459450] couldn't load carrier config: 'Cannot send message: QMI service 'pdc' version '1.15' required, got version '1.0''
Yes, that is unrelated, and that error will actually go away in libqmi 1.26: https://gitlab.freedesktop.org/mobile-broadband/libqmi/merge_requests/80
aleksander0m
on 16 Dec 2019
These seem to match.
System | device: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4
| drivers: qcserial, qmi_wwan
| plugin: Sierra
| primary port: cdc-wdm0
| ports: ttyUSB0 (qcdm), ttyUSB1 (gps), ttyUSB2 (at),
| cdc-wdm0 (qmi), wwan0 (net)
--------------------------------
config interface 'wan1'
option proto 'modemmanager'
option device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4'
option apn 'r.ispsn'
option auth 'none'
option delegate '0'
option iptype 'ipv4'
option lowpower '1'
@wicadmin ok, this is good. And what happens if you manually run ifup wan1?
aleksander0m
on 17 Dec 2019
Absolutely nothing seems to happen.
If I issue: mmcli -m 0 --set-power-state-on the modem moves out of 'low power' to 'on'
Then it seems to connect to the carrier network:
mmcli -m 0 --command='!gstatus?'
response: '!GSTATUS:
Current Time: 356 Temperature: 40
Reset Counter: 56 Mode: ONLINE
System mode: LTE PS state: Attached
LTE band: B25 LTE bw: 15 MHz
LTE Rx chan: 8615 LTE Tx chan: 26615
LTE CA state: NOT ASSIGNED
EMM state: Registered Normal Service
RRC state: RRC Connected
IMS reg state: No Srv
PCC RxM RSSI: -48 RSRP (dBm): -78
PCC RxD RSSI: -64 RSRP (dBm): -94
Here is all the modules installed:
adblock - 3.8.14-1
base-files - 204.1-r10775-db8345d8e4
bash - 5.0-3
bnx2-firmware - 20190416-1
busybox - 1.30.1-5
ca-bundle - 20190110-1
ca-certificates - 20190110-1
cgi-io - 14
curl - 7.66.0-1
dbus - 1.12.12-1
diffutils - 3.7-2
dnsmasq-full - 2.80-14
dropbear - 2019.78-2
e2fsprogs - 1.44.5-2
fdisk - 2.34-1
firewall - 2019-11-22-8174814a-1
fstools - 2019-08-28-6a61b9ac-1
fwtool - 2
getrandom - 2019-06-16-4df34a4d-3
glib2 - 2.58.3-3
ip-tiny - 5.0.0-2.1
ip6tables - 1.8.3-1
iperf3 - 3.7-1
ipset - 7.3-1
iptables - 1.8.3-1
jq - 1.6-1
jshn - 2019-06-16-ecf56174-1
jsonfilter - 2018-02-04-c7e938d6-1
kernel - 4.14.156-1-e1dd7676581672f6f0bdb1363506dee1
kmod-bnx2 - 4.14.156-1
kmod-button-hotplug - 4.14.156-3
kmod-hid - 4.14.156-1
kmod-hid-generic - 4.14.156-1
kmod-hwmon-core - 4.14.156-1
kmod-i2c-algo-bit - 4.14.156-1
kmod-i2c-core - 4.14.156-1
kmod-igb - 4.14.156-1
kmod-input-core - 4.14.156-1
kmod-input-evdev - 4.14.156-1
kmod-ip6tables - 4.14.156-1
kmod-ipt-conntrack - 4.14.156-1
kmod-ipt-core - 4.14.156-1
kmod-ipt-ipset - 4.14.156-1
kmod-ipt-nat - 4.14.156-1
kmod-ipt-offload - 4.14.156-1
kmod-lib-crc-itu-t - 4.14.156-1
kmod-libphy - 4.14.156-1
kmod-mii - 4.14.156-1
kmod-natsemi - 4.14.156-1
kmod-ne2k-pci - 4.14.156-1
kmod-nf-conntrack - 4.14.156-1
kmod-nf-conntrack-netlink - 4.14.156-1
kmod-nf-conntrack6 - 4.14.156-1
kmod-nf-flow - 4.14.156-1
kmod-nf-ipt - 4.14.156-1
kmod-nf-ipt6 - 4.14.156-1
kmod-nf-nat - 4.14.156-1
kmod-nf-reject - 4.14.156-1
kmod-nf-reject6 - 4.14.156-1
kmod-nfnetlink - 4.14.156-1
kmod-nls-base - 4.14.156-1
kmod-pps - 4.14.156-1
kmod-ptp - 4.14.156-1
kmod-r8169 - 4.14.156-1
kmod-tun - 4.14.156-1
kmod-udptunnel4 - 4.14.156-1
kmod-udptunnel6 - 4.14.156-1
kmod-usb-core - 4.14.156-1
kmod-usb-ehci - 4.14.156-1
kmod-usb-hid - 4.14.156-1
kmod-usb-net - 4.14.156-1
kmod-usb-net-cdc-ether - 4.14.156-1
kmod-usb-net-cdc-mbim - 4.14.156-1
kmod-usb-net-cdc-ncm - 4.14.156-1
kmod-usb-net-hso - 4.14.156-1
kmod-usb-net-qmi-wwan - 4.14.156-1
kmod-usb-net-sierrawireless - 4.14.156-1
kmod-usb-serial - 4.14.156-1
kmod-usb-serial-option - 4.14.156-1
kmod-usb-serial-qualcomm - 4.14.156-1
kmod-usb-serial-sierrawireless - 4.14.156-1
kmod-usb-serial-wwan - 4.14.156-1
kmod-usb-wdm - 4.14.156-1
kmod-usb2 - 4.14.156-1
kmod-usb3 - 4.14.156-1
kmod-wireguard - 4.14.156+0.0.20190702-1
libattr - 2.4.48-1
libblkid1 - 2.34-1
libblobmsg-json - 2019-06-16-ecf56174-1
libc - 1.1.24-2
libcares - 1.15.0-4
libcomerr0 - 1.44.5-2
libcurl4 - 7.66.0-1
libdbus - 1.12.12-1
libexpat - 2.2.7-1
libext2fs2 - 1.44.5-2
libf2fs6 - 1.12.0-3
libfdisk1 - 2.34-1
libffi - 3.2.1-3
libgcc1 - 7.5.0-2
libgmp10 - 6.1.2-2
libip4tc2 - 1.8.3-1
libip6tc2 - 1.8.3-1
libipset13 - 7.3-1
libiwinfo-lua - 2019-10-16-07315b6f-1
libiwinfo20181126 - 2019-10-16-07315b6f-1
libjson-c2 - 0.12.1-3
libjson-script - 2019-06-16-ecf56174-1
libkmod - 20-2
liblua5.1.5 - 5.1.5-3
liblucihttp-lua - 2019-07-05-a34a17d5-1
liblucihttp0 - 2019-07-05-a34a17d5-1
liblzo2 - 2.10-2
libmbedtls12 - 2.16.3-1
libmbim - 1.20.2-3
libmnl0 - 1.0.4-2
libmosquitto-nossl - 1.6.8-1
libncurses6 - 6.1-5
libnetfilter-conntrack3 - 2018-05-01-3ccae9f5-2
libnettle7 - 3.5.1-1
libnfnetlink0 - 1.0.1-3
libnl-tiny - 0.1-5
libopenssl-conf - 1.1.1d-2
libopenssl1.1 - 1.1.1d-2
libpci - 3.6.2-3
libpopt0 - 1.16-2
libpthread - 1.1.24-2
libqmi - 1.24.2-1
libreadline8 - 8.0-1
librt - 1.1.24-2
libsensors5 - 3.5.0-4
libsmartcols1 - 2.34-1
libss2 - 1.44.5-2
libsysfs2 - 2.1.0-3
libubox20170601 - 2019-06-16-ecf56174-1
libubus-lua - 2018-10-06-221ce7e7-1
libubus20170705 - 2018-10-06-221ce7e7-1
libuci20130104 - 2019-09-01-415f9e48-3
libuclient20160123 - 2019-05-30-3b3e368d-1
libusb-1.0-0 - 1.0.22-2
libustream-openssl20150806 - 2019-11-05-c9b66682-2
libuuid1 - 2.34-1
libxtables12 - 1.8.3-1
lm-sensors - 3.5.0-4
lm-sensors-detect - 3.5.0-4
logd - 2019-06-16-4df34a4d-3
lscpu - 2.34-1
lua - 5.1.5-3
luci - git-19.344.41526-af5d665-1
luci-app-adblock - git-19.344.41526-af5d665-1
luci-app-commands - git-19.344.41526-af5d665-1
luci-app-firewall - git-19.344.41526-af5d665-1
luci-app-openvpn - git-19.344.41526-af5d665-1
luci-app-opkg - git-19.344.41526-af5d665-1
luci-app-wireguard - git-19.344.41526-af5d665-1
luci-base - git-19.344.41526-af5d665-1
luci-compat - git-19.344.41526-af5d665-1
luci-lib-ip - git-19.344.41526-af5d665-1
luci-lib-jsonc - git-19.344.41526-af5d665-1
luci-lib-nixio - git-19.344.41526-af5d665-1
luci-mod-admin-full - git-19.344.41526-af5d665-1
luci-mod-network - git-19.344.41526-af5d665-1
luci-mod-status - git-19.344.41526-af5d665-1
luci-mod-system - git-19.344.41526-af5d665-1
luci-proto-ipv6 - git-19.344.41526-af5d665-1
luci-proto-modemmanager - svn-r15103-1
luci-proto-ppp - git-19.344.41526-af5d665-1
luci-proto-qmi - git-19.344.41526-af5d665-1
luci-proto-wireguard - git-19.344.41526-af5d665-1
luci-ssl-openssl - git-19.344.41526-af5d665-1
luci-theme-bootstrap - git-19.344.41526-af5d665-1
mbim-utils - 1.20.2-3
mkf2fs - 1.12.0-3
modemmanager - 1.12.2-1
mosquitto-client-nossl - 1.6.8-1
mosquitto-nossl - 1.6.8-1
mtd - 24
mtr - 0.92-6
nano - 4.6-1
netifd - 2019-08-05-5e02f944-1
odhcp6c - 2019-01-11-e199804b-16
odhcpd-ipv6only - 2019-09-15-88d9ab64-3
openssl-util - 1.1.1d-2
openvpn-openssl - 2.4.7-2
openwrt-keyring - 2019-07-25-8080ef34-1
opkg - 2019-06-14-dcbc142e-1
partx-utils - 2.34-1
pciutils - 3.6.2-3
perl - 5.28.1-3
perlbase-base - 5.28.1-3
perlbase-bytes - 5.28.1-3
perlbase-class - 5.28.1-3
perlbase-config - 5.28.1-3
perlbase-cwd - 5.28.1-3
perlbase-errno - 5.28.1-3
perlbase-essential - 5.28.1-3
perlbase-fcntl - 5.28.1-3
perlbase-file - 5.28.1-3
perlbase-filehandle - 5.28.1-3
perlbase-i18n - 5.28.1-3
perlbase-integer - 5.28.1-3
perlbase-io - 5.28.1-3
perlbase-list - 5.28.1-3
perlbase-locale - 5.28.1-3
perlbase-params - 5.28.1-3
perlbase-posix - 5.28.1-3
perlbase-re - 5.28.1-3
perlbase-scalar - 5.28.1-3
perlbase-selectsaver - 5.28.1-3
perlbase-socket - 5.28.1-3
perlbase-symbol - 5.28.1-3
perlbase-tie - 5.28.1-3
perlbase-unicore - 5.28.1-3
perlbase-utf8 - 5.28.1-3
perlbase-xsloader - 5.28.1-3
procd - 2019-09-16-62dc8c0e-2
qmi-utils - 1.24.2-1
r8169-firmware - 20190416-1
rpcd - 2019-11-10-77ad0de0-1
rpcd-mod-file - 2019-11-10-77ad0de0-1
rpcd-mod-iwinfo - 2019-11-10-77ad0de0-1
rpcd-mod-luci - 20191114
rpcd-mod-rrdns - 20170710
rsync - 3.1.3-2
sysfsutils - 2.1.0-3
terminfo - 6.1-5
ubox - 2019-06-16-4df34a4d-3
ubus - 2018-10-06-221ce7e7-1
ubusd - 2018-10-06-221ce7e7-1
uci - 2019-09-01-415f9e48-3
uclient-fetch - 2019-05-30-3b3e368d-1
uhttpd - 2019-08-17-6b03f960-4
unzip - 6.0-8
uqmi - 2019-06-27-1965c713-7
urandom-seed - 1.0-1
urngd - 2019-06-17-c057e177-1
usb-modeswitch - 2017-12-19-f40f84c2-2
usbutils - 007-10
usign - 2019-08-06-5a52b379-1
wireguard - 0.0.20190702-1
wireguard-tools - 0.0.20190702-1
wwan - 2014-07-17-1
zlib - 1.2.11-3
Info from dmesg:
```[ 2.865826] init: Console is alive
[ 2.881883] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 2.892713] pps_core: LinuxPPS API ver. 1 registered
[ 2.899796] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it
[ 2.911541] PTP clock support registered
[ 2.917544] Button Hotplug driver version 0.4.1
[ 2.920053] hid-generic 0003:0518:0002.0002: input,hidraw1: USB HID v1.10 Device [USB-compliant keyboard] on usb-0000:00:14.0-5/input1
[ 2.940478] ehci-platform: EHCI generic platform driver
[ 2.947762] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 2.957436] init: - preinit -
[ 2.987152] random: jshn: uninitialized urandom read (4 bytes read)
[ 2.998881] random: jshn: uninitialized urandom read (4 bytes read)
[ 3.008372] random: jshn: uninitialized urandom read (4 bytes read)
[ 3.170240] clocksource: Switched to clocksource tsc
[ 3.430467] scsi 4:0:0:0: Direct-Access SanDisk Cruzer Fit 1.26 PQ: 0 ANSI: 6
[ 3.442913] sd 4:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[ 3.453655] sd 4:0:0:0: [sdb] Write Protect is off
[ 3.459995] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 3.460274] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3.479056] sdb: sdb1 sdb2
[ 3.485552] sd 4:0:0:0: [sdb] Attached SCSI disk
[ 6.056781] mount_root: mounting /dev/root
[ 6.066606] EXT4-fs (sda2): re-mounted. Opts: (null)
[ 6.084667] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[ 6.094749] urandom-seed: Seeding with /etc/urandom.seed
[ 6.105208] procd: - early -
[ 6.278989] urandom_read: 4 callbacks suppressed
[ 6.278990] random: jshn: uninitialized urandom read (4 bytes read)
[ 6.307357] random: jshn: uninitialized urandom read (4 bytes read)
[ 6.332133] random: jshn: uninitialized urandom read (4 bytes read)
[ 6.769773] procd: - ubus -
[ 6.824526] procd: - init -
[ 6.852015] urngd: v1.0.0 started.
[ 6.855837] kmodloader: loading kernel modules from /etc/modules.d/*
[ 6.866307] natsemi dp8381x driver, version 2.1, Sept 11, 2006
[ 6.866307] originally by Donald Becker becker@scyld.com
[ 6.866307] 2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
[ 6.866758] random: crng init done
[ 6.895870] tun: Universal TUN/TAP device driver, 1.6
[ 6.904262] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[ 6.912867] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 6.920996] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 6.929555] Netfilter messages via NETLINK v0.30.
[ 6.936857] ip_set: protocol 6
[ 6.944985] i2c /dev entries driver
[ 6.956522] usbcore: registered new interface driver cdc_wdm
[ 6.965343] hso: drivers/net/usb/hso.c: Option Wireless
[ 6.972223] usbcore: registered new interface driver hso
[ 6.980453] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 6.987830] ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
[ 6.997560] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 7.005594] ctnetlink v0.93: registering with nfnetlink.
[ 7.017065] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 7.051059] r8169 0000:01:00.0 eth0: RTL8168g/8111g at 0xffffc90000015000,, XID 0c000800 IRQ 43
[ 7.064001] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 7.076457] usbcore: registered new interface driver usbserial
[ 7.084909] usbcore: registered new interface driver usbserial_generic
[ 7.093106] usbserial: USB Serial support registered for generic
[ 7.102201] wireguard: WireGuard 0.0.20190702 loaded. See www.wireguard.com for information.
[ 7.112219] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld Jason@zx2c4.com. All Rights Reserved.
[ 7.126544] xt_time: kernel timezone is -0000
[ 7.133334] usbcore: registered new interface driver cdc_ether
[ 7.141920] usbcore: registered new interface driver cdc_ncm
[ 7.150929] usbcore: registered new interface driver qmi_wwan
[ 7.159386] usbcore: registered new interface driver sierra
[ 7.166282] usbserial: USB Serial support registered for Sierra USB modem
[ 7.175297] usbcore: registered new interface driver sierra_net
[ 7.183954] usbcore: registered new interface driver cdc_mbim
[ 7.191392] usbcore: registered new interface driver option
[ 7.198214] usbserial: USB Serial support registered for GSM modem (1-port)
[ 7.206780] usbcore: registered new interface driver qcserial
[ 7.213794] usbserial: USB Serial support registered for Qualcomm USB modem
[ 7.222058] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 8.772401] r8169 0000:01:00.0 eth0: link down
[ 8.772404] r8169 0000:01:00.0 eth0: link down
[ 8.772552] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 8.774648] IPv6: ADDRCONF(NETDEV_UP): eth0.300: link is not ready
[ 8.776348] IPv6: ADDRCONF(NETDEV_UP): eth0.400: link is not ready
[ 8.778035] IPv6: ADDRCONF(NETDEV_UP): eth0.500: link is not ready
[ 8.779655] IPv6: ADDRCONF(NETDEV_UP): eth0.900: link is not ready
[ 8.780783] IPv6: ADDRCONF(NETDEV_UP): eth0.10: link is not ready
[ 8.781484] IPv6: ADDRCONF(NETDEV_UP): eth0.2: link is not ready
[ 8.810142] usb 1-4: new high-speed USB device number 4 using xhci_hcd
[ 8.990671] usb 1-4: config 1 has an invalid interface number: 8 but max is 3
[ 8.990674] usb 1-4: config 1 has no interface number 1
[ 8.992002] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[ 8.992077] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
[ 8.992492] qcserial 1-4:1.2: Qualcomm USB modem converter detected
[ 8.992554] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB1
[ 8.992967] qcserial 1-4:1.3: Qualcomm USB modem converter detected
[ 8.993032] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB2
[ 8.993466] qmi_wwan 1-4:1.8: cdc-wdm0: USB WDM device
[ 8.993752] qmi_wwan 1-4:1.8 wwan0: register 'qmi_wwan' at usb-0000:00:14.0-4, WWAN/QMI device,
[ 11.653413] r8169 0000:01:00.0 eth0: link up
mm.log does not have anything new. Remains this way.
tail /var/log/mm.log
```
wicadmin
on 18 Dec 2019
Absolutely no idea what may be happening I'm afraid. You shouldn't need the manual mmcli command to set it to power-on because the netfid protocol handler is the one responsible for "enabling" the modem, and the power-on state is part of the enabling phase.
Would it be possible to give me ssh access to that machine so that I can try to debug it further? Email me details if possible.
aleksander0m
on 18 Dec 2019
yeah, this one is not easy to figure out.
Do you have one of these modems? If so, I can get you the image. You can run it in qemu or some other VM. e.g.:
qemu-system-x86_64 -name OpenWRT -cpu Nehalem -m 1024 -boot d -hda openwrt-19.07.0-rc2-x86-64-combined-ext4.img
Hi there,
I'd just give git-bisect a try. Because you know it worked in the past.
In the beginning you wrote that MM 1.8.0-1 works on OpenWrt 18.06.1 with
EM7455. So I'd install 18.06.1 on my router. Then I would fetch the
18.06.1 SDL and replace MM 1.8.0-1 in it with the current MM. Then I'd
compile MM, load it onto the router and give it a try.
If it works the issue shouldn't be with MM. If it doesn't use git-bisect
on MM to find the commit where things went south.
The issue could also be with the freedesktop libs. So the same procedure
could be applied to them.
If you can exclude the libs and MM then the problem is likely in the
kernel. You could git bisect between OpenWrt 18.06.1 and master, in this
case.
This may boil down to some work for you. But in the past whenever I used
git-bisect it got me where I needed to be. :)
Just my 2 cents.
Regards,
Seb
micmac1
on 19 Dec 2019
@micmac1 in this very specific case, though, the issue is neither in MM nor in the freedesktop libs. The modem is correctly detected by MM, but there is no "enable" request arriving to MM, so the modem is never enabled (set to power state on).
I still don't know exactly why this is happening, but I suspect more on the MM protocol handler than on any other thing. Speaking of which....
@wicadmin could you please install the pppd package as well? I don't see it in the list you provided, and it's a requirement of the protocol handler. Your issue could be as simple as that... We should make the MM package depend on pppd, but I didn't get a chance to do that myself (patches welcome). See this bug report for context: https://github.com/openwrt/packages/issues/10802
aleksander0m
on 19 Dec 2019
@aleksander0m - it could be that simple. Not sure how it is there is 18.06.1 and now gone using the same build scripts. I will add and try that.
wicadmin
on 19 Dec 2019
@wicadmin my original packaging rules, the ones you probably used in 18.06.1, had an explicit dependency on ppp: https://gitlab.freedesktop.org/mobile-broadband/mobile-broadband-openwrt/blob/master/modemmanager/Makefile
aleksander0m
on 19 Dec 2019
(also please reboot your setup once you have installed the ppp package)
aleksander0m
on 19 Dec 2019
well, that was it. PPP was the missing link.
Now I can go try moving to the em12-g and the dw5821e /T77W968 should be arriving soon. Just need to know how to lock these to Sprint band 25. Any help on that before I close out this issue.
BTW - luci-proto-modemmanager works fine too!
wicadmin
on 19 Dec 2019
well, that was it. PPP was the missing link.
Yey!
Now I can go try moving to the em12-g and the dw5821e /T77W968 should be arriving soon. Just need to know how to lock these to Sprint band 25. Any help on that before I close out this issue.
You need to run this before the modem gets connected:
$ sudo mmcli -m 0 --set-current-bands="eutran-25"
There's no current support to configure that via /etc/config/network, but I don't see why we couldn't have that.
aleksander0m
on 19 Dec 2019
@aleksander0m ooohhh, that would be awesome and a nice holiday surprise to get some of those properties externalized into /etc/config/network.
I assume this will work?:
In /etc/init.d/modemmanager:
# Setup ModemManager service
procd_open_instance
procd_set_param command /usr/sbin/ModemManager
procd_append_param command --log-file=/var/log/mm.log
procd_append_param command --debug
procd_set_param respawn ${respawn_threshold:-3600} ${respawn_timeout:-5} ${respawn_retry:-5}
procd_set_param pidfile "${MODEMMANAGER_PID_FILE}"
procd_close_instance
mmcli -m 0 --set-current-bands="eutran-25"
mmcli -G ERR
Thanks so much for all your help on this one. We got there in the end and I'm delighted.
wicadmin
on 19 Dec 2019
@aleksander0m ooohhh, that would be awesome and a nice holiday surprise to get some of those properties externalized into
/etc/config/network.I assume this will work?:
In /etc/init.d/modemmanager: # Setup ModemManager service procd_open_instance procd_set_param command /usr/sbin/ModemManager procd_append_param command --log-file=/var/log/mm.log procd_append_param command --debug procd_set_param respawn ${respawn_threshold:-3600} ${respawn_timeout:-5} ${respawn_retry:-5} procd_set_param pidfile "${MODEMMANAGER_PID_FILE}" procd_close_instance mmcli -m 0 --set-current-bands="eutran-25" mmcli -G ERRThanks so much for all your help on this one. We got there in the end and I'm delighted.
Agreed, that would allow us to do things like band locking and so much more in luci-proto-modemmanager
nickberry17
on 19 Dec 2019
Agreed, that would allow us to do things like band locking and so much more in luci-proto-modemmanager
That is very true, will make this very appealing to most folks and easier to see all config items in LuCI.
wicadmin
on 19 Dec 2019
Maintainer: @nickberry17 @aleksander0m
Environment: (x86_64, x86, OpenWrt version: snapshot)Description:
Using a previously compiled (modemmanager 1.8.0-1) from a year ago with 18.06.1, works with the EM7455. Now, trying to build a snapshot with the included modemmanager 1.12.0-1 is keeping the EM744 in low-power mode. If I switch back to the previous (my 18.06.1 image), everything works so the modem appears to be setup ok.I didn't see anything standing out in dmesg or at boot log.
good that it is working now. I had the same issue!
I found out there is the possibility to disable that FCC auth needed by lenovo branded modems
https://www.lteforum.at/mobilfunk/cat-12-modul-sierra-airprime-em7565.8143/post-253940
Have not tried it so far
nevusZ
on 20 Dec 2019
Related issues
Lyoko-Jeremie
·
8Comments
u8wdz7
·
4Comments
aparcar
·
3Comments
muddyfeet
·
9Comments
robcollins55
·
5Comments
Most helpful comment
@wicadmin a good way forward to keep on discussing on the backport of MM to 19.07 would be to try to do the port yourself and suggest it as a PR to the 19.07 branch, and keep on discussing that in the PR. I have no idea what the process is to backport packages when the list has already been closed, but that would be a good and positive start. Complaining about this in an unrelated bug report is definitely not useful. I'm not an openwrt maintainer, but I'd suggest to keep a good and positive tone in all these discussions; using strong words and a bad tone doesn't help your cause ;)