You are not logged in.

#1 2009-03-15 22:13:38

yingwuzhao
Member
Registered: 2009-01-13
Posts: 109

How does udev decide to load oss or alsa when boot up?

Since Skottish has told me I do not need to blacklist alsa in MODULES in order to use oss.
I assume that udev will choose oss rather than alsa to load when booting up, then I am wondering how does udev choose which one to load, alsa or oss?
And suppose one day, I want to use alsa again, how can I make udev to choose alsa instead of oss?

Also by the way, will there be any conflict to load both alsa and oss together?
Thanks, guys.:)

Offline

#2 2009-03-15 22:16:22

pharcyde
Member
From: Connecticut
Registered: 2009-03-13
Posts: 88

Re: How does udev decide to load oss or alsa when boot up?

Wouldn't you just replace ALSA with OSS daemons in /etc/rc.conf?

Offline

#3 2009-03-15 22:44:39

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,942

Re: How does udev decide to load oss or alsa when boot up?

yingwuzhao,

I'm sorry for closing the other thread. I thought that you were done and it was starting to become something else.

What pharcyde said is correct. Remove 'alsa' from the DAEMONS array in rc.conf, and put 'oss' in it's place. Also, if there are any traces of sound related stuff in the MODULES section, remove those too. You don't need them for ALSA or OSS.

Offline

#4 2009-03-15 22:55:11

yingwuzhao
Member
Registered: 2009-01-13
Posts: 109

Re: How does udev decide to load oss or alsa when boot up?

Ok, so udev actually look at what is DAEMON to decide what to load?

I didn't know this.. I thought when boot up, udev will load alsa by default, then why did the OSS Wiki said we need to put !soundcore in MODULES to blacklist Alsa?

hmm

Last edited by yingwuzhao (2009-03-15 22:58:59)

Offline

#5 2009-03-15 22:56:58

ataraxia
Member
From: Pittsburgh
Registered: 2007-05-06
Posts: 1,553

Re: How does udev decide to load oss or alsa when boot up?

As far as I understand it, udev will always try to load alsa, unless it's blacklisted or absent (the OSS install script removes the ALSA modules, that's why you don't need to blacklist them). udev doesn't know about OSS. The OSS modules are loaded by the oss rc.d script.

Sound-heads, is this accurate?

Offline

#6 2009-03-15 23:08:45

yingwuzhao
Member
Registered: 2009-01-13
Posts: 109

Re: How does udev decide to load oss or alsa when boot up?

the OSS install script removes the ALSA modules, that's why you don't need to blacklist them

Where did oss install script remove alsa modules from? can you elaberate it a little bit?
If so, after installing oss, can you still load alsa instead of oss?

thanks.:/

Offline

#7 2009-03-15 23:13:39

Misfit138
Misfit Emeritus
From: USA
Registered: 2006-11-27
Posts: 4,189

Re: How does udev decide to load oss or alsa when boot up?

Alsa is a kernel component. (API)
Alsa modules are simply drivers, which can be automatically loaded by udev.
The Alsa daemon simply restores volume levels, nothing more.

Offline

#8 2009-03-15 23:35:24

yingwuzhao
Member
Registered: 2009-01-13
Posts: 109

Re: How does udev decide to load oss or alsa when boot up?

then the same question: how did we load alsa after installing oss? if oss install script remove the alsa modules?
hmm

Offline

#9 2009-03-16 01:24:51

ataraxia
Member
From: Pittsburgh
Registered: 2007-05-06
Posts: 1,553

Re: How does udev decide to load oss or alsa when boot up?

It tells you when you install oss that it's moving away the alsa modules. It runs a script packaged with oss to do this. I haven't actually read the script. It's located at /usr/lib/oss/build/install.sh .

Offline

#10 2009-03-16 03:18:20

yingwuzhao
Member
Registered: 2009-01-13
Posts: 109

Re: How does udev decide to load oss or alsa when boot up?

Thanks, I see. That helps!
big_smile

Offline

Board footer

Powered by FluxBB