| LinHES Forums http://forum.linhes.org/ |
|
| Installing loadable driver for SCSI host adapter...? http://forum.linhes.org/viewtopic.php?f=14&t=4790 |
Page 1 of 1 |
| Author: | Captain Dunsel [ Fri Jun 03, 2005 2:04 pm ] |
| Post subject: | Installing loadable driver for SCSI host adapter...? |
Semi-noob question: My brandy-new KnoppMyth server box is configured and working properly and is booting off a standard IDE disk. The system includes an on-mobo RAID controller based upon an ITE chipset. I have obtained the driver source from ITE and built it, and the driver loads just fine using insmod and appears to work fine. My simple question: how do I get the driver to load at boot time instead of having to manually do an insmod (or automate same by making an /etc/rc file)? It's not critical that the driver get loaded VERY early, 'cuz I don't plan to use it for my boot disk -- it's just gonna be a RAID 0 array on which my MythTV shows will be stored. I'm sure this is a simple thing to do, but I will admit that I don't know my way around Knoppix very well... ...and yes, I am running the 18.1 build of KnoppMyth, if that matters. Thanks in advance for your help! CD |
|
| Author: | Xsecrets [ Fri Jun 03, 2005 2:14 pm ] |
| Post subject: | |
put the modulename in /etc/modules that file is basically a list of modules to load at boot time |
|
| Author: | Captain Dunsel [ Fri Jun 03, 2005 2:56 pm ] |
| Post subject: | |
Thanks for the quick reply Xsecrets! I have indeed added the module name (iteraid) to /etc/modules, but it's not being loaded... The bigger question is: where does iteraid.o have to be placed in order for this to work? Also, if I simply copy the .o file into some particular location, do I have to "tell" the system using command(s) that a new driver has been added (beyond adding the entry to /etc/modules)? Thanks again, CD |
|
| Author: | brendan [ Fri Jun 03, 2005 3:09 pm ] |
| Post subject: | |
There is no 18.1 build of KnoppMyth. Also, my understanding is that kernel modules under KnoppMyth end in the .ko extension. Why does yours end in .o? -brendan |
|
| Author: | Xsecrets [ Fri Jun 03, 2005 4:35 pm ] |
| Post subject: | |
the .o extention is indeed interesting, as 2.4 and older kernels used .o 2.6 which knoppmyth uses is .ko any source module should have a make install to put it where it's supposed to go. and if modprobe modulename works then putting it in /etc/modules should work. if however modprobe does not work you need to find out why and fix that. I know of no other way to load a module that fails with modprobe other than to creat a script and loat it with insmod, but I would suggest fixing the problem instead of going that route. |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|