On Thu, 12 Sep 2002, Randall Hobbs wrote:
> Hi guys. I've got Alsa compiled and running fine on my RedHat 7.2 machine
> (using KDE 3.0.7 and one SoundBlaster PCI512). I've just got a few "quirks"
> that I'm trying to work out, and have found no answers to them yet. First
> off, I get this in my logwatch daily:
>
> --------------------- ModProbe Begin ------------------------
>
> Can't locate these modules:
>    sound-service-3-0: 4 Time(s)
>    sound-slot-1: 4 Time(s)
>    sound-slot-2: 4 Time(s)
>    sound-slot-3: 4 Time(s)
>    sound-service-1-0: 4 Time(s)
>    sound-service-2-0: 4 Time(s)

I get that too every now and then. What it means is that some software
using OSS tried to access what would be the 2nd sound card (or even the
3rd one in your case). In my case Audacity always does that (I have 2
sound cards, so Audacity always wants to load sound-slot-2, no idea why).
You can get rid of all these messages in the log if you add lines like
this to your modules.conf:
alias sound-slot-1 off
alias sound-slot-2 off
etc. This will make it stop complaining. This still does not answer the
question what gave it the idea to even try for the 3rd sound card :)

>
>
>  ---------------------- ModProbe End -------------------------
>
> Here's a copy of my modules.conf file:
>
> alias parport_lowlevel parport_pc
> alias eth0 tulip
> alias usb-controller usb-uhci
> alias char-major-195 NVdriver
>
> # ALSA portion
> alias char-major-116 snd
> alias snd-card-0 snd-emu10k1
> # module options should go here
>
> # OSS/Free portion
> alias char-major-14 soundcore
> alias sound-slot-0 snd-card-0
>
> # card #1
> alias sound-service-0-0 snd-mixer-oss
> alias sound-service-0-1 snd-seq-oss
> alias sound-service-0-3 snd-pcm-oss
> alias sound-service-0-8 snd-seq-oss
> alias sound-service-0-12 snd-pcm-oss
>
> Everything seems to work great, but I'm sorta' curious about those messages
> from logwatch. Also, I don't know if it's any relation or not, but when open
> a page with Konquorer that contains a midi, it locks the window up
> completely. Trying to go into kcontrol and clicking on midi also locks that
> window up. Don't know if this might be related to the modules problem above
> or what, but it's something I would sure like to get fixed.
>
> Thanks for any help you might be able to give.
>
>

-- 
                                  Fedor G. Pikus
Mentor Graphics Corporation         | Phone: (503) 685-4857
8405 SW Boeckman Road               | FAX:   (503) 685-1239
Wilsonville, Oregon 97070           | http://www.pikus.net/~pikus/


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to