On Tue January 24 2006 10:30, Uwe Schindler wrote: > I have solved this type of configuration by setting the wrong modules > to the blacklist of hotplug/udev. The right module is then in /etc/modules. > If you do not put the modules into the blacklist, udev/hotplug will > load the *WRONG* module additionally (leads to crash/problems). That was definetly a problem in the earlier Debian udev package, but I believe it has been fixed in the latest (or semi-latest) release. In particulair, the following line is now in /etc/udev/hotplug.rules file, so the system should not try and load drivers for devices that are already claimed: # check if the device has already been claimed by a driver ENV{PHYSDEVDRIVER}=="?*", GOTO="hotplug_driver_loaded" If this is in there and it is still insisting on trying to load a second driver, you might need to upgrade your kernel (only the very latest 2.6 kernel versions export all the information required by the latest udev to user space). -T -- Tyson Whitehead (-twhitehe at uwo.ca -- WSC-) Computer Engineer Dept. of Applied Mathematics, Graduate Student- Applied Mathematics University of Western Ontario, GnuPG Key ID# 0xF7666BFF London, Ontario, Canada
Attachment:
pgpCAvLvKSBP5.pgp
Description: PGP signature