(Slack 9.1, KDE 3.1.4)

For the hell of it I was looking at my syslog and I see zillions of the
following message. Sometimes they are two hours apart, sometimes less and
they are always in two pairs. What is goin' on? (This has been probably
happening for the past year!)

BTW, my sound works just fine. I have an Intel 810 mobo with built-in sound
(not a seperate sound card that I know of.)

Research done (which did not help)

http://www.fedoraforum.org/forum/showthread.php?t=406 (fedora)

http://linux.derkeiler.com/Mailing-L...4-02/3853.html (debian)

http://216.239.57.104/search?q=cache...xquestions.org
questions/printthread.php%3Fs%3D%26threadid%3D157120+slackwa re+modprobe
+modprobe:+Can%27t+locate+module+sound-slot-1&hl=en&lr=lang_en (slackware,
but it could have been Greek!)

Finally there was the start of thread about this on a.o.l.s but it got into a
flame war:

http://groups.google.com/groups?hl=e...ark_mitwro ng
40vlad.bellsouth.net&rnum=4&prev=/groups%3Fq%3Dslackware%2520modprobe%253A
2520modprobe%253A%2520Can%27t%2520locate%2520modul e%2520sound-slot-1%26num
3D50%26hl%3Den%26lr%3D%26sa%3DN%26tab%3Dwg

Honest. I've tried but can't seem to find how to stop this.... or even if I
should! Do I qualify for a bit of help?

-Al


Oct 16 13:31:56 darkstar modprobe: modprobe: Can't locate module sound-slot-1
Oct 16 13:31:56 darkstar modprobe: modprobe: Can't locate module
sound-service-1-0

Oct 16 13:31:56 darkstar modprobe: modprobe: Can't locate module sound-slot-1
Oct 16 13:31:56 darkstar modprobe: modprobe: Can't locate module
sound-service-1-0

Oct 16 13:51:58 darkstar modprobe: modprobe: Can't locate module sound-slot-1
Oct 16 13:51:58 darkstar modprobe: modprobe: Can't locate module
sound-service-1-0

Oct 16 13:51:58 darkstar modprobe: modprobe: Can't locate module sound-slot-1
Oct 16 13:51:58 darkstar modprobe: modprobe: Can't locate module
sound-service-1-0

Oct 16 14:01:39 darkstar modprobe: modprobe: Can't locate module sound-slot-1
Oct 16 14:01:39 darkstar modprobe: modprobe: Can't locate module
sound-service-1-0

Oct 16 14:01:39 darkstar modprobe: modprobe: Can't locate module sound-slot-1
Oct 16 14:01:39 darkstar modprobe: modprobe: Can't locate module
sound-service-1-0


Oct 16 16:42:45 darkstar modprobe: modprobe: Can't locate module sound-slot-1
Oct 16 16:42:45 darkstar modprobe: modprobe: Can't locate module
sound-service-1-0

Oct 16 16:42:45 darkstar modprobe: modprobe: Can't locate module sound-slot-1
Oct 16 16:42:45 darkstar modprobe: modprobe: Can't locate module
sound-service-1-0

Al C. wrote:

> Oct 16 16:42:45 darkstar modprobe: modprobe: Can't locate module
> sound-slot-1 Oct 16 16:42:45 darkstar modprobe: modprobe: Can't locate
> module sound-service-1-0

I looked around a bit more and found the following adivce:

You don't have to do anything. However, if you /want/ to do something, you
should edit your /etc/modules.conf file to include
alias sound-slot-1 off
alias sound-service-1-0 off
and that should stop the warnings from coming out

Lew Pitcher
IT Consultant, Enterprise Technology Solutions

_&_&_&_&_&_&_&_&_&_&_&_&___&__&


What Lew posted will get rid of the symptoms (and it works).

If you are using KDE, the cause may be you have more than one mixer
configured.

See Settings/Control Center/Sound & Multimedia/Sound System/Mixer and ensure
your Hardware Settings have only one mixer vice two.

Jack S. Lai - Senior Systems Analyst

I tried the KDE thing. Both were set to "2" so I set them to 1.

Do I have to re-boot or re-log on? Same question ... do I reboot if I fix
etc/modules/conf.

Al

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Al C. wrote:
> Al C. wrote:
>
>
>>Oct 16 16:42:45 darkstar modprobe: modprobe: Can't locate module
>>sound-slot-1 Oct 16 16:42:45 darkstar modprobe: modprobe: Can't locate
>>module sound-service-1-0
>
>
> I looked around a bit more and found the following adivce:
>
> You don't have to do anything. However, if you /want/ to do something, you
> should edit your /etc/modules.conf file to include
> alias sound-slot-1 off
> alias sound-service-1-0 off
> and that should stop the warnings from coming out
>
> Lew Pitcher
> IT Consultant, Enterprise Technology Solutions
>
> _&_&_&_&_&_&_&_&_&_&_&_&___&__&
>
>
> What Lew posted will get rid of the symptoms (and it works).
>
> If you are using KDE, the cause may be you have more than one mixer
> configured.
>
> See Settings/Control Center/Sound & Multimedia/Sound System/Mixer and ensure
> your Hardware Settings have only one mixer vice two.
>
> Jack S. Lai - Senior Systems Analyst
>
> I tried the KDE thing. Both were set to "2" so I set them to 1.
>
> Do I have to re-boot or re-log on? Same question ... do I reboot if I fix
> etc/modules/conf.

No, you do not have to reboot or log off and on again.

You should log in as root (su or sudo will do), and execute
/sbin/depmod -a
to avoid a warning that comes when you change modules.conf, though.

In any case, as my original post (which you obviously found) indicates, the
messages are just warnings, and not errors. You can safely ignore them for
now, and let the next reboot take care of applying your /etc/modules.conf
changes, if you want.

Luck be with you ;-)


- --
Lew Pitcher

Master Codewright & JOAT-in-training | GPG public key available on request
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBcdd8agVFX4UWr64RAq5fAKCMytGkZqgs5NvdyoXfJU knLjF5gACeLPEf
KUdQ4clldz/nc8+fQvrGxPk=
=n1E3
-----END PGP SIGNATURE-----

On 2004-10-17, Al C. <no.spam.acanton@adams-blake.no.spam.com> wrote:

> http://216.239.57.104/search?q=cache...xquestions.org
> questions/printthread.php%3Fs%3D%26threadid%3D157120+slackwa re+modprobe
> +modprobe:+Can%27t+locate+module+sound-slot-1&hl=en&lr=lang_en (slackware,

> http://groups.google.com/groups?hl=e...ark_mitwro ng
> 40vlad.bellsouth.net&rnum=4&prev=/groups%3Fq%3Dslackware%2520modprobe%253A
> 2520modprobe%253A%2520Can%27t%2520locate%2520modul e%2520sound-slot-1%26num
> 3D50%26hl%3Den%26lr%3D%26sa%3DN%26tab%3Dwg

You may want to try a link shortener:

http://makeashorterlink.com/index.php
http://tinyurl.com/

nb

On Sat, 16 Oct 2004 17:27:53 -0700, Al C. wrote:

> (Slack 9.1, KDE 3.1.4)
>
> For the hell of it I was looking at my syslog and I see zillions of the
> following message. Sometimes they are two hours apart, sometimes less and
> they are always in two pairs. What is goin' on? (This has been probably
> happening for the past year!)
>
> BTW, my sound works just fine. I have an Intel 810 mobo with built-in sound
> (not a seperate sound card that I know of.)
>
See if the messages correlate with any particular activity. Clearly,
somebody is trying to load those modules, and can't find them. It's
probably just the one app. Since you say your sound works OK, then
you can disable whatever is looking for those modules. Finding
what that is, only you can do. ;-)

Maybe, check the log file, do something that you'd expect to make
a sound, check the log file again, do something else ...

Good Luck!
Rich

Rich Grise wrote:

> On Sat, 16 Oct 2004 17:27:53 -0700, Al C. wrote:
>
>> (Slack 9.1, KDE 3.1.4)
>>
>> For the hell of it I was looking at my syslog and I see zillions of the
>> following message. Sometimes they are two hours apart, sometimes less and
>> they are always in two pairs. What is goin' on? (This has been probably
>> happening for the past year!)
>>
>> BTW, my sound works just fine. I have an Intel 810 mobo with built-in sound
>> (not a seperate sound card that I know of.)
>>
> See if the messages correlate with any particular activity. Clearly,
> somebody is trying to load those modules, and can't find them. It's
> probably just the one app. Since you say your sound works OK, then
> you can disable whatever is looking for those modules. Finding
> what that is, only you can do. ;-)
>
> Maybe, check the log file, do something that you'd expect to make
> a sound, check the log file again, do something else ...

First I set the KDE Mixer thing to 1 from 2. I waited a few hours, but sure
enough the error messages kept coming. So then I made the changes to
modules.conf as suggested by Lou P. and I re-booted (mainly because I didn't
understand the depmod man page and was afraid of doing some real "an idiot in
root" damage. I had not re-booted this machine since June when power went off
for half a day!)

This morning I checked the syslog and it is an "empty document" so looks like
I cured the problem.

I'd like to get rid of the "-- MARK --" in messages log. I can't figure out
any reason for that, but it's benign. Actually I'd like to find a good HOW-TO
on logging, what is reported where, etc. but have not really looked yet. I
checked usr/docs/HOWTO and nothing for logging... and while the stuff in
there is interesting a lot of it is 4 or 5 years old!

I'm kind of surprised that Linux (or KDE) does not have a built-in log reader
that formats some of these logs into columns and rows (sort of like what
"top" does) so that you don't have to look at the raw data in the files. It
would make it easier for my old eyes!

ANC

Al C. wrote :

> I'd like to get rid of the "-- MARK --" in messages log. I can't figure out
> any reason for that, but it's benign.

From 'man syslogd':

"-m interval
The syslogd logs a mark timestamp regularly. The default interval
between two -- MARK -- lines is 20 minutes. This can be changed with
this option. Setting the interval to zero turns it off entirely."
--
Thomas O.

This area is designed to become quite warm during normal operation.

On Sun, 17 Oct 2004 08:17:49 -0700, Al C. wrote:

> I'd like to get rid of the "-- MARK --" in messages log.

Open /etc/rc.d/rc.syslog in your favorite editor and add "-m 0" to the
arguments ... "man syslogd" ...

> I can't figure out any reason for that,

Well if running a central log server in the network , one might want to
know the syslog service on clients are still alive and well. (And checking
if the daemon(s) are still running - say by way of setting an SNMP trap -
isn't as good as haveing it send an actual massage periodically.)

> but it's benign. Actually I'd like to find a good HOW-TO on logging,

Maybe a web search will help (idunno). I think the docs are quite good.
Try man pages: syslogd , syslog , syslog.conf , logger , klogd , logrotate

> what is reported where, etc. but have not really looked yet. I checked
> usr/docs/HOWTO and nothing for logging... and while the stuff in there
> is interesting a lot of it is 4 or 5 years old!

As long as not much has changed, that shouldn't matter.

> I'm kind of surprised that Linux (or KDE) does not have a built-in log
> reader that formats some of these logs into columns and rows (sort of
> like what "top" does) so that you don't have to look at the raw data in
> the files. It would make it easier for my old eyes!

kwatch

--
-Menno.

On Sun, 17 Oct 2004 17:11:03 +0000, Menno Duursma wrote:

> On Sun, 17 Oct 2004 08:17:49 -0700, Al C. wrote:
....
>> what is reported where, etc. but have not really looked yet. I checked
>> usr/docs/HOWTO and nothing for logging... and while the stuff in there
>> is interesting a lot of it is 4 or 5 years old!
>
> As long as not much has changed, that shouldn't matter.

I'd like to find something on iptables a little more introductory than
man iptables. :-)

Cheers!
Rich