[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200905141208.n4EC8xh3017350@mercury.physics.adelaide.edu.au>
Date: Thu, 14 May 2009 21:38:59 +0930 (CST)
From: Jonathan Woithe <jwoithe@...sics.adelaide.edu.au>
To: romieu@...zoreil.com (Francois Romieu)
Cc: jwoithe@...sics.adelaide.edu.au (Jonathan Woithe),
linux-kernel@...r.kernel.org
Subject: Re: Realtek 8168D: no active link (2.6.29.2)
Hi again
> Jonathan Woithe <jwoithe@...sics.adelaide.edu.au> :
> [...]
> > 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.
>
> Which XID does it display in dmesg when the module is inserted and which
> behavior do you experience with version 8.011.00 of Realtek's r8168 driver ?
Following up on my previous email, it seems that the stock kernel r8169
driver is now working with the card in this machine ever since I tried the
Realtek driver version 8.012.00. It's almost as if the Realtek driver
"unlocked" something on the chip (eg: activated the PHY), the status of
which is remembered across reboots and hard powercycles.
For instance, before using the Realtek driver the green "link" LED would
never light - not during BIOS POST, Linux boot or after the respective
ethernet interface was brought up. Now, having used the Realtek driver
once, the green "link" LED lights even during BIOS POST. I then tested this
by removing power from the machine completely for about a minute. When
power was restored and the PC was turned on, the green "link" LED came on
almost immediately.
Note that all this is with 2.6.30-rc5.
I'll test again tomorrow after the machine has been off for several hours.
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