Yeah you need at least mono 2.4
The guide needs to be updated then, as that is the version I got when following the directions.
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
Yeah you need at least mono 2.4
No it doesn't. If you are running Jaunty or Karmic the guide should grab version 2.4 or newer.The guide needs to be updated then, as that is the version I got when following the directions.
No it doesn't. If you are running Jaunty or Karmic the guide should grab version 2.4 or newer.
sudo apt-get install libmono-winforms2.0-cil
Encoding name 'Windows-1252' not supported
Do not use 9.10, the GPU performance is awful when the CPU client is running, I am currently trying to figure it out. Use 9.04 for maximum performance
In case you were wondering, the reason that I'm using the 7.10 toolkit is because the GPU2 wrapper was written for that version of the toolkit, newer toolkits do not work.
hi,
I'm guessing that using Mono probably means X is running and you would view HFM.net in that? Any chance that HFM could work without the GUI, just creating html pages for viewing?
My situation is that I'm using a Debian box remotely, and only have console access. Any hints on how to do this would be helpful. (I could do the HFM config on a box with GUI, make sure it works and then move the files over)
thanks!
PS - your guide looks great
Is the information here and at http://linuxfah.info/index.php?title=Main_Page#Linking_The_Toolkit still current for running a GPU task on Linux? No. And some of it is wrong. A better page seems to be http://www.gpu3.hostei.com/index.php/Main_Page. At least the links to the wrapper work.
I'm currently using the 260.19.29 drivers and have the 64 bit CUDA 3.2 toolkit installed. I'm using this to crunch SETI on my GPU and I'm reluctant to mess with that to get FAH running on my GPU (GTX 460) instead.
I wonder if it would be possible to run FAH on a VM guest running the correct version of the S/W. Anyone know anything about that?
thanks,
hank
Do you mean that the CPU cycles sacrificed to keep the GPU well fed just offset the gains from the GPU? That was something I wrestled with when running SETI on the GPU and Rosetta on the CPU. With the stock kernel, the only to keep the GPU busy was to restrict Rosetta to using only 3 of 4 cores. I switched to a real time kernel and upped to two instances of SETI on the GPU. That kept the GPU relatively well fed and I could run Rosetta on all 4 CPU cores, albeit at a 15% drop in CPU throughput due to the extra overhead of the RT kernel.Check to make sure it's worth it. I've found with some setups you net 0% gain from the GPU client.
It doesn't make any difference how many % cpu or gpu you're using. How many ppd does it make on the smp client running alone compared to running smp + gpu? That's all that matters. Optimize ppd, not % gpu and cpu. On your AMD x4, I imagine you will make more ppd running both since the 460 is going to make a lot more ppd than the x4.
You need a monitoring program (HFM) or a ppd calculator.