Puppy Linux Discussion Forum

I have been messing around with pulseaudio on fatdog, systemd is not a dependency/requirement. However I have not been able to complete the mission of building a working pulseaudio, with pavucontrol etc. After installing all dependencies manually and linking libraries, the result is a wrong elf class .... or unable to find blah blah blah. So hopefully the fatdog team can find it in their hearts to put in some extra effort to get this sorted!

I don't know if the fatdog team is staunchly anti-systemd .... regardless I would love the option to boot into systemd. I had it installed successfully but I balked at modifying the initrd init to handover correctly! Maybe even just providing guidelines, again to help me out.

I know I could just switch to a systemd / pulse OS setup ... but that's not what I want!

kind regards
stemsee

I sent you a PM.

Thanks step! I tried your lean package. Didn't work, and I feel that my own all deps included package is closer to the goal.
If you are willing have a look, it feels like there are just a couple things to do.
https://drive.google.com/file/d/12lpixi ... sp=sharing

the result is a wrong elf class ....

That is usually all about trying to use a 32bit whatever, in a 64 bit Puppy.
Can also be trying to use 64 bit whatever, in a 32 bit Puppy.

The 64 bit Puppy versions 32bit compatibility sfs, usually provides the needed 32 bit support, in 64 bit Puppies.

64 bit whatever, in a 32 bit Puppy, will never work.

stemsee wrote: ↑Tue Aug 25, 2020 9:53 am If you are willing have a look, it feels like there are just a couple things to do.
https://drive.google.com/file/d/12lpixi ... sp=sharing

Like what?

That aside, I checked your SFS and there are no 32-bit ELFs inside. If you're still seeing that error message it could mean that 32bit-fd64.sfs is loaded, your pulseaudio SFS doesn't include all dependencies, and some of the missing dependencies can be found in 32bit-fd64.sfs, which trigger the wrong ELF class message.

Well ok....i installed a different libfftw3 ... and pulse runs but, these few errors. After adding user pulse and audio group.



before this on running pulseaudio --system=TRUE I got 'permission denied /var/run/pulse' is not home directory for pulse. Slowly chasing it down

I reconfigure /etc/pulse/client.pa and /ect/pulse/system.pa now the daemon wont start.

So I loaded the devx and my music sfs with jack etc and pulseaudio starts without complaining. But no controls are drawn with pavucontrol.

I think the .asound.rc file needs further work.

Finally, pulseaudio is fully working. My hardware is a chromebook and sound on linux is not yet functional. I will build a package and post it for testing.

Noted

I only have alsa in EasyOS, but the 'bluez' v5 package expects pulseaudio, for bluetooth audio support. Which is a very big headache!

I compiled 'bluez-alsa', which is a kind of substitute to pulseaudio, and does enable bluetooth audio to work with just alsa. Some of my blog posts:

https://bkhome.org/news/202001/audioson ... os-22.html

https://bkhome.org/news/202001/sound-ca ... tooth.html

https://bkhome.org/news/202003/blueman- ... piled.html

I briefly considered installing pulseaudio, but was horrified how complex pulseaudio is, and backed off. Might look at it again, as you are reporting success.

Thanks Barry!

That's encouraging me to sit down and earnestly piece together and extract the working components, however daunting. As stated my problem is that I'm working on a acer 714 chromebook which is noted for touch and internal sound not working with linux.....booting with legacy seabios from mrchromebox. There is also a full efi from the same source, which as you may know, can affect positively or negatively hardware. But I haven't tried it yet as I would lose my current chromeos with touch and sound working!

I will go over the linked posts.

cheers
stemsee

This is my pulseaudio.sfs
edited https://drive.google.com/file/d/1QlssLr ... MtdhUiaDnC
this is my music.sfs
edited https://drive.google.com/file/d/1QCBtAF ... RgjpL7bih7
and i loaded fatdog-devx (thanks step) EDIT: As stated my hardware is a chromebook so I couldn't actually get any sound, or hardware graphs. So I can only say pulseaudio appears to be working. I also have two other pulseaudio sfs files, and I lost track of which ones I used when ... so testing required, and if need be I'll upload those.

@stemsee the google drive links you posted lead to login request forms. Please post open links. What does your last post mean? It seems the text was cut off after "As stat". Were you going to add anything?

For @Stemsee and any of us who are Google users: Should you have things to share with forum users it is easy to click "Share" for the folder or file; and allow Everyone OR "Everyone with a link" to access what you share.

I am sure you will see other useful share options there, too. Google make it easy peasy.

Hope this helps everyone.

@stemsee why did you post download links that ask to enter a password?

Oh...sorry everyone! I have shared gdrive links tens of times....i did nothing different!

I will check and try again!!

Dangling symbolic links in your pulseaudio sfs:

lib/firmware/intel/dsp_fw_release.bin -> dsp_fw_release_v969.bin
usr/lib/x86_64-linux-gnu/libtdb.so -> libtdb.so.1.4.3
usr/lib64/libasyncns.so.0 -> /mnt/sda3/pulseaudio/usr/lib64/libasyncns.so.0.3.1
usr/lib64/libgdkmm-3.0.so.1 -> /mnt/sda3/pulseaudio/usr/lib64/libgdkmm-3.0.so.1.1.0

Very well spotted!

Those links were part of an attempt to follow a guide on getting the soundcard to work on linux!

I'm a little confused - I've tried using the SFS and I can't seem to get Pulseaudio going.

What are the steps? Do you need to do this:

Or something else?
It seems to me like something in the SFS is conflicting with something else I installed earlier or the sfs is incomplete somehow.

Has anyone tried it successfully on a clean install or fresh fd64save file?

Also any hint as to how you built it stemsee? Might be handy for those needing to do the same in the future.