minor problem: loading modules at start up

[Ben Pfaff]

Dam_Edged <DamedgedDon'tBother@home.com> writes:

> I have entries in my syslog that read as follows:
> 
> modprobe: Can't locate module binfmt -0000
> modprobe: Can't locate module binfmt -0000
> modprobe: Can't locate module sound-service-0-0
> modprobe: Can't locate module sound-slot-1
> modprobe: Can't locate module sound-service-1-0
> modprobe: Can't locate module sound-slot-1
> modprobe: Can't locate module sound-service-1-0

These errors occur when kmod tries to load a module and can't
find it.  For hardware devices, usually they occur when a piece
of hardware isn't actually present or not configured.

> I am assuming the errors are occuring at
> start up. (correct?)

Probably.

> I have no idea what binfmt is for.

I assume that it's for alternate binary formats--a.out, ELF, #!,
Java, misc being the common ones.

> Is there a conif file that I can edit, so this
> machine doesn't try to load these modules?
> I looked at the modules.conf, and I did see an
> line that reads:
> 
> alias sound-slot-0 sb

You can change it to `alias sound-slot-0 off' if you want to
disable it.

> Would editing a config file be the best way 
> to correct this problem? 

Well, yes, if you consider it a real problem.  Feel free to just
ignore those messages.  They're harmless.
-- 
"Ho ho ho. I _so_ enjoy making a fool out of myself."
--Linus, on Christmas Day, 2000