Hi!

If the modules are not printed, that probably means that they cannot be
loaded :). (Bah, I assume that by looking at the vm code that does that
[1]).
So, first thing you can do is to see the output of stderr. Second, you can
try to do an ldd [2] to the vm-sound-ALSA.so library to check the
dependencies and try to get them installed via ap-tget.

Keep us informed :)

Cheers,
Guille

[1]
https://github.com/pharo-project/pharovm/blob/e4ccdb38e01578e3569c9c42d2199682584772ec/platforms/unix/vm/sqUnixMain.c#L965
[2] http://man.yolinux.com/cgi-bin/man2html?cgi_command=ldd


On Wed, Sep 4, 2013 at 11:32 AM, Marcus Denker <[email protected]>wrote:

>
> On Sep 4, 2013, at 11:22 AM, J.F. Rick <[email protected]> wrote:
>
> Hmm. Did this get sent or was it filtered? It doesn't seem to be in my
> inbox for the pharo-dev list.
>
>
> It arrived…
>
>
> Cheers,
>
> Jeff
>
>
> On Tue, Sep 3, 2013 at 5:03 PM, J.F. Rick <[email protected]> wrote:
>
>> I'm using Pharo 2.0 on Ubuntu 13.10 and I can't seem to get sound
>> working. Getting sound to work on Linux seems to be a common problem. While
>> I've checked the archive for solutions, none of them work for me. I've
>> investigated a bit and here's what I've found:
>>
>> Inside of the /usr/lib/pharo-vm directory, I see the following:
>> vm-sound-ALSA.so
>> vm-sound-null.so
>> vm-sound-pulse.so (I added that based on an archive post that this would
>> work)
>>
>> When I do "pharo -vm-sound-null pharo.image", it works correctly.
>> When I do "pharo -vm-sound-ALSA pharo.image", it gives me an error that
>> "could not find module vm-sound-ALSA".
>>
>> When I do "pharo-help", I find that the only sound driver available is
>> "vm-sound-null", though the others are clearly there in the directory. Is
>> there anything I can do to make the VM acknowledge that the other files are
>> there?
>>
>> Cheers,
>>
>> Jeff
>>
>> --
>> Jochen "Jeff" Rick, Ph.D.
>> http://www.je77.com/
>> Skype ID: jochenrick
>>
>
>
>
> --
> Jochen "Jeff" Rick, Ph.D.
> http://www.je77.com/
> Skype ID: jochenrick
>
>
>

Reply via email to