Re: Sound porblems with Suse 10.1 and MSI Motherboard
- From: Norbert Kolvenbach <noko4711@xxxxxxxxxxx>
- Date: Fri, 01 Sep 2006 21:46:27 +0200
chuckcar wrote:
Norbert Kolvenbach <noko4711@xxxxxxxxxxx> wrote inSo --- to get on with the story: I found partial solution.
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.
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?
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.
I went to runlevel 3 and did alsaconf and alsamixer settings, and guess
what? - BIG soud!! Doing startx and starting up KDE: No sound. I found that
after starting kde, all mixer settings where set back to a default. Result:
No sound. Also arts sometimes gets started, sometimes not. If I try to
reconfigure soundsystem in kde, restart of arts starts to loop endlessly.
However, cutting a long story short: hardware is ok, drivers and modules are
ok, dammed desktop application stuff lets me down. Any trick to reliably
start arts and reliably save mixer settings?
nuff today, cheers,
NoKo
--
"Careful with that VAX, Eugene!"
.
- Prev by Date: ext3 Volume Labels
- Next by Date: Re: "Forever" fsck?
- Previous by thread: ext3 Volume Labels
- Next by thread: Anyone get an All-in-Wonder 2006 working as TV?
- Index(es):
Relevant Pages
|
|
