[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: USB ACM vs USB memory device conflict



On Thu, Sep 15, 2011 at 02:44:28PM +0000, Camaleón wrote:
> On Wed, 14 Sep 2011 18:06:40 -0400, Thomas H. George wrote:
> 
> > I purchased a Verizon Samsung SHU-u370 cell phone and installed a
> > microSD card.  When connected to a usb port the phone registers as an
> > ACM device, specifically as ttyACM0.  The settins on the phone allow a
> > choice between Media Sync Mode and Modem modem and clearly the Debian
> > kernel has chosen the latter though the phone is set for the former. The
> > manual for the phone says it should appear as a new cd drive (presumably
> > when connected to a Windows system, not having a Windows system I have
> > not tried this).
> > 
> > Any ideas as to how I can persuade my Debian system to cancel the ACM
> > setting which I am unlikely to need and recognize the phone as a mass
> > storage device?
> 
> The fact the device is recognized as a modem and does not detect the µSD 
> card on it usually means that you need to make an additional step to 
> configure the phone, but IIRC, most of these devices need to be put as 
> what it is call "USB Mass Storage" and not as "modem" nor for "syncing" 
> options which allow another features. 
> 
> I would investigate this further by reading the mobile phone's manual :-? 
> 
The phone's manual instructions are to connect the usb cable and then in
settings/tools chose USB Mass Storage.  My problem is that immediately
upon connecting the usb cable the phone is choosen as a modem.  When I
select the USB Mass Storage option the phone displays a picture of a
phone and a pc with a dot bouncing back and forth between them but there
is no indication on the Debian terminal of any change.  Leaving the
phone in this mode I disconnect and reconnect the usb cable.  The result
shown in syslog is 


Sep 15 13:10:44 dragon kernel: [17977.120523] usb 1-2: new high speed USB device using ehci_hcd and address 117
Sep 15 13:10:44 dragon kernel: [17977.254938] usb 1-2: New USB device found, idVendor=04e8, idProduct=68ab
Sep 15 13:10:44 dragon kernel: [17977.255656] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 15 13:10:44 dragon kernel: [17977.256587] usb 1-2: Product: SCH-U370
Sep 15 13:10:44 dragon kernel: [17977.257615] usb 1-2: Manufacturer: SAMSUNG
Sep 15 13:10:44 dragon kernel: [17977.258650] usb 1-2: SerialNumber: A0000002AE7C33400000000000000000
Sep 15 13:10:44 dragon kernel: [17977.259919] usb 1-2: configuration #1 chosen from 1 choice

Normally this would include an indication that the device is connected
as ssd or ssd1.  Neither of these can be mounted.

I think there must be a way to tell udev or the kernel to let go of the
device ttyACM0 and recognize a usb connection to a mass storage device.

Tom


Reply to: