This bug has to do with properly configuring ALSA in the
/etc/mplayer/mplayer.conf file. An easy work-around for some computers
is to use the setting:
ao = pulse
in the "Audio Settings" portion of the conf file.
--
[AO_ALSA] Unable to find simple control 'PCM'
https://bugs.launchpad.net/bugs/27
*** This bug is a duplicate of bug 104125 ***
https://bugs.launchpad.net/bugs/104125
I've got a similar problem too. My motherboard is an Asus a7n8x also. 2.6.20-13
was fine, but going to -14 gave me an error when mounting my IDE drive and one
of my SATA drives. Very strange that it would af
I've got a possibly related problem on my computer. After a suspend to
resume, my Prism54 mPCI card changes from /dev/eth2 to /dev/eth1.
This is interesting for several reasons:
Why doesn't it assign to /dev/eth1 on boot?
Why does the card act differently (often requiring an ifdown/ifup to reconne
I've got the same problem here. Onboard audio (VIA VT1708S) detects
fine, but my PCI board (CMedia 8738-based) generates a bunch of profiles
that don't seem to work as one would expect.
I can confirm that the ALSA mixer (gnome-alsamixer) sees and controls
the hardware properly, but gnome-volume-co
