[Bug 1817410] Re: After last software update Huawei 3372H-153 modem is not working
Kevin Morgan
1817410 at bugs.launchpad.net
Fri Mar 1 19:14:50 UTC 2019
Hello
I suffered the same problem. My Huawei E353 Mobile Broadband dongle on
Ubuntu 16.04.6 LTS stopped working after the following updates:-
'Start-Date: 2019-02-23 10:10:31
Commandline: aptdaemon role='role-commit-packages' sender=':1.94'
Upgrade:
libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
libgs9:amd64 (9.26~dfsg+0-0ubuntu0.16.04.4, 9.26~dfsg+0-0ubuntu0.16.04.5),
bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.16.04.4, 9.26~dfsg+0-0ubuntu0.16.04.5),
ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.16.04.4, 9.26~dfsg+0-0ubuntu0.16.04.5),
libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.16.04.4, 9.26~dfsg+0-0ubuntu0.16.04.5),
libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12),
base-files:amd64 (9.4ubuntu4.7, 9.4ubuntu4.8)
End-Date: 2019-02-23 10:11:29
Start-Date: 2019-02-23 10:12:23
Commandline: aptdaemon role='role-commit-packages' sender=':1.94'
Upgrade:
libc6-dbg:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11),
libc6-dev:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11),
libc6:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11),
libc6:i386 (2.23-0ubuntu10, 2.23-0ubuntu11),
locales:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11),
libc-bin:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11),
libc6-i386:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11),
libc-dev-bin:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11),
multiarch-support:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11)
End-Date: 2019-02-23 10:13:02'
It stopped working after the reboot after installing these updates.
N.B. The dongle still works, however, on Ubuntu 14.04.5 LTS.
Examining the syslogs before and after the updates, the relevant entries
are:-
Before (i.e. when it worked):-
'Feb 23 10:08:27 COMPUTER usb_modeswitch: switch device 12d1:1446 on 001/004
Feb 23 10:08:27 COMPUTER kernel: [ 150.314200] usb 1-7: USB disconnect, device number 4
Feb 23 10:08:29 COMPUTER colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Feb 23 10:08:31 COMPUTER kernel: [ 154.180021] usb 1-7: new high-speed USB device number 5 using ehci-pci
Feb 23 10:08:31 COMPUTER kernel: [ 154.322549] usb 1-7: New USB device found, idVendor=12d1, idProduct=1506
Feb 23 10:08:31 COMPUTER kernel: [ 154.322555] usb 1-7: New USB device strings: Mfr=4, Product=3, SerialNumber=0
Feb 23 10:08:31 COMPUTER kernel: [ 154.322558] usb 1-7: Product: HUAWEI Mobile
Feb 23 10:08:31 COMPUTER kernel: [ 154.322561] usb 1-7: Manufacturer: Huawei Technologies
Feb 23 10:08:31 COMPUTER kernel: [ 154.336940] usb-storage 1-7:1.5: USB Mass Storage device detected
Feb 23 10:08:31 COMPUTER kernel: [ 154.337144] scsi host8: usb-storage 1-7:1.5
Feb 23 10:08:31 COMPUTER kernel: [ 154.337336] usb-storage 1-7:1.6: USB Mass Storage device detected
Feb 23 10:08:31 COMPUTER kernel: [ 154.337470] scsi host9: usb-storage 1-7:1.6
Feb 23 10:08:31 COMPUTER mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7"
Feb 23 10:08:31 COMPUTER mtp-probe: bus: 1, device: 5 was not an MTP device
Feb 23 10:08:31 COMPUTER usb_modeswitch_dispatcher[2506]: Could not read attribute: No such file or directory
Feb 23 10:08:31 COMPUTER usb_modeswitch[2506]: usb_modeswitch: switched to 12d1:1506 on 1/5
Feb 23 10:08:31 COMPUTER kernel: [ 154.482550] usbcore: registered new interface driver usbserial
Feb 23 10:08:31 COMPUTER kernel: [ 154.482587] usbcore: registered new interface driver usbserial_generic
Feb 23 10:08:31 COMPUTER kernel: [ 154.482600] usbserial: USB Serial support registered for generic
Feb 23 10:08:31 COMPUTER kernel: [ 154.604647] usbcore: registered new interface driver option
Feb 23 10:08:31 COMPUTER kernel: [ 154.604666] usbserial: USB Serial support registered for GSM modem (1-port)
Feb 23 10:08:31 COMPUTER kernel: [ 154.604757] option 1-7:1.0: GSM modem (1-port) converter detected
Feb 23 10:08:31 COMPUTER kernel: [ 154.605264] usb 1-7: GSM modem (1-port) converter now attached to ttyUSB0
Feb 23 10:08:31 COMPUTER kernel: [ 154.605319] option 1-7:1.3: GSM modem (1-port) converter detected
Feb 23 10:08:31 COMPUTER kernel: [ 154.605434] usb 1-7: GSM modem (1-port) converter now attached to ttyUSB1
Feb 23 10:08:31 COMPUTER kernel: [ 154.605449] option 1-7:1.4: GSM modem (1-port) converter detected
Feb 23 10:08:31 COMPUTER kernel: [ 154.605623] usb 1-7: GSM modem (1-port) converter now attached to ttyUSB2'
After (i.e. when it nolonger worked):-
'Feb 24 09:24:58 COMPUTER usb_modeswitch: switch device 12d1:1446 on 001/005
Feb 24 09:24:59 COMPUTER usb_modeswitch_dispatcher[2549]: Could not read attribute: No such file or directory
Feb 24 09:24:59 COMPUTER usb_modeswitch[2549]: usb_modeswitch: switched to 12d1:1446 on 1/5
Feb 24 09:25:00 COMPUTER usb_modeswitch_dispatcher[2549]: Unable to open bind list file: No such file or directory
Feb 24 09:25:00 COMPUTER kernel: [ 173.445398] usbcore: registered new interface driver usbserial
Feb 24 09:25:00 COMPUTER kernel: [ 173.445415] usbcore: registered new interface driver usbserial_generic
Feb 24 09:25:00 COMPUTER kernel: [ 173.445428] usbserial: USB Serial support registered for generic
Feb 24 09:25:00 COMPUTER kernel: [ 173.475599] usbcore: registered new interface driver option
Feb 24 09:25:00 COMPUTER kernel: [ 173.475618] usbserial: USB Serial support registered for GSM modem (1-port)
Feb 24 09:25:00 COMPUTER usb_modeswitch[2549]: usb_modeswitch: add device ID 12d1:1446 to driver option
Feb 24 09:25:00 COMPUTER usb_modeswitch[2549]: usb_modeswitch: please report the device ID to the Linux USB developers!'
It seems to be a problem related to 'usb_modeswitch'. If you do a search
on the internet then this seems to be a problem that continually
reappears for various ubuntu versions over the last decade.
Here is a short term solution I found that worked for me:-
1). Plug your dongle into usb port and wait until it indicates a signal has been detected.
2). Do a 'Ctrl-Alt-t' to get a terminal window up.
3). In terminal window type 'lsusb' and then hit return.
4). One of the entries in the output should read something like:-
'Bus 001 Device 004: ID 12d1:1446 Huawei Technologies Co., Ltd.
Broadband stick (modem on)'
5). Make a note of the two hexidecimal numbers after the 'ID' i.e. in this example '12d1' and '1446'.
6). In the terminal window type:-
'sudo usb_modeswitch -v 12d1 -p 1446 -J'
replacing the numbers after the '-v' and '-p' with the numbers you made a note of in step 5). above and hit return.
7). The output looks something like:-
'Look for default devices ...
product ID matched
Found devices in default mode (1)
Access device 004 on bus 001
Current configuration number is 1
Use interface number 0
Use endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: Huawei Technologies
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Using standard Huawei switching message
Looking for active driver ...
OK, driver detached
Set up interface 0
Use endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reset response endpoint 0x81
Reset message endpoint 0x01
Device is gone, skip any further commands
-> Run lsusb to note any changes. Bye!'
8). In terminal window type 'lsusb' and then hit return.
9). The entry noted in step 4). above should now read something like:-
'Bus 001 Device 005: ID 12d1:1506 Huawei Technologies Co., Ltd.
Modem/Networkcard'
10). The dongle interface should now appear in 'Network Tools' and you should be able to connect as usual.
11). You need to go through this everytime you reboot until an update fixes the bug. Not ideal but a life saver if you can only connect to the network using this device !
regards,
Kevin Morgan
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1817410
Title:
After last software update Huawei 3372H-153 modem is not working
Status in ubuntu-release-upgrader package in Ubuntu:
Confirmed
Bug description:
After today's (February 23) software update Huawei 3372H-153 modem is
not working anymore (it was working for last 6 weeks). Modem itself
is OK - provides connection when used with router instead of sticking
it to laptop directly.
This is a content of last three updates from /var/log/apt/history.log:
Start-Date: 2019-02-21 07:41:44
Commandline: aptdaemon role='role-commit-packages' sender=':1.79'
Upgrade: libkmod2:amd64 (22-1ubuntu5.1, 22-1ubuntu5.2), binutils:amd64 (2.26.1-1ubuntu1~16.04.7, 2.26.1-1ubuntu1~16.04.8), kmod:amd64 (22-1ubuntu5.1, 22-1ubuntu5.2)
End-Date: 2019-02-21 07:43:19
Start-Date: 2019-02-22 03:06:34
Commandline: aptdaemon role='role-commit-packages' sender=':1.91'
Upgrade: libc6-dbg:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11), libc6-dev:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11), libgs9:amd64 (9.26~dfsg+0-0ubuntu0.16.04.4, 9.26~dfsg+0-0ubuntu0.16.04.5), libc6:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11), libc6:i386 (2.23-0ubuntu10, 2.23-0ubuntu11), locales:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11), libc-bin:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11), libc6-i386:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.16.04.4, 9.26~dfsg+0-0ubuntu0.16.04.5), ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.16.04.4, 9.26~dfsg+0-0ubuntu0.16.04.5), libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.16.04.4, 9.26~dfsg+0-0ubuntu0.16.04.5), libc-dev-bin:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11), multiarch-support:amd64 (2.23-0ubuntu10, 2.23-0ubuntu11)
End-Date: 2019-02-22 03:09:33
Start-Date: 2019-02-23 08:12:16
Commandline: aptdaemon role='role-commit-packages' sender=':1.80'
Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.11, 1:9.10.3.dfsg.P4-8ubuntu1.12), base-files:amd64 (9.4ubuntu4.7, 9.4ubuntu4.8)
End-Date: 2019-02-23 08:15:22
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.26
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Sat Feb 23 13:28:42 2019
InstallationDate: Installed on 2017-11-10 (469 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.update-manager.release-upgrades: 2018-03-28T02:15:33.576701
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1817410/+subscriptions
More information about the foundations-bugs
mailing list