Verizon CDMA card no longer works

[Kaye Kelley]

Under 2.6.27-9 the card will correctly be located and initialized by NetworkManager - under 2.6.27-11 the card is identified, but the PPP connection is not started.

Under 2.6.27-9 the ttyACM0 device node is created and PPPD is bound to that device.

Under 2.6.27-11 the ttyACM0 device node is NOT created, and the system attempts to bind to the /dev/ttyUSB0 node instead - which does not work.

(obviously, the modem not working makes it a bit difficult to create a bug report under the failing kernel).

uname -a: Linux kaye-laptop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux
cat /proc/version_signature: Ubuntu 2.6.27-9.19-generic (working system)

[Cedric Mordrin (cedricmordrin)]

I noticed this as well, with my UM150 and reverting to the 2.6.27.9 kernel allows for the device to work again.
I tried on a co-workers Fedora 10 box w/ 2.6.27.12 and it had the same error I was seeing on mine. We also tried his AT&T Aircard and it also did not work.

[Cedric Mordrin (cedricmordrin)]

Output from syslog:

Feb 2 13:30:16 Durandal NetworkManager: <info> Activation (ttyUSB0) starting connection 'SHSU Verizon Card'
Feb 2 13:30:16 Durandal NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4
Feb 2 13:30:16 Durandal NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 2 13:30:16 Durandal NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Feb 2 13:30:16 Durandal NetworkManager: <debug> [1233603016.128454] nm_serial_device_open(): (ttyUSB0) opening device...
Feb 2 13:30:16 Durandal NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Feb 2 13:30:18 Durandal kernel: [ 147.970659] type=1503 audit(1233603018.095:5): operation="inode_permission" requested_mask="w::" denied_mask="w::" fsuid=0 name="/dev/ttyUSB0" pid=6807 profile="/usr/sbin/cupsd"
Feb 2 13:30:18 Durandal kernel: [ 147.970706] type=1503 audit(1233603018.095:6): operation="inode_permission" requested_mask="w::" denied_mask="w::" fsuid=0 name="/dev/ttyUSB1" pid=6807 profile="/usr/sbin/cupsd"
Feb 2 13:30:18 Durandal kernel: [ 147.970741] type=1503 audit(1233603018.095:7): operation="inode_permission" requested_mask="w::" denied_mask="w::" fsuid=0 name="/dev/ttyUSB2" pid=6807 profile="/usr/sbin/cupsd"
Feb 2 13:30:18 Durandal kernel: [ 147.970773] type=1503 audit(1233603018.095:8): operation="inode_permission" requested_mask="w::" denied_mask="w::" fsuid=0 name="/dev/ttyUSB3" pid=6807 profile="/usr/sbin/cupsd"
Feb 2 13:30:27 Durandal NetworkManager: <WARN> init_done(): Modem initialization timed out
Feb 2 13:30:27 Durandal NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9
Feb 2 13:30:27 Durandal NetworkManager: <debug> [1233603027.420123] nm_serial_device_close(): Closing device 'ttyUSB0'
Feb 2 13:30:27 Durandal NetworkManager: <info> Marking connection 'SHSU Verizon Card' invalid.
Feb 2 13:30:27 Durandal NetworkManager: <info> Activation (ttyUSB0) failed.
Feb 2 13:30:27 Durandal NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3
Feb 2 13:30:27 Durandal NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).
Feb 2 13:30:27 Durandal NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Feb 2 13:30:27 Durandal NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed

uname -a:
Linux Durandal 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux

[webguy (ubuntu-seremeth)]

I can confirm as well - running the earlier kernel resolves the issue. If you need any testing, please let me know. Thanks.

[Kaye Kelley (7131kelley)]

It looks like somewhere between -9 and -11 the USB ID's for this card have been removed from the acm driver - so the driver is not binding to the card.

[Stefan Bader (smb)]

Hi, could someone do a quick check whether the current Intrepid kernel (-12.28) still lacks this support. There have been a few patches coming in from stable upstream and I'd like to make sure this wasn't fixed there.
Also it would be helpful if someone could post the USB ID in question and confirm we are talking about the cdc-acm driver. Thanks.

[Kaye Kelley (7131kelley)]

For reference, the output of lsusb -v (for this device) under 2.6.27-9 is
Bus 005 Device 002: ID 106c:3702 Curitel Communications, Inc. Pantech PX-500
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 2 Communications
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x106c Curitel Communications, Inc.
  idProduct 0x3702 Pantech PX-500
  bcdDevice 1.00
  iManufacturer 1 PANTECH
  iProduct 2 PANTECH USB MODEM
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 90
    bNumInterfaces 3
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 2 Communications
      bInterfaceSubClass 2 Abstract (modem)
      bInterfaceProtocol 1 AT-commands (v.25ter)
      iInterface 0
      CDC Header:
        bcdCDC 1.09
      CDC Call Management:
        bmCapabilities 0x03
          call management
          use DataInterface
        bDataInterface 1
      CDC ACM:
        bmCapabilities 0x0f
          connection notifications
          sends break
          line coding and serial state
          get/set/clear comm features
      CDC Union:
        bMasterInterface 0
        bSlaveInterface 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 32
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 10 CDC Data
      bInterfaceSubClass 0 Unused
      bInterfaceProtocol 0
      iInterface 3 Data Interface
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0...

[Longwing (dlongwing)]

I tried it this morning with a fully updated copy of Ubuntu 8.10. Still no dice.

[Stefan Bader (smb)]

Actually it seems like the IDs were not removed but added to the wrong driver.

commit 10d0ada031651357920661937492724220c346a6
Author: Dan Williams <email address hidden>
Date: Fri Oct 10 06:41:16 2008 -0400
    USB: option: add Pantech cards
    commit 8b6346ec899713a90890c9e832f7eff91ea73504 upstream

This got reverted by the update to 2.6.27.16 which is included in the current -proposed kernel (Ubuntu-2.6.27-12.28). For information how to enable this see https://wiki.ubuntu.com/Testing/EnableProposed. Maybe you want to try that kernel.

[webguy (ubuntu-seremeth)]

Yeah - here's my experience:

New kernel (2.6.12-27) -- no dice.

Feb 27 09:49:02 my-laptop kernel: [ 195.113938] ppdev0: registered pardevice
Feb 27 09:49:02 my-laptop python: io/hpmud/pp.c 627: unable to read device-id ret=-1
Feb 27 09:49:02 my-laptop kernel: [ 195.160509] ppdev0: unregistered pardevice
Feb 27 09:49:04 my-laptop kernel: [ 197.121184] usb 7-2: new high speed USB device using ehci_hcd and address 3
Feb 27 09:49:04 my-laptop kernel: [ 197.261345] usb 7-2: configuration #1 chosen from 1 choice
Feb 27 09:49:04 my-laptop kernel: [ 197.419804] usbcore: registered new interface driver usbserial
Feb 27 09:49:04 my-laptop kernel: [ 197.419819] usbserial: USB Serial support registered for generic
Feb 27 09:49:04 my-laptop kernel: [ 197.419874] usbcore: registered new interface driver usbserial_generic
Feb 27 09:49:04 my-laptop kernel: [ 197.419876] usbserial: USB Serial Driver core
Feb 27 09:49:04 my-laptop kernel: [ 197.429183] usbserial: USB Serial support registered for GSM modem (1-port)
Feb 27 09:49:04 my-laptop kernel: [ 197.429336] option 7-2:1.0: GSM modem (1-port) converter detected
Feb 27 09:49:04 my-laptop kernel: [ 197.429570] usb 7-2: GSM modem (1-port) converter now attached to ttyUSB0
Feb 27 09:49:04 my-laptop kernel: [ 197.429690] option 7-2:1.1: GSM modem (1-port) converter detected
Feb 27 09:49:04 my-laptop kernel: [ 197.429847] usb 7-2: GSM modem (1-port) converter now attached to ttyUSB1
Feb 27 09:49:04 my-laptop kernel: [ 197.429966] option 7-2:1.2: GSM modem (1-port) converter detected
Feb 27 09:49:04 my-laptop kernel: [ 197.430088] usb 7-2: GSM modem (1-port) converter now attached to ttyUSB2
Feb 27 09:49:04 my-laptop kernel: [ 197.430103] option 7-2:1.3: GSM modem (1-port) converter detected
Feb 27 09:49:04 my-laptop kernel: [ 197.430160] usb 7-2: GSM modem (1-port) converter now attached to ttyUSB3
Feb 27 09:49:04 my-laptop kernel: [ 197.430172] usbcore: registered new interface driver option
Feb 27 09:49:04 my-laptop kernel: [ 197.430174] option: USB Driver for GSM modems: v0.7.2
Feb 27 09:49:04 my-laptop kernel: [ 197.441182] usbcore: registered new interface driver cdc_acm
Feb 27 09:49:04 my-laptop kernel: [ 197.441188] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Feb 27 09:49:04 my-laptop kernel: [ 197.450611] usbcore: registered new interface driver libusual
Feb 27 09:49:04 my-laptop nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_106c_3711_noserial_if0_serial_usb_0, iface: (null)): iface not found
Feb 27 09:49:04 my-laptop NetworkManager: <info> ttyUSB0: driver is 'option'.
Feb 27 09:49:04 my-laptop NetworkManager: <debug> [1235746144.852624] setup_monitor_device(): No monitoring udi provided
Feb 27 09:49:04 my-laptop NetworkManager: <info> Found new Modem device 'ttyUSB0'.
Feb 27 09:49:04 my-laptop NetworkManager: <info> (ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_106c_3711_noserial_if0_serial_usb_0
Feb 27 09:49:08 my-laptop kernel: [ 201.294028] ppdev0: registered pardevice
Feb 27 09:49:08 my-laptop hp: io/hpmud/pp.c 627: unable to read device-id ret=-1
Feb 27 09:...

[Mike Rushton (leftyfb)]

I can confirm this.

Dell Mini 9
Verizon UM150VW aircard
Ubuntu 8.10 installed from scratch fully updated
linux kernel 2.6.27-12
proposed repository enabled

I have noticed that inserting the device after boot results in the above dmesg output. But having the device plugged in before and during boot allows it to work normally.

[Mike Rushton (leftyfb)]

I think this was fixed in the latest kernel update. It seems to be working now for me:
linux-image-2.6.27-13-generic

from http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=blob_plain;f=debian/changelog;hb=1c917b2b6acee502647057f153c5cb55ce055a2e

  * USB: gadget: cdc-acm deadlock fix
  * USB: cdc-acm.c: fix recursive lock in acm_start_wb error path
  * USB: fix memory leak in cdc-acm
  * USB: fix cdc-acm resume()

[Stefan Bader (smb)]

@Kaye, since you are the original commiter, is this fixed for you as well? I am marking it "fix released" for now. I it doesn't work for you, please set it back to new. Thanks.

[Stefan Bader (smb)]

The same patch went up with Jaunty in Ubuntu-2.6.28-8.21.

[webguy (ubuntu-seremeth)]

Working for me (and I can see the display now that I've upgraded to the beta nvidia driver ;p).

[Mark Stosberg (markstos)]

I ran into this bug on Intrepid, with a 2.6.27-11 kernel.

I can also confirm that installing "linux-image" from intrepid-proposed fixes it. The version I installed from there is 2.6.27-13.

   Mark