Re: Sound porblems with Suse 10.1 and MSI Motherboard

chuckcar wrote:

Norbert Kolvenbach <noko4711@xxxxxxxxxxx> wrote in
news:ecf48e$d0i$03$1@xxxxxxxxxxxxxxxxx:

chuckcar wrote:

seems fine. Have you tried:

cat <wavefile> &>/dev/adsp ?

tried with /dev/dsp no error it simply returns after a while.
With /dev/adsp I get an error message telling me device not available
although it is there under /dev.


Sorry - someone had to read the alsa howo ;-) - that should be:

cat <wavefile> &>/dev/snd/pcm

for alsa and /dev/dsp for OSS.


noko@noko1:~> ll /dev/snd
insgesamt 0
crw-rw----+ 1 root audio 116, 7 2006-08-23 19:13 controlC0
crw-rw----+ 1 root audio 116, 6 2006-08-23 19:13 pcmC0D0c
crw-rw----+ 1 root audio 116, 5 2006-08-23 19:13 pcmC0D0p
crw-rw----+ 1 root audio 116, 4 2006-08-23 19:13 pcmC0D1c
crw-rw----+ 1 root audio 116, 3 2006-08-23 19:13 pcmC0D2p
crw-rw----+ 1 root audio 116, 8 2006-08-23 17:14 seq
crw-rw----+ 1 root audio 116, 2 2006-08-23 19:13 timer

I do cat wavefile > /dev/snd/pcmC0D0c

and get bash error: wrong inode!


you can get any howto you don't have - read them they're there for a
reason ;-) at:

http://tldp.org/docs.html#howto

the relevant ones are the alsa-HOWTO and the sound-HOWTO.


If you do a:

modprobe snd-pcm1-oss

you get *both* oss and alsa compatibility and don't have to worry about
either in theory. put that line in your/etc/rc.d/rc.modules if the file
is there - the other variation I'm unclear on maybe a little birdy would
help?


I cry for a birdy!! ;-)


when I cat > /dev/dsp I get the following status information:

noko@noko1:/proc/asound/card0/pcm0p/sub0> cat status
state: RUNNING
trigger_time: 1156256701.678412000
tstamp : 1156256705.216843000
delay : 8468
avail : 3832
avail_max : 6238
-----
hw_ptr : 169908
appl_ptr : 178376
noko@noko1>

Seems not too much unreasonable. I'm getting lost now...

Not, what I'm used to seeing. That seems to be the pci timing for the
card from alsa. There used (?) to be a proc file (I *think*
/proc/asound/sndstat) that used to list the different devices within the
sound card - i.e. midi, wave etc. and what specific hardware each used.
The alsa howto covers this. What you posted seems to be the pci timings
for the sound card itself, meaning (as the output from your cat I saked
for) that as far as linux is concerned the card is fine - true or not,
we don't know yet - not raising a bugaboo, just being neutral about it.


NoKo

--
"Careful with that VAX, Eugene!"
.

Relevant Pages

  • Re: Sound porblems with Suse 10.1 and MSI Motherboard
    ... With /dev/adsp I get an error message telling me device not available ... for alsa and /dev/dsp for OSS. ... That seems to be the pci timing for the ... sound card - i.e. midi, wave etc. and what specific hardware each used. ...
    (comp.os.linux.hardware)
  • Re: Sound porblems with Suse 10.1 and MSI Motherboard
    ... With /dev/adsp I get an error message telling me device not available ... for alsa and /dev/dsp for OSS. ... sound card - i.e. midi, wave etc. and what specific hardware each used. ... Also arts sometimes gets started, ...
    (comp.os.linux.hardware)
  • Re: alsamixer wont come up properly, cant adjust volumes
    ... I'm using one sound card, the one integrated on my asus m2n-mx motherboard. ... The only messages in the log concerning alsa say the driver has been loaded. ... I've done this in the past, but in the last two installs ... > alsa mixer wont load properly ie, the program will open but there are ...
    (Fedora)
  • Re: alsa sound card
    ... where everything really works under ALSA? ... >> cpu time. ... >can use the game port for external midi. ... and back to digital before it makes it's way through the sound card. ...
    (comp.os.linux.hardware)
  • gap in sound device numbering
    ... OSS emulation where necessary. ... The sound card is card 0 for alsa. ... since the strange midi device does not have any dsp. ...
    (Debian-User)