What works some times (but not all the time) is to set up your mixer settings EXACTLY the way you want them, and then run with root permissions:
alsactl store
First, with the exception of the application libdvdcss (or libdvdcss2, what ever its called on your PC) replace any OTHER applications from the libdvdcss repository that you just removed with a packman repository equivalent packaged application.
Then install from packman: libffmpeg0, ffmpeg0, libxvidcore4, libquicktime0 … and that should get you started with needed codecs. You can tell packman packaged versions by the ‘pm’ in the version number. Do NOT use videolan/libdvdcss repos versions of those apps. Use packman packaged versions. Also replace the Novell packaged versions of libxine1 and xine-ui with packman packaged versions of the same apps, and install phonon-backend-xine, libxine1-pulse, libxine1-gnome-vfs and libxine1-codecs.
I recall when I was first reading up on Linux in 1998, before my 1st installation of Linux. (I know, I am a bit different than anyone else. I actually read books on Linux for 3 months before I tried to install it. ) … anyway, I recall reading a few times on the web posts by users who noted while it was common in MS-Windows (win95 @ the time) to reboot to fix a problem (and hence users often rebooted and felt comfortable in rebooting at the slightest drop of a pin in MS-Windows), in Linux it was the opposite. Rebooting was rarely necessary, and to reboot often caused the biggest concern amongst Linux users. rotfl!
… that fundamental difference in the operational use of the two different operating systems is so true!
In the end, removing the other repositories, reloading the multimedia codec packages from packman, then adjusting the alsamixer cli and storing the settings fixed it.
The sound and all multimedia works fine with two caveats:
The sound is turned down in alsamixer upon bootup. I have to terminal to it and turn the sound up each time. Even when I save it (alsactl store) it won’t save the setting.
Not a deal killer, I’m already used to doing it, but it IS a pain in the tukus.
The built-i mic is scratchy no matter what I do. Again, not a deal killer, I’ll just buy an external mic, that should fix it.
Any insight as to why #1 happens and how I can fix it permanently??
Alrightalready!! C’mon cpu, you know I’m a newby!! I think I’ve done pretty well thus far. The only things bugging me shouldn’t be that hard to fix, and I’m sure I’m not the only one with this problem.
So forget the insight and speculation!!! How about a little hand (and not the opera clap either)! rotfl!
) … anyway, I recall reading a few times on the web posts by users who noted while it was common in MS-Windows (win95 @ the time) to reboot to fix a problem (and hence users often rebooted and felt comfortable in rebooting at the slightest drop of a pin in MS-Windows), in Linux it was the opposite. Rebooting was rarely necessary, and to reboot often caused the biggest concern amongst Linux users. rotfl!