Dylan Semler wrote:
On 6/6/07, *Jim Cornette* <fc-cornette@xxxxxxxxxxxxxx
<mailto:fc-cornette@xxxxxxxxxxxxxx>> wrote:
Regarding using the GUI tools instead of command line tools, I use the
GUI tools if available. Why not if they setup items correctly.
That's true. It's just much more cumbersome to explain the steps when
troubleshooting.
If you open up a terminal and run /sbin/lspci, what is the output for
the Ethernet?
There is some bug for one NIC type. This might be the one if it causes
so much trouble. I think it was E1000 but cannot recall the specifics of
the Ethernet card that has problems.
If it's a laptop, is NIC still the right term? Anyways the device is
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169
Gigabit Ethernet (rev 10)
It was working in all previous Fedora releases and I think this is a
pretty common laptop ethernet controller so I'm not skeptical about it
being a bug, but who knows. Is there any way to get more output/debug
info when enabling the device?
There seems to be bugs filed that describe your problem in some aspects.
The card must not be detecting whether the cable is connected or not in
your instance.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242572
and
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242301
Regarding information about what is going on, dmesg and var/log/messages
should let you know what is going on. I had trouble with a 3com card
that worked since RHL 5.2 go bad from one release to a newer release one
day. It took a long time to get that problem fixed. I believe messages
is where I found most failure information.
Jim
--
Dylan
Type faster. Use Dvorak:
http://dvzine.org
--
It's not usually cost effective time wise to go do it. But if something's
really pissing you off, you just go find the code and fix it and that's
really cool.
-- John Carmack, on the advantages of open source
