Hey
Just wanted to share my first R-Pi project: a standalone, wireless Jukebox
http://blog.ziade.org/2012/07/01/a-raspberry-pi-juke-box-how-to/
http://blog.ziade.org/2012/07/04/my-raspberry-pi-juke-box-follow-up/
I'd be curious to have some feedback if anyone here did a similar thing
Cheers
Nice jukebox and good writeup, Tarek. And coincidentally your post came in at the exact time that I wanted to configure sound on my newly arrived Pi, so I used your first link as a handy reference --- thanks! 
I have sound running on lots of other Linux machines and found the Broadcom module through a scan of /lib/modules, but the mixer output control was more obscure:
sudo modprobe snd_bcm2835
sudo amixer cset numid=3 1
I'm not sure what this particular Pi is going to do yet (I don't want to endanger it with hardware interfacing until they're freely available from stock at Farnell), but I wanted to get sound working just to check that all systems are operational.
mpg123 is a good stalwart, I agree, but I've become a big fan of MOC, which is as lightweight as mpg123 but has the better property of running in the background and allowing you to connect from any xterm anywhere, as many times in parallel as you want.
moc - ncurses based console audio player - http://moc.daper.net
An apt-get brought the moc package in, and "mocp" worked as soon as I found a file to play, an ogg in this case.
I notice that you found your jukebox using 100% CPU. Well I've noticed that mocp uses 36% CPU on the Pi, whereas on an Intel system its usage is under 4% for an ogg. I wonder what's going on there, since the BCM2835 is a top-end media processor and should be doing all the decoding. It seems unlikely that transferring data to the hardware at audio rates is going to require 36% CPU, or 100% in your case.
This will need investigating.
Morgaine.
