{"id":202400,"date":"2015-11-13T01:47:07","date_gmt":"2015-11-13T06:47:07","guid":{"rendered":"http:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/uncategorized\/raspberry-pi-supercomputer-guide-steps.php"},"modified":"2015-11-13T01:47:07","modified_gmt":"2015-11-13T06:47:07","slug":"raspberry-pi-supercomputer-guide-steps","status":"publish","type":"post","link":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/super-computer\/raspberry-pi-supercomputer-guide-steps.php","title":{"rendered":"Raspberry Pi Supercomputer Guide Steps"},"content":{"rendered":"<p><p>    Return to <a href=\"http:\/\/www.soton.ac.uk\/~sjc\/raspberrypi\" rel=\"nofollow\">http:\/\/www.soton.ac.uk\/~sjc\/raspberrypi<\/a>  <\/p>\n<p>    View video at: <a href=\"http:\/\/www.youtube.com\/watch?v=Jq5nrHz9I94\" rel=\"nofollow\">http:\/\/www.youtube.com\/watch?v=Jq5nrHz9I94<\/a>  <\/p>\n<p>    Prof Simon Cox  <\/p>\n<p>    Computational Engineering and Design Research Group  <\/p>\n<p>    Faculty of Engineering and the Environment  <\/p>\n<p>    University of Southampton, SO17 1BJ, UK.  <\/p>\n<\/p>\n<p>    V0.2: 8th September 2012  <\/p>\n<p>    V0.3: 30th November 2012 [Updated with less direct    linking to MPICH2 downloads]  <\/p>\n<p>    V0.4: 9th January 2013 [Updated step 33]  <\/p>\n<p>    First steps to get machine    up  <\/p>\n<\/p>\n<p>    1.    Get image from  <\/p>\n<p>    <a href=\"http:\/\/www.raspberrypi.org\/downloads\" rel=\"nofollow\">http:\/\/www.raspberrypi.org\/downloads<\/a>  <\/p>\n<p>    I originally used:     2012-08-16-wheezy-raspbian.zip  <\/p>\n<p>    Updated 30\/11\/12:     2012-10-28-wheezy-raspbian.zip  <\/p>\n<p>    My advice is to to check    the downloads page on    raspberrypi.org and use the latest version.  <\/p>\n<p>    2.    Use win32 disk imager to put image onto an SD Card (or on a Mac    e.g. Disk Utility\/ dd)  <\/p>\n<p>        <a href=\"http:\/\/www.softpedia.com\/get\/CD-DVD-Tools\/Data-CD-DVD-Burning\/Win32-Disk-Imager.shtml\" rel=\"nofollow\">http:\/\/www.softpedia.com\/get\/CD-DVD-Tools\/Data-CD-DVD-Burning\/Win32-Disk-Imager.shtml<\/a>  <\/p>\n<p>    You will use the Write option to put the image from the disk    to your card  <\/p>\n<p>    3.    Boot on Pi  <\/p>\n<p>    4.    Expand image to fill card using the option on screen when you    first boot. If you dont do this on first boot, then you need    to use  <\/p>\n<p>    $ sudo raspi-config  <\/p>\n<p>    <a href=\"http:\/\/elinux.org\/RPi_raspi-config\" rel=\"nofollow\">http:\/\/elinux.org\/RPi_raspi-config<\/a>  <\/p>\n<p>    5.    Log in and change the password  <\/p>\n<p>        <a href=\"http:\/\/www.simonthepiman.com\/beginners_guide_change_my_default_password.php\" rel=\"nofollow\">http:\/\/www.simonthepiman.com\/beginners_guide_change_my_default_password.php<\/a>  <\/p>\n<p>    $ passwd  <\/p>\n<p>    6.    Log out and check that you typed it all OK (!)  <\/p>\n<p>    $ exit  <\/p>\n<p>    7.    Log back in again with your new password  <\/p>\n<p>    Building MPI so we can run    code on multiple nodes  <\/p>\n<p>    8.    Refresh your list of packages in your cache  <\/p>\n<p>    $ sudo    apt-get update  <\/p>\n<p>    9.    Just doing this out of habit, but note not doing any more than    just getting the list (upgrade is via sudo apt-get upgrade).  <\/p>\n<p>    10. Get    Fortran after all what is    scientific programming without Fortran being a possibility?  <\/p>\n<p>    $ sudo    apt-get install gfortran  <\/p>\n<p>    11. Read    about MPI on the Pi. This is an excellent post to read just to    show you are going to make it by the end, but dont type or get    anything just yet- we are going to build everything ourselves:  <\/p>\n<p>        <a href=\"http:\/\/westcoastlabs.blogspot.co.uk\/2012\/06\/parallel-processing-on-pi-bramble.html\" rel=\"nofollow\">http:\/\/westcoastlabs.blogspot.co.uk\/2012\/06\/parallel-processing-on-pi-bramble.html<\/a>  <\/p>\n<p>    Note there are a few things to note here  <\/p>\n<p>    a)    Since we put Fortran in we are good to go without excluding    anything  <\/p>\n<p>    b)    The packages here are for armel and    we need armhf in this case so we    are going to build MPI ourselves  <\/p>\n<p>    12. Read a    bit more before you begin:  <\/p>\n<p>        <a href=\"http:\/\/www.mcs.anl.gov\/research\/projects\/mpich2\/documentation\/files\/mpich2-1.4.1-installguide.pdf\" rel=\"nofollow\">http:\/\/www.mcs.anl.gov\/research\/projects\/mpich2\/documentation\/files\/mpich2-1.4.1-installguide.pdf<\/a>  <\/p>\n<p>    Note: As the version of MPICH2 updates, you are better to go    to:  <\/p>\n<blockquote class=\"wp-embedded-content\" data-secret=\"FeGpg5fmv4\"><p><a href=\"https:\/\/www.mpich.org\/documentation\/guides\/\">Guides<\/a><\/p><\/blockquote>\n<p><iframe loading=\"lazy\" class=\"wp-embedded-content\" sandbox=\"allow-scripts\" security=\"restricted\" style=\"position: absolute; visibility: hidden;\" title=\"&#8220;Guides&#8221; &#8212; MPICH\" src=\"https:\/\/www.mpich.org\/documentation\/guides\/embed\/#?secret=RMey83TgBi#?secret=FeGpg5fmv4\" data-secret=\"FeGpg5fmv4\" width=\"584\" height=\"329\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\"><\/iframe>  <\/p>\n<p>    and get the latest installers    Guide.  <\/p>\n<p>    We are going to follow the steps from 2.2 (from the Quick Start    Section) in the guide.  <\/p>\n<p>    13. Make a    directory to put the sources in  <\/p>\n<p>    $ mkdir \/home\/pi\/mpich2  <\/p>\n<p>    $ cd ~\/mpich2  <\/p>\n<p>    14. Get MPI    sources from Argonne.  <\/p>\n<p>    $ wget     <a href=\"http:\/\/www.mcs.anl.gov\/research\/projects\/mpich2\/downloads\/tarballs\/1.4.1p1\/mpich2-1.4.1p1.tar.gz\" rel=\"nofollow\">http:\/\/www.mcs.anl.gov\/research\/projects\/mpich2\/downloads\/tarballs\/1.4.1p1\/mpich2-1.4.1p1.tar.gz<\/a>  <\/p>\n<p>    [Note that as the MPI source updates, you can navigate to:  <\/p>\n<p>    <a href=\"http:\/\/www.mpich.org\/downloads\/\" rel=\"nofollow\">http:\/\/www.mpich.org\/downloads\/<\/a>    to get the latest stable release version for MPICH2]  <\/p>\n<p>    15. Unpack    them.  <\/p>\n<p>    $ tar xfz    mpich2-1.4.1p1.tar.gz  <\/p>\n<p>    [Note: You will need to update this as the version of MPICH2    increments]  <\/p>\n<p>    16. Make    yourself a place to put the compiled stuff  this will also    make it easier to figure out what you have put in new on your    system. Also you may end up building this a few times  <\/p>\n<p>    $ sudo    mkdir \/home\/rpimpi\/  <\/p>\n<p>    $ sudo    mkdir \/home\/rpimpi\/mpich2-install  <\/p>\n<p>    [I just chose the rpimpi to    replace the you in the Argonne guide and I did the directory    creation in two steps]  <\/p>\n<p>    17. Make a    build directory (so we keep the source directory clean of build    things)  <\/p>\n<p>    mkdir \/home\/pi\/mpich_build  <\/p>\n<p>    18. Change    to the BUILD directory  <\/p>\n<p>    $ cd \/home\/pi\/mpich_build  <\/p>\n<p>    19. Now we    are going to configure the build  <\/p>\n<p>    $ sudo    \/home\/pi\/mpich2\/mpich2-1.4.1p1\/configure    -prefix=\/home\/rpimpi\/mpich2-install  <\/p>\n<p>    [Note: You will need to update this as the version of MPICH2    increments]  <\/p>\n<p>    Make a cup of tea  <\/p>\n<p>    20. Make the    files  <\/p>\n<p>    $ sudo    make  <\/p>\n<p>    Make another cup of tea  <\/p>\n<p>    21. Install    the files  <\/p>\n<p>    $ sudo    make install  <\/p>\n<p>    Make another cup of tea  it will finish  <\/p>\n<p>    22. Add the    place that you put the install to your path  <\/p>\n<p>    $ export PATH=$PATH:\/home\/rpimpi\/mpich2-install\/bin  <\/p>\n<p>    Note to permanently put this on the path you will need to edit    .profile  <\/p>\n<p>    $nano ~\/.profile  <\/p>\n<p>     and add at the bottom these two    lines:  <\/p>\n<p>    # Add MPI to path  <\/p>\n<p>    PATH=\"$PATH:\/home\/rpimpi\/mpich2-install\/bin\"  <\/p>\n<p>    23. Check    whether things did install or not  <\/p>\n<p>    $ which mpicc  <\/p>\n<p>    $ which mpiexec  <\/p>\n<p>    24. Change    directory back to home and create somewhere to do your tests  <\/p>\n<p>    $ cd ~  <\/p>\n<p>    $ mkdir mpi_testing  <\/p>\n<p>    $ cd mpi_testing  <\/p>\n<p>    25. Now we    can test whether MPI works for you on a single node  <\/p>\n<p>    mpiexec    -f machinefile -n <number>    hostname  <\/p>\n<p>    where machinefile contains a list of IP addresses (in    this case just one) for the machines  <\/p>\n<p>    a)    Get your IP address  <\/p>\n<p>    $ ifconfig  <\/p>\n<p>    b)    Put this into a single file called machinefile  <\/p>\n<p>    26. $    nano machinefile  <\/p>\n<p>    Add this line:  <\/p>\n<p>    192.168.1.161  <\/p>\n<p>    [or whatever your IP address was]  <\/p>\n<p>    27.    If you use  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Follow this link:<\/p>\n<p><a target=\"_blank\" href=\"http:\/\/www.southampton.ac.uk\/~sjc\/raspberrypi\/pi_supercomputer_southampton.htm\" title=\"Raspberry Pi Supercomputer Guide Steps\">Raspberry Pi Supercomputer Guide Steps<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Return to <a href=\"http:\/\/www.soton.ac.uk\/~sjc\/raspberrypi\" rel=\"nofollow\">http:\/\/www.soton.ac.uk\/~sjc\/raspberrypi<\/a> View video at: <a href=\"http:\/\/www.youtube.com\/watch?v=Jq5nrHz9I94\" rel=\"nofollow\">http:\/\/www.youtube.com\/watch?v=Jq5nrHz9I94<\/a> Prof Simon Cox Computational Engineering and Design Research Group Faculty of Engineering and the Environment University of Southampton, SO17 1BJ, UK. V0.2: 8th September 2012 V0.3: 30th November 2012 [Updated with less direct linking to MPICH2 downloads] V0.4: 9th January 2013 [Updated step 33] First steps to get machine up 1. Get image from <a href=\"http:\/\/www.raspberrypi.org\/downloads\" rel=\"nofollow\">http:\/\/www.raspberrypi.org\/downloads<\/a> I originally used: 2012-08-16-wheezy-raspbian.zip Updated 30\/11\/12: 2012-10-28-wheezy-raspbian.zip My advice is to to check the downloads page on raspberrypi.org and use the latest version.  <a href=\"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/super-computer\/raspberry-pi-supercomputer-guide-steps.php\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"limit_modified_date":"","last_modified_date":"","_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[41],"tags":[],"class_list":["post-202400","post","type-post","status-publish","format-standard","hentry","category-super-computer"],"modified_by":null,"_links":{"self":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/posts\/202400"}],"collection":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/comments?post=202400"}],"version-history":[{"count":0,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/posts\/202400\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/media?parent=202400"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/categories?post=202400"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/wp-json\/wp\/v2\/tags?post=202400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}