RE: issues getting I/O device to work with udev....

[Kay Sievers <kay.sievers@vrfy.org>]

On Fri, 2006-08-25 at 11:19 +0200, Jan Zwiegers wrote:
> > -----Original Message-----
> > From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> > Sent: 24 August 2006 01:10 AM
> > To: chris@seberino.org
> > Cc: md@Linux.IT; linux-hotplug-devel@lists.sourceforge.net; John Thomas;
> > jan@eagle.co.za; Ray Schumacher
> > Subject: Re: issues getting I/O device to work with udev....
> > 
> > On Wed, 2006-08-23 at 16:02 -0700, chris@seberino.org wrote:
> > > Marco
> > >
> > > Thanks.  I changed 10-edredaq.rules and z-edredaq.rules to both be
> > >
> > > SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
> > NAME="edredaq/device%m"
> > >
> > > Now 'udevtest edredaq/device0' has just this error message left:
> > 
> > Udevtest expects the sysfs devpath, not the node name. Try:
> >   udevtest /class/edredaq/device0
> [Jan Zwiegers] 
> I'm the developer at Eagle who wrote all the Linux DAQ class & device
> drivers (PCI, PC104 & USB) and also the udev rule. Out API depends on the
> fact that the device gets created under /dev/edredaq/device0-99. This rules
> worked just fine on previous systems, but suddenly it started to fail on
> newer distros. Please have a look at the following. udev seems to work fine,
> but I think the problem might be with PAM.
> 
> udevinfo -a -p /sys/class/edredaq/device0/
> 
> ...
> looking at device '/class/edredaq/device0':
>     KERNEL="device0"
>     SUBSYSTEM="edredaq"
>     SYSFS{edredaq_nodename}="device0"
>     SYSFS{dev}="253:0"
> ...
> 
> udevtest /class/edredaq/device0/
> 
> main: looking at device '/class/edredaq/device0' from subsystem 'edredaq'
> udev_rules_get_name: rule applied, 'device0' becomes 'edredaq/device0'
> create_node: creating device node '/dev/edredaq/device0', major = '253',
> minor = '0', mode = '0666', uid = '0', gid = '0'
> main: run: 'socket:/org/kernel/udev/monitor'
> main: run: '/lib/udev/udev_run_devd'
> main: run: 'socket:/org/freedesktop/hal/udev_event'
> main: run: '/sbin/pam_console_apply /dev/edredaq/device0 '
> 
> And also the updated rule z-edredaq.rules as suggested by Marco (many thanks
> Marco)
> SUBSYSTEM="edredaq", SYSFS{edredaq_nodename}="device*",
> NAME="edredaq/device%m"
> 
> Can you guys maybe point me to a solution?

Hmm, what exactly is the problem? What suddenly started to fail?

Can you paste the output of 'udevmonitor' when you load the kernel
module? Or the output when connect the USB device, if you only have it
built-in.

Kay


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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