From msfrank@u.washington.edu Sun Jan 14 18:19:37 2001
Received: from jason03.u.washington.edu (jason03.u.washington.edu [140.142.8.11])
	by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id SAA61636
	for <linux@lists.u.washington.edu>; Sun, 14 Jan 2001 18:19:36 -0800
Received: from dante38.u.washington.edu (msfrank@dante38.u.washington.edu [140.142.15.198])
	by jason03.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id SAA39138
	for <linux@u.washington.edu>; Sun, 14 Jan 2001 18:19:35 -0800
Received: from localhost (msfrank@localhost)
	by dante38.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id SAA07576
	for <linux@u.washington.edu>; Sun, 14 Jan 2001 18:19:34 -0800
Date: Sun, 14 Jan 2001 18:19:34 -0800 (PST)
From: michael scott frank <msfrank@u.washington.edu>
To: UW Linux Group <linux@u.washington.edu>
Subject: Re: Questions about the eth0.
In-Reply-To: <000001c07e82$fcbda870$4200ed18@outland>
Message-ID: <Pine.A41.4.21.0101141802270.104408-100000@dante38.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

  You are sure that the correct kernel module is being inserted at boot
time?  This seems to be the problem 99% of the time when a question
like this is asked.  Past that, its difficult to determine the problem 
without knowing the EXACT error you are getting, and when it happens.
You said "eth0 will not initialize", does that mean when you try to
'insmod <whatever_your_eth_module.o> it returns some error, or does that
mean you have inserted the kernel module successfully, but 'ifconfig'
or 'route' gives an error?  If it is  the latter, then most likely part of
the network information you entered is incorrect (for example 'route' will
rightly complain if the specified gateway is outside of your subnet).

  If you are using linuxconf, and you don't know what i'm talking about 
with ifconfig and route, they are the command line equivalents of the
linuxconf network setup.  It might be good to try and bring up
networking completely by hand, so you can isolate the exact problem.  This
consists of:

  insmod <NIC_module.o>
  ifconfig eth0 <your_ip_address> netmask <your_netmask> up
  route add default gw <your_gateway_address> dev eth0

Try this, and post where exactly you get an error.

Michael


-------------------------  .~.
Michael Frank              /v\
msfrank@u.washington.edu  // \\
------------------------ /(   )\
                          ^`~'^

On Sun, 14 Jan 2001, Mark Weisman wrote:

> Hello list, and Mike:
> 
> I have recently installed another installation of Red Hat Linux v6.2 and
> during this installation, I added a new motherboard and system. During this
> installation I found that the eth0 connection will not initialize regardless
> how I set it up. The "netconf" shows the card properly, identifying the IO
> address and IRQ properly. However, I can't seem to get the eth0(or anything
> else) except for lo. I've ensured that the card is not in "plug and play"
> mode, and checked to ensure that the motherboard was not allocating the
> resources. I've tried changing some of the configuration, however, to no
> effect. I'm needing to try and use this card due to it's MAC address being
> registered already. The card worked prior to this installation. Any help
> would be greatly appreciated.
> 
> Thanks,
> Mark
> 
> 

.