ATTENTION: To use our store you have to activate JavaScript and deactivate script blockers!  
Thank you for your understanding!

Setting up and troubleshooting UMTS/LTE modules

    Step 1
    Your SIM card must be inserted in the device.
    On most of our devices the SIM card slot is under the battery, on a few of them it is on the side.
    Important: THE SIM card will often only be recognized after a cold start of the device (switch off, then switch on again -- a restart does not count here!).

    Step 2
    If your SIM card has a PIN, Ubuntu sometimes already displays the PIN request in the login screen. However, this does not work here yet, so please cancel the query here, then log on to the system as usual. After a few seconds, the PIN prompt appears again.

    Step 3
    We'll see! It can take up to 5 minutes for the LTE module to be recognized and activated in the system by the network manager. The network manager of Ubuntu is unfortunately just a bit sluggish when integrating the hardware.

     

    Before: You can read out the required IDs in the system via "lsusb" in the terminal:
    lsusb
    The line could look like this, for example:
    Bus 001 Device 007: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270/E870 HSDPA/HSUPA Modem
    The part "ID 12d1:1003" gives us the information we need in vendor:product format. In this example, the line for /etc/modprobe.d/huawai-me936.conf would be like this:
    options usbserial vendor=0x12d1 product=0x1003

     

    TROUBLESHOOTING

    A) The module is not recognized
    If the device is identified as "any device" when setting up the connection, then the hardware was not recognized correctly. As a result, the configured connection will not work either, but this can be fixed.

    Two configurations are required to load the modules so that the UMTS/LTE module or stick can be recognized correctly:
    (Our examples are here for the Huawei ME936 we use)

    1.) sudo nano /etc/modules-load.d/huawei-me936.conf
    (The file name "huawei-me936" is arbitrary)
    Enter these two lines in this file:
    qcserial
    usbserial

    Then save and close the file.

    2.) sudo nano /etc/modprobe.d/huawei-me936.conf
    (The file name "huawei-me936" is arbitrary)
    Enter the following line in this file:
    options usbserial vendor=0x12d1 product=0x15bb
    Then save and close the file.

     

    B) The module is recognized correctly and the connection could be established. The connection establishment only works sometimes, the connection is very unstable or not possible/usable.
    In this case you can create a so-called "udev-rule":

     

    sudo nano /etc/udev/rules.d/77-mm-huawei-configuration.rules
    (The file name "77-mm-huawei-configuration" is arbitrary. To ensure that your own rules are not subsequently overwritten by system standards, you should start the file name with a high number or without a number. It is important that the files containing the rules end with.rules, otherwise they will not be executed.)

    Enter the following text block and save and close again:

    ACTION=="add|change", SUBSYSTEM=="usb", \
    ENV{DEVTYPE}=="usb_device", \
    ATTR{idVendor}=="12d1", ATTR{idProduct}=="15bb", \
    ATTR{bNumConfigurations}=="3", ATTR{bConfigurationValue}!="3" \
    ATTR{bConfigurationValue}="3"

    Here, the vendor and product IDs must also use the one that applies to your module. Our example refers to a Huawei ME936(12d1:15bb).

    Special case

    A special case is the Huawei ME906s module, which was sometimes installed as a replacement item when the ME936 was not in stock. The command 

    lsusb | grep -i huawei

    for this module results in the ID 

    12d1:ID 15c1

    The Udev rule to be entered for this device if required differs slightly from that for the ME936 module and reads:

    ACTION=="add|change", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="12d1", ATTR{idProduct}=="15c1", ATTR{bNumConfigurations}=="3", ATTR{bConfigurationValue}!="2", ATTR{bConfigurationValue}="2"