And if coldplug, which you should be using over hotplug for bootup detection, doesnt work, just add the required modules to your 2.6 module autoload file.Maarten wrote:
The most important one is: how does one make sure the /dev/ entries survive a reboot (and/or are created when the physical USB connection is made) ?
Should hot- or coldplug handle this (and if so, why doesn't it?)
Other USB inserts do get handled as anticipated; for instance inserting a USB mass storage device triggers loading of sd_mod perfectly fine...
hotplug/coldplug should take care of this. If it isn't, it means that either it isn't running correctly, or that the USB IDs for your device aren't in the database.
The other question is about that pl2303 module, how does the kernel know it is needed ?
If hotplug/coldplug are working correctly, when the device is plugged in the kernel will start the hotplug scripts and send the USB ID along. The usb.agent script will look up the ID in the database and determine what modules handle it and load the module if necessary.
You may have to add some lines to the usb.usermap file if the usb.distmap file doesn't have entries for your device.
That way, it will be detected by udev correctly and the device nodes will be created, assuming that udev has an entry to tell it about your hardware.
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.2 - Release Date: 21/01/2005
-- gentoo-user@gentoo.org mailing list
