Hello, Maybe I'm wrong but you should try to put the complete path of the module file, not simply the name.
insmod is looking, per default, in /var/lib/modules/`uname -r` If your module is in /my_modules, just use insmod /my_modules/aic79xx.o should load it properly. Ben * Gerald Justice <[EMAIL PROTECTED]> [03-06-19 16:20]: > I am still having a problem, though I feel "this close" to success. > (Picture a Kids in the Hall scene of someone remotely squeezing a head.) > > I followed the FAQ at http://www.systemimager.org/doc/html and with > some hints in response to my previous plea, I think I am "doing what I > am supposed to do" but I get the following error regarding loading > my_modules when the autoinstaller is running on the new client: > > ... > switch_root_to_tmpfs > > mount_dev_on_devfs > Started device management daemon v1.3.25 for /dev > > mount_proc > > adjust_arch > > ifconfig_loopback > > load_my_modules > insmod: /lib/modules/2.4.20-boel: No such file or directory > insmod: /lib/modules: No such file or directory > insmod: aic79xx.o: no module by that name found > > read_local_cfg > ... > > The module aic79xx.o is in the initrd_source/my_modules directory and I > can see it in the initrd_source/build_dir sub-directory. The > INSMOD_COMMANDS file also has as its last statement: > > insmod aic79xx > > But the mystery is why does the error complain about > > /lib/modules and the kernel-version sub-dir as not existing? > > Is it something I am doing wrong? > > More background: systemimager3.0.1, compile host=image server=RH8.0 > kernel 2.4.18-27.8.0. NOTE that I renamed the old driver directory > src/linux-2.4.20/drivers/scsi/aic7xxx and put the latest source for > aic7xxx (which includes support for aic79xx) into that directory. The > make binaries step did a make config which asked me a few questions > such as did I want 79xx support, I answered 'm' rather than 'N' for > that question but took defaults for everything else. It successfully > built the aic79xx.o and everything else. I did the make > install_binaries and the mkautoinstallcd with the flavor option. The > above error confirms I am getting the right autoinstall image as it > tries to load my_module. > > Thanks for any tips. > > Gerald Justice > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > Sisuite-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Benoit des Ligneris Ph. D. http://benoit.des.ligneris.net/ Centre de Calcul Scientifique http://ccs.USherbrooke.ca/ Mydynaweb Developpe(u)r http://mydynaweb.net/ OSCAR Developpe(u)r http://oscar.sourceforge.net/ �duLinux http://www.edulinux.org/ ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
