Couple questions about modules...
 

Hi folks,

I am currently using Suse 8.2 Pro, but I compiled 2.6.4 kernel on it.I' ve upgraded module-init-tools
to 0.9.14.Still, when I boot this kernel I see in /var/log/messages this line:

No module symbols loaded - kernel modules not enabled.

-----------------------------------------

I made initrd image in /boot directory as I should, and correct me if I am wrong, I have a problem
with mkinitrd (or mk_initrd), old version ,to be correct (or not ????).Anyway, I've downloaded mkinitrd-1.0-80.src.rpm and when I tried to install
it ( rebuild first !) I got output that it conflicts with aaa_base scripts, currently I got
aaa_base-2003.3.18-0.So what should I do?Remove old aaa_base and install new one (which version for 2.6.4. kernel?),
and then install appropriate mkinitrd, or just new aaa_base, or just new mkinitrd (again, which version for 2.6.x kernel?).

And another thing concerns me.When I try to load module in command line, it fails with insmod and works with modprobe.
What is wrong?


I made a lot of assumptions in this topic, please tell me what I am doing wrong.
Really don't know what do.If anybody has some older version of (older than 9.0)
Suse with successfully compiled 2.6.x kernel, please write what you upgraded to get your Suse working fine with new kernel.
Thanks in advance!

Re: Couple questions about modules...
 

Did you build that kernel yourself ? Than you need to switch on module support. SuSE standard-kernels should have that allways.

Quote:

I made initrd image in /boot directory as I should, and correct me if I am wrong, I have a problem with mkinitrd (or mk_initrd), old version ,to be correct (or not ????).Anyway, I've downloaded mkinitrd-1.0-80.src.rpm and when I tried to install it ( rebuild first !) I got output that it conflicts with aaa_base scripts, currently I got aaa_base-2003.3.18-0.So what should I do?Remove old aaa_base and install new one (which version for 2.6.4. kernel?),

I think there is no new aaa_base for every new kernel. Because aaa_base contains a whole bunch of basic tools like "ln" "ls" and bashes and all that.
That conflict is (i think, but i am not a master of rpm databases) not really a problem. I would just force mkinitrd. But you might want to make sure its really working. Because to undo that step might be ugly.

Quote:

And another thing concerns me.When I try to load module in command line, it fails with insmod and works with modprobe. What is wrong?

That could be because modprobe can load complete chains of modules by its dependancies and even hand them correct options needed. So you might want to check "lsmod" after using modprobe to see which other modules it loads. Where it gets the parameters i dont know exactly. (maybe /etc/modules.conf can help here ?)

Quote:

I made a lot of assumptions in this topic, please tell me what I am doing wrong. Really don't know what do.If anybody has some older version of (older than 9.0) Suse with successfully compiled 2.6.x kernel, please write what you upgraded to get your Suse working fine with new kernel. Thanks in advance!

Sorry i am still on 2.4.x :)
But i hope i coud help clear things a bit up

Chris

chris78, thanks for this huge reply, but

I am sure that I've compiled a loadable module support,
as proof I am posting a part from my .config file in
/usr/src/linux-2.6.4:

# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y
"
Or there is some other option I should look for?

And I am aware of differences of insmod and modprobe, but
this is isn't thing this time.For example, I tried to load module
cryptoloop with insmod and modprobe, respectively and failed with first one,
but succeeded with second then I did lsmod and there was just cryptoloop as new module
without any modules in it's "background" or in list of modules.

If this gives you any new idea, please write.
Thanks !

I don't think you're doing anything wrong. There doesn't seem to be a problem. Evidently kernel modules are enabled, since you can load modules using modprobe. I don't know why insmod doesn't work, but why does it matter? The modules docs recommend using modprobe, so just don't use insmod. ("modprobe -v ..." may show how modprobe calls insmod, if you're curious.) That message from the kernel that modules are not enabled must mean they're not enabled *yet* --- I get that message, too. Not to worry.

I am writing this reply because I googled a lot, unsatisfied with your answers (nothing personal GregLee and chris78, thanks for effort!). I found out that I should update aaa_base and mkintrd, both for 2.6.x kernel and Suse 9.0 don't which means that I should find aaa_base and mkinitrd for Suse 9.0 and that's it.Does anybody happens to know links for them (I still don't know the actual version numbers of those programs/scripts)?Thanks!

Please read http://kerneltrap.org/node/view/1753
What you should try is to replace " /proc/ksyms " with " /proc/kallsyms " within /etc/rc.sysinit there where it says:

if ! LC_ALL=C grep -iq nomodules /proc/cmdline 2>/dev/null && [ -f /proc/ksyms ]; then
USEMODULES=y
fi

pablob, thanks for replying, I've already thought that my topic sank on bottom of this forum.Your link is interesting in way it gives me fact that I am not only one with this problem.But your advice doesn't work because I don't have /etc/rc.sysinit file and not even any file with those lines in my /etc/directory.Thanks anyway!


P.S.

I like your cookie!