12d1:1446 Huawei E173 only detected as mass storage

[Bernd Schlapsi]

My Huawei E173 UMTS-Stick is only detected as a mass storage device so I can't connect to the internet with Ubuntu 13.10.
It works great with Ubuntu 13.04

lsusb:
    Bus 002 Device 006: ID 12d1:1446 Huawei Technologies Co., Ltd. E1552/E1800/E173 (HSPA modem)

I tried to add "usbserial ...." into the /etc/modules, but that didn't help.

Also this USB device is already included in /lib/udev/rules.d/40-usb_modeswitch.rules
    # Huawei, newer modems
    ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1446", RUN+="usb_modeswitch '%b/%k'"

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-generic 3.10.0.5.14
ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
Uname: Linux 3.10.0-5-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3761 F.... pulseaudio
                      ubuntu 5721 F.... pulseaudio
CasperVersion: 1.335
Date: Thu Jul 25 20:46:32 2013
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130725)
MachineType: Dell Inc. XPS M1330
MarkForUpload: True
ProcFB: 0 nouveaufb
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
RelatedPackageVersions:
 linux-restricted-modules-3.10.0-5-generic N/A
 linux-backports-modules-3.10.0-5-generic N/A
 linux-firmware 1.112
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: XPS M1330
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Bernd Schlapsi, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Bernd Schlapsi (bernd-sch)]

I tested the following i386-kernels
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10.4-saucy/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/

With both kernels I have the same problem. The UMTS stick is mounted as a mass storage device.

[penalvch (penalvch)]

Bernd Schlapsi, the next step is to bisect from Raring to Saucy, in order to identify the offending commit. Could you please do this via https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Bernd Schlapsi (bernd-sch)]

So, I tested a lot of mainline kernels yesterday, but with no luck. I started from the first mainline kernel tagged with saucy (3.8)

So today I installed 12.04, 13.04 and 13.10 on an USB stick and tested the live version of Ubuntu. No surprise the UMTS stick works great with 12.04 and 13.04, but don't work with 13.10

So I reinstalled 13.10 with the latest daily image (3.10.0-6-generic) again and started testing. The UMTS stick don't work with the latest kernel, so I went to https://launchpad.net/ubuntu/saucy/+source/linux and installed the following kernels:
-> 3.8.0-19-generic
-> 3.9.0-0-generic
-> 3.10.0-0-generic
But none of them worked :-(

So could it be that the problem is maybe the network-manager? The version in saucy is 0.9.8.0-6. The version in 13.04 is 0.9.8.0-0

I could send an USB stick Huawai E173 (12d1:1446) to someone who is willing to look into this problem. Or please tell me what I can do now to debugg this problem

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Danillo (danillo)]

This was also happening in Ubuntu 12.10, as described in bug #1057186. Couldn't this be the same problem?

[penalvch (penalvch)]

Bernd Schlapsi, it's possible this is not a bug in the linux stack. If you boot into either your install of 12.04 or 13.04, and then install for example 3.10.0-0-generic, and if it still works, it would seem not a linux kernel bug. Could you please test this and report back?

[Aurélien PROVIN (aprovin)]

I have the same problem.

In the 13.10 version, the next kernel modules don’t load automatically when the stick is plugged:
- option
- usb_wwan
- usbserial

The modem is correctly detected if they are previously loaded :

[ 521.845581] usb-storage 1-3:1.0: USB Mass Storage device detected
[ 521.845902] option 1-3:1.0: GSM modem (1-port) converter detected
[ 521.846131] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0
[ 521.846318] usb-storage 1-3:1.1: USB Mass Storage device detected
[ 521.846427] option 1-3:1.1: GSM modem (1-port) converter detected
[ 521.846581] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1

Can you help me to solve this regression ?

[penalvch (penalvch)]

Aprovin, in order to track your hardware, could you please file a new report at a terminal:
ubuntu-bug linux

[Aurélien PROVIN (aprovin)]

Christopher, here is the reference of the new bug report #1249678

[Alejandro Arcos (aarcos)]

Hi
Today detect in my Dell Inspiron 14R the same problem, when run lsusb

Bus 002 Device 003: ID 8087:07da Intel Corp.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0c45:648d Microdia
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 12d1:1446 Huawei Technologies Co., Ltd. E1552/E1800/E173 (HSPA modem)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

He detect correctly this modem but only i have the mass storage!!

thanks a lot

[penalvch (penalvch)]

Alejandro Arcos, so your hardware may be tracked, could you please file a new report via a terminal:
ubuntu-bug linux

[Alejandro Arcos (aarcos)]

Hi Cristopher, how to upload the result of ubuntu-bug linux to this bug

[penalvch (penalvch)]

Alejandro Arcos, you don't. Please again see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205104/comments/14 .

[Alejandro Arcos (aarcos)]

Hi Christopher M. Penalver (penalvch) I upload ubuntu-bug linux info in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256604

Thanks

[Alejandro Arcos (aarcos)]

Hi Christopher M. Penalver, update of bios applied, but no change behaviour. I can do another ?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Danillo, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

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

[AZ (m-dev)]

I've just installed (recompiled) usb-modeswitch (2.1.0+repack0-1) and usb-modeswitch-data (20140129-1) from debian sid, removed and replugged the umts device and then suddenly the gsm devices (serial devices) turned and I could actually connect to umts.

[penalvch (penalvch)]

AZ, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

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

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[arnuschky (abrutschy)]

I am having exactly this problem on 14.04.1.

@AZ: how did you solve this problem exactly?

[penalvch (penalvch)]

arnuschky, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

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

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]