After installing KDE 3.2 I lost the sound, and the usual cures don't seem to help. Reinstalling via Yast2 does nothing, and alsaconf actually hangs while trying to play the sample sound. Removing the alsaconf entries from /etc/modules.conf doesn't help either. What's particularly odd is that although the problem was provoked by installing KDE 3.2, it doesn't seem to be caused by KDE 3.2. I tried booting into runlevel 3, which avoids activating KDE at all, and then ran alsaconf. Again alsaconf hung while trying to play the sample sound. One possibility is that when I ran redcarpet to install KDE 3.2, it also brought in some other package that's causing the problem. If I start at runlevel 5 and log in via kdm as a virgin user (one just created by Yast), I get: Sound server informational message Error while initializing the sound driver device: default can't be opened for playback (Device or resource busy) The sound server will continue using the null output device. Any suggestions on how to go about tracking this one down? Paul Abrahams
On Friday 06 February 2004 05.16, Paul W. Abrahams wrote:
One possibility is that when I ran redcarpet to install KDE 3.2, it also brought in some other package that's causing the problem.
Seems unlikely, unless you subscribed to the packman channel and got their alsa 1.0.2 packages, but I don't think that should matter, as I think they're backwards compatible Do you get anything in /var/log/messages? Are the sound modules getting loaded? (check with lsmod)
On Thursday 05 February 2004 11:24 pm, Anders Johansson wrote:
Do you get anything in /var/log/messages? Are the sound modules getting loaded? (check with lsmod)
Nothing in /var/log/messages, and lsmod shows: suillus:~ # lsmod Module Size Used by Not tainted snd-mixer-oss 15576 0 (autoclean) snd-via82xx 16160 0 snd-pcm 74148 0 [snd-via82xx] snd-timer 17024 0 [snd-pcm] snd-ac97-codec 45400 0 [snd-via82xx] snd-mpu401-uart 4128 0 [snd-via82xx] snd-rawmidi 15968 0 [snd-mpu401-uart] snd-seq-device 4528 0 [snd-rawmidi] snd 40388 0 [snd-mixer-oss snd-via82xx snd-pcm snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-device] What's particularly odd is that the loss of sound was provoked by the switch to KDE 3.2, but if I start my system in state 3, thus bypassing KDE, alsaconf still hangs up when trying to play its sample sound. I've tried uninstalling and reinstalling the sound card from Yast, and also running with the sound card uninstalled. I've tried removing all sound entries from /etc/modules.conf and then reinstalling the sound device, either through alsaconf or through Yast. Nothing works. This is a very frustrating problem. Paul Abrahams Paul Abrahams
On Saturday 07 February 2004 00.57, Paul W. Abrahams wrote:
What's particularly odd is that the loss of sound was provoked by the switch to KDE 3.2, but if I start my system in state 3, thus bypassing KDE, alsaconf still hangs up when trying to play its sample sound.
I don't know, it sounds very strange. I see nothing available through red carpet that could cause this. The kernel would be the immediate guess, but kernels aren't distributed through red carpet so that can't be it. You can check exactly what red carpet has installed/uninstalled on the history tab I don't suppose you ran an online update around that time, and got a new kernel through that?
On Thu, 5 Feb 2004 23:16:54 -0500
"Paul W. Abrahams"
After installing KDE 3.2 I lost the sound, ... What's particularly odd is that although the problem was provoked by installing KDE 3.2, it doesn't seem to be caused by KDE 3.2.
Strange. I am using ALSA 1.0.2 with KDE 3.2 (aRts version 1.2) and have no problems. What errors do you get in /var/log/messages when you restart ALSA? If worst comes to worst, recompile ALSA driver with the debug flag and see what addition errors it generates. Charles -- There are no threads in a.b.p.erotica, so there's no gain in using a threaded news reader. (Unknown source)
Also, I forgot to ask if you were using an older version of ALSA (0.9.x) before upgrading to 1.0.2. If yes, try downloading the ALSA driver source and run the snddevices shell script. The ALSA devices names changed sometime during the latter part of the 0.9.x series That may solve your problem. Charles -- "World domination. Fast" (By Linus Torvalds)
On Friday 06 February 2004 7:38 pm, Charles Philip Chan wrote:
Also, I forgot to ask if you were using an older version of ALSA (0.9.x) before upgrading to 1.0.2. If yes, try downloading the ALSA driver source and run the snddevices shell script. The ALSA devices names changed sometime during the latter part of the 0.9.x series That may solve your problem.
Indeed I'm running alsa-0.9.6-96, which is the latest available on the SuSE website. I'll go get the snddevices shell script. But in the meantime I did find a way to get back the sound. In the configuration for my sound card under Yast/Hardware/Sound, there's an option for support for DXS channels. It was originally set to 0 (auto). Setting it to 1 (enable), as suggested in the log messages, produced the error Feb 6 19:51:50 suillus kernel: ALSA pcm_lib.c:2155: playback write error (DMA or IRQ trouble?) But setting it to 2 (disable), miraculously, has restored the sound!!!! I suppose I should heave a sigh of relief and rejoice in my good fortune in having the sound back. But some puzzling questions remain: 1. Why did the switch to KDE 3.2 provoke the problem? 2. What are the DXS channels? Am I likely to miss them? 3. Why did reinstalling the sound card driver (VIA 8235) cause the DXS value to be set to 0 rather than 2? Or was it 0 all along, but something else happened to cause 0 not to work? Perhaps someone here can answer some or all of these questions. Paul Abrahams
participants (3)
-
Anders Johansson
-
Charles Philip Chan
-
Paul W. Abrahams