Re: Newbie installation problem

Re: Newbie installation problem

[Amin]

E.N.:

Since you're using Red Hat, try using Red Hat's network configuration
wizard:

# neat &

This is a nice graphical interface to get your NIC up and running.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Newbie installation problem

[Enrique Nieves]

I'm a newbie with Linux and I'm trying to install Red Hat 7.3 in my AMD K6
box (128 mb RAM, 233 mhz, 6 gb hard drive) to be the sole OS for that box.
When the installation program tries to detect the network card (eth0) it
gives me a FAILED message.

I'm trying to have a home network using a LinkSys router with a Windows XP
box and this AMD PC connected peer to peer and another ethernet connection
to use with my laptop.

I'm trying to decide if the problem is in the NIC card or in my attempt to
install Red Hat.  Is it very difficult to connect a Linux box and an XP box
peer to peer?

Thanks,

EN


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Ray Olszewski]

At 08:07 PM 8/2/02 -0400, Enrique Nieves wrote:
>I'm a newbie with Linux and I'm trying to install Red Hat 7.3 in my AMD K6
>box (128 mb RAM, 233 mhz, 6 gb hard drive) to be the sole OS for that box.
>When the installation program tries to detect the network card (eth0) it
>gives me a FAILED message.

Please be a bit clearer about the details here.

1. What NIC do you have in the system?  Make and model.
2. At what stage does RH fail? (Technically, eth0 is an interface, not a 
card; it does not get created until -AFTER- the card has been detected and 
an appropriate kernel module loaded.)
3. Quote the EXACT error message (not just the word "FAILED").
4. Has the NIC worked previously, say with some version of Windows? Or is 
this a new NIC (from the hardware details, I'd guess it is not a completely 
new PC)?

>I'm trying to have a home network using a LinkSys router with a Windows XP
>box and this AMD PC connected peer to peer and another ethernet connection
>to use with my laptop.

What do you mean by "peer to peer"? In this context, the term usually 
describes two hosts that are connected directly via Ethernet, without a hub 
in between ... but your mention of the Linksys router causes me to doubt 
that that is what you mean. Do you just mean that the two hosts are on the 
same LAN?

>I'm trying to decide if the problem is in the NIC card or in my attempt to
>install Red Hat.  Is it very difficult to connect a Linux box and an XP box
>peer to peer?

No matter what you might mean by "peer to peer", the answer is no, at least 
from the Linux side. (Also from the XP side, probably, as I doubt it is 
very different from WIn98 or Win2k). But if RH is having trouble either 
detecting or initializing your NIC, you are way far away from worrying 
about anything that the host is connected to (other host, hub, whatever).

The details I asked for above will help us give you advice. The problem 
*may* be a NIC that the RH installer cannot auto detect, requiring you to 
configure it manually (which someone else will need to help with the 
details of, since I haven't installed RH in years).


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Enrique Nieves]

Ray,

Thanks for your query.  I've placed a response after each of your questions
below.
Another possibility may be the cable itself; however, the router lights
indicate the
cable is connected.

EN

----- Original Message -----
From: "Ray Olszewski" <ray@comarre.com>
To: "Enrique Nieves" <spanfax@charter.net>; <linux-newbie@vger.kernel.org>
Sent: Friday, August 02, 2002 9:27 PM
Subject: Re: Newbie installation problem


> At 08:07 PM 8/2/02 -0400, Enrique Nieves wrote:
> >I'm a newbie with Linux and I'm trying to install Red Hat 7.3 in my AMD
K6
> >box (128 mb RAM, 233 mhz, 6 gb hard drive) to be the sole OS for that
box.
> >When the installation program tries to detect the network card (eth0) it
> >gives me a FAILED message.
>
> Please be a bit clearer about the details here.
>
> 1. What NIC do you have in the system?  Make and model.

Netgear, 32 bit, PCI Adapter, 10/100 Mbps Fast Ethernet FA311

> 2. At what stage does RH fail? (Technically, eth0 is an interface, not a
> card; it does not get created until -AFTER- the card has been detected and
> an appropriate kernel module loaded.)

When booting up and detecting hardware it indicated that it can't detect IP
settings

> 3. Quote the EXACT error message (not just the word "FAILED").

After the error message FAILED it indicates that IP settings can't be
detected

> 4. Has the NIC worked previously, say with some version of Windows? Or is
> this a new NIC (from the hardware details, I'd guess it is not a
completely
> new PC)?
>

It's a new NIC


> >I'm trying to have a home network using a LinkSys router with a Windows
XP
> >box and this AMD PC connected peer to peer and another ethernet
connection
> >to use with my laptop.
>
> What do you mean by "peer to peer"? In this context, the term usually
> describes two hosts that are connected directly via Ethernet, without a
hub
> in between ... but your mention of the Linksys router causes me to doubt
> that that is what you mean. Do you just mean that the two hosts are on the
> same LAN?

As Riley Williams indicted, I'm trying to set up a home network with three
systems on it,
my Windows XP box, the AMD I'm trying to set up under Red Hat Linux
and  my laptop, and I'm not sure if I'm using a 10baseT or 100baseTX
ethernet with my
LinkSys router, which is acting as a routing hub for the three of them.

>
> >I'm trying to decide if the problem is in the NIC card or in my attempt
to
> >install Red Hat.  Is it very difficult to connect a Linux box and an XP
box
> >peer to peer?
>
> No matter what you might mean by "peer to peer", the answer is no, at
least
> from the Linux side. (Also from the XP side, probably, as I doubt it is
> very different from WIn98 or Win2k). But if RH is having trouble either
> detecting or initializing your NIC, you are way far away from worrying
> about anything that the host is connected to (other host, hub, whatever).
>
> The details I asked for above will help us give you advice. The problem
> *may* be a NIC that the RH installer cannot auto detect, requiring you to
> configure it manually (which someone else will need to help with the
> details of, since I haven't installed RH in years).
>
>
> --
> -------------------------------------------"Never tell me the
odds!"--------
> Ray Olszewski -- Han Solo
> Palo Alto, California, USA   ray@comarre.com
> --------------------------------------------------------------------------
-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Riley Williams]

Hi Enrique.

I hope you don't mind my responding, but I'm sure Ray will ask the same
questions...

> Thanks for your query.  I've placed a response after each of your
> questions below. Another possibility may be the cable itself;
> however, the router lights indicate the cable is connected.

The router lights only indicate that the PC -> Router direction is
working. To rule out the cable, you need to turn it round and see if the
router lights still work with it plugged in the other way round.

>>> I'm a newbie with Linux and I'm trying to install Red Hat 7.3 in my
>>> AMD K6 box (128 mb RAM, 233 mhz, 6 gb hard drive) to be the sole OS
>>> for that box. When the installation program tries to detect the
>>> network card (eth0) it gives me a FAILED message.

>> Please be a bit clearer about the details here.
>>
>> 1. What NIC do you have in the system?  Make and model.

> Netgear, 32 bit, PCI Adapter, 10/100 Mbps Fast Ethernet FA311

Does this system finish booting after reporting the failure, or does it
just lock up at that point?

If it finishes booting, can you log in as root and then attach the
output of the `lspci -v` command?

>> 2. At what stage does RH fail? (Technically, eth0 is an interface,
>>    not a card; it does not get created until -AFTER- the card has
>>    been detected and an appropriate kernel module loaded.)

> When booting up and detecting hardware it indicated that it can't
> detect IP settings

>> 3. Quote the EXACT error message (not just the word "FAILED").

> After the error message FAILED it indicates that IP settings can't
> be detected

Ah - now, that isn't a hardware failure but a case of no DHCP server on
your network and you haven't statically allocated IP settings to the
interface. You need to allocate an IP address to each machine on your
network, so let's do that first.

IP addresses in the 192.168.X.Y format are reserved for use on private
networks, so I am going to assume you are using such a range of
addresses. You thus need to make two decisions:

 1. You need to select a number for your network as a whole. This
    number is in the range 1 to 254 and must be the same for all
    machines on your network, so choose your favourite number in
    this range. This number forms the value X in the IP address.

 2. You need to select a number for each machine on your network.
    This is also in the range 1 to 254, but needs to be DIFFERENT
    on each machine. There is a convention that the number 254 is
    allocated to the system on your network that acts as a gateway
    to other networks, but you do not need to follow this if you
    prefer not to. This number forms the value Y in the IP address
    for each machine, and there will be three different values,
    which I will refer to as Y1, Y2 and Y3.

Having selected the values X and Y for each machine, I suggest you jot
them down in a table similar to the following:

	IP Address	System Description	Sample IP Address
	~~~~~~~~~~	~~~~~~~~~~~~~~~~~~	~~~~~~~~~~~~~~~~~
	192.168.X.Y1	AMD K6 running Linux	192.168.99.254
	192.168.X.Y2	Windows XP Desktop	192.168.99.1
	192.168.X.Y3	Laptop			192.168.99.2

When the AMD finishes booting Linux, log in as root, then run the
`netconfig` command and specify that you would like to set up
networking. On the next screen, make sure that the "Use dynamic IP
configuration" checkbox is NOT selected, then enter the following values
in the fields underneath:

	IP address:		192.168.X.Y1
	Netmask:		255.255.255.0
	Default gateway:	(blank)
	Primary nameserver:	127.0.0.1

This will configure networking on that machine.

>> 4. Has the NIC worked previously, say with some version of Windows?
>>    Or is this a new NIC (from the hardware details, I'd guess it is
>>    not a completely new PC)?

> It's a new NIC

>>> I'm trying to have a home network using a LinkSys router with a
>>> Windows XP box and this AMD PC connected peer to peer and another
>>> ethernet connection to use with my laptop.

>> What do you mean by "peer to peer"? In this context, the term
>> usually describes two hosts that are connected directly via
>> Ethernet, without a hub in between ... but your mention of the
>> Linksys router causes me to doubt that that is what you mean.
>> Do you just mean that the two hosts are on the same LAN?

> As Riley Williams indicted, I'm trying to set up a home network with
> three systems on it, my Windows XP box, the AMD I'm trying to set up
> under Red Hat Linux and my laptop, and I'm not sure if I'm using a
> 10baseT or 100baseTX ethernet with my LinkSys router, which is
> acting as a routing hub for the three of them.

Based on the information provided earlier, if the router can handle 100
speed, then you are attempting to use 100baseTX ethernet, if not, you
are attempting to use 10baseT ethernet.

One final question: Am I right in assuming that you are trying to set it
up with the AMD under Linux as the system that connects to the Internet,
and both the WinXP machine and the laptop piggy-backing onto that
connection?

The reason I ask this is that on rereading your comments, I note your
repeated reference to "LinkSys router" and I'm wondering if that's an
ADSL router that forms your Internet connnection. If it is, then the
advice to be given is rather different to the above, and the above
advice should be ignored.

In this event, please run the `netconfig` command but ensure that the
"Use dynamic IP configuration" box IS checked. In this case, the values
of the remaining fields are irrelevant and should be ignored. You also
need to configure your router to enable the DHCP server and the NAT
facilities therein, and it will then configure the IP addresses,etc, on
all the systems on your network.

Best wishes from Riley.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Enrique Nieves]

> Based on the information provided earlier, if the router can handle 100
> speed, then you are attempting to use 100baseTX ethernet, if not, you
> are attempting to use 10baseT ethernet.
>
> One final question: Am I right in assuming that you are trying to set it
> up with the AMD under Linux as the system that connects to the Internet,
> and both the WinXP machine and the laptop piggy-backing onto that
> connection?

The XP is the system that is connected to the internet, and I'm trying to
piggy back to that connection the AMD  box and the XP laptop.

>
> The reason I ask this is that on rereading your comments, I note your
> repeated reference to "LinkSys router" and I'm wondering if that's an
> ADSL router that forms your Internet connnection. If it is, then the
> advice to be given is rather different to the above, and the above
> advice should be ignored.

I have a Linksys Ethernet 10/100 Cable/DSL Router (BEFSR41 ver.2) with four
ports connected to a Shark Fin cable modem.
>
> In this event, please run the `netconfig` command but ensure that the
> "Use dynamic IP configuration" box IS checked. In this case, the values
> of the remaining fields are irrelevant and should be ignored. You also
> need to configure your router to enable the DHCP server and the NAT
> facilities therein, and it will then configure the IP addresses,etc, on
> all the systems on your network.
>
> Best wishes from Riley.

Thanks for your advice.

Enrique



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Ray Olszewski]

At 12:55 AM 8/4/02 -0400, Enrique Nieves wrote:
>Ray,
>
>Thanks for your query.  I've placed a response after each of your questions
>below.
>Another possibility may be the cable itself; however, the router lights
>indicate the
>cable is connected.

No no no. If RH cannot detect the NIC, then the problem is inside the 
computer. Things like cabling come way later.  (But if the problem is NOT 
NIC detection ... see below ... then the problem could be in the cabling, 
evn if the lights indicate a connection. Do you ever see actual traffic 
over the link?)

[...]
> > 1. What NIC do you have in the system?  Make and model.
>
>Netgear, 32 bit, PCI Adapter, 10/100 Mbps Fast Ethernet FA311

It is *possible* that RH simply does not autodetect this one, perhaps 
because does not include its module in the ones it automatically tries. I 
don't use this NIC itself, but I seem to recall that it uses one fo the 
less common modules (natsemi.o maybe? does anyone else recall?). You may 
need to add it manually (however RH provides for that).


> > 2. At what stage does RH fail? (Technically, eth0 is an interface, not a
> > card; it does not get created until -AFTER- the card has been detected and
> > an appropriate kernel module loaded.)
>
>When booting up and detecting hardware it indicated that it can't detect IP
>settings

What do you mean by "IP settings"? This phrase usually means the systems's 
own IP address and routing information (network, gateway, possibly DNS 
servers). It would not be looked for at the hardware detection stage. So 
either you have the place where the failure occurs wrong, or you mean 
something different from what I use this phrase to mean.

> > 3. Quote the EXACT error message (not just the word "FAILED").
>
>After the error message FAILED it indicates that IP settings can't be
>detected

Once again I'd ask for the exact error message, not your interpretation of 
what "it indicates". The paraphrase you provide reads like the NIC itself 
it detected but the installer can't get an IP address and such. If that is 
so, then please tell us what you are telling the system about how it should 
get an IP address and related information (netmask, gateway, maybe DNS 
servers ... whatever the installer asks about).

After I wrote this, I saw that Riley replied with a lot of good advice ... 
only it was based on guesses about what some unclear parts of what you 
wrote mean. If he got it right, then that should take care of your 
problems. If he guessed wrong, you need to describe the location and nature 
of the error more clearly than you have so far.


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Enrique Nieves]

> No no no. If RH cannot detect the NIC, then the problem is inside the
> computer. Things like cabling come way later.  (But if the problem is NOT
> NIC detection ... see below ... then the problem could be in the cabling,
> evn if the lights indicate a connection. Do you ever see actual traffic
> over the link?)


I don't see any traffic.


>
> [...]
> > > 1. What NIC do you have in the system?  Make and model.
> >
> >Netgear, 32 bit, PCI Adapter, 10/100 Mbps Fast Ethernet FA311
>
> It is *possible* that RH simply does not autodetect this one, perhaps
> because does not include its module in the ones it automatically tries. I
> don't use this NIC itself, but I seem to recall that it uses one fo the
> less common modules (natsemi.o maybe? does anyone else recall?). You may
> need to add it manually (however RH provides for that).


I'll try adding the driver that came with the Netgear NIC manually.


>
> > > 2. At what stage does RH fail? (Technically, eth0 is an interface, not
a
> > > card; it does not get created until -AFTER- the card has been detected
and
> > > an appropriate kernel module loaded.)
> >
> >When booting up and detecting hardware it indicated that it can't detect
IP
> >settings
>
> What do you mean by "IP settings"? This phrase usually means the systems's
> own IP address and routing information (network, gateway, possibly DNS
> servers). It would not be looked for at the hardware detection stage. So
> either you have the place where the failure occurs wrong, or you mean
> something different from what I use this phrase to mean.
>
> > > 3. Quote the EXACT error message (not just the word "FAILED").
> >
> >After the error message FAILED it indicates that IP settings can't be
> >detected
>
> Once again I'd ask for the exact error message, not your interpretation of
> what "it indicates". The paraphrase you provide reads like the NIC itself
> it detected but the installer can't get an IP address and such. If that is
> so, then please tell us what you are telling the system about how it
should
> get an IP address and related information (netmask, gateway, maybe DNS
> servers ... whatever the installer asks about).



The exact message is:

"Checking for New Hardware
                .
                .
                .
Bringing up interface Eth0:
    Determining IP information for Eth0 . . . failed

[FAILED]"


This occurs when the RH 7.3 does the initial boot up.




> After I wrote this, I saw that Riley replied with a lot of good advice ...
> only it was based on guesses about what some unclear parts of what you
> wrote mean. If he got it right, then that should take care of your
> problems. If he guessed wrong, you need to describe the location and
nature
> of the error more clearly than you have so far.

Thanks again for you patience.

Enrique



>
>
> --
> -------------------------------------------"Never tell me the
odds!"--------
> Ray Olszewski -- Han Solo
> Palo Alto, California, USA   ray@comarre.com
> --------------------------------------------------------------------------
-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Ray Olszewski]

Oh. From what you sent this time, it does look like the NIC is being 
detected, but RH cannot assign an IP address to the interface. I'm not 
entirely sure of this, though, based on the details of what you quote, namely:

>"Checking for New Hardware
>                 .
>                 .
>                 .
>Bringing up interface Eth0:
>     Determining IP information for Eth0 . . . failed
>
>[FAILED]"
>
>
>This occurs when the RH 7.3 does the initial boot up.

Several things confuse me here.

First, just a detail -- does it really say "Eth0" eather than "eth0"? If 
so, then RH is introducing unnecessary confusion into the process (since 
interface names are normally all lower case). If not, then you are not 
quoting exactly.

Second, what *immediately* precedes the failure message? Are you *sure* the 
system is still in the New Hardware phase?

Third, I had previously thought that this message was coming from a RH 
install. Now it sounds like part of the boot/init process of an installed 
RH 7.3. Could you clarify?

Fourth, what happens next? If we are talking about an installed RH, does it 
complete initialization, then give you the login: prompt (or the X 
equivalent, depending on your setup)? If it does, may we see at this point 
the output of:

         ifconfig -a
         netstat -nr
         lsmod
         lspci

Last, how do you *want* this system to get its IP address?

         Do you plan to assign a static address by hand? If so, you 
(probably) specify this by editing the file /etc/network/interfaces .

         Use a DHCP server? If so, then where on the LAN are you running 
one? The Linksys? The XP system? Do you see network traffic (in the form of 
appropriate blinking lights on the NIC and the hub) just before you get the 
failure message you quote above (if you don't, then the system isn't 
managing to connect to the LAN to look for a DHCP server).

         Those are the only real alternatives (technically there are some 
others, but no one uses them in small home setups).

At 01:08 PM 8/4/02 -0400, Enrique Nieves wrote:
[details deleted]


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Enrique Nieves]

Hello Ray,

> Several things confuse me here.
>
> First, just a detail -- does it really say "Eth0" eather than "eth0"? If
> so, then RH is introducing unnecessary confusion into the process (since
> interface names are normally all lower case). If not, then you are not
> quoting exactly.

sorry, it says eth0


> Second, what *immediately* precedes the failure message? Are you *sure*
the
> system is still in the New Hardware phase?


actually, what immediately precedes the message is "bringing up loopback
interface       [OK]"


>
> Third, I had previously thought that this message was coming from a RH
> install. Now it sounds like part of the boot/init process of an installed
> RH 7.3. Could you clarify?

It is in the first boot/init after installation.

>
> Fourth, what happens next? If we are talking about an installed RH, does
it
> complete initialization, then give you the login: prompt (or the X
> equivalent, depending on your setup)? If it does, may we see at this point
> the output of:
>
>          ifconfig -a
>          netstat -nr
>          lsmod
>          lspci


This is the output I get for:
ifconfig -a
netstat -nr
lsmod
I will send lspci output next.

[root@localhost  root] # ifconfig -a
eth0    Link encap:Ethernet    HWaddr    00:40:F4:70:3E:F3

           BROADCAST MULTICAST MTU:1500 Metric:1
me:0
            TX packets:0  errors:0  dropped:0  overruns:0  car
rier:0
            collisions:0  txqueuelen:100
            RX bytes:0 (0.0 b)    TX bytes:0    (0:0 b)
            Interrupt:10  Base address:0x3000

lo        Link encap: Local Loopback
           inet addr:127.0.0.1    Mask:255.0.0.0
           UP LOOPBACK RUNNING MTU:16436    Metric:1
            RX     packets:8    errors:0  dropped:0   overruns:0    fra
            TX     packets:8    errors:0  dropped:0   overruns:0    car
0
            collisions:0    txqueuelen:0
            RX bytes:560    (560.0 b)        TX bytes:560    (560.0 b)

[root@localhost  root] # netstat -nr
Kernel IP routing table
Destination    Gateway    Genmask    Flags MSS    Window    irtt Iface
127.0.0.0       0.0.0.0      255.0.0.0   U      40        0               0
lo

[root@localhost  root] # lsmod
Module            Size            Used    by            Not    tainted
es1371            29728         0        (autoclean)
ac97_codec    11872          0        (autoclean)        [es1371]
gameport            3392         0        (autoclean)        [es1371]



> Last, how do you *want* this system to get its IP address?
>
>          Do you plan to assign a static address by hand? If so, you
> (probably) specify this by editing the file /etc/network/interfaces .
>
>          Use a DHCP server?


Yes, I plan to use DHCP


If so, then where on the LAN are you running
> one? The Linksys? The XP system?


The Linksys

Do you see network traffic (in the form of
> appropriate blinking lights on the NIC and the hub) just before you get
the
> failure message you quote above (if you don't, then the system isn't
> managing to connect to the LAN to look for a DHCP server).


No, I'm not seeing network traffic



>
>          Those are the only real alternatives (technically there are some
> others, but no one uses them in small home setups).


Thanks again for your time and patience.

Enrique





-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Ray Olszewski]

OK. This is all quite different from how I had interpreted your earlier 
messages. I was proceeding in the belief that during installation, the RH 
installer was unable to find your NIC. From the additional details you 
posted, your problem is simply with address assignment.  Riley's earlier 
advice is what you should be trying, supplemented by a few comments I offer 
below.

At 01:32 AM 8/5/02 -0400, Enrique Nieves wrote:
>[...]
>This is the output I get for:
>ifconfig -a
>netstat -nr
>lsmod
>I will send lspci output next.

Don't bother. Wer're past this part.

>[root@localhost  root] # ifconfig -a
>eth0    Link encap:Ethernet    HWaddr    00:40:F4:70:3E:F3
>
>            BROADCAST MULTICAST MTU:1500 Metric:1
>me:0
>             TX packets:0  errors:0  dropped:0  overruns:0  car
>rier:0
>             collisions:0  txqueuelen:100
>             RX bytes:0 (0.0 b)    TX bytes:0    (0:0 b)
>             Interrupt:10  Base address:0x3000

OK. This tells us that your NIC *is* being detected. But RH cannot 
initialize it (hence it has no IP address, just a MAC (hardware) address).
[...]
>[root@localhost  root] # lsmod
>Module            Size            Used    by            Not    tainted
>es1371            29728         0        (autoclean)
>ac97_codec    11872          0        (autoclean)        [es1371]
>gameport            3392         0        (autoclean)        [es1371]

Not sure how the NIC is getting detected. Maybe RH compiles support for 
some NICs right into its default kernel?

> > Last, how do you *want* this system to get its IP address?
> >
> >          Do you plan to assign a static address by hand? If so, you
> > (probably) specify this by editing the file /etc/network/interfaces .
> >
> >          Use a DHCP server?
>
>
>Yes, I plan to use DHCP
>
>
>If so, then where on the LAN are you running
> > one? The Linksys? The XP system?
>
>
>The Linksys

OK. As I said earlier, I'm not a Red Hat user (I use Debian), so I can't 
tell you the Red-Hat-specific tricks, only the basic Linux-level ways to 
troubleshoot this. Perhaps a Red Hat user will supplement this. But for now ...

1. Does the RH host know that it is supposed to get a DHCP lease? The place 
to look is in /etc/network/interfaces, to see what type of address 
assignment is specified for eth0. You are looking for a block like this:

         auto eth0
         iface eth0 inet dhcp

2. Is the DHCP server on the Linksys router working? (Is the XP host, for 
example, getting a lease from it?) I've never used a Linksys, but I have 
used the similar Netgear router, so I think this should be easy to set up 
from the Linksys config menu.

3. Is the physical connection between the Linux host and the Linksys good? 
Does the same cable work between the XP host and the *same* port on the 
Linksys? (You should be using a normal Ethernet cable connected to a normal 
port on the Linksys ... not either a crossover cable or an uplink port.)

4. If you give the RH host a static IP address, does it now initialize 
properly (check this with "ifconfig -a" as before) and connect to (test 
with "ping") the Linksys router? You do this with a block like the 
following in /etc/network/interfaces:

auto eth0
iface eth0 inet static
         address 192.168.1.12
         netmask 255.255.255.0
         network 192.168.1.0
         broadcast 192.168.1.255
         gateway 192.168.1.1

(This example assumes that the Linksys uses network 192.168.1.0/24 and, for 
its own LAN interface, IP address 192.168.1.1; the Linksys docs will either 
confirm this or give you the right values to use.) After you replace the 
exsting entry with a block like this one, you either reboot or restart 
networking (something like "/etc/init.d/networking restart" -- Red Hat may 
do it a bit differently, though).

5. I've assumed that the NIC has only a UTP (Cat 5) connection ... don't 
recall ever seeing a FA111 that didn't ... but if it has another connection 
(such as a BNC connection for thinnet coax) ... is the NIC configured to 
use the UTP port? (this one is a long shot.)


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Riley Williams]

Hi Enrique.

>> First, just a detail -- does it really say "Eth0" eather than
>> "eth0"? If so, then RH is introducing unnecessary confusion into the
>> process (since interface names are normally all lower case). If not,
>> then you are not quoting exactly.

> sorry, it says eth0

>> Second, what *immediately* precedes the failure message? Are you
>> *sure* the system is still in the New Hardware phase?

> actually, what immediately precedes the message is "bringing up
> loopback interface [OK]"

>> Third, I had previously thought that this message was coming from a
>> RH install. Now it sounds like part of the boot/init process of an
>> installed RH 7.3. Could you clarify?

> It is in the first boot/init after installation.

>> Fourth, what happens next? If we are talking about an installed RH,
>> does it complete initialization, then give you the login: prompt (or
>> the X equivalent, depending on your setup)? If it does, may we see
>> at this point the output of:
>>
>>          ifconfig -a
>>          netstat -nr
>>          lsmod
>>          lspci

> This is the output I get for:
>
>	ifconfig -a
>	netstat -nr
>	lsmod

The output was badly mangled. Can I suggest you do...

	ifconfig -a > /tmp/ifconfig.log
	netstat -nr > /tmp/netstat.log

...and then just attach /tmp/ifconfig.log and /tmp/netstat.log to your
email for reference if full output is needed.

However, by reading through the mangled logs, I was able to work out
that the interface is being brought up correctly, but the DHCP request
is failing to locate a DHCP server on the network.

>> Last, how do you *want* this system to get its IP address?
>>
>> Do you plan to assign a static address by hand? If so, you
>> (probably) specify this by editing the file /etc/network/interfaces.
>>
>> Use a DHCP server?

> Yes, I plan to use DHCP

>> If so, then where on the LAN are you running one?

> The Linksys

At the moment, the DHCP server in the LinkSys is disabled and you will
need to go in and enable it to solve this problem. Basically, your Linux
setup is almost certainly fine.

Best wishes from Riley.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[pa3gcu]

On Sunday 04 August 2002 04:55, Enrique Nieves wrote:
> Ray,
>
> Thanks for your query.  I've placed a response after each of your questions
> below.
> Another possibility may be the cable itself; however, the router lights
> indicate the
> cable is connected.
>
> EN

A few questions from me;

What does the following commands produce, PLEASE cut and paste "all" of the 
text, like Ray said, not simply what you think is relavant.

/sbin/lspci | grep -i ethernet 
/sbin/ifconfig -a

I susspect Riley is correct in saying that the NIC is trying to obtain a IP# 
via DHCP.

The LinkSys router you mentioned i belive has DHCP turned off by default.

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Newbie installation problem

[Riley Williams]

Hi Enrique.

> I'm a newbie with Linux and I'm trying to install Red Hat 7.3 in my
> AMD K6 box (128 mb RAM, 233 mhz, 6 gb hard drive) to be the sole OS
> for that box.

There should be no problems with that setup - I recently installed Red
Hat 7.3 on an AMD K6 box with a 266 MHz cpu but otherwise identical to
your specification and had no problems at all.

> When the installation program tries to detect the network card
> (eth0) it gives me a FAILED message.

What precicely is the FAILED message? There are many different ones that
can come up, and the precice message is needed to determine the problem.

Also, what is the network card it's trying to detect?

> I'm trying to have a home network using a LinkSys router with a
> Windows XP box and this AMD PC connected peer to peer and another
> ethernet connection to use with my laptop.

I presume what you really mean is that you are trying to set up a home
network with three systems on it, these being your Windows XP box, the
AMD you're trying to set up under Red Hat Linux and your laptop, and you
are using either 10baseT or 100baseTX ethernet with the LinkSys router
acting as a routing hub for the three of them.

> I'm trying to decide if the problem is in the NIC card or in my
> attempt to install Red Hat.

If you're letting Red Hat Linux use its normal installation package,
then you should be unable to cause problems. However, it is always
possible that there is a problem with the NIC itself.

> Is it very difficult to connect a Linux box and an XP box peer to
> peer?

If they both detect the network interface correctly, then both Linux and
XP automatically set up 99% of what is required to produce a network
setup like the description above. All you need to do is to allocate an
IP address for each system, and you can set up the Linux system to do
that for the other systems automatically using DHCP software.

Best wishes from Riley.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs