Re: driver r8169 suddenly failed

Robert Grasso : [...] > So, what is your opinion : > - should I broaden my request for help to other teams than yours (kernel > maintainers) ? If I had to untangle this mess, I would check that my router is not configured with an empty dhcp range. Then I would put

Re: driver r8169 suddenly failed

Hello, I have some unexpected (and interesting) news. I did not run the test yet. While I was investigating my issue, I ordered a fast Ethernet-to-USB3 converter, able to reach 1000Mbit/s, in order to recover my broadband quickly : here is the chip as reported by dmesg : [8.114327]

Re: driver r8169 suddenly failed

Thank you for your quick answer ! Allow me some days for this test : 1 - I am at work these days 2 - it has been a while since I have dealt with custom kernels, I am a bit rusty, it will be good to review this topic -- Robert Grasso @home --- UNIX was not designed to stop you from doing

Re: driver r8169 suddenly failed

Robert Grasso : [dhcp snafu] > First of all, can you confirm that I am doing right in posting to you > (addresses found in README.Debian) ? It isn't completely wrong. > If I do, can you help ? I am not very proficient with Ethernet, and I am not > able to figure out

driver r8169 suddenly failed

Hello, I am a senior Linux sysadmin. At home, I am using a Shuttle DS47 barebones computer as my firewall; it contains the following two network cards : 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01) 02:00.0 Ethernet controller: Realtek