Re: Modprobe error

[Robert Storey <y2kbug@ms25.hinet.net>]

Dear RituRaj,

Modprobe won't load the driver if the device isn't present. And yes, it will report the error. Important: you should only type "modprobe ips" rather than "modprobe ips.o". Since I'm using a 2.6 kernel, my error message is different from yours, but similar:

   root@sonic:~# modprobe ips
   FATAL: Error inserting ips    (/lib/modules/2.6.10-kanotix-8/kernel/drivers/scsi/ips.ko): No such device

As a footnote, you might want to know that on 2.6.x kernel, the modules have been renamed to end with *.ko rather than *.o, though again this makes no different since you don't use the extension with the modprobe command.

cheers,
Robert

On Mon, 4 Apr 2005 03:02:28 -0700 (PDT)
RituRaj <ritu_turu@yahoo.com> wrote:

> I have compiled a customised 2.4.29 kernel. I am able
> to boot into the new kernel. For some reason i want to
> do a modprobe on ips.o But it is not working.
> 
> modprobe ips
> /lib/modules/2.4.29-grsec-custom1/kernel/drivers/scsi/ips.o:
> init_module: No such device
> Hint: insmod errors can be caused by incorrect module
> parameters, including invalid IO or IRQ parameters.
>       You may find more information in syslog or the
> output from dmesg
> /lib/modules/2.4.29-grsec-custom1/kernel/drivers/scsi/ips.o:
> insmod
> /lib/modules/2.4.29-grsec-custom1/kernel/drivers/scsi/ips.o
> failed
> /lib/modules/2.4.29-grsec-custom1/kernel/drivers/scsi/ips.o:
> insmod ips failed
> 
> 
> I am testing this on a test machine which does not
> have the SmartArray IBM adapter(for which ips.o is the
> driver). So my question is does the modprobe/insmod
> give error while loading a driver if it doesnt find
> the  required device id? or is it something else?
> 
> Regards;
> Rituraj