Re: [suse-sparc] ALSA doesn't work on Ultra 10

From: Aurelian Lavric (aurelian.lavric@inria.fr)
Date: Tue Mar 27 2001 - 01:22:27 PST

  • Next message: Walker, John: "Hello out there"

    From: Aurelian Lavric <aurelian.lavric@inria.fr>
    Date: Tue, 27 Mar 2001 11:22:27 +0200
    Message-Id: <01032711222700.01424@bjork.inria.fr>
    Subject: Re: [suse-sparc] ALSA doesn't work on Ultra 10
    

    On Tuesday 27 March 2001 08:39, Peter Becker wrote:
    > Aurelian Lavric wrote:
    > > On my computer I got some problems with KDE and sound card with Crystal
    > > chipset. The workaround can be to give in a terminal (afther the KDE
    > > started) a command like "audioctl -w play.pause=0". That works for me.
    >
    > For me, too. Thanks a lot.
    >
    > > If it works for
    > > you also, I suggest you to make a script (I named it artsplay_pause)
    > > where to insert the given command and a command like "artsplay $@". Use
    > > this script as the program to play all the sounds of the system in the
    > > Kde notifier setup (in Preferences/Look&Feel/System Notification/Use
    > > external player). The problem is that each time the arts daemon get to
    > > sleep state you got to rewrite the pause=0 command. But if you use the
    > > given script you can just generate a system sound (like the bell in the
    > > kterm generated by the TAB if you use bash) and the sound comes alive.
    > >
    > > This was a problem on my computer since KDE1.1 related to the arts daemon
    > > on sparc-linux. I don't know if that's your problem also, but in all
    > > cases you should try to see if the artsd process is running by a simple
    > > ps command, or see the output of the audioctl -a. If the sounds doesn't
    > > come probably you should try also to make a rmmod on the sound driver
    > > module and insmod it again (that will reset the chipset if a play.error=1
    > > is displayed by audioctl, for me it works even if the error flag is set).
    >
    > Isn't there some place to file a bug report for this? Sound as if
    > someone who knows the code has to change two or three lines ;-)
    >
    > The problem left for me is that the KDE mixer doesn't work well.
    > Sometimes faders move with other faders (e.g. moving the balance fader
    > changes the volume, too) and I wasn't able to do this: "audioctl -w
    > play.port=2" without using the command line, but maybe I just miss
    > something. At one time I wasn't even able to get any sound again, the
    > programs were happily playing, but nothing came out of the speaker or
    > headphones. Even killing and restarting the daemon process didn't help
    > (and the modules were busy) -- I had to reboot the machine.

    Well, usually killing the sound daemons (with "killall -9 artsd") and then
    removing and reinserting the sound module ("rmmod cs****" and
    "modprobe/insmod cs****" I don't remember the number as I write this email
    from a i386 system, the sparc one is at home) that should do the job.

    On the 2.2.* kernels the mixer interface is still buggy (the sound driver for
    the sun systems is still in experimental state). Instead in the 2.4.* ones
    the mixer works a little better, but in this one there's another problem
    related to the short sounds, something like the click sound, that doesn't
    close the sound card, leaving it in a bad state (for this one usually I use
    the mpg123 player to restore the state, as to not remove/reinsert the sound
    module), and also there's a problem opening the sound card from some
    applications at a different output frequency than 44.1 KHz. Usually for the
    two kernels the use of a sound daemon can solve the problems. For instance in
    2.2.* kernels I change the volume using the esd libraries (that's working
    well even when the sound daemon is not started) - by using the xmms player
    for example. For the artsd daemon its arts control process (found in
    multimedia menu) works very well for me (I use now KDE2.1). As to change the
    output I think that the best solution remains the audioctl application. (well
    you can use it also to change the volume by setting play.gain=[0..254], on my
    system, when I use 2.2.* kernels, the 255 value blocks the sound card). I
    don't remember exactly if in 2.4.* kernels the mixer was allowing the change
    of the output port. On my computer I use some scripts to save and restore the
    sound card state at the boot/shutdown time, so I don't have to use too often
    the mixer. I use only the sound daemon's mixer to adjust the volume.

    >
    > Any further hints on this? Otherwise it is not a real issue since your
    > last mail solved the most important problems.
    >
    > Thanks again,
    > Peter

    With pleasure,
        Aurelian



    This archive was generated by hypermail 2.1.0 : Wed Jun 06 2001 - 11:08:54 PDT