No internet in Linux after rebooting from Windows

Question

After rebooting from Windows XP to Gentoo Linux, I can't connect to anywhere (internet, others computers, router). Internet is working fine if instead of rebooting I shutdown the PC and then boot properly.

Ifconfig shows everything is fine, except no packet are received/transmitted.

ping 192.168.9.1
-> Destination Host Unreachable

mtr <ip> shows nothing, just empty line. Works only on loopback and IP specified in config: /etc/conf.d/net.eth0

IP is assigned automatically via DHCP and by MAC address (so both Linux & Windows have same IP)
IP is static 192.168.9.3.

Router used: Asus WL-500gP (with Oleg firmware), whole network is 100 Base-T, IP: 192.168.9.1 MASK: 255.255.255.0

Windows info:

• NIC: Realtek RTL8139/810x Family
• Driver version: 5.719.325.2009

Linux info:

• DMESG: 8139too RealTek RTL8139
• Kernel built-in driver: RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter
• Kernel version 3.5.7 & latest 3.7.4 (gentoo-sources)

The LEDs on NIC blink only in Windows, remain black even during POST.

Answer 1

Google is my friend. Thanks goes to Ubuntu Forums and marvelous ArchWiki:

Users with Realtek 8168 8169 8101 8111(C) based NICs (cards / and on-board) may notice an issue where the NIC seems to be disabled on boot and has no Link light. This can usually be found on a dual boot system where Windows is also installed. It seems that using the offical Realtek drivers (dated anything after May 2007) under Windows is the cause. These newer drivers disable the Wake-On-LAN feature by disabling the NIC at Windows shutdown time, where it will remain disabled until the next time Windows boots. You will be able to notice if this issue is affecting you if the Link light remains off until Windows boots up; during Windows shutdown the Link light will switch off. Normal operation should be that the link light is always on as long as the system is on, even during POST. This issue will also affect other operative systems without newer drivers (eg. Live CDs).

Possible solutions:

1. Rollback/change Windows driver
2. Enable WOL in Windows driver
3. Newer Realtek Linux driver
4. Enable LAN Boot ROM in BIOS/CMOS

I tried 2nd one which works. 4th did not (MB is some old EPoX).

To Enable WOL hit WIN+R -> devmgmt.msc -> double-click your NIC -> On Advanced Tab set Shutdown Wake-On-Lan to Enabled. REBOOT!

If you are interested, bug is filled here: https://bugzilla.kernel.org/show_bug.cgi?id=53521

Answer 2

What kernel version are you using? I'd try using the latest stable point release of the Linux kernel, at the very least.

My initial insight into this is that it's likely a bug where Windows "does something" to the hardware, which is not properly reset on a regular reboot, but is reset during a full power off. Whatever Windows does is incompatible with the way the 8139too driver works.

Using the latest kernel version will reduce the possibility that there is a bug which has already been fixed. If the latest kernel version doesn't resolve the bug, I would include the following in an email to LKML (the Linux Kernel Mailing List) or at least to the Gentoo developers:

• Output of lspci -nnvv
• Output of dmesg on a cold boot where ethernet works
• Output of dmesg on a reboot from Windows