Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial and not network-manager

[Cysioland]

If you plug the modem first time after booting, it cannot connect. Hovewer, after you unplug it and plug it again, it works like a charm.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-30-generic 3.19.0-30.34
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: cysioland 2089 F.... pulseaudio
 /dev/snd/controlC0: cysioland 2089 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Oct 20 11:28:10 2015
HibernationDevice: RESUME=UUID=ed44c356-6a11-447b-94bc-88d54b0ead64
InstallationDate: Installed on 2014-10-14 (370 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Acer Extensa 5635G
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=31750940-1f18-4f57-8933-4f779556f31b ro quiet splash libata.allow_tpm=1
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-30-generic N/A
 linux-backports-modules-3.19.0-30-generic N/A
 linux-firmware 1.143.3
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-05-23 (149 days ago)
dmi.bios.date: 12/21/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.3311
dmi.board.name: BA50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5635G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Christopher M. Penalver (penalvch)]

Cysioland, thank you for reporting this and helping make Ubuntu better.

Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Cysioland (cysioland)]

Testing it was painful (mainly due to NVIDIA), but it worked.

[Christopher M. Penalver (penalvch)]

Cysioland, to see if this is already fixed in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[Cysioland (cysioland)]

I live booted a regular 15.10 publicly released image, and couldn't connect with it.

[Christopher M. Penalver (penalvch)]

Cysioland, the next step is to fully reverse commit bisect from kernel 4.2 to 4.3-rc6 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Cysioland (cysioland)]

Why did you change the kernel version? I tested only 4.0-rc6, I don't know, if it works on 4.3-rc6.

[Cysioland (cysioland)]

Sorry, I in fact did test on 4.3-rc6.

[Cysioland (cysioland)]

Actually, I installed 4.2.3, and it works like a charm. What to do next?

[Cysioland (cysioland)]

Should I upgrade to wily?

[Cysioland (cysioland)]

Something is sketchy there. I upgraded to wily, and it didn't work on the same kernel it worked on in vivid.

[Cysioland (cysioland)]

On rc6 it works only incidentally. I think it's not kernel, it's NetworkManager, because I was able to connect fine with wvdial.

[Cysioland (cysioland)]

Someone please help me with that launchpad stuff, so I can help fix this bug

[Cysioland (cysioland)]

Possibly related: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1330262

[Juha Jeronen (juha-jeronen)]

I'm getting the original variant of this issue: my Huawei E3372 (vendor:device 12d1:14dc) works only if plugged in several times. Sometimes one replug is enough, sometimes three or even four.

I'm running Linux Mint 17.2, which is based on Ubuntu 14.04 LTS, so the issue is probably older than Ubuntu 15.10.

This occurs on both the default 3.13 kernel and the updated 3.19 kernel (3.9.0-39-generic).

Attached is the output of dmesg when the modem is plugged to the USB port, both in the failed and success cases. From what I can immediately see, the device ID is detected differently in these cases, so this might indeed have something to do with usb-modeswitch and not the kernel itself.

When it fails, it seems the modem is detected as a CD-ROM, resulting in I/O errors. When it succeeds, there is no mention of a CD-ROM before the modem is detected as a HUAWEI_MOBILE.

The read errors are surprising, since to my understanding these kinds of modems first usually identify themselves as a CD-ROM (to provide Windows drivers), before performing the switch to modem mode. One possible explanation would be a race condition: maybe usb-modeswitch sometimes attempts to perform the switch while the "CD-ROM" is being read, causing both the read to fail and the modem not to perform the switch correctly.

Or maybe not. This probably needs an expert opinion :)

[dennis (dennisschneck)]

Hi,
using HUAWEI E3372 (Telekom Speedstick V).
Have the same Problem, that the Networkmanager do not work with the Stick.
Did not detect it.

see attach, some information about the system.

[AzZiD (ricardocasares)]

I have a Huawei E3372 modem, and I'm also having some issues, even though I found a way to connect.

At first the modem was not switching modes (stuck in 12d1:1f01), and lsusb output was:

Bus 003 Device 039: ID 12d1:1f01 Huawei Technologies Co., Ltd.

At this point everytime I plugged the modem the blue led stayed on (connected), but it wasn't recognized, and I couldn't use it or find it in Network Manager whatsoever.

After looking around on the internet, I found this command to switch modes which worked for me:

usb_modeswitch -J -v 0x12d1 -p 0x1f01

After issuing this command NetworkManager popup saying new ethernet connection was available and I could connect. Still, the modem was not recognized, but working. The output of lsusb was:

Bus 003 Device 039: ID 12d1:14dc Huawei Technologies Co., Ltd.

Playing around with usb_modeswitch found that switching to 0x1001 the blue led started to blink instead of being always on, and after a few seconds the modem was recognized, I tried to setup a broadband connection but I couldn't connect. Now lsusb was printing:

Bus 003 Device 039: ID 12d1:155f Huawei Technologies Co., Ltd.

I'm attaching the system log since I plug the modem till connection attempt finally times out.

I can use the modem, but not 'dialing' I would say.

Hope it helps, let me know if I can provide you with some more information.

[AzZiD (ricardocasares)]

BTW, I'm runnung 16.04