Kernel Modules

[Sanjay Yugal Kishore Ha]

Hi,

I have a set of kernel modules that are statically linked to the kernel. The kmsystem -q displays the Loadable field of these modules as N.
Even the $LOADABLE value of these modules' system file in /stand/system.d/ have the value N.

However, when I use SAM to add these modules to the kernel, I get a new window asking me whether I would like to make these modules as loadable at boot time. This means that SAM would first link these modules statically to kernel by executing - 'kmsystem -l N module_name' and then adding these modules into /etc/loadmods. Next result is obvious - When the system comes after a reboot, it would start cribbing that I'm trying to add a module that's already there.

Now the questions-
1. If a module's /stand/system.d/ says $LOADABLE N, then does it mean it has to stay that way throughout, even when adding it to the kernel. Or in other words I cannot/shouldnot change the $LOADABLE flag to Y, either from the command line (with 'kmsystem -l Y') or from SAM?
2. Is there any other way to determine if a module is static apart from the kmsystem -q or the kmadmin commands?
3. Where can I find some documentation on the kernel modules? I've been through the kmadmin and kmsystem commands.

I could sure use some help here.

Regards,
Sanjay

[James Murtagh]

Hi Sanjay,

As no-one has answered...

1) You can't actually change the loadable flag yourself. This field indicates "is this module loadable?". For instance, hpux 11i has some loadable drivers and tunables, for instance maxuprc. The /etc/loadmods file is for modules that you have loaded dynamically, but would like them to remain at that value/configuration after a reboot. In time, you will see more loadable modules. Using the command you specified would have no effect on non-loadable modules.

2) Well, these are the tools specifically written for the new interface, so no, not by user-commands. Why would you want two ways to find out the same information? Also look at kmtune for the kernel tunables.

3) Look in www.docs.hp.com for more information. The links at the bottom of the index page, "all information for the .... release of hpux".

If you are concerned about the way SAM displays this information, use the command line options. The SAM team work with a lot of different teams within HP so the interface may not be exactly as you expect.

Hope this helps,

James.