Bug#756183: Realtek RTL8111/8168/8411 module (r8168 or r8169) not loaded at boot

2014-07-27 Thread Ryan Kavanagh
On Sun, Jul 27, 2014 at 10:09:14AM +0200, Ryan Kavanagh wrote:
 The module for my Ethernet controller [0200]: Realtek Semiconductor
 Co., Ltd.  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 [10ec:8168] (rev 09) does not get loaded at boot under 3.14-2-amd64,
 but does on previous kernel versions. This device works with both the
 r8168 and the r8169 modules, but previous kernels loaded r8168.

I did some more investigating, and it turns out that I had r8168-dkms
installed, and in its long description:

 Installation of the r8168-dkms package will disable the in-kernel r8169
 module. To re-enable r8169, the r8168-dkms package must be purged.

My hypothesis is that either r8168-dkms failed to compile the DKMS
module locally on my end for 3.14-2 (most likely), and since the
r8168-dkms package was installed, the kernel didn't load r8169 either;
or that r8168 managed to compile it and 3.14-2 refused to load it, and
since the r8168-dkms package was installed, the kernel didn't load r8169
either. After purging r8168-dkms, r8169 started getting loaded properly
by 3.14-2 at boot.

Thus, this is likely a non-bug. Sorry for the noise.

Best wishes,
Ryan


signature.asc
Description: Digital signature


Bug#756183: Realtek RTL8111/8168/8411 module (r8168 or r8169) not loaded at boot

2014-07-27 Thread Ben Hutchings
Control: reassign -1 r8168-dkms

On Sun, 2014-07-27 at 10:52 +0200, Ryan Kavanagh wrote:
 On Sun, Jul 27, 2014 at 10:09:14AM +0200, Ryan Kavanagh wrote:
  The module for my Ethernet controller [0200]: Realtek Semiconductor
  Co., Ltd.  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
  [10ec:8168] (rev 09) does not get loaded at boot under 3.14-2-amd64,
  but does on previous kernel versions. This device works with both the
  r8168 and the r8169 modules, but previous kernels loaded r8168.
 
 I did some more investigating, and it turns out that I had r8168-dkms
 installed, and in its long description:
 
  Installation of the r8168-dkms package will disable the in-kernel r8169
  module. To re-enable r8169, the r8168-dkms package must be purged.
 
 My hypothesis is that either r8168-dkms failed to compile the DKMS
 module locally on my end for 3.14-2 (most likely), and since the
 r8168-dkms package was installed, the kernel didn't load r8169 either;
 or that r8168 managed to compile it and 3.14-2 refused to load it, and
 since the r8168-dkms package was installed, the kernel didn't load r8169
 either. After purging r8168-dkms, r8169 started getting loaded properly
 by 3.14-2 at boot.
 
 Thus, this is likely a non-bug. Sorry for the noise.

It's a bug in r8168 that it failed to compile.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


signature.asc
Description: This is a digitally signed message part