© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
@Kai-Heng your latest kernel completely breaks the network using r8169 for me. The system sort of manages to complete startup but fails to attach an address to the network card. This is accompanied with lots of console output similar to this
```
Aug 7 14:46:28 kernel: [ 25.761050] r8169 0000:05:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Aug 7 14:46:28 kernel: [ 25.771937] r8169 0000:05:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Aug 7 14:46:28 kernel: [ 26.068062] r8169 0000:05:00.0 eth0: rtl_ocpar_cond == 1 (loop: 100, delay: 1000).
Aug 7 14:46:28 kernel: [ 26.168057] r8169 0000:05:00.0 eth0: rtl_ocpar_cond == 1 (loop: 100, delay: 1000).
Aug 7 14:46:28 kernel: [ 26.268060] r8169 0000:05:00.0 eth0: rtl_ocpar_cond == 1 (loop: 100, delay: 1000).
Aug 7 14:46:28 kernel: [ 26.368055] r8169 0000:05:00.0 eth0: rtl_ocpar_cond == 1 (loop: 100, delay: 1000).
```
Using the standard bionic kernel the network works as long as I run `sudo ethtool -s eth0 wol g` between reboots. Otherwise the network card just vanishes (not visible in BIOS and Linux) until I unplug the computer for a minute or so.