I have the problem that for working properly my soundcard needs sort of re-initialisation after every reboot (11.3, 64 bit).
I have to change a setting in the sound module of yast that causes the yast to rerun its final steps.
What is not working otherwise is audio playback from a usb TV-stick (recording is no problem, same as playing an audio/video file).
any idea what might be the problem?
if someone could tell me how to call the final steps of the sound module of yast from the command line, I could at least put that call into boot.local to avoid having to call yast.
You can also try to update alsa and maybe this will be a permanent solution. Please read the instructions and follow them carefully. I would also recommend to export the current state of your packages using yast->software management->file->export in case You will have to revert the changes. SDB:Alsa-update - openSUSE
It could be your system is sensitive to the order of sound devices, where after a regular boot your motherboard sound is sound-card-0 and your USB device is sound-card-1, and the setting you change in YaST is to reverse the order of sound devices.
Of course if you don’t tell us the “setting you change in the sound module of yast” we are forced to guess, which is not so efficient.
what I change is in fact the order of the soundcards.
I left it out on purpose in order not to mislead for the following reason:
at first, activating pulseaudio - what is required by the TV stick - also made sound work, up to the next reboot.
one soundcard is the one of the motherboard, the second is the one of the graphics card. (the TV provides no sound card)
if I change the order of the soundcards, IRRESPECTIVE OF WHAT CURENTLY IS THE PRIMARY SOUNDCARD, causes yast to run the setup and makes sound playback work.
“rcalsasound restart” makes it - THANKS!
but why is it necessary to call it after every reboot?
IMHO what your proved just now is that it is not necessary to change sound card order, and that may have had nothing to do with the problem, but rather the problem was an alsa restart was needed.
Possibly upon boot some application has seized your audio device, and the restart of alsa is necessary to free it. You could investigate this a bit more. Restart, and then use the “lsof” command to list open files in the directories where the sound device is located/accessed. You can do that by immediately after a boot (before trying to use your sound) run:
lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
note that last entry is " /dev/snd/* " and NOT "/dev/snd* ".
Record what you get (easiest to copy and paste to a text file).
Then try an application to see if sound works. If no sound, again run:
lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
and again record what you get.
Then restart alsa with: su -c ‘rcalsasound restart’
and again run:
lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
and record what you get.
Then again run an app that plays sound, and assuming sound works, while the sound is being played run:
lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
and again record what you get.
Then compare all 4. The output ‘might’ give you a hint as to what is going on.
Further to my above post, I note you have pulse audio running.
Try installing the application ‘pavucontrol’ and then run ‘pavucontrol’ such that you can access its gui when you are trying to play an audio application. Check out the pavucontrol menus. Maybe it will shed some light.
I made a new login (without reboot).
same result: tvtime produced no sound.
then, whith tvtime running, I started pavucontrol.
there I could notice that instead of “internal audio analog stereo” the graphics card audio was selected.
when I selected “internal audio analog stereo” the sound was fine!
your had the right idea.
therefore, I called the KDE multemedia module.
there the graphics card audio was at the first position.
to solve the problem, is it correct, to move arts to the first position?
alternatives would be “Jack audio connection kit” or “Esound (ESD)”.
In openSUSE-11.4 pulse audio was enabled in KDE, and I had problems myself. I found pavucontrol was quite useful in enabling me to tune away the problems. I do not know why the problems happen. I also track the Fedora forum a bit, and the sound guru’s there often recommend Fedora Gnome users install pavucontrol.