Getting information about your Myricom Myri-10G Network Adapters: ================================================================ Use: ./bin/myri_info It will display information (including model and serial-numbers) about the Myricom NICs installed on the machine where the command is run. Myricom 10G-PCIE firmware upgrade: ================================== To update the firmware and PCI-ROM of Myri 10G-PCIE* devices, go in this directory on the machine where the card(s) is(are) installed and use: Default: blank PCI-ROM (no PXE, no EFI): ./ze-upgrade myri-eeprom-.mcp2 You may optionally specify a PCI expansion ROM to be included in the upgrade. Etherboot, gPXE, and EFI ROMs are provided in the rom/ subdirectory. For example, ./ze_upgrade -R rom/gpxe/myri10ge.rom myri-eeprom-.mcp2 programs a gPXE ROM with PXE, DHCP, UNDI, TFTP, iSCSI, AoE, and HTTP boot support. For Etherboot and EFI boot options, see "Choosing a ROM" below. The new firmware will only be taken into account after the next reboot. Some machine might even need a power-cycle to switch to the new firmware (if a simple reset or reboot does not necessarily send a fundamental reset signal to the card). Getting XFP/SFP information for Myricom "*-R or *-S" cards ======================================================= ./bin/mdio_rw Choosing a ROM ============== Myricom NICs provide optional Ethernet boot support via an optional PCI Expansion ROM Image, which can be loaded as part of your firmware upgrade. Most users do not need this optional pre-boot networking support, and should upgrade their NICs without specifying a ROM image. Users who require pre-boot networking support can choose from * Etherboot, which supports legacy PXE DHCP boot and IBM BIOS INT18h. * gPXE, which supports legacy PXE DHCP boot, plus iSCSI, AoE, HTTP, and UNDI, but does not yet support IBM BIOS INT18h. * EFI, which supports EFI-1.1 and UEFI-2.0 booting. Myricom recommends the gPXE ROM for all systems that can use it. The Etherboot ROM continues to be provided for customers familiar with Etherboot and for IBM BIOS users. To program the gPXE ROM, use: ./ze_upgrade -R rom/gpxe/myri10ge.rom myri-eeprom-.mcp2 To program the Etherboot ROM, use: ./ze_upgrade -R rom/etherboot/myri10ge.zrom myri-eeprom-.mcp2 EFI/UEFI users should note that while EFI defines network booting interfaces, not all Motherboards support EFI network booting. Most EFI motherboards continue to support PXE, and we recommend using the gPXE ROM on those systems. The potential problems with EFI include the following: * Many motherboots lack EFI network boot stacks. Such systems effectively require the NIC to supply the boot stack. This release does not provide boot stack drivers, though we can provide them in some cases. * While EFI allows platform-independent boot support via EFI Byte Code (EBC) drivers, some Motherboards lack EBC support, even though it is required by the EFI and UEFI specifications. In some cases, we can support such systems by provide the EBC support in ROM, but that is not supported by this release. * Some motherboards simply have broken EFI network boot stacks. For these reasons, we recommend using PXE boot on EFI systems whenever possible, until motherboard vendors' EFI network boot support matures. If you must use EFI, we recommend you first try the EBC SNP driver, which we expect to work on all compliant EFI motherboards that provide a boot stack: ./ze_upgrade -R rom/efi/MyriSnpEbc.rom myri-eeprom-.mcp2 If you program the EBC driver but it does not appear in the EFI boot manager after system reset, then you may have a motherboard that does not support EBC. In that case, we recommend you try the native SNP driver for your CPU type. The native SNP drivers are rom/efi/MyriSnpIa32.rom for 32-bit x86 processors, rom/efi/MyriSnpX64.rom for 64-bit x86 processors, and rom/efi/MyriSnpIpf.rom for Itanium processors. We also supply EFI UNDI32/64 drivers in case any customer requires UNDI32/64 support, but please note that UNDI32/64 is *not* backwards compatible with legacy UNDI. As far as we know, there are no users of UNDI32/64 except for the sample SNP driver in the EFI Development KIT. Finally, it is possible to program NICs with multiple PCI expansion ROMs via ROM chaining. Most users will not need to do it, but ROM chaining is achieved by providing a comma-delimited list of ROMs to program. For example, ./ze_upgrade -R rom/efi/MyriSnpEbc.rom,rom/gpxe/myri10ge.rom \ myri-eeprom-.mcp2 programs both the EFI EBC SNP ROM and the gPXE ROM, so the NIC can support both EFI and legacy systems. For help selecting a ROM, email help@myri.com .