From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110324/003633.html | 87 +++++++++++++++++++++++++++++++++ 1 file changed, 87 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110324/003633.html (limited to 'zarb-ml/mageia-dev/20110324/003633.html') diff --git a/zarb-ml/mageia-dev/20110324/003633.html b/zarb-ml/mageia-dev/20110324/003633.html new file mode 100644 index 000000000..8cdbdc52d --- /dev/null +++ b/zarb-ml/mageia-dev/20110324/003633.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] Sudden problems with r8169 NICs ? + + + + + + + + + +

[Mageia-dev] Sudden problems with r8169 NICs ?

+ andre999 + andr55 at laposte.net +
+ Thu Mar 24 22:30:57 CET 2011 +

+
+ +
Frank Griffin a écrit :
+>
+> On 03/24/2011 04:37 PM, Thomas Backlund wrote:
+>>
+>> I'm not sure it's broken.
+>>
+>> Realtek is known to have somewhat crappy NICs that can tend to lock up
+>> in a "middle state" if a driver probe comes too fast, and then they
+>> dont react to any link or driver loading anymore.
+>>
+>> One way that might help is to power off the computer, disconnect it
+>> from power _and_ disconnect the network cables, wait a few minutes,
+>> connect everything again and try again.
+>
+> OK. I *did* try a cold boot, but I didn't go quite that far. I'll try
+> this, but probably not till Monday. Odd, though, that I've never had a
+> whisper of trouble from this NIC in the years since I built this
+> machine. Thanks for the suggestion.
+
+I had a similar problem from time to time on a system with an 8139c nic 
+a while back.
+The suggested solution worked.
+(It was a common solution for similar problems at the time.)
+Sometimes unplugging/replugging the data cable a few times helps.
+It might be more the connected circuits than the nic itself.
+Static charges, apparently.
+
+-- 
+André
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1