This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Rockbox player problem

Tags: None
(comma "," separated)
User avatar
marcel
Registered Member
Posts
595
Karma
0
OS

Rockbox player problem

Tue Jan 05, 2010 5:23 pm
Hi,

I have a somewhat weird problem with Amarok 2 and my Rockbox player. Here's what happens:

Amarok is not running, I plug in the player. dmesg says
usb 2-3: Product: Rockbox media player
usb 2-3: Manufacturer: Rockbox.org


It detects correctly that it is a mass-storage USB device and lists the partitions. The device shows up in KDE4's device notifier.

But if I now start Amarok, my player gets removed from the device notifier and dmesg now says:

usb 2-3: usbfs: process 7143 (amarok) did not claim interface 0 before use
usb 2-3: reset high speed USB device using ehci_hcd and address 16


If I plug in the player while Amarok is running, I get the same message as above and the player never shows up in the device manager.

So far, I failed to find any explanation for this behavior or any solution to my problem. Other (non-media-player) USB devices work just fine with Amarok running.
Any hints what is going wrong here?

Thanks a lot,
Marcel
User avatar
google01103
Manager
Posts
6668
Karma
25

Re: Rockbox player problem

Tue Jan 05, 2010 7:11 pm
I think maybe you're running an older version of Amarok as I had a similar issue with my RockBox. I think it was resolved in the 2.1 release.


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
marcel
Registered Member
Posts
595
Karma
0
OS

Re: Rockbox player problem

Wed Jan 06, 2010 8:35 am
I have this problem consistently for a while, including 2.2.1, and now running the latest beta from Debian Experimental.
User avatar
marcel
Registered Member
Posts
595
Karma
0
OS

Re: Rockbox player problem

Mon Jan 11, 2010 5:06 pm
Answering my own question, it seems hal is reporting the device as mtp for some reason. Amarok then tries to automatically connect to it which of course does not work and somehow prevents it from being listed as a USB storage device afterwards.

I fixed this for the moment by removing all Sansa-related entries from /usr/share/hal/fdi/information/20thirdparty/20-libmtp8.fdi
(that's for Debian. I heard there might be similar entry in gphoto.fdi if present).
Not elegant, but it works for me.


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]