Ubuntu
libgphoto2 package

Philips GoGear ViBE (set to MSC) recognized as MTP

Bug #616596 reported by Darryl Rees on 2010-08-12

This bug affects 3 people

Affects

Status

Importance

Assigned to

Milestone

libgphoto2 (Ubuntu)

Triaged

Undecided

Unassigned

You need to log in to change this bug's status.

Affecting:	libgphoto2 (Ubuntu)
Filed here by:	Darryl Rees
When:	2010-08-12
Confirmed:	2010-09-01

Target

Distribution
Package	(Find…)
Project	(Find…)

Status	Importance
	Undecided

Assigned to

	Nobody
	Me

Comment on this change (optional)

Email me about changes to this bug report

(?)

Bug Description

Binary package hint: udev

Philips GoGear ViBE (usb vendor/model = 471/2075) is set to MSC but recognized as MTP by udev. ('s brokened)

Fix for me was to comment out line 785 of /lib/udev/rules.d/40-libgphoto2-2.rules
#ATTRS{idVendor}=="0471", ATTRS{idProduct}=="2075", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="proprietary", ENV{ID_MEDIA_PLAYER}="1", MODE="0664", GROUP="plugdev"

but this would obviously break udev for someone who wanted to use MTP. I don't know how to make generalized fix, or how to make direct bugreport to udev developers.

I have attached output from:

udevadm monitor --udev --kernel --property
#plug device in
dmesg | tail -10
udevadm info --query=property --name=/dev/bus/usb/001/...
udevadm test /devices/pci0000:00/0000:00:1d.7/usb1/...
udevadm monitor --udev --kernel --property
#unplug device
dmesg | tail -10

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: udev 151-12
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
Architecture: i386
Date: Thu Aug 12 09:32:48 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Acer Aspire 4710
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic root=UUID=d6d8d71d-dc09-4616-93a3-750801189e52 ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_AU.utf8
SHELL=/bin/bash
SourcePackage: udev
dmi.bios.date: 08/10/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.07
dmi.board.name: Volvi
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.07:bd08/10/2007:svnAcer:pnAspire4710:pvr0100:rvnAcer:rnVolvi:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 4710
dmi.product.version: 0100
dmi.sys.vendor: Acer

Tags: Edit Tag help

Darryl Rees (dardie) wrote on 2010-08-12:

Troubleshooting info from udevadm Edit (19.2 KiB, application/octet-stream)
BootDmesg.txt Edit (49.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (122.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (13.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (468 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (122.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (254.2 KiB, text/plain; charset="utf-8")

Darryl Rees (dardie) wrote on 2010-08-12:

Umm - obviously I already 'fixed' the problem on my system and the device mounted ok; P'raps I should have rebrokened it before running ubuntu-bug so that all the system files that automatically get attached reflect the problem. Nonethess I think all the info needed is in my attachment 'Troubleshooting info from udevadm'. If not let me know.

Martin Pitt (pitti) wrote on 2010-08-26:

What's wrong with using the device in MTP mode? And what is "MSC", "mass storage"?

affects:	udev (Ubuntu) → libgphoto2 (Ubuntu)
Changed in libgphoto2 (Ubuntu):
status:	New → Incomplete

Darryl Rees (dardie) wrote on 2010-08-27: Re: [Bug 616596] Re: Philips GoGear ViBE (set to MSC) recognized as MTP

MSC = Mass Storage Class = UMS
http://en.wikipedia.org/wiki/USB_mass-storage_device_class

a) MTP didn't work out of the box with ViBE as a mountable filesystem
b) I've always had issues in the past with MTP, so I just set to MSC which
is more of an industry standard and is more mature on linux
c) it works on Karmic
d) a cursory search of launchpad reveals similar bugs for other devices
which were considered worth fixing:
https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/330383
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/236422
https://bugs.launchpad.net/ubuntu/+bug/345916

I set the device to MSC so it should be detected as MSC. (And is, when the
offending rule is removed).

lsusb output showing the ViBE identifying as a Mass Storage class device.
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk (Zip)
      iInterface 4 USB/MSC LCD Player

Martin Pitt (pitti) wrote on 2010-09-01:

Thanks, setting to triaged then.

Changed in libgphoto2 (Ubuntu):
status:	Incomplete → Triaged

Peter (petru-severin) wrote on 2015-12-01:

This bug was never fixed but it's still present. I also see this bug with a slightly different version of the same GoGear Vibe device. Product id as identified by lsusb is 207b.

The fix is the same as above but now involves removing or commenting out the line 218 in file /lib/udev/rules.d/69-libmtp.rules (which is part of libmtp-common package) as follows:

# Philips GoGear ViBE SA1VBE04/08
# ATTR{idVendor}=="0471", ATTR{idProduct}=="207b", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"