Red Hat Bugzilla – Bug 66385
sndconfig with VIA VT8233 AC97 hangs
Last modified: 2013-07-02 22:06:03 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513
Description of problem:
The exact string that sndconfig returns is VIA Technologies|VT8233 AC97 Audio
Controller. This is correct (as far as i know), and is the on-board sound for
the Spacewalker KT266A motherboard. After detecting this, it says it will try to
play a sound, then it hangs trying. I hear nothing, and the output of "ps" shows
me that sox is trying to do something, but sndconfig doesn't do anything else.
^C kills it as expected. I have tried this in a terminal window under X, and
from single user mode, if that makes any difference.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Run sndconfig with the proper hardware.
Actual Results: sndconfig hangs.
Expected Results: It should either play something that i can hear, or it should
fail in some way. I would expect that it plays the sample and comes back to ask
me if i had heard it properly.
If it helps, the following three lines appear in the system log:
kernel: Via 686a audio driver 1.9.1
kernel: ac97_codec: AC97 Audio codec, id: 0x4943:0x4511 (ICE1232)
kernel: via82cxxx: board #1 at 0xE800, IRQ 5
If it *hangs*, that implies a driver issue.
In my experience, the problem might be the volume and/or the mixer settings.
That is, the sound is played but the volume (either in the mixer or in the
is too low.
If that were the case, then i would expect that sndconfig would return at some
point and ask if i had heard the sound. Certainly used to work that way.
sndconfig never returned and had to be killed with ^C
As long as we're on the topic, 2.4.18-5 now claims that the sound device is not
there, although it is onboard. sndconfig detects the sound controller, just as
it did in previous versions, but when it tries to play a sample sound, it gives
me the error:
/lib/modules/2.4.18-5/kernel/drivers/sound/via82cxxx_audio.o: init_module: No
...and further insmod errors that all stem from that first error.
*** This bug has been marked as a duplicate of 54905 ***