<br><br><div class="gmail_quote">On Sat, Feb 21, 2009 at 5:00 AM, Dale Pontius <span dir="ltr"><<a href="mailto:DEPontius@edgehp.net">DEPontius@edgehp.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="Wj3C7c">Allen Edwards wrote:<br>
> On Fri, Feb 20, 2009 at 7:59 PM, <<a href="mailto:jarpublic@gmail.com">jarpublic@gmail.com</a>> wrote:<br>
><br>
>> On Fri, Feb 20, 2009 at 10:49 PM, Allen Edwards <<a href="mailto:allen.p.edwards@gmail.com">allen.p.edwards@gmail.com</a><br>
>>> wrote:<br>
>>> noticed no difference between 0.0 and<br>
>>>> 1.0 on the overscan setting in xorg.conf.<br>
>>><br>
>>> For sure the xorg.conf TVOverScan will not work. It has not worked for<br>
>>> many months. Although it is still in the documentation at Nvidia, I was<br>
>>> told July that it was "depreciated".<br>
>>><br>
>>> Please, try this from the command line:<br>
>>> nvidia-settings -1 TVOverScan[*TV*-0]=20<br>
>>><br>
>> This gives a syntax error. I think you mean :<br>
>> nvidia-settings -a TVOverScan[*TV*-0]=20<br>
>><br>
>> but that still has no effect for me. Are you using an 8400 GS and if so<br>
>> what driver are you running?<br>
>><br>
><br>
> You are correct in what I should have said. I am not using a 8400GS<br>
> although I have one in my windows machine. I have a 6200.<br>
><br>
> I wish I could remember what happened the last time I changed my system<br>
> because I was sure that TVOverScan quit working. I remember calling my son,<br>
> who is the one who made the last set of changes, but he claimed to have done<br>
> nothing. I think it started working after a reboot or perhaps after I got<br>
> something else fixed, I don't remember sorry. At this point, if it were me,<br>
> I would put that command just before the exit 0 in /etc/gdm/Init/Default<br>
> and reboot. If that didn't work, they you clearly have a board specific<br>
> issue or another Nvidia update issue. My Nvidia driver is 173.14.12 so if<br>
<br>
</div></div>Well that tears it. It appears that you can have proper overscan OR you<br>
can have vdpau, but not both. I recently set up a new laptop for work,<br>
and found that I had to stick with the 173-series nVidia drivers -<br>
there's a nasty timeout with the later ones.<br>
<br>
So if proper overscan requires 173.x and vdpau requires >180...<br>
<div class="Ih2E3d"><br>
> you have a later one, perhaps you can try that one. Otherwise, it would<br>
> have to be the board. If it still doesn't work, let me know and I will go<br>
> down and play with my system and at least come up with a definitive test.<br>
</div>I need to get my Mythbox out of the basement and hooked to the TV, so I<br>
can start working with this.<br>
<font color="#888888"><br>
Dale Pontius<br>
</font></blockquote></div><br><div>As part of my experiments when setting up the dual monitor system I did experiment with the settings in myth for screen size and you can make the screen smaller and thus no overscan using that. It didn't work for me because I have two screens with different sizes that are display 1 but it may work for others. Of course, when you use firefox to watch Hulu you have a problem. If the myth browser would do flash that could be solved there.</div>
<div><br></div><div>That said, is it possible to fake out the screen size with a mode statement and reduce the screen that way? Another idea is to run X inside a virtual screen that is adjustable. Perhaps that could be part of the release. Is that possible, I don't know.</div>
<div><br></div><div>Allen</div><div><br></div><div><br></div><div><br></div>