udev and irda-usb trouble

udev and irda-usb trouble

[Chris Horn]

Generally I am quite happy with udev and USB in Linux.  One thing, 
though,
really bothers me.  I haven't been able to write a udev rule to pick up 
my
irda-usb based IrDA dongle.

I can talk to it just fine if I manually create an irda0 node in /dev 
with
mknod, but I don't want to keep doing that (udev keeps deleting my 
node).
Irattach connects just fine with 'irattach irda0 none -s'** without
the /dev/irda0 node, but my application (jpilot) obviously needs a file 
to
talk through.

Problems:
1. I can't seem to get any info with udevinfo on any irda or ircomm 
node.
2. Even if I create a /dev/irda0 node, unload all the modules and then 
have
usb.agent detect the device plugin event and start up all the modules, 
udev
will not make any nodes for me.  I even tried rebooting, even though I 
know
that shouldn't be necessary.
3. udev works fine for my other devices.

The latest rule I've been trying is:
BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="%k"

Not that it really matters, but I'm working with an Extended Systems, 
Inc.
XTNDAccess IrDA Dongle.  lsusb and usbview tell me lots about the 
device, but
nothing particularly useful.

# l /sys/bus/usb/drivers/irda-usb/
total 0
lrwxrwxrwx  1 root root 0 Dec 21 02:34 2-2.6:1.0
-> ../../../../devices/pci0000:00/0000:00:10.0/usb2/2-2/2-2.6/2-2.6:1.0

Why won't udev make my irda-usb device a node?  It does for everything 
else
I've asked it to - namely 'sd[a-z][0-9]' type devices.

Some relevant /var/log/messages output:
Dec 21 02:34:30 snozberry kernel: usb 2-2.6: new full speed USB device 
using address 10
Dec 21 02:34:30 snozberry kernel: NET: Registered protocol family 23
Dec 21 02:34:30 snozberry kernel: IRDA-USB found at address 10, Vendor: 
8e9, Product: 100
Dec 21 02:34:30 snozberry usb.agent[4317]:      irda-usb: loaded 
successfully
Dec 21 02:34:30 snozberry usb.agent[4317]:      ir-usb: blacklisted
Dec 21 02:34:30 snozberry kernel: IrDA: Registered device irda0
Dec 21 02:34:30 snozberry kernel: usbcore: registered new driver 
irda-usb
Dec 21 02:34:30 snozberry kernel: USB IrDA support registered
Dec 21 02:45:45 snozberry irattach: executing: '/sbin/modprobe irda0'
Dec 21 02:45:45 snozberry irattach: executing: 'echo snozberry > 
/proc/sys/net/irda/devname'
Dec 21 02:45:45 snozberry irattach: executing: 'echo 1 > 
/proc/sys/net/irda/discovery'
Dec 21 02:45:45 snozberry irattach: Starting device irda0
Dec 21 03:03:16 snozberry kernel: usb 2-2.7: control timeout on ep0in

I always get a lot of those ep0in timeout messages; I'm pretty sure 
they're harmless.


Please cc: me, as I'm not a list member.  Many thanks in advance.
Chris Horn.

** I'm using Debian's latest testing version of irda-utils.



-------------------------------------------------------
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

Re: udev and irda-usb trouble

[Kay Sievers]

On Tue, 2004-12-21 at 16:17 -0500, Chris Horn wrote:
> Generally I am quite happy with udev and USB in Linux.  One thing, 
> though,
> really bothers me.  I haven't been able to write a udev rule to pick up 
> my
> irda-usb based IrDA dongle.
> 
> I can talk to it just fine if I manually create an irda0 node in /dev 
> with
> mknod, but I don't want to keep doing that (udev keeps deleting my 
> node).
> Irattach connects just fine with 'irattach irda0 none -s'** without
> the /dev/irda0 node, but my application (jpilot) obviously needs a file 
> to
> talk through.
> 
> Problems:
> 1. I can't seem to get any info with udevinfo on any irda or ircomm 
> node.
> 2. Even if I create a /dev/irda0 node, unload all the modules and then 
> have
> usb.agent detect the device plugin event and start up all the modules, 
> udev
> will not make any nodes for me.  I even tried rebooting, even though I 
> know
> that shouldn't be necessary.
> 3. udev works fine for my other devices.
> 
> The latest rule I've been trying is:
> BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="%k"

Hey, don't use the same value for NAME _and_ SYMLINK. :)

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

Re: udev and irda-usb trouble

[Chris Horn]

On Tuesday 21 December 2004 18:50, Kay Sievers wrote:
> On Tue, 2004-12-21 at 16:17 -0500, Chris Horn wrote:
> > Generally I am quite happy with udev and USB in Linux.  One thing, 
> > though,
> > really bothers me.  I haven't been able to write a udev rule to pick up 
> > my
> > irda-usb based IrDA dongle.
> > 
> > I can talk to it just fine if I manually create an irda0 node in /dev 
> > with
> > mknod, but I don't want to keep doing that (udev keeps deleting my 
> > node).
> > Irattach connects just fine with 'irattach irda0 none -s'** without
> > the /dev/irda0 node, but my application (jpilot) obviously needs a file 
> > to
> > talk through.
> > 
> > Problems:
> > 1. I can't seem to get any info with udevinfo on any irda or ircomm 
> > node.
> > 2. Even if I create a /dev/irda0 node, unload all the modules and then 
> > have
> > usb.agent detect the device plugin event and start up all the modules, 
> > udev
> > will not make any nodes for me.  I even tried rebooting, even though I 
> > know
> > that shouldn't be necessary.
> > 3. udev works fine for my other devices.
> > 
> > The latest rule I've been trying is:
> > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="%k"
> 
> Hey, don't use the same value for NAME _and_ SYMLINK. :)
> 
> Kay

Thanks for the tip - I should've realized that was silly.  I've tried it with 
other text there (and just re-tried it), though, and it still doesn't work.

I just tried this:
BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="IRdongle"


Chris.


-------------------------------------------------------
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

Re: udev and irda-usb trouble

[Greg KH]

On Tue, Dec 21, 2004 at 07:05:47PM -0500, Chris Horn wrote:
> On Tuesday 21 December 2004 18:50, Kay Sievers wrote:
> > On Tue, 2004-12-21 at 16:17 -0500, Chris Horn wrote:
> > > Generally I am quite happy with udev and USB in Linux.  One thing, 
> > > though,
> > > really bothers me.  I haven't been able to write a udev rule to pick up 
> > > my
> > > irda-usb based IrDA dongle.
> > > 
> > > I can talk to it just fine if I manually create an irda0 node in /dev 
> > > with
> > > mknod, but I don't want to keep doing that (udev keeps deleting my 
> > > node).
> > > Irattach connects just fine with 'irattach irda0 none -s'** without
> > > the /dev/irda0 node, but my application (jpilot) obviously needs a file 
> > > to
> > > talk through.
> > > 
> > > Problems:
> > > 1. I can't seem to get any info with udevinfo on any irda or ircomm 
> > > node.
> > > 2. Even if I create a /dev/irda0 node, unload all the modules and then 
> > > have
> > > usb.agent detect the device plugin event and start up all the modules, 
> > > udev
> > > will not make any nodes for me.  I even tried rebooting, even though I 
> > > know
> > > that shouldn't be necessary.
> > > 3. udev works fine for my other devices.
> > > 
> > > The latest rule I've been trying is:
> > > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="%k"
> > 
> > Hey, don't use the same value for NAME _and_ SYMLINK. :)
> > 
> > Kay
> 
> Thanks for the tip - I should've realized that was silly.  I've tried it with 
> other text there (and just re-tried it), though, and it still doesn't work.
> 
> I just tried this:
> BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="IRdongle"

Is there really a /sys/class/usb/irda* device in sysfs for your device?
I didn't think the irda driver used the usb major number.  Where in
sysfs does the "dev" file for this device show up (it should be
somewhere in /sys/class/.  If not there, that's why this isn't working.

thanks,

greg k-h


-------------------------------------------------------
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

Re: udev and irda-usb trouble

[Chris Horn]

On Tuesday 21 December 2004 19:26, Greg KH wrote:
> On Tue, Dec 21, 2004 at 07:05:47PM -0500, Chris Horn wrote:
> > On Tuesday 21 December 2004 18:50, Kay Sievers wrote:
> > > On Tue, 2004-12-21 at 16:17 -0500, Chris Horn wrote:
> > > > Generally I am quite happy with udev and USB in Linux.  One thing, 
> > > > though,
> > > > really bothers me.  I haven't been able to write a udev rule to pick up 
> > > > my
> > > > irda-usb based IrDA dongle.
> > > > 
> > > > I can talk to it just fine if I manually create an irda0 node in /dev 
> > > > with
> > > > mknod, but I don't want to keep doing that (udev keeps deleting my 
> > > > node).
> > > > Irattach connects just fine with 'irattach irda0 none -s'** without
> > > > the /dev/irda0 node, but my application (jpilot) obviously needs a file 
> > > > to
> > > > talk through.
> > > > 
> > > > Problems:
> > > > 1. I can't seem to get any info with udevinfo on any irda or ircomm 
> > > > node.
> > > > 2. Even if I create a /dev/irda0 node, unload all the modules and then 
> > > > have
> > > > usb.agent detect the device plugin event and start up all the modules, 
> > > > udev
> > > > will not make any nodes for me.  I even tried rebooting, even though I 
> > > > know
> > > > that shouldn't be necessary.
> > > > 3. udev works fine for my other devices.
> > > > 
> > > > The latest rule I've been trying is:
> > > > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="%k"
> > > 
> > > Hey, don't use the same value for NAME _and_ SYMLINK. :)
> > > 
> > > Kay
> > 
> > Thanks for the tip - I should've realized that was silly.  I've tried it with 
> > other text there (and just re-tried it), though, and it still doesn't work.
> > 
> > I just tried this:
> > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="IRdongle"
> 
> Is there really a /sys/class/usb/irda* device in sysfs for your device?
> I didn't think the irda driver used the usb major number.  Where in
> sysfs does the "dev" file for this device show up (it should be
> somewhere in /sys/class/.  If not there, that's why this isn't working.
> 
> thanks,
> 
> greg k-h

It's got information under /sys/class: 
 
# l /sys/class/net/irda0/
total 0
-r--r--r--  1 root root 4096 Dec 21 19:01 addr_len
-r--r--r--  1 root root 4096 Dec 21 19:01 address
-r--r--r--  1 root root 4096 Dec 21 19:01 broadcast
-r--r--r--  1 root root 4096 Dec 21 19:01 features
-rw-r--r--  1 root root 4096 Dec 21 19:01 flags
-r--r--r--  1 root root 4096 Dec 21 19:01 ifindex
-r--r--r--  1 root root 4096 Dec 21 19:01 iflink
-rw-r--r--  1 root root 4096 Dec 21 19:01 mtu
drwxr-xr-x  2 root root    0 Dec 21 19:01 statistics
-rw-r--r--  1 root root 4096 Dec 21 19:01 tx_queue_len
-r--r--r--  1 root root 4096 Dec 21 19:01 type

Realizing I may be an idiot, I just tried:
BUS="net", KERNEL="irda[0-9]", NAME="%k", SYMLINK="irdongle"
but that didn't work, either.

Thanks for the help so far!
Chris.


-------------------------------------------------------
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

Re: udev and irda-usb trouble

[Greg KH]

On Tue, Dec 21, 2004 at 07:43:47PM -0500, Chris Horn wrote:
> On Tuesday 21 December 2004 19:26, Greg KH wrote:
> > On Tue, Dec 21, 2004 at 07:05:47PM -0500, Chris Horn wrote:
> > > On Tuesday 21 December 2004 18:50, Kay Sievers wrote:
> > > > On Tue, 2004-12-21 at 16:17 -0500, Chris Horn wrote:
> > > > > Generally I am quite happy with udev and USB in Linux.  One thing, 
> > > > > though,
> > > > > really bothers me.  I haven't been able to write a udev rule to pick up 
> > > > > my
> > > > > irda-usb based IrDA dongle.
> > > > > 
> > > > > I can talk to it just fine if I manually create an irda0 node in /dev 
> > > > > with
> > > > > mknod, but I don't want to keep doing that (udev keeps deleting my 
> > > > > node).
> > > > > Irattach connects just fine with 'irattach irda0 none -s'** without
> > > > > the /dev/irda0 node, but my application (jpilot) obviously needs a file 
> > > > > to
> > > > > talk through.
> > > > > 
> > > > > Problems:
> > > > > 1. I can't seem to get any info with udevinfo on any irda or ircomm 
> > > > > node.
> > > > > 2. Even if I create a /dev/irda0 node, unload all the modules and then 
> > > > > have
> > > > > usb.agent detect the device plugin event and start up all the modules, 
> > > > > udev
> > > > > will not make any nodes for me.  I even tried rebooting, even though I 
> > > > > know
> > > > > that shouldn't be necessary.
> > > > > 3. udev works fine for my other devices.
> > > > > 
> > > > > The latest rule I've been trying is:
> > > > > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="%k"
> > > > 
> > > > Hey, don't use the same value for NAME _and_ SYMLINK. :)
> > > > 
> > > > Kay
> > > 
> > > Thanks for the tip - I should've realized that was silly.  I've tried it with 
> > > other text there (and just re-tried it), though, and it still doesn't work.
> > > 
> > > I just tried this:
> > > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="IRdongle"
> > 
> > Is there really a /sys/class/usb/irda* device in sysfs for your device?
> > I didn't think the irda driver used the usb major number.  Where in
> > sysfs does the "dev" file for this device show up (it should be
> > somewhere in /sys/class/.  If not there, that's why this isn't working.
> > 
> > thanks,
> > 
> > greg k-h
> 
> It's got information under /sys/class: 
>  
> # l /sys/class/net/irda0/
> total 0
> -r--r--r--  1 root root 4096 Dec 21 19:01 addr_len
> -r--r--r--  1 root root 4096 Dec 21 19:01 address
> -r--r--r--  1 root root 4096 Dec 21 19:01 broadcast
> -r--r--r--  1 root root 4096 Dec 21 19:01 features
> -rw-r--r--  1 root root 4096 Dec 21 19:01 flags
> -r--r--r--  1 root root 4096 Dec 21 19:01 ifindex
> -r--r--r--  1 root root 4096 Dec 21 19:01 iflink
> -rw-r--r--  1 root root 4096 Dec 21 19:01 mtu
> drwxr-xr-x  2 root root    0 Dec 21 19:01 statistics
> -rw-r--r--  1 root root 4096 Dec 21 19:01 tx_queue_len
> -r--r--r--  1 root root 4096 Dec 21 19:01 type

net devices do not have a /dev node :)

thanks,

greg k-h


-------------------------------------------------------
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

Re: udev and irda-usb trouble

[Chris Horn]

On Tuesday 21 December 2004 19:52, Greg KH wrote:
> On Tue, Dec 21, 2004 at 07:43:47PM -0500, Chris Horn wrote:
> > On Tuesday 21 December 2004 19:26, Greg KH wrote:
> > > On Tue, Dec 21, 2004 at 07:05:47PM -0500, Chris Horn wrote:
> > > > On Tuesday 21 December 2004 18:50, Kay Sievers wrote:
> > > > > On Tue, 2004-12-21 at 16:17 -0500, Chris Horn wrote:
> > > > > > Generally I am quite happy with udev and USB in Linux.  One thing, 
> > > > > > though,
> > > > > > really bothers me.  I haven't been able to write a udev rule to 
pick up 
> > > > > > my
> > > > > > irda-usb based IrDA dongle.
> > > > > > 
> > > > > > I can talk to it just fine if I manually create an irda0 node 
in /dev 
> > > > > > with
> > > > > > mknod, but I don't want to keep doing that (udev keeps deleting my 
> > > > > > node).
> > > > > > Irattach connects just fine with 'irattach irda0 none -s'** 
without
> > > > > > the /dev/irda0 node, but my application (jpilot) obviously needs a 
file 
> > > > > > to
> > > > > > talk through.
> > > > > > 
> > > > > > Problems:
> > > > > > 1. I can't seem to get any info with udevinfo on any irda or 
ircomm 
> > > > > > node.
> > > > > > 2. Even if I create a /dev/irda0 node, unload all the modules and 
then 
> > > > > > have
> > > > > > usb.agent detect the device plugin event and start up all the 
modules, 
> > > > > > udev
> > > > > > will not make any nodes for me.  I even tried rebooting, even 
though I 
> > > > > > know
> > > > > > that shouldn't be necessary.
> > > > > > 3. udev works fine for my other devices.
> > > > > > 
> > > > > > The latest rule I've been trying is:
> > > > > > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="%k"
> > > > > 
> > > > > Hey, don't use the same value for NAME _and_ SYMLINK. :)
> > > > > 
> > > > > Kay
> > > > 
> > > > Thanks for the tip - I should've realized that was silly.  I've tried 
it with 
> > > > other text there (and just re-tried it), though, and it still doesn't 
work.
> > > > 
> > > > I just tried this:
> > > > BUS="usb", KERNEL="irda[0-9]", NAME="%k", SYMLINK="IRdongle"
> > > 
> > > Is there really a /sys/class/usb/irda* device in sysfs for your device?
> > > I didn't think the irda driver used the usb major number.  Where in
> > > sysfs does the "dev" file for this device show up (it should be
> > > somewhere in /sys/class/.  If not there, that's why this isn't working.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > It's got information under /sys/class: 
> >  
> > # l /sys/class/net/irda0/
> > total 0
> > -r--r--r--  1 root root 4096 Dec 21 19:01 addr_len
> > -r--r--r--  1 root root 4096 Dec 21 19:01 address
> > -r--r--r--  1 root root 4096 Dec 21 19:01 broadcast
> > -r--r--r--  1 root root 4096 Dec 21 19:01 features
> > -rw-r--r--  1 root root 4096 Dec 21 19:01 flags
> > -r--r--r--  1 root root 4096 Dec 21 19:01 ifindex
> > -r--r--r--  1 root root 4096 Dec 21 19:01 iflink
> > -rw-r--r--  1 root root 4096 Dec 21 19:01 mtu
> > drwxr-xr-x  2 root root    0 Dec 21 19:01 statistics
> > -rw-r--r--  1 root root 4096 Dec 21 19:01 tx_queue_len
> > -r--r--r--  1 root root 4096 Dec 21 19:01 type
> 
> net devices do not have a /dev node :)
> 

Okay, thanks - I didn't know that.

Is there anything I can do to get udev (or whatever is responsible) from 
deleting the nodes I put in by hand?  Is there a "don't delete list 
somewhere?"

Thanks.
Chris.


-------------------------------------------------------
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

Re: udev and irda-usb trouble

[Greg KH]

On Tue, Dec 21, 2004 at 07:54:35PM -0500, Chris Horn wrote:
> 
> Is there anything I can do to get udev (or whatever is responsible) from 
> deleting the nodes I put in by hand?  Is there a "don't delete list 
> somewhere?"

I don't understand, why do you want to keep device nodes that are never
used?

Anyway, that's a distro specific issue, I suggest asking the proper
distro mailing list for how to do that.

Hope this helps,

greg k-h


-------------------------------------------------------
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

Re: udev and irda-usb trouble

[Chris Horn]

On Tuesday 21 December 2004 20:01, Greg KH wrote:
> On Tue, Dec 21, 2004 at 07:54:35PM -0500, Chris Horn wrote:
> > 
> > Is there anything I can do to get udev (or whatever is responsible) from 
> > deleting the nodes I put in by hand?  Is there a "don't delete list 
> > somewhere?"
> 
> I don't understand, why do you want to keep device nodes that are never
> used?
> 
> Anyway, that's a distro specific issue, I suggest asking the proper
> distro mailing list for how to do that.
> 
> Hope this helps,
> 
> greg k-h

I'm sorry: one more message.  I mis-typed what I want - and I see from your 
message that I need to clarify my problem.  I meant:

"Is there anything I can do to get udev (or whatever is responsible) to NOT 
delete nodes I've added by hand?"

The problem is that when I go to sync my Palm Pilot with jpilot, udev (or some 
other software) has often deleted the /dev/irda0 node I created for jpilot to 
talk through.  This means that almost every time I want to sync my Palm I 
have to create /dev/irda0 by hand because something has deleted it.  I want 
to stop whatever is automatically deleting the nodes I've added by hand (in 
this case /dev/irda0).  It's really annoying!

Thanks.
Chris.


-------------------------------------------------------
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

Re: udev and irda-usb trouble

[Greg KH]

On Tue, Dec 21, 2004 at 08:12:43PM -0500, Chris Horn wrote:
> 
> I'm sorry: one more message.  I mis-typed what I want - and I see from your 
> message that I need to clarify my problem.  I meant:
> 
> "Is there anything I can do to get udev (or whatever is responsible) to NOT 
> delete nodes I've added by hand?"

Well, the kernel device that caused that device to be created was
removed from the system (that's what happens with palm devices.)  So
udev _has_ to delete the device node as if it didn't, it would be a
security problem.

Just have udev create the node you want for your pilot, and then you
don't have to do anything by hand :)

thanks,

greg k-h


-------------------------------------------------------
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

Re: udev and irda-usb trouble

[Kay Sievers]

On Tue, 2004-12-21 at 20:12 -0500, Chris Horn wrote:
> On Tuesday 21 December 2004 20:01, Greg KH wrote:
> > On Tue, Dec 21, 2004 at 07:54:35PM -0500, Chris Horn wrote:
> > > 
> > > Is there anything I can do to get udev (or whatever is responsible) from 
> > > deleting the nodes I put in by hand?  Is there a "don't delete list 
> > > somewhere?"
> > 
> > I don't understand, why do you want to keep device nodes that are never
> > used?
> > 
> > Anyway, that's a distro specific issue, I suggest asking the proper
> > distro mailing list for how to do that.
> > 
> > Hope this helps,
> > 
> > greg k-h
> 
> I'm sorry: one more message.  I mis-typed what I want - and I see from your 
> message that I need to clarify my problem.  I meant:
> 
> "Is there anything I can do to get udev (or whatever is responsible) to NOT 
> delete nodes I've added by hand?"
> 
> The problem is that when I go to sync my Palm Pilot with jpilot, udev (or some 
> other software) has often deleted the /dev/irda0 node I created for jpilot to 
> talk through.  This means that almost every time I want to sync my Palm I 
> have to create /dev/irda0 by hand because something has deleted it.  I want 
> to stop whatever is automatically deleting the nodes I've added by hand (in 
> this case /dev/irda0).  It's really annoying!

Does it really get deleted without a reboot? If your system use udev,
than there is a high chance that the /dev directory is on tmpfs which
will not survive a reboot.

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

Re: udev and irda-usb trouble

[Chris Horn]

On Dec 21, 2004, at 20:23, Greg KH wrote:

> On Tue, Dec 21, 2004 at 08:12:43PM -0500, Chris Horn wrote:
>>
>> I'm sorry: one more message.  I mis-typed what I want - and I see 
>> from your
>> message that I need to clarify my problem.  I meant:
>>
>> "Is there anything I can do to get udev (or whatever is responsible) 
>> to NOT
>> delete nodes I've added by hand?"
>
> Well, the kernel device that caused that device to be created was
> removed from the system (that's what happens with palm devices.)  So
> udev _has_ to delete the device node as if it didn't, it would be a
> security problem.
>
> Just have udev create the node you want for your pilot, and then you
> don't have to do anything by hand :)


I see what you're saying, but I sync my Palm via infrared!  The device 
that's irda0 is the USB dongle that gives my PC the ability to talk to 
the Palm via IR.  It's ALWAYS plugged in!

I think Kay Sievers may have pinned it down with my /dev system being 
on a tmpfs which doesn't survive reboots.  It looks like the deleting 
of /dev/irda0 is because of this (I don't sync very often).  Now it 
looks like I will have to investigate what builds the /dev system upon 
boot - so I can modify it to add my irda0 node.  What a pain.

Thanks.
Chris.

P.S. - mount tells me:
none on /dev type tmpfs (rw,size=5M,mode\a55)



-------------------------------------------------------
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