The Myrinet Solaris driver is compiled under Solaris 2.5 for the UltraSparcs and Solaris 2.5 for Intel machines. The 2.5 drivers work fine under 2.6.

We have seen a problem if the /dev/mlanai and /driver/pseudo directories are NFS mounted under Solaris 2.6. When our NFS server is a SunOS 4.1.3 machine, the character special files created with "mknod" using a major number greater than 127 will have the major/minor number sign extended, making them unuseable. We have not discovered whether this is a client-side (Sol2.6) or server-side (SunOS 4.1.3) problem. If you have your /dev and /devices directories on a local disk you should experience no problems.

WARNING the intel_solaris driver seems to panic some 2.5.1 machines during the install process. Until we discover what is causing the problem, this procedure seems to work.

The Myrinet Solaris device driver is actually two separate drivers. One is a Data Link Provider Interface (DLPI) driver and the other is a pseudo driver for mmap()/API access. The DLPI driver needs to be loaded/initialized BEFORE the pseudo driver can load. To install the drivers, first

 cd [...]/myrinet/install

You will need to be root to allow access to /kernel/drv and /etc/devlink.tab. Running

	INSTALL.sparc_solaris
		For SPARC platform with SBus cards

	INSTALL.sol25.sunpci
		For SPARC platform with PCI cards

	INSTALL.intel_solaris
		For Intel platform with PCI cards

should install the drivers in the appropriate places. You will be asked how many boards you have in the machine. It is important to enter the exact number of boards and to re-install the software if you ever change the number of boards or move boards from slot to slot. Solaris maintains a device to slot mapping "/etc/path_to_inst" that is very sticky. Apparently, only reinstalling the driver software causes this mapping to get updated correctly.

The one thing that seems to work is

1) re-install the Myrinet drivers
2) touch /reconfigure
3) edit /etc/path_to_inst and /etc/path_to_inst.old
	and remove all lines with "MYRICOM,mlanai" or "pci10e8,8043"
4) sync ; sync ; sync
5) shutdown
6) power cycle and reboot

See "devlinks", "drvconfig", "path_to_inst" in the man pages for further information on the driver setup if you have trouble loading or running the driver. The file /etc/path_to_inst can create problems if it is trying to assign instance numbers to the boards such that the numbers don't start at zero, or they are not consecutive. We have found the /etc/path_to_inst files to be very "sticky". If we're changing the number of boards in the machine, we sometimes will remove all MLANAI entries in the file, then power-cycle the machine.

The DLPI device must be "plumbed" before the mmap() device will work. The install procedure adds a file /etc/rc3.d/S99myrinet to automatically plumb the interface so it is available for use. If you want to configure the IP interface automatically, you need to edit the commented ifconfig command in that file.

To use the mmap()/API interface without the IP interface, you must at least initialize/load the IP interface with the command

/usr/sbin/ifconfig myri0 plumb

By default, the protection on the Myrinet devices is rw-rw-rw (0666) so as to allow user-level access to the network. You should modify the protections if you do NOT want to allow general user access to the Myrinet device.

After completing the driver install procedure you need to configure the Myrinet software and tools for your site. This is done with the script myri.INIT. Please see the section on Configuring Software for more information.

Solaris 2.5 on Intel platforms limits the amount of memory available for DMA. To increase the limit, you need to add the following line to the end of /etc/system

        set lomempages=120

Then "sync; sync; sync"

A few Myrinet tools use Motif, you should add

/usr/dt/lib

 setenv LD_LIBRARY_PATH /usr/dt/lib 

Some of the Myricom tools use PERL. You can find packaged versions of PERL (x86 PERL) or (SPARC PERL) at sunsite.unc.edu.