Briefly as it's been 40 degrees Celsius here and I've been outside
working all day (almost beer o'clock)
On 23/11/14 18:27, Marc Shapiro wrote:
> On 11/22/2014 04:09 PM, Scott Ferguson wrote:
>> 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.
<snipped>
>>>
>>> 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"
Did you try the above? If so, what results?
>>
>>> 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
Did you try this after applying the example rule three paragraphs up?
<snipped>
>>
>> You mention two devices - in which case I'd:-
>> ;suggest you turn on udev debugging (as root "udevadm control
>> --log-priority=debug")
Sorry - did you apply the above, and if so - what do the logs show?
(please post any relevant information for all to reference.).
> For now, I'm just trying to get my daughter's iPod connected. My wife
> says that she is only interested in getting photos and video off and I
> should be able to do that with shotwell. Shotwell works with unmounted
> devices and detects and accesses my daughter's iPod just fine, so will
> probably work with my wife's iPad Mini, as well.
>> ;*post* the output of "udevadm info"[*1] for both IPod devices) to
>> paste.debian.net and include a link in your reply.
>>
>> [*1] see the Ref below for an expansion on what I mean by that.
> The first thing that post says to do is to get the device node. That is
> my problem. I do not have a device node for the iPod (see the output
> from dmesg and my comments, above).
It's possible that a fusefs has "grabbed" the device... I have little
experience with Apple devices so this is a learning curve for me to. I'm
guessing you run GNOME - something else I have (very) little experience
with.
Please try unplugging the device, them, while running as root, "udevadm
monitor --property" and posting the results from plugging the Apple
device back in (if any).
> I tried the grep on
> /var/log/messages, as the post suggested, but it did not provide a
> device node. It gave pretty much the same as the dmesg output that I
> posted above:
>
> Nov 22 17:39:18 quixote kernel: [11593.557084] usb 4-4.4: USB
> disconnect, device number 8
> Nov 22 17:39:18 quixote kernel: [11593.789452] usb 4-4.4: new high-speed
> USB device number 9 using ehci-pci
> Nov 22 17:39:18 quixote kernel: [11593.885203] usb 4-4.4: New USB device
> found, idVendor=05ac, idProduct=12aa
> Nov 22 17:39:18 quixote kernel: [11593.885213] usb 4-4.4: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
> Nov 22 17:39:18 quixote kernel: [11593.885218] usb 4-4.4: Product: iPod
> Nov 22 17:39:18 quixote kernel: [11593.885222] usb 4-4.4: Manufacturer:
> Apple Inc.
> Nov 22 17:39:18 quixote kernel: [11593.885226] usb 4-4.4: SerialNumber:
> ea1f2a0800d76f91f9bc0d50d6620151d249e6a9
> Nov 22 17:39:18 quixote mtp-probe: checking bus 4, device 9:
> "/sys/devices/pci0000:00/0000:00:16.2/usb4/4-4/4-4.4"
> Nov 22 17:39:18 quixote mtp-probe: bus: 4, device: 9 was not an MTP device
Thanks. (do test the rule I posted - it 'should' work based on that
handy dmesg snip).
>
> It did not continue with any of the other lines such as you show and
> most specifically, does not provide a device node.
OK. Again, thanks for the useful information (your efforts are much
appreciated as I don't have the devices to analyse).
> I had already looked
> in /dev/disk/by-path, but there is nothing there. If I had a device
> node then I would not have posted the question, since I would have been
> able to mount the device and use gtkpod. My problem is the *lack* of a
> device node.
Let's see what the use of the rule I posted, the logs, and the output of
"udevadm monitor --property" show. What you desire *is* possible, just
difficult as I don't have the device, and your system, on hand to test.
Your patience is greatly appreciated.
Kind regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5471998b.3080...@gmail.com
