| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200905091403.n49E3fb5025843@mercury.physics.adelaide.edu.au> Date: Sat, 9 May 2009 23:33:40 +0930 (CST) From: Jonathan Woithe <jwoithe@...sics.adelaide.edu.au> To: linux-kernel@...r.kernel.org Cc: jwoithe@...sics.adelaide.edu.au (Jonathan Woithe) Subject: Realtek 8168D: no active link (2.6.29.2) Hi I am currently testing a Gigabyte EX58-UD4P mainboard which is equipped with an onboard Realtek RTL-8168D network controller. The kernel version is 2.6.29.2. The r8169 module is loaded correctly, identifies the chip as an 8168D and seemingly is happy. However, after loading the module the link remains dead. The green and orange status LEDs remain off at all times. It doesn't seem to matter whether the remote end of the network line is plugged into a switch when the computer is booted. Repeatedly removing and inserting the r8169 module also doesn't help. In short, it seems impossible to get a functioning network link with the 8168D. Support for the 8168D appears relatively recent given related patch activity around October 2008, so I'm guessing it's still a work in progress. I would be happy to test patches and run other tests if it will help make the 8168D-based chipsets work better. Alternatively, if there's a known workaround to get the 8168D working now I would be interested to try it. Regards jonathan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists