Felipe wrote: > If the USB driver in the kernel is having problems with the device, it > can't identify the device and create a node for it. I doubt that the > situation would be any better with a static /dev entry for it either. Yeah! With a static /dev tree, the device node would be there sitting useless, idle, waiting for the USB driver to stop timing out. It seems the root of that problem is not udev itself, but a bug in the USB kernel core. This seems to be the problem I am having also. I have a USB cd recorder that will not work (yet) with FC3 and worked great with RH 9. I tried to trace problems through udev and did not find anything. Udev is recognizing the device correctly. It just seems the kernel is having problems with mounting the device. Someone mentioned the difference between KDE and Gnome but I don't think that has anything to do with it. I have both on my system and, actually, KDE handled the problems with this device better than Gnome. KDE will load correctly, mostly ignoring the whirring CD and automatically opening the device manager box. Gnome will not load the splash screen for a couple of minutes until the whole CD mishmash times out, leaving no icons on the desktop. Either way, the device is recognized correctly. It is just unmountable. Occasionally it will even mount correctly if there is a disk in it! But when that disk is ejected it will not mount another one. Udev seems to be working with the USB system correctly because it has never failed to mount, read or write to a USB memory stick.
