[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#731473: marked as done (Wheezy: eth0 not working)

Your message dated Sat, 24 Apr 2021 12:06:16 -0700 (PDT)
with message-id <60846c28.1c69fb81.e1e49.d700@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #731473,
regarding Wheezy: eth0 not working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
731473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731473
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 

Package: linux-image-3.2.0-4-amd64
Version: 3.2.51-1
I installed Wheezy on a new machine (Shuttle DS47) at first via netinst-CD, but access to the mirrors was not possible. Thus, Wheezy was installed with the standard set of DVDs, to be able to solve the problem from an working OS. Symptoms were as follows: It was not possible to ping from or to the machine, although dmesg said that eth0 was up and ready and although arp -a from another computer could identify MAC and IP address of the attached Shuttle. Two Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller are built in and the module r8169 was present.
Only after downloading the proprietary driver from the sites of Realtek, transferring it via USB stick to the Shuttle and compiling it there made the ethernet work.
--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: