From: Christian Convey <cconvey@cox.net>
To: linux-hotplug@vger.kernel.org
Subject: Debugging udev problem; request ideas
Date: Sun, 28 Nov 2004 06:38:15 +0000 [thread overview]
Message-ID: <41A97257.6070708@cox.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 2914 bytes --]
Hey guys,
My saga continues trying to get my Kodak DC6490 camera to get a USB
storage device (i.e., /dev/sda1) associated with it. I'm using Debian
Sarge/2.6.9-1-smp with udev.
I'm thinking that somewhere in either hotplug or udev land, the event is
getting dropped (presumably a config problem).
I added the following lines to the top of the /sbin/hotplug script:
logger -s -t CJC::hotplug `env`
logger -s -t CJC::hotplug-cmdline "$@"
Low and behold, when I plug the camera in and hit its "sync" button, I
get these lines appearing in /var/log/syslog:
> Nov 28 01:32:26 localhost kernel: usb 2-1.2: new full speed USB device using address 13
> Nov 28 01:32:26 localhost CJC::hotplug: DEVPATH=/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.2 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTIONd PWD=/ SHLVL=1 HOME=/ SEQNUM0 _=/usr/bin/env
> Nov 28 01:32:26 localhost CJC::hotplug: DEVPATH=/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.2/2-1.2:1.0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTIONd PWD=/ SHLVL=1 HOME=/ DEVICE=/proc/bus/usb/002/013 INTERFACE=6/1/1 PRODUCT@a/575/100 TYPE=0/0/0 SEQNUM1 _=/usr/bin/env
> Nov 28 01:32:26 localhost CJC::hotplug-cmdline: usb
> Nov 28 01:32:26 localhost CJC::hotplug-cmdline: usb
> Nov 28 01:32:27 localhost usb.agent[8506]: libgphoto2: loaded successfully
So I have good reason to believe that the hotplug script catches the event.
So then I added a file named /etc/udev/rules.d/10-local.rules, with the
following content:
> KERNEL="*", PROGRAM="logger -s -t CJC::/etc/udev/rules.d/10-local.rules", NAME="foo%k"
>
> SYSFS{manufacturer}="Eastman Kodak Company", SYSFS{serial}="KCTCT42820593", NAME="%k", PROGRAM="logger -s -t CJC::/etc/udev/rules.d/\
> 10-local.rules", SYMLINK="/dev/jenns-camera"
>
The first rule was just an attempt to get udev to print SOMETHING,
ANYTHING to syslog when I hit the camera's sync button. But adding these
rules didn't cause any change in what I see from /var/log/syslog when I
sync the camera.
Does anyone have any ideas about where this process (or my
understanding) might be falling down?
Also, does anyone know why when I sync the camera, I see the addition of
TWO distinct devices?:
DEVPATH=/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.2 and
DEVPATH=/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.2/2-1.2:1.0
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-28 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 6:38 Christian Convey [this message]
2004-11-30 4:06 ` Debugging udev problem; request ideas Greg KH
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=41A97257.6070708@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.