for Mac OS X
|
Myrinet
GM-2 Software for Mac OS X |
To download Myrinet software,
you need a login and password.
If you don't already have these, please
request them.
The Mac OS X GM software is distributed in both source and binary forms, and supports Mac OS X version 10.3 and 10.4 on Macintosh G4 and G5 computers.
| NIC | ||
|---|---|---|
| Operating System / Architecture | PCIXF (One port, Lanai 2XP) and PCIXD (Lanai XP) |
PCI64 Series (Lanai 7 or 9) |
| Mac OS X 10.3 for Macintosh G4 and G5 | GM-2.0.21 for MacOSX 10.3 | GM-2.0.21 for MacOSX 10.3 |
| Mac OS X 10.4 for Macintosh G4 and G5 | GM-2.0.21 for MacOSX 10.4 + patch | GM-2.0.21 for MacOSX 10.4 + patch |
NOTE: Ethernet emulation is not supported on MacOSX 10.4!
NOTE: GM-2.0.21 for Mac OS X was tested on Mac OS X 10.4.0. If you install Mac OS X 10.4.1 or later, you will need to install the above GM patch to avoid kextload errors on GM start. To apply the binary patch, simply extract the binary patch tarball over the top of the GM tarball, and then install as usual. The binary patch replaces the driver, dependency list, and the mapper with updated versions.
NOTE: The installation procedure for GM has changed slightly between gm-1.6.3 and gm-2.0.21. Refer to the abbreviated installation instructions below. Automated installation scripts will need to be updated!
Abbreviated Binary Installation Instructions
Please be sure to read the README files (README and README-MacOSX) for detailed installation instructions and architecture-specific troubleshooting. Unresolved questions could also be answered in the FAQ.
Current cautions and common problems:
GM installation is performed in three easy steps:
1. Unpacking the GM driver.
tar zxvf gm-2.0.21_MacOSX-10.3-16ports.tar.gz
2. Installing the GM driver.
Select an installation directory path <install_path>. It is usually best for <install_path> to be the path to an NFS directory available on all machines that are to share this GM installation. The directory must be accessible using <install_path> on all machines that are to share the installation. <install_path> must be an absolute path; it must start with /. However, <install_path> may contain symbolic links.
cd gm-2.0.21_MacOSX-10.3-16ports
./GM_INSTALL <install_dir>
If you omit <install_dir>, the driver will be installed in the default, /opt/gm/.
Next, you must run
sudo <install_path>/sbin/gm_install_drivers
sudo /System/Library/StartupItems/GM/GM start
on each machine in the cluster.
Details of these installation scripts can be found in the README-linux. When the GM module is loaded, a mapper daemon called gm_mapper is started for each Myrinet NIC contained in the machine. The PIDs of the running gm_mappers are stored in /var/run/gm_mapper/pid.<board_id>.
If you wish for the driver to auto-load at boot, you must copy StartupParameters.plist to the /System/Library/StartupItems/GM/ directory:
sudo cp <install_path>/etc/StartupParameters.plist /System/Library/StartupItems/GM/
Alternatively, you may start and stop the drivers manually using
sudo /System/Library/StartupItems/GM/GM start
sudo /System/Library/StartupItems/GM/GM stop
or
sudo /System/Library/StartupItems/GM/GM restart
to start, stop, or restart the driver, respectively.
For directions on how to uninstall the GM driver, refer to the "Miscellaneous" section of the README-MacOSX.
3. Testing the GM Installation.
Once the GM software has been properly installed on all of the hosts in your cluster, you are ready to validate your Myrinet installation by performing the following sequence of tests.
Each of these steps is detailed in the Troubleshooting section of the FAQ.
The test scripts (gm_board_info, gm_debug, gm_allsize, gm_stress) are available in <install_path>/bin in your GM installation. A README describing each of these tests can be found in <install_path>/bin/README.
Congratulations! You have successfully installed GM.
| NIC | ||
|---|---|---|
| Operating System / Architecture | PCIXF (One port, Lanai 2XP) and PCIXD (Lanai XP) |
PCI64 Series (Lanai 7 or 9) |
| Mac OS X 10.2.x, 10.3.x, and 10.4.x for Macintosh G4 and G5 | GM-2.0.21_MacOSX + patch | GM-2.0.21_MacOSX + patch |
NOTE: Ethernet emulation is not supported on MacOSX 10.4!
NOTE: GM-2.0.21 for Mac OS X was tested on Mac OS X 10.4.0. If you install Mac OS X 10.4.1 or later, you will need to install the above GM patch to avoid kextload errors on GM start.
VERY IMPORTANT NOTE: The installation procedure for GM has changed slightly between gm-1.6.3 and gm-2.0.21. Refer to the abbreviated installation instructions below. Automated installation scripts will need to be updated!
Abbreviated Source Installation Instructions
To compile GM on Mac OS X platforms, you will need GNU make, and the Apple C/C++ compiler. These tools are provided by Apple as part of the Developer Tools (also known as Xcode) package available through the Apple Developer Connection. The Developer Tools package is also included in the Mac OS X 10.3 retail box. Please be sure to read the README files (README and README-MacOSX) for detailed installation instructions and architecture-specific troubleshooting. Unresolved questions could also be answered in the FAQ.
Current cautions and common problems:
GM installation is performed in four easy steps:
1. Configuring and compiling the GM driver
tar zxvf gm-2.0.21_MacOSX.tar.gz
cd gm-2.0.21_MacOSX
./configure
make
2. Installing the GM driver.
Select an installation directory path <install_path>. It is usually best for <install_path> to be the path to an NFS directory available on all machines that are to share this GM installation. The directory must be accessible using <install_path> on all machines that are to share the installation. <install_path> must be an absolute path; it must start with /. However, <install_path> may contain symbolic links.
cd binary
./GM_INSTALL <install_dir>
If you omit <install_dir>, the driver will be installed in the default, /opt/gm/.
Next, you must run
sudo <install_path>/sbin/gm_install_drivers
sudo /System/Library/StartupItems/GM/GM start
on each machine in the cluster.
Details of these installation scripts can be found in the README-linux. When the GM module is loaded, a mapper daemon called gm_mapper is started for each Myrinet NIC contained in the machine. The PIDs of the running gm_mappers are stored in /var/run/gm_mapper/pid.<board_id>.
If you wish for the driver to auto-load at boot, you must copy StartupParameters.plist to the /System/Library/StartupItems/GM/ directory:
sudo cp <install_path>/etc/StartupParameters.plist /System/Library/StartupItems/GM/
Alternatively, you may start and stop the drivers manually using
sudo /System/Library/StartupItems/GM/GM start
sudo /System/Library/StartupItems/GM/GM stop
or
sudo /System/Library/StartupItems/GM/GM restart
to start, stop, or restart the driver, respectively.
For directions on how to uninstall the GM driver, refer to the "Miscellaneous" section of the README-MacOSX.
4. Testing the GM Installation.
Once the GM software has been properly installed on all of the hosts in your cluster, you are ready to validate your Myrinet installation by performing the following sequence of tests.
Each of these steps is detailed in the Troubleshooting section of the FAQ.
The test scripts (gm_board_info, gm_debug, gm_allsize, gm_stress) are available in <install_path>/bin in your GM installation. A README describing each of these tests can be found in <install_path>/bin/README.
Congratulations! You have successfully installed GM.
Refer to the Software and Documentation Page for details of GM-based software (MPICH-GM, VI-GM, PVM-GM, Sockets-GM). Currently only MPICH-GM, PVM-GM, and Sockets-GM can be used with GM-2. All other middleware requires GM-1. If you encountered difficulties during any phase of this installation process, we recommend that you first consult the README-MacOSX and FAQ, and if you still have unresolved questions, please feel free to contact technical support at help@myri.com.
Last updated: 16 May 2006