Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wenn <prismatic7@bigpond.com>
To: Alsa-Announce List <alsa-announcet@lists.sourceforge.net>,
	Alsa-Devel List <alsa-devel@lists.sourceforge.net>
Subject: Terratec DMX (Newbie)
Date: Mon, 25 Feb 2002 13:33:05 +1100	[thread overview]
Message-ID: <3C79A261.7030704@bigpond.com> (raw)

Hey there.

Soory about the cross-posting, but I'm hoping someone can give me a 
couple of pointers. I have a Terratec SoundSystem DMX (that's a Maestro 
2E card) which I can't get fired up using either alsaconf or by hand 
(I'm running the debian packages of alsa 0.9.0beta10) When I configure 
the card in alsaconf, I get through the first part ok (though I'm 
guessing at the values for configuration), until it's time to load up 
the mixer progs, at which point it crashes out saying:

# Loading driver:
# Starting ALSA sound driver (version 0.9.0beta10): no sound cards
# defined.
# Setting the PCM volume to 100% and the Master output volume tp 50%
# amixer: Mixer attach default error: No such file or directory
# Could not initialize the mixer, the card was probably not detected
# correctly.

If I do the configuration by hand in /etc/modules.conf, I get an error 
saying that 'parm_snd_pcm_channels_p' and 'parm_snd_pcm_channels_c' do 
not exist (sorry, I don't have the exact output to hand)

If someone could mail me the correct values and a quick how-to on 
getting the damn thing fired up, I'd much appreciate it.

Thanks
Chris



_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

             reply	other threads:[~2002-02-25  2:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25  2:33 Chris Wenn [this message]
2002-02-25 12:07 ` Terratec DMX (Newbie) Takashi Iwai

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=3C79A261.7030704@bigpond.com \
    --to=prismatic7@bigpond.com \
    --cc=alsa-announcet@lists.sourceforge.net \
    --cc=alsa-devel@lists.sourceforge.net \
    /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