audacious, mcs from -current
hi all,
I am running slack-11, 2.6.19.1 #2 in my sig. With the death of xmms imminent decided to install audacious & mcs from -current. my problem: Code:
perry@phargrave:/usr/local/src$ audacious& 1) is there great risk by upgrading libcurl to -current also? 2) anyone know that the alsa problem is about? admittedly i really never listen to music on this lappy... 3) would it be easier to just compile audacious for myself? (only problem is no libmcs in slack-11) where can find libmcs? google turned up some chemistry thing.. and the link in audacious readme was 404 in case this is relevant.. Code:
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) |
Did you install the audacious-plugins package? It is required for audacious to work. Basically you only need this from the Slackware-current tree:
Code:
~$ ls -l /var/log/packages/ | grep -i audacious Quote:
|
Generally speaking, it is a bad idea to selectively upgrade packages by picking them from slackware-current and install them into an earlier release. You may break your whole system if you pick the wrong package.
In your case, it is simply a matter of the audacious binary failing to find libraries that Slackware-current has, nothing worse. If you don't care about the rest of Slackware-current it may be better for you to create your own packages for audacious, audacious-plugins and mcs by downloading their source directories: Code:
http://slackware.mirrors.tds.net/pub/slackware/slackware-current/source/l/mcs/ You'll end up with an audacious installation that is built for your specific version of Slackware. Don't forget to remove these packages from slackware-current before you start compiling stuff! Eric |
thanks for the replies-
Quote:
Quote:
|
once again, thanks for the help. audacious is now up and running, still working on getting it to work with my media keys and xfce (reading...)
i still have this error tho' Code:
** (audacious:10778): WARNING **: alsa_setup_mixer(): Failed to find mixer element: PCM i get no alsa errors on boot (like I hadn't run alsaconf or alsamixer) any ideas? do I need new alsa modules? thanks! |
I have a mcs package (compiled on 11.0) here.
|
thanks GeneralFailure, but I've already got mcs built and installed:
Code:
root@phargrave:/usr/local/src/linux-2.6.19.1# ls /var/log/packages/mcs-0.4.1-i486-1 I hadn't noticed this error before, but now I'm paying more attention :D Code:
root@phargrave:/usr/local/src/linux-2.6.19.1# alsactl restore ??? |
Audacious assumes every card has PCM for it's software volume control; if you run alsamixer and there is no PCM slider, then you don't need to worry about it.
I've had these "error" messages all the while I've been using audacious (since 0.2 I think) with a Creative Labs SB Audigy LS soundcard. |
aaahhh..
Code:
perry@phargrave:/usr/local/src/conky-1.4.5$ amixer controls I have a new question that is related to this, in my .conkyrc: Code:
# set to yes if you want Conky to be forked in the background ?? even though i find the ps -a shows audacious ?? aha, nevermind... pidof _is_ the command conky is using.. it is in my /sbin and conky was looking in /usr/local/bin.. |
It appears you've PCM, which audacious isn't detecting. :rolleyes: As audacious is working fine, theres no need to worry :)
|
can / should I do anything to get rid of this error?
|
Short of bug hunting in the audacious source, don't worry about it :)
|
All times are GMT -5. The time now is 06:51 AM. |