On 23/11/14 09:50, Marc Shapiro wrote:
My daughter has recently purchased an iPod Touch and would like to be
able to maintain it from our linux box running Wheezy. My wife has an
iPad Mini and it would be nice to be able to maintain that from the
linux box, as well. I have googled. I have upgraded to the latest
kernel from Backports (3.16). I have installed libimobiledevice-utils.
I have done everything I can think of.
When I plug the device in I get the following in dmesg:
[ 127.569680] usb 4-4.4: new high-speed USB device number 6 using ehci-pci
[ 127.665562] usb 4-4.4: New USB device found, idVendor=05ac,
idProduct=12aa
[ 127.666054] usb 4-4.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 127.666538] usb 4-4.4: Product: iPod
[ 127.667021] usb 4-4.4: Manufacturer: Apple Inc.
[ 127.667517] usb 4-4.4: SerialNumber:
ea1f2a0800d76f91f9bc0d50d6620151d249e6a9
You will note that there is no mention of a mountable device node. I
have added a file, '50-custom.rules' in /etc/udev/rules.d that contains
the line:
BUS=="scsi", ATTRS{idVendor}=="05ac", ATTRS{idProduct}=="12aa",
ATTRS{serial}=="ea1f2a0800d76f91f9bc0d50d6620151d249e6a9",
NAME{all_partitions}="ipod", GROUP="plugdev"
Should be "BUS=="usb"
Also, MODE="0660"
Note that you:-
;only need to supply enough rules to match the device (minimum of 2 from
memory) I'd suggest you use BUS and ATTRS{serial}.
;you haven't mentioned what you want to "do" with the device i.e. mount
it somewhere - or "who" should do that. Please let me know what you want
to do (I don't know anything about gtkpod requirements)
Example only - this will work - but should be modified to suit your
requirement (please read further down):-
ATTRS{serial}=="ea1f2a0800d76f91f9bc0d50d6620151d249e6a9",
ATTRS{manufacturer}=="Apple Inc.", ATTRS{product}=="iPod",
KERNEL=="sd?1", SYMLINK+="ipod", GROUP="plugdev", MODE="0660"
I then tried connecting the device again. Still nothing. I rebooted
with the device attached. Nothing.
Apologies - I'm rushed today and don't have time to check my notes. Try:-
udevadm control --reload-rules
What am I doing wrong?
Not supplying dense walls of text describing your circumstances? ;)
You mention two devices - in which case I'd:-
;suggest you turn on udev debugging (as root "udevadm control
--log-priority=debug")