2 Jan
2007
2 Jan
'07
11:28 p.m.
I am using alsa drivers built right into the kernel, rather than
modules. My Kubuntu system figures that my M-audio card is 0, and
the Soundblaster is 1. I want to reverse that. Can I?
The reason for this, is that many apps seem to be unable to play
through the M-audio. I'm thinking it's because they use the OSS
interface, and there is no OSS kernel option for the ice1712.
Could that be true?
Actually, after booting my new kernel, I find that there are no
/dev/dsp* devices at all. No wonder the non-alsa apps don't work.
Still, I checked OSS support, and support for the Live! card.
Not sure why I don't have at least /dev/dsp0.
Thanks,
Tobiah
3 Jan
3 Jan
1:24 a.m.
Solved for now, I think. I haven't built a kernel in
a while, and I thought that including the native OSS support
would get me my /dev/dsp* stuff back. After reading some
internet, I realized that the OSS stuff is truly out of the
loop, and one really wants to build in the OSS emulation
stuff that is under the ALSA menu.
So, after rebooting many times, and answering the nvidia
driver questions as many times, I still wonder about the
issue of card order. Right now all is ok, but I've heard
many reports of card order swapping from boot to boot. Not
so hot.
Experiences?
Thanks,
Tobiah
St wrote:
I am using alsa drivers built right into the kernel,
rather than
modules. My Kubuntu system figures that my M-audio card is 0, and
the Soundblaster is 1. I want to reverse that. Can I?
The reason for this, is that many apps seem to be unable to play
through the M-audio. I'm thinking it's because they use the OSS
interface, and there is no OSS kernel option for the ice1712.
Could that be true?
Actually, after booting my new kernel, I find that there are no
/dev/dsp* devices at all. No wonder the non-alsa apps don't work.
Still, I checked OSS support, and support for the Live! card.
Not sure why I don't have at least /dev/dsp0.
Thanks,
Tobiah
7:41 a.m.
simple solution sudo asoundconf list prints a list of all sound cards in the
system
sudo asoundconf set-default-card "very nice sound card"
On 1/3/07, St <st(a)tobiah.org> wrote:
Solved for now, I think. I haven't built a kernel in
a while, and I thought that including the native OSS support
would get me my /dev/dsp* stuff back. After reading some
internet, I realized that the OSS stuff is truly out of the
loop, and one really wants to build in the OSS emulation
stuff that is under the ALSA menu.
So, after rebooting many times, and answering the nvidia
driver questions as many times, I still wonder about the
issue of card order. Right now all is ok, but I've heard
many reports of card order swapping from boot to boot. Not
so hot.
Experiences?
Thanks,
Tobiah
St wrote:
--
"When you get to the end of all the light you know and it's time to step
into the darkness of the unknown, faith is knowing that one of two things
shall happen: either you will be given something solid to stand on, or you
will be taught how to fly." --Dr. Edward Teller
I am using alsa drivers built right into the
kernel, rather than
modules. My Kubuntu system figures that my M-audio card is 0, and
the Soundblaster is 1. I want to reverse that. Can I?
The reason for this, is that many apps seem to be unable to play
through the M-audio. I'm thinking it's because they use the OSS
interface, and there is no OSS kernel option for the ice1712.
Could that be true?
Actually, after booting my new kernel, I find that there are no
/dev/dsp* devices at all. No wonder the non-alsa apps don't work.
Still, I checked OSS support, and support for the Live! card.
Not sure why I don't have at least /dev/dsp0.
Thanks,
Tobiah
2:53 p.m.
Now THAT is slick! Thanks David!
I wonder why I haven't read that anywhere before?
Think I'm going to sticky note that in my blog.
Jon Hoskins
On 1/3/07, David Stephens <linuxrootuser(a)gmail.com> wrote:
simple solution sudo asoundconf list prints a list of all sound cards in
the system
sudo asoundconf set-default-card "very nice sound card"
On 1/3/07, St <st(a)tobiah.org> wrote:
Solved for now, I think. I haven't built a kernel in
a while, and I thought that including the native OSS support
would get me my /dev/dsp* stuff back. After reading some
internet, I realized that the OSS stuff is truly out of the
loop, and one really wants to build in the OSS emulation
stuff that is under the ALSA menu.
So, after rebooting many times, and answering the nvidia
driver questions as many times, I still wonder about the
issue of card order. Right now all is ok, but I've heard
many reports of card order swapping from boot to boot. Not
so hot.
Experiences?
Thanks,
Tobiah
St wrote:
--
"When you get to the end of all the light you know and it's time to step
into the darkness of the unknown, faith is knowing that one of two things
shall happen: either you will be given something solid to stand on, or you
will be taught how to fly." --Dr. Edward Teller I am using alsa drivers built right into the
kernel, rather than
modules. My Kubuntu system figures that my M-audio card is 0, and
the Soundblaster is 1. I want to reverse that. Can I?
The reason for this, is that many apps seem to be unable to play
through the M-audio. I'm thinking it's because they use the OSS
interface, and there is no OSS kernel option for the ice1712.
Could that be true?
Actually, after booting my new kernel, I find that there are no
/dev/dsp* devices at all. No wonder the non-alsa apps don't work.
Still, I checked OSS support, and support for the Live! card.
Not sure why I don't have at least /dev/dsp0.
Thanks,
Tobiah
5 Jan
5 Jan
1:08 a.m.
Interesting, when I try it here (in a root terminal), I get only "Names
of available sound cards:" followed by nothing. Yet ALSA plays sound
just fine on my system.
Jon H wrote:
Now THAT is slick! Thanks David!
I wonder why I haven't read that anywhere before?
Think I'm going to sticky note that in my blog.
Jon Hoskins
On 1/3/07, *David Stephens* <linuxrootuser(a)gmail.com
<mailto:linuxrootuser@gmail.com>> wrote:
simple solution sudo asoundconf list prints a list of all sound
cards in the system
sudo asoundconf set-default-card "very nice sound card"
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
3 Jan
3 Jan
4:03 p.m.
David Stephens wrote:
simple solution sudo asoundconf list prints a list of
all sound cards in
the system
sudo asoundconf set-default-card "very nice sound card"
Will that also change which card gets /dev/dsp0 in OSS emulation?
I only want to use two cards, but if I had three, would I be able
to specify the order of all three?
Thanks,
Toby
6:01 p.m.
Not to butt in but... <heh>
Hmmmm I've got to mess aound with my setting for a 'new' junk machine I
am fooling around with...
If it was just for OSS applications you could do re-directs in the device
drivers I guess... I've got to do that one myself sometime this week
because I'm setting up two 'cards'... one on the mother board and the
other as a PCI card...
Alsa sees these two cards 'backwards' to my way of thinking and need...
It sees the mother board card as 'card1' and the plugin card as
'card0'...
I alsa need to set up /dev/dsp1 to card1... Alsa only set up emulation to
/dev/dsp (/dev/dsp0) and ignors the second card altogether...
It's been quite awhile since I have done these simple tasks and need a
refresher course... for sure ;-O Seems 'X' has got me away from the
console <heh>
I keep listening to this thread... I need an education too...
Have a good day and a better tomorrow...
thanks too also...
vince
On Wed, 3 Jan 2007, Tobiah wrote:
David Stephens wrote:
simple solution sudo asoundconf list prints a
list of all sound cards in
the system
sudo asoundconf set-default-card "very nice sound card"
Will that also change which card gets /dev/dsp0 in OSS emulation?
I only want to use two cards, but if I had three, would I be able
to specify the order of all three?
Thanks,
Toby
8:20 a.m.
On Tue, 2007-01-02 at 21:24 -0800, St wrote:
So, after rebooting many times, and answering the
nvidia
driver questions as many times, I still wonder about the
issue of card order. Right now all is ok, but I've heard
many reports of card order swapping from boot to boot. Not
so hot.
You can give every device their own card slot, regardless of the order
they are discovered in. This is an excerpt from my /etc/modprobe.conf:
alias sound-slot-0 snd-emu10k1
alias sound-slot-1 snd-cmipci
alias sound-slot-2 snd-usb-audio
alias sound-slot-3 snd-usb-audio
alias sound-slot-4 snd-usb-audio
options snd-emu10k1 index=0
options snd-cmipci index=1
options snd-usb-audio index=2,3,4 vid=0x0A4D,0x17A0,0x0c45
pid=0x0090,0x0001,0x60AF
(that's not supposed to be a line break before "pid")
The "index" options tells the driver modules which sound card slot the
devices using that driver should be loaded into, and the vid and pid
options for the USB module specify which particular USB devices
(specified by their vendor and product IDs) should be loaded into slots
2, 3, and 4 (in this case a MIDI keyboard, a microphone and a webcam).
If the keyboard is discovered first it will still get loaded into slot
2, if the emu10k1 is loaded second it will still get loaded into slot 0,
etc. Provided, of course, that no other device has already been loaded
into slots 2 or 0 - so in order for this to work you have to specify
indices for all devices you may connect. It would be better if there was
some sort of central 'device -> slot number' mapping so that modules for
new devices automatically knew that they should avoid indices 0 to 4,
but I don't think there is.
--
Lars Luthman - please encrypt any email sent to me if possible
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x04C77E2E
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
4:27 p.m.
Tobiah wrote:
But I have the drivers compiled into the kernel, not
modules, so this
would have no effect, right?
I don't think it's a good idea to have alsa modules compiled into the
kernel, at least it wasn't the last time I tried :-)
--
peace, love & harmony
Atte
http://www.atte.dk | quintet: http://www.anagrammer.dk
| compositions: http://www.atte.dk/compositions
5:59 p.m.
I don't think it's a good idea to have alsa modules compiled into the
kernel, at least it wasn't the last time I tried :-)
I've been running like that for quite a while. I don't
seem to have any problems, save this card order thing,
which as Lars pointed out could be solved if I was using
modules.
6560
days inactive
6563
days old
linux-audio-user@lists.linuxaudio.org
10 comments
8 participants
participants (8)
-
Atte André Jensen -
david -
David Stephens -
Jon H -
Lars Luthman -
St -
Tobiah
-
Vince Werber