Kapil,

Can you send me the o/p of dmesg to my id?

Aditya

On 12/7/05, Kapil D. Pendse <[EMAIL PROTECTED]> wrote:
>
>
> > > I'm have trouble getting sound working on my suse 10 installation.
> > > Using onboard audio - intel D865GBF mobo.
> > > YaST detected and configured sound properly, but "test" sound of yast
> > > doesn't produce any output. Same with xmms/mplayer/xine.
> >
> > Hi,
> > Try running alsamixer and check whether the channels are muted.
> >
> > -aditya
>
> Already tried that. Master and PCM are at 100%. Those are the ones that
> usually matter. AFAIK, the others that are of importance are sound hardware
> specific channels, such as:
>
> IEC958, IEC958 Playback AC97-SPSA etc.
>  In my case, the first one, IEC958, is set to 0% and it's not adjustable.
>
> Card: Intel ICH5
> Chip: Analog Devices AD1985
> View: [Playback] Capture  All
> Item: IEC958
>
> The second one is set to 100% and is adjustable.
>
> Card: Intel ICH5
> Chip: Analog Devices AD1985
> View: [Playback] Capture  All
> Item: IEC958 Playback AC97-SPSA
>
>
> I tried fiddling with /etc/modprobe.d/sound, no luck.
> Even played with KDE sound system through KControlCenter. Tried disabling
> sound system completely, tried OSS, autodetect, ALSA (the default). No luck.
> Every time I make any changes and click on apply, it starts(/restarts) the
> sound system. Then if I click on Test Sound, nothing happens and a moment
> later a window pops up saying artsd crashed with SIGSEGV.
>
> Hmmm, seg fault?
>
> Just now I deleted /etc/modprobe.d/sound and reconfigured sound with YaST. It
> shows sound configured now but still nothing audible. It did make a small
> scratch-like noise when I clicked on save settings.
>
> After that I changed KDE sound system to "autodetect" and clicked on Apply.
> It's showing a process bar that says "restarting sound system". The bar moves
> from 0% to 100% and then loops back to 0%... this is still going on.
>
> # ps -e | grep artsd
> 8027 ?        00:00:06 artsd
> 8029 ?        00:00:00 artsd
>
> This despite doing `killall artsd` as root before starting KControlCenter. And
> I made sure that killall certainly killed the running artsd with `ps -e |
> grep artsd`.
>
> Now I don't understand why KControlCenter is starting 2 instances of artsd. I
> ran `ps -e | grep artsd` as soon as I clicked on "Apply" in control center.
> And even when the process bar was at 15% (in the 0th loop), I could see 2
> instances of artsd.
>
> Oh, setting sound system to ALSA and then applying the settings causes the
> process bar to appear only once instead of looping indefinitely, that makes
> some sense! :-(
>
> Please please someone help me out. I've been behind this thing for almost 15
> days now...
>
> Thanks and Regards,
> Kapil
>
> --
> "The Power to Imagine, is The Power to Create!"
> -TTux
> --
> ______________________________________________________________________
> Pune GNU/Linux Users Group Mailing List:      ([email protected])
> List Information:  http://plug.org.in/mailing-list/listinfo/plug-mail
> Send 'help' to [EMAIL PROTECTED] for mailing instructions.
>

--
______________________________________________________________________
Pune GNU/Linux Users Group Mailing List:      ([email protected])
List Information:  http://plug.org.in/mailing-list/listinfo/plug-mail
Send 'help' to [EMAIL PROTECTED] for mailing instructions.

Reply via email to