Installation instructions for v6.41 GPU in Linux

[Jesse_V]

The procedures for setting v6 GPU3 in Linux under Wine seems to be regarded as highly difficult, and I was very confused at first. So far I've found three guides at this topic, but two are a bit out-of-date and all three can be confusing if you're not familiar with Linux or what you're doing. I recently got GPU3 to run in Linux, and I'm very pleased about that. I'd like to document the steps I took in getting it to work, so that if anyone is interested they can try this procedure and hopefully get it working for them. The setup is necessary for the older GPUs, such as the G80 series, since they are too old to be likely supported naively.

Before beginning, I'd highly recommend that one study the other guides. All three approach the problem in a slightly different way, so reading them over helps build a good perspective of the steps involved.

http://linuxfah.info/mediawiki/index.php?title=Main_Page - Pretty good site, but I found their "Linking the Toolkit" step to be unclear.
http://foldingforum.org/viewtopic.php?f=54&t=6793 - especially handy for a headless installation, and the long-running thread contains useful info
http://bredsaal.dk/running-the-foldinghome-gpu-client-on-ubuntu-10-10 - this one uses older versions of the CUDA toolkit and the v6 GPU client

I began with Linux Mint 14, which is based on Ubuntu 12.10, and uses the 3.5 series kernel. I don't know if it works on higher kernel versions, so please let me know if it does. I'd recommending starting at step 1, although skipping to step 6 is of course just find if 1-5 are already done.

1)

sudo apt-get update
sudo apt-get dist-upgrade

Upgrades to the latest supported packages. This is fairly important if you're starting from a fresh installation.

2) Restart the computer. When I ran it, dist-upgraded upgraded my kernel, so a restart was required. If a bunch of packages were upgraded, might as well restart just to be safe.

3)

sudo apt-get install nvidia-current.

Installs the latest proprietary nvidia driver. This is necessary for running CUDA.

4) Restart the computer. The drivers are tied into the kernel, and a restart is necessary to start using them.

5)

sudo apt-get autoremove
sudo apt-get autoclean

Cleans out any older and obsolete packages. You can also use the Package Manager to remove old Linux kernel images.

6)

cd ~
mkdir fahgpu
cd fahgpu/

Make a directory for us to work in.

7)

wget http://developer.download.nvidia.com/compute/cuda/3_0/toolkit/cudatoolkit_3.0_linux_32_ubuntu9.04.run
chmod u+x cudatoolkit_3.0_linux_32_ubuntu9.04.run

Downloads the CUDA Toolkit, and marks it as executable.

8) The toolkit installer will prompt you for an installation location. Just press Enter to accept the default of usr/local/cuda

9)

sudo apt-get install wine
WINEARCH=win32 winecfg

Installs Wine, and sets up a 32-bit environment for the client.

10)

sudo sh -c "echo PATH=/usr/local/cuda/bin:$PATH > /etc/profile.d/cuda.sh"
sudo sh -c "echo /usr/local/cuda/lib > /etc/ld.so.conf.d/cuda.conf"
sudo ldconfig

Links the toolkit. Although it shouldn't happen, there's a possibility of running into this error.

11)

cd ~/.wine/drive_c/windows/system32
wget http://www.linuxfah.info/wrapper-3.0/cudart/cudart.dll.so
wget http://www.linuxfah.info/wrapper-3.0/cufft/cufft.dll.so

Fetches the Wine CUDA wrappers.

12)

ln -s cudart.dll.so cudart32_30_14.dll
ln -s cudart.dll.so cudart.dll
ln -s cudart.dll.so nvcuda.dll
ln -s cufft.dll.so cufft32_30_14.dll
ln -s cufft.dll.so cufft.dll
ldd cudart.dll
export LD_LIBRARY_PATH=/usr/local/cuda/lib:$LD_LIBRARY_PATH

Links up the wrappers. As described in the other guides, the output should look like:

Code: Select all

linux-gate.so.1 =>  (0xf7706000)
        libcudart.so.3 => /usr/local/cuda/lib/libcudart.so.3 (0xf7697000)
        libwine.so.1 => /usr/lib32/libwine.so.1 (0xf7556000)
        libm.so.6 => /lib32/libm.so.6 (0xf752f000)
        libc.so.6 => /lib32/libc.so.6 (0xf73cc000)
        libdl.so.2 => /lib32/libdl.so.2 (0xf73c8000)
        libpthread.so.0 => /lib32/libpthread.so.0 (0xf73af000)
        librt.so.1 => /lib32/librt.so.1 (0xf73a6000)
        libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf72b7000)
        libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf72a7000)
        /lib/ld-linux.so.2 (0xf7707000)

but if it doesn't then something is wrong with the linking, so goto step 10.
It was my experience that this and step 10 were the most complicated, so I recommend that you look at the other guides as well for ideas.

13)

cd ~/fahgpu/
wget http://www.stanford.edu/group/pandegroup/folding/release/Folding@home-Win32-GPU_XP-641.zip
sudo apt-get install unzip
unzip Folding@home-Win32-GPU_XP-641.zip

Fetches the client, and unzips it in the fahgpu folder.

14)

rm cudatoolkit_3.0_linux_32_ubuntu9.04.run
rm *.dll

Cleanup. Removing Stanford's supplied .dll's is important, as we want to use Wine's instead.

15)

wget http://www.linuxfah.info/wrapper-3.0/auto-mator-g80.sh.txt
mv auto-mator-g80.sh.txt gpu3.sh
chmod u+x gpu3.sh

Fetches a handly script called Auto-Mator that dynamically changes the SLEEPWAIT environmental variable to to make sure the GPU client doesn't use an entire CPU core.

16)

./gpu3.sh

Runs the script, launching GPU3 in Wine. I personally prefer to open it in the command-line, then move the window to another workspace so that it's out of the way.

As you can see, the procedure is fairly straightforward, but using the command-line is required. These are basically the steps I took to set it up. ATM I have not yet started over and retested these instructions, but they should work. Please let me know if you have any issues or improvement suggestions.

Edit 3-22-2013: Fixed typos

[P5-133XL]

Seems much clearer than previous instructions I've read.

[davidcoton]

Nice one Jesse!

From reading (not testing) I can see two possible problems:
Step 11. The weblink has been coded as such, and the visible script has an ellipsis (...) instead of the full path.
Step 13. Download 6.41 but unzip 6.23.

I'll test it next time I need to reinstall, but I hope that isn't too soon.

Hope that helps,

David

[Jesse_V]

From reading (not testing) I can see two possible problems:
Step 11. The weblink has been coded as such, and the visible script has an ellipsis (...) instead of the full path.
Step 13. Download 6.41 but unzip 6.23.

Fixed. Thanks.

Also, I used a combination of the GUI and the command-line when I set this up. It's entirely possible to download the files through Chrome and then move them to the proper location, or you can do the entire process in Terminal. Multiple ways of doing this, but the same goal is accomplished.
Setup driver, install CUDA toolkit, link toolkit, install Wine, configure Wine wrappers, install and setup client, run.

[art_l_j_PlanetAMD64]

Great instructions, Jesse!

I have a "standard" way of installing the Linux/Wine/GPU3 console client, that I've been meaning to document, but I haven't had the extra time to do it yet. It is based on Hyperlife's NVIDIA GPU3 Linux/Wine Headless Install Guide, and I have used this method to install the GPU3 v6.41r2 console client on 16 Debian v6.0.6 Linux systems here. It's gotten to the point where the installation procedure is so uneventful, that I can do it correctly even when half-asleep!

I've got to go out now, but when I get back, I'll document my procedure here, so we can compare them.

Art

[art_l_j_PlanetAMD64]

Here are the instructions on how to install the FAH GPU3 v6.41r2 console client in a Debian Linux v6.0.6 machine. This procedure has been used on 16 Linux machines here, and it has worked flawlessly every time. The instructions should work on Ubuntu as well, although that has not been tested. For other Linux distributions, you'll have to figure out the "wrinkles" on your own, although I and others here will be available to help sort out any problems that may come up.

A lot of this was shamelessly copied from Hyperlife's excellent NVIDIA GPU3 Linux/Wine Headless Install Guide. Hyperlife and the contributors to that thread deserve most of the credit for what you will see here.

These instructions are not written for beginners. For example, you will be told to "Create a new directory ~/fahgpu3, and cd to it". It is assumed that you know how to do this without being told every step in detail.

A good working knowledge of how to use vi (or a similar non-GUI text editor) will be a great asset, although there is a work-around for those who don't know how to use text editors in a non-GUI environment.

It is assumed that you have already downloaded, installed, and set up your Linux system, before starting these instructions.

OK, now let's get started:

1. Edit the file /etc/sudoers, to include yourself in the list of those who can use the sudo command. You must become the root user, before you can edit the /etc/sudoers file. Here is my /etc/sudoers file, from one of my Linux systems here:

   Code: Select all

   # /etc/sudoers
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the man page for details on how to write a sudoers file.
#

Defaults   env_reset

# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
root   ALL=(ALL) ALL
art    ALL=(ALL) ALL

# Allow members of group sudo to execute any command
# (Note that later entries override this, so you might need to move
# it further down)
%sudo ALL=(ALL) ALL
#
#includedir /etc/sudoers.d

2. Create a new directory ~/bin, and cd to it. Install the following files/command scripts there:
   
   cuda_init:

   Code: Select all

   #!/bin/bash

    PATH=$PATH:/usr/local/cuda/bin

    modprobe nvidia

    if [ "$?" -eq 0 ]; then

    # Count the number of NVIDIA controllers found.
    N3D=`/usr/bin/lspci | grep -i NVIDIA | grep "3D controller" | wc -l`
    NVGA=`/usr/bin/lspci | grep -i NVIDIA | grep "VGA compatible controller" | wc -l`

    N=`expr $N3D + $NVGA - 1`
    for i in `seq 0 $N`; do
    mknod -m 666 /dev/nvidia$i c 195 $i;
    done

    mknod -m 666 /dev/nvidiactl c 195 255

    else
    exit 1
    fi


   
   debian_update:

   Code: Select all

   sudo apt-get update
sudo apt-get dist-upgrade
sudo reboot

   
   fah_disable_nouveau:

   Code: Select all

   sudo cp -fp nvidia-installer-disable-nouveau.conf /etc/modprobe.d

   
   fah_get_utils:

   Code: Select all

   sudo apt-get install binutils
sudo apt-get install gcc-4.3
sudo apt-get install make

   
   fahgpu:

   Code: Select all

   #!/bin/bash
#
# Folding@home GPU3 Linux/Wine Client
#
# fahgpu - Starts the Folding@home GPU3 Linux/Wine Client
#
#

HOME=$(pwd)
NAME=$(basename $HOME)
EXEC=$HOME/Folding@home-Win32-GPU.exe
LOG=$HOME/FAHlog.txt
NICE=$HOME/.nice
VERBOSITY=$HOME/.verbosity
GPU=$HOME/.gpu
EXTRA_ARGS=$HOME/.extra_args



get_gpu() {
    cat $GPU
}


get_nice() {
    cat $NICE
}


get_verbosity() {
    cat $VERBOSITY
}


get_extra_args() {
    if [ -f $EXTRA_ARGS ]; then
        cat $EXTRA_ARGS
    fi
}


echo -n "Starting $NAME ... "

if [ ! -d $HOME ]; then
  echo "FAILED"
  echo "Directory $HOME does not exist"
  exit 1
fi

if [ ! -f $GPU ]; then
  echo "FAILED"
  echo "File $GPU does not exist"
  exit 1
fi

if [ ! -f $NICE ]; then
  echo "FAILED"
  echo "File $NICE does not exist"
  exit 1
fi

if [ ! -f $VERBOSITY ]; then
  echo "FAILED"
  echo "File $VERBOSITY does not exist"
  exit 1
fi

# Now execute the command line to run the program
nice -n $(get_nice) wine $EXEC -verbosity $(get_verbosity) -forcegpu $(get_gpu) $(get_extra_args)

   
   get_driver_cuda:

   Code: Select all

   wget http://us.download.nvidia.com/XFree86/Linux-x86_64/304.64/NVIDIA-Linux-x86_64-304.64.run
wget http://developer.download.nvidia.com/compute/cuda/3_0/toolkit/cudatoolkit_3.0_linux_32_ubuntu9.04.run

   
   get_install_wine:

   Code: Select all

   sudo sh -c "echo 'deb http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu jaunty main' >> /etc/apt/sources.list"
sudo sh -c "echo 'deb-src http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu jaunty main' >> /etc/apt/sources.list"
sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 5A9A06AEF9CB8DB0
sudo apt-get update
sudo apt-get install wine

   
   get_wine_wrappers:

   Code: Select all

   wget http://www.linuxfah.info/wrapper-3.0/cudart/cudart.dll.so
wget http://www.linuxfah.info/wrapper-3.0/cufft/cufft.dll.so
ln -s cudart.dll.so cudart32_30_14.dll
ln -s cudart.dll.so cudart.dll
ln -s cudart.dll.so nvcuda.dll
ln -s cufft.dll.so cufft32_30_14.dll
ln -s cufft.dll.so cufft.dll

   
   link_cuda:

   Code: Select all

   sudo sh -c "echo '/usr/local/cuda/lib' > /etc/ld.so.conf.d/cuda.conf"
sudo ldconfig

   
   list_nvidia:

   Code: Select all

   dpkg --list | grep -i --color nvidia

   
   nvidia-installer-disable-nouveau.conf:

   Code: Select all

   # generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0

   
   purge_nvidia:

   Code: Select all

   apt-get --purge remove xserver-xorg-video-nouveau nvidia-kernel-common nvidia-kernel-dkms nvidia-glx nvidia-smi

3. While still in the ~/bin directory, execute the following commands:

   Code: Select all

   chmod u+x *
chmod -x *.conf
./fah_get_utils
./debian_update

   (the system will reboot after this command).
4. Log back in after rebooting, then install the latest version of Wine:

   Code: Select all

   get_install_wine

5. Download the latest NVIDIA Linux 64-bit driver and the CUDA 3.0 32-bit toolkit:

   Code: Select all

   cd ~/Downloads
get_driver_cuda

6. Before you install the NVIDIA driver, you need to install some Linux build utilities and header files:

   Code: Select all

   sudo apt-get install build-essential linux-headers-`uname -r`

   Those are backward apostrophes surrounding the uname command, which allows the output of uname to be incorporated into the filename of the headers file. Cut and paste from the above line if you have trouble downloading the proper headers.
7. To install the NVIDIA 304.64 driver, Nouveau (the default Debian NVIDIA driver) must be disabled before the reboot into the non-GUI, single-user "recovery mode". The NVIDIA driver cannot be installed while a GUI is running, it must be installed in the non-GUI, single-user "recovery mode". Please follow these instructions to install the NVIDIA 304.64 driver:

   Code: Select all

   cd ~/bin
fah_disable_nouveau
sudo reboot

   During the reboot, you need to quickly select the "recovery mode" from the GRUB menu, and then login using the root password. While logged in as root, please follow these instructions to install the NVIDIA 304.64 driver:
   • Execute these commands (replace "art" with your username in that system):

     Code: Select all

     cd /home/art/bin
./purge_nvidia
./list_nvidia
cd /home/art/Downloads
sh NVIDIA-Linux-x86_64-304.64.run

     Follow the prompts from the NVIDIA installer. You must install the 32-bit OpenGL libraries, when you are asked about it. Answer "Yes" when asked if you would like to run the nvidia-xconfig utility. You must edit the file /etc/X11/xorg.conf, to add the line shown with Option "Coolbits" "5", to have the option of controlling the GPU's fan speed manually. Edit the file /etc/X11/xorg.conf, using vi or any other non-GUI editor, so that the end of the file looks like this:

     Code: Select all

     Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    Option         "Coolbits" "5"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

     
     Work-around: If you are not able to use vi or any other non-GUI editor, then you can edit the /etc/X11/xorg.conf file after the next "normal" boot and login, as long as you reboot immediately after saving the file.
8. Install the NVIDIA 32-bit toolkit:

   Code: Select all

   cd ~/Downloads
sudo sh cudatoolkit_3.0_linux_32_ubuntu9.04.run

   Use the default path by hitting Enter when prompted.
9. Link the toolkit:

   Code: Select all

   link_cuda

10. Create the WINE directory structure:

    Code: Select all

    cd ~
wine notepad

    Disregard the errors; all we need is the directory structure created in ~/.wine when you run it the first time.
11. Create a new directory ~/fahgpu3, and cd to it. Put these files into that directory:
    • .gpu:

      Code: Select all

      nvidia_fermi

      (or use nvidia_g80 for NVIDIA GPUs older than Fermi)
    • .nice :

      Code: Select all

      0

      (The nice value to use for the program.)
    • .verbosity :

      Code: Select all

      9

      (The verbosity level to use in the program.)
    • client.cfg :

      Code: Select all

      [settings]
username=art_l_j_PlanetAMD64
team=45862
passkey=********************************
asknet=no
machineid=2
bigpackets=big
local=1

[http]
active=no
host=localhost
port=8080
usereg=no

      (Edit with your own personal FAH information.)
    • Copy the fahgpu script from ~/bin to ~/fahgpu3.
12. Download the latest Wine wrappers, save them to ~/fahgpu3, and create a few symlinks:

    Code: Select all

    cd ~/fahgpu3
get_wine_wrappers

    (This always works, to have the Wine wrappers and symlinks in the Application directory, Wine sometimes had problems locating them when they were in Wine's windows/system32 directory.)
13. Run the cuda_init script as root:

    Code: Select all

    sudo cuda_init

    You should now have a few extra devices in /dev; check to make sure:

    Code: Select all

    ls /dev/nv*

    If you have one video card, you should see the following:

    Code: Select all

    /dev/nvidia0  /dev/nvidiactl

14. Time to download the console version of the GPU3 folding client (finally!), from this link:
    http://www.stanford.edu/group/pandegroup/folding/release/Folding@home-Win32-GPU_XP-641.zip
    Copy the zip file to the ~/fahgpu3 directory, and unzip it there, to get the executable file (Folding@home-Win32-GPU.exe).
15. From the Debian desktop, go to System -> Preferences -> NVIDIA X Server Settings, right-click on it, and select "Add this launcher to panel".
16. Click on this launcher you just created, to start up the NVIDIA X Server Settings. When it is running, click on "PowerMizer", and select "Prefer Maximum Performance" as the Preferred Mode at the bottom-right. Then click on "Thermal Settings", click to "Enable GPU Fan Settings", dismiss the warning message, and set the percent value you want for the Fan Speed.
17. Open a Terminal window, and start up the FAH GPU3 v6.41r2 client by doing the following:

    Code: Select all

    cd ~/fahgpu3
./fahgpu

18. I always open a second terminal window, to do a 'tail' of the log file, as follows:

    Code: Select all

    cd ~/fahgpu3
tail -n 1024 -f FAHlog.txt

[Napoleon]

Decided to try G80 folding with wine, but there's a bit of a problem... http://linuxfah.info seems to be out of commission, so no wine wrappers and automator script are available. Is there some alternate location for those files?

PS: obviously the problem applies to Hyperlife's NVIDIA GPU3 Linux/Wine Headless Install Guide as well.

[Jesse_V]

Decided to try G80 folding with wine, but there's a bit of a problem... http://linuxfah.info seems to be out of commission, so no wine wrappers and automator script are available. Is there some alternate location for those files?

PS: obviously the problem applies to Hyperlife's NVIDIA GPU3 Linux/Wine Headless Install Guide as well.

Well I hope they get their site back up. In the meantime, here are the files I have. I pulled the .so files out of the Wine directory, so they should (in theory) be identical to the ones hosted by linuxfah.info. Just tweak the commands so that you fetch the files from the following paths instead of from linuxfah.info, and it should work.
http://www.jessevictors.com/files/permalink/fahWine/cudart.dll.so
http://www.jessevictors.com/files/permalink/fahWine/cufft.dll.so
http://www.jessevictors.com/files/permalink/fahWine/auto-mator-g80.sh.txt
The auto-mator-g80 file is my own version, and I've modified some of the numbers a bit from the original. I didn't see much of a difference, and I stopped using it in favor of a run.sh script instead. If you really want the original auto-mater-g80 script, you might be able to find it elsewhere or from someone else.

#!/bin/sh
wine Folding@home-Win32-GPU.exe -forcegpu nvidia_g80

Also, I experienced a noticeable amount of lag from the v6 GPU client, most of it with Chrome. Luckily there's a "use hardware acceleration" checkbox at the very bottom of chrome://settings/. Once I unchecked that and restarted Chrome I didn't experience much lag at all. So far I've completed 277 WUs on my GT 240m under Linux!

[smoking2000]

The CUDA wrapper code is also on GitHub:

Shellnutt2: cuda-wine-wrapper
v3.0

sebastic: cuda-wine-wrapper
Has cuda4 branch with incomplete CUDA 4 support, required for recent NVIDIA drivers that don't support CUDA 3 anymore, but the FahCore requires undocumented functions from CUDA 3 that are removed in CUDA 4.

[Napoleon]

The CUDA wrapper code is also on GitHub:

Shellnutt2: cuda-wine-wrapper.

Got the wrappers and the G80 automator script from there... success!
For simplicity, I actually dropped the wrappers and symlinks to the same directory where the FAH executable and the script is - seemed simpler to me to do it that way.

For fun, I also tried playing with Win32 v7.3.6 tarball client (pause-on-start for now). I can telnet to the "wine FAHClient.exe" port 36330 just fine, but for some reason FAHControl can't connect to it over LAN from my Windows setup. Remote FahControl works just fine for the native Linux v7.3.6 tarball FAHClient, though. I've disabled all firewalls inside my LAN and everything is connected to a single LAN/WLAN switch, so I can't quite understand why telnet works for the "wine FAHClient.exe" thingy, but FAHControl is stumped.

It'd be great if I could use a single FAHControl as a one-stop-shop for monitoring and controlling. I'll experiment with wine'd v7.3.6 tarball client some more later on. However, I want to finish all pending work before that.

[Jesse_V]

For fun, I also tried playing with Win32 v7.3.6 tarball client (pause-on-start for now). I can telnet to the "wine FAHClient.exe" port 36330 just fine, but for some reason FAHControl can't connect to it over LAN from my Windows setup. Remote FahControl works just fine for the native Linux v7.3.6 tarball FAHClient, though. I've disabled all firewalls inside my LAN and everything is connected to a single LAN/WLAN switch, so I can't quite understand why telnet works for the "wine FAHClient.exe" thingy, but FAHControl is stumped.

It'd be great if I could use a single FAHControl as a one-stop-shop for monitoring and controlling. I'll experiment with wine'd v7.3.6 tarball client some more later on. However, I want to finish all pending work before that.

Umm, did you try https://fah-web.stanford.edu/projects/FAHClient/wiki/RemoteClients?

[Napoleon]

Sort of... basically I just copied a working config.xml from native Linux tarball client to the wine'd Windows tarball client. Then also tried removing and readding the remote Linux client in FahControl. I just added verbosity 5 to the wine'd client config.xml, maybe that'll tell me more about the connection issue once I get the chance to try again.

Anyway, it'll still take almost 23h for the native Linux client to finish. I'll let it run its course and reboot before messing around any further. I'm pretty hopeful about getting v7 to run under wine though - the telnet connection worked already. Most likely I've simply missed some trivial little tweak/setting somewhere.

[Jesse_V]

Sort of... basically I just copied a working config.xml from native Linux tarball client to the wine'd Windows tarball client. Then also tried removing and readding the remote Linux client in FahControl. I just added verbosity 5 to the wine'd client config.xml, maybe that'll tell me more about the connection issue once I get the chance to try again.

You aren't going to be able to connect to the v6 GPU client (even if it was running natively) in FAHControl since V7 introduced the remote socket connections that v6 lacks. The two will not be able to communicate with one another. This is why all the third-party remote monitors for the v6 clients did their own thing, and parsed the log to figure out what the v6 client was doing. V7's FAHClient has an API that FAHControl and Web Control hook into.

Anyway, it'll still take almost 23h for the native Linux client to finish. I'll let it run its course and reboot before messing around any further. I'm pretty hopeful about getting v7 to run under wine though - the telnet connection worked already. Most likely I've simply missed some trivial little tweak/setting somewhere.

So far as I know, running V7 through Wine like that is not possible. For me, I just run the v6 GPU client in the command-line. It's more Linux-like that way.

[Napoleon]

So far as I know, running V7 through Wine like that is not possible. For me, I just run the v6 GPU client in the command-line. It's more Linux-like that way.

Now that I actually tried the v7 legacy GPU side of things, I couldn't even get "wine FAHClient.exe --lspci" to run properly. No biggie, v6 seems to be working well and I can use HFM to monitor the shared directory. I just got the urge to try.

[TheWolf]

BTW not sure what OS of linux your running but you shouldn't need wine to run v7 FAHclient in a terminal.
Just type "FAHclient" in terminal hit enter and it runs.