Linux Sound subsystem development
 help / color / mirror / Atom feed
From: otisg@ivillage.com
To: linux-sound@vger.kernel.org
Subject: SB16: Bad or missing 16 bit DMA channel
Date: Fri, 07 Sep 2001 17:39:41 +0000	[thread overview]
Message-ID: <marc-linux-sound-99988458525824@msgid-missing> (raw)

Hello,

I have a SB sound card, model CT4170 plugged into an ISA slot of a Epox mother board, model EP-MVP3G5.

Every hour or so I see this in /var/log/messages:

modprobe: modprobe: Can't locate module sound-service-0-0
kernel: Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
kernel: sb: Creative ViBRA16X PnP detected
kernel: sb: ISAPnP reports 'Creative ViBRA16X PnP' at i/o 0x220, irq 5, dma 1, 3
kernel: SB 4.16 detected OK (220)
kernel: SB16: Bad or missing 16 bit DMA channel
kernel: sb: 1 Soundblaster PnP card(s) found.


I'm wondering why the kernel needs sound-service-0-0 module, which fails to load, when my sound works just fine without it, apparently?

I am also wondering what is causing "SB16: Bad or missing 16 bit DMA channel" warnings?

This is what I have in /etc/modules.conf:

alias sound-slot-0 sb 
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || : 
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :

Should I remove or change this?
I can't remember why I put this in modules.conf nor what it does, any more. :(

Thanks,
Otis

_________________________________________________________________
iVillage.com: Solutions for Your Life 
Check out the most exciting women's community on the Web   
http://www.ivillage.com

             reply	other threads:[~2001-09-07 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-07 17:39 otisg [this message]
2001-09-14  4:57 ` SB16: Bad or missing 16 bit DMA channel Paul Laufer

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=marc-linux-sound-99988458525824@msgid-missing \
    --to=otisg@ivillage.com \
    --cc=linux-sound@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