Jaunty fails to recognize USB-connected cell phone as device

Bug #368053 reported by bedhead75
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I did a fresh install of Jaunty 9.04 64-bit. My LG Shine (VX-8700) shows up as connected to "Bus 006 Device 002" when I type "lsusb" in the terminal, but it doesn't list as a connected device when I type "df". When I was using Hardy or Interpid, I believe it would also show up as "/dev/ttyACM0", but not in Jaunty. Bitpim lists "/dev/ttyACM0" as an inoperable port, even when run as root so I don't think this is a USB permissions problem. Here is the output given by "dmesg" in the terminal after connecting the phone:

[ 7019.108011] usb 6-2: new full speed USB device using uhci_hcd and address 2
[ 7019.271321] usb 6-2: configuration #1 chosen from 1 choice
[ 7019.298318] cdc_acm 6-2:1.0: ttyACM0: USB ACM device
[ 7019.301177] usbcore: registered new interface driver cdc_acm
[ 7019.301180] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
[ 7086.232274] usb 2-4: usbfs: interface 0 claimed by usb-storage while 'python' sets config #1
[ 7086.235184] usb 6-2: usbfs: interface 0 claimed by cdc_acm while 'python' sets config #1
[ 7086.236513] usb 6-2: usbfs: USBDEVFS_CONTROL failed cmd python rqt 128 rq 6 len 255 ret -71
[ 7086.237513] usb 6-2: usbfs: USBDEVFS_CONTROL failed cmd python rqt 128 rq 6 len 255 ret -71
[ 7086.237610] usb 6-2: usbfs: interface 0 claimed by cdc_acm while 'python' sets config #1
[ 7086.239512] usb 6-2: usbfs: USBDEVFS_CONTROL failed cmd python rqt 128 rq 6 len 255 ret -71
[ 7086.240551] usb 6-2: usbfs: USBDEVFS_CONTROL failed cmd python rqt 128 rq 6 len 255 ret -71

Revision history for this message
rado3105 (vlasodar) wrote :

same here, problem with hp laserprinter 1018

Revision history for this message
A7Bo (a7bo) wrote :

I have the same problem as "bedhead75." Bitpim worked and my LG vx8350 was autodetected in Ubuntu (Kubuntu) 8.04 with Bitpim 1.0.2 . My output from dmesg is:

[ 847.996013] usb 2-3: new full speed USB device using ohci_hcd and address 7
[ 848.208094] usb 2-3: configuration #1 chosen from 1 choice
[ 848.211083] cdc_acm 2-3:1.0: ttyACM1: USB ACM device
[ 1087.733124] usb 2-2: usbfs: interface 1 claimed by usblp while 'python' sets config #1
[ 1087.759149] usb 2-2: usbfs: interface 1 claimed by usblp while 'python' sets config #1
[ 1087.777132] usb 2-2: usbfs: interface 1 claimed by usblp while 'python' sets config #1
[ 1087.804114] usb 2-2: usbfs: interface 1 claimed by usblp while 'python' sets config #1
[ 1092.833110] usb 2-2: usbfs: interface 1 claimed by usblp while 'python' sets config #1
[ 1092.859141] usb 2-2: usbfs: interface 1 claimed by usblp while 'python' sets config #1
[ 1092.877133] usb 2-2: usbfs: interface 1 claimed by usblp while 'python' sets config #1
[ 1092.904116] usb 2-2: usbfs: interface 1 claimed by usblp while 'python' sets config #1
[ 1436.481643] usb 2-3: USB disconnect, address 7

Revision history for this message
Chris (bridgeriver) wrote :

In my case (Jaunty AMD64, Sanyo Katana II) I'm getting the same dmesg output as A7Bo, but the symptoms are different as seen from bitpim. There, /dev/ttyACM0 is accessible, as is one of the two ports needed to access the phone. At the moment usb::002::014::2 is accessible but usb::002::014::1 is not.

This is after I modified the file /lib/udev/rules.d/40-bitpim.rules, adding the text

  GROUP="plugdev",

to each line. Before that the device (e.g., /dev/bus/usb/002/014) showed up with group "root" and both its ports were inaccessible from bitpim run as a normal user. Now the device is created with group "plugdev".

Interestingly, the program /lib/udev/bpudev which the rules file points to appears not to be getting executed. Therefore any changes to it, or to /etc/default/bitpim (which it invokes to set the default user and group for the devices) are not applied.

I tried running bitpim using gksudo, and even then only one of these two ports was accessible. So it seems it's not a permissions problem any more.

Revision history for this message
R (Chandra) Chandrasekhar (chandra) wrote :

On Kubuntu Karmic 9.10 I have the same problem with an Sony Ericsson K750i mobile phone.

Here is what I did to get around the problem:

1. sudo apt-get install usbmount pmount

2. Create /etc/udev/rules.d/75-mobile-phone.rules with this content:

SUBSYSTEM!="usb_device", ACTION!="add", GOTO="mobile_phone_rules_end"

# Sony Ericsson K750i mobile phone
SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="d016", GROUP="plugdev", MODE="0660"

LABEL="mobile_phone_rules_end"

3. Check that dmesg | tail had something like this:

[ 9833.932132] scsi 15:0:0:0: Direct-Access Sony Eri Memory Stick 0000 PQ: 0 ANSI: 0
[ 9833.933302] sd 15:0:0:0: Attached scsi generic sg3 type 0
[ 9833.972064] sd 15:0:0:0: [sdc] 124416 512-byte logical blocks: (63.7 MB/60.7 MiB)
[ 9833.982224] sd 15:0:0:0: [sdc] Write Protect is off
[ 9833.982235] sd 15:0:0:0: [sdc] Mode Sense: 00 6a 00 00
[ 9833.982242] sd 15:0:0:0: [sdc] Assuming drive cache: write through
[ 9834.015020] sd 15:0:0:0: [sdc] Assuming drive cache: write through
[ 9834.015029] sdc: sdc1
[ 9834.055064] sd 15:0:0:0: [sdc] Assuming drive cache: write through
[ 9834.055076] sd 15:0:0:0: [sdc] Attached SCSI removable disk

4. pmount /dev/sdc1 /media/usb0

5. cd /media/usb0

to access the mobile phone as a mass storage device.

6. cd ~/; pumount /media/usb0

to unmount the device.

This workaround was suggested by

http://ubuntuforums.org/showpost.php?p=6204815&postcount=13

I do not understand the intricacies of how this works or whether it will always work, but it enabled me to download the images from my mobile phone in Karmic, something that I was able to do in previous releases but not in Karmic.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi bedhead75,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 368053

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
David Ayers (ayers) wrote :

I have this issue on Karmic and Lucid but I seems that I cannot add my data...

You are not the reporter of bug 368053.
Is that really the bug you want to update? [y/N]y
Bug title: Jaunty fails to recognize USB-connected cell phone as device
Collecting apport information for source package linux...
Uploading additional information to Launchpad bug...
   short text data...
Traceback (most recent call last):
  File "/usr/bin/apport-collect", line 173, in <module>
    upload(report, bug)
  File "/usr/bin/apport-collect", line 52, in upload
    subject='apport-collect data')
  File "/usr/lib/python2.6/dist-packages/lazr/restfulclient/resource.py", line 448, in __call__
    args[key] = simplejson.dumps(value, cls=DatetimeJSONEncoder)
  File "/usr/lib/pymodules/python2.6/simplejson/__init__.py", line 237, in dumps
    **kw).encode(obj)
  File "/usr/lib/pymodules/python2.6/simplejson/encoder.py", line 194, in encode
    return encode_basestring_ascii(o)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xff in position 1207: unexpected code byte

Revision history for this message
David Ayers (ayers) wrote :

Sorry... wrong bug report.. I'm having the same messages when trying to connect a LaserJet 6MP via parallel / USB cable... not a phone.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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