Active Topics

 



Notices


Reply
Thread Tools
Posts: 1 | Thanked: 1 time | Joined on Jun 2010
#1
Hi everybody... could you give me a help in making sound work inside a easy-chrooted custom debian image?

I'm using easy-chroot (not easy-debian) to chroot into a custom debian image that I created with debootstrap. "Everything" is working fine: iceweasel, openoffice, xchat, etc... but I cannot play any sound (tried with mplayer and audacious).

I changed the qchroot script to avoid "mount -bind" /home: I want a clean environment, less coupled as possible with maemo.

What is the trick to make the sound working inside such a chroot? In the error messages there are something like "there is no /dev/dsp" (I created it manually, but it didn't work), or problems in alsa-related .c files (these are strange alsa errors because they reference its source).

Thank you!

-----------------------------

EDIT: Done! I have a N900, and this uses pulse as audio server AFAIK. Maemo's /etc/asound.conf should be copied to /etc in the chroot environment; this way, ALSA will "use" pulse. I installed so many things that now I don't know the minimum set o packages to install, but probably pulseaudio (I don't know if libpulse0 has to be installed also, because apps that needs it should install by themselves... I dunno), alsa-base and alsa-utils.
Now my mplayer is working (played just a couple of times an mp3 file), even with wma internet radios that is not supported by n900's maemo internet radio player.
A nice reference: https://wiki.ubuntu.com/PulseAudio

Regarding audacious, aucacious-plugins-extra package is responsible for a segmentation fault error in the initialization of this player. I installed this plugins package, copied the .so related to pulse from /usr/lib/audacious/Output or something like this, and then removed the package. After that, I copied the saved pulse .so to the same old dir and it worked; but the mp3 playing presents many fast-stops too often - did not tried to solve this because mplayer is working... but I think this could be a problem in audacious pulse lib, a configuration trouble, or an audacious requirement for a more powerful hardware to work well.

Last edited by tnords5; 2010-06-05 at 20:17.
 

The Following User Says Thank You to tnords5 For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 13:48.