I waited awhile to see if someone else might be able to help based on what
you said in your message. At this point, all I can do is ask you to clarify
your posting so that I might be able to suggest what's going on.

First, what does "ifconfig eth0" actually say? Not a paraphrase or summary.
Since ifconfig seems to find the actual card on the interface, I assume that
your problem s not with hardware or the NE2000 kernel module.

Second, when you say "I did a dmesg and saw that the net card was being
loaded but the tc/ip protocol was not bound to it," what are you seeing that
tells you that? On my systems, the eth0 dmesg lines don't include anything
about TCP/IP, but a much earlier line confirms that "TCP/IP for NET3.034" is
loaded.

Third, are you sure you configured networking correctly? Somewhere in your
rc* scripts should be an entry that configures eth0; what does it say? Are
there any boottime error messages from ifconfig in your logs?

At this point, my guess is that you don't have the ifconfig line set up
correctly in the boottime script (I forget which rc* script it is under RH).
But it's just a guess.

At 03:54 PM 5/18/99 +0200, Langa Kentane wrote:
>Hi.
>I have just installed RedHat 6.0 on my PII Celeron and I can't get tcp/ip
>bound to my network card.
>
>The system sees the ethernet card coz when I do 'ifconfig eth0' it info like
>the mac address but not the tcp/ip info.
>
>When I went to see which pci devices are loaded I can see the network card
>listed and when I check what devices are loaded on the system, I cannot see
>eth0.
>
>I did a dmesg and saw that the net card was being loaded but the tc/ip
>protocol was not bound to it... I don't know if it normally does show you
>the bindings info when it's loading.
>
>The card that I am using is a pci ethernet card. A ne2000 compatible realtek
>8029.

------------------------------------"Never tell me the odds!"---
Ray Olszewski                                        -- Han Solo
762 Garland Drive
Palo Alto, CA  94303-3603
650.328.4219 voice                              [EMAIL PROTECTED]        
----------------------------------------------------------------

Reply via email to