libbz2

[calxalot]

That’s the user guide.

The instructions for building is
https://github.com/FoldingAtHome/fah-cl ... ING-RPM.md

[calxalot]

I think libbz2 is dynamically linked now.
This might be why the debian build is not working on redhat.

[AZBrandon]

Look where you are posting your comments. The topic of the thread is libbz2, and the reason for the thread was that user misread the guide (which is not a massive issue, we all do that from time to time). You come in with something completely different. Your issue is neither libbz2, nor misreading the client build guide related

This is the error message I receive:

fah-client_8.5.5-64bit-release$ ./fah-client
./fah-client: error while loading shared libraries: libbz2.so.1.0: cannot open shared object file: No such file or directory

Your statement is that my issue is not libbz2 related, but I'm not sure how to reconcile that with the error message after I installed the fah 8.5.5 client saying it couldn't load libbz2. I'll see if I can find anything helpful though, and in the meantime it does seem that the fah servers still provide WUs to the older 8.4 client, so I have some time to work with.

[muziqaz]

Look where you are posting your comments. The topic of the thread is libbz2, and the reason for the thread was that user misread the guide (which is not a massive issue, we all do that from time to time). You come in with something completely different. Your issue is neither libbz2, nor misreading the client build guide related

This is the error message I receive:

fah-client_8.5.5-64bit-release$ ./fah-client
./fah-client: error while loading shared libraries: libbz2.so.1.0: cannot open shared object file: No such file or directory

Your statement is that my issue is not libbz2 related, but I'm not sure how to reconcile that with the error message after I installed the fah 8.5.5 client saying it couldn't load libbz2. I'll see if I can find anything helpful though, and in the meantime it does seem that the fah servers still provide WUs to the older 8.4 client, so I have some time to work with.

You are trying to run the client from source code directory without first building it. Of course you will get missing library error, since that library does not exist in source code directory. Your initial statement does not mention anything about your issue about libbz2. You just link to the guide page.
Fah-client building, installation and running it are 3 different things.
1st you build it (if you need it, so please do not build just for the sake of it), or download it from fah website
Then install from the built package
Then do not run the client yourself, but simply launch web browser and punch in v8-5.foldingathome.org

Work will be sent to all the old client versions down to v7, so need to rush. I'm sure we will announce to everyone once v7 is unsupported (no plans for that yet)

[calxalot]

They are trying to run the tarball client built for debian on a redhat distro.
This no longer works because of dynamic linking to libbz2.so.1.0, which is named libbz2.so.1 on redhat.

The current solution is to build the client yourself using the instructions in the GitHub repo.
https://github.com/FoldingAtHome/fah-cl ... ING-RPM.md

Or you can probably create a symlink to libbz2.so.1.0

There is activity toward getting rpm builds on the download page,
but there is no ETA, or even a promise it will happen.

[calxalot]

You can also continue to use the 8.4.9 tarball.

[calxalot]

To the person on Bazzite, I would say build the tarball on another redhat system and use that.
You use "scons dist" instead of "scons package"

[muziqaz]

Yeah, we need those packages for rpm distros published on website

[AZBrandon]

They are trying to run the tarball client built for debian on a redhat distro.
This no longer works because of dynamic linking to libbz2.so.1.0, which is named libbz2.so.1 on redhat.

The current solution is to build the client yourself using the instructions in the GitHub repo.
https://github.com/FoldingAtHome/fah-cl ... ING-RPM.md

Or you can probably create a symlink to libbz2.so.1.0

There is activity toward getting rpm builds on the download page,
but there is no ETA, or even a promise it will happen.

Thanks for the description. Yeah, so it doesn't appear I can create symlinks in Bazzite since it's Atomic Fedora, and the filesystem is in read-only mode as part of the whole "Atomic" part. It's nice that the 8.4.9 client works from the tarball though. It folds on either CPU or GPU on my (older) AMD 8845 system, but says OpenCL isn't supported on my Strix Halo system.

This seems to be an AMD issue; support for Strix Halo is virtually non-existent on most linux distributions that don't have the absolute latest kernel, but at least it does establish that I'm able to get it functioning on that system, though I can only GPU fold on the Strix Halo host when it's booted to Windows at the moment. Pretty typical for AMD though - hardware first, working drivers some time later.

I appreciate the both of you being patient with me. I retired from my tech career a couple years ago and tinkering is just a side project for me at this point, but I do try to learn new things and keep my mind sharp. Perhaps I'll spin up a non-Atomic Fedora build on my Proxmox server to build my own 8.5.x client if needed once the kernel in the Bazzite line actually supports the GPU fully.

I also appreciate the link to the build document, separate from the "run" document, or whatever. Obviously from my join date here I've been around a while, but only in the last year or so have I had enough time to expand my horizons into some aspects of homelab and stuff that I just never had any time for in the past.

[calxalot]

Is it just the system parts of file system that are read only with bazzite? Are you free to do whatever you want under your home?

[AZBrandon]

Is it just the system parts of file system that are read only with bazzite? Are you free to do whatever you want under your home?

Looks like it! According to a doc I found, the following directory paths are read-only in Fedora Atomic editions (which Bazzite is based on):

/usr, /etc, /var, /sysroot, and /boot

and the implication is all subdirectories therein are read only. I put the fah-client 8.5.5 tarball in my home directory and tried creating a symlink to the main libbz2 file from there as well as adding my homedir to the default binary path, but I'm not sure I was doing it the way the program expects. Not a big deal right now. There's a certain appeal to the Atomic editions (general safety of the operating system versus other release types) so perhaps it will be something to design around in the future.

Are there any stats on the breakdown of popularity of operating systems for FAH these days? Just curious.

[muziqaz]

Are there any stats on the breakdown of popularity of operating systems for FAH these days? Just curious.

Not by distros.

[Albuquerquefx]

For anyone else running Fedora OS who sees this thread and runs into this problem, and who isn't running Bazzite or another locked-down variant, I can help you solve this error.

This no longer works because of dynamic linking to libbz2.so.1.0, which is named libbz2.so.1 on redhat.

This is the true root cause, and the solution is exactly as calxalot mentioned: create a symlink named libbz2.so.1.0 linked to libbz2.so.1. Here's how you do it:

FIrst, you need to locate the libbz2.so.1 file in your OS. If you're on the native 64-bit Fedora OS, it's almost surely in /lib64, although you may find it in /usr/lib64 (usually this is symlinked back to /lib64.) If somehow you don't have it, you may need to install the bzip2-libs:

Code: Select all

sudo dnf install bzip2-libs

Once you know where the file is located, simply change directory to where you found it and symlink it:

Code: Select all

cd /lib64
sudo ln -s libbz2.so.1 libbz2.so.1.0

Now Folding at Home will work without issue. No need to completely compile the code from source, unless you're just into that sort of thing