On Fri, Oct 26, 2018 at 3:17 PM Tim Harvey <thar...@gateworks.com> wrote: > > Greetings, > > I'm working with a u-blox SARA R410M CAT M1 modem > (https://www.u-blox.com/en/product/sara-r4n4-series) using Linux 4.15 > and modem-manager-1.9.0 / libqmi-utils-1.21.4 from Aleksander's next > PPA. My SIM is a Verizon 4G LTE Cat M1 SIM Card from Nibelink > (https://nimbelink.com/Documentation/Sim_Cards/NL-SIM-VER-M1/1001410_NL-SIM-VER-M1_Datasheet.pdf) > and I've activated it with Nibelink. > > While modemmanager is able to detect, enable, and successfully scan it > won't connect. > > root@bionic-armhf:~# uname -r > 4.15.0-36-generic > root@bionic-armhf:~# cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=18.04 > DISTRIB_CODENAME=bionic > DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" > root@bionic-armhf:~# dpkg -s modemmanager | grep Version > Version: 1.9.0.next-20181010-1-0aleksander1 > root@bionic-armhf:~# dpkg -s libqmi-utils | grep Version > Version: 1.21.4.next-20181010-1-0aleksander1 > > root@bionic-armhf:~# mmcli --list-modems > > Found 1 modems: > /org/freedesktop/ModemManager1/Modem/0 [u-blox] SARA-R410M-52B > > root@bionic-armhf:~# mmcli -m 0 > > /org/freedesktop/ModemManager1/Modem/0 (device id > '9469a10655ec4f4d00c5ebad896376291d2a563b') > ------------------------- > Hardware | manufacturer: 'u-blox' > | model: 'SARA-R410M-52B' > | revision: 'L0.0.00.00.06.05 1 [Aug 01 2018 14:05:07]' > | H/W revision: '10000' > | supported: 'lte' > | current: 'lte' > | equipment id: '357812090839082' > ------------------------- > System | device: > '/sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.2/1-1.2.3' > | drivers: 'qmi_wwan, option1' > | plugin: 'Generic' > | primary port: 'cdc-wdm0' > | ports: 'ttyUSB1 (qcdm), ttyUSB2 (at), cdc-wdm0 > (qmi), wwan0 (net)' > ------------------------- > Numbers | own : 'unknown' > ------------------------- > Status | lock: 'sim-pin2' > | 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: 4g; preferred: none' > | current: 'allowed: 4g; preferred: none' > ------------------------- > Bands | supported: 'eutran-1, eutran-2, eutran-3, eutran-4, > eutran-5, eutran-8, eutran-12, eutran-13, eutran-17, eutran-18, > eutran-19, eutran-20, eutran-39' > | current: 'eutran-1, eutran-2, eutran-3, eutran-4, > eutran-5, eutran-8, eutran-12, eutran-13, eutran-17, eutran-18, > eutran-19, eutran-20, eutran-39' > ------------------------- > IP | supported: 'ipv4, ipv6, ipv4v6' > ------------------------- > 3GPP | imei: '357812090839082' > | enabled locks: 'none' > | operator id: 'unknown' > | operator name: 'unknown' > | subscription: 'unknown' > | registration: 'unknown' > | EPS UE mode: 'csps-2' > | PCO: 'n/a' > ------------------------- > SIM | path: '/org/freedesktop/ModemManager1/SIM/0' > > ------------------------- > Bearers | paths: 'none' > > root@bionic-armhf:~# mmcli -m 0 --enable > successfully enabled the modem > root@bionic-armhf:~# mmcli --modem 0 --3gpp-scan --timeout=300 > > Found 3 networks: > 311480 - 311 480 (lte, current) > 313100 - 313 100 (lte, available) > 310410 - 310 410 (lte, available) > > root@bionic-armhf:~# mmcli --modem 0 --simple-connect="apn=vzwinternet" > > Stopping ModemManager and using qmicli in every way I currently know > how yields this: > > root@bionic-armhf:~# systemctl stop ModemManager > root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --uim-get-card-status > [/dev/cdc-wdm0] Successfully got card status > Provisioning applications: > Primary GW: slot '0', application '2' > Primary 1X: session doesn't exist > Secondary GW: session doesn't exist > Secondary 1X: session doesn't exist > Card [0]: > Card state: 'present' > UPIN state: 'not-initialized' > UPIN retries: '0' > UPUK retries: '0' > Application [0]: > Application type: 'csim (4)' > Application state: 'detected' > Application ID: > A0:00:00:03:43:10:02:F3:10:FF:FF:89:02:00:00:FF > Personalization state: 'unknown' > UPIN replaces PIN1: 'no' > PIN1 state: 'not-initialized' > PIN1 retries: '0' > PUK1 retries: '0' > PIN2 state: 'not-initialized' > PIN2 retries: '0' > PUK2 retries: '0' > Application [1]: > Application type: 'isim (5)' > Application state: 'detected' > Application ID: > A0:00:00:00:87:10:04:F3:10:FF:FF:89:08:00:00:FF > Personalization state: 'unknown' > UPIN replaces PIN1: 'no' > PIN1 state: 'not-initialized' > PIN1 retries: '0' > PUK1 retries: '0' > PIN2 state: 'not-initialized' > PIN2 retries: '0' > PUK2 retries: '0' > Application [2]: > Application type: 'usim (2)' > Application state: 'ready' > Application ID: > A0:00:00:00:87:10:02:F3:10:FF:FF:89:08:00:00:FF > Personalization state: 'ready' > UPIN replaces PIN1: 'no' > PIN1 state: 'disabled' > PIN1 retries: '3' > PUK1 retries: '10' > PIN2 state: 'enabled-not-verified' > PIN2 retries: '3' > PUK2 retries: '10' > Application [3]: > Application type: 'unknown (0)' > Application state: 'detected' > Application ID: > A0:00:00:00:63:50:4B:43:53:2D:31:35 > Personalization state: 'unknown' > UPIN replaces PIN1: 'no' > PIN1 state: 'not-initialized' > PIN1 retries: '0' > PUK1 retries: '0' > PIN2 state: 'not-initialized' > PIN2 retries: '0' > PUK2 retries: '0' > root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-signal-info > error: couldn't get signal info: QMI protocol error (74): > 'InformationUnavailable' > root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-signal-strength > [/dev/cdc-wdm0] Successfully got signal strength > Current: > Network 'none': '-128 dBm' > RSSI: > Network 'none': '-128 dBm' > ECIO: > Network 'none': '-2.5 dBm' > IO: '-106 dBm' > SINR (8): '9.0 dB' > root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 > --nas-get-system-selection-preference > [/dev/cdc-wdm0] Successfully got system selection preference > Emergency mode: 'no' > Mode preference: 'lte' > Band preference: 'bc-0-a-system, bc-0-b-system, bc-1-all-blocks, bc-2, > bc-3-a-system, bc-4-all-blocks, bc-5-all-blocks, gsm-dcs-1800, > gsm-900-extended, gsm-900-primary, bc-6, bc-7, bc-8, bc-9, bc-10, > bc-11, gsm-450, gsm-480, gsm-750, gsm-850, gsm-900-railways, > gsm-pcs-1900, wcdma-2100, wcdma-pcs-1900, wcdma-dcs-1800, > wcdma-1700-us, wcdma-850-us, wcdma-800, bc-12, bc-14, bc-15, > wcdma-2600, wcdma-900, wcdma-1700-japan, bc-16, bc-17, bc-18, bc-19, > wcdma-850-japan, wcdma-1500' > LTE band preference: '1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, > 17, 18, 19, 20, 21, 24, 25, 26, 28, 29, 31, 33, 34, 35, 36, 37, 38, > 39, 40, 41, 42, 43' > Network selection preference: 'automatic' > Service domain preference: 'cs-ps' > GSM/WCDMA acquisition order preference: 'gsm' > Acquisition order preference: none, none > root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-operator-name > error: couldn't get operator name data: QMI protocol error (71): > 'InvalidQmiCommand' > root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-serving-system > [/dev/cdc-wdm0] Successfully got serving system: > Registration state: 'not-registered-searching' > CS: 'detached' > PS: 'detached' > Selected network: 'unknown' > Radio interfaces: '1' > [0]: 'none' > Data service capabilities: '0' > Detailed status: > Status: 'none' > Capability: 'cs-ps' > HDR Status: 'none' > HDR Hybrid: 'no' > Forbidden: 'no' > root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-home-network > error: couldn't get home network: QMI protocol error (16): 'NotProvisioned' > root@bionic-armhf:~# qmicli -d /dev/cdc-wdm0 --nas-get-system-info > [/dev/cdc-wdm0] Successfully got system info: > LTE service: > Status: 'none' > True Status: 'none' > Preferred data path: 'no' > SIM reject info: 'available' > root@bionic-armhf:~# echo "APN=vzwinternet" > /etc/qmi-network.conf > root@bionic-armhf:~# echo "PROXY=yes" >> /etc/qmi-network.conf > root@bionic-armhf:~# qmi-network /dev/cdc-wdm0 start > Loading profile at /etc/qmi-network.conf... > APN: vzwinternet > APN user: unset > APN password: unset > qmi-proxy: yes > Checking data format with 'qmicli -d /dev/cdc-wdm0 > --wda-get-data-format --device-open-proxy'... > Device link layer protocol retrieved: raw-ip > Getting expected data format with 'qmicli -d /dev/cdc-wdm0 > --get-expected-data-format'... > Expected link layer protocol retrieved: raw-ip > Device and kernel link layer protocol match: raw-ip > Starting network with 'qmicli -d /dev/cdc-wdm0 > --wds-start-network=apn='vzwinternet' --client-no-release-cid > --device-open-proxy'... > error: couldn't start network: QMI protocol error (14): 'CallFailed' > call end reason (3): generic-no-service > verbose call end reason (3,2001): [cm] no-service > Saving state at /tmp/qmi-network-state-cdc-wdm0... (CID: 3) > error: network start failed, no packet data handle > Clearing state at /tmp/qmi-network-state-cdc-wdm0... > > Seems like qmicli is telling me I'm not registered on a network so > perhaps a SIM/provisioning issue? >
Greetings, I've been working on this modem again recently after getting a proper SIM and Cat-M1 dataplan which was the connection issue I faced. Now I'm running into an issue where I can connect, obtain IP info, and ping but can't do IP related activity like file transfers via HTTP. The issue appears to be the fact that the MTU is 64 bytes which appears to be a CAT M-1 thing. Any idea how to deal with this small MTU? Best Regards, Tim _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
