Linux support for MDM9200 based products
05c6:f000 (Before USB modeswitch)
|Related products||Tube-U4G, Onyx4G|
|Kali 2021.3(a)||Works out-of-the-box|
|Kali 2020.4||Works out-of-the-box|
|Ubuntu 20.04||Works out-of-the-box|
|Debian 10.7.0||Works out-of-the-box|
Linux kernel mainline
|Support kernel versions||>= 3.7|
|Support ModemManager versions||
We found the support status failed since the commit: https://github.com/freedesktop/ModemManager/commit/bc895067ec5b4acfb71693bfbf73bae9c55a7552 Version >= 1.16.0 doesn't support for now.
There is a time delay between device pluging and device probing.
In our tests, it takes around 9~10 seconds for
/dev/ttyUSB0 .. /dev/ttyUSB3 to show up,
and take around 40~46 seconds for
mmcli -L listing detected modems.
Per our tests, the device starts running since the commit: https://github.com/freedesktop/ModemManager/commit/b67a3948b5900c9af0fd4b97f0febae52ac4a1cc
|Support versions||>= 2016-11-22|
This device has two running mode, it starts in
VID:PID=05c6:f000 and then changes to
VID:PID=05c6:6000 after switch.
The mode switch is trigged by a tool:
usb_modeswitch. Most of linux distrobutions had preinstalled up-to-date
and auto trigger
usb_modeswitch when auto detected this device.
In older linux distrobutions, you might need to trigger the mode swith manually by following command:
usb_modeswitch -W -v 05c6 -p f000 -K
You can check your device mode state with command:
lsusb | grep "05c6:". If your device is already running in mode of
05c6:6000, you needn't apply command again.