> Bering uses a 2.4 series kernel, while the Dachstein-small modules from my > site are for the 2.2.19-3 Dachstein kernel. While you might be > able to get > away with using LAN modules from one 2.2 series kernel on another, you > typically can't change major version numbers successfully (too much in the > kernel changes from 2.2 to 2.4). Try using the 2.4 series modules from > Bering, and you'll probably have better luck. >
That did the trick! I used the Bering module with no arguments and the driver worked great. While I was researching the issue, I did discover that IBM Token Ring cards have one of two possible chipsets (Tropic and Olympic). I have no idea what chipset my card has but it is labeled "IBM Auto 16/4 Token Ring ISA", uses a twisted-pair connection and works great with the ibmtr.o module from the Bering distribution. Apparently other IBM Token Ring cards may require the olympic.o driver. In the interests of anyone trying this, I thought I would all add my discovery that the network file must use the Token Ring interface by the label assigned by the driver (to0 in my case). At first I was puzzled by the Token Ring interface not coming up until I realized that I still had the third interface labeled as 'eth2' rather than 'to0'. And, of course, Token Ring 'taint Ethernet... Also, for anyone who needs the setup utilities for this Token Ring card, I actually found them on the Compaq site after failing to find them anywhere on ibm.com - it's a 4-disk set but the important stuff is all on disk 1. paul Paul M. Wright, Jr. McKay Technologies "making technology play nice..." _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
