topic Can't locate module in Operating System - Linux

Can't locate module

Alex Lavrov. — Tue, 30 Aug 2005 07:58:27 GMT

Hello,

I just installed RHAS3-U4 and almost on every command (line network restart, rpm -qa etc ..) I get a message:

modprobe: Can't locate module block-major-135

Any suggestions?

Thanx.

Re: Can't locate module

Gopi Sekar — Tue, 30 Aug 2005 09:05:01 GMT

I believe something is missing in your system (obviously:)

check the /etc/modprobe.conf file if there is any entry with 'block-major-135' then comment that line and see whether you are getting that message.

what i gave you is just a hint on how to suppress the message, but you may have to listen to some other expert to find the root cause and correct it.

Hope this helps,
Gopi

Re: Can't locate module

Vitaly Karasik_1 — Tue, 30 Aug 2005 09:27:59 GMT

Alex,

First at all, RHEL3 UPD5 is available.

Do you have something unusual in your modules.conf? dmesg?

Rgds,
Vitaly

Re: Can't locate module

Ivan Ferreira — Tue, 30 Aug 2005 09:48:19 GMT

Try adding the following line to modprobe.conf:

alias block-major-135 off

Maybe you need to reboot.

Re: Can't locate module

Matti_Kurkela — Tue, 30 Aug 2005 10:13:52 GMT

block-major-135 refers to SCSI disk devices named /dev/sdig.../dev/sdiv. That means the 240th to 255th SCSI disks installed in the host.

If you don't actually have that many disks, you can definitely add the line
alias block-major-135 off
to /etc/modules.conf.

After making the change, run the "depmod" command. You don't need to boot after that, but booting instead of "depmod" works too.

The "depmod" command is normally run at boot time, but you can run it manually any time you wish.

Most "Can't locate module" messages are a result of a program probing the /dev directory trying to find some hardware. Probing a device file that has no driver attached will trigger an attempt to autoload the necessary module(s). If the messages are annoying, you can silence them by adding a "alias off" line to /etc/modules.conf.

Re: Can't locate module

Steven E. Protter — Tue, 30 Aug 2005 10:16:53 GMT

I suggest reinstallation. There may be a reason why RHAS3 U5 got released.

shalom Alex.

SEP

Re: Can't locate module

Alex Lavrov. — Wed, 31 Aug 2005 01:09:22 GMT

Yep, I saw in several places that I can comment the line and it will suppress this message.

I don't have that amount of disks, only 2 mirrored 18GB disks.

Alex.

Re: Can't locate module

Stuart Browne — Wed, 31 Aug 2005 03:46:05 GMT

By default, Linux assigns various major and minor numbers for various functions. When you do something that accesses different subsystems, it briefly pokes these major and minor numbers to see if they are alive.

All that's happening is when you do given commands, it pokes the SCSI subsystem, which goes and pokes the SCSI device nodes in /dev.

If you're only getting block-major-135, then you'll have:

/dev/sda (sda1-sda15)
/dev/sdb (sdb1-sdb15)
...
/dev/sdif (sdif1-sdif15)

But you'll be missing the '/dev/sdig' through to '/dev/sdiv' grouping (which is block major 135).

Now, you can either create 256 device nodes, or as you don't have that many SCSI devices anyway, just turn the block-major-135 off by modifying '/etc/modprobe.conf'.

Choice is yours.

Re: Can't locate module

Alex Lavrov. — Wed, 31 Aug 2005 04:20:34 GMT

Thanx Stuart.