Diff: HowToTokenRing - Waikato Linux Users Group

Differences between current version and previous revision of HowToTokenRing.

Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History

Newer page:	version 3	Last edited on Friday, October 29, 2004 4:29:10 am	by StuartYeates
Older page:	version 2	Last edited on Friday, June 7, 2002 1:07:42 am	by perry	Revert

@@ -1,2741 +1 @@

-~~Token-Ring mini-HOWTO~~

-~~!!!Token-Ring mini-HOWTO~~

-~~!Mike Phillips~~

-

- ~~mikep@linuxtr.net~~

-

-~~!Tom Gall~~

-

- ~~tom_gall@vnet.ibm.com~~

-

-~~!Mike Eckhoff~~

-__Revision History__Revision 5.002002-01-23Revised by: mlpUpdated to reflect the current state of Token Ring with !LinuxRevision 4.329 March 2000Revised by: tgBrought up to date.Revision 4.17 January 1998Revised by: mev4.1 released by Mike

-

- ~~This howto is designed to help you get up and running using a Token~~

-~~Ring adaptor to access the network. Generally speaking Section 3~~

-~~will tell you which driver you need based on the adaptor card you~~

-~~have.~~

-

-----; __Table of Contents__; 1. Introduction: ; 1.1. Special Thanks; 1.2. Copyright Information; 1.3. Disclaimer; 1.4. New Versions; 1.5. Credits; 1.6. Feedback; 2. Hardware requirements; 3. Which driver should I use?: ; 3.1. Drivers/Adapter Specifics; 4. Known problems; 5. VMWare and Token Ring; 6. Commonly asked Questions; A. GNU Free Documentation License: ; A.1. . PREAMBLE; A.2. 1. APPLICABILITY AND DEFINITIONS; A.3. 2. VERBATIM COPYING; A.4. 3. COPYING IN QUANTITY; A.5. 4. MODIFICATIONS; A.6. 5. COMBINING DOCUMENTS; A.7. 6. COLLECTIONS OF DOCUMENTS; A.8. 7. AGGREGATION WITH INDEPENDENT WORKS; A.9. 8. TRANSLATION; A.10. 9. TERMINATION; A.11. 10. FUTURE REVISIONS OF THIS LICENSE----

-~~!!!1. Introduction~~

-

- ~~Welcome to the Linux Token Ring mini-howto. We hope you find the information~~

-~~contained within helpful.~~

-

- ~~If you have any problems with the drivers that are not talked about in~~

-~~this howto, feel free to email me at `mikep@linuxtrnetb.~~

-

- ~~You may also wish to join the Linux on Token Ring Listserv~~

-~~by mailing `majordomo@linuxtr.netb with the body containing:~~

-

-~~subscribe linux-tr~~

-~~The latest and greatest information, drivers, patches, bug fixes, etc, etc~~

-~~can always be found at the Linux Token Project site.~~

-

-~~----~~

-~~!!1.1. Special Thanks~~

-

- ~~Thanks to Mark Swanson, Peter De Schrijver, David Morris, Paul Norton~~

-~~and everyone else who has contributed to the Token Ring code~~

-~~and drivers over the years.~~

-

- ~~Thanks also to the many people and companies who have provided~~

-~~hardware and technical documents to enable the drivers to be~~

-~~written in the first place.~~

-

- ~~Special Thanks to Mike Eckhoff the originator of this HOWTO, and Tom Gall~~

-~~for the previous version, and to Matthew Marsh for hosting~~

-~~the website and mailing list!~~

-

- ~~And, finally, thanks to all to subscribers to the linux-tr mailing list who~~

-~~have provided support, feedback, testing and thanks over the years. It~~

-~~wouldn't have been worth it without your continued support and gratitude.~~

-

-~~----~~

-~~!!1.2. Copyright Information~~

-

-~~Phillips.~~

-

- ~~Permission is granted to copy, distribute and/or modify this~~

-~~document under the terms of the GNU Free Documentation License,~~

-~~Version 1.1 or any later version published by the Free Software~~

-~~Foundation, with no Invariant sections, with no Front-Cover Texts,~~

-~~and with no Back-Cover Texts.~~

-

- ~~A copy of the license is included in~~

-~~Appendix A~~

-

- ~~If you have any question, please contact~~

-~~`linux-howto@linuxdoc.orgb~~

-

-~~----~~

-~~!!1.3. Disclaimer~~

-

- ~~No liability for the contents of this document can be accepted.~~

-~~Use the concepts, examples and other content at your own risk.~~

-~~As this is a new edition of this document, there may be errors~~

-~~and inaccuracies, that may of course be damaging to your system.~~

-~~Proceed with caution, and although this is highly unlikely,~~

-~~the authors do not take any responsibility for that.~~

-

- ~~All copyrights are held by their respective owners, unless~~

-~~specifically noted otherwise. Use of a term in this document~~

-~~should not be regarded as affecting the validity of any trademark~~

-~~or service mark.~~

-

- ~~Naming of particular products or brands should not be seen as~~

-~~endorsements.~~

-

- ~~You are strongly recommended to take a backup of your system~~

-~~before major installation and backups at regular intervals.~~

-

-~~----~~

-~~!!1.4. New Versions~~

-

- ~~The latest version of this document can always be found at~~

-~~Linux Token Ring Project~~

-~~under the Documentation section.~~

-

- ~~The latest version of this HOWTO will always be made available on~~

-~~the Linux Token Ring Project website, in a variety of formats:~~

-

-*

-

- ~~HTML,~~

-

-*

-

- ~~Plain text,~~

-

-*

-

- ~~Adobe Acrobat pdf,~~

-

-*

-

- ~~Postscript,~~

-

-*

-

- ~~SGML source,~~

-

-*

-

-~~----~~

-~~!!1.5. Credits~~

-

- ~~In this version I have the pleasure of acknowleding:~~

-

- ~~''IBM'' for providing hardware,~~

-~~technical documentation and technical support when the tech docs~~

-~~didn't quite seem enough.~~

-

- ~~''Madge'' for providing their hardware to test with.~~

-

- ~~''3Com'' for proving the technical documents to~~

-~~allow the 3c359 driver to be developed.~~

-

-~~----~~

-~~!!1.6. Feedback~~

-

- ~~Feedback is most certainly welcome for this document. Without your~~

-~~submissions and input, this document wouldn't exist. Please send~~

-~~your additions, comments and criticisms to the following email~~

-~~address: `mikep@linuxtr.netb~~

-

-~~----~~

-~~!!!2. Hardware requirements~~

-

- ~~Make sure that you have a Token Ring card that is supported from~~

-~~the list below. Many PCI,ISA and even the odd MCA cards are now~~

-~~supported. Check http://www.linuxtr.net for~~

-~~the latest information.~~

-

- ~~Cards that are reported to work:~~

-

- ~~3COM~~

-

-*

-

-~~3C389 PCMCIA~~

-

-*

-

-~~3C619, 3C619B or 3C619C Token Link~~

-

-*

-

-~~3C319 Velocity ISA~~

-

-*

-

-~~3C359 Velocity XL - PCI~~

-

-*

-

-~~3C339 Velocity PCI~~

-

-*

-

- ~~IBM~~

-

-*

-

-~~__PCI. __ PCI Token Ring Adapter; PCI Wake on Lan Token Ring Adapter; 16/4 Token Ring~~

-~~PCI Adapter 2, Wake on Lan, and Wake on Lan Special; High Speed 100/16/4~~

-~~Token Ring Adapter, Token Ring 16/4 Management Adapter.~~

-

-*

-

-~~__Cardbus. __ 16/4 Token Ring Adapter~~

-

-*

-

-~~__!LanStreamer. __ PCI: Auto !LanStreamer, Triple Lanstreamer; MCA: !LanStreamer MC16, Lanstreamer~~

-~~MC32, !AutoLanstreamer MC32, Dual Lanstreamer MC32~~

-

-*

-

-~~__ISA. __ Auto 16/4 Token Ring Adapter, 16/4 Token Ring Adapter, Turbo 16/4 Token~~

-~~Ring Adapter, Auto Wake Token Ring Adapter.~~

-

-*

-

-~~__PCMCIA. __ Turbo 16/4 PC Card, Turbo 16/4 PC Card 2, Auto 16/4 Credit Card Adapter,~~

-~~16/4 Credit Card Adapter, 16/4 Credit Card Adapter II~~

-

-*

-

-~~__Tropic MCA. __ 16/4 Token Ring Adapter/A, Auto 16/4 Token Ring Adapter~~

-

-*

-

- ~~Olicom~~

-

-*

-

-~~!RapidFire 3139, 3140, 3141, and 3540~~

-

-*

-

-~~OC 3136~~

-

-*

-

-~~OC 3137~~

-

-*

-

-~~OC 3118~~

-

-*

-

-~~OC 3129~~

-

-*

-

- ~~Madge~~

-

-*

-

-~~51-02 Smart 16/4 PCI~~

-

-*

-

-~~20-03 16/4 Cardbus Adapter Mk2~~

-

-*

-

-~~51-04 Smart 16/4 PCI Ringnode Mk3~~

-

-*

-

-~~51-09 Smart 16/4 Fiber PCI Ringnode~~

-

-*

-

-~~51-07 Smart 100/16/4 PCI-HS Ringnode~~

-

-*

-

-~~51-05 Smart 100/16/4 PCI Ringnode~~

-

-*

-

-~~20-01 Smart 16/4 PCMCIA~~

-

-*

-

-~~60-07 Presto PCI 2000~~

-

-*

-

-~~60-06 Presto PCI Plus~~

-

-*

-

-~~60-05 Presto PCI~~

-

-*

-

-~~53-05 Smart Mk4 PCI Adapter (low profile)~~

-

-*

-

-~~31-40 Rapidfire 3140V2 16/4 PCI Adapter~~

-

-*

-

- ~~!SysKonnect~~

-

-*

-

-~~TR4/16(+) SK-4190 ISA~~

-

-*

-

-~~TR4/16(+) SK-4590 PCI~~

-

-*

-

-~~TR4/16(+) SK-4591 PCI~~

-

-*

-

- ~~SMC~~

-

-*

-

-~~Tokencard Elite (8115T)~~

-

-*

-

-~~Tokencard Elite/A MCA (8115T/A)~~

-

-*

-

- ~~Intel~~

-

-*

-

-~~!TokenExpress PRO~~

-

-*

-

-~~!TokenExpress 16/4~~

-

-*

-

- ~~Cards that may cause problems:~~

-

-~~__Token-Ring Network 16/4 Adapter II. __ This adapter will NOT work.~~

-~~Do not confuse this card with the IBM Token Ring adapter II (4mbit)~~

-~~which does. It is a DMA/Busmaster adapter for ISA.~~

-

-~~__3Com !TokenLink Velocity ISA. __ You may or may not get this one to work.~~

-~~I have had reports of people running it without problems,~~

-~~and others who get errors left and right.~~

-

-~~----~~

-~~!!!3. Which driver should I use?~~

-

- ~~The realm of Token Ring drivers on Linux has expanded quite a bit in~~

-~~last couple of years. It's not just ibmtr anymore! So as a result this~~

-~~map will tell you given a card which driver you should try and the~~

-~~recommended minimum kernel version (if any).~~

-

- ~~3COM~~

-

-*

-

-~~3C389 PCMCIA -- ibmtr_cs~~

-

-*

-

-~~3C619, 3C619B or 3C619C Token Link -- ibmtr~~

-

-*

-

-~~3C319 Velocity ISA -- try ibmtr~~

-

-*

-

-~~3C359 Velocity XL - PCI -- driver available from~~

-~~http://www.linuxtr.net~~

-

-*

-

-~~3C339 Velocity PCI -- tms380tr~~

-

-*

-

- ~~IBM~~

-

-*

-

-~~PCI Token Ring Adaptor -- olympic~~

-

-*

-

-~~PCI Wake on Lan Token Ring Adaptor -- olympic~~

-

-*

-

-~~16/4 Token Ring PCI Adaptor 2, Wake On Lan, and Wake on Lan Special -- olympic~~

-

-*

-

-~~High Speed 100/16/4 Token Ring -- olympic~~

-

-*

-

-~~Turbo 16/4 ISA adapter -- ibmtr~~

-

-*

-

-~~Token Ring Auto 16/4 ISA adapter -- ibmtr~~

-

-*

-

-~~Token Ring Auto 16/4 adapter /A -- ibmtr~~

-

-*

-

-~~Token Ring 16/4 adapter /A -- ibmtr~~

-

-*

-

-~~Token Ring adapter /A -- ibmtr~~

-

-*

-

-~~Token Ring adapter II (4 Megabit only) -- ibmtr~~

-

-*

-

-~~16/4 ISA Token Ring card (16bit) -- ibmtr~~

-

-*

-

-~~16/4 ISA Token Ring card (8bit) -- ibmtr~~

-

-*

-

-~~All LANStreamer -- lanstreamer~~

-

-*

-

-~~PCMCIA - Turbo 16/4 -- ibmtr_cs~~

-

-*

-

-~~PCMCIA - 16/4 -- ibmtr_cs~~

-

-*

-

-~~Cardbus - 16/4 - olympic, kernel v.2.4.3 or greater~~

-

-*

-

- ~~Olicom~~

-

-*

-

-~~!RapidFire 3139, 3140, 3141, and 3540~~

-

-*

-

-~~OC 3136~~

-

-*

-

-~~OC 3137~~

-

-*

-

-~~OC 3118~~

-

-*

-

-~~OC 3129~~

-

-*

-~~For these Olicom cards, see their website~~

-~~http://www.olicom.com for drivers. You will need a~~

-~~2.2.x series kernel.~~

-

- ~~Madge~~

-

-*

-

-~~51-02 Smart 16/4 PCI~~

-

-*

-

-~~20-03 16/4 Cardbus Adapter Mk2~~

-

-*

-

-~~51-04 Smart 16/4 PCI Ringnode Mk3~~

-

-*

-

-~~51-09 Smart 16/4 Fiber PCI Ringnode~~

-

-*

-

-~~51-07 Smart 100/16/4 PCI-HS Ringnode~~

-

-*

-

-~~51-05 Smart 100/16/4 PCI Ringnode~~

-

-*

-

-~~20-01 Smart 16/4 PCMCIA~~

-

-*

-

-~~60-07 Presto PCI 2000~~

-

-*

-

-~~60-06 Presto PCI Plus~~

-

-*

-

-~~60-05 Presto PCI~~

-

-*

-~~For these Madge cards you'll want to visit their site~~

-~~http://www.madge.com~~

-~~for drivers and get the 2.31 Madge drivers.~~

-~~You will need either a 2..36 or 2.2.5 as a minimum.~~

-

- ~~2.41 drivers:~~

-

-*

-

-~~51-05 Smart Mk4 PCI Adapter~~

-

-*

-

-~~53-05 Smart Mk4 PCI Adapter (low profile)~~

-

-*

-

-~~31-40 Rapidfire 3140V2 16/4 PCI Adapter~~

-

-*

-

-~~20-03 Smart 16/4 Cardbus Mk2~~

-

-*

-

-~~51-04 Smart 16/4 PCI Ringnode Mk3~~

-

-*

-

-~~60-07 Presto PCI 2000~~

-

-*

-

-~~60-06 Presto PCI Plus~~

-

-*

-

-~~60-05 Presto PCI~~

-

-*

-~~According to the Madge README file the 2.41 driver has been tested on~~

-~~uniprocessor and SMP kernel versions: 2..36, 2.2.5-15 ,2.2.10,~~

-~~2.2.12-20, 2.4.2-2.~~

-

- ~~Other Madge cards are reportedly based on the Texas Instruments tms380~~

-~~chipset and thus as of the 2.3.26 kernel you can try the tms380tr driver.~~

-

- ~~!SysKonnect~~

-

-*

-

-~~TR4/16(+) SK-4190 ISA~~

-

-*

-

-~~TR4/16(+) SK-4590 PCI~~

-

-*

-

-~~TR4/16(+) SK-4591 PCI~~

-

-*

-~~In the 2.2.x series of kernels try sktr. In the 2.3.x and greater~~

-~~series try the tms380tr driver.~~

-

- ~~SMC~~

-

-*

-

-~~Tokencard Elite (8115T)~~

-

-*

-

-~~Tokencard Elite/A MCA (8115T/A)~~

-

-*

-~~Driver is included as part of the 2.3.38+ kernel.~~

-

- ~~Intel~~

-

-*

-

-~~!TokenExpress PRO~~

-

-*

-

-~~!TokenExpress 16/4~~

-

-*

-~~Support for these cards is currently under development.~~

-~~Check http://www.linuxtr.net for status.~~

-

-~~----~~

-~~!!3.1. Drivers/Adapter Specifics~~

-

- ~~Here we'll describe the different options and configurations available~~

-~~for each of the available drivers.~~

-

-~~----~~

-~~!3.1.1. Kernel Module Aliases and Parameters~~

-

- ~~Most drivers accept arguments in the form of module paramters (with the~~

-~~exception of the special case of PCMCIA, which is fully described below).~~

-

- ~~Kernel modules are specified in the file /etc/conf.modules or /etc/modules.conf~~

-~~depending upon which version of modutils you've got.~~

-

- ~~You can directly modify this file or use the tools builtin to your specific~~

-~~distribution. These distribution specific tools are beyond the scope of this~~

-~~document, but you can always directly modify the modules.conf file by hand~~

-~~to get things up and running and then figure out how your distribution~~

-~~handles these files. For example, Debian has several files in the /etc/modutils~~

-~~directory and from these builds the modules.conf file.~~

-

- ~~Kernel modules aliases are utilized to associate a particular name with a~~

-~~kernel module.~~

-

- ~~For token ring, this is used to assign drivers for each of the token ring~~

-~~interfaces so that the system scripts know which driver to insert when~~

-~~you bring an interface up.~~

-

- ~~The format of the alias lines are:~~

-

- ~~alias ''module_name'' interface~~

-

-~~Usually, the only line you'll need for the token ring networking would be~~

-~~something like:~~

-

-~~alias olympic tr0~~

-~~This binds the olympic driver to the tr0 interface so when you type~~

-

-~~ifconfig tr0 up~~

-~~if the tr0 interface is not already loaded, the system will insert the~~

-~~olympic driver, which in turn will find the network card and create~~

-~~the tr0 network device.~~

-

- ~~Kernel modules parameters are specified in the following format:~~

-

- ~~options ''module_name'' ''parameter_1''=XXX~~ [~~[''parameter2''=YYY ...~~ ]

-

-~~Where the modules_name is the name of the driver, i.e. olympic, ibmtr, 3c359 and the~~

-~~` parameters are those available for each driver. See either the following sections for~~

-~~driver specifics or check out the drivers source code.~~

-

- ~~For example, if you wanted to set the Olympic driver to 16 mbps operation and with~~

-~~a default buffer size of 8192 bytes, you would use the following line:~~

-

- ~~options olympic ringspeed=16 pkt_buf_sz=8192~~

-

-~~----~~

-~~!3.1.2. IBMTR Driver~~

-

- ~~IBM Tropic Chipset Based Token Ring Adapters~~

-

- ~~This is the original token ring driver in the kernel and supports almost all~~

-~~adapters that use the IBM Tropic chipset, including the IBM ISA, ISA/Pnp, and~~

-~~a multitude of adapters from other manufacturers.~~

-

- ~~The IBM Turbo 16/4 ISA/PnP adapter will, in fact, work fine with the ibmtr driver.~~

-~~In older drivers you had to run the card in Auto 16/4 compatability mode.~~

-~~The simplest way to set this is to use the LANAID disks~~

-~~sent with the card and run the command:~~

-

-~~LANAIDC /FAST=AUTO16~~

-~~You should then use LANAIDC or LANAID~~

-~~to configure the card according to documentation.~~

-~~The latest drivers for the Turbo Adapters will recognize these adapters~~

-~~and configure them straight out of the box. You may have to either turn~~

-~~off isapnp support in the kernel or modify your isapnp.conf file to~~

-~~enable the adapter.~~

-

- ~~Options:~~

-

- ~~Perusal of the ibmtr source code may leave you to believe that the adapter can~~

-~~take three parameters, however, in reality the driver doesn't take any. These~~

-~~parameters are a hang over from the early stages of the driver and are only~~

-~~intended to be used to force the driver to only test restricted �ddresses when~~

-~~looking for adapters. The information on these options are included here for~~

-~~completeness only.~~

-

-*

-

- ~~''io'': Specify the I/O ports that the driver will check~~

-~~for the presence of any cards. All Tropic based ISA adapters, or adapters~~

-~~emulating the ISA cards will be found on either port 0xA20 or 0xA24. If~~

-~~you know that your adapter is configured for 0xA24 and/or that probing~~

-~~on port 0xA20 will cause problems with your machine, use io to force the~~

-~~driver to check a specific port only.~~

-

- ~~The Turbo adapters (including the confusingly named latest Auto 16/4~~

-~~cards) can have their io regions located anywhere permitted by the PnP~~

-~~specification. This location is found using the new turbo detection code~~

-~~and no parameters are required.~~

-

-*

-

- ~~''irq'' 8 ''mem'': The two options were used~~

-~~to tell the driver exactly which irq to use and where the shared ram for the~~

-~~adapter could be found. These two options are now totally redundant in the driver~~

-~~as the interrupt line and the location of the shared ram is obtained directly by~~

-~~interrogating the adapter.~~

-

-*

-

-~~----~~

-~~!3.1.3. Olympic Driver~~

-

- ~~IBM PCI Pit/Pit-Phy/Olympic chipset based token ring cards~~

-

- ~~Options:~~

-

- ~~The driver accepts four options: ringspeed, pkt_buf_sz,~~

-~~message_level and network_monitor.~~

-

- ~~These options can be specified differently for each card found, i.e if you~~

-~~have two olympic adapters in your machine and want to assign a ring speed of 16mbps~~

-~~to the first adapter, but a ring speed of 4mbps to the second adapter, your options~~

-~~line would read:~~

-

- ~~options olympic ringspeed=16,4~~

-

-~~However, it should be noted that the driver assigns value to each adapter in the~~

-~~order they are discovered� which is usually the order there are present on the pci~~

-~~bus. A little trial and error may be required to be certain which adapter is receiving~~

-~~which configuration option.~~

-

-*

-

- ~~''ringspeed'': Has one of three settings 0 (default), 4 or 16. 0 will~~

-~~make the card autosense the ringspeed and join at the appropriate speed,~~

-~~this will be the default option for most people. 4 or 16 allow you to~~

-~~explicitly force the card to operate at a certain speed. The card will fail~~

-~~if you try to insert it at the wrong speed. (Although some hubs will allow~~

-~~this so be *very* careful). The main purpose for explicitly setting the ring~~

-~~speed is for when the card is first on the ring. In autosense mode, if the card~~

-~~cannot detect any active monitors on the ring it will not open, so you must~~

-~~re-init the card at the appropriate speed. Unfortunately at present the only~~

-~~way of doing this is rmmod and insmod which is a bit tough if it is compiled~~

-~~in the kernel. The driver does support 100 mbps full duplex operation. This~~

-~~is automatically detected by the adapter when connected to an appropriate~~

-~~switch.~~

-

-*

-

- ~~''pkt_buf_sz'': This is this initial receive buffer allocation~~

-~~size. This will default to 4096 if no value is entered. You may increase~~

-~~performance of the driver by setting this to a value larger than the network~~

-~~packet size, although the driver now re-sizes buffers based on MTU settings as well.~~

-

-*

-

- ~~''message_level'': Controls level of messages created by the~~

-~~driver. Defaults to 0 which only displays start-up and critical messages.~~

-~~Presently any non-zero value will display all soft messages as well. NB This~~

-~~does not turn debugging messages on, that must be done by modified the source code.~~

-

-*

-

- ~~''network_monitor'': Any non-zero value will provide a~~

-~~quasi network monitoring mode. All unexpected MAC frames (beaconing etc.)~~

-~~will be received by the driver and the source and destination addresses printed.~~

-~~Also an entry will be added in /proc/net called olympic_tr%d, where tr%d~~

-~~is the registered device name, i.e tr0, tr1, etc. This displays low~~

-~~level information about the configuration of the ring and the adapter.~~

-~~This feature has been designed for network administrators to assist in~~

-~~the diagnosis of network / ring problems. (This used to OLYMPIC_NETWORK_MONITOR,~~

-~~but has now changed to allow each adapter to be configured differently and~~

-~~to alleviate the necessity to re-compile olympic to turn the option on).~~

-

-*

-

-~~__Multi-card. __ The driver will detect multiple cards and will work with shared interrupts,~~

-~~each card is assigned the next token ring device, i.e. tr0 , tr1, tr2. The~~

-~~driver should also happily reside in the system with other drivers. It has~~

-~~been tested with ibmtr.c running. I have had multiple cards in the same~~

-~~system, all sharing the same interrupt and working perfectly fine together.~~

-~~This is also true for the Cardbus Olympic adapters, I have quite happily~~

-~~had a Cardbus adapter and regular 16 bit PCMCIA token ring adapter working~~

-~~together in the same laptop.~~

-

-~~__Variable MTU size:. __ The driver can handle a MTU size upto either 4500 or 18000 depending upon~~

-~~ring speed. The driver also changes the size of the receive buffers as part~~

-~~of the mtu re-sizing, so if you set mtu = 18000, you will need to be able~~

-~~to allocate 16 * (sk_buff with 18000 buffer size) call it 18500 bytes per ring~~

-~~position = 296,000 bytes of memory space, plus of course anything~~

-~~necessary for the tx sk_buff's. Remember this is per card, so if you are~~

-~~building routers, gateway's etc, you could start to use a lot of memory~~

-~~real fast.~~

-

-~~----~~

-~~!3.1.4. Lanstreamer Driver~~

-

- ~~IBM PCI/MCA Lanstreamer chipset based token ring cards~~

-

- ~~Options:~~

-

- ~~The driver accepts three options: ringspeed, pkt_buf_sz,~~

-~~message_level and network_monitor.~~

-

- ~~These options can be specified differently for each card found, i.e if you~~

-~~have two olympic adapters in your machine and want to assign a ring speed of 16mbps~~

-~~to the first adapter, but a ring speed of 4mbps to the second adapter, your options~~

-~~line would read:~~

-

- ~~options lanstreamer ringspeed=16,4~~

-

-~~However, it should be noted that the driver assigns value to each adapter in the~~

-~~order they are discovered� which is usually the order there are present on the pci/mca~~