On Sun, 2005-09-11 at 07:28 -0700, Mark Knecht wrote:
> Hi Nick,
>    I know it's unlikely, but one other possibility is the sound card
> itself. A number of my RME cards (Hammerfall, HDSP 9652) actually have
> no mixer elements, meaning they cannot be controlled by Alsamixer,

alsamixer and alsamixer-gui both work fine.

>  and
> so I get the same messages even though the cards work fine with
> mplayer, etc. I somehow doubt this is your case but it doesn't hurt to
> point out that this message can be normal.
> 
>    Are you attempting to run the Gnome sound server? If there a
> conflict happening there?

I dunno, is that the one called esd? mplayer -ao esd works.

> 
>    What sound hardware are you running?
> 
> lspci
> cat /proc/asound/cards
> 

some poxy thing onboard the motherboard:

0 [rev50          ]: VIA686A - VIA 82C686A/B rev50
                     VIA 82C686A/B rev50 with ICE1232 at 0xcc00, irq 10

I  am 95% sure that gnome-volume control worked at some stage.



> Good luck,
> Mark
> 
> On 9/10/05, Nick Rout <[EMAIL PROTECTED]> wrote:
> > When I log into gnome I get a dialog with the following message:
> > 
> > "Sorry, no mixer elements and/or devices found"
> > 
> > Advcie from google and forums.g.o seems to point to the following likely
> > solutions:
> > 
> > 1. make sure user has ability to do audio - yes I can, and everything I
> > run in gnome produces audio output when it should (mplayer, xmms,
> > mpg123, xine, whatever)
> > 
> > 2. run gst-register-0.8 - done it, more than once. Doesn't complain
> > about any problems, but makes no difference even after a reboot.
> > 
> > Thats about a summary of the suggested fixes and the results. I figured
> > that the error seemed to be on running gnome-volume-control, so when i
> > run it from an xterm I get the following:
> > 
> > [EMAIL PROTECTED] /home/torrents/nick $ gnome-volume-control
> > 
> > ** (gnome-volume-control:19921): CRITICAL **: how to remove plugins?
> > 
> > (gnome-volume-control:19921): GStreamer-CRITICAL **: Factory for
> > `ossmixer' has no type. This probably means the plugin wasn't found
> > because the registry is broken. The plugin GStreamer was looking for is
> > named 'ossaudio' and is expected in file
> > '/usr/lib/gstreamer-0.8/libgstossaudio.so'. The registry for this plugin
> > is located at '/var/lib/cache/gstreamer-0.8/registry.xml'
> > 
> > ** (gnome-volume-control:19921): CRITICAL **: how to remove plugins?
> > 
> > (gnome-volume-control:19921): GStreamer-CRITICAL **: Factory for
> > `alsamixer' has no type. This probably means the plugin wasn't found
> > because the registry is broken. The plugin GStreamer was looking for is
> > named 'alsa' and is expected in file
> > '/usr/lib/gstreamer-0.8/libgstalsa.so'. The registry for this plugin is
> > located at '/var/lib/cache/gstreamer-0.8/registry.xml'
> > 
> > 
> > OK well it looks like something is missing. I though gst-register-0.8
> > was supposed to sort all that out.
> > 
> > What am I missing or what do I do to fix this? Can I safely
> > delete /var/lib/cache/gstreamer-0.8/registry.xml and re-run the register
> > program and see if that makes a difference? Or will i break something?
> > 
> > 
> > As sound is in fact working in all apps I use, its not such a worry,
> > just a sign that something is broken, and if something is broken it may
> > get worse down the track.
> > --
> > Nick Rout <[EMAIL PROTECTED]>
> > 
> > --
> > [email protected] mailing list
> > 
> >
> 
-- 
Nick Rout <[EMAIL PROTECTED]>

-- 
[email protected] mailing list

Reply via email to