Nick Rout wrote:

>On Tuesday 06 February 2007 22:45, Nick Rout wrote:
>  
>
>>http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/sles9/adminguide-sles9/ch14.htm
>>l
>>
>>The above may be helpful, given that it is for suse. OTOH it is for an
>>older version and the kernel has made significant progress over the
>>relevant period.
>>    
>>
>
>Must.....stop.....replying.....to.................myself.
>
>http://www.novell.com/documentation/opensuse102/index.html?page=/documentation/opensuse102/opensuse102_reference/data/sec_udev_hplug.html
>
>seems more up to date and says:
>
>"The formerly used hotplug package is entirely replaced by udev and the 
>udev-related kernel infrastructure. The following parts of the former hotplug 
>infrastructure have been made obsolete or had their functionality taken over 
>by udev:"
>
>"16.9 For More Information
>
>For more information about the udev infrastructure, refer to the following man 
>pages:
>
>udev
>
>    General information about udev, keys, rules, and other important 
>configuration issues.
>udevinfo
>
>    udevinfo can be used to query device information from the udev database.
>udevd
>
>    Information about the udev event managing daemon.
>udevmonitor
>
>    udevmonitor prints the kernel and udev event sequence to the console. This 
>tool is mainly used for debugging purposes."
>
>In other words RTFM LOL...
>  
>
Yup that's the one I have been reading and leads me to the salient
points below:

   1. It seems that for each device the kernel generates a MODALAIS and
      passes that via UEVENT to UDEV.
   2. The MODALIAS of the device which driver can handle is stored in
      the kernel module itself.
   3. depmod scans all the available kernel modules working out
      dependencies and builds a databases of available handlers for the
      various MODALIAS.
   4. modprobe -c will list the content of said database.
   5. this database is stored in files modules.alias and similar.
   6. the module I want loaded upon insertion of my multiport serial
      card doesn't contain the MODALIAS string from [2]
   7. the module I want loaded is therefore not contained in the
      database and not loaded upon insertion.
   8. the kernel included module does load in it's place but is not
      fully functional.

hmmm...

Chris

Reply via email to