From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Tue, 07 Mar 2006 23:07:48 +0000 Subject: Re: udev does not create ttyUSB devices for Visor Message-Id: <20060307230748.GA9877@vrfy.org> List-Id: References: <1469.1141769620@www024.gmx.net> In-Reply-To: <1469.1141769620@www024.gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, Mar 07, 2006 at 11:13:40PM +0100, Grischa Stegemann wrote: > I have a Handspring Visor device which is supposed to communicate with my > computer using the usb-serial driver. > > My udev version is 056 (Debian stable, Kernel 2.6.15.1) and it fails to > create the appropriate device nodes ttyUSB0 and ttyUSB1. When I hit the > hotsync-button on the cradle the kernel recognizes the device correctly: You may need a newer udev version for a recent kernel, don't know if that udev release still works correctly. > localhost kernel: usb 1-2: Handspring Visor now attached to ttyUSB0 > localhost kernel: usb 1-2: Handspring Visor now attached to ttyUSB1 > > The simple udev-rule > KERNEL="ttyUSB[0-9]*", NAME="%k" > should now yield the corresponding devices, but it does not. It is > perfectly ignored by udev and I cannot figure out why. There's no problem > with any other device. It may be that some other rules catch away the event? > It becomes even weirder (for me) if I create the device-nodes by hand: > mknod /dev/ttyUSB0 c 188 0; mknod /dev/ttyUSB1 c 188 1 > > Now I can communicate with my Visor. BUT once the hotsync-procedure is > finished, the visor disconnects completely from the computer, the > usb-driver deregisters the device and -guess what!- NOW udev removes the > corresponding ttyUSB-nodes.:( If the device node matches the kernel device that goes away, udev removes the device node. That's the correct behavior. > How comes udev is ignoring the device during registering but removes the > device nodes during deregistering the device? > It also removes them if I have absolutely no rule concerning ttyUSB > at all. There is no need to provide any rule if you only want a default device node, udev will do that anyway. Kay ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ 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