mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin Eriksson" <nitrax@giron.wox.org>
To: "Matteo Sasso" <icemaze@tiscalinet.it>, <linux-kernel@vger.kernel.org>
Subject: Re: Bug (?) report - Nope
Date: Tue, 27 Nov 2001 18:21:10 +0100	[thread overview]
Message-ID: <002d01c17767$e89e7480$0201a8c0@HOMER> (raw)
In-Reply-To: <GAELJDOEMJGDLHEONDIOEEBOCBAA.icemaze@tiscalinet.it>

----- 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/



      parent reply	other threads:[~2001-11-27 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-27 15:04 Bug (?) report Matteo Sasso
2001-11-27 15:51 ` Tommy Reynolds
2001-11-27 17:21 ` Martin Eriksson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002d01c17767$e89e7480$0201a8c0@HOMER' \
    --to=nitrax@giron.wox.org \
    --cc=icemaze@tiscalinet.it \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®