Bug (?) report

Bug (?) report

[Matteo Sasso]

I'm quite a new linux user and system administrator (my own!) and I
encountered the following problems:
1) As the system starts up and the mixer settings are loaded, modprobe
complains that 'sound-slot-0' and 'sound-service-0-0' modules are not
present (in my kernel/drivers/sound directory I got just ac97_codec.o,
emu10k1, sound.o and soundcore.o). I've got a Sound Blaster Live! 5.1, a
'2.4.16-pre1' kernel and kmod usually works good, failing only with sound
(both with 'gom' mixer and with 'mpg123' player), so I have to 'modprobe
emu10k1' manually.
2) I tried for the first time to play a bit with kernel source and I was
trying to lower console_loglevel in order to have all the startup printk's
disappear. I lowered the DEFAULT_CONSOLE_LOGLEVEL constant in
'kernel/printk.c' from '7' to '5' (just to be sure) but that wasn't enough
to get rid of all those annoying KERN_INFO. Why didn't it work?

Please feel free not to answer if you don't feel like. I know I can be buggy
sometimes! :P

Thank you!
--
icemaze@tiscalinet.it

Re: Bug (?) report

[Tommy Reynolds]

[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]

Quick to seize an opportunity, "Matteo Sasso" <icemaze@tiscalinet.it> wrote:

> I'm quite a new linux user and system administrator (my own!) and I
> encountered the following problems:
> 1) As the system starts up and the mixer settings are loaded, modprobe
> complains that 'sound-slot-0' and 'sound-service-0-0' modules are not
> present (in my kernel/drivers/sound directory I got just ac97_codec.o,
> emu10k1, sound.o and soundcore.o). I've got a Sound Blaster Live! 5.1, a
> '2.4.16-pre1' kernel and kmod usually works good, failing only with sound
> (both with 'gom' mixer and with 'mpg123' player), so I have to 'modprobe
> emu10k1' manually.

Add the following line to "/etc/modules.config":

	alias sound-slot-0 emu10k1

and then:

	# /sbin/depmod -ae

You need this because your module is named "emu10k1" but the sound system is
looking for a module named "sound-slot-0" (this is a computed module name, not
an actual name).

> 2) I tried for the first time to play a bit with kernel source and I was
> trying to lower console_loglevel in order to have all the startup printk's
> disappear. I lowered the DEFAULT_CONSOLE_LOGLEVEL constant in
> 'kernel/printk.c' from '7' to '5' (just to be sure) but that wasn't enough
> to get rid of all those annoying KERN_INFO. Why didn't it work?

You don't need to mess with that.  Just:

	# echo 5 > /proc/sys/kernel/printk

anytime you want.  Of course, since Step-1 above fixed your original problem,
you won't need to do this at all ;-)

---------------------------------------------+-----------------------------
Tommy Reynolds                               | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone:  +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA  | FAX:    +1.256.837.3839
Senior Software Developer                    | Mobile: +1.919.641.2923

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: Bug (?) report - Nope

[Martin Eriksson]

----- Original Message -----
From: "Matteo Sasso" <icemaze@tiscalinet.it>
To: <linux-kernel@vger.kernel.org>
Sent: Tuesday, November 27, 2001 4:04 PM
Subject: Bug (?) report


> I'm quite a new linux user and system administrator (my own!) and I
> encountered the following problems:
> 1) As the system starts up and the mixer settings are loaded, modprobe
> complains that 'sound-slot-0' and 'sound-service-0-0' modules are not
> present (in my kernel/drivers/sound directory I got just ac97_codec.o,
> emu10k1, sound.o and soundcore.o). I've got a Sound Blaster Live! 5.1, a
> '2.4.16-pre1' kernel and kmod usually works good, failing only with sound
> (both with 'gom' mixer and with 'mpg123' player), so I have to 'modprobe
> emu10k1' manually.

You have to alias sound-slot-0 and/or sound-service-0-0 to the correct
module.
"man modules.conf" will propably tell you more

> 2) I tried for the first time to play a bit with kernel source and I was
> trying to lower console_loglevel in order to have all the startup printk's
> disappear. I lowered the DEFAULT_CONSOLE_LOGLEVEL constant in
> 'kernel/printk.c' from '7' to '5' (just to be sure) but that wasn't enough
> to get rid of all those annoying KERN_INFO. Why didn't it work?

Propably you just block the console messages *after* boot. I suspect there
is already a kernel parameter to set this though, so you don't need to mess
with the source. Browse a bit in "Documentation/kernel-parameters.txt"

(hint: try appending "quiet=1" when you boot your kernel)

>
> Please feel free not to answer if you don't feel like. I know I can be
buggy
> sometimes! :P

Hmm. Yes. Read the FAQ for lkml:
http://www.tux.org/lkml/