LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 04-23-2007, 01:17 PM   #1
bioe007
Member
 
Registered: Apr 2006
Location: lynnwood, wa - usa
Distribution: archlinux
Posts: 654

Rep: Reputation: 30
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] 27395
perry@phargrave:/usr/local/src$ Failed to load plugin (/usr/lib/audacious/General/libscrobbler.so): libcurl.so.4: cannot open shared object file: No such file or directory
Failed to load plugin (/usr/lib/audacious/General/libcurl.so): libcurl.so.4: cannot open shared object file: No such file or directory
I/O warning : failed to load external entity "/home/perry/.config/audacious/playlist.xspf"

** (audacious:27395): WARNING **: alsa_setup_mixer(): Failed to find mixer element: PCM
I'm not too worried about the lack of playlist, but the libcurl.so.4 seems to be a -current vs. -11 issue.

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)
        Subsystem: Dell Unknown device 01cc
        Flags: bus master, fast devsel, latency 0, IRQ 21
        Memory at dfebc000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
many thanks!
 
Old 04-23-2007, 01:27 PM   #2
raska
Member
 
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816

Rep: Reputation: 30
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
-rw-r--r-- 1 root root   10236 2007-04-13 10:31 audacious-1.3.2-i486-1
-rw-r--r-- 1 root root    6721 2007-04-13 10:31 audacious-plugins-1.3.2-i486-1
~$ ls -l /var/log/packages/ | grep -i mcs
-rw-r--r-- 1 root root    1169 2007-04-13 10:31 mcs-0.4.1-i486-1
Also looking at your problem, it seems like you don't have any modules loaded on your kernel for your audio device:
Quote:
Originally Posted by bioe007
** (audacious:27395): WARNING **: alsa_setup_mixer(): Failed to find mixer element: PCM
Try the alsamixer command, does it work?
 
Old 04-23-2007, 01:35 PM   #3
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,238

Rep: Reputation: Disabled
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/
http://slackware.mirrors.tds.net/pub/slackware/slackware-current/source/xap/audacious/
http://slackware.mirrors.tds.net/pub/slackware/slackware-current/source/xap/audacious-plugins/
Compile and install your packages in the above order by first running the <packagename>.SlackBuild scripts in their respective directories and running "installpkg /tmp/<packagename>*.tgz" after the build completes.
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
 
Old 04-23-2007, 03:43 PM   #4
bioe007
Member
 
Registered: Apr 2006
Location: lynnwood, wa - usa
Distribution: archlinux
Posts: 654

Original Poster
Rep: Reputation: 30
thanks for the replies-

Quote:
Originally Posted by raska
Try the alsamixer command, does it work?
yes..

Quote:
Originally Posted by Alien Bob
...it is a bad idea to selectively upgrade packages...it may be better for you to create your own packages for audacious, audacious-plugins and mcs by downloading their source directories
thanks! exactly the kind of advice I was looking for. will do!
 
Old 04-24-2007, 12:48 AM   #5
bioe007
Member
 
Registered: Apr 2006
Location: lynnwood, wa - usa
Distribution: archlinux
Posts: 654

Original Poster
Rep: Reputation: 30
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'm clueless 'cause otherwise sound seems fine?

i get no alsa errors on boot (like I hadn't run alsaconf or alsamixer)

any ideas? do I need new alsa modules?

thanks!
 
Old 04-24-2007, 05:32 AM   #6
General Failure
Member
 
Registered: Jan 2007
Location: Germany
Distribution: Slackware 13.37
Posts: 384

Rep: Reputation: 34
I have a mcs package (compiled on 11.0) here.
 
Old 04-24-2007, 11:33 AM   #7
bioe007
Member
 
Registered: Apr 2006
Location: lynnwood, wa - usa
Distribution: archlinux
Posts: 654

Original Poster
Rep: Reputation: 30
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 
/var/log/packages/mcs-0.4.1-i486-1
from slackware-current sources and associated slackbuilds. now I'm thinking there is some problem with 1) my kernel 2) my alsa driver?

I hadn't noticed this error before, but now I'm paying more attention
Code:
root@phargrave:/usr/local/src/linux-2.6.19.1# alsactl restore
alsactl: set_control:873: failed to obtain info for control #7 (No such file or directory)
root@phargrave:/usr/local/src/linux-2.6.19.1#
also see that near the end of bootup when init is running alsactl restore..

???
 
Old 04-24-2007, 02:51 PM   #8
samwwwblack
Member
 
Registered: Apr 2003
Location: Midlands, UK
Distribution: Lapwing-Linux 2009.1
Posts: 64

Rep: Reputation: 15
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.
 
Old 04-24-2007, 04:52 PM   #9
bioe007
Member
 
Registered: Apr 2006
Location: lynnwood, wa - usa
Distribution: archlinux
Posts: 654

Original Poster
Rep: Reputation: 30
aaahhh..

Code:
perry@phargrave:/usr/local/src/conky-1.4.5$ amixer controls 
numid=2,iface=MIXER,name='Master Playback Switch'
numid=1,iface=MIXER,name='Master Playback Volume'
[/b]numid=7,iface=MIXER,name='PCM Playback Volume'[/b]
numid=6,iface=MIXER,name='Capture Mux Volume'
numid=5,iface=MIXER,name='Capture Switch'
numid=4,iface=MIXER,name='Capture Volume'
numid=3,iface=MIXER,name='Input Source'
perry@phargrave:/usr/local/src/conky-1.4.5$
am i misunderstanding this output? (this is now a learning exercise as the audacious seems to be working fine)

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
background yes

# Use Xft?
use_xft yes

# Xft font when Xft is enabled
xftfont Bitstream Courier 10 pitch:size=9

# Text alpha when using Xft
xftalpha 0.8

# Print everything to stdout?
out_to_console yes

# Update interval in seconds
update_interval 1.0

# Set to zero to run forever.
total_run_times 0

# Create own window instead of using desktop (required in nautilus)
own_window no

# Use double buffering (reduces flicker, may not work for everyone)
double_buffer yes

# Minimum size of text area
minimum_size 280 5

# Draw shades?
draw_shades yes

# Draw outlines?
draw_outline yes

# Draw borders around text
draw_borders no

# Draw borders around graphs
draw_graph_borders no

# Default colors and also border colors
default_color green
default_shade_color black
default_outline_color black

# Text alignment, other possible values are commented
alignment top_left

# same thing as passing -x at command line
gap_x 340
gap_y 0

# Subtract file system buffers from used memory?
no_buffers yes

# set to yes if you want all text to be in uppercase
uppercase no

# set to 1 to disable averaging
cpu_avg_samples 2

# set to 1 to disable averaging
net_avg_samples 2

# Force UTF8? note that UTF8 support required XFT
override_utf8_locale no

# Add spaces to keep things from moving about?  This only affects certain objects.
use_spacer yes

TEXT
${color white}CPU:${offset 6}${color green}${cpu 1}/${offset 8}${cpu 2}%${offset 16}${color white}temp:${offset 6}${color green}${acpitemp}${color white}${offset 16}MEM/SWP:${offset 6}${color green}$memperc/$swapperc%${offset 12}${color white}FAN:${color green}${offset 6}${i8k_right_fan_rpm}${offset 12}${color white}BAT:${color green}$battery , $battery_time ${color white}DOWN: ${color green}${offset 6}${downspeed eth0}
${if_running audacious}${color white}Audacious:${color green} ${audacious_title 20} ${color RoyalBlue}${audacious_bar 8,45}${endif}
if get this error: sh: pidof: command not found

?? 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..

Last edited by bioe007; 04-24-2007 at 04:59 PM.
 
Old 04-25-2007, 11:33 AM   #10
samwwwblack
Member
 
Registered: Apr 2003
Location: Midlands, UK
Distribution: Lapwing-Linux 2009.1
Posts: 64

Rep: Reputation: 15
It appears you've PCM, which audacious isn't detecting. As audacious is working fine, theres no need to worry
 
Old 04-25-2007, 02:40 PM   #11
bioe007
Member
 
Registered: Apr 2006
Location: lynnwood, wa - usa
Distribution: archlinux
Posts: 654

Original Poster
Rep: Reputation: 30
can / should I do anything to get rid of this error?
 
Old 05-01-2007, 04:58 AM   #12
samwwwblack
Member
 
Registered: Apr 2003
Location: Midlands, UK
Distribution: Lapwing-Linux 2009.1
Posts: 64

Rep: Reputation: 15
Short of bug hunting in the audacious source, don't worry about it
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
about audacious - libraries problem tramni1980 Slackware 6 11-11-2006 01:25 PM
No output device in audacious Zmyrgel Slackware 7 11-09-2006 06:39 PM
cvs diff the most current and second last current version powah Linux - Software 1 03-30-2006 01:02 PM
Installing MCS Skaan Debian 7 05-24-2005 08:54 AM
current Slack-Current giving troubles? r_jensen11 Slackware 5 02-02-2004 05:08 PM


All times are GMT -5. The time now is 06:41 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration