![]() ![]() In MSC mode, it behaves as any other USB storage device-you can drag and drop files onto the device through your file manager. The Sansa Fuze can work in two USB modes: MTP and MSC. setting the Fuze to MTP mode rather than AutodetectĪnyway, if you'd like to know what steps I've done so far, here are my instructions from another thread:.hotplug.sh from the libmtp 0.3.7 source directory I ran into the lock-up problem, mentioned in this thread, but one of two steps seems to have solved it (not sure which one): I have the Sansa Fuze version 2 player working flawlessly with Amarok 2 right now. So at the moment it appears that the MTP support for the Version 2 of the Fuze does not work. I do not get the last 3 lines.Īfter changing the rules files I run the mtp-connect command and it shows a line with the Fuze and it's ID still being 0x74c0. If I look at the file /etc/udev/rules.d/les at lines 147/148 and 472/473 has the ID of the Fuze as 0x74c0.Īfter I change those lines to 0x74c2 and run the mtp-detect command it gives me screens and screens of info but locks up towards the end.Ī user with a version 1 Fuze shows this as their output of mtp-detect. ![]() When I run the command mtp-detect it shows "no raw devices found. When I connect the version 2 Fuze in MTP mode it has an ID of 0x74c2. usr/share/hal/fdi/information/10freedesktop/10-usb-music-players.fdi ![]() To get the purdy music player icon on my Desktop and Rhythmbox to recognise it as a player device I had to add that ID to the Fuze line in the file: In MSC mode the version 2 Fuze has a ID of 0x74c3 when I do run the lsusb command. I have my Fuze working perfectly in MSC mode and I do not intend using it in MTP mode but I wanted to share what I found when trying to. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |