Menu
▾
▴
#2 device undetected
I am trying to connect a Sansa C150 to Amarok on a FC6 PC and have repeated 'cannot connect to MTP device' errors.
When connected I ran mtp-detect with this result
"# mtp-detect
Found non-autodetected device "SanDisk Sansa c150" on USB bus...
usb_claim_interface(): Device or resource busy
Connection error.
No devices."
there is an entry in the rules.d/libmtp.rules for Sansa c150
What steps need I take to allow mtp transactions ?
Discussion
Anonymous
Logged In: YES
user_id=1705062
Originator: YES
I don't know if this will expedite any resolution of this vexing matter but the previously mentioned file says
<deviceinfo>
<wmpdeviceid =="" "{c77d97d5-6118-4dda-928d-a81df4b2e452}"relationshipid"{00000000-0000-0000-0000-000000000000}"=""></wmpdeviceid></deviceinfo>
Logged In: YES
user_id=1705062
Originator: YES
this information has been provided by 'usbutils'
Bus 005 Device 005: ID 0781:7410 SanDisk Corp.
Logged In: YES
user_id=473872
Originator: NO
Please upgrade firmware. This is a common problem on the Sansas.
Logged In: YES
user_id=1705062
Originator: YES
[quote]Please upgrade firmware. This is a common problem on the Sansas.[/quote]
the only firmware upgrade available is to a previous version
perhaps you can indicate which is the 'known good' firmware version
Logged In: YES
user_id=1705062
Originator: YES
Device firmware - 2.0.007
I contacted Sandisk who reponded with
[quote]
The firmware Version was: 1.0.003A or 2.0.007(2 different version, v1 can not be upgraded to v2). There was no official firmware update ever published for Sansa c100 series.[/quote]
So perhaps closing this bug report with "Please upgrade firmware. This is a common problem on the Sansas." is possibly premature
Logged In: YES
user_id=473872
Originator: NO
Sorry man, my wrong. Too much to do and too many devices out there
makes things mix up in my head :-/
Logged In: YES
user_id=1705062
Originator: YES
So I was wondering, need I re-sumbit this bug report/request or will it be re-opened at some time ?
Logged In: YES
user_id=473872
Originator: NO
I already reopened it with the last comment on my
erroneous statements...
If you want to help out in testing and development,
please try using CVS version and join the libmtp
mailinglist to discuss issues with this device, we
need you!
Logged In: YES
user_id=1705062
Originator: YES
I posted this 'problem' on one of the Linux forums and received this reply
[quote]I was able to successfully connect to my Sansa c150.
The problem is udev configures the usb-storage and prevents libmtp from accessing the device.
As root,
(1) unload usb-storage
(2) temporarily move usb-storage.ko out of the way
(3) plug-in your Sansa c150
You will now be able to use mtp commands to access the
mtp-only files.[/quote]
It seems like a radical step to disable USB storage devices to enable MTP access
Logged In: YES
user_id=473872
Originator: NO
Does it work to temporarily blacklist usb-storage i /etc/modprobe.d/blacklist?
Logged In: YES
user_id=1705062
Originator: YES
[quote]Does it work to temporarily blacklist usb-storage i
/etc/modprobe.d/blacklist?[/quote]
NOPE
"MTP device not detected"
Logged In: YES
user_id=1705062
Originator: YES
libMTP has been updated and I have the ability to use the MTP to view files on the Sansa but remain beset by 'unable to write to device' messages when attempting a transfer from the PC to the MP3 player
Logged In: YES
user_id=1705062
Originator: YES
About 8 weeks ago I reported that the latest libmtp allows the amarok software to detect the Sansa C150 at
Bus 005 Device 010: ID 0781:7410 SanDisk Corp.
but the device will not accept read/write from either 'user' or 'root'
So the installed files and playlists may be seen but not manipulated
I was wondering of other users of this device experienced these difficulties
Logged In: YES
user_id=473872
Originator: NO
Very strange this :-/
I don't know if it could be related to the problems
caused by drivers needing to be unloaded, but I don't
think so...
Sorry for asking perhaps obvious things, but does track
transfer work in either direction if you:
Use the libmtp example tools like mtp-sendtr
as root,
Dito, but as a regular user, not root
If you transfer just data files with mtp-sendfile
as root
Dito, as a regular user...
Linus
Logged In: YES
user_id=1705062
Originator: YES
[quote]1. Use the libmtp example tools like mtp-sendtr
as root,[/quote]
Does something, quite a lot of timing out but ends eventually.
Unfortunately the track isn't transferred
Logged In: YES
user_id=1705062
Originator: YES
[quote]root@usaidwot Only Ones-The Only Ones]# mtp-sendtr --sendtrack 02\ -\ Another\ Girl\,\ Another\ Planet.mp3 /media/Sansa\ c150/
PTP: Opening session
PTP: request code 0x1002 sending req wrote only 0 bytes instead of 16
PTP_ERROR_IO: Trying again after resetting USB
inep: usb_get_endpoint_status(): Connection timed out
outep: usb_get_endpoint_status(): Connection timed out
usb_clear_halt() on IN endpoint: Connection timed out
usb_clear_halt() on OUT endpoint: Connection timed out
usb_clear_halt() on INTERRUPT endpoint: Connection timed out
PTP: Opening session
LIBMTP PANIC: Could not open session! (Return code 765)
Try to reset the device.
LIBMTP PANIC: configure_usb_devices() error code: 7 on line 1686
LIBMTP_Get_First_Device: Error Connecting
No devices.
[root@usaidwot Only Ones -The Only Ones]#
[/quote]
takes almost a minute for this to fail
Logged In: YES
user_id=473872
Originator: NO
Sadly, I'm totally out of ideas for this problem :-/
Too old, set to pending.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).