[SOLVED] No sound after start-up?

J_Szucs · 09-17-2010, 01:13 AM

I have a default OpenSuse 11.3 system with KDE4 and alsa and an Asrock 4coredual Sata2 motherboard with intergrated audio.

I configured audio by yast2 after installation of the system, and it was working. But: anytime I re-start the system, a message pops up after start-up, asking if I really want to remove audio device this and that, and no matter what I choose, there will be no sound.

I can only get sound again by:
- running yast2,
- deleting the audio device configured,
- adding the same device, and setting the volumes again.

It is rather time consuming to manually re-configure (remove and add) audio after each system start-up.

Another issue: there is absolutely no way to configure skype to be able to use the microphone input. What I speak into the microphone it goes to the loudspeakers (connected to the front speaker output), but never to skype.
The only way to get skype capture mic input is to configure the front speaker as a microphone input device is skype, in which case skype captures all sounds that go to the loudspeakers, but in this case sound is overly distorted.
Sometimes muting channels other than Mic and Master in kmix does not work either.

Is there a way to get a working audio in today's developped linux distributions, especially SuSE 11.3, or that is the past, like convenient file managers and useable desktop?

How to solve this sound issue?

Peacedog · 09-17-2010, 07:45 PM

Hi J_Szucs, Welcome to LQ. Please post the output from the following:

Code:

# lspci -v | grep Audio
# lsmod
# cat /proc/asound/card0/codec#* | grep Codec

Armed with that information, have a look at

Code:

/usr/src/linux/Documentation/sound/alsa/HD-Audio-Models.txt

Good luck. ;-)

J_Szucs · 09-25-2010, 03:09 PM

It turned out to be a hardware problem: there was a random, intermittent short-circuit in one channel of the jack connector plugged into line out, that made the audio device instable. (When the audio device has shut down itself because of the short-circuit, yast2 was able to "revive it" for some time.)