Using an ATT (Sierra Wireless/Netgear) 340u on Slate AX

Technical Support for Routers
1

I’m trying to do the same thing as in this topic: Using an ATT (seirra wireless/netgear) 340u on AR150

I’ve installed all the “QMI” stuff but it’s still not seen as an available Tethering/Modem device.

It’s being picked up as a “cdc_mbim” device (just as it is on my Linux laptop, which does work with this device) but I think it may not be mode-switching the usb (and “usb-modeswitch” is installed).

Here’s the relevant lines from “dmesg”:

[ 2942.117880] usb 1-1.2: config 1 has an invalid interface number: 9 but max is 0
[ 2942.117911] usb 1-1.2: config 1 has no interface number 0
[ 2942.124324] usb 1-1.2: config 2 has an invalid interface number: 12 but max is 1
[ 2942.129686] usb 1-1.2: config 2 has an invalid interface number: 13 but max is 1
[ 2942.137060] usb 1-1.2: config 2 has an invalid interface number: 13 but max is 1
[ 2942.144419] usb 1-1.2: config 2 has no interface number 0
[ 2942.151791] usb 1-1.2: config 2 has no interface number 1
[ 2942.159789] usb-storage 1-1.2:1.9: USB Mass Storage device detected
[ 2942.163169] usb-storage: probe of 1-1.2:1.9 failed with error -5
[ 2945.421058] usb 1-1.2: USB disconnect, device number 15
[ 2945.867410] usb 1-1.2: new high-speed USB device number 16 using xhci-hcd
[ 2945.987791] usb 1-1.2: config 1 has an invalid interface number: 8 but max is 4
[ 2945.987824] usb 1-1.2: config 1 has an invalid interface number: 9 but max is 4
[ 2945.993980] usb 1-1.2: config 1 has no interface number 1
[ 2946.001237] usb 1-1.2: config 1 has no interface number 4
[ 2946.007150] usb 1-1.2: config 2 has an invalid interface number: 12 but max is 1
[ 2946.012184] usb 1-1.2: config 2 has an invalid interface number: 13 but max is 1
[ 2946.019817] usb 1-1.2: config 2 has an invalid interface number: 13 but max is 1
[ 2946.027039] usb 1-1.2: config 2 has no interface number 0
[ 2946.034439] usb 1-1.2: config 2 has no interface number 1
[ 2946.077946] cdc_mbim 1-1.2:2.12: cdc-wdm0: USB WDM device
[ 2946.078776] cdc_mbim 1-1.2:2.12 wwan0: register 'cdc_mbim' at usb-xhci-hcd.0.auto-1.2, CDC MBIM, 96:7d:a3:e9:aa:8a
[ 2946.084852] usb 1-1.2: usbfs: process 1496 (usbmode) did not claim interface 13 before use
[ 2946.092863] usb 1-1.2: usbfs: process 1496 (usbmode) did not claim interface 13 before use
[ 2946.101071] usb 1-1.2: usbfs: process 1496 (usbmode) did not claim interface 13 before use
[ 2946.309590] usb 1-1.2: usbfs: interface 12 claimed by cdc_mbim while 'usbmode' sets config #1
[ 2946.468875] usb 1-1.2: usbfs: process 1779 (usbmode) did not claim interface 13 before use
[ 2946.468916] usb 1-1.2: usbfs: process 1779 (usbmode) did not claim interface 13 before use
[ 2946.476055] usb 1-1.2: usbfs: process 1779 (usbmode) did not claim interface 13 before use
[ 2946.684864] usb 1-1.2: usbfs: interface 12 claimed by cdc_mbim while 'usbmode' sets config #1

… and “lsusb”:

Bus 001 Device 016: ID 1199:9051 Sierra Wireless, Incorporated AirCard 340U

root@GL-AXT1800:~# ls -las /dev/cdc*
     0 crw-------    1 root     root      180, 176 Feb  9 10:25 /dev/cdc-wdm0

… any hints as to what to do/try next?

2

Do you set mbim mode for your Netgear 340U?

Please execute the instruction:
AT+QCFG=“usbnet”

And please contact the supplier of this product to confirm which ‘usbnet’ modes are supported?

3

How would I do this on the Slate?

4

This may work, but you can SSH into your router and run the following:

dmesg | grep ttyUSB - see if your modem is making ports available, though your logs did not show any. If not, the following commands will not work.

gl_modem -D -B 1-1.2 - Verify the control port ( USB2 usually)

gl_modem -D -B 1-1.2 AT /dev/ttyUSB2 AT+QCFG=“usbnet”

I’m not familiar with your USB WWAN device, but have you looked at the installation section on this page?

5

The only one I see that looks promising is /dev/ttyMSM0 (and trying that port with the commands above segfaults).

If I plug it into my Linux laptop (and my Chromebook, I was pleased to discover) it is recognized and passes data, I guess it’s a mode-switching issue (modem not in database?)

I’ve seen that page, all packages are up-to-date:

root@GL-AXT1800:~# gl_modem -D -B 1-1.2 AT /dev/ttyMSM0
Segmentation fault
root@GL-AXT1800:~# gl_modem -D -B 1-1.2 AT /dev/ttyMSM0 AT+QCFG=“usbnet”
Segmentation fault
root@GL-AXT1800:~# opkg update
Downloading https://fw.gl-inet.com/releases/v21.02-SNAPSHOT/kmod-4.1.0/arm_cortex-a7/ip60xx/Packages.gz
Updated list of available packages in /var/opkg-lists/glinet_core
Downloading https://fw.gl-inet.com/releases/v21.02-SNAPSHOT/packages-4.1/arm_cortex-a7/glinet/Packages.gz
Updated list of available packages in /var/opkg-lists/glinet_gli_pub
Downloading https://fw.gl-inet.com/releases/v21.02-SNAPSHOT/packages-4.0/arm_cortex-a7/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/opnwrt_packages
Updating database.
Database update completed.
root@GL-AXT1800:~# opkg install comgt kmod-usb-serial kmod-usb-serial-option kmod-usb-serial-wwan usb-modeswitch
Package comgt (0.32-33) installed in root is up to date.
Package kmod-usb-serial (4.4.60-1) installed in root is up to date.
Package kmod-usb-serial-option (4.4.60-1) installed in root is up to date.
Package kmod-usb-serial-wwan (4.4.60-1) installed in root is up to date.
Package usb-modeswitch (2017-12-19-f40f84c2-2) installed in root is up to date.
6

Huh. Apparently it’s covered by the usb-modeswitch package; inside /etc/usb-mode.json I see:

                "1199:9051": {
                        "*": {
                                "msg": [  ],
                                "config": 1
                        }
                },

:confused:

7

What is your firmware version?

8

Yeah, that looks like a serial port, but not valid for the modem/AT command.

What port/interface did the aircard use in linux? Eth0/1 (tether) or another port (ex. ttyUSBx).

Perhaps the following set of packages are used with your dongle. If you’ve exhausted the driver options, there are few results for your device on openwrt forums to get a better idea about your modem configuration.

1. Add support for MBIM devices

kmod-usb-net-cdc-mbim Kernel module for MBIM Devices
umbim MBIM modem utility
opkg update
opkg install kmod-usb-net-cdc-mbim umbim
2. Add support for PC Interface (ttyUSB0) - You need it if you want to send AT commands, for eg. to check your balance by USSD.

kmod-usb-serial-option
kmod-usb-serial
kmod-usb-serial-wwan
opkg update
opkg install kmod-usb-serial-option kmod-usb-serial kmod-usb-serial-wwan
3. Add support for FlashCard of your dongle - refer to: USB Storage

Installation
1. Install all the needed packages

opkg update
opkg install usb-modeswitch kmod-mii kmod-usb-net kmod-usb-wdm kmod-usb-net-qmi-wwan uqmi
9

More information, from my Linux laptop (it’s long, so also attached to the post).
wanmodem-syslog.zip (3.7 KB)

Feb 11 14:44:28 xps-9320 kernel: [102464.303131][T42197] usb 3-1: new high-speed USB device number 30 using xhci_hcd
Feb 11 14:44:28 xps-9320 kernel: [102464.492203][T42197] usb 3-1: config 1 has an invalid interface number: 9 but max is
 0
Feb 11 14:44:28 xps-9320 kernel: [102464.492212][T42197] usb 3-1: config 1 has no interface number 0
Feb 11 14:44:28 xps-9320 kernel: [102464.492712][T42197] usb 3-1: config 2 has an invalid interface number: 12 but max i
s 1
Feb 11 14:44:28 xps-9320 kernel: [102464.492720][T42197] usb 3-1: config 2 has an invalid interface number: 13 but max i
s 1
Feb 11 14:44:28 xps-9320 kernel: [102464.492722][T42197] usb 3-1: config 2 has an invalid interface number: 13 but max i
s 1
Feb 11 14:44:28 xps-9320 kernel: [102464.492725][T42197] usb 3-1: config 2 has no interface number 0
Feb 11 14:44:28 xps-9320 kernel: [102464.492727][T42197] usb 3-1: config 2 has no interface number 1
Feb 11 14:44:28 xps-9320 kernel: [102464.493564][T42197] usb 3-1: New USB device found, idVendor=1199, idProduct=0fff, bcdDevice= 0.06
Feb 11 14:44:28 xps-9320 kernel: [102464.493575][T42197] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 11 14:44:28 xps-9320 kernel: [102464.493579][T42197] usb 3-1: Product: AirCard 340U
Feb 11 14:44:28 xps-9320 kernel: [102464.493582][T42197] usb 3-1: Manufacturer: Sierra Wireless, Incorporated
Feb 11 14:44:28 xps-9320 kernel: [102464.493584][T42197] usb 3-1: SerialNumber: 013323002658699
Feb 11 14:44:28 xps-9320 kernel: [102464.496836][T42197] usb-storage 3-1:1.9: USB Mass Storage device detected
Feb 11 14:44:28 xps-9320 kernel: [102464.510292][T42197] usb-storage: probe of 3-1:1.9 failed with error -5
Feb 11 14:44:28 xps-9320 mtp-probe: checking bus 3, device 30: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Feb 11 14:44:28 xps-9320 mtp-probe: bus: 3, device: 30 was not an MTP device
Feb 11 14:44:28 xps-9320 systemd[1]: Created slice Slice /system/usb_modeswitch.
Feb 11 14:44:28 xps-9320 systemd[1]: Starting USB_ModeSwitch_3-1...
Feb 11 14:44:29 xps-9320 mtp-probe: checking bus 3, device 30: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Feb 11 14:44:29 xps-9320 mtp-probe: bus: 3, device: 30 was not an MTP device
Feb 11 14:44:29 xps-9320 usb_modeswitch: switch device 1199:0fff on 003/030
Feb 11 14:44:29 xps-9320 kernel: [102465.201357][T46904] usb-storage 3-1:2.12: USB Mass Storage device detected
Feb 11 14:44:29 xps-9320 kernel: [102465.205606][T46857] usbcore: registered new interface driver cdc_ncm
Feb 11 14:44:29 xps-9320 vmnetBridge: RTM_NEWLINK: name:wwan0 index:16 flags:0x00001082
Feb 11 14:44:29 xps-9320 kernel: [102465.240499][T46904] cdc_mbim 3-1:2.12: cdc-wdm2: USB WDM device
Feb 11 14:44:29 xps-9320 kernel: [102465.240674][T46904] cdc_mbim 3-1:2.12 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-1, CDC MBIM, 5a:ef:47:f4:47:2c
Feb 11 14:44:29 xps-9320 kernel: [102465.240951][T46857] usbcore: registered new interface driver cdc_mbim
Feb 11 14:44:29 xps-9320 systemd-udevd[46916]: Using default interface naming scheme 'v249'.
Feb 11 14:44:30 xps-9320 root: usb_modeswitch: switched to 1199:0fff on 003/030
Feb 11 14:44:31 xps-9320 systemd[1]: usb_modeswitch@3-1.service: Deactivated successfully.
Feb 11 14:44:31 xps-9320 systemd[1]: Finished USB_ModeSwitch_3-1.
Feb 11 14:44:31 xps-9320 ModemManager[1166]: opening device...
Feb 11 14:44:31 xps-9320 ModemManager[1166]: cannot connect to proxy: Could not connect: Connection refused
Feb 11 14:44:31 xps-9320 ModemManager[1166]: spawning new mbim-proxy (try 1)...
Feb 11 14:44:31 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Read max control message size from descriptors file: 4096
Feb 11 14:44:31 xps-9320 ModemManager[1166]: <info>  [cdc-wdm2/mbim] MBIM device is not QMI capable
Feb 11 14:44:31 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] channel destroyed
Feb 11 14:44:31 xps-9320 kernel: [102467.573370][T42197] usb 3-1: USB disconnect, device number 30
Feb 11 14:44:31 xps-9320 kernel: [102467.573599][T42197] cdc_mbim 3-1:2.12 wwan0: unregister 'cdc_mbim' usb-0000:00:14.0-1, CDC MBIM
Feb 11 14:44:31 xps-9320 vmnetBridge: RTM_DELLINK: name:wwan0 index:16 flags:0x00001082
Feb 11 14:44:31 xps-9320 ModemManager[1166]: <info>  [base-manager] port wwan0 released by device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1'
Feb 11 14:44:31 xps-9320 ModemManager[1166]: <info>  [base-manager] port cdc-wdm2 released by device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1'
Feb 11 14:44:31 xps-9320 ModemManager[1166]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1': Operation was cancelled
Feb 11 14:44:32 xps-9320 kernel: [102468.169010][T42197] usb 3-1: new high-speed USB device number 31 using xhci_hcd
Feb 11 14:44:32 xps-9320 kernel: [102468.561662][T42197] usb 3-1: config 1 has an invalid interface number: 8 but max is
 3
Feb 11 14:44:32 xps-9320 kernel: [102468.561673][T42197] usb 3-1: config 1 has no interface number 1
Feb 11 14:44:32 xps-9320 kernel: [102468.562197][T42197] usb 3-1: config 2 has an invalid interface number: 12 but max is 2
Feb 11 14:44:32 xps-9320 kernel: [102468.562207][T42197] usb 3-1: config 2 has an invalid interface number: 13 but max is 2
Feb 11 14:44:32 xps-9320 kernel: [102468.562209][T42197] usb 3-1: config 2 has an invalid interface number: 13 but max is 2
Feb 11 14:44:32 xps-9320 kernel: [102468.562212][T42197] usb 3-1: config 2 has an invalid interface number: 9 but max is 2
Feb 11 14:44:32 xps-9320 kernel: [102468.562215][T42197] usb 3-1: config 2 has no interface number 0
Feb 11 14:44:32 xps-9320 kernel: [102468.562217][T42197] usb 3-1: config 2 has no interface number 1
Feb 11 14:44:32 xps-9320 kernel: [102468.562219][T42197] usb 3-1: config 2 has no interface number 2
Feb 11 14:44:32 xps-9320 kernel: [102468.563027][T42197] usb 3-1: New USB device found, idVendor=1199, idProduct=9051, bcdDevice= 0.06
Feb 11 14:44:32 xps-9320 kernel: [102468.563038][T42197] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 11 14:44:32 xps-9320 kernel: [102468.563042][T42197] usb 3-1: Product: AirCard 340U
Feb 11 14:44:32 xps-9320 kernel: [102468.563045][T42197] usb 3-1: Manufacturer: Sierra Wireless, Incorporated
Feb 11 14:44:32 xps-9320 kernel: [102468.563047][T42197] usb 3-1: SerialNumber: 013323002658699
Feb 11 14:44:32 xps-9320 kernel: [102468.590752][T42197] cdc_mbim 3-1:2.12: cdc-wdm2: USB WDM device
Feb 11 14:44:32 xps-9320 kernel: [102468.591015][T42197] cdc_mbim 3-1:2.12 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-1, CDC MBIM, 5a:ef:47:f4:47:2c
Feb 11 14:44:32 xps-9320 kernel: [102468.592002][T42197] usb-storage 3-1:2.9: USB Mass Storage device detected
Feb 11 14:44:32 xps-9320 vmnetBridge: RTM_NEWLINK: name:wwan0 index:17 flags:0x00001082
Feb 11 14:44:32 xps-9320 kernel: [102468.592495][T42197] scsi host2: usb-storage 3-1:2.9
Feb 11 14:44:32 xps-9320 mtp-probe: checking bus 3, device 31: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Feb 11 14:44:32 xps-9320 mtp-probe: bus: 3, device: 31 was not an MTP device
Feb 11 14:44:32 xps-9320 systemd[1]: Starting USB_ModeSwitch_3-1...
Feb 11 14:44:33 xps-9320 NetworkManager[1080]: <info>  [1676155473.0655] audit: op="statistics" interface="eth0" ifindex=15 args="2000" pid=2902 uid=1000 result="success"
Feb 11 14:44:33 xps-9320 NetworkManager[1080]: <info>  [1676155473.0746] audit: op="statistics" interface="wlan0" ifindex=7 args="2000" pid=2902 uid=1000 result="success"
Feb 11 14:44:33 xps-9320 usb_modeswitch: switch device 1199:9051 on 003/031
Feb 11 14:44:33 xps-9320 systemd-udevd[46857]: Using default interface naming scheme 'v249'.
Feb 11 14:44:33 xps-9320 systemd[1]: usb_modeswitch@3-1.service: Deactivated successfully.
Feb 11 14:44:33 xps-9320 systemd[1]: Finished USB_ModeSwitch_3-1.
Feb 11 14:44:33 xps-9320 mtp-probe: checking bus 3, device 31: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Feb 11 14:44:33 xps-9320 mtp-probe: bus: 3, device: 31 was not an MTP device
Feb 11 14:44:33 xps-9320 kernel: [102469.657351][T44634] scsi 2:0:0:0: Direct-Access     Aircard  Disk Drive       1.00 PQ: 0 ANSI: 2
Feb 11 14:44:33 xps-9320 kernel: [102469.657907][T44634] sd 2:0:0:0: Attached scsi generic sg1 type 0
Feb 11 14:44:33 xps-9320 kernel: [102469.659066][T46938] sd 2:0:0:0: Power-on or device reset occurred
Feb 11 14:44:33 xps-9320 kernel: [102469.659711][T44646] sd 2:0:0:0: [sdc] Media removed, stopped polling
Feb 11 14:44:33 xps-9320 kernel: [102469.660363][T44646] sd 2:0:0:0: [sdc] Attached SCSI removable disk
Feb 11 14:44:34 xps-9320 systemd-udevd[46914]: sdc: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdc' failed with exit code 1.
Feb 11 14:44:34 xps-9320 ModemManager[1166]: opening device...
Feb 11 14:44:34 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Read max control message size from descriptors file: 4096
Feb 11 14:44:35 xps-9320 ModemManager[1166]: <info>  [cdc-wdm2/mbim] MBIM device is not QMI capable
Feb 11 14:44:35 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] channel destroyed
Feb 11 14:44:35 xps-9320 ModemManager[1166]: <info>  [device /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1] creating modem with plugin 'sierra' and '2' ports
Feb 11 14:44:35 xps-9320 ModemManager[1166]: <info>  [base-manager] modem for device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1' successfully created
Feb 11 14:44:35 xps-9320 ModemManager[1166]: opening device...
Feb 11 14:44:35 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Read max control message size from descriptors file: 4096
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Opening device with flags 'version-info, proxy, mbim, expect-indications'...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] created endpoint
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] creating MBIM device...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] MBIM device created
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] opening MBIM device...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: opening device...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Read max control message size from descriptors file: 4096
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] MBIM device open
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Checking version info (15 retries)...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] QMI Device supports 22 services:
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    ctl (1.5)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    wds (1.16)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    dms (1.13)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    nas (1.25)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    qos (1.3)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    wms (1.8)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    pds (1.13)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    auth (1.2)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    at (1.2)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    voice (2.1)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    cat2 (2.11)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    uim (1.12)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    pbm (1.4)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    loc (2.0)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    sar (1.0)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    ims (1.0)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    ts (1.0)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    tmd (1.0)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    wda (1.0)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    csvt (1.0)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    cat (2.11)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2]    unknown [0xf0] (1.0)
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Enabling QMI indications via MBIM...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] enabled QMI indications via MBIM
Feb 11 14:44:36 xps-9320 ModemManager[1166]: <info>  [modem0/cdc-wdm2/mbim] MBIM device is QMI capable
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Allocating new client ID...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Registered 'dms' (version 1.13) client with ID '3'
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Allocating new client ID...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Registered 'nas' (version 1.25) client with ID '3'
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Allocating new client ID...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Registered 'pds' (version 1.13) client with ID '1'
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Allocating new client ID...
Feb 11 14:44:36 xps-9320 ModemManager[1166]: [/dev/cdc-wdm2] Registered 'loc' (version 2.0) client with ID '1'
Feb 11 14:44:36 xps-9320 ModemManager[1166]: <info>  [modem0] QMI-based capability and mode switching support enabled
Feb 11 14:44:36 xps-9320 ModemManager[1166]: <warn>  [modem0] couldn't load carrier config: QMI PDC not supported
Feb 11 14:44:36 xps-9320 ModemManager[1166]: <warn>  [modem0] couldn't query SIM slots: NoDeviceSupport
Feb 11 14:44:36 xps-9320 ModemManager[1166]: <warn>  [modem0/sim0] couldn't load list of emergency numbers: No AT port available to run command
Feb 11 14:44:36 xps-9320 ModemManager[1166]: <warn>  [modem0/sim0] couldn't load list of preferred networks: No AT port available to run command
Feb 11 14:44:36 xps-9320 ModemManager[1166]: <warn>  [modem0] couldn't load UE mode of operation for EPS: No AT port available to run command
Feb 11 14:44:36 xps-9320 ModemManager[1166]: <warn>  [modem0] couldn't load initial EPS bearer settings: LTE attach status info is unsupported
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <warn>  [modem0] couldn't load supported assistance data types: QMI protocol error (5): 'ClientIdsExhausted'
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <warn>  [modem0] couldn't open ports during Modem SIM hot swap enabling: Couldn't get primary port
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] state changed (unknown -> disabled)
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.0590] manager: (cdc-wdm2): new Broadband device (/org/freedesktop/NetworkManager/Devices/24)
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.0593] device (cdc-wdm2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.0596] device (cdc-wdm2): modem state 'enabling'
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.0598] device (cdc-wdm2): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.0601] policy: auto-activating connection 'T-Mobile' (b4835599-4d0d-4ff3-b352-037f415e61ef)
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.0606] device (cdc-wdm2): Activation: starting connection 'T-Mobile' (b4835599-4d0d-4ff3-b352-037f415e61ef)
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.0606] device (cdc-wdm2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] state changed (disabled -> enabling)
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] simple connect started...
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] power state updated: on
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] state changed (enabling -> enabled)
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] simple connect state (5/8): register
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] 3GPP registration state changed (unknown -> registering)
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] 3GPP registration state changed (registering -> home)
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] state changed (enabled -> registered)
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] simple connect state (6/8): bearer
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] simple connect state (7/8): connect
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] state changed (registered -> connecting)
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] state changed (connecting -> connected)
Feb 11 14:44:37 xps-9320 ModemManager[1166]: <info>  [modem0] simple connect state (8/8): all done
Feb 11 14:44:37 xps-9320 vmnetBridge: RTM_NEWLINK: name:wwan0 index:17 flags:0x000110c3
Feb 11 14:44:37 xps-9320 vmnetBridge: Adding interface wwan0 index:17
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6333] device (cdc-wdm2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 11 14:44:37 xps-9320 vmnetBridge: RTM_NEWLINK: name:wwan0 index:17 flags:0x000110c3
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6343] device (cdc-wdm2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 11 14:44:37 xps-9320 avahi-daemon[1076]: Joining mDNS multicast group on interface wwan0.IPv4 with address 100.66.19.229.
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6345] modem-broadband[cdc-wdm2]: IPv4 static configuration:
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6345] modem-broadband[cdc-wdm2]:   address 100.66.19.229/30 brd* 100.66.19.231 lft forever pref forever lifetime 102449-0[0,0] src wwan
Feb 11 14:44:37 xps-9320 avahi-daemon[1076]: New relevant interface wwan0.IPv4 for mDNS.
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6345] modem-broadband[cdc-wdm2]:   gateway 100.66.19.230
Feb 11 14:44:37 xps-9320 avahi-daemon[1076]: Registering new address record for 100.66.19.229 on wwan0.IPv4.
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6345] modem-broadband[cdc-wdm2]:   DNS 10.177.0.34
Feb 11 14:44:37 xps-9320 vmnetBridge: RTM_NEWROUTE: index:17
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6345] modem-broadband[cdc-wdm2]:   DNS 10.177.0.210
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6345] modem-broadband[cdc-wdm2]:   MTU 1430
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <warn>  [1676155477.6346] device (cdc-wdm2): retrieving IP configuration failed: modem IP method unsupported
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6366] device (cdc-wdm2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Feb 11 14:44:37 xps-9320 vmnetBridge: Stopped bridge eth0 to virtual network 0.
Feb 11 14:44:37 xps-9320 vmnetBridge: Started bridge wwan0 to virtual network 0.
Feb 11 14:44:37 xps-9320 dbus-daemon[1078]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=1080 comm="/usr/sbin/NetworkManager --no-daemon " label="kernel")
Feb 11 14:44:37 xps-9320 systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 11 14:44:37 xps-9320 dbus-daemon[1078]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 11 14:44:37 xps-9320 systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6630] device (cdc-wdm2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6633] device (cdc-wdm2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Feb 11 14:44:37 xps-9320 NetworkManager[1080]: <info>  [1676155477.6649] device (cdc-wdm2): Activation: successful, device activated.
10

… and relevant lines from lsusb -tv and ifconfig:

/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 31, If 9, Class=Mass Storage, Driver=usb-storage, 480M
        ID 1199:9051 Sierra Wireless, Inc.
    |__ Port 1: Dev 31, If 13, Class=CDC Data, Driver=cdc_mbim, 480M
        ID 1199:9051 Sierra Wireless, Inc.
    |__ Port 1: Dev 31, If 12, Class=Communications, Driver=cdc_mbim, 480M
        ID 1199:9051 Sierra Wireless, Inc.

wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST>  mtu 1430
        inet 100.66.19.229  netmask 255.255.255.252  broadcast 100.66.19.231
        ether 5a:ef:47:f4:47:2c  txqueuelen 1000  (Ethernet)
        RX packets 3  bytes 128 (128.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 75  bytes 13134 (13.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
11

Lizh may have been correct to verify what firmware version you are on.

The AR150 has official openwrt support so even 22.03.3 may be an option.

Are you using 3.215?

https://dl.gl-inet.com/?model=ar150

12

?? I have a Slate AX running 4.1.0

At first I’d thought she’d meant “Firmware Version of the 340U”, and this weekend I’d upgraded it via Windows to 01.13.12.14 from here: https://www.downloads.netgear.com/files/aircard/AC340U/AC340U_FW_Upgrade.exe

13

Sorry about that. I did not glean anything from the logs and went back through your original link to see if the article had any info.

Other than drivers, I’m at a loss as to why your modem does not have standard ports available for the AT command and connectivity.

14

… OK:

root@GL-AXT1800:~# opkg update
Downloading https://fw.gl-inet.com/releases/v21.02-SNAPSHOT/kmod-4.1.0/arm_cortex-a7/ip60xx/Packages.gz
Updated list of available packages in /var/opkg-lists/glinet_core
Downloading https://fw.gl-inet.com/releases/v21.02-SNAPSHOT/packages-4.1/arm_cortex-a7/glinet/Packages.gz
Updated list of available packages in /var/opkg-lists/glinet_gli_pub
Downloading https://fw.gl-inet.com/releases/v21.02-SNAPSHOT/packages-4.0/arm_cortex-a7/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/opnwrt_packages
Updating database.
Database update completed.
root@GL-AXT1800:~# opkg install kmod-usb-net-cdc-mbim umbim
Package kmod-usb-net-cdc-mbim (4.4.60-1) installed in root is up to date.
Unknown package 'umbim'.
Collected errors:
 * opkg_install_cmd: Cannot install package umbim.

No package umbim. :confused:

Package kmod-usb-serial-option (4.4.60-1) installed in root is up to date.
Package kmod-usb-serial (4.4.60-1) installed in root is up to date.
Package kmod-usb-serial-wwan (4.4.60-1) installed in root is up to date.
Updating database.
Database update completed.
root@GL-AXT1800:~#

root@GL-AXT1800:~# opkg install usb-modeswitch kmod-mii kmod-usb-net kmod-usb-wdm kmod-usb-net-qmi-wwan uqmi
Package usb-modeswitch (2017-12-19-f40f84c2-2) installed in root is up to date.
Package kmod-mii (4.4.60-1) installed in root is up to date.
Package kmod-usb-net (4.4.60-1) installed in root is up to date.
Package kmod-usb-wdm (4.4.60-1) installed in root is up to date.
Package kmod-usb-net-qmi-wwan (4.4.60-1) installed in root is up to date.
Package uqmi (2020-11-22-0a19b5b7-3) installed in root is up to date.
Updating database.

It’s just nuts- every other dongle I’d used on one of your devices just works; I have no idea what’s the deal with this particular one … :expressionless:

15

After installing the packages, does ls /dev/tty* show ttyUSB2 or any other new ports?

I’ll preface and say that I have never seen or used a 340U, but a quick search shows that its called an AT&T Beam. The only SWAG (super wild a$$ guess) that I came across looking for “AT&T Beam Linux” was about gobi/sierra drivers dated from 2013-2015 on ubuntu. I also saw other posts using the same qmi-wwan packages.

kmod-usb-net-sierrawireless and kmod-usb-serial-sierrawireless

Those packages are not installed by default, but some search results did show the availability of ttyUSB2 on some of their results.

Sorry I couldn’t be of more help.

16

That’s just it- nothing at all on the Slate, but also nothing but /dev/cdc-wdm2 on my Linux box, which seems to work … ugh.

Thanks anyway. I’ll keep banging it out for a little while longer and see if I can get anything to work. One thing I think is happening on the Slate is usb_modeswitch seems to try to happen the same time the driver does ([ 2946.084852] usb 1-1.2: usbfs: process 1496 (usbmode) did not claim interface 13 before use)

17

Possibly worth investigating in the troubleshooting section for usbmodes:

My router is not detecting the dongle. What should I do?
Try the following commands:

usbmode -l
It should respond with a message about your USB device is detected. If it does, issue the next command. If it doesn't, you might want to get help from the forum.

usbmode -s
Then wait for the dongle to get issued an IP from your ISP.

I have to issue //usbmode -l// and //usbmode -s// every time I reboot my router to detect my USB device. How can I automate it?
Include the following codes into /etc/rc.local just before exit 0:

/sbin/usbmode -l
/bin/sleep 2
/sbin/usbmode -s
18

No joy, unfortunately:

root@GL-AXT1800:~# usbmode -l
Found device: 1199:9051 (Manufacturer: "Sierra Wireless, Incorporated", Product: "AirCard 340U", Serial: "013323002658699")
root@GL-AXT1800:~# sleep 2 ; usbmode -s
root@GL-AXT1800:~# dmesg | tail -20
[   55.229657] wlan-sta0: RX AssocResp from e8:9f:80:e6:cf:87 (capab=0x1511 status=0 aid=4)
[   55.235089] wlan-sta0: associated
[   55.324998] wlan-sta0: Limiting TX power to 30 (30 - 0) dBm as advertised by e8:9f:80:e6:cf:87
[   55.445486] ath11k c000000.wifi: bss color param 0x81000000 set on vdev 1
[   55.445728] br-lan: port 4(wlan0-1) entered forwarding state
[   55.451298] br-lan: port 4(wlan0-1) entered forwarding state
[   63.464418] br-lan: port 4(wlan0-1) entered forwarding state
[  421.312153] ath11k c000000.wifi: TWT Add Dialog Event - Status: OK, DialogId: 1, VdevId: 1
[  504.087406] usb 1-1.4: usbfs: process 29556 (usbmode) did not claim interface 13 before use
[  504.087442] usb 1-1.4: usbfs: process 29556 (usbmode) did not claim interface 13 before use
[  504.094563] usb 1-1.4: usbfs: process 29556 (usbmode) did not claim interface 13 before use
[  504.303127] usb 1-1.4: usbfs: interface 12 claimed by cdc_mbim while 'usbmode' sets config #1
[  554.586355] usb 1-1.4: usbfs: process 31652 (usbmode) did not claim interface 13 before use
[  554.586392] usb 1-1.4: usbfs: process 31652 (usbmode) did not claim interface 13 before use
[  554.593514] usb 1-1.4: usbfs: process 31652 (usbmode) did not claim interface 13 before use
[  554.802125] usb 1-1.4: usbfs: interface 12 claimed by cdc_mbim while 'usbmode' sets config #1
[  612.469919] usb 1-1.4: usbfs: process 1494 (usbmode) did not claim interface 13 before use
[  612.469955] usb 1-1.4: usbfs: process 1494 (usbmode) did not claim interface 13 before use
[  612.477307] usb 1-1.4: usbfs: process 1494 (usbmode) did not claim interface 13 before use
[  612.685584] usb 1-1.4: usbfs: interface 12 claimed by cdc_mbim while 'usbmode' sets config #1
root@GL-AXT1800:~#

… and of course, no “Tethering” nor “Cellular” options on the “Internet” screen. Ah well, thanks anyway :frowning:

19

The usbfs is the sdcard on your dongle. Have you tried removing the sdcard or adding one for sh!ts and giggles? It doesn’t address the port issues, but if its hanging on the sdcard for whatever reason, its just technology with a sense of humor.

If you have a windows box, you can always install the software and change modes to see if you can find a mode that is compatible with linux and your slate. I just casually passed by statements of various modes available on the 340U in search results, so its another SWAG.

https://dl.gl-inet.com/?model=axt1800&type=beta

You also have the option of getting a fresh start with the beta versions (or reinstalling stable) and see if it automagically works with a little finessing. I did pass an article that said the qmi-wwan drivers may have conflicted with the gobi/sierra drivers on linux, so who knows.

Good luck with your slate.