At 05:24 PM 4/7/2001 +0000, Declan Moriarty wrote:
> I'm trying to network 2 linux pcs here and have run into a spot of
>bother. One seems fine. The other will ping 127.0.0.1 OK, but sees the network
>as unreachable.
What does it think its routing table should look like? The check with route
-n to
see the routing table, if there is a problem there, the initialization files
/etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-eth0 should be
checked to make sure they have the proper values.
>Anyhow, my problem:
>eth0 throws up an error and can't be initialised on bootup
What is that error?
>This is what insmod throws up.
> [root@workhorse /etc]# insmod ne2k-pci
>/lib/modules/2.2.14-15mdk/net/ne2k-pci.o: unresolved symbol ei_open
>/lib/modules/2.2.14-15mdk/net/ne2k-pci.o: unresolved symbol ethdev_init
>/lib/modules/2.2.14-15mdk/net/ne2k-pci.o: unresolved symbol ei_interrupt
>/lib/modules/2.2.14-15mdk/net/ne2k-pci.o: unresolved symbol NS8390_init
>/lib/modules/2.2.14-15mdk/net/ne2k-pci.o: unresolved symbol
>ei_close
>[root@workhorse /etc]#
Unresolved symbols are the harbinger of doom. Just kidding. They usually
represent modules that are compiled for a different kernel. Check the kernel
settings and remake and reinstall the modules at a minimum.
The installation is 7.0 (Air), kernel 2.2.14-15. Curiously, the graphical "What
>have we got here?" programs say it's a 586 cpu, correctly identify it as a k6,
>and give it the generation number 6 (=i686). Clear as mud, isn't it?
See the earlier thread on this list about i686 and i586 binaries for a "good"
discussion of this problem on k6's.
--
Matthew Micene
Systems Development Manager
Express Search Inc.
www.ExpressSearch.com
