Your message dated Sat, 21 Nov 2015 11:45:23 +0100
with message-id
and subject line
has caused the Debian Bug report #676431,
regarding mtpfs: Device 0 (VID=17ef and PID=74cc) is UNKNOWN - LIFETAB_S9512
Manufacturer: LENOVO
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
676431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mtpfs
Version: 1.1-2
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
try mounting the device
* What exactly did you do (or not do) that was effective (or
ineffective)?
mount.mtpfs /mnt/android/
* What was the outcome of this action?
Listing raw device(s)
Device 0 (VID=17ef and PID=74cc) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp
development team
Found 1 device(s):
17ef:74cc @ bus 2, dev 13
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB
interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
usbview shows:
shows following data:
LIFETAB_S9512
Manufacturer: LENOVO
Serial Number: FD00026216
Speed: 480Mb/s (high)
USB Version: 2.00
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 17ef
Product Id: 74cc
Revision Number: 2.16
Config Number: 1
Number of Interfaces: 2
Attributes: c0
MaxPower Needed: 500mA
Interface Number: 0
Name: usbfs
Alternate Number: 0
Class: ff(vend.)
Sub Class: ff
Protocol: 00
Number of Endpoints: 3
Endpoint Address: 81
Direction: in
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 0ms
Endpoint Address: 02
Direction: out
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 0ms
Endpoint Address: 82
Direction: in
Attribute: 3
Type: Int.
Max Packet Size: 28
Interval: 4ms
Interface Number: 1
Name: usb-storage
Alternate Number: 0
Class: 08(stor.)
Sub Class: 06
Protocol: 50
Number of Endpoints: 2
Endpoint Address: 83
Direction: in
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 0ms
Endpoint Address: 03
Direction: out
Attribute: 2
Type: Bulk
Max Packet Size: 512
Interval: 125us
dmesg shows:
usb-storage: *** thread sleeping.
usb-storage: queuecommand_lck called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x5c1a L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x5c1a R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
* What outcome did you expect instead?
correct mount ;-)
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.4.0 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mtpfs depends on:
ii fuse-utils2.9.0-1
ii libc6 2.13-33
ii
