From: Christian Convey <cconvey@cox.net>
To: linux-hotplug@vger.kernel.org
Subject: Problem getting udev to see Kodak camera?
Date: Tue, 23 Nov 2004 05:26:02 +0000 [thread overview]
Message-ID: <41A2C9EA.6040906@cox.net> (raw)
Hey guys,
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? ...
After hitting the camera's base-station's "sync" button, I ran 'dmesg'
and got this output:
usb 3-1.2: new full speed USB device using address 5
usb 3-1.2: USB disconnect, address 5
So then I ran this command with the following results:
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
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful
attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at class device
'/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1.2/3-1.2:1.0':
SYSFS{bAlternateSetting}=" 0"
SYSFS{bInterfaceClass}="06"
SYSFS{bInterfaceNumber}="00"
SYSFS{bInterfaceProtocol}="01"
SYSFS{bInterfaceSubClass}="01"
SYSFS{bNumEndpoints}="03"
SYSFS{detach_state}="0"
SYSFS{iInterface}="00"
What concerns me is that I don't see any "BUS" or "ID" line, like I see
in various examples such as shown here:
http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimerMisc.html
Could the omission of those two lines from 'udevinfo's output indicate a
problem?
Also, is there some good way I can trace through what udev does when I
hit the camera's sync button? It's apparent that my rule isn't getting
triggered:
SYSFS{manufacturer}="Eastman Kodak Company",\
SYSFS{serial}="KCTCT42820593", NAME="%k", SYMLINK="/dev/my-camera"
and I'd like to figure out where the process is falling down.
Thanks,
Christian
-------------------------------------------------------
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
next reply other threads:[~2004-11-23 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 5:26 Christian Convey [this message]
2004-11-23 23:45 ` Problem getting udev to see Kodak camera? Kay Sievers
2004-11-24 1:29 ` Christian Convey
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=41A2C9EA.6040906@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).