tulip driver installation

[bubblenut]

Does anyone know where I can find an easy, step by step guide of how to install the tulip driver? I'm having real troubles with it :(

Thanks
Bubble

[knute]

What kind of troubles are you having with it?

Do you need to compile it first, or just install it?

[bubblenut]

I can't remember to be honest. I haven't been able to get it working so I haven't got broadband on my Linux boot so for the last week or so I've just been using <bubble>ducks his head to avoid the swing</bubble> windows. I got as far as the insmod command (I'm doing it as a Kernel module) but it was expecting some parameters (IO range and IRQ if I remember correctly) which I found out but could not find the correct way to pass these parameters to insmod.

I'm going to boot up in linux and find out the details. I'll be back in a bit.

Thanks for your help
Bubble

[knute]

What kind of nic do you have btw?

Also, have you tried the command modprobe -v tulip.
The reason being is that mobprobe can normally configure the attributes automagically by simply asking the card what those settings should be.

HTH

[DMR]

The tulip driver has been built into the kernel for a looooong time. You shouldn't have to compile it from source; you probably have other problems with the NIC setup.

If "modprobe tulip" doesn't work, run the following command and then try the modprobe again:

depmod -ae

(the command may take awhile to run- wait until it returns you to the command prompt)

If that doesn't work, we need a lot more information. The exact make/model of NIC and the exact text of any error messages would be a good start.

Read this (http://www.justlinux.com/forum/showthread.php?threadid=112549), and more specifically this (http://www.stevewolfonline.com/Downloads/DMR/Doc/Linux/Network/NICConfig.txt) for more information and help.


* Note:
I've got a pretty good feeling that this is going to turn out to be a general NIC troubleshooting issue more than a software issue per se, so I'm moving it to the Networking forum.

[bubblenut]

Right I had added an entry into my /etc/modules (it wasn't working before that either) I ran the modprobe before removing the entry in /etc/modules and again after. After running depmod modprobe gave me the following

/sbin/insmod /lib/modules/2.4.20-8/kernel/drivers/net/tulip/tulip.o
Using /lib/modules/2.4.20-8/kernel/drivers/net/tulip/tulip.o
Symbol version prefix ''
/lib/modules/2.4.20-8/kernel/drivers/net/tulip/tulip.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-8/kernel/drivers/net/tulip/tulip.o: insmod /lib/modules/2.4.20-8/kernel/drivers/net/tulip/tulip.o failed
/lib/modules/2.4.20-8/kernel/drivers/net/tulip/tulip.o: insmod tulip failed
[code]
Info on the card (copied from redht's control center)
[code]
00:0b.o Ethernet controller: 3Com Corporation 3CSOHO100B-TX [910-AO1](rev 31)
Subsystem: 3Com Corporation 3CSOHO100B-TX [910-AO1]
Flags: bus master, medium devsel, latency 64, IRQ 10
I/O ports at de00 [size=256]
Memory at effffc00 (32-bit, non-prefetchable)) [size=1K]
Expansion ROM at effc0000 [disabled][size=128K]
Capabilities: <available only to root>

I've also tried setting it up with redhat's gui and even tried reinstalling redhat (in the hope that it would pick it up on install) but all to no avail :(
Cheers
Bubble

[knute]

After a quick google search on the type of nic that you have, I ran across this link. (http://www.tux.org/hypermail/linux-vortex/2002-Dec/0054.html)

Now. I'm not sure if this will help or not, but it's a start.

[DMR]

Originally posted by bubblenut
/lib/modules/2.4.20-8/kernel/drivers/net/tulip/tulip.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesgUm, I don't mean to sound short here, but:

The above message is telling you what to look at for more information about the probable cause, and the second link I gave you in my last post gives specific troubleshooting steps for exactly this problem. Have you tried any of those suggestions yet? If so, please post the complete and accurate results of working through those troubleshooting steps.

[bubblenut]

the lspci -vv ... gives the same details as were pulled from control center, I managed to get as far as the ifconfig command but this gave me nothing to do with the nic even with ifconfig -a; this is all that it gave me.

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8191 errors:0 dropped:0 overruns:0 frame:0
TX packets:8191 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:564679 (551.4 Kb) TX bytes:564679 (551.4 Kb)

ppp0 Link encap:Point-to-Point Protocol
inet addr:62.6.121.240 P-t-P:212.140.88.195 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:584 errors:0 dropped:0 overruns:0 frame:0
TX packets:634 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:461043 (450.2 Kb) TX bytes:104050 (101.6 Kb)


/proc/ioports has the line
de00-deff : PCI device 10b7:9300 (3Com Corporation)
and no other device on that range
/proc/interrupts gives me the following (no eth0) but then I also have nothing in ifconfig to compare it against.

CPU0
0: 580787 XT-PIC timer
1: 4405 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 63379 XT-PIC serial
8: 1 XT-PIC rtc
9: 19332 XT-PIC es1371
10: 228073 XT-PIC usb-ohci
14: 36635 XT-PIC ide0
15: 90 XT-PIC ide1
NMI: 0
ERR: 0


Thanks again
Bubble

[mdwatts]

So you have two ethernet cards? The tulip based as eth0 and the 3Com as eth1?

Have you tried any of the troubleshooting tips DMR posted?

Ensure you have PnP OS disabled in the bios as that alone can be the cause of 'No such device - Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters'.

Have we established what nic model you have that is supposed to be using the tulip module?

[DMR]

Originally posted by mdwatts
So you have two ethernet cards? The tulip based as eth0 and the 3Com as eth1?Mike- where are you seeing references to eth0 and eth1?

Originally posted by mdwatts
Ensure you have PnP OS disabled in the bios as that alone can be the cause of 'No such device - Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters'. Absolutely. This looks very much like an IRQ (interrupt) conflict on your PCI bus, and having Plug-N-Play support enabled in your BIOS is the main cause of that conflict when using a non-Microsoft OS.

That fact that /proc/interrupts shows no IRQ assigned to the NIC really points to this.

Originally posted by mdwatts
Have we established what nic model you have that is supposed to be using the tulip module? Yes, at least from the quick check I did yesterday. However, I didn't have time to check if there are issues regarding specific versions of that model of card needing a module other than tulip. This could be the case, although tulip does seem to be loading, so I'm leaning more towards the IRQ conflict at the moment.

[knute]

Originally posted by knute
After a quick google search on the type of nic that you have, I ran across this link. (http://www.tux.org/hypermail/linux-vortex/2002-Dec/0054.html)

Now. I'm not sure if this will help or not, but it's a start.
:D

[mdwatts]

Originally posted by DMR
Mike- where are you seeing references to eth0 and eth1?


Since 3Com ethernet cards do not use the tulip module, I figured bubblenut must have 2 nics due to


00:0b.o Ethernet controller: 3Com Corporation 3CSOHO100B-TX [910-AO1](rev 31)
Subsystem: 3Com Corporation 3CSOHO100B-TX [910-AO1]
Flags: bus master, medium devsel, latency 64, IRQ 10
I/O ports at de00 [size=256]
Memory at effffc00 (32-bit, non-prefetchable)) [size=1K]
Expansion ROM at effc0000 [disabled][size=128K]
Capabilities: <available only to root>


which is a 3Com nic and bubblenut must have a 2nd ethernet card since this thread is on the tulip module.

Make sense? :)

*cough* Just did a G4L search for 3CSOHO100B-TX and found it does indeed use the tulip module.

Please ignore everything I've said. :rolleyes:

I must be coming down with DMR-itis. :eek:

[DMR]

Originally posted by mdwatts
I must be coming down with DMR-itis. :eek: It's contagious? Uh-oh....


Yes- the "B" version of that card uses the tulip module. The previous (non "B") version usd the 3c59x module like many other 3Com NICs.

:)

[bubblenut]

Right I'm not at my machine for a couple of days but I'll get on this when I get home. One little problem though, when I bought my computer they put a password on my bios (so that I have to take it back to them for maintenance) but they now deny having done this. Will just popping the battery off the motherboard have any bad effects?
Cheers for the help so far
Bubble

[mdwatts]

Originally posted by bubblenut
Will just popping the battery off the motherboard have any bad effects?


Doing so may reset any changed bios settings back to the defaults.

Once you get into the bios, verify all settings (including clock) are set correctly.