Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am having some difficulty in trying to make the driver file. I seem to get error when I follow the instructions form the manufacturer.
Can any give me any assistence in making this file (tulip.o)
You shouldn't need to compile the tulip driver as an external module at all, as it's had native support in the kernel forever.
What version of Redhat are you running, and what is the make/model of your card? For versions of Redhat prior to 7., use linuxconf to set up your NIC. For 7.x, use the Network Administration Tool; just type "neat" (no qoutes) at a prompt.
I am currently running Red Hat 7.0 (though I have attempted to update the kernel to 7.2 from Red Hat - so far unsuccessful)
I have tried to use the tulip driver that the distribution cam with but it does not seem to respond. When I attempt to force the driver to load with
Code:
insmod tulip - f
It comes back with the following error
Code:
Using /lib/modules/2.2.16-22/net/tulip.o
/lib/modules/2.2.16-22/net/tulip.o: ini_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
I have run the diag program in does on the smae machine to deteremine the correct parameters for the card and it appears to be running on IO=6200 and IRQ=11
Is there a way of passing the parameters with the insmod command?
There are a few things that could be going on, but none of them need (or will be fixed by) compiling a new tulip driver.
1) As I asked before- please give us the exact make and model of your NIC card; it makes a difference, especially if you have an old ISA card or a card with a non-standard chipset.
2)insmod isn't as "intelligent" as the "modprobe" command in the fact that insmod doesn't know if one module needs to have another module loaded in order for the first module to function (module dependency). Type the following two commands at a prompt:
depmod -ae
modprobe tulip
If you get no errors, type lsmod and see if the tulip module appears in the resulting list of loaded drivers.
My guess is that the above won't work, because the "device or resource busy" error usually means that you do indeed have a resource (IRQ or I/O address) conflict. I've reponded to a few very similar problems in the past; here's the link to the results I got from the forum search when I went to dig them up. Turning off PNP support in the BIOS is something you should do before trying any of the other remedies.
As to your question of passing parameters, the answer is "yes...sort of"- the success you'll have can depend on the type of card. Options can be passed by adding entries to /etc/modules.conf, although in the case of NICs and their IRQ/IO, I'm pretty sure this only works for ISA cards.
Hi there. I too am having virtually exactly the same difficulties with the SMC1255TX Card. My chip version is apparently a Accton EN1216 (rev11) when I do an lspci. My kernel is 2.4.18 and I can find a tulip.o.gz stashed away somewhere.
My understanding of the situation is that for some reason the driver and the bios aren't talking to each other. Surely just switching the PnP BIOS off and rebooting can't fix it... Surely...
Bugger. I switched off the PnP BIOS and insmod tulip followed by lspci and everything seemed to be absolutely fine. (lspci called the card by its Box Brand name and everything, the ISDN adapters in Harddrake detected the presence of an ethernet card and so on...)
I think what was central to the issue was that at first, I had the card inserted into the final PCI slot, next to the ISA slots. Neither Windows nor Linux liked that one little bit.
I also have a SMC1255tx card... I turned of the PnP in BIOS but I get the same message. I have inserted the card in the middle of the three pci slots on my MSI mainboard.
I think there might be a kernel issue here... I got it to work under SuSe 7.2 with kernel 2.4.4 but not under debian potato with kernel 2.2.something, I therefore expect it to work with the final woody version kernel 2.4.4 but I haven't tried it yet...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.