<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Marvell Yukon on Asus P5NSLI in Other Manufacturers</title>
<link>http://www.dslreports.com/forum/r22170958</link>
<description></description>
<language>en</language>
<pubDate>Wed, 02 Dec 2009 23:43:04 EDT</pubDate>
<lastBuildDate>Wed, 02 Dec 2009 23:43:04 EDT</lastBuildDate>

<item>
<title>Re: Marvell Yukon on Asus P5NSLI</title>
<link>http://www.dslreports.com/forum/remark,22381870</link>
<description><![CDATA[<A HREF="/useremail/u/377417"><b>ctceo</b></A> : UPDATE:<br><br>Well its been more than a month, and I am starting to have the same problem again.<br><br>For now I'm not going to suggest anyone get this motherboard UNLESS they have a replacement PCI NIC to use. The on board one doesn't pass muster.<br><br>I further tested by looking at the performance and problems of over 5 driver versions ,and several custom drivers. All had the same problems eventually, and diagnosis of an in-depth hardware nature shows that the chip itself is of faulty MFG.<br><br>Good luck to everyone out there who are still trying to get this dang chipset to play nice.<br><small>--<br>Would you like your ISP to govern how much you can use the web in a month? Well it might happen if we don't do something NOW!  &raquo;<A HREF="http://www.ipetitions.com/petition/PMDBI/" >www.ipetitions.com/petition/PMDBI/</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22381870</guid>
<pubDate>Wed, 13 May 2009 10:09:35 EDT</pubDate>
</item>

<item>
<title>Re: Marvell Yukon on Asus P5NSLI</title>
<link>http://www.dslreports.com/forum/remark,22200712</link>
<description><![CDATA[<A HREF="/useremail/u/377417"><b>ctceo</b></A> : After several tests, I think I've finally found the most stable driver and NIC Advanced properties configuration.<br><br>Driver Version 8.24.3.3 (WHQL Signed 3/30/2005)<br>Driver Provider, Marvell<br><br>802.1p Support, Off<br>Flow Control, Off<br>Hardware Checksumming, Off<br>Interrupt Moderation, On<br>Jumbo Frames, Disabled (Hub is only PN205ES 10/100 Switch)<br>Log Status Messages, None<br>Max IRQ per Sec, 5000<br>Network Address, Not Present<br>Number of Receive Buffers, 64<br>Number of Transmit Buffers, 64<br>Speed & Duplex, Auto-Sense<br>Wake from Shutdown, Off<br>Wake Up Capabilities, Disabled<br><small>--<br>Would you like your ISP to govern how much you can use the web in a month? Well it might happen if we don't do something NOW!  &raquo;<A HREF="http://www.ipetitions.com/petition/PMDBI/" >www.ipetitions.com/petition/PMDBI/</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22200712</guid>
<pubDate>Tue, 07 Apr 2009 19:36:00 EDT</pubDate>
</item>

<item>
<title>Marvell Yukon on Asus P5NSLI</title>
<link>http://www.dslreports.com/forum/remark,22170958</link>
<description><![CDATA[<A HREF="/useremail/u/377417"><b>ctceo</b></A> : The Marvel Yukon on a new Asus P5NSLI is acting strange. It seems to stop responding after a few minutes of web browsing. I've tried everything I know to get it to stop. DRTCP, NIC Advanced properties, reboots cold and warm, etc. etc.<br><br>I've been seeing reports of this problem from several sites, but no resolutions.<br><br>The NIC worked perfectly fine for the first month or so then it suddenly started acting up.<br><small>--<br>Would you like your ISP to govern how much you can use the web in a month? Well it might happen if we don't do something NOW!  &raquo;<A HREF="http://www.ipetitions.com/petition/PMDBI/" >www.ipetitions.com/petition/PMDBI/</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,22170958</guid>
<pubDate>Thu, 02 Apr 2009 12:21:59 EDT</pubDate>
</item>

</channel>
</rss>
