View PCNET_709772.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

installing the ndis 3.x and 4.x drivers 79 7. installing the nd is 3.x and 4.x drivers ................................ ................................ .......... 81 7.1. i nstallation of the ndis 3. x d river ................................ ................................ ........................ 81 7.1.1. microsoft windows nt ................................ ................................ ................................ ...... 81 7.1.2. microsoft windows for workgroups 3.11 ................................ ................................ ........... 83 7.1.3. installation of the ndis 3.x win 95 driver ................................ ................................ .......... 85 7.1.4. win 95 ndis 3.x driver installation when controller is not detected on system boot ..... 86 7.1.5. installation of the winnt 3.51 ndis 3.x driver ................................ ................................ . 87 7.2. i nstallation of the ndis 4. x d river ................................ ................................ ........................ 89 7.2.1. microsoft windows nt ................................ ................................ ................................ ...... 89 8. installing the sc o unix lli driver (odt 3.0 and below) ............ 91 8.1. d river i nstallation f rom t he c ommand l ine p rompt ................................ .............................. 91 8.2. sco u nix lli d river k eywords ................................ ................................ ............................... 94 9. installing the sco unix mdi driver (sco openserver 5.0 and above) ... 97 9.1. sco u nix mdi d river k eywords ................................ ................................ ............................. 97 10. installing the s co mdi driver (release 4.0) ................................ ................................ . 99 10.1. sco mdi s oftware r elease 4.0 d river k eywords ................................ .......................... 100 10.1.1. led keywords ................................ ................................ ................................ ................ 100 11. installing the s co unixware 1.1 dlpi driver ................................ ............................ 105 11.1. d river i nstallation u sing t he d esktop gui ................................ ................................ ..... 105 11.2. d river i nstallation f rom t he c ommand l ine p rompt ................................ ....................... 108 11.3. u nixware 1.1 dlpi d river k eywords ................................ ................................ ................ 112 12. installing the s co unixware 2.x dlpi driver ................................ ........................... 115 12.1. u nixware 2. x dlpi d river k eywords ................................ ................................ ................ 115 13. installing the v xworks driver ................................ ................................ ..................... 117 13.1. i ntroduction ................................ ................................ ................................ ...................... 117 13.2. i nstallation p rocedure ................................ ................................ ................................ .... 117 14. installing the s unsoft solaris driver ................................ ................................ ...... 119 14.1. s un s oft s olaris d river k eywords ................................ ................................ ................... 121 15. installing the p acket driver ................................ ................................ ......................... 123 15.1. d river i nstallation u sing t he aminstal u tility ................................ ............................. 123 15.2. d river i nstallation f rom t he c ommand l ine p rompt ................................ ....................... 124 15.3. k eyword e xample ................................ ................................ ................................ .............. 124 15.4. p acket d river k eywords ................................ ................................ ................................ .. 124 16. installing the d mi component interface (ci) ................................ ........................... 127 16.1. d esktop m anagement i nterface (dmi) ................................ ................................ .............. 127 16.1.1. service layer ................................ ................................ ................................ .................. 128 16.1.2. co mponent interface (ci) ................................ ................................ ................................ 128 16.2. dmi i nstallation p rogram (dmi v ersion 1.1) ................................ ................................ ... 129 16.2.1. invoking dminstl ................................ ................................ ................................ .......... 129 16.2.2. editing input ................................ ................................ ................................ .................... 131 16.2.3. starting the installation program ................................ ................................ ..................... 131 16.2.4. exiting the installation program ................................ ................................ ...................... 133 16.3. dmi i nstallation p rocedure (dmi v ersion 2.0) ................................ ................................ 133 17. installing a uni versal boot rom ................................ ................................ ................. 135

installing the ndis 3.x and 4.x drivers 81 7. installing the ndis 3.x and 4.x drivers 7.1. installation of the ndis 3.x driver the network driver interface specification (ndis) 3.x is a driver specification developed by microsoft to offer a standard driver interface for adapter cards. amd?s ndis 3.x driver supports the following environments: ? microsoft windows nt 3.1, 3.5, 3.51 ? microsoft windows for workgroups 3.11 and microsoft windows 95 installation of amd?s ndis 3.x driver for the environments listed above is described below. 7.1.1. microsoft windows nt support is provided for the microsoft windows nt (versions 3.1, 3.5, and 3.51) environment. notes : 1) the directory structure provided on the amd ndis 3.x driver diskette has been set up for automatic oem installation. also, more information can be found in the microsoft windows nt user?s guide. 2) only x86-based windows nt platforms are supported. follow the steps listed below: __1 insert the amd ndis 3.x driver diskette into the floppy drive. __2 from the control panel in the windows nt main window, double click on the network icon to install the PCNET adapter card. __3 in the network settings dialog box, choose add adapter. __4 in the add network adapter dialog box, pull down the adapt er card list menu and select requires disk from manufacturer from the list and continue. __5 in the next window, enter: a:\winnt350 __6 then, select amd PCNET family ethernet adapter from the dialog box to
PCNET family network driver installation guide 82 install the amd PCNET adapt er card. __7 in the amd PCNET family ethernet adapter card setup dialog box, select bus type all (defaults to all if nothing is selected). if more than one network adapter card is used, select its bus type. note : sometimes all will not work on pci-based systems. in this case, try selecting pci1 or pci2 depending on the bus type. __7.1 for a PCNET-isa adapter card: enter the correct i/o port, irq, and dma channel values to correspond with what is set on the card by jumpers. if no v alues are selected, the default values will be chosen by the amd driver. __7.2 for PCNET-isa+, PCNET-isa ii, PCNET-32, and PCNET-pci adapter cards: irq and dma channel values are auto-detected. however, the values must be specified for multiple network cards. the irq and dma values are set by using the aminstal utility (see the express installation section for more details). shutdown windows nt and run the aminstal utility from dos. note : if you are using a PCNET-pci adapter card, you do not need to run the aminstal utility. __8 reboot your system to complete the driver installation process. for additional information, refer to your microsoft windows nt os documentation. in addition, the user may review the readme.txt file in the winnt directory of the amd ndis 3.x driver diskette. 7.1.1.1. keyword example to set the tp keyword, go into the amd PCNET family ethernet adapter card setup dialog box (see instructions above on how to access this dialog box), activate the tp button to use the tp keyword as described in the software keywords section (appendix b).
installing the ndis 3.x and 4.x drivers 83 7.1.2. microsoft windows for workgroups 3.11 support is provided for the microsoft windows for workgroups (version 3.11) environment. microsoft windows for workgroups 3.11 supports both ndis 2.01 and ndis 3.x drivers. amd provides both of these ndis drivers. notes : 1) the format and procedure to install the ndis drivers for windows for workgroups 3.11 is different from that of windows for workgroups 3.1. 2) the directory structure that is provide d on the amd ndis 3.x driver diskette has been setup for automatic oem installation. the oem installation section of this manual provides more details regarding oem driver installation. also, more information can be found in the microsoft windows for workgroups 3.11 user?s guide. follow the steps listed below: __1 insert the amd ndis 3.x driver diskette into the floppy drive. __2 in the windows for workgroups 3.11 program manager, double click on the windows setup icon. __3 from the options menu, se lect change network settings. __4 from the network setup dialog box, select the drivers... button to install the PCNET ndis 2.01 and ndis 3.x drivers. __5 in the network drivers dialog box, select the add adapter button to install the PCNET dev ice drivers. __6 in the add network adapter window, choose the unlisted or updated network adapter from the menu and then select ok. note : the detect button, the am2100/am1500t, or the PCNET family selections from the menu of standard drivers uses a previous release of the amd driver software. __7 the install driver dialog box will appear. enter the floppy drive containing the amd ndis 3.x driver diskette and specify the windows for workgroups 3.11 path to install the PCNET drivers. for exam ple, enter: a:\wfw311\isa for isa cards or a:\wfw311\pci for pci cards then select ok. __8 the advanced micro devices PCNET family selection will appear under the network adapters list. select ok to continue. __9 answer the series of questio ns for the correct base i/o port, irq channel, and dma channel.
PCNET family network driver installation guide 84 in the network drivers dialog box, select setup. in the amd PCNET family dialog box: __9.1 for a PCNET-isa adapter card: specify the irq, base i/o port, and dma channel to corres pond to the jumper settings on the adapter card. __9.2 for PCNET-isa+, PCNET-isa ii, PCNET-32, and PCNET-pci adapter cards: a. set interrupt (irq) to auto_scan and the base i/o port to 0. b. select ok. in the network drivers dialog box, sele ct close. in the network setup dialog box, select ok. for the microsoft- specific dialog boxes, select skip. for the install driver dialog box, enter: \wfw311 note : if auto_scan is selected for PCNET-isa+, PCNET-isa ii, PCNET-32, or PCNET-pci, then no value need be specified; however, windows for workgroups 3.11 will issue a warning message regarding possible interrupt conflict. this is due to the temporary configuring of the interrupt to channel 0 until the real value is set according to the eeprom configuration. __10 select ok to exit. windows for workgroups 3.11 will ask the user to reboot the machine once the installation is completed. the installation of the ndis 3.x driver for windows for workgroups 3.11 is now complete. 7.1.2.1. keyword example to set the led0 keyword value, follow the instructions given above to access the advanced settings for a PCNET adapter card. a dialog box will appear to set the led keyword options. in the led0 setting, enter the value desired from the list given in the software keywords section (appendix b). see table 4 for ndis 3.x driver keywords.
installing the ndis 3.x and 4.x drivers 85 7.1.3. installation of the ndis 3.x win 95 driver this installation assumes that there is a PCNET controller and driver installed in the system and that this is an upgrade. to install the driver from the distribution floppy, follow these instructions: __1 click on the start button, choose settings, and then choose control panel. __2 choose the network icon from the menu. then delete the already installed network card. __3 from distribution diskette 7, copy the file netamd.inf from :\win95\mac\ndis3 to c:\windows\inf __4 then shut down the system. __5 on reboot, win95 detects the PCNET controller installed in the system and prompts the user for the path of the distribution floppy. for example, a:\win95\mac\ndis3 note : in case, win95 does not detect the controller on the system, then skip the following and try the next installation procedure. __6 the rest of the network files are copied from the win95 distribution disks. __7 on completion of the installation, the user will be prompted to shutdown the system. when the system comes up again, the network should be up and running. __8 highlight the amd PCNET adapter in the network control panel a nd select the file sharing box. choose the appropriate box here. __9 the experienced user can choose the advanced button in the network control panel of settings and set the appropriate parameters.
PCNET family network driver installation guide 86 7.1.4. win 95 ndis 3.x driver installation when controller is not detected on system boot __1 click on the start button, choose settings, and then choose control panel. __2 choose the network icon and then click on add. __3 select the amd PCNET family adapters, from which the appropriate adapter type can be chosen. __4 the user may be prompted to choose the i/o resources. select resources without any conflicts. __5 the experienced user can choose the advanced button in the network control panel of settings and can set the appropriate parameters. __6 hig hlight the amd PCNET adapter in the network control panel and select the file sharing box. choose the appropriate box here. __7 on completion, shutdown the system and then reboot. the ndis 3.x driver should be up and running now.
installing the ndis 3.x and 4.x drivers 87 7.1.5. installation of the winnt 3.51 ndis 3.x driver this installation procedure is the same procedure as for the winnt 3.1/3.5 driver. refer to section 7.1. the amd winnt 3.51 ndis 3.x driver is in distribution diskette 6 under the winnt 3.51 subdirectory. there is only one difference. the winnt 3.51 will detect the PCNET-pci controller if it is in the system and the pci-only dialog box will appear. this means the user does not have to select the bus to scan for pci controllers. if there is a non-pci controller in the system, then the amd PCNET vl/isa dialog box appears, and the appropriate parameters can be chosen as in the winnt 3.1/3.5 driver case. if there is a pci and an isa/vl controller in the same system, then the pci controller is detected first, and the pci dialog box appears. then, when the user adds the next adapter, the amd PCNET vl/isa dialog box appears and the appropriate parameters can be chosen as in the winnt 3.1/3.5 driver case. note : this driver will work on winnt 3.51 onwards only and is not compatible with nt 3.1/3.5. the name of the driver has changed to amdpcn.sys . 7.1.5.1. ndis 3.x driver keywords see table 4 for the ndis 3.x driver keywords. table 1 . ndis 3.x driver keywords keyword description keyword name additional keyword details range default i/o address ioaddress see common keywords. interrupt interrupt see common keywords. dma dmachannel see common keywords. bus type designation bus_to_scan see amd driver specific keywords.
PCNET family network driver installation guide 88 net address netaddress this keyword allows the user to specify or overwrite the ieee or mfr. address. this must be edited in protocol.ini or nt registry. any valid ieee address or not present not present full duplex fdup * supported on PCNET- isa ii only fdup keyword is used to enable or disable full duplex on the 10baset and aui ports. see common keywords. utp aui off not present (what is on the eeprom) note : all of the keywords available to the ndis 3.x driver may be activated by selecting the options through a dialog box in the appropriate operating system.
installing the ndis 3.x and 4.x drivers 89 7.2. installation of the ndis 4.x driver the network driver interface specification (ndis 4.x) was developed by microsoft to offer a standard driver interface for adapter cards. amd?s ndis 4.x driver supports the following environments: microsoft windows nt 4.0 microsoft windows 95 osr2 and above (memphis, etc.) installation details for amd?s ndis 4.x driver are described below. 7.2.1. microsoft windows nt support is provided for microsoft window nt (version 4.0) environment. notes: 1. the directory structure that is provided on the amd ndix 4.x driver diskette has been set up for automatic oem installation. also, more information can be found in the microsoft windows nt user?s guide. 2. only x86-based windows nt platforms are supported. follow the steps listed below: __1 insert the amd ndis 4.x driver diskette into the floppy drive. __2 from the control panel in the windows nt main window, double click on the network icon to install the PCNET adapter card. __3 from the network settings dialog box, choose adapter and click add. __4 from the select network adapter dialog box, click have disk button. __5 from the insert disk window, enter: a:\winnt\miniport\ndis4 __6 on completion of the installation, the user will be prompted to shut down the system. when the system comes up again, the network should be up and running. __7 highlight the amd PCNET adapter in the network control panel and select the file sharing box. choose the appropriate box here. __8 the experienced user can choose the advanced button in the network control panel settings and set the appropriate parameters.
PCNET family network driver installation guide 90
installing the sco unix lli driver 91 8. installing the sco unix lli driver (odt 3.0 and below) support is provided for the sco unix (version 3.2.4) environment. the sco unix lli stream-based driver should be installed from the command line prompt. notes : 1) support for version 3.2.2 is no longer provided by amd. 2) t he directory structure that is provided on the amd sco unix driver diskette has been set up for automatic oem installation. the oem installation section of this manual provides more details regarding oem driver installation. also, more information can be found in the sco unix user?s guide. 8.1. driver installation from the command line prompt if you currently have an older sco unix driver installed in your system, you should remove it prior to installing a newer version. use the netconfig and custom utilities to remove the older driver version. refer to your sco unix os documentation as needed. after removing your existing driver, you may then proceed with installing a newer sco unix driver. note : the custom and netconfig utilities are provided by sco. follow the steps listed below: __1 login in as root. __2 insert the amd sco unix lli driver diskette into floppy drive a. make sure the floppy drive in which this diskette is inserted is fd0. this is the default floppy drive where the sco unix custom u tility will look for the driver and the corresponding installation script. __3 run the custom utility by typing: custom then press note : if you are using drive b, run the custom utility with the -m option to specify the correct drive where the amd sco unix lli driver diskette is located. __4 in the custom utility main menu, you will see four main options at the upper left hand corner of the screen (install, remove, list, quit). use the right/left arrow keys to select the install opt ion and then press . __5 next, use the up/down arrow keys to select a new product and press . __6 three options will be displayed (entire product, packages, files). select entire
PCNET family network driver installation guide 92 product and press . __7 the following message will be displayed: insert the requested volume and press to continue the installation insert: distribution floppy volume 1 continue quit press to continue. __8 the following message will be displayed: installing custom da ta files... insert the requested volume and press to continue the installation insert: amd PCNET family lli driver floppy volume 1 continue quit press to continue. __9 the following message will be displayed: extracti ng files... checking file permissions... you will then be returned to the custom utility main screen. __10 select quit from the custom utility main options. answer yes you want to exit from the custom utility. you will then be returned to the unix prompt. __11 next, run the netconfig utility by typing: netconfig then press . the netconfig utility is used to configure the sco unix driver for different int, dma, and i/o address values. this utility is also used to add the driver to th e protocol chain. note : the netconfig utility modifies the space.c file automatically and must be used in order to get proper support for pci bios api calls.
installing the sco unix lli driver 93 __12 the following will be displayed: available options: 1. add a chain 2. remo ve a chain 3. reconfigure an element in a chain q. quit select option: select option 1 (add a chain) by typing: 1 then press . __13 the following will be displayed: select top level of chain to add or q to quit: select the app ropriate top level of chain for your system by entering the appropriate number (num) value and pressing . __14 next, select the appropriate number (num) value for the amd PCNET ethernet driver and press . __15 answer all of the question s asked by netconfig as appropriate for your system. refer to your sco unix os documentation as needed. also, see the software keyword section in this manual for more details on keyword settings. note : if you need to modify keyword values, you should edit the space.c file as needed. the path for this file is: /etc/conf/pack.d/pnt0/space.c __16 select quit from the netconfig utility by typing q and then press . __17 at this point, you should relink your kernel and reboot the system. refe r to your sco unix os documentation as needed. the installation of the sco unix lli driver is now complete.
PCNET family network driver installation guide 94 8.2. sco unix lli driver keywords keywords can be added, deleted, and/or modified by manually editing the appropriate #define values in the space.c file. see appendix b ( software keywords ) and your sco unix manuals for more details. a sample version of this file is listed below: /******************************************************************************/ /* copyright (c) 1993 advanced micro devices, inc. */ /* */ /* file: /etc/conf/pack.d/pnt0/space.c */ /* version: 1.0 */ /* description: sco unix system v/386 config. file for PCNET family */ /* author: leonid grossman */ /* created: 08/20/93 */ /******************************************************************************/ #include config.h #if defined(pnt3_units) #define tot_units (pnt3_units+pnt2_units+pnt1_units+pnt_units) #elif defined(pnt2_units) #define tot_units (pnt2_units+pnt1_units+pnt_units) #elif defined(pnt1_units) #define tot_units (pnt1_units+pnt_units) #else #define tot_units (pnt_units) #endif #define max_minors 16 /* please do not modify */ #define tx_buffers_0 16 /* must be power of 2 (1,2,4,8,...512) */ #define tx_buffers_1 16 #define tx_buffers_2 16 #define tx_buffers_3 16 #define rx_buffers_0 16 #define rx_buffers_1 16 #define rx_buffers_2 16 #define rx_buffers_3 16 #define scan_type_0 0 /* 0-all, 1-pci, 2-pnp, 3-vesa, 4-isa, 5-pci1, 6-pci2 */ #define scan_type_1 0 #define scan_type_2 0 #define scan_type_3 0 #define led0_0 0xffffffff /* 0xffffffff - defaults */ #define led0_1 0xffffffff #define led0_2 0xffffffff #define led0_3 0xffffffff #define led1_0 0xffffffff #define led1_1 0xffffffff #define led1_2 0xffffffff #define led1_3 0xffffffff #define led2_0 0xffffffff #define led2_1 0xffffffff #define led2_2 0xffffffff #define led2_3 0xffffffff #define led3_0 0xffffffff #define led3_1 0xffffffff #define led3_2 0xffffffff #define led3_3 0xffffffff #define dmarotate_0 0 /* 0 - normal priority, 1 - rotate priority */ #define dmarotate_1 0 #define dmarotate_2 0 #define dmarotate_3 0 #define tp_0 0 /* 0 - the autoselect mode, 1 - the utp mode */ #define tp_1 0 #define tp_2 0 #define tp_3 0 #define fdup_0 0 /* 0 - default, 1 - aui, 2 - 10baset, 3 - off */
installing the sco unix lli driver 95 #define fdup_1 0 #define fdup_2 0 #define fdup_3 0 /* please do not modify access_type and last_bus parameters */ /* unless you are sure that the values provided by 'netconfig' are wrong */ #define access_type_0 0 #define access_type_1 0 #define access_type_2 0 #define access_type_3 0 #define last_bus_0 256 #define last_bus_1 256 #define last_bus_2 256 #define last_bus_3 256 int pnt_maxstreams = max_minors; int pnt_totaldevcount = tot_units; /* * structure used in space.c to pass configuration to driver. this information * is copied to the pnt_devicestruct structure. */ struct pnt_configstruct { short index; /* board index */ short minors; /* minor devices configured */ short vec; /* interrupt vector # */ short iobase; /* boards base memory address */ short ioend; /* ending base i/o address */ short dma; /* dma channel used by the board */ short tx_buffers; /* number of transmit buffers*/ short rx_buffers; /* number of receive buffers*/ long bus_scan; /* bus type to search for */ long led0; /* led value */ long led1; /* led value */ long led2; /* led value */ long led3; /* led value */ long dmarotate; long tp; long fdup; long access_type; long last_bus; }; struct pnt_configstruct pnt_configarray[tot_units] = { #if defined pnt_units {0, max_minors, pnt_0_vect, pnt_0_sioa, pnt_0_eioa, pnt_chan, tx_buffers_0, rx_buffers_0, scan_type_0, led0_0, led1_0, led2_0, led3_0, dmarotate_0, tp_0, fdup_0, access_type_0, last_bus_0 }
PCNET family network driver installation guide 96 #endif #if defined pnt1_units ,{1, max_minors, pnt1_0_vect, pnt1_0_sioa, pnt1_0_eioa, pnt1_chan, tx_buffers_1, rx_buffers_1, scan_type_1, led0_1, led1_1, led2_1, led3_1, dmarotate_1, tp_1, fdup_1, access_type_1, last_bus_1 } #endif #if defined pnt2_units ,{2, max_minors, pnt2_0_vect, pnt2_0_sioa, pnt2_0_eioa, pnt2_chan, tx_buffers_2, rx_buffers_2, scan_type_2, led0_2, led1_2, led2_2, led3_2, dmarotate_2, tp_2, fdup_2, access_type_2, last_bus_2 } #endif #if defined pnt3_units ,{3, max_minors, pnt3_0_vect, pnt3_0_sioa, pnt3_0_eioa, pnt3_chan, tx_buffers_3, rx_buffers_3, scan_type_3, led0_3, led1_3, led2_3, led3_3, dmarotate_3, tp_3, fdup_3, access_type_3, last_bus_3 } #endif };
97 9. installing the sco unix mdi driver (sco openserver 5.0 and above) note : for PCNET software release 3.x only. sco openserver 5.0 has built-in support for the PCNET driver. see the sco documentation for the network driver installation directions. to upgrade the amd PCNET driver to the 3.0 version, follow the steps below: __1 copy the install file from the scounix.50 directory on diskette 6. the file is in dos format. it can be copied with the doscp command or from the dos merge session. __2 run sh install command to upgrade the PCNET mdi driver package. 9.1. sco unix mdi driver keywords keywords can be added, deleted, and/or modified by using the advanced button for PCNET driver during netconfig installation. see appendix b ( software keywords ) and your sco unix manuals for more details . the sco mdi driver has an additional keyword, PCNET2 . if set to a non-zero value, the PCNET2 keyword enables advanced features for the PCNET-pci2 chip.
PCNET family network driver installation guide 98
99 10. installing the sco mdi driver (release 4.0) sco open server 5.0 or 5.0.4 have the amd pnt driver in their installation cd-roms. after the operating system is installed, the updated pnt driver can be installed by following the steps below: __1 boot up the system after inserting the network card. __2 install the older driver that comes with the sco 5.0 and 5.0.4 cd with netconfig and bind with tcpip. relink and reboot. to make sure that it works, follow these steps: __2.1 start netconfig . __2.2 click and select the following options: hardware, add new lan adapter, amd adapter , and add protocol and the other options. __3 copy the following four files from the updated driver files or from the software release 4.0 files: driver.o space.c space.h pnt.h __4 link the kernel with the command: /etc/conf/cf.d/link_unix and then reboot. make sure the following values are correct in the /etc/conf/pack.d/space.h file: pnt_0_pci_bus 0 pnt_0_pci_dev 14 pnt_0_pci_func 0 the above values are for pci; those for isa will be different. make sure they are not -1. note : a bug exists during driver removal when using the netconfig file. manually remove the pnt directory under /etc/conf/pack.d , otherwise the next installation of the pnt driver will not work.
PCNET family network driver installation guide 100 10.1. sco mdi software release 4.0 driver keywords the software release 4.0 pnt driver has additional keywords added to it for the user's convenience. the user may access the space.c file in the /etc/conf/pack.d/pnt/ directory and edit the file to set the following keywords as per the requirement: fulldup speed100 aui mii_ext_phy 10baset auto-negotiation overrides when all the aui, mii_ext_phy, and 10baset keywords are set to 0. care should be taken that only one of the interface or none is enabled. if none is enabled, then auto-negotiation overrides. also fulldup and speed100 may be enabled or disabled by setting the values to 0 or 1, respectively. note : if speed100 is set to 1 for controllers that support only 10 mbps data transfer, it is ignored by the driver/controller and the 10 mbps speed is effective. 10.1.1. led keywords the /etc/conf/pack.d/space.h file may be edited to reflect the desired values for the leds of the controllers. if the user uses the default leds, the leds reflect the 4.0 specifications. if the user changes the values, the drivers reprogram the leds to reflect the desired value. these values may be edited and changed in the space.h file to reflect the user?s desired values. note : after making any keyword changes the unix kernel must be linked with the command /etc/conf/cf.d/link_unix and rebooted for the changes to be effective . the space.c and space.h files are provided below for reference. /******************************************** space.c ********************************************/ #include sys/types.h #include sys/stream.h #include sys/mdi.h #include sys/pci.h #include pnt.h
101 #include config.h #include space.h #define max_minors 16 int pnt_maxstrepnt = max_minors; int pnt_totaldevcount = pnt_cntls; /* kathyp */ int fulldup=0; int speed100=0; int aui=0; int tenbaset=0; int mii_extphy=1; struct pnt_configstruct pnt_configarray[pnt_cntls] = { #if defined pnt_0 {0, max_minors, pnt_0_vect, pnt_0_sioa, pnt_0_eioa, pnt_0_dma, pnt_0_tx_buffers, pnt_0_rx_buffers, pnt_0_led0, pnt_0_led1, pnt_0_led2, pnt_0_led3, pnt_0_dmarotate, pnt_0_tp, pnt_0_fdup, pnt_0_PCNET2, pnt_0_pci_bus, pnt_0_pci_dev, pnt_0_pci_func } #endif #if defined pnt_1 ,{1, max_minors, pnt_1_vect, pnt_1_sioa, pnt_1_eioa, pnt_1_dma, pnt_1_tx_buffers, pnt_1_rx_buffers, pnt_1_led0, pnt_1_led1, pnt_1_led2, pnt_1_led3, pnt_1_dmarotate, pnt_1_tp, pnt_1_fdup, pnt_1_PCNET2, pnt_1_pci_bus, pnt_1_pci_dev, pnt_1_pci_func } #endif #if defined pnt_2 ,{2, max_minors, pnt_2_vect, pnt_2_sioa,
PCNET family network driver installation guide 102 pnt_2_eioa, pnt_2_dma, pnt_2_tx_buffers, pnt_2_rx_buffers, pnt_2_led0, pnt_2_led1, pnt_2_led2, pnt_2_led3, pnt_2_dmarotate, pnt_2_tp, pnt_2_fdup, pnt_2_PCNET2, pnt_2_pci_bus, pnt_2_pci_dev, pnt_2_pci_func } #endif #if defined pnt_3 ,{3, max_minors, pnt_3_vect, pnt_3_sioa, pnt_3_eioa, pnt_3_dma, pnt_3_tx_buffers, pnt_3_rx_buffers, pnt_3_led0, pnt_3_led1, pnt_3_led2, pnt_3_led3, pnt_3_dmarotate, pnt_3_tp, pnt_3_fdup, pnt_3_PCNET2, pnt_3_pci_bus, pnt_3_pci_dev, pnt_3_pci_func } #endif }; extern int pntopen(), pntclose(), pntuwput(); extern int nulldev(); struct module_info pnt_minfo = { 0, pnt , 14, 1514, 16*1514, 12*1514 }; struct qinit pnturinit = { 0, 0, pntopen, pntclose, nulldev, &pnt_minfo, 0 }; struct qinit pntuwinit = { pntuwput, 0, pntopen, pntclose, nulldev, &pnt_minfo, 0 }; struct streamtab pntinfo = { &pnturinit, &pntuwinit, 0, 0 }; /*****************************************************/ @(#) space.h 7.1 94/12/19 scoinc *****************************************************/ /* dma channel - modified for jumpered isa adapters */ #define pnt_0_dma -1 #define pnt_1_dma -1 #define pnt_2_dma -1 #define pnt_3_dma -1 /* number of transmit buffers */ #define pnt_0_tx_buffers 32 #define pnt_1_tx_buffers 32
103 #define pnt_2_tx_buffers 32 #define pnt_3_tx_buffers 32 /* number of receive buffers */ #define pnt_0_rx_buffers 16 #define pnt_1_rx_buffers 16 #define pnt_2_rx_buffers 16 #define pnt_3_rx_buffers 16 /* 10-baset enforced if non-zero */ #define pnt_0_tp 0 #define pnt_1_tp 0 #define pnt_2_tp 0 #define pnt_3_tp 0 /* led0 value */ #define pnt_0_led0 0xc0 #define pnt_1_led0 0xc0 #define pnt_2_led0 0xc0 #define pnt_3_led0 0xc0 /* led1 value */ #define pnt_0_led1 0xb0 #define pnt_1_led1 0xb0 #define pnt_2_led1 0xb0 #define pnt_3_led1 0xb0 /* led2 value */ #define pnt_0_led2 0x4088 #define pnt_1_led2 0x4088 #define pnt_2_led2 0x4088 #define pnt_3_led2 0x4088 /* led3 value */ #define pnt_0_led3 0x81 #define pnt_1_led3 0x81 #define pnt_2_led3 0x81 #define pnt_3_led3 0x81 /* full duplex enabled */ #define pnt_0_fdup 0 #define pnt_1_fdup 0 #define pnt_2_fdup 0 #define pnt_3_fdup 0 /* dma controller in rotate priority mode */ #define pnt_0_dmarotate 0 #define pnt_1_dmarotate 0 #define pnt_2_dmarotate 0 #define pnt_3_dmarotate 0 /* advanced PCNET features */ #define pnt_0_PCNET2 0 #define pnt_1_PCNET2 0 #define pnt_2_PCNET2 0 #define pnt_3_PCNET2 0 /* pci bus number */ #define pnt_0_pci_bus 0 #define pnt_1_pci_bus -1 #define pnt_2_pci_bus -1 #define pnt_3_pci_bus -1 /* pci device number */ #define pnt_0_pci_dev 14 #define pnt_1_pci_dev -1 #define pnt_2_pci_dev -1
PCNET family network driver installation guide 104 #define pnt_3_pci_dev -1 /* pci adapter function number */ #define pnt_0_pci_func 0 #define pnt_1_pci_func -1 #define pnt_2_pci_func -1 #define pnt_3_pci_func -1
105 11. installing the sco unixware 1.1 dlpi driver support is provided for the sco unixware (version 1.1) environment. amd?s unixware driver is compliant with at&t?s data link provider interface (dlpi) specification. the unixware driver can be installed using the unixware desktop graphical user interface (gui) or from the unixware command line prompt. both methods are explained below. 11.1. driver installation using the desktop gui if you currently have an older unixware driver installed in your system, you should remove it prior to installing a newer version. after removing your existing driver, you may then proceed with installing a newer unixware driver. follow the steps listed below: __1 in the unixware desktop window, double click on the system_setup icon. __2 in the system setup window, double click on the appl-n_setup icon. the following message will be dis played: cataloging applications on your system; please wait wait for the system to catalog existing applications/sets currently installed. __3 insert the amd unixware dlpi driver diskette into drive a. __4 from the application setup menu bar, sel ect view. __5 from the view drop down menu, select uninstalled appl?ns. __6 from the uninstalled appl?ns drop down menu, select disk_a. the following message will be displayed: cataloging applications on disk_a; please wait wait for the system to catalog existing applications/sets currently on disk a. __7 select the pnt icon by clicking on it. __8 from the application setup menu bar, select application. __9 from the application drop down menu, select install.
PCNET family network driver installation guide 106 __10 a new window will then op en entitled, add application: pnt. the following message will be displayed: processing: package: advanced micro devices PCNET family driver (pnt) from . wait for the system to process the amd unixware driver. __11 next, within the add application: pnt window, you will see the adapter selection menu with the following: amd PCNET (pnt): 0 replace the 0 by typing: 1 the press . note : at this time amd?s unixware driver only supports one adapter. the apply box is then highlighted. press to continue. __12 next, within the add application: pnt window, you will see the pnt parameter selection menu with the following: interrupt vector: 0 i/o address: 0 0 dma: 0 if you are using a PCNET- isa adapter card, then go to step 14.1 below. if you are using a PCNET-isa+, PCNET-isa ii, PCNET-32, or PCNET-pci adapter card, then go to step 12.2 below. __12.1 for a PCNET-isa adapter card: a. you must know what your card?s irq (interrupt vect or), i/o base address, and dma values are. b. use the right arrow key to select the appropriate irq value for your card and then the down arrow key to move to the next field. c. after filling in each field, press the down arrow key to highlight t he apply box and then press . d. go to step 13 below to continue.
107 __12.2 for PCNET-isa+, PCNET-isa ii, PCNET-32, PCNET-pci adapter cards: a. leave the i/o base address and dma values set to 0. b. an auto scan will be performed to detect the proper i/o base address and dma values automatically. however, note that the irq (interrupt vector) value will also be automatically detected, but cannot be installed dynamically. c. if you know the correct irq value, enter it in the interrupt vector field, press the down arrow key to highlight the apply box, and then press . go to step 13 below to continue. d. if you do not know the correct irq value, enter a guess (e.g., 5 ), press the down arrow key to highlight th e apply box, and then press . e. if you happen to guess the correct irq value, you will not get an irq mismatch message and the installation process will continue. go to step 13 below to continue. f. most likely, you will get an irq mi smatch. in this case, you need to re- boot the system and restart the installation process. g. as the system comes up during the reboot you will get a warning message instructing you to run your setup again with a specified irq value. write this irq value down and restart the installation process from step 1 above. h. when you reach step 12.2 again, use the irq value you wrote down and use it to fill in the interrupt vector field leaving the other two fields set to 0. press the down arro w key to highlight the apply box, and then press . i. go to step 13 below to continue. __13 the following message will be displayed: ## installing part 1 of 1 wait for the system to install the unixware driver. __14 the following messag e will be displayed: click exit to terminate pkgadd click on the exit button.
PCNET family network driver installation guide 108 _15 the following message will be displayed at the bottom of the application setup window: software installation of pnt succeeded the installation of the unixware dlpi driver is now complete. note : you should now attach the network to the driver by running: /etc/confnet.d/configure -i refer to your unixware os documentation as needed. 11.2. driver installation from the command line prompt if you currently have an older unixware driver installed in your system, you should remove it prior to installing a newer version. after removing your existing driver, you may then proceed with installing a newer unixware driver. follow the steps listed below: __1 at the unixware prompt, type the following: pkgadd -d diskette1 then press . __2 the following message will be displayed: insert diskette into floppy drive 1. type [go] when ready, (default: go) or [q] to quit: insert the amd unixware dlpi driver d iskette into drive a. then press to accept the default value of go to start the installation process. __3 the following message will be displayed: installation in progress. do not remove the diskette. the following packages are available: 1 pnt advanced micro devices PCNET family driver (i386) 1 select package(s) you wish to process (or ?all? to process all packages). (default: all) [?,??,q] type the following: 1
109 then press to select the pnt package. __4 the fo llowing message will be displayed: processing: package: advanced micro devices PCNET family driver (pnt) from . wait for the system to process the pnt package. __5 next, you will see the adapter selection menu with the following: am d PCNET (pnt): 0 type the following: 1 then press . note : at this time amd?s unixware driver only supports one adapter. the apply box is then highlighted. press to continue. __6 next, you will see the pnt parameter selection menu with the following: interrupt vector: 0 i/o address: 0 0 dma: 0 if you are using a PCNET-isa adapter card, then go to step 6.1 below. if you are using a PCNET-isa+, PCNET-isa ii, PCNET-32, or PCNET-pci adapter card, then go to step 6.2 below. __6.1 for a PCNET-isa adapter card: a. you must know what your card?s irq (interrupt vector), i/o base address, and dma values are. b. use the right arrow key to select the appropriate irq value for your card and then the d own arrow key to move to the next field. c. after filling in each field, press the down arrow key to highlight the apply box and then press . d. go to step 7 below to continue. __6.2 for PCNET-isa+, PCNET-isa ii, PCNET-32, PCNET-pci adapt er cards: a. leave the i/o base address and dma values set to 0.
PCNET family network driver installation guide 110 b. an auto scan will be performed to detect the proper i/o base address and dma values automatically. however, please note that the irq (interrupt vector) value will also be au tomatically detected, but cannot be installed dynamically. c. if you know the correct irq value, enter it in the interrupt vector field, press the down arrow key to highlight the apply box, and then press . go to step 7 below to continue . d. if you do not know the correct irq value, enter a guess (e.g., 5), press the down arrow key to highlight the apply box, and then press . e. if you happen to guess the correct irq value, you will not get an irq mismatch message and the installation process will continue. go to step 7 below to continue. f. most likely, you will get an irq mismatch. in this case, you need to reboot the system and restart the installation process. g. as the system comes up during the reboot y ou will get a warning message instructing you to run your setup again with a specified irq value. write this irq value down and restart the installation process from step 1 above. h. when you reach step 6.2 again, use the irq value you wrote do wn in the interrupt vector field leaving the other two fields set to 0. press the down arrow key to highlight the apply box, and then press . i. go to step 7 below to continue. __7 the following message will be displayed: ## processing p ackage information ## processing system information ## verifying package dependencies followed by: ## installing part 1 of 1. followed by: the following loadable modules will be configured now: pnt module configuration is completed.
111 the unix operating system kernel will be rebuilt to include your configuration changes during the next system reboot. followed by: installation of advanced micro devices PCNET family driver (pnt) was successful. __8 the following message wil l be displayed: insert diskette into floppy drive 1. type [go] when ready, (default: go) or [q] to quit: type q and then press to quit the installation. you will then be returned to the unix prompt. the installation of the unixware dlpi driver is now complete. note : you should now attach the network to the driver by running: /etc/confnet.d/configure -i refer to your unixware os documentation as needed.
PCNET family network driver installation guide 112 11.3. unixware 1.1 dlpi driver keywords keywords can be added, deleted, and/or modified by manually editing the appropriate #define values in the space.c file. see appendix b ( software keywords ) and your sco unixware manual for more details. a sample version of this file is listed below: #ident %w% #ident $header: $ #include #include #include #include #define nsaps 8 #define maxmulti 8 #define inetstats 1 #define streams_log 0 #define ifname pnt #define pnt_tx_buf 16 #define pnt_rx_buf 16 int pnt_totaldevcount = pnt_cntls; int pnt_maxstreams = nsaps; int pntboards = pnt_cntls; int pntstrlog = streams_log; char *pnt_ifname = ifname; dl_bdconfig_t pntconfig[ pnt_cntls ] = { #ifdef pnt_0 { pnt_cmajor_0, pnt_0_sioa, pnt_0_eioa, pnt_0_scma, pnt_0_ecma, pnt_0_vect, nsaps, 0 } #endif };struct pnt_configstruct { short index; short minors; short vec; ushort iobase; ushort ioend; short dma; short tx_buffers; short rx_buffers; long bus_scan; long led0; long led1; long led2; long led3 ; long dmarotate; long tp; long fdup; long fast_isa; };
113 struct pnt_configstruct pnt_configarray[pnt_cntls] = { #ifdef pnt_0 { 0, nsaps, pnt_0_vect, pnt_0_sioa, pnt_0_eioa, pnt_chan, pnt_tx_buf, pnt_rx_buf, 0, /* bus to scan, must be set to 5 (pci1) on pci 1 machines */ 0, /* led 0 */ 0, /* led 1 */ 0, /* led 2 */ 0, /* led 3 */ 0, /* dmarotate */ 0, /* tp */ 0, /* full duplex */ 0 /* fast isa*/ } #endif };
PCNET family network driver installation guide 114
115 12. installing the sco unixware 2.x dlpi driver the sco unixware 2.x has built-in support for the PCNET driver. __1 use the unixware dcu utility to install the built-in PCNET driver. for help, see the sco unixware manual. __2 to upgrade to a new version of the driver, copy driver.o and space.c from disk 2 of the amd drivers to /etc/conf/pack.d/pnt directory. note: these files are in dos format in unixware 2.0 directory on the amd diskette and can be copied using the doscp command or from the dos merges session. __3 rebuild the kernel with /etc/conf/bin/idbuild command. 12.1. unixware 2.x dlpi driver keywords keywords can be added, deleted, and/or modified by manually editing the appropriate #define values in the space.c file. see appendix b ( software keywords ) and your sco unixware manuals for more details. for the sample version of this file, see the unixware 1.1 section. the PCNET driver for unixware 2.x has an additional keyword, PCNET2 . if set to a non-zero value, this keyword enables advanced features for the PCNET-pci2 chip.
PCNET family network driver installation guide 116
installing the vxworks driver 117 13. installing the vxworks driver 13.1. introduction the vxworks ethernet device driver is compatible with the PCNET-pci ii and the PCNET- fast network controllers. the source code of the driver is integrated and compiled in the vxworks operating system, and the boot image of the standalone vxworks (vxworks.st) is loaded onto the floppy diskette. this diskette may be used as a boot diskette to load the vxworks operating system. 13.2. installation procedure to install, follow the steps listed below: __1 insert the floppy diskette into the floppy drive and boot up the system with the vxworks operating system. __2 refer to the vxworks 5.3.1 programmer's guide to mount the hard disk and also to attach the network interface card. the command to attach the network card is: usrnetinit() __3 the initial network address and the host address are obtained from the boot parameters. to change the network interface address, use the command: ifaddrset. eg: ifaddrset( inpci , 139.95.95.1 ) __4 in order to add other hosts to connect to the vxworks system, user the command: hostadd() with the appropriate parameters.
PCNET family network driver installation guide 118
installing the sunsoft solaris driver 119 14. installing the sunsoft solaris driver support is provided for the sunsoft solaris x86 (version 2.1) environment. to install amd?s solaris driver, follow the steps listed below: __1 login as root. __2 at the prompt, type: pkgadd -d pnt where is the floppy drive (/dev/fd0). that is, the above line should look like the following: pkgadd -d /dev/fd0 pnt for more information, see the man page for pkgadd (enter man pkgadd for help). then press . __3 insert the amd solaris driver diskette into the floppy drive. __4 enter the path to the package base directory ( /kernel/drv ). __5 enter the pa th where you want the driver object installed ( /kernel/drv ). __6 the pkgadd application now installs: /kernel/drv/pnt /kernel/drv/pnt.conf __7 wait for the process to complete. __8 change into the directory where you installed the driver object ( cd /kernel/drv ). __9 edit the pnt.conf file ( vi pnt.conf ). for more information, see the man page on driver.conf for help ( man driver.conf ). make the following changes: a. change name to indicate the driver name ( name = pnt ). b. change class to indicate the system bus type ( class = sysbus ). c. change dmachan to indicate the dma channel ( dmachan = 5 for PCNET-isa). d. change intr to indicate the interrupt handle and line ( intr = 5,5 for PCNET-isa). e. delete ad ditional entries in the table to reflect the number of PCNET cards in
PCNET family network driver installation guide 120 the system. example (for PCNET-isa): name= pnt class= sysbus dmachan=5 intr=5,5 reg=0,0,0; __10 at the prompt, type the following: add_drv pnt then press . for more information, see the man page on add_drv for help ( man add_drv ). __11 edit the hosts file ( vi /etc/hosts ). make the following changes: add the ip address, hostname, and set entry as loghost. note : remove default local host entries. for example, if ipaddress = 77.0.12.4 hostname = solaris-24-1 127.0.0.1 localhost #loghost #solaris-24-1 77.0.12.4 loghost solaris-24-1 __12 edit the hostname.pcn0 file ( vi /etc/hostname.pnt0 ). enter the hostname in the file. for example, if hostname = solaris-24-1 solaris-24-1 __13 edit the netmasks file ( vi /etc/netmasks ). add the entry to conform to network requirements. for example, if ipaddress = 77.0.12.4 and you wish to limit access to the local segment 77.0.12.4 255.255.255 0 this will permit the system to recognize stations with ip addresses between 77.0.12.0 and 77.0.12.255. __14 reboot the system (shutdown -g0). the following message is displayed during the reboot phase: configuring network interfaces: pnt0 the ins tallation of the sunsoft solaris driver is now complete.
installing the sunsoft solaris driver 121 14.1. sunsoft solaris driver keywords see table 5 for sunsoft solaris driver keywords. table 2 . sunsoft solaris driver keywords keyword description keyword name additional keyword details range default driver name name= pnt this is required. n/a n/a driver class class= sysbus this indicates the system bus not the device type. n/a n/a interrupt [intr=5,x] see common keywords. i/o address [ioaddr= io_addr] see common keywords. dma [dmachan= dma_no] see common keywords. (isa only) full duplex fdup fdup keyword is used to enable or disable full duplex on the 10baset and aui ports. see common keywords. utp aui off not present (what is in the eeprom)
PCNET family network driver installation guide 122
installing the packet driver 123 15. installing the packet driver the amd packet driver for the PCNET architecture (backward compatible to the am2100/am1500t) is based on the packet driver from clarkson university. 15.1. driver installation using the aminstal utility follow the steps listed below: __1 run the aminstal utility to configure your PCNET adapter card?s i/o base address, irq channel, and dma channel. see the aminstal utility section for more information on configuring your PCNET adapter card. once you have completed the configuration of your PCNET adapter card using aminstal, go to step 2 below to continue. __2 select the continue button in the configuration dialog box. the installation dialog box will appear. __3 select the desired PCNET adapter card by highlighting it in the top of the dialog box. __4 highlight the packet driver to install the driver. change the default path if necessary. the default directory is: c:\pktdrv . __5 press the continue button to complete the installation. aminstal will copy the selected driver file into the specified directory and create a sample autoexec.net file in the specified directory. the autoexec.net file contains the following: pcntpk int=0x60 ioaddress= irq= dma= note : the packet driver uses a software interrupt to provide a handle for a tcp driver to automatically scan. the software interrupt range is 0x60-66. the aminstal utility uses a default value for int of 0x60. if there is a conflict with other software settings, please change this setting by e diting the autoexec.net file. __6 exit aminstal when the installation has been completed. the user may need to make modifications to the system files, using the amd sample files as reference. the installation of the packet driver is now complete.
PCNET family network driver installation guide 124 15.2. driver installation from the command line prompt source and executable code for the dos version of the packet driver is provided. a number of other utilities (including source) which run above the packet driver are also provided, as well as a number of documentation files. it is recommended that you read all of the information available. the most important file to start reading is install.doc . utilities are also described in this file. copy the amd packet driver (pcntpk.com) into a directory. the packet driver can be loaded from the dos prompt or from the autoexec.bat file. the command line format for the packet driver is: pcntpk [-n] [-d] [-w] [irq=int_no] [ioaddr=io_addr] [dma=dma_no] [bustype=bus] [dmarotate] [tp] [led0=xx] [led1=xx] [led2=xx] [led3=xx] [fdup=xx] when using windows, use either the -w option or the winpkt utility (see install.doc ). if the [irq=int_no], [ioaddr=io_addr], and [dma=dma_no] are not specified for the PCNET-isa adapter card, the default values are assumed by the packet driver. note : the following : int=packet_int_no is a handle for an upper layer interface (normally 0x60-66). this is not optional. an upper layer application such as tcp scans for the int handle between 0x60-66. additional common keywords may be specified. please refer to the software keywords section (appendix b) in this manual for more information. 15.3. keyword example an example command line is as follows: pcntpk int=0x60 irq=3 ioaddr=0x300 dma=5 15.4. packet driver keywords see table 6 for packet driver keywords.
installing the packet driver 125 table 3 . packet driver keywords keyword description keyword name additional keyword details range default packet converter [-n] the -n option converts ethernet type 8137 and novell pso-like packets. this is required if you use a standard boot rom from amd and use the packet driver and ipx included in the packet driver package as the drivers load from the boot image file. n/a not enabled initialization delay [-d] the -d option delays initialization. the -d option will keep the initialization code after loading. this is required for boot rom support. n/a not enabled windows option [-w] the -w switch is used for windows. install the packet driver before running ms-windows. this switch does not prevent windows from swapping the network application out of memory, it simply detects when that has happened, and drops the packet. see the winpkt utility for enhanced mode applications. n/a not enabled software interrupt this is the software interrupt used to communicate with the packet driver. see appendix a of the install.doc file for more details. 0x60-0x66 0x60
PCNET family network driver installation guide 126 keyword description keyword name additional keyword details range default i/o address [ioaddr= io_addr] see common keywords dma [dma= dma_no] see common keywords. full duplex fdup * supported on PCNET-isa ii only fdup keyword is used to enable or disable full duplex on the 10baset and aui ports. see common keywords. utp aui off not present (what is in the eeprom) note : keyword options for the packet driver may be activated by loading the driver at the command line or loading the driver from a batch file like autoexec.bat.
installing the dmi component interface (ci) 127 16. installing the dmi component interface (ci) 16.1. desktop management interface (dmi) the dmi brings manageability and intelligence to computer systems such as desktop pcs and servers, allowing vendors to easily add manageability to their products. the dmi works synergistically with existing standards such as plug ?n? play and simple network management protocol (snmp). specifically, amd?s dmi support (mif file and instrumentation) extends to the following drivers: ndis 2 dos driver ndis 2 os/2 driver ndis 3 windows for workgroups driver odi dos client driver odi os/2 client driver the dmi is a local interface to be used within a single system. it provides a means by which component instrumentation developed by multiple vendors can interplay within a single system to uniformly provide management information. the desktop management task force?s (dmtf) dmi interface consists of the following elements: the service layer (sl), a local program that collects information from components, manages that information through the mif database, and passes the information to management applications as requested. it controls communication between itself and management applications by means of the management interface (mi), and between itself and manageable products by means of the component interface (ci). see the dmi specification for detailed information. the mif database, which contains the information about the products installed on or attached to the system. the service layer manages the information in the database. the information comes from mif files provided with each manageable product. see the dmi specification for detailed information. management applications, remote or local programs for interrogating, changing, controlling, tracking, and listing the elements of a desktop system. a management application can be a graphical user interface program, a network management agent, an installer program, a diagnostics program, or a remote procedure call. see the dmi specification for detailed information. manageable products, also called components , are hardware, software, or peripherals that occupy or are attached to a desktop computer, such as hard disks, word processors, cd-roms, printers, motherboards, operating systems,
PCNET family network driver installation guide 128 spreadsheets, graphics cards, sound cards, and modems. each product provides information to the mif database by means of a mif file that contains the pertinent management information for that product. see the dmi specification for detailed information. the dmi structure is shown in figure 9 below. 16.1.1. service layer the service layer (sl) is the system-resident program that manages all dmi activities. it is a background task or process that is always ready for a request from a management application or managed components. there are specific implementations of the service layer for different operating systems and environments. refer to the dmi specification for installation procedures. 16.1.2. component interface (ci) the ci, an integral part of the sl, handles communication between component instrumentation and the sl. it shields vendors from the complexity of management information encoding and minimizes the responsibilities of the instrumentation. management applications management interface (mi) service layer (sl) component interface (ci) mif database hardware and software components general instrumentation net driver figure 9. desktop management interface structure
installing the dmi component interface (ci) 129 16.2. dmi installation program (dmi version 1.1) the dmi installation program edits the PCNET.mif file and copies the dmi instrumentation files and the mif file as follows: source file destination directory PCNET.mif c:\dmi\dos\mifs\backup PCNET.ovl c:\dmi\dos\bin PCNET.exe c:\dmi\win16\bin the installation program performs the following edits to the PCNET.mif file: 1. chooses comment or uncomment the path string for the dos overlay instrumentation, depending on whether the target driver (the driver that is going to be used in the system) is the windows for workgroups v3.11 ndis 3 driver or one of the dos drivers: ndis 2 or odi (comment for the former and uncomment for the latter). 2. inserts the serial number in the ?value? section of the ?serial number? attribute field. 3. inserts the installation date in the ?value? section of the ?installation? attribute field. 4. inserts the connector type in the ?value? section of the ?connector type? attribute field. these edits can be done manually if desired. a properly edited mif file can be installed with any dmi management application that supports a mif install feature such as the browser provided with the dmi sdk. 16.2.1. invoking dminstl to invoke the amd dmi installation utility from the distribution diskettes, insert diskette 6 into the a: drive. issue the following commands (assuming the diskette has the write- protect feature disabled ): a:>cd \dmi a:\dmi>dminstl the installation program can be copied to a directory on the target system and executed from there. the only limitation is that the files to be installed reside in the same directory as the installation program proper (this is true for installation from the floppy drive as well). note : when performing the dmi installation using the amd dmi installation utility (dminstl), remove all tsrs that are not essential to the installation. for example, if installing on an ms-dos v6.2 system, pressing the f5 key while the message, "starting ms-dos..." is displayed will bypass the system startup files and boot a clean system
PCNET family network driver installation guide 130 startup. if using an earlier version of dos (e.g., v3.3), booting from a floppy without the config.sys and autoexec.bat file will achieve the same result. once the system has been started using this method, the dmi installation program can be used to install dmi support for the PCNET drivers. 16.2.1.1. directory structure dminstl expects the following directory structure to exist in the target environment. if the directory structure does not exist, the installation program will create it. see figure 10. c: dos bin dmi mif win1 bin figure 10. directory structure 16.2.1.2. dminstl interaction with sl dminstl interacts with the service layer in one of two ways. if the sl is loaded, the installation program invokes it as required to perform the installation. if the sl is not loaded, dminstl loads it before continuing. once the installation completes, the sl is unloaded if dminstl loaded it. if the sl is not available on the target system, dminstl copies the PCNET.mif file both to the c:\dmi\dos\mifs and c:\dmi\dos\mifs\backup directories. 16.2.1.3. moving between fields once the installation program has been invoked, it presents a forms based interface with two text input fields and two pull-down menu fields. to move between the fields, the tab key is pressed repeatedly until the cursor enters the desired text input field, or until the desired pull down menu field is highlighted.
installing the dmi component interface (ci) 131 16.2.2. editing input 16.2.2.1. text edit fields when the cursor enters a text input field, three actions can be effected on the field itself. the cursor can be advanced one character position for each press of the right- arrow key except at the rightmost position of the field where the cursor ceases to advance. by pressing the left-arrow key, the cursor can be moved to the left by one character position in the same manner as when moving it to the right. finally, characters entered into the field are placed at the current cursor position and the cursor is advanced by one position to the right. again, at the end of the field, the character is inserted but the cursor is not advanced. 16.2.2.2. pull down list when the cursor is placed in a pull down menu field, the field is highlighted. to display the pull down list, press the down-arrow key while holding down the alt key. once displayed, the items in the list can be highlighted by using the up and down arrow keys. pressing the enter key selects the highlighted item and hides the pull down list. to hide the pull down list without making a selection, press the esc key. 16.2.3. starting the installation program the f10 key is used to instruct dminstl to begin the actual installation process. after filling all the fields as desired, press f10. see the subparagraphs below to get a description of the fields. dminstl will display a progress dialog in the center of the screen. the dialog will alternately draw and erase a blue bar in the center of the screen to demonstrate that the installation is progressing. once the installation completes, one of two actions will occur. if the installation succeeded, a dialog box appears indicating the success of the operation and the component id assigned to the driver. if the installation fails, a message box appears indicating the source of the failure. again, a key must be pressed to clear the message. 16.2.3.1. serial number the serial number field is used to enter the serial number of the network adapter card package. the number can usually be found on the outside of the package or on the distribution media. the purpose of this field is to allow the serial number of the package to be readily retrieved in case it is required for any purpose such as technical assistance. the serial number field is a straight text field. this means that it will accept any text (letters or numbers) that is typed into it.
PCNET family network driver installation guide 132 16.2.3.2. installation date the installation date field is initialized to the system date and time. the field uses the following format. mmm dd hh:mm:ss yyyy the ?mmm? portion represents the month. the following values are accepted: jan apr jul oct feb may aug nov mar jun sep dec the ?dd? subfield represents the day of the month and can be any legal value between 1 and 31. the hh:mm:ss subfield is used to denote the current time. the h, m, and s symbols represent the hours, minutes, and seconds, respectively. finally, the ?yyyy? field represents the year. any errors detected in the format of the time and date field will cause the value to be rejected and an error message displaying the required format to be displayed. 16.2.3.3. connector type the connector type field identifies the three possible connectors that can be used with the network interface controller. the three connector types currently supported are as follows: 1. aui 2. 10baset (rj45) 3. 10base2 (bnc) the connector type field is a pull down menu field. to display the choices, press alt- downarrow. 16.2.3.4. target driver the target driver field identifies the driver to be used with the dmi software. to select the desired driver, pull down (alt-downarrow) the menu and select either: 1. ndis 3 2. ndis 2/odi
installing the dmi component interface (ci) 133 the first selection is for use with windows for workgroups version 3.11. the second is for use with any network operating system that uses either the ndis 2 or odi drivers (e.g. lan server or netware, respectively). 16.2.4. exiting the installation program the installation program can be terminated at any time prior to pressing f10 to begin the actual installation process. to exit the program, press the f4 key while holding down the alt key. once the f10 key is pressed, the installation process must continue until complete. 16.3. dmi installation procedure (dmi version 2.0) to install, follow the steps listed below: __1 copy the PCNET.mif and PCNET.exe files to a directory (for instance, PCNET). __2 install intel's dmi sdk and dmi explorer. __3 reboot the system. make sure that the service layer (win32sl.exe) program is running. __4 launch the dmi explorer program. click on the add component option under the file menu. specify the path of the PCNET.mif file and click on the ok button. __5 from the start menu, run the PCNET.exe program. __6 in the dmi explorer window, double click on the my computer icon. you will see the item, amd PCNET ethernet controller component. expanding this item will show the 19 groups under it. you can examine the attributes and their corresponding values by expanding the group you are interested in. __7 if you are running the permanet server software driver and you have configured two adapters as a pair, you will see a pop-up message each time the primary nic fails or recovers. this can be demonstrated by causing a link failure on the primary nic by pulling the primary adapter's cable.
PCNET family network driver installation guide 134
installing a universal boot rom 135 17. installing a universal boot rom located in the bootrom directory of an amd driver diskette is a file called netrom.hex . boot rom support is provided for the PCNET-isa devices, PCNET vl device, and PCNET-pci devices. remote boot is allowed from the following servers: ? novell server ? microsoft lan manager (server) the boot rom is based on the ibm rpl protocol. to install the universal boot rom, follow the steps listed below: __1 obtain a boot rom from amd or borrow a prom with the netrom.hex file. this hex file is in intel mcs-86 hex format. note : currently, any eeprom greater than or equal to 16k in size can be used. also, this eeprom should be 250 ns or faster __2 insert the boot rom into the 28-pin socket. __3 if you are using a PCNET-isa adapter card, then go to step 3.1 below. otherwise, go to step 3.2 below. __3.1 for a PCNET-isa adapte r card: a. install the boot rom jumper to enable the boot rom. next, set the jumpers for the i/o base address, irq channel, and dma channel. b. for PCNET-isa, you must use one of the four configurations listed below when setting the jumpers: config option i/o addr irq dma boot rom addr 1 300h 3 5 c80000h 2 320h 4 6 cc000h 3 340h 5 7 d0000h 4 360h 9 3 d4000h note : boot rom addresses listed above are not jumper settings. c. go to step 4 below to continue. __3.2 for PCNET pnp isa adapter cards: a. using aminstal, configure the PCNET pnp isa adapter cards with available boot rom address.
PCNET family network driver installation guide 136 b. go to step 4 to continue. notes : 1) refer to the aminstal section to use the aminstal utility. 2) if a PCNET pnp isa adapter card is configured as a plug and play mode, boot rom address will be selected automatically (which is the same as the PCNET vl device and the PCNET pci devices). __4 follow the boot rom installation procedure outlined in the novell installation manual , microsoft lan manager server manual , or ibm lan server manual to prepare the server to support rpl. __5 if you are going to do a remote boot for an os/2 workstation on microsoft lan manager, follow the steps listed below prior to performing a remote boot from the server. otherwise, go to step 6 below to continue. a. edit the file os213bb.cnf . the path to this file is as follows: c:\lanman\rpl\bblock\netbeui\pcntd notes : 1) the file os213bb.cnf is a remote boot configuration file for os/2 version 1.3. if you are running a different version of os/2 on your workstation, the file name may be slightly different. 2) in the path for the os213bb.cnf file, netbeui may be different depending on which protoc ol you are using. b. edit the following line in the os213bb.cnf file: drv bblock\ndis\pcntnd.dos ~ ~ ~ note : the drv line shown above is the default. the tildes ( ~ ) represent parameter fields. by default a tilde means 0. change the second tilde to a value of 10. c. the drv line should now look like: drv bblock\ndis\pcntnd.dos ~ 10 ~ save the os213bb.cnf file. d. go to step 6 to continue. __6 next, perform a remote boot from the server. the diskless workstation will display some sign-on messages followed by: to boot from novell server, press 1 to boot from ibm lan server 2x and 3x, press 2 to boot from ibm lan server 4x, press 3 to boot from microsoft lan manager, press 4 to boot from the first available se rver, press 5 if no selection within 30 seconds, will use choice 5 please, make your choice now!
installing a universal boot rom 137 you may now make a selection by pressing the appropriate number. if nothing is selected within 30 seconds, the appropriate server will be selected by auto detect. this is also used to support workstations without a keyboard and monitor. after the selection is made, the remote boot process is started. note : this version of boot rom does not display the boot from network (y/n) message. make sure you do not have a bootable device in the system (i.e., no a or c drive). in a diskless system without a bootable device, this boot rom will take over the boot process.
PCNET family network driver installation guide 138

▲Up To Search▲

Price & Availability of PCNET

	To Download PCNET Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .