https://bugzilla.novell.com/show_bug.cgi?id=471265
User andrescimmarusti@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=471265#c9
Andres Cimmarusti changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|andrescimmarusti@yahoo.com |
--- Comment #9 from Andres Cimmarusti 2009-03-02 08:55:22 MST ---
I tried KDE4.1 and got rid off PulseAudio completely, but sometimes the
starting sound (when booting up) didn't sound at all, or got cut off abruptly.
The sound when logging off sometimes did not play and a message appeared: that
there was something wrong with ATI IXP rev2 with unknown codec device...
I admit that I let the problem rest for a while. Mainly because I had work to
do!. But I have come back to it. I'm once again running GNOME with full
pulseaudio support. I think I have a better idea of what is going on.
I did what you suggested. I killed pulseaudio and:
$ killall -9 pulseaudio
$ aplay -Dplug -vv /usr/share/sounds/alsa/test.wav
ALSA lib pcm.c:6814:(snd_pcm_slave_conf) missing field pcm
aplay: main:590: audio open error: Invalid argument
$ aplay -Dplug:dmix -vv /usr/share/sounds/alsa/test.wav
Playing WAVE '/usr/share/sounds/alsa/test.wav' : Signed 16 bit Little Endian,
Rate 44100 Hz, Stereo
Plug PCM: Rate conversion PCM (48000, sformat=S32_LE)
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 44100
exact rate : 44100 (44100/1)
msbits : 16
buffer_size : 7526
period_size : 940
period_time : 21333
tstamp_mode : NONE
period_step : 1
avail_min : 940
period_event : 0
start_threshold : 7526
stop_threshold : 7526
silence_threshold: 0
silence_size : 0
boundary : 986447872
Slave: Direct Stream Mixing PCM
Its setup is:
stream : PLAYBACK
access : MMAP_INTERLEAVED
format : S32_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 32
buffer_size : 8192
period_size : 1024
period_time : 21333
tstamp_mode : NONE
period_step : 1
avail_min : 1024
period_event : 0
start_threshold : 8192
stop_threshold : 8192
silence_threshold: 0
silence_size : 0
boundary : 1073741824
Hardware PCM card 0 'ATI IXP' device 0 subdevice 0
Its setup is:
stream : PLAYBACK
access : MMAP_INTERLEAVED
format : S32_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 32
buffer_size : 8192
period_size : 1024
period_time : 21333
tstamp_mode : ENABLE
period_step : 1
avail_min : 1024
period_event : 0
start_threshold : 1
stop_threshold : 1073741824
silence_threshold: 0
silence_size : 1073741824
boundary : 1073741824
(the playback was flawless for this one) I ran it in two terminals and they
worked well without any problems nor interference.
I've been doing some searching and in the forums and in pulseaudio's website I
came across the command:
$ grep -i pulse /var/log/messages
Mar 1 00:54:17 suse-linux pulseaudio[8998]: main.c: High-priority scheduling
enabled in configuration but not allowed by policy.
Mar 1 00:54:17 suse-linux pulseaudio[8998]: core-util.c: setpriority():
Permission denied
Mar 1 00:54:17 suse-linux pulseaudio[8998]: ltdl-bind-now.c: Failed to find
original dlopen loader.Mar 1 01:47:18 suse-linux pulseaudio[3452]:
module-alsa-sink.c: Increasing wakeup watermark to 36.75 ms
Mar 1 01:52:08 suse-linux pulseaudio[3452]: module-alsa-sink.c: Increasing
wakeup watermark to 34.00 ms
Mar 1 01:54:47 suse-linux pulseaudio[3452]: module-alsa-sink.c: Increasing
wakeup watermark to 68.00 ms
Mar 1 02:13:09 suse-linux pulseaudio[3452]: module-alsa-sink.c: Increasing
wakeup watermark to 136.00 ms
Mar 1 02:24:58 suse-linux pulseaudio[3452]: module-alsa-source.c: Your kernel
driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which
makes no sense.
(this is only a fraction of the output, however, the rest seem ok and it loops
over and over)
What concerns me is the last line. In the pulseaudio website they claim that
there are some alsa drivers that have problems. Could atiixp be one? or perhaps
just a bit, regarding the volume, or so it would seem.
Andres
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.