<br><br><div><span class="gmail_quote">On 3/1/06, <b class="gmail_sendername">Dylan R. Semler</b> <<a href="mailto:dsemler@macalester.edu">dsemler@macalester.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<<a href="http://www.mythtv.org/wiki/index.php/PCI_Latency">http://www.mythtv.org/wiki/index.php/PCI_Latency</a>><br><br><br>I just tried changing the latency on my three machines. I have two Dell<br>8200 desktops from about 2002 and a Sager laptop from December 2005. In
<br>all three machines, the initial IDE latency was 0 and changing it with<br><br>setpci -v -s 00:1f.1 latency_timer=b0 (or any other value)<br><br>did not seem to do anything. At least lspci -v continued to display<br>their latency as 0 (I have not been able to test this with Myth yet).
<br>Furthermore, I found that if tried this command on ANY controller whose<br>intial latency was 0, the command did nothing. If the initial latency<br>was not zero, the command would change the latency to the desired<br>
value. I Also tested that if a controller ititially had a non-zero<br>latency, and I changed it to zero, I was still able to change it back to<br>other values. I have no idea why this is or what can be done, but I<br>thought I'd add some more datapoints to the set. If anyone wants the
<br>maker of these mobos, I can probably find that out somehow.<br><br>Dylan<br></blockquote></div><br>Ditto here. Dell Dimension 8250 P4 2.4GHz Intel 828 chipset.<br><br>DS<br>