Message boards : Number crunching : Qestions about Linux
Author | Message |
---|---|
Hello, | |
ID: 34437 | Rating: 0 | rate: / Reply Quote | |
Hello, To understand the answer you first need to understand that traditionally Linux distros will not install proprietary software for you. Most distros adhere so that philosophy tenaciously. Ubuntu has departed from that philosophy and will install proprietary modules and packages for you as part of the distro which makes it much easier for general PC work. For BOINC and GPU crunching... there is very little difference, the all work pretty good but Ubuntu is slightly easier than the others, IMHO, for the following reasons: 1) It's the most popular distro amongst BOINC crunchers so no matter what project you need help with there will almost always be a Ubuntu user there to give hints and advice. 2) The BOINC devs build and test BOINC on Ubuntu LTS. The BOINC installer they supply (the Berkeley installer) won't give you an installation that works out of the box on Ubuntu however all you need to do is install a few missing shared libraries and it will work fine. If you use the Berkeley installer to install on other distros you will have to add maybe a few more shared libraries than you do for Ubuntu. I can give you the library names you need for Ubuntu 12.04 and the command for installing them. It takes 5 minutes or less. I don't know the names of the shared libs you would need for any of the other distros. That's the extent of the differences between distros that pertain to BOINC and now you can see the differences are almost negligible. I have a dual boot with XP but that pc has a PSU of only 350W and the P4, no cruncher anymore (to slow). All Linux distros have very tight security, tighter than Windows, but easier to use once you understand it. I know exactly the problem you had and it's not difficult to do if you understand how Linux permissions (rights) work. The reason you ran into permission issues is because you didn't use the Berkeley installer, instead you used the BOINC package in your distro's repository. So "installed from repos" is the short way to say it. If you install from repos then the installer automatically checks to make sure you have the shared libraries required for BOINC and if they are absent it downloads and installs them for you. That's the advantgae of installing BOINC (or any Package) from repos. The installer in repos also installs BOINC as a daemon sevice which means it runs on the account of a user named boinc, not on your account. You cannot access any of boinc's files or directories from your account. In order to access boinc's "stuff" you must become root (the super user). You can avoid 99% of the permissions issues you had if you use the Berkeley installer instead of the installer in repo. The Berkely installer installs BOINC to run on your own account which means you own all the files and directories and have permission to do whatever you want with them. Many Linux users who run BOINC like having that flexibility so that that's why they use the Berkeley installer instead of the installer in repo. An advantage of installing BOINC from repo is that the installer configures the BOINC daemon service to automatically start at boot time and to automatically shutdown properly when you restart or shutdown the computer. However, you can easily configure to auto-start and auto-shutdown BOINC even if it's installed via Berkeley installer. If you want I can give you step by step instructions for setting up a dual-boot system, installing and configuring BOINC and installing the NVIDIA driver. The first step would be to decide how you want the disks to be partitioned and shared. The possibilities there are almost limitless. Decide what you want and I'll tell you how to do it. Any existing Windows partitions that are formatted NTFS can be setup to be accessible by Linux or you can hide them. ____________ BOINC <<--- credit whores, pedants, alien hunters | |
ID: 34438 | Rating: 0 | rate: / Reply Quote | |
Thanks Dagorath. | |
ID: 34442 | Rating: 0 | rate: / Reply Quote | |
Here is a list of all the packages (.deb files) that contain the additional 64-bit shared libs you will need for BOINC on Ubuntu 12.04: sudo apt-get -y install libwxgtk2.8-dev libcurl4-openssl-dev libxss-dev libstdc++6 freeglut3 ia32-libs The -y option is not necessary. It tells the package installer to not stop for user input. If you exclude the -y the installer will stop after it checks each package, report some info and ask if you want to proceed. I assume since this is going to be a new install there will be ample disk space available for the additional libs so you won't have any reason to not proceed so I recommend including the -y. After you install the above packages and BOINC, test to see if all the libs the client and the manager require are installed and accessible. In a terminal do the following commands: 1) cd ~/BOINC (~ is shortcut for your home directory therefore if you installed BOINC in a directory named BOINC in your home directory this command will change to that directory) 2) ldd boinc (this lists all the shared libs the client needs, if the lib is accessible it prints the path to the lib to the right of the arrow(=>), if the lib is not accessible (perhaps not installed) then it prints "Not found" to the right of the arrow) 3) now you want to run ldd against the manager but the list of shared libs the manager needs is very long but if you want to see the list enter ldd boincmgr but the easier way is to filter the list so you get only the lines that contain "Not found", to do that enter ldd boincmgr | grep "ot found".... notice I left the "N" off "Not found" because I can't remember if the "Not" is uppercase or lower and I don't remember if the grep filter is case-sensitive so I sidestep around the issue by excluding the "n". Note that you must include the quotes in the ldd boincmgr | grep "ot found" command. If you get no output from the command then it means all the libs are installed and accessible. 4) enter ./boinc to start the client, starting it this way will cause the client to log to the terminal which is not the way you should normally run it but it's a good idea to try it this way the first time because if there is any error and it refuses to start then the error code will be there in the terminal where it's easy to see, otherwise you will see exactly what you see in Event Log in BOINC manager, pressing ctrl-c will shutdown the client Temperature control under Linux for CPU and GPU is a bit hard if I have read, but I think and hope that all have a safety build in and shut down when to warm? I am pretty sure the thermal protection (shutdown when too warm) is either coded in the video card BIOS or is hard wired on the video card. Either way it is OS and driver independent (I think). If you simply install the NVIDIA driver then the temperature will be automatically controlled by the BIOS on the video card. Sometimes that auto-mode works very well and you need nothing more, sometimes it does not, seems like it depends on the manufacturer. For example, I have a Gigabyte GTX 670 and an Asus GTX 670 and auto-mode keeps both cards below 70C with fan speed approximately 50%.... perfect! On the other hand I have an EVGA GTX 660Ti that, in auto-mode, allows the temperature to hover around 80C which sucks therefore I have to put the fan speed control for the 660Ti in manual mode to keep the temp below 70C. The point is... if auto-mode works well on your cards then that's probably all you need. Auto-mode is installed by the NVIDIA driver installer by default. To monitor the GPU temps use the nvidia-settings utility that installs along with the NVIDIA driver. To run nvidia-settings just open a terminal and enter nvidia-settings. The GUI will start, it's very intuitive, the temperature monitor is under "thermal settings". If the temperatures are too high then configure manual fan control by opening a terminal and copy 'n paste the following 3 commands 1 at a time: cd /etc/X11 If you prefer to type the above commands then note the X is an upper-case X but the other x's are lower-case. Linux is very case-sensitive whereas Windows frequently is not. The last command causes a reboot. Then start nvidia-settings again and on the "thermal settings" page you will see options to select manual mode. Tick the box, read the warning/disclaimer, scroll the warning/disclaimer all the way to the bottom to enable the continue button, click continue. In manual mode you will likely find you cannot increase the fan speed to more than 80%. Also, the GUI will not accept certain numbers, for example, it might not accept 50% but it might accept 55% or 60% so you will need to experiment. If you need manual fan control mode and you get this far then I'll show you how you can use my gpu_d to make the manual mode more automatic but I think an even better solution would be to re-program the auto-mode in the card's BIOS by re-flashing the card's BIOS. ____________ BOINC <<--- credit whores, pedants, alien hunters | |
ID: 34447 | Rating: 0 | rate: / Reply Quote | |
I will recommend you also give openSUSE a try. It's not as popular as Ubuntu/Debian, but is a very solid and easy to use distro. We have a control center called YaST where you can set up most system-related things. Also, openSUSE's KDE desktop is unmatched as a lot of KDE developer use openSUSE and the KDE project uses openSUSE's build service to build their desktop environment for various other distros, not just SUSE. | |
ID: 34455 | Rating: 0 | rate: / Reply Quote | |
I have this thread for help, but have two questions first. | |
ID: 34522 | Rating: 0 | rate: / Reply Quote | |
I have never installed Linux on a 2 disk system either but I can tell you a few things. You don't have to set anything in the BIOS, just allow it to boot from the same disk it now boots from. You don't have to manually create a boot manager because the Ubuntu installer will do that for you. I can probably give more help if you can answer this... Do you want Ubuntu to use the entire SSD2 or do you want SSD2 to be partitioned with Win7 on one partition and Ubuntu on the other partition? | |
ID: 34524 | Rating: 0 | rate: / Reply Quote | |
Yes indeed the entire SSD2 is for Linux. | |
ID: 34527 | Rating: 0 | rate: / Reply Quote | |
If you have the Ubuntu install CD then the steps below will not work. In that case I would recommend downloading the Ubuntu Live ISO and burning it to DVD. If you are not sure if you have the plain installer CD or the Live DVD then boot it and see if it gives you the option mentioned in step 2 below. It won't erase any data until step 6 therefore going to just step 2 is completely safe.
| |
ID: 34528 | Rating: 0 | rate: / Reply Quote | |
Another option for installing Ubuntu and Windows 7 in a dual boot configuration. | |
ID: 34535 | Rating: 0 | rate: / Reply Quote | |
I've read that Windows will not install a service pack upgrade if the MBR is missing. Thanks, captainjack, for updating me, I had no idea. Does that apply to Win8 too? I recommend following the link captainjack provides if one wants a Linux-Win7 dualboot. The article is well written and uses screenshots for key points. Would the moderator please hide my message 34528 upthread. The procedure in that message is obviously inferior. ____________ BOINC <<--- credit whores, pedants, alien hunters | |
ID: 34541 | Rating: 0 | rate: / Reply Quote | |
I've read that Windows will not install a service pack upgrade if the MBR is missing. No, please leave that message (34528), it is good information for me! Thanks Dagorath for the indept explanation. It is very useful to me. I have to read it carefully again and then start with the installation soon. Also thanks to captainjack for the extra information. I will use the link from captainjack for the dual boot installation. ____________ Greetings from TJ | |
ID: 34551 | Rating: 0 | rate: / Reply Quote | |
Message boards : Number crunching : Qestions about Linux