Intalling my network card driver....   :(

dyma82
dyma82 used Ask the Experts™
on
Hi. I have recently installed RedHat Linux 6.2. I have a Linksys LNE100TX network card. This network card came with the "Linux driver" already. I followed the instructions to install it. In the process I compiled "tulip.c" and "pci-scan.c" by calling "make". Now, eventhough it compiled without errors (at least it did not output anything) the remaining of the process failed. Here is the whole process :

[root@localhost netdrivers]# ls
netdrv.tgz
[root@localhost netdrivers]# tar xzvf netdrv.tgz
kern_compat.h
makefile
pci-scan.c
pci-scan.h
tulip.c
[root@localhost netdrivers]# ls
kern_compat.h  makefile  netdrv.tgz  pci-scan.c  pci-scan.h  tulip.c
[root@localhost netdrivers]# make
gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -I/usr/src/linux/include
-pipe -fno-strength-reduce -DMODVERSIONS   -c -o pci-scan.o pci-scan.c
gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -I/usr/src/linux/include
-pipe -fno-strength-reduce -DMODVERSIONS   -c -o tulip.o tulip.c
[root@localhost netdrivers]# ls
kern_compat.h  netdrv.tgz  pci-scan.h  tulip.c
makefile       pci-scan.c  pci-scan.o  tulip.o
[root@localhost netdrivers]# insmod pci-scan.o
pci-scan.o: unresolved symbol apm_register_callback_Rsmpf70b592f
pci-scan.o: unresolved symbol apm_unregister_callback_Rsmp99700428
[root@localhost netdrivers]# insmod tulip.o
tulip.o: unresolved symbol pci_drv_unregister
tulip.o: unresolved symbol pci_drv_register
[root@localhost netdrivers]#

As you can see I was not able to install the modules.
What can I do?  :(
Thanks a lot for your help in advance.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
At the botton of the source file I found what appears to be the recommended way to compile these "c" files. It is completely useless. It keeps complaining about wrong options and recommending to use "-0"...?????...

I have tried to migrate from Windows to Linux (completely) three times, and things like this really make me think if I am just wasting my time. It is not the problem itself. It is the lack of cooperation that I sense from those who already know how to move inside Linux. Isn't it the whole point to make it as easy as possible for those trying to migrate so that Linux spread around the world??

Nah....never mind...
After several hours navigating around in the web, I found somewhere a little warning about differences in the format use for text files in Linux and Windows.
Could it be that the guys at Linksys by mistake use Windows format to save the tulip.c file on the driver's floppy???

I checked the source code and it seems fine.
Any help pleaseeee???
Thanks a lot in advance
tulip driver comes with the redhat installation also, try that first.
Top Expert 2005
Commented:
There could be a problem with that particular version of the tulip sources. I'd suggest going to http://www.scyld.com/network/tulip.html and using that source.

Also make sure that you have the kernel-source package loaded onto the system before you try to build the driver. The 'build' lines at the bottom of the tulip.c file will work, I've used them.

I understand your frustration, but you'd probably be better off with a later version of RedHat, say 7.3. It is much more likely to support all of your hardware 'out of the box'.
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

Gabriel OrozcoSolution Architect

Commented:
maybe use of modprobe instead insmod, let linux load all the related modules needed.

hope this helps
redhat provides tulip driver use that/

Author

Commented:
How could I check what hardware has been already properly installed and assimilated by RedHat and which one have not???
Top Expert 2005

Commented:
I remember problems with a number of Linksys round-about 6.2-7.1. Linsys has a habit of changing the chipset on any given card without changing the part number, and that may mean that you need a later driver. For RedHat below 7.2 I had to use the sources from scyld.com a number of times to get a Linksys card to work.

The usual approach, unless you have certain knowledge that a replacement driver is needed, it to let RedHat set things up and then see if something doesn't work. And if there is a problem the next step is to bring the box up to date w/respect the the Redhat errata for that release. If the problem still persists, then it's time to think about building a driver from source.

Commented:
it seems to me that your module was compiled but never got installed. try a

#make install

after compiling. this should copy tulip.o to
/lib/modules/kernel/drivers/net/tulip/tulip.o

then do a

#depmod -a

to update the module database and try to load the module with

#modprobe tulip

check the success with

#lsmod

--asem
Gabriel OrozcoSolution Architect

Commented:
mmhhh... make install copies the kernel, not the modules.

make modules_install, will.
sometimes, make modules gives errors, u can use
make mrproper
for that
Gabriel OrozcoSolution Architect

Commented:
make mrproper will delete all your previous configuration. use it with care if you are not experienced compiling the kernel. I feel it should be used only when the normal procedure fails.

Author

Commented:
I have tried some of your solutions. Finally, tulip.c and pci-scan.c compiled properly using the compilation line at the botton of both files. However, when I call "insmod" it crashes like this :

[root@localhost netdrivers]# insmod pci-scan.o
pci-scan.o: unresolved symbol apm_register_callback_Rsmpf70b592f
pci-scan.o: unresolved symbol apm_unregister_callback_Rsmp99700428
[root@localhost netdrivers]# insmod tulip.o
tulip.o: unresolved symbol pci_drv_unregister
tulip.o: unresolved symbol pci_drv_register

I use an MSI MotherBoard.
Could that be the problem?
Do I need to install any driver to use PCI components???

I know this MotherBoard came with drivers for PCI and AGP 4x, and I had to install them when I installed W2K.

Could it be a problem with PCI???

Thanks a lot for all your help! Please don't give up on me. I am really determine to switch to Linux from W2K.
Gabriel OrozcoSolution Architect

Commented:
again... did you tried with modprobe?

there is no documentation telling you to move those drivers into an specific area before/after compiling?

Author

Commented:
YES, I tried "modprobe", and it output three lines saying that "insmod" failed for tulip.o

Does it make any difference what type of CPU I use.
I use an AMD Athlon 1600 1.4 MHz on a MSI MotherBoard.

I use the tulip.c and the pci-scan.c files that come in the installation floppy for my LNE100TX linksys network card. Could it be that the files were copied into the floppy from a Windows computer and the text format got all screwed up???
(They compiled fine though)

Thanks for your time.

Author

Commented:
jlevie : How do I let RedHat setup my network card???
It did not happen at installation time.

Could this has anything to do with PCI interface???????
Do I need drivers to be able to use PCI cards??????????

Author

Commented:
I got RedHat 8.0 and it installed so smooth.
Bye, bye Windows...   :)

I even got QuakeIII up and running...hehe

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial