Sierra Wireless 320U USB-to-WWAN modem is not detected (needs updated drivers from manufacturer website)

Bug #933972 reported by Tomas Cassidy
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
Invalid
Medium
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I have a Sierra Wireless 320U USB 4G/LTE modem that is not detected when I plug it in to a USB port. I can get it working in Ubuntu 11.10 and precise, but only by installing the directIP drivers from the manufacturers website at http://mycusthelpadmin.net/SIERRAWIRELESS/_cs/AnswerDetail.aspx?aid=44. The current "sierra" and "sierra_net" drivers in the linux kernel are older than those provided on the manufacturers website.

I should also note that "lsusb" reports a different name for the device:
Bus 001 Device 010: ID 0f3d:68aa Airprime, Incorporated

The device manufacturer page is at http://www.sierrawireless.com/en/productsandservices/AirCard/USBModems/AirCard_320U.aspx and my ISP page for the device is at http://www.telstra.com.au/bigpond-internet/mobile-broadband/bigpond/

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-16-generic 3.2.0-16.25
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 3238 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 3238 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe8fc000 irq 45'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,19daa140,00100001'
   Controls : 15
   Simple ctrls : 7
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfcf7c000 irq 19'
   Mixer name : 'Nvidia GPU 0b HDMI/DP'
   Components : 'HDA:10de000b,10de0101,00100200'
   Controls : 24
   Simple ctrls : 4
CasperVersion: 1.304
Date: Fri Feb 17 04:30:20 2012
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120215)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/ubnkern
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-16-generic N/A
 linux-backports-modules-3.2.0-16-generic N/A
 linux-firmware 1.69
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/05/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: NM10
dmi.board.vendor: ZOTAC
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd05/05/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnZOTAC:rnNM10:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc2 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc2'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc3-precise/

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-17.26)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-17.26
Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote : Re: Sierra Wireless 320U USB-to-WWAN modem is not detected

Tested with upstream v3.3-rc4 and the device is still not detected.

tags: added: bot-stop-nagging
removed: kernel-request-3.2.0-17.26
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

Tested with upstream v3.3-rc5 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc5-precise/) and the device still not detected.

I can confirm that the updated drivers from Sierra Wireless website work on v3.3-rc5. After installing the updated drivers, the device is detected and a wwan0 interface is created.

summary: - Sierra Wireless 320U USB-to-WWAN modem is not detected
+ Sierra Wireless 320U USB-to-WWAN modem is not detected (needs updated
+ drivers from manufacturer website)
description: updated
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you know if the manufacturer is working to get the latest drivers upstream?

We generally ask bug reporters to first request that the driver be added to the upstream kernel. This can be done by mailing the Linux Kernel Mailing List or opening a bug at bugzilla.kernel.org.

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

I sent an e-mail to <email address hidden> asking if they could submit their latest driver to the linux kernel, but I haven't yet received any response. I've filed a bug upstream on bugzilla.kernel.org at https://bugzilla.kernel.org/show_bug.cgi?id=42830

Changed in linux:
importance: Unknown → Medium
status: Unknown → Invalid
Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

I've now sent an e-mail to <email address hidden> as per GregKH's instructions on the bugzilla bug.

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :
Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

Note that these patches do not implement the full updated driver from SierraWireless. They only add the new device ID to the existing sierra drivers, so are lacking any new features that are in the latest drivers from SierraWireless.

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :
Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :
Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :
tags: added: kernel-fixed-upstream-3.0
removed: kernel-bug-exists-upstream
tags: added: kernel-fixed-upstream-v3.0
removed: kernel-fixed-upstream-3.0
tags: added: kernel-fixed-upstream
removed: kernel-fixed-upstream-v3.0
Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :
Revision history for this message
madbiologist (me-again) wrote :

I have found one of these patches in the changelog for the just-released upstream 3.5 kernel:

author Tom Cassidy
Wed, 6 Jun 2012 07:08:48 +0000 (17:08 +1000)
committer Greg Kroah-Hartman
Tue, 12 Jun 2012 23:05:59 +0000 (16:05 -0700)
commit 19a3dd1575e954e8c004413bee3e12d3962f2525
tree b69ff4a609705f8283c99882f73d9a96a733e47a
parent 5bbfa6f427c1d7244a5ee154ab8fa37265a5e049

USB: serial: sierra: Add support for Sierra Wireless AirCard 320U modem

Add support for Sierra Wireless AirCard 320U modem

Signed-off-by: Tomas Cassidy
Cc: stable
Signed-off-by: Greg Kroah-Hartman

Presumably the other one is in there somewhere too.

Revision history for this message
madbiologist (me-again) wrote :

Yep, there it is (in the 3.5 kernel):

author Bjørn Mork
Tue, 5 Jun 2012 21:18:10 +0000 (21:18 +0000)
committer David S. Miller
Wed, 6 Jun 2012 17:40:32 +0000 (10:40 -0700)
commit dd03cff23d694cfb0fdae80cb618e7ced05ea696
tree 88025350444664bbe7808c8519c3204ba4b57d32
parent 9a43a02648e8414b2a757437820aa928208fc42f

net: sierra_net: device IDs for Aircard 320U++

Adding device IDs for Aircard 320U and two other devices
found in the out-of-tree version of this driver.

Cc: linux at sierrawireless.com
Cc: Autif Khan
Cc: Tom Cassidy
Cc: stable
Signed-off-by: Bjørn Mork
Acked-by: Greg Kroah-Hartman
Signed-off-by: David S. Miller

Revision history for this message
madbiologist (me-again) wrote :

If it is in the stable 3.2 tree it will eventually come to Precise as an SRU.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Chris Tree (christree63)
information type: Public → Private
Revision history for this message
Chris Tree (christree63) wrote :

Hi, as indicated above I need a little help getting a grasp of things I can't point and click with a mouse, however I've tried updating the development kernel as described above expecting that the patches now in linux-stable would have taken effect, however I'm still not able to connect with the Sierra Wireless AirCard 320U modem. Hope you're able to give me a clue as to how I can do that, thanks?

information type: Private → Public
Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

Please don't mark bugs as private unless there is confidential information in the bug report.

This has already been fixed, as the patches for this are now included in the current released kernels for Ubuntu 12.04 and 12.10. You shouldn't have to do anything with the driver from Sierra Wireless. It should "just work" and be detected automatically when you plug in your usb modem device.

If you have previously installed a separate driver (eg. from the Sierra Wireless website), then you will need to uninstall that to revert to the driver included in the kernel.

If you run "modinfo sierra" and "modinfo sierra_net" from a Terminal window, you should see the following driver versions:

$ modinfo sierra
filename: /lib/modules/3.5.0-19-generic/kernel/drivers/usb/serial/sierra.ko
license: GPL
version: v.1.7.16
description: USB Driver for Sierra Wireless USB modems
...

$ modinfo sierra_net
filename: /lib/modules/3.5.0-19-generic/kernel/drivers/net/usb/sierra_net.ko
license: GPL
version: v.2.0
description: USB-to-WWAN Driver for Sierra Wireless modems
...

Revision history for this message
Chris Tree (christree63) wrote :

Hi, thanks for your advice Tom, sorry for not following protocol with the private/public thing, I'm still learning how it all works. I'm puzzled though, as the only reason I've tried anything new is the Sierra modem doesn't work. It works fine on a Windows PC, but not this Ubuntu machine. As I pointed out earlier, I'm a bit of a novice with the Terminal, but I'm prepared to have a go at anything with a bit of advice. If you were able to give me a clue as to what else to try I'd appreciate it. Thanks.

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

Can you post the output of "modinfo sierra" and "modinfo sierra_net"? Run those two commands in a terminal window without the surrounding quotes.

Revision history for this message
Chris Tree (christree63) wrote :
Download full text (5.3 KiB)

Tom, thanks again for your help. Below is the "modinfo sierra" and "modinfo sierra_net" you requested. I hope it helps. I've had some more attempts to make it go. It is now being detected as a Sierra Wireless Aircard 320U, I'm wondering if the problem is really an incorrect description of the plan. Is it possible to get the modem to report back it's settings?

I know it's a Telstra 4G modem and the person I'm trying to help has given me their bill but no matter what I try calling it, it simply won't connect. I've scoured the Telstra website trying to ID the plan, but I'm just going in circles. I have a Telstra Next G modem I've never had an issue with, so I don't understand what I'm doing wrong.

I have learnt a few more commands when using the terminal, I suppose that's plus! Anyway, I hope you can help me, thank you for your time. Chris.

modinfo sierra

filename: /lib/modules/3.5.0-19-generic/kernel/drivers/usb/serial/sierra.ko
license: GPL
version: v.1.7.16
description: USB Driver for Sierra Wireless USB modems
author: Kevin Lloyd, Elina Pasheva, Matthew Safar, Rory Filer
srcversion: EAB194D6B1111FBA8A094A3
alias: usb:v413Cp8133d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0F3Dp68A3d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0F3Dp68AAd*dc*dsc*dp*icFFiscFFipFF*
alias: usb:v1199p68A3d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p68A2d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6893d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6892d*dc*dsc*dp*icFFiscFFipFF*
alias: usb:v1199p6891d*dc*dsc*dp*icFFiscFFipFF*
alias: usb:v1199p6890d*dc*dsc*dp*icFFiscFFipFF*
alias: usb:v1199p6880d*dc*dsc*dp*icFFiscFFipFF*
alias: usb:v1199p685Ad*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6859d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6856d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6855d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6853d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6852d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6851d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6850d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p683Ed*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p683Dd*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p683Cd*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p683Bd*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p683Ad*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6839d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6838d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6835d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6834d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6833d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6832d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6822d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6821d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6820d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6816d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6815d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6813d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6812d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6809d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1199p6808d*dc*dsc*dp*ic*isc*ip*
al...

Read more...

Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :

That looks like the correct drivers. If you run "ifconfig -a" do you see a wwan0 interface listed? If not, then I'm not sure what else to do as I am running from one of these devices right now.

If the wwan0 interface is there then it should be appearing in Network Manager. There should also be a new option in the network menu for "Enable Mobile Broadband". You will also see a bunch of stuff appearing in the syslog at /var/log/syslog after plugging in the device.

Revision history for this message
Chris Tree (christree63) wrote :

Hi Tom, I'm online using the Sierra modem. No good explanation for it. I kept trying various different combinations of Telstra log in options and finally tried to connect using my Next G USB modem. It connected immediately, so that eliminated interference or low signal. I shut down immediately and connected the Sierra in one of the rear USB ports. Connected immediately. So then I tried a process of elimination and discovered the Sierra won't run on the front USB ports, I assume it doesn't get enough power, don't have any better explanation. Once again thank you for your help and patience in helping try to solve this problem, hope this helps someone else. Chris.

Revision history for this message
allen Brown (4gltemobilebroadband) wrote :

i had the problem of Sierra 320U Aircard to work with my Win 7 OS, anybody give some advice??

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.