3G HSUPA modem Olivetti Olicard 160 is not recognized

Bug #1232896 reported by Ayrton Santana
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Usb Modeswitch
New
Undecided
Unassigned
Usb Modeswitch Data
New
Undecided
Unassigned

Bug Description

Brief summary:
The 3G HSUPA modem Olivetti Olicard 160 is not recognized by Ubuntu 13.04 64bits as a mobile broadband modem.

The result of lsusb | grep -i olivetti:
Bus 003 Device 004: ID 0b3c:f00c Olivetti Techcenter

Steps to reproduce:
Plug the modem in the usb port.
What happens:
The modem starts blinkin a yellow led, but network-manager doesn't show the modem when manually adding a mobile broadband connetion.

What is expected:
network-manager show the modem in the modems list when try to add a mobile broadband connection.

Additional information:
I also tried create the file /etc/udev/rules.d/14-olicardmodules.rules with the following rules:
SYSFS{idVendor}=="0b3c",SYSFS{idProduct}=="f00c",RUN+="/sbin/modprobe usbserial vendor=0x0b3c product=0xf00c"
KERNEL==”ttyUSB[23]“,ACTION==”add”,SYSFS{idVendor}==”0b3c”,SYSFS{idProduct}==”f00c″,RUN+=”/bin/sleep 2″

I confirmed that bug based on the question https://answers.launchpad.net/ubuntu/+source/usb-modeswitch-data/+question/234966 and some other related issues with this specific modem reported in forums.

Ayrton Santana (ayrton)
no longer affects: usb-modeswitch-data (Ubuntu)
Revision history for this message
JulioHM (jhm-g) wrote :

I can confirm this happens in Ubuntu 13.10 64bits as well.

Does this have an update? The modem is quite popular in Brazil, for example. I'm hoping for a fix, or at least a final answer.

Revision history for this message
Lars Melin (larsm17) wrote :

Provide the output from lsusb -v -d 0b3c:f00c as a start

Revision history for this message
André Lucas Wirth (wirthandre) wrote :

the output

 lsusb -v -d 0b3c:f00c

Bus 002 Device 008: ID 0b3c:f00c Olivetti Techcenter
Couldn't open device, some information will be missing
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x0b3c Olivetti Techcenter
  idProduct 0xf00c
  bcdDevice 0.00
  iManufacturer 3
  iProduct 2
  iSerial 4
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 1
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk-Only
      iInterface 0
      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 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0

Revision history for this message
Lars Melin (larsm17) wrote :

Sorry for a late reply.
0b3c:f00c is the cd-rom install id so the dongle has to be mode switched.

Can you please try:
sudo usb_modeswitch -v 0b3c -p f00c -W -I -M 5553424312345679000000000000061b000000020000000000000000000000

or

sudo usb_modeswitch -v 0b3c -p f00c -W -I -M 55534243123456788000000080000606f50402527000000000000000000000

and check with lsusb to see if the dongle switched mode (got a new usb id) for any of those two possible switch messages.

If it does then please paste the lsusb -v -d output for the new id here.

Revision history for this message
Renato Rodrigues (renato-rdg) wrote :

I've tryed the two commands above.

The first does nothing, but the second chanched the usb id from f00c to c00a, though nothing show in the NetworkManager icon in gmome shell bar.

Revision history for this message
Lars Melin (larsm17) wrote :

Thanks for that, 0b3c:f00c switching to 0b3c:c00a will be added for usb_modeswitch support in the next usb_modeswitch data package update.
The dongle still needs linux driver support in order for it to show up in NetworkManager, I will request it to be included but need to see the dongles interface info after it has switched mode.

Please attach the output from lsusb -v -d 0b3c:c00a after you have sent the correct (the second) switch message to it.

Revision history for this message
Luis Minko (lminko) wrote :
Download full text (9.9 KiB)

Hi,

I have the same problem here on my red hat 6.5.

See something interesting, I have a mac osx, and the modem works perfectly. In mac osx it is recognized as 0b3c: c00a.

Follow my lsusb -v -d 0b3c:c00a on red hat:

Bus 001 Device 013: ID 0b3c:c00a Olivetti Techcenter
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x0b3c Olivetti Techcenter
  idProduct 0xc00a
  bcdDevice 0.00
  iManufacturer 3 USBModem
  iProduct 2 HSPA Data Card
  iSerial 4 1234567890ABCDEF
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 184
    bNumInterfaces 7
    bConfigurationValue 1
    iConfiguration 1 USBModem Configuration
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      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 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
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 0
      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 0x02 EP 2 OUT
        bmAttributes 2
          Transfer T...

Revision history for this message
Lars Melin (larsm17) wrote :

Thanks for the lsusb listing, the device will be supported in linux option driver for the serial interfaces (3G ppp modem and application ports), and in linux qmi_wwan driver for the direct ethernet adapter interface.

Interfaces according to Windows driver pack matches the lsusb listing:

MI_00 Olicard160 Application1 Port
MI_01 Olicard160 Application2 Port
MI_02 Olicard160 Application3 Port
MI_03 Olicard160 Application4 Port
MI_04 USB Mass Storage Device
MI_05 Olicard160 3G Modem Port
MI_06 Olicard160 Wireless Ethernet Adapter

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

Other bug subscribers

Related questions

Remote bug watches

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