[linux-audio-user] RME Hammerfall setup difficulty

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



	        Hello all.  I have recently installed Debian and compiled 2.6.0-9test for a new Hammerfall digi9652 card I purchased.  I'm having a very difficult time getting alsa to recognize the card and am hoping someone here might have some ideas.

The most damning symptom is that cat /proc/asound/cards gives only: ---no soundcards---

Running aplay phone.wav (as root and reg users) gives the following error:

	aplay: main:484: audio open error: No such device

And trying to start alsamixer (as root and reg user) gives:

        alsamixer: function snd_ctl_open failed for default: No such device


        I have heard that some professional soundcards do not have hardware mixers.  The user's manual for the Hammerfall digi9652 doesn't say anything about a hardware mixer so this could be the case for this card.
        I have pasted background information below that I hope might be helpful.   Thank you in advance for any advice you might provide.

        Kris Bergstrom
        Los Angeles, CA


SYSTEM

uname -r

  2.6.0-test9
  I checked all the dependencies of the kernel before compiling and they were fine.  I compiled the kernel without error.

soundcard:  RME Hammerfall digi9652


ALSA RELATED

dpkg -l | grep alsa

  ii  alsa-base   0.9.6-5  ALSA sound driver common files
  ii  alsa-utils  0.9.6-1  Advanced Linux Sound Architecture (utils)
  ii  alsaconf    0.9.6-5  ALSA configuration generato


more /etc/modprobe.d/alsa

  ### DEBCONF MAGIC
# This file was automatically generated by alsa-base's debconf stuff
alias char-major-116 snd
alias char-major-14 soundcore
options snd major=116 cards_limit=4
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
alias snd-card-0 snd-rme9652
alias snd-slot-0 snd-card-0
alias sound-slot-0 snd-slot-0


lsmod:

Module                  Size  Used by
snd_seq_oss            34048  0 
snd_seq_midi_event      7936  1 snd_seq_oss
snd_seq                54160  4 snd_seq_oss,snd_seq_midi_event
snd_seq_device          8200  2 snd_seq_oss,snd_seq
snd_pcm_oss            51876  0 
snd_mixer_oss          18944  1 snd_pcm_oss
snd_rme9652            27972  0 
snd_pcm                96292  2 snd_pcm_oss,snd_rme9652
snd_page_alloc         11780  2 snd_rme9652,snd_pcm
snd_timer              25220  2 snd_seq,snd_pcm
snd                    48996  9 snd_seq_oss,snd_seq_midi_event,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_rme9652,snd_pcm,snd_timer
soundcore               9152  1 snd
8139too                20736  0 
mii                     5248  1 8139too
crc32                   4608  1 8139too
af_packet              16904  2 


	In case it's of use: I accidentally ran ./snddevices when trying to debug the problem.  I now think that one needn't do that with newer versions of alsa.  If that were causing problems, I'd assume it would be a problem of only being able to run a program as root but I could certainly be wrong.


-- 
H5n9d0+5

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux