wheezy and Sound

Jude DaShiell jdashiel at shellworld.net
Mon Apr 23 22:08:52 UTC 2012

Certain things need to be disabled in mplayer configuration for it to 
work half decently.  I think when I last had it working I saved my 
configuration file to a zip file and may be able to dig that up again.  
For one thing, I have video set to null and lirc and joystick and mouse 
are also disabled.  I did get vlc working too, but I don't normally push 
beyond c.l.i. since so much in G.U.I. works so poorly.  I think when I 
did anything with the mixer, I used rexima and adjusted things and then 
saved everything with alsactl store.  The alsaconfig script that used to 
be there so far as I can find out is now gone.  That helped square 
things away nicely while available.  Probably one of the biggest 
problems with alsa is udev and udev certainly misconfigured this system 
to the extent that a whole slew of alsa errrors happen with each login.  
Pulseaudio though may be helping this mess some too.  The jackd server 
is figured to be present and when it can't be found that also generates 
its own alsa errors.

On Mon, 23 Apr 2012, Martin McCormick wrote:

> 	Has anybody been experimenting with wheezy and the new
> speakup-enabled kernel?
> The system I am using for these tests is a 2004-era
> Pentium3 with a bit more than 1 gigabyte of RAM and a 2.7-GHZ
> processor so it should be ready to rock and roll when I get a
> good system on it. It refuses to generate any system sounds or
> speech in any ubuntu version since version 9 and that was gnome
> with frequent crashes so I tried the wheezy netinst ISO image
> from a few weeks ago and was pleasantly surprised to get speakup
> to start every time so things are improving.
> 	I installed wheezy and am able to get a CLI session with
> speakup but the audio system is still in shreds. If I try to run
> amixer, the output is a skimpy couple of lines unless you count
> the spew of errors related to configuration lines and modules
> that protest seemingly everything except the price of tea.
> mplayer appears to start but there is no sound and speakup is
> dead afterwards so it not only won't play but kills speakup
> which is the only audio working.
> 	This is not my only system so the world isn't coming to
> an end at my house, but I am wondering if I shouldn't just blow
> it all away and re install as wheezy is still very young.
> 	If I can get normal audio such as mplayer to start
> working without loosing speakup and maybe even get speakup to
> work while in gnome, I will feel hopeful but right now except
> for the normal command shell, the things related to audio are
> still hurting.
> 	If I allow gdm3 to start, that also kills speakup. I can
> get speakup back that time by using ssh to log in from another
> system and then stopping gpm3. On the actual console, I must go
> to another console and then back to the first one and I have
> speakup back which, of course, is not what we normally want to
> happen.
> 	My question is whether others have had sound trouble
> with Debian wheezy when also using speakup.
> Martin
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

Jude <jdashiel-at-shellworld-dot-net>

More information about the Blinux-list mailing list