1 |
On Fri, Jul 25, 2014 at 11:49 AM, walt <w41ter@×××××.com> wrote: |
2 |
|
3 |
> On 07/23/2014 09:59 PM, Walter Dnes wrote: |
4 |
> > I sent this a day or 2 ago, but it doesn't show up on the list for me. |
5 |
> > Apologies to anyone seeing a duplicate. |
6 |
> > |
7 |
> > I'm a total noobie at mtpfs/FUSE. My "excellent adventure" started |
8 |
> > yesterday when I got a clearout 7" tablet, and took a sample photo, and |
9 |
> > tried mounting the tablet... no /dev/sdb to be found anywhere. I went |
10 |
> > to "Mr. Google" for help, and found out that MTP is the "new and |
11 |
> > improved" way of doing things. So I installed mtpfs. It works great |
12 |
> > for root, but a regular user can't mount the tablet. The mtpfs command |
13 |
> > immediately returns to the command prompt, with no error message or any |
14 |
> > other info. The tablet is not mounted... |
15 |
> > |
16 |
> > [d531][waltdnes][~] mtpfs ~/tablet |
17 |
> > [d531][waltdnes][~] |
18 |
> > |
19 |
> > Before anyone asks... |
20 |
> > |
21 |
> > 1) Yes, I have enabled FUSE in the kernel. At first I hadn't, but I got |
22 |
> > a big red warning when I tried compiling mtpfs. I tweaked and rebuilt |
23 |
> > the kernel, and rebooted, then built mtpfs. |
24 |
> > |
25 |
> > 2) Yes, I am a member of plugdev... |
26 |
> > |
27 |
> > [d531][root][~] grep plugdev /etc/group |
28 |
> > plugdev:x:247:waltdnes,user2 |
29 |
> > |
30 |
> > 3) This PC uses mdev rather than udev. Could that be the problem? |
31 |
> > |
32 |
> > I've figured out a kludge to get around it. This involves issuing a |
33 |
> > few commands as root. I've added them into a file in /etc/sudoers.d/ |
34 |
> > but I'd really rather prefer a cleaner solution. |
35 |
> > |
36 |
> > [d531][root][~] mtpfs -o allow_other /home/waltdnes/tablet |
37 |
> > Device 0 (VID=0bb4 and PID=2008) is UNKNOWN. |
38 |
> > Please report this VID/PID and the device model to the libmtp |
39 |
> development team |
40 |
> > Android device detected, assigning default bug flags |
41 |
> > |
42 |
> > When I was finished, I tried... |
43 |
> > |
44 |
> > [d531][waltdnes][~] fusermount -u tablet |
45 |
> > fusermount: entry for /home/waltdnes/tablet not found in /etc/mtab |
46 |
> > |
47 |
> > I had to unmount as root... |
48 |
> > |
49 |
> > [d531][root][~] fusermount -u /home/waltdnes/tablet |
50 |
> > |
51 |
> > I experienced similar problems with simple-mtpfs, so that's not a |
52 |
> > solution either. Any ideas? |
53 |
> |
54 |
> I vaguely remember suffering through the same problem when I bought my |
55 |
> Nexus7 |
56 |
> tablet from google about a year ago. (My memories now are a bit fuzzy.) |
57 |
> |
58 |
> I believe I had to add this file manually: |
59 |
> |
60 |
> #cat /etc/udev/rules.d/51-android.rules |
61 |
> |
62 |
> SUBSYSTEM=="usb",ATTRS{idVendor}=="18d1",ATTRS{idProduct}=="4e41",MODE="0666",OWNER="wa1ter" |
63 |
> |
64 |
> I harvested those hex numbers from running "lsusb -v" IIRC. |
65 |
> |
66 |
> |
67 |
The idea behind w41ter's plan is to make sure that the device file |
68 |
corresponding to the mtp device is read-writable by the user running mtpfs. |
69 |
|
70 |
You mentioned that you are a member of the plugdev group, but does the |
71 |
plugdev group actually get ownership of the mtp device? This is something |
72 |
you'll have to investigate in your mdev rules. |
73 |
|
74 |
|
75 |
|
76 |
|
77 |
-- |
78 |
This email is: [ ] actionable [ ] fyi [ ] social |
79 |
Response needed: [ ] yes [ ] up to you [ ] no |
80 |
Time-sensitive: [ ] immediate [ ] soon [ ] none |