Re: cdc_acm
On Sun, Jan 29, 2006 at 10:25:49PM +0000, Michael Ott wrote:
> Hello!
>
> I want to connect to my new mobile phone (Motorola V635) using cdc_acm.
> I can see the memory in the mobile, but there will not create an device
> to the modem.
And I want to connect my Motorola E815... Different messages/logs but
similar problems. Hopefully between us we can get something working...
> Here my log:
> # vim /var/log/syslog:
In my log I don't get any errors. What kernel version are you running?
I'm using 2.6.15, locally compiled from Debian source, on an otherwise
up to date sarge distribution. I'm using the motorola cable.
My problem is the opposite of yours: even though I have a trans-flash
card in the phone, the usb system/kernel doesn't see it, even after
loading usb-storage manually.
I do see device /dev/ttyACM0, created by the cdc_acm module, but I
can't talk to the phone with minicom.
Below is my lsusb -v (only the part related to the phone):
There is plenty of CDC/serial info, but I can't get the phone to
even echo the AT commands typed in minicom. I've tried /dev/ttyACM0
at just about every imaginable baud rate. Stty reports 9600.
Below the lsusb -v output is the portion of my syslog that deals with
the usb events. Nothing related to usb-storage. Even after I load
usb-storage manually, nothing shows up.
Bus 001 Device 002: ID 22b8:2a62 Motorola PCS
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x22b8 Motorola PCS
idProduct 0x2a62
bcdDevice 0.01
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 20mA
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 3
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 Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 3
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 0x0040 1x 64 bytes
bInterval 0
Syslog output:
Jan 30 21:43:21 positron udev[5316]: creating device node '/dev/vcs6'
Jan 30 21:43:21 positron udev[5317]: creating device node '/dev/vcsa6'
Jan 30 21:43:21 positron udev[5320]: creating device node '/dev/vcs2'
Jan 30 21:43:21 positron udev[5321]: creating device node '/dev/vcsa2'
Jan 30 21:43:22 positron udev[5324]: creating device node '/dev/vcs3'
Jan 30 21:43:22 positron udev[5325]: creating device node '/dev/vcsa3'
Jan 30 21:43:22 positron udev[5328]: creating device node '/dev/vcs4'
Jan 30 21:43:22 positron udev[5329]: creating device node '/dev/vcsa4'
Jan 30 21:43:22 positron udev[5331]: creating device node '/dev/vcs5'
Jan 30 21:43:22 positron udev[5356]: creating device node '/dev/vcsa5'
Jan 30 21:43:22 positron udev[5408]: creating device node '/dev/vcs7'
Jan 30 21:43:22 positron udev[5409]: creating device node '/dev/vcsa7'
Jan 30 21:43:55 positron kdm_greet[5426]: Can't open default user face
Jan 30 21:45:57 positron kernel: usb 1-1: new full speed USB device using uhci_hcd and address 2
Jan 30 21:46:03 positron kernel: cdc_acm 1-1:1.0: ttyACM0: USB ACM device
Jan 30 21:46:03 positron kernel: usbcore: registered new driver cdc_acm
Jan 30 21:46:03 positron kernel: drivers/usb/class/cdc-acm.c: v0.23:USB Abstract Control Model driver for USB modems and ISDN adapters
Jan 30 21:46:03 positron usb.agent[5613]: cdc-acm: loaded successfully
Jan 30 21:46:05 positron udev[5712]: creating device node '/dev/usbdev1.2'
Jan 30 21:46:05 positron udev[5713]: creating device node '/dev/ttyACM0'
Jan 30 21:47:40 positron kernel: Initializing USB Mass Storage driver...
Jan 30 21:47:40 positron kernel: usbcore: registered new driver usb-storage
Jan 30 21:47:40 positron kernel: USB Mass Storage support registered.
Ok, it seems that the serial port part of the device is recognized,
but I can't reach it. It appears that the USB mass storage driver
doesn't see the flash card in the phone.
Any clues, anyone? I would think I should be seeing something like
what is below.
> [ errors deleted ]
> Jan 29 22:18:05 zolnott06 kernel: usb 3-1: new full speed USB device using uhci_hcd and address 14
> Jan 29 22:18:05 zolnott06 kernel: scsi9 : SCSI emulation for USB Mass Storage devices
> Jan 29 22:18:05 zolnott06 kernel: usb-storage: device found at 14
> Jan 29 22:18:05 zolnott06 kernel: usb-storage: waiting for device to settle before scanning
> Jan 29 22:18:10 zolnott06 kernel: Vendor: Motorola Model: Motorola Phone Rev: 2.31
> Jan 29 22:18:10 zolnott06 kernel: Type: Direct-Access ANSI SCSI revision: 02
> Jan 29 22:18:10 zolnott06 kernel: SCSI device sdb: 990977 512-byte hdwr sectors (507 MB)
> Jan 29 22:18:10 zolnott06 kernel: sdb: Write Protect is off
> Jan 29 22:18:10 zolnott06 kernel: sdb: Mode Sense: 0b 00 00 08
> Jan 29 22:18:10 zolnott06 kernel: sdb: assuming drive cache: write through
> Jan 29 22:18:10 zolnott06 kernel: SCSI device sdb: 990977 512-byte hdwr sectors (507 MB)
> Jan 29 22:18:10 zolnott06 kernel: sdb: Write Protect is off
> Jan 29 22:18:10 zolnott06 kernel: sdb: Mode Sense: 0b 00 00 08
> Jan 29 22:18:10 zolnott06 kernel: sdb: assuming drive cache: write through
> Jan 29 22:18:10 zolnott06 kernel: sdb: sdb1
> Jan 29 22:18:10 zolnott06 kernel: sd 9:0:0:0: Attached scsi removable disk sdb
> Jan 29 22:18:10 zolnott06 kernel: usb-storage: device scan complete
> Jan 29 22:18:47 zolnott06 kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 14
> Jan 29 22:18:50 zolnott06 kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 14
> Jan 29 22:18:59 zolnott06 kernel: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
>
> Can anybody help to get this modem to work
>
> Using SID with udev 0.082
Since I'm using a quite recent SID kernel (2.6.15) this shouldn't be
much different. However, I don't know anything about udev. Any
specific device I should be aware of? mount /dev/sda1 /mnt (which
works with a camera with flash storage) doesn't work with the phone.
> CU
>
> Michael
Anyway, maybe you can compare the lsusb output to what's above. I hope
we can come up with something...
Augustine
Reply to:
- References:
- cdc_acm
- From: Michael Ott <michael@zolnott.de>