[sf-lug] Fedora 7 Ethernet Issues FIX

D.V.Rogers dvr at allshookup.org
Mon Mar 24 02:55:39 PDT 2008

Thanks Erich for your reply.

After poking around google I found the FIX


As of 27 May 2007, in kernel, you may experience the issues
with the r8169 driver if you dual boot Windows on some systems.
Windows by defaults disables the NIC at Windows shutdown time in order
to disable Wake-On-Lan, and this NIC will remain disabled until the
next time Windows turns it on. The r8169 driver in the kernel does not
know how to turn the NIC on from this disabled state; therefore, the
device will not respond, even if the driver loads and reports that the
device is up. To work around this problem, simply enable the feature
"Wake-on-lan after shutdown." You can set this options through
Windows' device manager.

Edit: Problem with dual-booting with Windows exist also in
and kernel, so it is safe to assume that it will concern all
2.6 kernels until the kernel developers update the drivers for RTL8168
to the version that will be able to turn on the NIC from disabled
state. (Corey)

Second edit: Powering off and unplugging the machine for a few seconds
(around 10 usually does it) seems to reset the card, so it will work
in Linux again until you boot Windows again.

The FIX is

In XP enable "Wake-On-Lan after shutdown" as well as make sure power
management for the ethernet card is disabled as well.

See link below for graphical snapshots on how to do this under windows XP


Then I reinstalled Fedora 7 again and network card is working fine. As
it turns out FC7 could see the network card eth0 but XP had blocked it
for usage under FC7. Nasty Windows!!

I am using a Realtek 8168 chipset ethernet card..

With Thanks and Best

On Mon, Mar 24, 2008 at 6:32 PM, Erich Newell <erich.newell at gmail.com> wrote:
> David,
> Please provide some more diagnostics so we can point you in the right
> direction. Try opening a terminal, and typing "ifconfig". This should list
> all of your interfaces and their current settings.
> If you have a listing similar to:
> eth0: error fetching interface information: Device not found
> Then do:
> lspci |grep -i ethernet
> If this comes back empty you may indeed have an issue with the device.
> If you instead see something like:
> eth0      Link encap:Ethernet  HWaddr 00:AB:CD:EF:99:01
>            UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:18
> Then its more likely a DHCP or basic networking configuration error. Check
> your DHCP settings or try static assignment.
>  On Sun, Mar 23, 2008 at 9:36 PM, D. V. Rogers <dvr at allshookup.org> wrote:
> >
> >
> >
> > Hello SF Linux Users Group
> >
> > I am having problems getting my Ethernet Card to work with Fedora 7.
> > FC7 is dual booting with Windows XP, both installed on separate drives
> > Using the standard default partition it installed just fine, it is
> > dualbooting no problem.
> > Fedora does not recognise the Ethernet Card.
> > It knows the eth0 is their but asks me to check the connection...
> > I have tested this as it works fine with XP using DHCP.
> > It is strange as I have set up dual boot boxes before using FC7 and XP
> > with No problem
> >
> > Any suggestions on how to fix this?
> >
> > Best Regards and Thanks
> >
> > David
> >
> > _______________________________________________
> > sf-lug mailing list
> > sf-lug at linuxmafia.com
> > http://linuxmafia.com/mailman/listinfo/sf-lug
> >
> --
> "A man is defined by the questions that he asks; and the way he goes about
> finding the answers to those questions is the way he goes through life."


Parkfield Interventional EQ Fieldwork
28th June - 28th September 2008
Parkfield California USA


More information about the sf-lug mailing list