Meet the Gang   1   2   3   4   5   6   7   8   9

Installing tulip.o in 6.2

From William Laing

Answered By Ben Okopnik, Breen Mullins

hello

Can someone instruct me how to install the module/ driver in Linux 6.2 .for the Linksys networking card.

The following module came with the card on a floppy and I was able to load it in as follows as per the instructions. I have tulip.o loaded in at this location.

# locate tulip.o
   /lib/modules/2.2.17-14/net/old_tulip.o
   /lib/modules/2.2.17-14/net/tulip.o

Does the old file require to be deleted or may it stay ? I am be having some fun, but not making any headway on insmod.At this point I cant go ant further.

Thanking you. Bill

[Ben] Did you try loading the module that was already on your system? I would do that before using the new one, by preference - consider that to be your fallback position if the new one fails, or gives you any problems. Presumably, you're using the 2.2.17 kernel; all you have to do is type

insmod tulip

If the module loads without errors, check to see if the system actually "sees" the card as it should:

ben@Baldur:~$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:4C:69:6E:75:79
          inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
          BROADCAST PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0x200

Note that your numbers may not be the same as mine; in fact, the line starting with "inet addr" will most likely be absent. This is normal.

Truth to tell, I'm a little surprised at the fact that the manufacter included a module: they're normally compiled for a given kernel, and will error out (although they can be force-loaded) when pushed onto a different one.

The old module (I assume, from the above, that you renamed the original to "old_tulip.o") does not need to be deleted. If you want to test the system with it instead of the new one, you should just be able to type

insmod old_tulip

Don't try to load more than one of them at a time; unload the one that you don't want with

rmmod <module_name>

You can always see what's loaded by typing

lsmod

Ben

Thank you for Clear instructions, much apprecated. The following happens while using the commands you suggested.

Presumably, you're using the 2.2.17 kernel; all you have to do is type...

Yes a 2.2.17-14 kernal

insmod tulip

Yeilds as follows:

Using /lib/modules/2.2.17-14/net/tulip.o: init_module:
Device or resource busy Hint: insmod errors can be caused by incorrect
module parameters including invalid I0 or IRQ parameters.

[Ben] That sounds like it's looking for parameters. This can also be caused by I/O or IRQ conflicts, but ...

[Breen] The tulip cards are all PCI and you shouldn't attempt to specify either IRQs or IO addresses for them. The system assigns these for a PCI device, not the driver.

[Ben] Right. Check "/proc/pci".

insmod old_tulip

Yields the same as the new one. I believe I am guilty of copying both modules myself to the linux box.

[Ben] It sounds like either one will work, once you have the correct parameters.

lsmod

Yeilds:

# lsmod
Module                        Size             Used by
#

With nothing listed.

[Ben] This is fine.

Both machines can ping each other while Window applications are installed suggesting the network path is funtional.

[Ben] Good - knowing that will narrow down any troubleshooting that you may do.

Ben, Breen

Agn thank you people for you kind assistance. The results of your suggestions follow. (It is a bare bones machine text only.)


The kernel is a 2.2.17-14
The card is a Linksys LNE Ver.4.1 TAIMAG HE-012D

I do have other D-Link Cards I have tried, using RTL8139, but the results were the same.

# /var/log/dmesg
    Permission denied
#

[Ben] Erm, you're supposed to read it - not execute it. "/bin/dmesg" will print out the contents; for a bit more scrolling control, try

more /var/log/dmesg

Reading "daemon.log" and "messages" in "/var/log" would be of even more use - they would tell you what happened when you tried to load the module. A quick look at the available parameters for "tulip.o" tells me that there's a "debug" option, enabled by

insmod tulip debug=value

Where "value" is 1-6 (I just took a quick look through the code, and the tests for "tulip_debug" max out at 'if (tulip_debug > 5)...') This should print much more info to the logs.

[Breen] As Ben said, you're supposed to read the file. But you won't find the detection message we're looking for in dmesg; I realize that you need to look in /var/log/messages.

Try this:

# grep tulip /var/log/messages*

You'll be looking for a line similar to this:

messages.3:Oct  8 13:17:41 archy kernel: tulip.c:v0.91g-ppc 7/16/99
[email protected]

That tells us the version of the tulip driver you're using. Mine is old but so is the card I'm using.

Instead of Ben's suggestion of

# insmod tulip

you may want to try

# modprobe tulip

(Some versions of the tulip driver need a shim driver to load first. modprobe will pick that up.)

If that doesn't work, try getting the latest drivers from Donald Becker's site:

ftp://ftp.scyld.com/pub/network/netdrivers-3.0-1.src.rpm

Become root and install the rpm:

# rpm -i netdrivers-3.0-1.src.rpm

# cd /usr/src/redhat/SPECS
# rpm -bb netdrivers.spec

That will build the latest set of drivers.

# cd ../RPMS/i386
# rpm -Uvh netdrivers-3.0-1.i386.rpm
  (you MAY have to use a --force flag with that -- you'll know if you do.)

# depmod -a
# modprobe tulip

Which should get you up and running.

This page edited and maintained by the Editors of Linux Gazette Copyright © 2001
Published in issue 73 of Linux Gazette December 2001

HTML script maintained by Heather Stern of Starshine Technical Services, http://www.starshine.org/

Meet the Gang   1   2   3   4   5   6   7   8   9