Guys, I'd like to include a tiny script (attached) into boel_binaries which can solve one of our longest lasting problems: the inability to deal with unkown hardware. Of course, we have UYOK, but that sometimes fails and is somewhat unconfortable to use. No, I don't want to replace UYOK. I just believe that the current detection framework can get some help.
pci-automod (the script in the attachment) detects the PCI hardware in your
machine and checks which module has support for this hardware. It deals with
three classes of hardware right now: storage, network and serial. It does not
require any pci.lst list, it only uses information available in the modules,
respectively the modules.pcilst file. I.e. if it finds a module which supports
your hardware, it will tell you or load it. The script is simple and runs fine
under the busybox "ash".
Usage:
pci-automod --class storage|net|serial --list|--load|--hwlist
Detect modules which need to be loaded in order to get the
storage or ethernet drivers activated. This uses information
in the modules and from the PCI bus. When multiple modules are
available for one device, all of them will be loaded!!!
Options:
--class storage|net|serial : device class filter
--list : list modules to load
--hwlist : produce hardware.lst compatible lines
for systemconfigurator
--load : try to modprobe the modules
Usage examples for systemimager:
pci-automod --load --class storage
will load the storage related drivers which the current detection framework
wasn't able to detect.
pci-automod --hwlist --class storage --class net >>
/a/etc/systemconfig/hardware.lst
will add the detected storage and network related modules to the hardware.lst
file in the freshly deployed node such that systemconfigurator has an easy job
to configure modprobe.conf and the initrd.
There is a small drawback: if there is more than one driver available for
supporting particular hardware, this script will list and try to load all
these modules. How should we deal with this situation? Should we select only
the first available module? Or add some detection for stuff that already has a
driver in kernel (or module) and just skip that load? This would lead to only
the first driver being loaded.
The inclusion of this thing is straight forward and requires additional lines
in the systemimager trunk. Should I include it? Any comments or ideas?
Thanks,
best regards,
Erich
pci-automod
Description: application/shellscript
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
