Interphase Corp. - V/ETHERNET 4221 Condor - Document No. UGR0111-000, Rev. A RRRR EEEEE A DDDD M M EEEEE FFFFF I RRRR SSS TTTTT R R E A A D D MM MM E F I R R S S T RRRR EEE A A D D M M M EEE FFF I RRRR S T R R E AAAAA D D M M E F I R R S T R R E A A D D M M E F I R R S S T R R EEEEE A A DDDD M M EEEEE F I R R SSS T HP-UX 10.20 4221 DRIVER R1.0 This document contains Application Notes, Installation Notes, Corrections, and Deficiencies of the Interphase HP-UX 10.20 4221 Driver R1.0 for HP 9000 Series 700 computers. Part Numbers: SM00027-A00 DDS tape distribution SX00354-A00 media independent image Application Notes: ------------------ This release of the 4221 Condor driver is intended for use with HP/UX 10.20. This software release supports a maximum of three (3) 4221 Condor VME adapter cards per system. The following HP 9000 Series 700 hardware models are supported by this release: 742i, 743i, 747i, 748i Installation Notes: ------------------- This driver may be installed over a previous release. It is not necessary to remove the old version. Ensure the hardware jumpers on the 4221 are configured for a short I/O address range that will not conflict with any other VME devices in the machine. If you have a 743i it may inadvertently remove the 1M shared memory needed for the slave mapper. If the slave mapping is not correct the 4221 may print out a message indicating that map_mem_to_bus failed. Use 'vme_config -m A32' to verify whether you have a 1M region, for example: A32 Memory Range Size Name --------------------------------------------------------- 0x00100000 - 0x001fffff Size: 1M SHARED_MEM_CPU1 If not, you will need to edit your vme.CFG file to add a 1M entry in the A32 memory structure entitled "Space for A32 direct mapped window". For example the following will suffice: // address Name Proc Options align 1M:1M pg1M hp743i hints=SYSTEM_ONLY, PRIVATE Execute 'vme_config -m A32' again to verify the mapper will now recognize the 1M region. You may now see two 1M regions, but the system will function normally. Execute 'vme_config' (no options) to save the configuration before the next system reboot. Shut down the machine and install the 4221 into a vacant slot. Reboot the machine and load the tape containing the 4221 software. To install the 4221 driver, run 'swinstall'. When the install script is completed, it will build a new kernel and reboot the system. When the machine comes back up, despite the fact that the VME config file has not been changed, the driver may recognize the hardware and install itself. Regardless, once the machine is up, change directories to "/sbin/lib/vme". Modify the EM_START_ADDR and EM_END_ADDR addresses in the vme.CFG.4221 file so that the EM_START_ADDR matches the short I/O space selected via the jumpers, and the EM_END_ADDR is 0x1ff larger than EM_START_ADDR. Append the contents of vme.CFG.4221 to vme.CFG. Test that the changes you made have no errors, run 'vme_config -c -f vme.CFG' You must run 'vme_config' without options to save the configuration before the next system reboot. Edit the "/etc/rc.config.d/netconf" file. There will be a template entry that looks like this: # # NOTE: Subitute new values for the place holders www.xxx.yyy.zzz # for the Condor Ethernet interface. # Uncomment the next four lines. #INTERFACE_NAME[1]=em0 #IP_ADDRESS[1]="www.xxx.yyy.zzz" #SUBNET_MASK[1]="www.xxx.yyy.zzz" #BROADCAST_ADDRESS[1]="" # #INTERFACE_NAME[2]=em1 #IP_ADDRESS[2]="www.xxx.yyy.zzz" #SUBNET_MASK[2]="www.xxx.yyy.zzz" #BROADCAST_ADDRESS[2]="" Remove the pound in front of the INTERFACE_NAME, IP_ADDRESS, SUBNET_MASK, and the BROADCAST_ADDRESS lines and replace www.xxx.yyy.zzz with appropriate values for the desired IP address. If there is more than one 4221 installed, there will need to additional entries created for each additional board. Reboot the machine again. Upon the next boot up the device will be properly configured and ready for use. To quickly test the interface, try to 'ping' another ETHERNET host on the same segment. Corrections: ------------ None. This is the initial driver release. Deficiencies/comments: ---------------------- o The driver will support up to three 4221 boards in each system. However, at this time, installing more than one board has not been tested. o This driver currently does not support lanadmin, lanscan, or nettl.