From: "Anna G. Zapata" <azapata@du.edu>
To: Ray Olszewski <ray@comarre.com>, linux-newbie@vger.kernel.org
Subject: RE: activating eth0
Date: Wed, 19 Nov 2003 14:14:11 -0700 [thread overview]
Message-ID: <HBEJLOFMLEPBMAAEFNFDIECBCDAA.azapata@du.edu> (raw)
In-Reply-To: <5.1.0.14.1.20031119121638.01f72bb0@celine>
Nevermind, it is now working again. I didn't do anything, but it seems fine now. One minute it was working, the next
it wasn't working, and now it's back up again. Sorry for the bother.
-----Original Message-----
From: linux-newbie-owner@vger.kernel.org
[mailto:linux-newbie-owner@vger.kernel.org]On Behalf Of Ray Olszewski
Sent: Wednesday, November 19, 2003 1:32 PM
To: linux-newbie@vger.kernel.org
Subject: Re: activating eth0
At 12:16 PM 11/19/2003 -0700, Anna G. Zapata wrote:
>Hello everyone,
>
>I am running RH 8.0. My network card was working just fine and then one
>day just flopped over. I have tried
>reactivating it using the GUI and using the command ifup eth0, but nothing
>seems to work. Any thoughts?
First, provide technical descriptions of the failures, not metaphorical
ones (e.g., "just flopped over" is colorful but not very informative).
Beyond that ...
What were the symptoms of the initial failure? Did it occur out of the
blue, or after a reboot, or what?
What does happen when you try to reactivate the interface? That is, what
happens when you enter (as root) the command "ifup eth0"?
What is the complete, unedited output of "ifconfig -a"? (After you do the
above attempt to reactivate, or right after a fresh boot/init, but tell us
which you are reporting.)
What kernel are you running ("uname -a")? Is it stock or one you compiled
locally?
What sort of NIC is it? What kernel module(s) does it use (or is the driver
compiled into the kernel)?
Is there any possibility of either a physical failure of the NIC or a BIOS
problem?
During the boot/init sequence, does the kernel (or the loading of the
relevant module) detect the NIC? (This info will show up in the dmesg
buffer, which RH *may* write out someplace like /var/log/dmesg .)
You may have checked some of this already, but I don't know what actual
efforts are covered by your statement that "nothing seems to work", so I
decided to be inclusive rather than risk skipping something useful because
it was too "obvious" to ask about.
-
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
prev parent reply other threads:[~2003-11-19 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 19:16 activating eth0 Anna G. Zapata
2003-11-19 20:31 ` Ray Olszewski
2003-11-19 21:14 ` Anna G. Zapata [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=HBEJLOFMLEPBMAAEFNFDIECBCDAA.azapata@du.edu \
--to=azapata@du.edu \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox