<br><br><div class="gmail_quote">On Sat, Mar 7, 2009 at 2:36 PM, 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="h5">Allen Edwards wrote:<br>
> On Sat, Feb 21, 2009 at 5:00 AM, Dale Pontius <<a href="mailto:DEPontius@edgehp.net">DEPontius@edgehp.net</a>> wrote:<br>
><br>
>> 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 <<br>
>> <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>
>>>>> 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<br>
>> 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>
>>> 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<br>
>> son,<br>
>>> who is the one who made the last set of changes, but he claimed to have<br>
>> done<br>
>>> nothing. I think it started working after a reboot or perhaps after I<br>
>> got<br>
>>> something else fixed, I don't remember sorry. At this point, if it were<br>
>> 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<br>
>> if<br>
>><br>
>> 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>
>><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<br>
>> go<br>
>>> down and play with my system and at least come up with a definitive test.<br>
>> I need to get my Mythbox out of the basement and hooked to the TV, so I<br>
>> can start working with this.<br>
>><br>
>> Dale Pontius<br>
>><br>
><br>
> As part of my experiments when setting up the dual monitor system I did<br>
> experiment with the settings in myth for screen size and you can make the<br>
> screen smaller and thus no overscan using that. It didn't work for me<br>
> because I have two screens with different sizes that are display 1 but it<br>
> may work for others. Of course, when you use firefox to watch Hulu you have<br>
> a problem. If the myth browser would do flash that could be solved there.<br>
><br>
> That said, is it possible to fake out the screen size with a mode statement<br>
> and reduce the screen that way? Another idea is to run X inside a virtual<br>
> screen that is adjustable. Perhaps that could be part of the release. Is<br>
> that possible, I don't know.<br>
><br>
</div></div>What level of nvidia-drivers are you using?<br>
<br>
Yesterday I borrowed the extra cabling, and brought the new Myth<br>
frontend upstairs and connected using component video at 480i. Aside<br>
from the terrible overscan, the picture is great.<br>
<br>
I'm running Gentoo, and "stable" is nvidia-drivers-177.82 on x86, amd64.<br>
I seemed to remember hearing somewhere that things got dicey past 173,<br>
so I just masked that system and am running nvidia-drivers-173.14.15 on<br>
it now.<br>
<br>
Using nvidia-settings I can't change the overscan. Moreover, it won't<br>
even query any sort of overscan setting, even though it gracefully<br>
accepts your suggested commands.<br>
<br>
I haven't yet tried working with the modelines, though I go to the sites<br>
you suggested, and have one to try. At the moment I'm more concerned<br>
about getting the modeline into the right section in xorg.conf.<br>
Thinking of this, the ongoing "simplification" of xorg.conf scares me,<br>
because I fear it's taking away my ability to MAKE it work, when it<br>
doesn't "just work", as is happening now.<br>
<br>
At the moment I can get back to nvidia-drivers-71.86.06 with several<br>
levels in between. What level are you running?<br>
<font color="#888888"><br>
Dale Pontius<br>
</font></blockquote></div><br><div><br></div><div>I am not at my system so cannot check for sure but it is an agp system and had some other issues with newer drivers so as I recall it was one of the 71 series, perhaps the one you reference above. I think there is only one on the nvidia site of that series.</div>
<div><br></div><div>Allen</div>