[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20091211145824.GB19780@slinky.marshes.co.uk>
Date: Fri, 11 Dec 2009 14:58:24 +0000
From: Ian Marsh <mushypea@...inion.net.uk>
To: Franco Fichtner <franco@...tsummer.de>
Cc: netdev@...r.kernel.org
Subject: Re: r8169
Hi, Franco,
Thanks for your reply.
On Fri 11 Dec 2009 at 10:17:49 +0100, Franco Fichtner wrote:
> At work we're also using ubuntu which comes with the r8169 driver,
> and had to deal with network dropouts while trying to benchmark
> heavy loads. This is what the support of our boxes told us:
>
>> Please use 8168 instead of 8169. Please see the notice about this
>> important point in May..
>>
>> The situation you observed should be a misjudgment by the Linux Kernel.
>> Driver 8168 is recommended by Realtek. Please use this revision.
I have tried the 8168 driver, and get the same problem. I followed this
process:
1) rmmod the 8169 driver
2) blacklist the 8169 driver
3) install the 8168 driver
4) rebuild initramfs
5) reboot
Symptoms are identical; it loads the module, gets an IP, pings, fetches Google
okay, but nothing more substantial.
I believe I tried 8.014.00 with a patch to make it compile for 2.6.31 (from
www.jamesonwilliams.com/bin/r8168_scripts.tar.bz2 ). I don't think I could
get 8.015.00 from www.realtek.com.tw to compile at all, but can't check at the
moment.
When searching for a solution, I did come across several different problems
with the r8169 driver, mostly believed to be fixed in earlier kernels, and
tried several fixs/workarounds to no avail.
Ian.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists