Arch Linux

vosskaem

Member

Registered: 2017-08-06

Posts: 10

Huawei ME936 Modem does not connect [solved]

I have a dual boot system with Ubuntu 16.04 and ArchLinux.

With Ubuntu the Modem works following this https://www.linux-onlineshop.de/forum/i … postID=590

But under ArchLinux the modem does not work in the same way as under Ubuntu before I added the special udev rule.

I am using Gnome with NetworkManager.

# uname -a
Linux m42a 4.12.4-1-ARCH #1 SMP PREEMPT Fri Jul 28 18:54:18 UTC 2017 x86_64 GNU/Linux

# lsusb | grep Hua
Bus 001 Device 002: ID 12d1:15bb Huawei Technologies Co., Ltd.

# cat /etc/modules-load.d/huawai-me936.conf
qcserial
usbserial

# cat /etc/modprobe.d/huawai-me936.conf 
options usbserial vendor=0x12d1 product=0x15bb

# cat /etc/udev/rules.d/77-mm-huawei-configuration.rules 
ACTION=="add|change", SUBSYSTEM=="usb", \
ENV{DEVTYPE}=="usb_device", \
ATTR{idVendor}=="12d1", ATTR{idProduct}=="15bb", \
ATTR{bNumConfigurations}=="3", ATTR{bConfigurationValue}!="3" \
ATTR{bConfigurationValue}="3

# lsmod | grep serial
qcserial               20480  0
usb_wwan               20480  2 qcserial,option
usbserial              36864  9 qcserial,option,usb_wwan
usbcore               208896  13 usbnet,uvcvideo,usbhid,cdc_mbim,qcserial,cdc_ncm,cdc_wdm,usbserial,xhci_pci,btusb,option,usb_wwan,xhci_hcd

# mmcli -m 0 

/org/freedesktop/ModemManager1/Modem/0 (device id 'bc5a3264c511b500e041b75cbce7267345a3e8a0')
  -------------------------
  Hardware |   manufacturer: 'Huawei Technologies Co., Ltd.'
           |          model: 'ME936'
           |       revision: '11.350.20.01.00'
           |      supported: 'gsm-umts, lte'
           |        current: 'gsm-umts, lte'
           |   equipment id: '862595020674178'
  -------------------------
  System   |         device: '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2'
           |        drivers: 'generic, cdc_ncm'
           |         plugin: 'Huawei'
           |   primary port: 'ttyUSB2'
           |          ports: 'wwp0s20f0u2c2 (net), ttyUSB2 (at), ttyUSB3 (at)'
  -------------------------
  Numbers  |           own : 'unknown'
  -------------------------
  Status   |           lock: 'none'
           | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)'
           |          state: 'registered'
           |    power state: 'on'
           |    access tech: 'umts'
           | signal quality: '61' (recent)
  -------------------------
  Modes    |      supported: 'allowed: 2g; preferred: none
           |                  allowed: 3g; preferred: none
           |                  allowed: 4g; preferred: none
           |                  allowed: 2g, 3g, 4g; preferred: none'
           |        current: 'allowed: 2g, 3g, 4g; preferred: none'
  -------------------------
  Bands    |      supported: 'unknown'
           |        current: 'unknown'
  -------------------------
  IP       |      supported: 'ipv4, ipv6, ipv4v6'
  -------------------------
  3GPP     |           imei: '862595020674178'
           |  enabled locks: 'none'
           |    operator id: 'unknown'
           |  operator name: 'o2-de'
           |   subscription: 'unknown'
           |   registration: 'home'
  -------------------------
  SIM      |           path: '/org/freedesktop/ModemManager1/SIM/0'

  -------------------------
  Bearers  |          paths: '/org/freedesktop/ModemManager1/Bearer/0'

# ll /dev/ttyU*
crw-rw---- 1 root uucp 188, 0  6. Aug 15:44 /dev/ttyUSB0
crw-rw---- 1 root uucp 188, 1  6. Aug 15:44 /dev/ttyUSB1
crw-rw---- 1 root uucp 188, 2  6. Aug 17:00 /dev/ttyUSB2
crw-rw---- 1 root uucp 188, 3  6. Aug 15:44 /dev/ttyUSB3

This looks like unter Ubuntu before I added the udev rule. With that udev rule there is only one ttyUSB under Ubuntu.

Maybe the udev rule does not work as expected under ArchLinux ?!?

Any idea?

Last edited by vosskaem (2017-08-07 10:37:45)

vosskaem

Member

Registered: 2017-08-06

Posts: 10

Re: Huawei ME936 Modem does not connect [solved]

I was right, the udev rule does not work
There is a " missing at the end... Copy and paste error...