5 Aug
2004
5 Aug
'04
10:11 a.m.
Hi,
Maybe your problem is, that via onboard is loaded before sb live.
Then via onboard audio will be /dev/dsp0 and sblive /dev/dsp1
Same is for ALSA. Via will be first and default soundcard.
Could you send my your modules.conf ??
There should be what sound driver loads and in what order.
Also for midi playback on sb live is ALSA (it contains hardware midi
synth - i think, this is better as timidity).
Peter Zubaj
____________________________________
http://www.pobox.sk/ - spolahliva a bezpecna prevadzka
5 Aug
5 Aug
12:16 p.m.
New subject: [linux-audio-user] sound on debian 2.4.26
>>>> "Peter" == Peter Zubaj
<pzad(a)pobox.sk> writes:
Peter> Maybe your problem is, that via onboard is loaded before sb live.
I seem to have managed to get rid of the via stuff.
Peter> Could you send my your modules.conf ??
Peter> There should be what sound driver loads and in what order.
Peter> Also for midi playback on sb live is ALSA (it contains hardware midi
Peter> synth - i think, this is better as timidity).
I'll try it if I ever get anything working.
Thanks,
--
Laura (mailto:lconrad@laymusic.org , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
1:22 p.m.
New subject: [linux-audio-user] sound on debian 2.4.26
On Thu, Aug 05, 2004 at 10:01:24AM -0400, Laura Conrad wrote:
Hi Laura,
I am not a debian user, but I see your "modules.conf":
you have 2 sounds devices in the slot-0 (the first).
alias snd-card-0 snd-via82xx
alias sound-slot-0 snd-via82xx
alias snd-card-0 snd-emu10k1
alias sound-slot-0 snd-emu10k1
This succeeds when run more times the script "alsaconf".
If you do not mean to use the "via" device
comments (#) (or delete) at all the first text block written from alsaconf (all regarding
"via")
else
change, in the text block regarding "emu10k1",
snd-card-0 in snd-card-1
sound-slot-0 in sound-slot-1
After if you decide to configure both the cards
remembers that you must run "alsamixer" with the relative card option (to the
card that you have attacked to your amplifier) "alsamixer -c <which card>"
(otherwise you can regulate the volumes of the card that you are not using)
run "alsamixer -help" before.
Remembers that in order to use the second card you will have to
always make reference to the card number 1.
when the audio part of alsa is working and you start to configure the midi
I suggest you to read this:
http://www.tldp.org/HOWTO/MIDI-HOWTO-10.html by Frank Barknecht
bye,
--
Lazzaro
>>>> "Peter" == Peter Zubaj <pzad(a)pobox.sk> writes:
Peter> Maybe your problem is, that via onboard is loaded before sb live.
I seem to have managed to get rid of the via stuff.
Peter> Could you send my your modules.conf ??
Peter> There should be what sound driver loads and in what order.
3:03 p.m.
New subject: [linux-audio-user] sound on debian 2.4.26
Thanks. I got modules.conf and modutils/alsa-base looking a little
saner and then tried rebooting.
I ended up with both the alsa and the oss modules loaded. Does anyone
have any idea why the oss modules are loading? They certainly aren't
anywhere in either modules.conf or modutils/*.
I still have the depmod errors when I run update-modules, but this
message suggests that those aren't my problem:
<http://lists.debian.org/debian-user/2004/08/msg00039.html>
I'm starting to be good at removing all the sound-related modules.
When I do that, and then run "/etc/init.d/alsa start", here are the
modules I end up with:
snd-emu10k1 75336 1 (autoclean)
snd-pcm-oss 39464 1 (autoclean)
snd-mixer-oss 13848 0 (autoclean) [snd-pcm-oss]
snd-pcm 61124 0 (autoclean) [snd-emu10k1 snd-pcm-oss]
snd-timer 14532 0 (autoclean) [snd-pcm]
snd-hwdep 5248 0 (autoclean) [snd-emu10k1]
snd-util-mem 1264 0 (autoclean) [snd-emu10k1]
snd-ac97-codec 55580 0 (autoclean) [snd-emu10k1]
snd-rawmidi 13504 0 (autoclean) [snd-emu10k1]
snd-seq-device 4160 0 (autoclean) [snd-emu10k1 snd-rawmidi]
snd 33508 0 (autoclean) [snd-emu10k1 snd-pcm-oss snd-mixer-oss
snd-pcm snd-timer snd-hwdep snd-util-mem snd-ac97-codec snd-rawmidi snd-seq-device]
soundcore 3940 6 (autoclean) [snd]
Does this look right? soundcore has the same name as an oss driver, I
think. Is there any chance I'm loading the wrong one?
When I run timidity on a MIDI file, either from my own account or from
root, it looks like it thinks it's playing, and I get no error
messages as a user. I have unplugged a usb device and removed its
module, and this gets rid of the messages about sharing IRQ's that
were showing up in /var/log/messages, so there are now no error
messages anywhere that I know about.
Is LINUX going overboard trying to look like windows? It used to be
you could find log files with error messages when something didn't
work. Not that you could always understand the error messages, but
they gave you somewhere to start with google or a mailing list like
this.
--
Laura (mailto:lconrad@laymusic.org , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
3:44 p.m.
New subject: [linux-audio-user] sound on debian 2.4.26
On Thu, Aug 05, 2004 at 12:48:35PM -0400, Laura Conrad wrote:
I ended up with both the alsa and the oss modules loaded. Does anyone
have any idea why the oss modules are loading? They certainly aren't
anywhere in either modules.conf or modutils/*.
/etc/modules maybe? That file specifies what modules to load. You could also
try to move the modules in question out of the way (or even delete), same
goes for the ones that give you depmod errors.
When I do that, and then run "/etc/init.d/alsa
start", here are the
modules I end up with:
snd-emu10k1 75336 1 (autoclean)
snd-pcm-oss 39464 1 (autoclean)
snd-mixer-oss 13848 0 (autoclean) [snd-pcm-oss]
snd-pcm 61124 0 (autoclean) [snd-emu10k1 snd-pcm-oss]
snd-timer 14532 0 (autoclean) [snd-pcm]
snd-hwdep 5248 0 (autoclean) [snd-emu10k1]
snd-util-mem 1264 0 (autoclean) [snd-emu10k1]
snd-ac97-codec 55580 0 (autoclean) [snd-emu10k1]
snd-rawmidi 13504 0 (autoclean) [snd-emu10k1]
snd-seq-device 4160 0 (autoclean) [snd-emu10k1 snd-rawmidi]
snd 33508 0 (autoclean) [snd-emu10k1 snd-pcm-oss snd-mixer-oss
snd-pcm snd-timer snd-hwdep snd-util-mem snd-ac97-codec snd-rawmidi snd-seq-device]
soundcore 3940 6 (autoclean) [snd]
Does this look right? soundcore has the same name as an oss driver, I
think. Is there any chance I'm loading the wrong one?
No, soundcore ist just the generic sound support module, it is the same for
ALSA and OSS. Otherwise it all looks good to me. Just for comparison, here is
what 'lsmod | grep snd' gives me for my onboard Via:
snd_pcm_oss 53800 0
snd_mixer_oss 19712 1 snd_pcm_oss
snd_via82xx 29028 1
snd_ac97_codec 68868 1 snd_via82xx
snd_pcm 94756 2 snd_pcm_oss,snd_via82xx
snd_timer 24452 1 snd_pcm
snd_page_alloc 11720 2 snd_via82xx,snd_pcm
snd_mpu401_uart 7616 1 snd_via82xx
snd_rawmidi 24576 1 snd_mpu401_uart
snd_seq_device 8264 1 snd_rawmidi
snd 55268 15
snd_pcm_oss,snd_mixer_oss,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 9824 1 snd
gameport 4608 2 snd_via82xx,grip
When I run timidity on a MIDI file, either from my own
account or from
root, it looks like it thinks it's playing, and I get no error
messages as a user. I have unplugged a usb device and removed its
module, and this gets rid of the messages about sharing IRQ's that
were showing up in /var/log/messages, so there are now no error
messages anywhere that I know about.
Run alsamixer again and make sure that the channels are turned up AND unmuted
(press 'm' to toggle).
cheers,
Christian
--
"Somewhere in Texas... a village is missing its idiot."
6:15 p.m.
New subject: [linux-audio-user] sound on debian 2.4.26
Thanks to everybody who helped. The last problem I fixed was that
the speakers were plugged into the mike in instead of the line out
jack. (Not the original problem -- I'd been playing with that a lot
recently.)
I'm sure lots of the other problems were necessary to fix, too.
--
Laura (mailto:lconrad@laymusic.org , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
6:52 p.m.
New subject: [linux-audio-user] sound on debian 2.4.26
Laura Conrad wrote:
Thanks to everybody who helped. The last problem I
fixed was that
the speakers were plugged into the mike in instead of the line out
jack. (Not the original problem -- I'd been playing with that a lot
recently.)
As if no one else on this list has ever plugged things into the wrong
jacks before... :-P I spent quite a while recently trying to diagnose
MIDI/Jack transport issues only to discover that the corresponding
channels for my MIDI devices on my outboard mixer had their MUTE buttons
pushed in.
-- Brett
--
Rule of Feline Frustration:
When your cat has fallen asleep on your lap and looks utterly
content and adorable, you will suddenly have to go to the
bathroom.
7547
days inactive
7547
days old
linux-audio-user@lists.linuxaudio.org
6 comments
5 participants
participants (5)
-
Brett W. McCoy -
Christian Henz -
Laura Conrad -
Lazzaro N. Ciccolella -
Peter Zubaj