How-To: Ubuntu cruncher! Install and forget

Well i got couple of requests to make this kinda howto from this :)
The installion is pretty much this: Put cd in and click next but and fill couple forms if you fail in this you're an idiot :rofl:

First lets get the installion image file and burn it.

64X or i386 Images:

http://www.ubuntu.com/getubuntu/download

Imgburn is light'n fast burning software.

http://www.imgburn.com/

Or use the UNetbootin to make an booting installer stick.
UNetbootin dls the image files and makes the stick bootable automaticly, over 1GB sticks prefered.

http://unetbootin.sourceforge.net/

Lets begin!

select your language:


Now just press enter:


Next you should see window like this:

CLICK install that's what you wanna do

Just press next when these appear unless you really wanna read em!:






Now you need to select you HDD i prefer use whole disk if you're just planning to run cruncher :)


Now just will these forms as you like, Just remember to check: Login automaticly!:

You're done! Just press Install button and take cup of coffee this i'll take a while ~5-10min =P


I'll post little later about the boinc installion :)

OK! Installion done:
http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-20-55-48.png
Press restart now.

BOINC that's what we wanna see!

Locate console/terminal:

http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-21-00-16.png

Write:

Code:

---

1.
wget http://boinc.berkeley.edu/dl/boinc_6.6.4_i686-pc-linux-gnu.sh <- 32b
or
wget http://boinc.berkeley.edu/dl/boinc_6.6.4_x86_64-pc-linux-gnu.sh <- x64
or you can use any other earlier version instead of those i listed :)

2. sh boinc_6.6.4_x86_64-pc-linux-gnu.sh <- x64
or
sh boinc_6.6.4_i686-pc-linux-gnu.sh <-32b

With 64bit version remember to install ia32-libs
2a.
sudo apt-get install ia32-libs

*HINT* You can use tab in console ;) first letter of file *tab*

---

Now in console reads:
use /home/*username*/BOINC/run_manager to start BOINC

Lets not do that yet. Lets set the autostart :)

Autostart boinc on boot

Locate Sessions name service (System - > Preferences - > Sessions), just try follow what i do next :P
http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-21-09-30.png

Press Add
http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-21-11-12.png

Press browse
http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-21-11-28.png

http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-21-11-35.png

http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-21-11-40.png

Press add:
http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-21-11-45.png

If you have this kinda view front of you, well you've done it right.
http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-21-11-49.png

Time to reboot
The power buttons are located at right upper corner, restart your rig from there lets test does the autostart work and then you can setup your account data for boinc :)

If you see this window when the desktop has been loaded you can say success!

http://s0lid.bx.fi/kuva/xsubuntu/XSU...3-21-20-58.png

AND what comes to my low res i were runnin that OS from vmware :)

Here's some good guide made by karl_eller which can be found from end of second page:

Setting up Remote Desktop for Ubuntu + Monitoring and Overclocking with Ubuntu

I should also point out that this guide works great for installing Ubuntu on a USB disk, just select the USB disk when doing the "Guided, use the whole disk" part. Then on this screen, click "Advanced" and choose to install GRUB on the USB (usually something like sdb1) rather than HDD:
http://xs536.xs.to/xs536/09091/xsubu...0-44-34362.png
While this does technically put the swap partition on the USB drive, on my E7200 with 2Gb RAM, Linux doesn't use ANY of the Swap partition, and barely 1/4 of the RAM, so I'm not worried about constant swap read/writes destroying the USB drive.

Monitoring and Overclocking with Ubuntu
So you've followed s0lid's excellent guide so far, and you have your shiny new Ubuntu machine up and crunching. However now you want to be able to check on the PC without having to have a screen/keyboard attached to it, and most importantly you want to keep an eye on temps and be able to overclock. That's where this little guide comes in.

First:
Setting up Remote Desktop

OK, first things first, you are most likely going to want to set a static IP to your machine, if you haven't done so already. Static IP addresses make it much easier for configuring things like remote desktop, since the IP of the machine won't change when the PC and/or router restarts.
To do this, find the network icon in the top-right, right-click on it and click "Edit Connections", which should bring up a screen like this:
http://i113.photobucket.com/albums/n...s/ubuntu_1.png

Click on "Auto Ethernet" (or whatever your connection may be called), then click "Edit". Click the "IPv4 Settings" tab and select "Manual" from the method drop-down menu.
Now you'll need to enter in the desired IP address, netmask and default gateway. The IP address will depend on how your network is configured, although in most cases it will be something like 192.168.1.xxx (where xxx is between 1 and 255). I suggest starting from a high-ish number (eg 80 or higher) so that the router's DHCP still has plenty of IPs for automatic assignment. Netmask is usually 255.255.255.0, although that might be different depending on your network setup. Gateway is the IP of your modem, usually something like 192.168.1.1 or 10.0.0.1.
Once you've done that, enter the IP for your router (and any alternate IPs it may have) in the "DNS Servers" box, and you'll wind up with something that looks a little like this:
http://i113.photobucket.com/albums/n...s/ubuntu_2.png
Click "Apply" and then close the "Network Connections" window. To check it is configured properly, right-click the Network icon again, untick "Enable Networking", and then tick it again. If all is well, you should have net connection again, and the "Connection Information" window (again found by right-clicking the Network icon) should show the correct IP Address and Primary/Secondary DNS's.

Right, so that's your static IP set up. Now lets get some kind of remote desktop happening.

To do that, click: System > Preferences > Remote Desktop, like thus (although you most likely won't have boxes ticked):
http://i113.photobucket.com/albums/n...s/ubuntu_3.png
Just a random note, with this window, unlike a lot of other settings windows, changes are applied immediately upon ticking/unticking a box instead of waiting for Apply/Cancel, so if you're running this headless, make sure you don't untick "Allow other users to view your desktop" or "allow other users to control your desktop" while using a VNC program, otherwise you may find yourself locked out like I did :p:

So now, you want to tick "Allow other users to view your desktop", "allow other users to control your desktop", and make sure that "You must confirm each access to this machine" is UNticked. Password is optional (Remote Desktop will only accept connections from the local network by default, AFAIK), depending on how much you trust other users of your local network. You should wind up with a screen that looks like the above.
What this does is enable Ubuntu's built in VNC program, so you are obviously going to need a program to connect to a VNC server. I personally use UltraVNC which has a really nice little stand-alone VNC Viewer.
To double check everything is working, use your VNC program of choice to try connecting to the Ubuntu machine. I use the IP Address (hence setting a static IP), since I have isses connecting to hostnames on a mixed Windows/Linux network. If it works, contgratulations! If it doesn't, you'll need to re-check your network settings.

Temperature monitoring

So we're accessing this machine remotely and it's crunching 24/7. But there is a heat-wave coming, or you're wanting to OC a bit, and you want to be able to check temperatures. Luckily, Linux has you covered. Open up a terminal window, and enter the following:

Code:

---

sudo apt-get install lm-sensors gkrellm

---

enter your root password and answer "y" to any prompts.
This installs the lm-sensors package (one of the most common, and really the only, temp sensor package in Ubuntu) and the GNU Krell Monitors, a nice little sidebar-like program that reads lm-sensors.
If you have any problems installing by the terminal, you can install them via the Synaptics Package Manager. Click System > Administration > Synaptics Package Manager, search for the 2 packages ("lm-sensors" and "gkrellm"), mark them for install and then click "apply".

Now you have them installed, you need to configure lm-sensors. In a terminal window, enter:

Code:

---

sudo sensors-detect

---

It will now ask you a bunch of prompts as to if it should scan or load certain things, you will want to enter "Yes" to all of them. Once it has finished scanning, it will give you a summary and ask you to press Enter a couple of times to continue. Do so. You'll end up with a terminal that looks a little like this:
http://i113.photobucket.com/albums/n...s/ubuntu_4.png
Pay attention to the stuff between the two "#----cut here----", these are the sensors that have been detected on your motherboard. They will vary from board-to-board, although all of them should have at least "coretemp" in common. Enter "yes" for the last prompt, and you've finished sensors-detect.

Now all that does is detect what sensors are available, it doesn't actually install the modules required to read them (despite what it might say about editing /etc/modules), you'll need to enter each one manually using:

Code:

---

sudo modprobe [module name]

---

For example, on my MSI P35 Neo2-FR, sensors-detect found "f71882fg" and "coretemp", so I entered:

Code:

---

sudo modprobe f71882fg
sudo modprobe coretemp

---

Once you've done that, check that lm-sensors is working, by typing

Code:

---

sensors

---

into a terminal. You should end up with something that looks a little like:
http://i113.photobucket.com/albums/n...s/ubuntu_5.png
Of course the actual output will vary a lot depending on what sensors your motherboard has, but you can at least see the temps for each core, vCore and System (usually the Northbridge, but YMMV). As you can see, not all the voltage readings are entirely trustworthy, depending on what sensors you have and what your board can monitor. You'll need to figure out what can be believed and what can be ignored. In my case, only vCore reads even remotely close to what it should be, so I'm ignoring the rest of the voltage readings.

OK, so that's lm-sensors installed and configured. But terminals are boring, and it doesn't update, so we need something that can read lm-sensors real-time and give us some nice pretty graphs and stuff. This is where Gkrellm comes in. You can launch it by clicking Applications > System Tools > GKrellM System Monitor.

To open the Configuration, either click anywhere on the GKrellM window and hit F1, or right-click on the hostname and click "Configuration". The sensors and other items can be found by expanding "Builtins". I won't bother going into what different things do and how they should be set up, as it'll add way too much to this already kinda lengthy How-to, and I'm sure most of you can figure it out.

This is how mine looks:
http://i113.photobucket.com/albums/n...s/ubuntu_6.png

Overclocking and stress-testing tools

When it comes to tools for OC'ing, Ubuntu doesn't have a whole lot in it's repositories. However tools do exist, and they are pretty handy. Two that I use are PerlMon, a CPU-Z equivalent, and SysTester, which basically runs X threads of Y loops of Z length SuperPi, and error checks the whole way, rather than making you validate a checksum at the end. I find around 30 loops of 8M digits on all cores gives you a fairly good indication as to if it's WCG stable or not. But as with all OC'ing, YMMV, and the amount of time taken to complete these loops will vary a lot depending on your clock speed.

------------------

Hopefully I was able to help people out with this little addition to s0lid's existing Ubuntu guide.

Eller

I would like to add a little something ... you want your session to auto-start run_client not run_manager. That way you can open the manager whenever you want and close it again without killing the client or wasting cycles making pretty pictures.

I'm getting ready to set up a couple of crunchers and I'll try this out.

Thread stuck.. Thanks s0lid!:up:

Yeah, thanks, as some folks apparently had trouble this is long overdue! :up:

great guide solid :up: edit the title tho to add the "h" in cruncher

Thanks solid. The linux noob in me gave up far to early! I now recognise what I was doing wrong. Can this work with BoincView?

Great guide, 8.04 is a lot faster than 8.10 in Folding so I am sure it would be in WCG also. Something about the newer kernel is slower...

Sweeeeet. :up: No time now, but I'll be back.....:yepp:

You can also get the Boinc cient from the applications>add/remove it may not be the newest though.

That's the same one you get if you open the terminal and enter "sudo apt-get install boinc-client boinc-manager" (or do it through the synaptic package manager), trouble is, they never update it between OS releases.

Does the 64 bit client still require you to install the ia32libs in order to work ? I guess it's been a little bit since I've done a new one. Before, you needed to do that in order to run the work units, which are 32 bit. I believe some projects may now have native 64 bit code but some not.
Also, an editing idea, include a link to the ubuntu download page instead of directly to the .iso files for the current versions.

Quote:

---

Originally Posted by don_xvi

Does the 64 bit client still require you to install the ia32libs in order to work ? I guess it's been a little bit since I've done a new one. Before, you needed to do that in order to run the work units, which are 32 bit. I believe some projects may now have native 64 bit code but some not.
...

---

The last time I did a fresh install they weren't required, but that could be that they were already installed by default, too. If in doubt, install them.

"sudo apt-get install ia32-libs"

Quote:

---

Originally Posted by D_A

I would like to add a little something ... you want your session to auto-start run_client not run_manager. That way you can open the manager whenever you want and close it again without killing the client or wasting cycles making pretty pictures.

---

Good point btw!

Quote:

---

Originally Posted by 64dragon

great guide solid :up: edit the title tho to add the "h" in cruncher

---

Fixd =)

Quote:

---

Originally Posted by emuexport

Thanks solid. The linux noob in me gave up far to early! I now recognise what I was doing wrong. Can this work with BoincView?

---

Well i don't know for sure, i've never used boincview before.

Quote:

---

Originally Posted by don_xvi

Does the 64 bit client still require you to install the ia32libs in order to work ? I guess it's been a little bit since I've done a new one. Before, you needed to do that in order to run the work units, which are 32 bit. I believe some projects may now have native 64 bit code but some not.
Also, an editing idea, include a link to the ubuntu download page instead of directly to the .iso files for the current versions.

---

64bit client installs w/o any addional libs :D

Quote:

---

Originally Posted by D_A

That's the same one you get if you open the terminal and enter "sudo apt-get install boinc-client boinc-manager" (or do it through the synaptic package manager), trouble is, they never update it between OS releases.

---

Just tried to check which version of boinc reposities have. Couldn't find :shrug:

Quote:

---

Originally Posted by s0lid

Just tried to check which version of boinc reposities have. Couldn't find :shrug:

---

8.04 is still pushing 5.10.45

Go to GetDeb is where I get mine its a little newer.. :up:

I seem to remeber I had to install the ia32libs last time I installed Ubuntu.

I would suggest to do it anyway (to be safe) by typing 'sudo apt-get install ia32-libs'

This is a great sticky but I would like to know 2 things.

Is there a good app like coretemp for ubuntu?

Secondly is there also something as Prime95 to test the cpu because i just build a Q6600 cruncher on ubuntu and want to clock it but I don't have/ can't find the apps like for windows.

Thanks.

I use a monitoring applet called gKrellm .
http://members.dslextreme.com/users/...m/gkrellm.html

Thanks i got gKrellm running now but it does not detect the temps. I have installed the lib package for the lm-sensorss with detect-sensors he finds my sensors and with sensors in the terminal it also gives me some temperature.

I'm just such a noob at this linux stuff.

Quote:

---

Originally Posted by Ramaistro

Thanks i got gKrellm running now but it does not detect the temps. I have installed the lib package for the lm-sensorss with detect-sensors he finds my sensors and with sensors in the terminal it also gives me some temperature.

I'm just such a noob at this linux stuff.

---

read here from post #22
http://www.xtremesystems.org/forums/...ghlight=ubuntu

Dead image links? Only two images took forever to load. If you like, I can host these images for you.

Quote:

---

Originally Posted by Ashraf

Dead image links? Only two images took forever to load. If you like, I can host these images for you.

---

XS.to is slow as hell i see... wait a sec i'll host these at BX.fi :)

E: 2nd posts pics moved to new server, need to dl pics from 1st post, they're not on this rig anymore :shakes:

Looks like you edited this today-thanks a million. I will be getting the sammies up and running on this and this guide is the bestis!!!

Ubuntu 9.04 is out now. I've downloaded it, gonna try it out soon.

It runs faster than Ubuntu 8.10 , but still is slower than Fedora or Suse.

Quote:

---

Originally Posted by Jaco

read here from post #22
http://www.xtremesystems.org/forums/...ghlight=ubuntu

---

Thanks Jaco,

it is all workig fine now. Just need to find out how to run without a videocad installed ( pc just dosn't boot, vnc is set-up and working with card in it. )

Some machines just won't boot without a vid card and that's all there is to it, others just keep on truckin' and seem to not care at all. I think it depends on the BIOS but I don't really know.

I am downloading Ubuntu 9.04 for my sossaman rig's right now-very excited will finally get these baby's up and running. I have onboard video for these but once I have them crunching video it will be of no concern as these babies are dedicated crunchers; so once there set up that is that

Ok so I am getting ready to install Linux on my systems- and downloaded 9.04. I unzipped the file and within are a few folders- my ?? question is what are the necessary ones that I need to install the OS. Thanks

http://i30.photobucket.com/albums/c3...547/Fam_OS.jpg

Quote:

---

Originally Posted by CaptMorgan

Ok so I am getting ready to install Linux on my systems- and downloaded 9.04. I unzipped the file and within are a few folders- my ?? question is what are the necessary ones that I need to install the OS. Thanks

[IMG]SNIP[/IMG]

---

Didnt you download it as an ISO? maybe you have extracted the files from the ISO image?

If so just burn the image to disk and you're right to go!

I see the ISO linux in the file up above- so that must be the 1 I need to put on disk. Thank you

Quote:

---

Originally Posted by CaptMorgan

I see the ISO linux in the file up above- so that must be the 1 I need to put on disk. Thank you

---

No worries! :D

WinRar opens everything nowadays right! As well as associating itself with all kinds of files making it look like a zip file!

Quote:

---

Originally Posted by emuexport

No worries! :D

WinRar opens everything nowadays right! As well as associating itself with all kinds of files making it look like a zip file!

---

Ok maybe I confused myself-so I should just put the original file I downloaded from the Ubuntu website on disk; which is the one on the bottom left of the pic above. I had justunzipped it when I got it and everything plus the file itself I had put into a folder on my desktop.

Quote:

---

Originally Posted by CaptMorgan

Ok maybe I confused myself-so I should just put the original file I downloaded from the Ubuntu website on disk; which is the one on the bottom left of the pic above. I had justunzipped it when I got it and everything plus the file itself I had put into a folder on my desktop.

---

Here's simple how-to:
1. DL the ISO image which you want.
2. Don't open it/unzip it anywhere.
3. DL & Install Imgburn
4. Open Imgburn
5. Press "Write image file to disc"
6. Select the ISO file which you just DLd in imgburn (Little folder icon with zooming lens in it.)
7. Then burn and you're done :)

Thank you sOlid that did the trick

Well after succesfully running my firt ubuntu cruncher for over a month now I have builded my second one. ( I7 920@3.9 ) Installing went without a problem but now the following.

- The pc is connected thru wireless so every reboot it will requir for the password of the network or atleast some stupid keyring bull I do not want to act up.

So how to disable / remove the keyring and let the pc auto connect. ( tried searching the inet but didn't find anything clear enough for me to understand)

- Second problem/issue the pc doesn't want to install new packages anymore. I downloaded gkrellm to monitor but at install is loads some stuff and then says E: could not find package ...........

What could be wrong I did not change anything I can recall.

- As third I let Boinc manager auto start at startup but for some stupid reason at startup it doesn't start boinc so nothing is happening. Now if I shutdown boincmanager and start it again after the pc is done booting completly it wil work just fine and starts boinc also.

And again what could this be?

You don't want to start the boinc manager at boot time, you should be starting the boinc client (using the run_client script). As for the missing package, try changing the server you are downloading from (it's a setting in the 'software sources' menu). I have no idea about the stupid wireless thing, I'm sorry. I gave up on mine and went for a crawl under the house to run a cable instead.

Quote:

---

Originally Posted by D_A

You don't want to start the boinc manager at boot time, you should be starting the boinc client (using the run_client script). As for the missing package, try changing the server you are downloading from (it's a setting in the 'software sources' menu). I have no idea about the stupid wireless thing, I'm sorry. I gave up on mine and went for a crawl under the house to run a cable instead.

---

Tnx for the reply. Found out WICD is a great alternative for network manager and will auto connect without all the prompting.

Trying the run-cleint script thingy now.

About the package installation what server and how to change it?

Quote:

---

Originally Posted by Ramaistro

About the package installation what server and how to change it?

---

Click through (in English) System > Administration > Software Sources >enter your password > click the tab "Ubuntu Software" then in the middle of the window there is a menu titled "Download from:" followed by the name of the current server. Click that and you will be able to choose either your current server or the Main Server. Pick the other one and then let it reload the package lists.

Quote:

---

Originally Posted by D_A

Click through (in English) System > Administration > Software Sources >enter your password > click the tab "Ubuntu Software" then in the middle of the window there is a menu titled "Download from:" followed by the name of the current server. Click that and you will be able to choose either your current server or the Main Server. Pick the other one and then let it reload the package lists.

---

Well I did that and got all errors smacked at me that there were problems downloading from some links. It seems like some links I had added when I was trying to following a how to install for gkrellm as that wasn't working.

B.t.w. boinc runs fine now starting that cript instead of the manager.

Ok my I7 is up and running for a few days now and i'm allready disappointed. It seems to score about 25% lower then my other I7 on Vista 64bit. My pc at home is @ 3.8 and my new one is @ 3.9 What could this be ?

So I finally got my Sammy up and running and did get BOINC up, but I was not able to get it running at boot up. Regardless once I got over the Wall of Noob with Ubuntu and installing software/programs its nice to get this baby up!!

Since this is an Ubuntu ?? I thought I would post here, though it's on my Sossaman rig. I got 4 gb of ram and it seems to be reading only 3.4 . This is and was my very first install of Linux on a new machine, once it seemed to be working Ok ehough I loaded Boinc up on it just want to get the kinks out and have it running efficiently. Also while I am at it are there any temps programs out? shoot I am running 9.04

Quote:

---

Originally Posted by CaptMorgan

Since this is an Ubuntu ?? I thought I would post here, though it's on my Sossaman rig. I got 4 gb of ram and it seems to be reading only 3.4 . This is and was my very first install of Linux on a new machine, once it seemed to be working Ok ehough I loaded Boinc up on it just want to get the kinks out and have it running efficiently. Also while I am at it are there any temps programs out? shoot I am running 9.04

---

Sounds like you got the 32 bit version of Ubuntu. It shows all 6 gigs of my setup with 64 bit.

Ica only use 32-bit because of the type of system the Sossaman's are

Quote:

---

Originally Posted by s0lid

Well i got couple of requests to make this kinda howto from this :)
The installion is pretty much this: Put cd in and click next but and fill couple forms if you fail in this you're an idiot :rofl:

First you should DL the cd disk and burn.

64X or normal i386

8.10s
I386: http://ubuntu.media.mit.edu/ubuntu-r...sktop-i386.iso
X64: http://ubuntu.media.mit.edu/ubuntu-r...ktop-amd64.iso

Or you can select 8.04 and maybe from some other ftp :)
http://www.ubuntu.com/getubuntu/download

Imgburn is light'n fast burning software. No more now :)

Lets begin!

select your language:
http://xs536.xs.to/xs536/09091/xsubu...0-32-28222.png

Now just press enter:
http://xs536.xs.to/xs536/09091/xsubu...0-32-57889.png

Next you should see window like this:
http://xs536.xs.to/xs536/09091/xsubu...0-41-39616.png
CLICK install that's what you wanna do

Just press next when these appear unless you really wanna read em!:
http://xs536.xs.to/xs536/09091/xsubu...0-43-09752.png

http://xs536.xs.to/xs536/09091/xsubu...0-43-22328.png

http://xs536.xs.to/xs536/09091/xsubu...0-43-30771.png

Now you need to select you HDD i prefer use whole disk if you're just planning to run cruncher :)
http://xs536.xs.to/xs536/09091/xsubu...0-43-46523.png

Now just will these forms as you like, Just remember to check: Login automaticly!:
http://xs536.xs.to/xs536/09091/xsubu...0-44-24372.png

You're done! Just press Install button and take cup of coffee this i'll take a while ~5-10min =P
http://xs536.xs.to/xs536/09091/xsubu...0-44-34362.png

I'll post little later about the boinc installion :)

---

Thanks for the easy How-to guide. I have it working very nice! :up:

I should also point out that this guide works great for installing Ubuntu on a USB disk, just select the USB disk when doing the "Guided, use the whole disk" part. Then on this screen, click "Advanced" and choose to install GRUB on the USB (usually something like sdb1) rather than HDD:
http://xs536.xs.to/xs536/09091/xsubu...0-44-34362.png
While this does technically put the swap partition on the USB drive, on my E7200 with 2Gb RAM, Linux doesn't use ANY of the Swap partition, and barely 1/4 of the RAM, so I'm not worried about constant swap read/writes destroying the USB drive.

Monitoring and Overclocking with Ubuntu
So you've followed s0lid's excellent guide so far, and you have your shiny new Ubuntu machine up and crunching. However now you want to be able to check on the PC without having to have a screen/keyboard attached to it, and most importantly you want to keep an eye on temps and be able to overclock. That's where this little guide comes in.

First:
Setting up Remote Desktop

OK, first things first, you are most likely going to want to set a static IP to your machine, if you haven't done so already. Static IP addresses make it much easier for configuring things like remote desktop, since the IP of the machine won't change when the PC and/or router restarts.
To do this, find the network icon in the top-right, right-click on it and click "Edit Connections", which should bring up a screen like this:
http://i113.photobucket.com/albums/n...s/ubuntu_1.png

Click on "Auto Ethernet" (or whatever your connection may be called), then click "Edit". Click the "IPv4 Settings" tab and select "Manual" from the method drop-down menu.
Now you'll need to enter in the desired IP address, netmask and default gateway. The IP address will depend on how your network is configured, although in most cases it will be something like 192.168.1.xxx (where xxx is between 1 and 255). I suggest starting from a high-ish number (eg 80 or higher) so that the router's DHCP still has plenty of IPs for automatic assignment. Netmask is usually 255.255.255.0, although that might be different depending on your network setup. Gateway is the IP of your modem, usually something like 192.168.1.1 or 10.0.0.1.
Once you've done that, enter the IP for your router (and any alternate IPs it may have) in the "DNS Servers" box, and you'll wind up with something that looks a little like this:
http://i113.photobucket.com/albums/n...s/ubuntu_2.png
Click "Apply" and then close the "Network Connections" window. To check it is configured properly, right-click the Network icon again, untick "Enable Networking", and then tick it again. If all is well, you should have net connection again, and the "Connection Information" window (again found by right-clicking the Network icon) should show the correct IP Address and Primary/Secondary DNS's.

Right, so that's your static IP set up. Now lets get some kind of remote desktop happening.

To do that, click: System > Preferences > Remote Desktop, like thus (although you most likely won't have boxes ticked):
http://i113.photobucket.com/albums/n...s/ubuntu_3.png
Just a random note, with this window, unlike a lot of other settings windows, changes are applied immediately upon ticking/unticking a box instead of waiting for Apply/Cancel, so if you're running this headless, make sure you don't untick "Allow other users to view your desktop" or "allow other users to control your desktop" while using a VNC program, otherwise you may find yourself locked out like I did :p:

So now, you want to tick "Allow other users to view your desktop", "allow other users to control your desktop", and make sure that "You must confirm each access to this machine" is UNticked. Password is optional (Remote Desktop will only accept connections from the local network by default, AFAIK), depending on how much you trust other users of your local network. You should wind up with a screen that looks like the above.
What this does is enable Ubuntu's built in VNC program, so you are obviously going to need a program to connect to a VNC server. I personally use UltraVNC which has a really nice little stand-alone VNC Viewer.
To double check everything is working, use your VNC program of choice to try connecting to the Ubuntu machine. I use the IP Address (hence setting a static IP), since I have isses connecting to hostnames on a mixed Windows/Linux network. If it works, contgratulations! If it doesn't, you'll need to re-check your network settings.

Temperature monitoring

So we're accessing this machine remotely and it's crunching 24/7. But there is a heat-wave coming, or you're wanting to OC a bit, and you want to be able to check temperatures. Luckily, Linux has you covered. Open up a terminal window, and enter the following:

Code:

---

sudo apt-get install lm-sensors gkrellm

---

enter your root password and answer "y" to any prompts.
This installs the lm-sensors package (one of the most common, and really the only, temp sensor package in Ubuntu) and the GNU Krell Monitors, a nice little sidebar-like program that reads lm-sensors.
If you have any problems installing by the terminal, you can install them via the Synaptics Package Manager. Click System > Administration > Synaptics Package Manager, search for the 2 packages ("lm-sensors" and "gkrellm"), mark them for install and then click "apply".

Now you have them installed, you need to configure lm-sensors. In a terminal window, enter:

Code:

---

sudo sensors-detect

---

It will now ask you a bunch of prompts as to if it should scan or load certain things, you will want to enter "Yes" to all of them. Once it has finished scanning, it will give you a summary and ask you to press Enter a couple of times to continue. Do so. You'll end up with a terminal that looks a little like this:
http://i113.photobucket.com/albums/n...s/ubuntu_4.png
Pay attention to the stuff between the two "#----cut here----", these are the sensors that have been detected on your motherboard. They will vary from board-to-board, although all of them should have at least "coretemp" in common. Enter "yes" for the last prompt, and you've finished sensors-detect.

Now all that does is detect what sensors are available, it doesn't actually install the modules required to read them (despite what it might say about editing /etc/modules), you'll need to enter each one manually using:

Code:

---

sudo modprobe [module name]

---

For example, on my MSI P35 Neo2-FR, sensors-detect found "f71882fg" and "coretemp", so I entered:

Code:

---

sudo modprobe f71882fg
sudo modprobe coretemp

---

Once you've done that, check that lm-sensors is working, by typing

Code:

---

sensors

---

into a terminal. You should end up with something that looks a little like:
http://i113.photobucket.com/albums/n...s/ubuntu_5.png
Of course the actual output will vary a lot depending on what sensors your motherboard has, but you can at least see the temps for each core, vCore and System (usually the Northbridge, but YMMV). As you can see, not all the voltage readings are entirely trustworthy, depending on what sensors you have and what your board can monitor. You'll need to figure out what can be believed and what can be ignored. In my case, only vCore reads even remotely close to what it should be, so I'm ignoring the rest of the voltage readings.

OK, so that's lm-sensors installed and configured. But terminals are boring, and it doesn't update, so we need something that can read lm-sensors real-time and give us some nice pretty graphs and stuff. This is where Gkrellm comes in. You can launch it by clicking Applications > System Tools > GKrellM System Monitor.

To open the Configuration, either click anywhere on the GKrellM window and hit F1, or right-click on the hostname and click "Configuration". The sensors and other items can be found by expanding "Builtins". I won't bother going into what different things do and how they should be set up, as it'll add way too much to this already kinda lengthy How-to, and I'm sure most of you can figure it out.

This is how mine looks:
http://i113.photobucket.com/albums/n...s/ubuntu_6.png

Overclocking and stress-testing tools

When it comes to tools for OC'ing, Ubuntu doesn't have a whole lot in it's repositories. However tools do exist, and they are pretty handy. Two that I use are PerlMon, a CPU-Z equivalent, and SysTester, which basically runs X threads of Y loops of Z length SuperPi, and error checks the whole way, rather than making you validate a checksum at the end. I find around 30 loops of 8M digits on all cores gives you a fairly good indication as to if it's WCG stable or not. But as with all OC'ing, YMMV, and the amount of time taken to complete these loops will vary a lot depending on your clock speed.

------------------

Hopefully I was able to help people out with this little addition to s0lid's existing Ubuntu guide.

Eller

Great add :up:
Can add that post to first posts?

By all means, feel free to add it to the first posts, since it'll make things a lot easier to find and follow :p:

Eller

Little thread resurrection.
Just installed Ubuntu 9.10 from USB stick, well i can only say that the time you need to install this os is LESS than 5min :shocked:!
And boot time is just unbeatable, just little over 1min with Athlon II 245!

There's very easy way to make a bootable installer stick, a program called UNetbootin.

I run Ubuntu on the 2 Opterons and I like it. It is easy and once setup it just keeps running.

I have it setup on a USB stick so I can keep crunching if I loose a HD.

Why isn't this thread stickied any more? Daveeeeeeeeeeeeee!

Hello sOlid I did a fresh install on my sammies, well I got 1 going cause I am having problems with my switch(but that is another story:shakes:). I followed the "instructions" and got BOINC 6.10.17 installed but your images are missing on how to get The BOINC manager to startup with the computer?
If any1 could help:) I appreciate it- I do know you can desiganate The BOINC Manager to start up but I tried the manager I had installed but when I restarted it blank:confused:. So I had to start manually and left it runnin for now in the dungeon of crunching;)

Just trying to remember:
System preferences etc -> Sessions -> Add there new program which starts at boot -> boincmgr... hopefully this helps at all. otherwise i'll be installing ubu again to virtualbox :P

Newer versions is System>Preferences>Startup Applications
Older versions is System>Preferences>Sessions

I think we have a problem Houston. The first 10 or so images are like this:


http://img.techpowerup.org/100304/0001111111.jpg

Several others are broken.

Quote:

---

Originally Posted by s0lid

Just trying to remember:
System preferences etc -> Sessions -> Add there new program which starts at boot -> boincmgr... hopefully this helps at all. otherwise i'll be installing ubu again to virtualbox :P

---

No. Don't do that. Firstly, you need to run the client at login (not the manager) and second you need to use the "run_client" script (don't run either the client of the manager directly). Run the "run_manager" script to start the manager, but you don't need to do that unless you're managing BOINC locally from that machine, otherwise it's a waste of system resources.

I am using BOINC advanced view, because i seeing kind of guy, but when I go to Advanced > Options > I remember there used to be a box you check where you could tell BOINC to bot on start up. It is no longer there of course it might be starting up with the computer and I just do't realize it :)- and obviously it won't matter in the end cause I won't be turning off this little sucka anyways!!

I don't recall ever seeing that setting in the linux version, are you sure? You weren't using the Windows or Mac version were you? The different security systems between distros might make that sort of thing ... difficult.

Each time I open the boinc manager it closes if I hit attach to project...

Quote:

---

user@vinas:~/Downloads/BOINC$ uname -a
Linux vinas 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010 x86_64 GNU/Linux


user@vinas:~/Downloads/BOINC$ ./run_manager
04:51:26 PM: Error: Memory VFS already contains file 'webexternallink.xpm'!
04:51:26 PM: Error: Memory VFS already contains file 'nvidiaicon.xpm'!
04:51:26 PM: Error: Memory VFS already contains file 'atiicon.xpm'!
04:51:26 PM: Error: Memory VFS already contains file 'multicore.xpm'!
SIGSEGV: segmentation violation
Stack trace (59 frames):
./boincmgr(boinc_catch_signal+0x43)[0x5345f3]
/lib/libpthread.so.0[0x7f4c6576f190]
./boincmgr[0x4b049a]
./boincmgr[0x4aff17]
./boincmgr[0x71fe3c]
./boincmgr[0x7205af]
./boincmgr[0x7208a3]
./boincmgr[0x5316da]
./boincmgr[0x71fe3c]
./boincmgr[0x7205af]
./boincmgr[0x7208a3]
./boincmgr[0x638136]
./boincmgr[0x72084d]
./boincmgr[0x5c3f1d]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e)[0x7f4c66f295ae]
/usr/lib/libgobject-2.0.so.0[0x7f4c66f3ef70]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7f9)[0x7f4c66f3fd39]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83)[0x7f4c66f40283]
/usr/lib/libgtk-x11-2.0.so.0[0x7f4c690d4af5]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e)[0x7f4c66f295ae]
/usr/lib/libgobject-2.0.so.0[0x7f4c66f3e29c]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7f9)[0x7f4c66f3fd39]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83)[0x7f4c66f40283]
/usr/lib/libgtk-x11-2.0.so.0[0x7f4c690d37ad]
/usr/lib/libgtk-x11-2.0.so.0[0x7f4c69182728]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e)[0x7f4c66f295ae]
/usr/lib/libgobject-2.0.so.0[0x7f4c66f3e64d]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x68c)[0x7f4c66f3fbcc]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83)[0x7f4c66f40283]
/usr/lib/libgtk-x11-2.0.so.0[0x7f4c6928971f]
/usr/lib/libgtk-x11-2.0.so.0(gtk_propagate_event+0xe3)[0x7f4c6917acd3]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main_do_event+0x1f3)[0x7f4c6917bca3]
/usr/lib/libgdk-x11-2.0.so.0[0x7f4c68df0cec]
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x22e)[0x7f4c6667fbce]
/lib/libglib-2.0.so.0[0x7f4c66683598]
/lib/libglib-2.0.so.0(g_main_loop_run+0x1a5)[0x7f4c666839f5]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xa7)[0x7f4c6917c177]
./boincmgr[0x656a00]
./boincmgr[0x5cbf25]
./boincmgr[0x531ba8]
./boincmgr[0x52da77]
./boincmgr[0x4bf394]
./boincmgr[0x71fe3c]
./boincmgr[0x7205af]
./boincmgr[0x7208a3]
./boincmgr[0x720c3c]
./boincmgr[0x6ab6e4]
./boincmgr[0x5e2196]
./boincmgr[0x58aabb]
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x22e)[0x7f4c6667fbce]
/lib/libglib-2.0.so.0[0x7f4c66683598]
/lib/libglib-2.0.so.0(g_main_loop_run+0x1a5)[0x7f4c666839f5]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xa7)[0x7f4c6917c177]
./boincmgr[0x656a00]
./boincmgr[0x5e2094]
./boincmgr[0x6d76b0]
./boincmgr[0x44d1d2]
/lib/libc.so.6(__libc_start_main+0xfd)[0x7f4c64c64abd]
./boincmgr[0x4202e9]

Exiting...

---

Did you install both the BOINC manager and the client?

To install the client, open the terminal and type:

sudo apt-get install boinc-client

I had one doing that yesterday. You can get around this by doing it from the command line.

as root (or sudo) enter: boinccmd --project_attach http://www.worldcommunitygrid.org <your id from WCG site>

To get your id go to the WCG site, then to My Profile and it's down the bottom of the page.

Edit: didn't think to check if he'd installed the client

I have no idea as to what I've been doing wrong on the Sammy, but the Ubuntu installer won't allow me to create partitions / use my hdd. Gparted works as intended. I installed windows xp as last resort, but I'd rather be running linux on it :(

I've never seen a hdd yet that it couldn't handle, unless there was something seriously wrong with it.

What does it say when you try?

It just won't show anything in the box. I could install it fine on a 250gb HDD with bad clusters, changed the HDD to this good 320gb and can't make it work. :shrug:

Edit: I tried with and without partitions on the hdd as well. Gparted will always show the drive correctly, but the installer will not allow me to select it :(

Quote:

---

Originally Posted by D_A

I had one doing that yesterday. You can get around this by doing it from the command line.

as root (or sudo) enter: boinccmd --project_attach http://www.worldcommunitygrid.org <your id from WCG site>

To get your id go to the WCG site, then to My Profile and it's down the bottom of the page.

Edit: didn't think to check if he'd installed the client

---

Thanks guys. Unfortunately apt can't find the client for me so I had to use the one on the WCG website. After that didn't work I found the test version over on the BOINC website... Not all is lost though because the command above worked like a charm! :up:

Thanks much! Now my work computer will happily crunch away... Time to get my main rig online (luckily this one is windows) :rofl:

Thanks again!

If you got the manager from the repositories then you have access to the client as well. ("sudo apt-get install boinc-client" is the command) If not then you don't have the right repository enabled (it's in the "Universe" repo, from memory. You have to enable that through the software sources menu.)

@solid: VERY USEFUL mate! My rig has boinc installed via synaptic but it is somehow stuck. Will fix it tomorrow :)

thanks

I just installed Boinc on Ubuntu 10.4 beta 2 yesterday. This distro has Boinc in the Ubuntu Software Center. It couldn't be easier to install from there.
Just make sure you choose Boinc Core, Boinc Manager, and the metapackage for Boinc.

are the project servers down? cuz i'm getting that in the messages box after i followed this guide (really nice guide btw) but i'm not crunching yet :shrug:


update: now the message box is saying: scheduler request failed: peer certificate cannot be authenticated with known CA certificates

I'm not getting that message. :shrug:

Are you getting anything about certificates in the messages tab?

yes i am

You'll need to install the right ca-cetificates file then. Someone at Ubuntu, in their "infinite wisdom" did something silly with the certificates, but it's quite fixable. Give me a minute and I'll put a copy of the file up for download and tell you were to put it (nicely of course ;) )

lol! you're da man

Attachment 103422

Just unzip this file and copy it as root to /var/lib/boinc-client (sudo cp ca-bundle.crt /var/lib/boinc-client ... assuming you've extracted it in your home folder if you put it on your desktop use sudo cp /home/<your user name>/Desktop/ca-bundle.crt /var/lib/boinc-client ) then restart boinc (sudo /etc/init.d/boinc-client restart) and you should be golden

wow i'm utterly speechless. how in the world do you know how to do stuff like that?

I'm studying to be a systems administrator. There's other folk here that have been sys admins for ... long enough they probably don't want to be reminded. ;)

does that have anything to do with computer engineering?

p.s. you're gonna be a good admin

Yes, kind of and not really. All to varying degrees :)

I'm doing a Bachelor of Information Technology, currently majoring in Systems Administration with a minor in Database Administration and readings in Forensic Science. My original study goal was to work with the Federal Police Cybercrimes Division.

quick question. now that's its up and running, if i need to play with my OC can i pause the work from the simple view, restart the pc, and have it resume work where it left off?

Quote:

---

Originally Posted by D_A

You'll need to install the right ca-cetificates file then. Someone at Ubuntu, in their "infinite wisdom" did something silly with the certificates, but it's quite fixable. Give me a minute and I'll put a copy of the file up for download and tell you were to put it (nicely of course ;) )

---

This is what I use for the UBUNTU ca cert problem:

Wordcommunitygrid Message "Peer certificate cannot be authenticated with known CA certificates."

Install the upstream ca-bundle.crt file for BOINC:
1. cd /var/lib/boinc-client
2. sudo mv ca-bundle.crt{,.bak}
3. sudo wget http://boinc.berkeley.edu/trac/expor.../ca-bundle.crt -O ca-bundle.crt.upstream
4. sudo cp -a ca-bundle.crt{.upstream,}

cool. hopefully if someone has this problem that will work for them. D A did the trick for me already tho :) i still need to know boinc will resume where it left off (like in windows) if i restart my pc?

It will resume from it's last checkpoint, just fine.

cool. another ?. is it possible that sensors and therefore gkrellm are reading my e6420 temps wrong? cuz right now at stock setting across the board it's loading at 79C. i used to be able to OC this thing easily to 3200 and stay cool.. heatsink is installed correctly, this isn't my first go around and yes i'm having stability issues with it. i'm out of ideas.

Is it possible that the sensors are wrong? Definitely. The added issues of instability might suggest otherwise though. I'd be inclined to double check the heat sink mount and make sure you haven't acquired a family of dust-bunnies as well. Also check your core voltage. If you've accidentally left it a notch or so too high you could have issues.

well i have it on my bench.. cleaned out the dust before installed. core voltage was at stock. is it also possible that the chip is just degrading? i bumped up the vcore and it's running still but showing 81C. is there any way to check what the TJMax is set at?

Off the top of my head I'd say you'd have to look it up. If you installed lm-sensors you could open a terminal and type "sensors" and I think it will tell you.

edit: Just tried it ... maybe not. It says something but not sure it's what you're after.

the guide on the first page has setup of the local IP addresses. does this also apply for wireless? some of my machines are unreachable to the router, so i just plug in a wireless network card, and when i try to remotely connect to it using realVNC, sometimes it can't connect after the computer has been on for long periods of time. i'm not sure if it's the router, wireless adapter, windows, or realVNC that causes this problem. this is on win7. i'm suspecting it might be some power saving feature, but after i switched that off, the problem is still there.

if i switched this cruncher to ubuntu would it have this same problem?

I had a system here that I was running on wireless. It would communicate fine on a fresh boot but after a while the wireless would just ... stop. No reason I could find. A reboot always got it going again. I put it down to the wireless NIC going to sleep and not waking up on network traffic, but it wouldn't wake on local input either. I just threw that card in the bin. This was on Win XP, btw.
I'd guess (but that's all it is) that your wireless NIC is to blame and it wouldn't matter what OS you were using it'd do the same thing.

Quote:

---

Originally Posted by D_A

Off the top of my head I'd say you'd have to look it up. If you installed lm-sensors you could open a terminal and type "sensors" and I think it will tell you.

edit: Just tried it ... maybe not. It says something but not sure it's what you're after.

---

i'm gonna install xp on a separate hard drive right quick. i'll let ya know what Real Temp has to say.

edit: ok real temp on xp is showing 68C tops, so lm-sensors is wrong. not that 68C at stock settings is good by any means but at least i feel better. i think my chip is just degrading from use.. oh well crunch it till it dies!!!!

Just got this running on an Ubuntu 10.04 install. Just did "sudo apt-get install BOINC" and attached WCG. Set preferences to 100% and I was off to the races :up:

hello will this work with Ubuntu 11.10 or will it work the same as the 10.04 thanks in advance.
i hate beating my head on the wall so i figured i would ask.

You can install boinc using the software manager in Ubuntu 11.10.

If you prefer, you can install the client using Ubuntu 11.10 Server edition and text commands. This means you could run the cruncher without a GUI and use SSH to remotely log in from your other boxes.

http://boinc.berkeley.edu/wiki/Boinccmd_tool

Quote:

---

sudo apt-get install boinc
boinccmd --lookup_account http://www.worldcommunitygrid.org [login] [password]

*This will give you your account key.*

boinccmd --project_attach http://www.worldcommunitygrid.org [account key]

*Now give it few to download your tasks and you should be up and running.*

boinccmd --_get_state
top

---

The last two lines will tell you whether it is running the project properly. Use the wiki page to manage any settings you need.

There should be instructions here on how to set the client up so it can be remotely administered using BOINC Manager on another machine so you don't need to use the terminal very often at all once it's set up.
If you can't find it, say so and I'll dig up the exact directory and file names to walk you through it.

Thank you. good to know things haven't changed that much in XS fast speedy reply i got it going :D
now for the ocing part then i will be up and running.

Got a new q6600. Going to set it up as an Ubuntu cruncher. About time I stopped relying so much on Windows. I know this is an old thread, but Thanks for the guide.

I updated my other post. I forgot an important command that is necessary to attach the project to your account.

I really recommend installing Ubuntu Server with openSSH and just use Putty to log in. It's low maintenance... basically just a really efficient cruncher that you can run from your other boxes.

After install of the OS and boinc, do this:

Quote:

---

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

sudo apt-get dist-upgrade
sudo reboot

---

Do that last part if you want to get the latest server kernel. Those updates always require a reboot to take effect. Since boinc installs as a daemon, it's always running when the computer is on. You can verify by typing "top" and looking for the tasks. (ctrl-c exits the "top" status)