Modules at boot
 

I was looking to add a module at boot, so that I don't have to every time by hand. Now, it seems that when I mknod, that gets saved through boots, even if the module isn't loaded. So, what I need to do is get the machine to load the module at boot, I think. Now, I found a modules.conf file that was empty. Right next to it was modules.devfs, which when I read told me that if I wanted to add to it, DO NOT MODIFY ME, but change my buddy, modules.conf. So, modules.conf is empty, but if I add insmod Intel536.o, will it be loaded at the boot? Also, where are all these modules kept usually? I'm tired of keeping my Intel driver in my home directory.

I may also need to know if root needs to own the files to use it in the way I intend? Or if there's and other things I just don't know about.

lets see -- slackware i think just put that command in
/etc/rc.d/rc.local
for it to start at boot

did you try doing 'make install' as root after you built the module and install failed
(it does that sometimes when it gets confused)

modules generally go in /lib/modules/current.running.kernel.version/kernel somewhere

since yours is working ok just stick it in somewhere and use the full path in the command

aught to work ??

but better to use 'make install' if you can there are some other files the installer puts in like
/etc/hamregistry.bin

and yes user root group root should own the module but that may not be so important cause root is using it ok as it is (root rules)
permissions should be 644 but i bet that's ok already too

"make install" doesn't work, failed a couple times. Hence my doing it the hard way.

I added "insmod <path to driver>" to rc.local...

Let's see how it goes

Hmm, it worked. Those rc.* files are some powerful stuff.