On 6/6/07, <b class="gmail_sendername">Jim Cornette</b> <<a href="mailto:fc-cornette@insight.rr.com">fc-cornette@insight.rr.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dylan Semler wrote:<br>> On 6/6/07, *Jim Cornette* <<a href="mailto:fc-cornette@insight.rr.com">fc-cornette@insight.rr.com</a><br>> <mailto:<a href="mailto:fc-cornette@insight.rr.com">fc-cornette@insight.rr.com
</a>>> wrote:<br>><br>> Regarding using the GUI tools instead of command line tools, I use the<br>> GUI tools if available. Why not if they setup items correctly.<br>><br>><br>> That's true. It's just much more cumbersome to explain the steps when
<br>> troubleshooting.<br>><br>> If you open up a terminal and run /sbin/lspci, what is the output for<br>> the Ethernet?<br>> There is some bug for one NIC type. This might be the one if it causes
<br>> so much trouble. I think it was E1000 but cannot recall the specifics of<br>> the Ethernet card that has problems.<br>><br>><br>> If it's a laptop, is NIC still the right term? Anyways the device is
<br>> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169<br>> Gigabit Ethernet (rev 10)<br>><br>> It was working in all previous Fedora releases and I think this is a<br>> pretty common laptop ethernet controller so I'm not skeptical about it
<br>> being a bug, but who knows. Is there any way to get more output/debug<br>> info when enabling the device?<br><br>There seems to be bugs filed that describe your problem in some aspects.<br>The card must not be detecting whether the cable is connected or not in
<br>your instance.<br><br><a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242572">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242572</a><br><br>and<br><br><a href="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242301">
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242301</a><br><br>Regarding information about what is going on, dmesg and var/log/messages<br>should let you know what is going on. I had trouble with a 3com card<br>that worked since RHL
5.2 go bad from one release to a newer release one<br>day. It took a long time to get that problem fixed. I believe messages<br>is where I found most failure information.</blockquote><div><br>Geeze, thanks for doing the legwork for me. I'll be sure to search bugzilla next time before posting to the list. Anyways I'll keep an eye on these bugs.
<br></div><br></div>-- <br>Dylan<br><br>Type faster. Use Dvorak:<br><a href="http://dvzine.org">http://dvzine.org</a>