Re: No sound on new Wheezy system
On Sat, 2012-12-01 at 00:57 -0800, Marc Shapiro wrote:
> On 12/01/2012 12:47 AM, Marc Shapiro wrote:
> > I have a newly installed Wheezy system on a freshly built AMD64 system
> > with a Gigabyte GA-970A-DS3 motherboard with built-in sound. Aptitude
> > shows that alsa-utils is installed. Jack and pulseaudio are not
> > installed. I also just installed sox. If I run 'play filename' then
> > play runs and displays the file info and shows its progress through
> > the file. Unfortunately the is no sound from the speakers. I have
> > tried to run alsamixer to verify that the sound is not muted and the
> > volume is sufficiently high. Unfortunately, running alsamixer with no
> > arguments yields:
> >
> > cannot load mixer controls: Invalid argument
> >
> > I have not passed any arguments on the command line and none should be
> > required. How can it say that there is an invalid argument? I have
> > tried running both 'play' and 'alsamixer' as a normal user and as root.
> >
> > When I run lspci, it shows:
> >
> > 01:00.1 Audio device: ATI Technologies Inc Manhattan HDMI Audio
> > [Mobility Radeon HD 5000 Series]
> >
> > What else should I check? What other output would help diagnose this
> > problem. I am used to sound on Debian "just working" so I am not sure
> > what to look for when it doesn't.
> >
> > Marc
> Sorry about replying to my own post, but...
>
> I am using LXDE as my DE. I added the volume control to my panel and
> verified that it is NOT muted. But the sound is all the way down and
> will not let me increase it. Something must be misconfigured, but I
> don't know what. Please help!
>
> Marc
>
>
http://www.google.de/#hl=de&tbo=d&output=search&sclient=psy-ab&q=linux
+driver+ATI+Technologies+Inc+Manhattan+HDMI+Audio+&oq=linux+driver+ATI
+Technologies+Inc+Manhattan+HDMI+Audio
+&gs_l=hp.3...1042.4770.0.5167.14.14.0.0.0.0.161.1485.8j6.14.0.crnk_cprob..0.0...1.1.W_sqV5aw8Vg&pbx=1&bav=on.2,or.r_gc.r_pw.r_qf.&fp=fc6f9251b130aa44&bpcl=39314241&biw=1152&bih=729
I have a visitor at the moment, so no time right now, but it might be a
driver issue. perhaps you need to get another version of ALSA.
Hth,
Ralf
Reply to: