Find the answer to your Linux question:
Results 1 to 4 of 4
I am using a live CD implementation of a custom Linux application on a Dell Poweredge 2850 server. The CD cannot automatically see the internal RAID drives on the server ...
  1. #1
    Just Joined!
    Join Date
    Jan 2007
    Posts
    3

    Post Creating a .ko file?

    I am using a live CD implementation of a custom Linux application on a Dell Poweredge 2850 server. The CD cannot automatically see the internal RAID drives on the server (LSI Logic Perc 4e/Di RAID Controller). When I autoprobe for the drivers, I'm told that the necessary driver, megaraid_mbox, is not found on the CD.

    I can manually install the driver at runtime via a floppy disk. However, it requires that I provide the driver with a .ko extension (megaraid_mbox.ko). I've searched all over the place for this file, and cannot find it in this form.

    I've downloaded a .tar.gz version of the file with the necessary .c and .h files along with a Makefile file. When I look at the included Makefile, this is what I see:

    Code:
    obj-$(CONFIG_MEGARAID_MM)	+= megaraid_mm.o
    obj-$(CONFIG_MEGARAID_MAILBOX)	+= megaraid_mbox.o
    It looks like running the makefile on a Linux system output ".o" files. I assume I can't just change the .o to .ko in the Makefile, since .ko files have additional information built into them.

    I'm also running Windows, so I don't have any software (Cygwin?) to compile the .c files.

    Can anyone provide me with a link to download the megaraid_mbox.ko file? If not, can someone either compile it or help me compile it? Here is the .tar.gz file that has the necessary components in it.

    ftp://ftp.lsil.com/pub/linux-megarai...id2.20.3.1.tgz

    Thanks in advance for all of your help.

  2. #2
    JHB
    JHB is offline
    Just Joined!
    Join Date
    Jan 2007
    Location
    South Africa
    Posts
    22

    Missing kernel module

    Files with the .ko extention are kernel modules for the 2.6 version of kernels.

    I am running SuSE 10.2, and have the megaraid_mbox.ko file, but it was compiled for the 2.6.18.2-34-default kernel used.

    I don't think getting this working on a Live CD is going to be easy.

    If you have another linux box, you can copy the content of the whole cd to disk, modify it, and create a new cd.

    I think it will be something like this:

    #dd if=/dev/cdrom of=cdimage.iso

    You can then mount this image using
    #mount cdimage /mnt

    I don't think the sources of the kernel will be on the cd, so you may have to download one that closely matches the running one, recompile it, and also compile the megaraid module.

    You may need to use #chroot /mnt to be able to ubdate the boot sector of the image, but I have never done this. I avoid Live CD's because they are slow.

    There is a way of ignoring the version numbers on modules, but I haven't used it in a long time. Then you can use a closely matched kernel, just compile the module, and put it on the image

    You can then use a package like k3b to burn the image to cd again.

    Good luck

  3. #3
    Just Joined!
    Join Date
    Jan 2007
    Posts
    3
    Actually, the live CD does not require me to recompile the kernel after adding the new driver file. It allows me to provide the new driver at runtime in order to detect the server RAID hardware.

    I downloaded a Gentoo distro and extracted the required .ko file to a floppy. However, I got the same error on the server. I think it's because the live CD is based on the 2.6.7 kernel, while the megaraid_mbox.ko file from the Gentoo release is from kernel 2.6.17.

    Can anyone point me to a place where I can find the megaraid_mbox.ko file from a 2.6.7 kernel? Thanks.

  4. #4
    Just Joined!
    Join Date
    Jan 2007
    Posts
    3
    Well, I no longer have a need for the .ko file. I was able to take care of the issue by other means (without using Linux). Thanks for everyone's help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...