I'm running Wily "daily" and none of the 4.2.0 kernels as of yet have been able to access internet using my nic "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11" on an Asus Z87-A mainboard. Kernel 4.1.6 and all earlier kernels works flawless, so there must be some regression going on. I know it took a while to be able to use the proprietary Nvidia graphics driver in kernel 4.2, due to a licensing issue in the kernel, could this network problem be something of the same? Whatever, I really would like this nic to work in kernel 4.2 and onwards as it is a common nic on gaming oriented mainboards and some of us do game on Linux. lshw (on a working 4.1.6 kernel) *-network beskrivning: Ethernet interface produkt: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller tillverkare: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:03:00.0 logiskt namn: eth0 version: 11 serienummer: d8:50:e6:40:e4:84 storlek: 1Gbit/s kapacitet: 1Gbit/s bredd: 64 bits klocka: 33MHz förmågor: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation konfiguration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=192.168.1.140 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resurser: irq:29 ioport:d000(storlek=256) memory:ef100000-ef100fff memory:ea100000-ea103fff
This coincided in time with a broken network-manager in the repos, so I've tried downgrading but it didn't solve the issue. Also everything has been fine all the time with non 4.2.0-kernels, and the broken network-manager has now been replaced with a good one in the repos. I run the good version. The symptom of the bug above is that network-manager sits searching for network access for about a minute and then states "no network". The nic itself, eth0, is presented in the gui but it is impossible to get it to access any network.
I did a fresh install which solved the problem, kernel 4.2.0-10.11 now works. Possibly it was some of the packages from Gnome 3 Team that had borked my install. Strange though that it only affected 4.2-kernels ... closed.