Alright, I think we might be right on the cusp of solving the problem - I had copied the command and only changed the path to match where I wanted it to be mounted. Now I’ve done everything exactly like you, as far as I can tell, like this:
so erget did you get it finally working all like you want? hope you did!
I am still waiting for my xoom and because of bank holiday weekend need to wait at least till Tuesday http://forums.opensuse.org/images/smiliesnew/angry.png but when I get it I definitely will need your experience on how you managed working it
Alright, getting closer maybe? The directory xoom did exist and had all permissions, but just to be safe I did it again and then tried to mount again. Here’s the output:
linux-hr34:/ # chmod 777 /xoom/
linux-hr34:/ # mtpfs -o allow_other /xoom
linux-hr34:/ # cd xoom
bash: cd: xoom: Transport endpoint is not connected
linux-hr34:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 472467736 63912156 384555532 15% /
devtmpfs 1919144 204 1918940 1% /dev
tmpfs 1925904 2424 1923480 1% /dev/shm
/dev/sda2 472467736 63912156 384555532 15% /
df: `/xoom': Transport endpoint is not connected
Interestingly enough, ls xoom shows me (like before) that the transport endpoint’s not connected, but when I plug the xoom in I can see the folder structure in Dolphin because it’s recognized as a media device. I can’t change anything though, and I can’t go inside the folders.
If I try to mount as a normal user I get the bad moint point thing again, but the directory exists, permissions are alright and I tried it with no trailing slashes.
Only difference is the Banshee library, I installed it after I saw that you had it and it’s only 2.0.0 rather than 2.0.1, but I think that should be alright because I don’t use Banshee. Or do you think that might be the problem? I’m feeling really confused. Thanks!
Alright, I just tried deleting the rules files, then I restarted udev and connected the Xoom. It was recognized as an external media player, so the restart must have been successful. mtpfs still gives me the same error with the bad mount point. :disapointed:
If I’m understanding you correctly, it shouldn’t be recognized as a media device anyway, because I want to be mounting it with mtpfs, right?
Honestly, I’m kind of scared to mess with the rules - would it be possible to disable them all by just putting a ~ in front of them and then test it, and then try switching them on one by one if it works? It’s true that there’s not a lot I could break there because I could always un-rename them with a live system, but that would be such a pain and I really need my system to work well in the other ways too. Maybe it would just be better to wait until somebody makes a program or updates an existing program to be able to deal with the Xoom, rather than all this DIY-ing? But then again that could take a really long time.
I will need to compare the rules you have to the ones I have. One that sticks out is “81-mptctl.rules”, could you list
the contents. Disabling a rule file is done (I think) by having the file not end in .rules usually mv xx-file.rules to xx-file.rules.hold.
When I connect the Xoom to my computer by USB it doesn’t pop up any more, since I deleted the old rules. I’ll deactivate that one as soon as I’m back, I got it by remote and will be out of town until the weekend. Then I can experiment some.