← Back to team overview

kernel-packages team mailing list archive

[Bug 1527914] Re: Huawei E3372 is not detected and cannot be used


This is what I see when I plug mine in:

The key lines are:

Jan 28 16:19:23 TimeBox systemd[1]: Starting USB_ModeSwitch...
Jan 28 16:19:23 TimeBox systemd[1]: usb_modeswitch@1-1.5-1-1.5:1.0.service: main process exited, code=exited, status=1/FAILURE

It seems Ubuntu is trying to do the wrong thing, it is trying to do
systemctl start usb_modeswitch@1-1.5-1-1.5:1.0 when in reality the
command should be:

$ systemctl start usb_modeswitch@1-1.5:1.0

When I run the correct command, I see this in syslog:

Jan 28 16:34:05 TimeBox systemd[1]: Starting USB_ModeSwitch...
Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: Could not read attribute: No such file or directory
Jan 28 16:34:06 TimeBox usb_modeswitch: switch device 12d1:14fe on 001/008
Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: message repeated 2 times: [ Could not read attribute: No such file or directory]
Jan 28 16:34:07 TimeBox usb_modeswitch[10502]: usb_modeswitch: switched to 12d1:14fe on 1/8
Jan 28 16:34:08 TimeBox usb_modeswitch_dispatcher[10502]: Unable to open bind list file: No such file or directory
Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: add device ID 12d1:14fe to driver option
Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: please report the device ID to the Linux USB developers!
Jan 28 16:34:15 TimeBox systemd[1]: Started USB_ModeSwitch.

So seems this is an unsupported device still? (I'm on Ubuntu 15.04

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Huawei E3372 is not detected and cannot be used

Status in linux package in Ubuntu:

Bug description:
  It does appear in lsb_usb, but networkmanager doesn't react to it or
  give me option to connect. It works in ubuntu-12.04.4-dvd-amd64.iso.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11 [modified: boot/vmlinuz-4.3.0-2-generic]
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
   /dev/snd/controlC0:  mikaela    1352 F.... pulseaudio
   /dev/snd/controlC1:  mikaela    1352 F.... pulseaudio
  CurrentDesktop: MATE
  Date: Sat Dec 19 20:35:36 2015
  HibernationDevice: RESUME=UUID=431ec214-73ef-4058-b283-5721bb5a45d2
  InstallationDate: Installed on 2015-12-12 (7 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151212)
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 13d3:3414 IMC Networks
   Bus 001 Device 006: ID 12d1:14dc Huawei Technologies Co., Ltd.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic.efi.signed root=UUID=ab0e7270-40bc-4a68-a541-59fd96690354 ro rw acpi_osi=
   linux-restricted-modules-4.3.0-2-generic N/A
   linux-backports-modules-4.3.0-2-generic  N/A
   linux-firmware                           1.154
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JX.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JX.204:bd05/07/2015:svnASUSTeKCOMPUTERINC.:pnX550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to: