[novatel mifi 2372] device is not recognized

[Eric Bellavance]

I have a Novatel Mifi 2372. I connect it with USB than I go to Setuo a Mobile Broadband Connection. The device not show up in the list of device...

I just installed the 11.04 Beta. Yes, it was working with Ubuntu 10.10

lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04
---
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 11.04
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
IpRoute:
 10.29.12.0/22 dev eth1 proto kernel scope link src 10.29.12.47 metric 1
 169.254.0.0/16 dev eth1 scope link metric 1000
 default via 10.29.12.1 dev eth1 proto static
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.
Keyfiles: Error: [Errno 2] No such file or directory
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
Package: network-manager-applet (not installed)
ProcEnviron:
 LANGUAGE=fr_CA:en
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
RfKill:

Tags: natty running-unity
Uname: Linux 2.6.38-8-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Eric Bellavance (ericbellavance-deactivatedaccount)]

This is my /var/log/dmesg

[Mathieu Trudel-Lapierre (cyphermox)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect 750362

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Eric Bellavance (ericbellavance-deactivatedaccount)]

apport information

[Eric Bellavance (ericbellavance-deactivatedaccount)]

apport information

[Eric Bellavance (ericbellavance-deactivatedaccount)]

apport information

[Eric Bellavance (ericbellavance-deactivatedaccount)]

apport information

[Eric Bellavance (ericbellavance-deactivatedaccount)]

apport information

[Eric Bellavance (ericbellavance-deactivatedaccount)]

apport information

[Eric Bellavance (ericbellavance-deactivatedaccount)]

I have run the apport-collect 750362 after connecting my Novatel Mifi...

[Mathieu Trudel-Lapierre (cyphermox)]

Are you clicking the Create a new mobile connection link in the menu, or are you going in the connection editor to do so?

Please connect your device, wait long enough for the link to appear in nm-applet, and then attach /var/log/syslog so we can see how the device is detected.

[Eric Bellavance (ericbellavance-deactivatedaccount)]

Allo Mathieu,

I use the connection editor, go on the Mobile Broadband tab than click Add button.

[Mathieu Trudel-Lapierre (cyphermox)]

I don't think this device is supposed to appear as a mobile broadband device when connected over USB. Can you not use it with Wifi?

[Mathieu Trudel-Lapierre (cyphermox)]

Reassigning to 'modemmanager' since it's the likely culprit (or maybe usb-modeswitch) if this Novatel device is actually supposed to do stuff over USB past configuration...

[Eric Bellavance (ericbellavance-deactivatedaccount)]

Don't have Wifi card on this pc

I used it with Ubuntu 10.10 on the same pc with USB

I can reinstall Ubuntu 10.10 if you want to compare logs...

[Mathieu Trudel-Lapierre (cyphermox)]

Don't need to ;)

Please edit /etc/usb_modeswitch.conf and set:
EnableLogging=0 to 1;

Then plug your device in and wait a little for it to maybe be detected; then attach both /var/log/syslog again and the file that should contain the logs for switching the device (it would probably be under /var/log/usb_modeswitch* if there is one).

I hope it's just that the switching code for this modem was somehow dropped.

[Eric Bellavance (ericbellavance-deactivatedaccount)]

I edited the file, rebooted the pc, plugged the usb modem and waited...

waited...

waited...

but... no usb_modeswitch* file in /var/log

[Eric Bellavance (ericbellavance-deactivatedaccount)]

Should I open a bug again usb_modeswitch ?

"Several new USB devices (especially high-speed WAN stuff, based on cell phone chipsets containing that feature) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After installation (and on every consecutive plugging) the driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. Modem maker "Option" calls that feature "ZeroCD (TM)" since it eliminates the need for shipping a separate driver carrier."

Yes, my Novatel have Windows drivers onboard and according to my syslog, my device is detected as usb-storage but not as a modem...

Apr 29 16:09:19 2007-0020 kernel: [ 406.854675] Initializing USB Mass Storage driver...
Apr 29 16:09:19 2007-0020 kernel: [ 406.854850] scsi4 : usb-storage 1-4:1.5
Apr 29 16:09:19 2007-0020 kernel: [ 406.855406] usbcore: registered new interface driver usb-storage
Apr 29 16:09:19 2007-0020 kernel: [ 406.855409] USB Mass Storage support registered.
Apr 29 16:09:20 2007-0020 kernel: [ 407.855311] scsi 4:0:0:0: Direct-Access NVTL Mass Storage 2.31 PQ: 0 ANSI: 0
Apr 29 16:09:20 2007-0020 kernel: [ 407.856091] sd 4:0:0:0: Attached scsi generic sg2 type 0
Apr 29 16:09:20 2007-0020 kernel: [ 407.865175] sd 4:0:0:0: [sdb] Attached SCSI removable disk

[Josua Dietze (digidietze)]

I don't think usb_modeswitch has ever handled this device; to be certain, I'd like to see a "lsusb" output.

If you enter "lsusb" with the device plugged, you might recognize the line with its ID (<vendor>:<product>).

Once you have that, enter "lsusb -v -d <vendor>:<product>" and attach the output.

[Eric Bellavance (ericbellavance-deactivatedaccount)]

>lsusb
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 10d5:5532 Uni Class Technology Co., Ltd
Bus 002 Device 002: ID 04cc:1520 ST-Ericsson
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1410:7001 Novatel Wireless
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

>sudo lsusb -v -d 1410:7001
Bus 001 Device 003: ID 1410:7001 Novatel Wireless
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x1410 Novatel Wireless
  idProduct 0x7001
  bcdDevice 0.00
  iManufacturer 3 Novatel Wireless, Inc.
  iProduct 2 Novatel Wireless HSPA
  iSerial 4 011861000079191
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 131
    bNumInterfaces 5
    bConfigurationValue 1
    iConfiguration 1 Qualcomm Configuration
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 5
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 32
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 32
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClas...

[Josua Dietze (digidietze)]

Hmm, what I can see there is a device which either does not need any switching or was switched correctly.
1410:7001 is a known TARGET mode ID in usb_modeswitch.

In the latter case, there should have been a log file from usb_modeswitch in /var/log though.

What I find suspicious are these repeating lines in your syslog:
...
 usb 1-4: reset high speed USB device using ehci_hcd and address 3
...

I know that some of these on-device install storages are quirky, returning wrong "mode sense" values and otherwise behaving badly.

Try this (as root or with "sudo") to prevent the resetting:
# echo "1" > /sys/bus/usb/devices/1-4/avoid_reset_quirk
Check the device address, it may have changed; the "1-4" is from your log.

Also, there is no sign that the "option" driver is binding to the device, even if the device ID is known to it.
So you are lacking the serial ports for using the device (should be ttyUSBx).

[Josua Dietze (digidietze)]

To address the driver question, try to load it manually (root or sudo):

# modprobe -v option
# echo "1410 7001" > /sys/bus/usb-serial/drivers/option1/new_id

[Eric Bellavance (ericbellavance-deactivatedaccount)]

After I executed your command I have been able to configure the connexion since my device was available. After I configured the device I tried to connect but it was not working. I disconnected my device than re-connected the device and I was to able to enable the connect to the internet...

May 4 09:17:32 2007-0020 kernel: [407700.232024] usb 1-4: new high speed USB device using ehci_hcd and address 7
May 4 09:17:32 2007-0020 kernel: [407700.369081] usb 1-4: config 1 has an invalid interface number: 5 but max is 4
May 4 09:17:32 2007-0020 kernel: [407700.369086] usb 1-4: config 1 has no interface number 4
May 4 09:17:32 2007-0020 kernel: [407700.388529] scsi9 : usb-storage 1-4:1.5
May 4 09:17:33 2007-0020 kernel: [407701.391493] scsi 9:0:0:0: Direct-Access NVTL Mass Storage 2.31 PQ: 0 ANSI: 0
May 4 09:17:33 2007-0020 kernel: [407701.393059] sd 9:0:0:0: Attached scsi generic sg2 type 0
May 4 09:17:33 2007-0020 kernel: [407701.401975] sd 9:0:0:0: [sdb] Attached SCSI removable disk
May 4 09:19:11 2007-0020 AptDaemon: INFO: Quitting due to inactivity
May 4 09:19:11 2007-0020 AptDaemon: INFO: Shutdown was requested
May 4 09:23:33 2007-0020 kernel: [408061.220868] usbcore: registered new interface driver usbserial
May 4 09:23:33 2007-0020 kernel: [408061.220889] USB Serial support registered for generic
May 4 09:23:33 2007-0020 kernel: [408061.221594] usbcore: registered new interface driver usbserial_generic
May 4 09:23:33 2007-0020 kernel: [408061.221597] usbserial: USB Serial Driver core
May 4 09:23:33 2007-0020 kernel: [408061.235302] USB Serial support registered for GSM modem (1-port)
May 4 09:23:33 2007-0020 kernel: [408061.236439] usbcore: registered new interface driver option
May 4 09:23:33 2007-0020 kernel: [408061.236444] option: v0.7.2:USB Driver for GSM modems
May 4 09:23:49 2007-0020 kernel: [408077.012356] option 1-4:1.0: GSM modem (1-port) converter detected
May 4 09:23:49 2007-0020 kernel: [408077.012529] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0
May 4 09:23:49 2007-0020 kernel: [408077.012576] option 1-4:1.1: GSM modem (1-port) converter detected
May 4 09:23:49 2007-0020 kernel: [408077.012673] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1
May 4 09:23:49 2007-0020 kernel: [408077.012715] option 1-4:1.2: GSM modem (1-port) converter detected
May 4 09:23:49 2007-0020 kernel: [408077.012818] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB2
May 4 09:23:49 2007-0020 kernel: [408077.012869] option 1-4:1.3: GSM modem (1-port) converter detected
May 4 09:23:49 2007-0020 kernel: [408077.012967] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB3
May 4 09:23:49 2007-0020 modem-manager[615]: <info> (ttyUSB3) opening serial port...
May 4 09:23:49 2007-0020 modem-manager[615]: <info> (ttyUSB0) opening serial port...
May 4 09:23:49 2007-0020 modem-manager[615]: <info> (ttyUSB1) opening serial port...
May 4 09:23:49 2007-0020 modem-manager[615]: <info> (ttyUSB2) opening serial port...
May 4 09:23:52 2007-0020 modem-manager[615]: <info> (ttyUSB3) closing serial port...
May 4 09:23:52 2007-0020 modem-manager[615]: <info> (ttyUSB3) serial po...

[Eric Bellavance (ericbellavance-deactivatedaccount)]

Is the change done with the command are persistent so I can reboot the computer with no problem?

[Josua Dietze (digidietze)]

If you still see the driver problem in 11.10 and don't get any logs in /var/log despite enabled logging option, the problem may be with the dispatcher.

[Launchpad Janitor (janitor)]

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