unresolved symbols and ethernet not working

GMAN · 07-03-2001, 01:25 PM

I have been trying to get my Realtec NIC working in Slackware 7.1, kernel 2.2.16 with no luck. When I depmod -a, I receive "unresolved symbol" messages on all the modules in /lib/modules/2.2.16. When I do a lsmod, the rt18139.o module is listed. When I tried a modprobe, it said it could not find the module. I believe the nic is trying to use autoconfigure for the interrupts. When I run a cat /proc/interrupts, it does not list one for eth0. dmesg shows it at 0x2400 for the i/o. Am I going to have to alias eth0? This is a PCI nic in a HP Pavilion XL753 with the Intel 810e chipset. any help is appreciated

crabboy · 07-03-2001, 05:51 PM

What happens when you do an insmod rt18139.o?

Building the .o directly into the kernel will solve your problem.

GMAN · 07-03-2001, 06:09 PM

I will be going home in a few minutes to hack again. I believe when I insmod, it says "cannot locate module rt13189.o"

I have tried building it into the kernel, and I still have no ethernet connection. Upon boot I get messages about "Network is unreachable" "SIOCSIFxxx:No such device" "SIOCSFFLAGS"
when I ifconfig it. I have been going through a lot of material over the last week, and still no resolution yet.

crabboy · 07-03-2001, 06:44 PM

Go to the directory under /lib/modules where the .o file is and try the insmod.

You may have to pass a parameter to the kernel about your card. I must do so for my 3c509's and scsi adapter.

append = "ether=11,0x300,4,0x3c509,eth0 ether=10,0x280,4,0x3c509,eth1 aha152x=0x340,12,7,1,1,0"

What you can pass with the ether= option depends on your cards driver. To figure out what I could pass I looked at the driver source code.

Let us know

Gary

crabboy · 07-03-2001, 09:37 PM

I saw that there are two different drivers for this card. Have you tried both of them? There is the rtl8139.c and a 8139too.c. There seems to be a bit of documentation for the too driver in /linux/Documentation/networking. Have you taken a look at that? There driver source is also documented a bit.

If you are desprate enough there is debug info in the source that you can compile in to enable.

What do you see in your dmesg output for the card. You should see the card init long before you see the "Network is Unreachable" error. That error is generated by the rc/init scripts that are started long after the hardware has been initialized.

Gary

jharris · 07-04-2001, 04:23 AM

So you've rebuilt your kernel to include the modules yeah? Did you remember to do

Code:

make modules
rm -rf /lib/modules/2.2.16
make modules_install

After you did your make bzlilo?? I've got these cards in both my linux boxes, one on 2.2.18/2.2.19 and the other on 2.4.5 with no problems so the support seems OK.

HTH

Jamie...

DMR · 07-04-2001, 01:22 PM

"SIOCSIFxxx:No such device" "SIOCSFFLAGS"

The above error, combined with some of your other symptoms, often indicates a BIOS Plug-N-Play configuration conflict. If posssible, try turning off P-N-P support in your BIOS.

GMAN · 07-05-2001, 09:20 AM

Thank you all for your replies. I may need a couple more, as I think I am close. Well...here is my update. Since this was a new install, I re-installed Linux. Either I was compiling wrong or there was some major corruption. All of my errors with "Unresolved symbols are gone now. I can depmod and modprobe the modules fine. Still I had no luck with the Generic NIC and RealTek module. dmesg shows it as IRQ 0 (which I believe is an auto IRQ)
When performing a cat /proc/interrupts, I cannot see any conflicts if I try and append it an IRQ of 10 and I/O of 0x2400. lspci lists it as a Accton Tech Corp, SMC2-1211TX rev. EZcard 10/100 card. and shows the RealTek module below it. So, I decided to throw in a LinkSys 10/100 NIC I had and try it with the tulip.o module. Well, compiling went well, depmod and modprobe. lsmod shows it just
fine (it does say "unused by it, as did the realtek module)
It tried appending it an IRQ of 10 and I/O of 0x240, but now luck, no change. I pulled the original card out just to see exactly what it was. It is a "Generic" 10/100 NIC with a MPX chip. I checked my manual, and MPX refers to Accton and Accton MPX. It shows as supported with the NE2000 driver. Talk about OEM??? "Will the real manufacturer please step forward!!" Just a little humor! Obviously it may work with more than one driver or mod.
Finally, after I put the Linksys card it, after shutdown I got a different message (this is a good thing, I got a change!!!) Right after POST, it says there is a "resource conflict with an Ethernet controller in PCI slot # 3. I played around in the system bios for a bit, but no luck. I will check more closely tonight for "plug and play" Any other thoughts?????

jharris · 07-05-2001, 09:48 AM

I think I might have been being stupid here. What RealTek chip is on that card?? If its a 8129/8139 then you need the RealTek module, if its a 8139 then you can use the alternative and newer RealTek module - rtl8139too.o, but if its a 8029 then its the good old ne2k-pci module you want.

Cheers!

Jamie...

GMAN · 07-05-2001, 12:48 PM

Hey Jamie. Nice website! I will have to look at the NIC when I get home tonight, but I remember the MPX chip on it with a long string of numbers. Using lspci, it lists it as an Accton Tech Corp.
SMC2-1211TX EZCard 10/100 rev.10 with the MPX chip on it.
But also remember I have the LinkSys NIC in it right now, as my previous post indicates. I believe it has something to do with possibly two things. # 1, a resourse conflict and or the PCI bus???

jharris · 07-05-2001, 01:20 PM

Quote:

Originally posted by GMAN
Hey Jamie. Nice website!

You must have been looking at the wrong URL mate!

Only the stuff in the resources is interesting on my server and thats not public access... Need more upstream bandwidth, my cable modems just ain't hacking it when I'm at Uni and getting stuff from home

(having said that no matter how much bandwidth you have its never enough)

cheers!

Jamie...