question about 2.6 modules

question about 2.6 modules

[lky]

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

Hi:
    I reinstalled my linux system today. I installed the Redhat9.0 first. Then I installed 2.6-based SELinux. In fact I installed two 2.6 kernels. One is the maintenance kernel with SELinux disabled and the other with SELinux enabled.Before the installation I installed the new modutils (downloaded from http://www.kernel.org/pub/linux/kernel/people/rusty/modules)   for the 2.6 kernel first. And then I modified the /etc/rc.sysinit, just let '/proc/sys/kernel/modprobe' replaced by '/sbin/modprobe'.After that I installed the maintenance kernel first. Everything is ok but when I rebooted the new kernel I found modules such as my network card and loopback device can't be automatically loaded to work yet. Why? The modules should work after installed the new modutils for 2.6 kernel. Have I forgot something? 
    Thanks!
lky  

[-- Attachment #2: Type: text/html, Size: 1368 bytes --]

Re: question about 2.6 modules

[Eric Estabrooks]

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

lky wrote:

> Hi:
> I reinstalled my linux system today. I installed the Redhat9.0 first.
> Then I installed 2.6-based SELinux. In fact I installed two 2.6
> kernels. One is the maintenance kernel with SELinux disabled and the
> other with SELinux enabled.Before the installation I installed the new
> modutils (downloaded from
> http://www.kernel.org/pub/linux/kernel/people/rusty/modules) for the
> 2.6 kernel first. And then I modified the /etc/rc.sysinit, just let
> '/proc/sys/kernel/modprobe' replaced by '/sbin/modprobe'.After that I
> installed the maintenance kernel first. Everything is ok but when I
> rebooted the new kernel I found modules such as my network card and
> loopback device can't be automatically loaded to work yet. Why? The
> modules should work after installed the new modutils for 2.6 kernel.
> Have I forgot something?
> Thanks!
> lky


do the modules have .ko instead of .o? the 2.6 kernel modules now need
to end in .ko to be automatically loaded, and it is just a name
difference. I had this problem with some modules that I had compiled for
2.6 and I just renamed them and depmod'd and they worked fine.

Eric


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3419 bytes --]

Re: question about 2.6 modules

[lky]

On Wednesday, October 29, 2003 8:26 AM,Eric Estabrooks wrote:

> do the modules have .ko instead of .o? the 2.6 kernel modules now need
> to end in .ko to be automatically loaded, and it is just a name
> difference. I had this problem with some modules that I had compiled for
> 2.6 and I just renamed them and depmod'd and they worked fine.

I have all my ordered modules with .ko and I can load them with modprobe from command line.But the modules can't be automatically loaded when I run the associated commands. For example,I have built the vfat filesystem as a module and the system also created the vfat.ko file.But when I reboot the new kernel and run 'mount /dev/hda6 /mnt' it said the kernel don't support vfat filesystem.(/dev/hda6 is a vfat section) However I can run 'modprobe vfat' to load the vfat module.
I have modified the /etc/rc.sysinit and just let '/proc/sys/kernel/modprobe' replaced by '/sbin/modprobe'. Did it have some problems?
Thanks!
lky


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.