Results 1 to 2 of 2

Thread: alsasound needs "rcalsasound restart"

  1. #1

    Default alsasound needs "rcalsasound restart"

    Hi,

    I have a problem concerning sound in openSuSE 11.1 with KDE 4. My problem is, that it works half.

    when I restart often only amarok works. no Startsound of kde and also skype says there is no sound.

    If I only do a "rcalsasound restart" as root everthing works well. I have sounds in KDE and Skype. I also tried to add the user to audio und pulse* groups but this does not chnge anything.

    Is there an better solutions als calling "rcalsasound restart" after each restart?

    Thanks
    Martin

  2. #2
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    27,109
    Blog Entries
    40

    Default Re: alsasound needs "rcalsasound restart"

    Quote Originally Posted by klinkigt View Post
    I have a problem concerning sound in openSuSE 11.1 with KDE 4. My problem is, that it works half.

    when I restart often only amarok works. no Startsound of kde and also skype says there is no sound.

    If I only do a "rcalsasound restart" as root everthing works well. I have sounds in KDE and Skype. I also tried to add the user to audio und pulse* groups but this does not chnge anything.

    Is there an better solutions als calling "rcalsasound restart" after each restart?
    klinkigt, if it were me with these symptoms, and if I wished to understand better what was happening, what I would try to do is determine what device was using the sound driver during the various instances you describe.

    Sometimes, when one has basic sound functioning, but then it appears to stop in the middle of a session (to be restored after a reboot or restored via "rcalsasound restart") it may be because an application has seized your audio device, and the application is not sharing nor letting go the audio device. To determine what application is using one's sound device, copy and paste the following into a terminal or a konsole:
    Code:
    lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
    If one runs the above line at different times, when one's sound is working and not working, one can learn better as to what the output means, and be better able to " point one's finger " at the offending application that has seized the audio device.

    So I recommend you run that line, and copy and paste and save the output, in each case you described, ... ie
    • when everything works - boot sound, amarok, Skype
    • when only amarok works
    • after running "rcalsasound restart"
    Then compare the various outputs, to see if you can determine the offending application that may have seized the sound when your Skype struggles. Note I do not use Skype, so I can not offer any support there.

    Note that "rcalsasound restart" will typically break the hold of any devices that have inappropriately "seized" the sound device.

    Also note that for multiple applications to use the sound device at the same time, typically requires one use the ALSA API, or use Pulse Audio, where unfortunately Pulse Audio is buggy, and its use not very understood by many of us (I include myself in that category).

    There are some basic sound concepts here (in case you are curious about more details): Sound-concepts - openSUSE

    If you wanted to run "rcalsasound restart" automatically at every boot, you can put it in at the end of the /etc/init.d/boot.local file.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •