Ubuntu Desktop Installation Guide for F@H

I like my boxen to "auto-login", so I always set that up. This is causing problems with VNC into the box, as the "keyring" feature requires the user on the host machine to type in a password to allow the vnc connection. Maybe we can update post #6 with the work-around for that problem.

To allow auto-login and vnc to work without typing password on host machine,

Applications/Accessories/Passwords and Encryption Keys
Right Click on "Passwords: default"
Type in Old Password
Leave New Password blank
Leave Confirm blank
Click OK
Confirm the security suggestion to allow reduced security.

Now when you reboot the user at the host does not need to authenticate VNC client connections
 
How about changing setting in Remote access (System --> Preferences --> Remote Desktop)
 
sbinh said:
How about changing setting in Remote access (System --> Preferences --> Remote Desktop)
Click to expand...

nope, it will still ask for a keyring pword on the host. The settings you suggest will be for client pwords. Keyring pwords are to protect the host security. Some such about protecting the hosts files from being viewed and changed by a remote connection.
 
I have been logging in to my 8P with xrdp for a few weeks now. I am running Ubuntu 11.04 using musky's guide and did not diviate from it. I log in using xrdp with my username and password the same as if I were logging into the machine physically with the keyboard. Other than the issue of the clipboards not being synced, and having to open the programs in the connected client, I have had no other issues. It is just like being on the machine.
 
I setup my box to bootup and go directly into desktop (did not setup to run fah at startup yet).
With changing settings in "remote desktop", when I access my box from winxp (using VNC) I only need to type in password (on client side) -- no need to go to server side to authenticate.
 
jebo_4jc said:
I think using WiFi creates the keyring issue.
Click to expand...

I hadn't thought of that. I am using a wifi client, the host is wired. I think this is worth adding to post #6. You and I can't be the only people who will run into this problem. Thoughts Musky?

I use mainly VNC around my home. I used to only use RDP, but that originally caused GPU units to bork, so I slowly shifted over to VNC. I've since found a way to prevent RDP from borking GPU WUs. I guess I could unify by installing xrdp like the post says, but most ubuntu builds come with VNC already installed, and in general VNC can do more. I really only utilize RDP on machines that the SWMBO needs to remote into. I keep it simple for her.
 
Last edited:
Actually just found out that having two network connections active can cause all sorts of s[H]it to happen, like not being able to SSH/VNC in from an external host on another network, to not being able to return WU's properly.

I had eth0 and eth1 wired up along with the IPMI port, all had fixed IP's but as soon as I disabled the second ethernet port everything started working.

wierd.
 
Biffa said:
Actually just found out that having two network connections active can cause all sorts of s[H]it to happen, like not being able to SSH/VNC in from an external host on another network, to not being able to return WU's properly.

I had eth0 and eth1 wired up along with the IPMI port, all had fixed IP's but as soon as I disabled the second ethernet port everything started working.

wierd.
Click to expand...

Hmmm.... something is not right. I have three interfaces on my two system( 1 dhcp with dns and 2 bonded ) and I have zero issues.
 
Of course it could just be that two interfaces incorrectly configured could cause an issue.. I can't rule out my ineptidude caused a problem :)
 
musky said:
[post=1037125467]Back to the top[/post]

Install "The Kraken" wrapper - for all multi-socket systems
A big thanks to tear for this. The original guide is here.
*EDIT - 10/30/11 - Updated for version 0.6
*EDIT - 5/20/12 - Updated for version 0.7-pre10
*EDIT - 5/22/12 - Updated to version 0.7-pre11

*NOTE: To get the most use out of the kraken, you need to have NUMA enabled (SR-2s, other 2p Intel boards) or node interleaving disabled (G34/C32/Socket F AMD systems). If you have a multi-processor board, you should have a bios setting for one or the other.

1. First, make sure the client has downed a core. The wrapper wraps the actual FAH core, so it doesn't do anything until you have a core downloaded.
2. Download the package:
Code: 
cd ~
wget http://darkswarm.org/thekraken-0.7-pre11.tar.gz
3. Untar it
Code: 
tar xvf thekraken-0.7-pre11.tar.gz
4. Install it
Code: 
cd thekraken-0.7-pre11
make
sudo make install
5. The Kraken is now available at /usr/bin/thekraken. To wrap your existing A3/A5 cores, move to your fah directory and run The Kraken with the -i flag:
Code: 
cd ~/fah
thekraken -i
You should see something like this:
Code: 
dave@bulldawg:~/fah$ thekraken -i
thekraken: The Kraken 0.7-pre11 (compiled Tue May 22 05:22:45 CDT 2012 by dave@bulldawg)
thekraken: Processor affinity wrapper for Folding@Home
thekraken: The Kraken comes with ABSOLUTELY NO WARRANTY; licensed under GPLv2
thekraken: performing installation to .
thekraken: /home/dave/fah/FahCore_a5.exe: wrapper succesfully installed
thekraken: descend into /home/dave/fah/backup and all other subdirectories [Y/n]? Y
thekraken: finished installation, 1 out of 1 files processed
6. Start the client. From another terminal window, type:
Code: 
top
If you top process looks something like this, "The Kraken" is working correctly:
Code: 
PID  USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
1984 dave       1  13 2789m 1.3g 3192 S 2384 22.8  16476:48 thekraken-FahCo

[post=1037125467]Back to the top[/post]
Click to expand...

I followed this almost to a "t"
downloaded the pre11 file, untared it, and found that it was pre14 instead. completed the install using pre14 instead of pre11. fired up folding on 12.04LTS and even before frame 1 was complete was greeted by engaging DLB. my second WU, no engage. OK well not garanteed. Look deeper..... Maybe I need to install with the -c autorestart=1..

I get:
thekraken: unknown configuration variable in 'autorestart=1'
and no install.:(

hmm where is thekraken.cfg? nope, don't have one... :confused:

What's going on here..... DLB did work, thekraken appears in top, if I install 'thekraken -i' it wraps the a3 and a5 cores located in fah

help
 
jfb9301 said:
I followed this almost to a "t"
downloaded the pre11 file, untared it, and found that it was pre14 instead. completed the install using pre14 instead of pre11. fired up folding on 12.04LTS and even before frame 1 was complete was greeted by engaging DLB. my second WU, no engage. OK well not garanteed. Look deeper..... Maybe I need to install with the -c autorestart=1..

I get:
thekraken: unknown configuration variable in 'autorestart=1'
and no install.:(

hmm where is thekraken.cfg? nope, don't have one... :confused:

What's going on here..... DLB did work, thekraken appears in top, if I install 'thekraken -i' it wraps the a3 and a5 cores located in fah

help
Click to expand...

The autorestart feature was removed in the 0.7-preXX versions of the kraken. With the DLB load feature working so well, the autorestart feature no longer seemed necessary.

Do you know which unit failed to engage DLB? What are the specs of the system? With -bigadv units (p8101, p6901, p6903, p6904), I have not seen DLB fail to engage within the 5 minute load period. On some systems, SMP units may not engage DLB reliably (as of 0.7-pre14).

EDIT: thekraken.cfg is only created if valid configuration parameters were used during the install of the kraken (thekraken -i)
 
hmm... valid install without autorestart and no thekraken.cfg.

machine is Alpha from my sig. WU is 6086 R1C65G196. So SMP probably not an issue if DLB doesn't engage. Just seems strange that there is no config file genereated.
 
Did you update your existing install with a new version of thekraken, or is this a new OS install? The simplest thing to do would be to uninstall thekraken then reinstall it. You always need to uninstall before you reinstall for an update. This guide assumes a new install of Ubuntu, do uninstalling would not be necessary.

From you fah directory:
Code: 
thekraken -u
Answer Yes to any questions, then do
Code: 
thekraken -i
That should fix you up.
 
but I've done that..... 5 times this morning... still no .cfg

new install as of yesterday when I built the computer....All it has ever had was 0.7 pre14
 
What firedfly is explaining -- you will not see thekraken.cfg after installation of 0.7-pre series (in typical configuration) and lack of thekraken.cfg is not an error.

So, if you see thekraken-FahCo* in top and thekraken.log reflects the version you installed there's nothing to worry about... or is there?
 
ahhh... that would do it.....

so it seems like everything is acting like expected and I don't actually have any problem. Live and learn.

thanks tear
 
musky said:
[post=1037125467]Back to the top[/post]

Misc Tweaks and Add-ons - these are all optional

=============================================================================
SSH - for connecting to and remote monitoring your Linux box
Boot to CLI
Once you have everything set up, there is no need to boot into the GUI. This will let you machine boot to a command line.
1. Open a terminal and type:
Code: 
sudo nano /etc/default/grub
Change this line:
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to this:
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash text"
Now, update grub:
Code: 
sudo update-grub
The next time you reboot, you will boot to a command line. To start the GUI, type:
Code: 
sudo service gdm start
To stop the GUI, type:
Code: 
sudo service gdm stop
===================================================================================


[post=1037125467]Back to the top[/post]
Click to expand...

for Ubuntu 11 and 12, the commands to start and stop the GUI after enabling CLI only seem to be
sudo service lightdm start
and
sudo service lightdm stop

but this post seems to say http://www.techienote.com/2012/05/how-to-disable-gui-boot-in-ubuntu-12-04.html
startx
is the correct command if you boot straight to CLI. I bring this up as I had my 12.04 box set up to boot CLI only and I could not get sudo service gdm start to work.
 
gdm = Gnome Desktop Manager. Newer version use Unity instead of Gnome, so I wouldn't expect "sudo service gdm start/stop/restart" to work with these non-Gnome versions. I'll try to do some testing and update the guide today.
 
EDIT*** nevermind ....all fixed too tired to set this up for the first time..lol
There are a couple of typos in the guide though. No biggie.
 
Last edited:
There's a missing ~ in one command line, and there's a couple of "1"'s should be "l"'s in some of the other lines. I won't be able to be more specific until I get home from work as there's a "suspicious embedded link" that's been "blocked for my protection";) on the first page, and a couple of others. We're also up to pre15 and the file url has to be typed that way. If you download pre11, after you untar it the files within are pre15. Would not work. Drove me nuts.
Not to worry, If I figured it out, anyone can!
Excellent guide Musky:cool: Couldn't have set my new rig up without it!
 
mflanaga said:
There's a missing ~ in one command line, and there's a couple of "1"'s should be "l"'s in some of the other lines. I won't be able to be more specific until I get home from work as there's a "suspicious embedded link" that's been "blocked for my protection";) on the first page, and a couple of others. We're also up to pre15 and the file url has to be typed that way. If you download pre11, after you untar it the files within are pre15. Would not work. Drove me nuts.
Not to worry, If I figured it out, anyone can!
Excellent guide Musky:cool: Couldn't have set my new rig up without it!
Click to expand...

Yeah, that damn tear and his constant updating of thekraken - I did fix the pre15 thing this morning.

I'll look for the others.
 
Damn me!

Yes, prereleases typically get redirected to the latest one
so users don't run into old (and known) bugs and don't
generate support calls.

0.7 is around the corner == Kraken aspect of the guide should
stabilize shortly.
 
Ok Musky, I think I found them, there's only two that I see (or can remember, still a little fuzzy after last nights brain drain):
Step 2 installing langouste: I believe (have not retried as I'm already running langouste)
"./langouste3 -l 8880 -D" ...wait *WOW* I think I know what happened. I JUST copy and pasted the command in quotes...it looks like a number 1 in the coded section of the step you posted, but when you paste it here, it shows as an l (as in "ell") which is correct. So I typed in a 1 as I thought it was, which did not work, but if you copy and paste the commands (which probably most do?) It comes out as an "ell".. weird. Some kind of font issue? Check it out.
Same on the line below it (step 3 section 4): "cd /home/<user>/fah/langouste && sudo -u <user> ./langouste3 -l 8880 -D"
That's all I see, the "missing" ~ I mentioned appears to have appeared by magic, or clarity of sleep...
 
Last edited:
jfb9301 said:
for Ubuntu 11 and 12, the commands to start and stop the GUI after enabling CLI only seem to be
sudo service lightdm start
and
sudo service lightdm stop

but this post seems to say http://www.techienote.com/2012/05/how-to-disable-gui-boot-in-ubuntu-12-04.html
startx
is the correct command if you boot straight to CLI. I bring this up as I had my 12.04 box set up to boot CLI only and I could not get sudo service gdm start to work.
Click to expand...

I just installed server 12.04 this time round and don't have to worry about the silly GUI anymore :D
 
I'm lazy to read everything, but there's no "special" additions to get an SR-2 running is there?
 
Patonb said:
I'm lazy to read everything, but there's no "special" additions to get an SR-2 running is there?
Click to expand...

Not really. You should do the base install + BFS + thekraken, and BFS isn't nearly as important as it used to be.
 
Is there a real time temp sensor, i'm using lm-sensor right now, that can be used through ssh?
 
Patonb said:
Is there a real time temp sensor, i'm using lm-sensor right now, that can be used through ssh?
Click to expand...

Anything that works in a terminal will work with SSH and a terminal emulatror like PuTTY.
 
Yha, thats how i'm running lm-sensor.

And a native insall has me 20k ppd boost over vm! 120k on 8101s
 
musky, it's about time I popped in to thank you for everything in your guide. My 4p has been running nearly flawlessly for almost a month.
Thanks for all you do!
 
Can this guide be updated for fah client 7.2.9? And the kraken guide updated to be compatible with that too?

Don't see the point of using 6.34 still...
 
You must log in or register to reply here.
Back
Top