linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Convey <cconvey@cox.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem getting udev to see Kodak camera?
Date: Wed, 24 Nov 2004 01:29:20 +0000	[thread overview]
Message-ID: <41A3E3F0.5050402@cox.net> (raw)
In-Reply-To: <41A2C9EA.6040906@cox.net>

Hey Kay,
Thanks for the help.

The list of cameras given on:
    http://www.gphoto.org/proj/libgphoto2/support.php
does list my camera, so at least on one level I'm in good shape.

I'm not positive, but I think back in my Fedora Core 2/3 days this 
camera was accessible to gphoto as a regular camera, and was accessible 
as a USB mass storage device (i.e., /dev/sda1).


My understanding is that software gets called in the following sequence 
(ideally). Is it correct?

1. usb driver tells kernel that a usb device was plugged in.
2. kernel invokes /sbin/hotplug, which in turn invokes:
3. /etc/hotplug.d/default/10-udev.hotplug (link to /sbin/udevsend)
4. udev invokes the rules in /etc/udev/rules.d/* in lexical order until
    one catches the event.
5. I've created a file named /etc/udev/rules.d/10-local.rules
    It just just this one line:
    SYSFS{manufacturer}="Eastman Kodak Company", \
    SYSFS{serial}="KCTCT42820593", NAME="%k", SYMLINK="/dev/my-camera"

If I understand this properly, then is my best bet just to put "echo" 
commands into the various scripts shown above, looking for where things 
fall apart?

Also, is the presence of my rule going to somehow prevent a USB 
harddrive partition (i.e., /dev/sda1) from getting created?

Thanks,
Christian


Kay Sievers wrote:
> On Tue, 2004-11-23 at 00:26 -0500, Christian Convey wrote:
> 
> Is this camera a generic storage device? If not, you will not get a
> device node for. Try libgphoto2:
>   http://www.gphoto.org/proj/libgphoto2/support.php
> 
> 
>>I've got a Kodak EasyShare DX6490, hooked up to my Toshiba P25-S507 
>>laptop. I'm running Debian Sarge with their 2.6.8-1 kernel and I've 
>>installed Sarge's udev package (version 046).
>>
>>I can't get my udev rules to show my camera in the /dev filesystem, and 
>>I'm concerned about the results of a test I ran. Anyone mind commenting? ...
> 
> 
>>    pascal:/sys/bus/usb/devices# udevinfo -p 
>>/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1.2/3-1.2:1.0 -a
> 
> 
> udev does not care about /sys/devices/* devices. There will never be a
> device node! The "dev" files are only for class and block devices.
> 
> Good luck,
> Kay
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2004-11-24  1:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23  5:26 Problem getting udev to see Kodak camera? Christian Convey
2004-11-23 23:45 ` Kay Sievers
2004-11-24  1:29 ` Christian Convey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41A3E3F0.5050402@cox.net \
    --to=cconvey@cox.net \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).