Author Topic: Overscan settings not held on reboot  (Read 1133 times)

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Overscan settings not held on reboot
« on: November 14, 2006, 07:22:46 am »
When using nvidia cards with 0.41 and tv-out the overscan settings are not remembered.

As a quick hack I have modified /usr/pluto/bin/Start_IceWM.sh to invoke nvtv for geforce2 cards and nvidia-settings for my geforce5 card.

Is this something that is planned for a future release, and if not is there a better way of running the above utilities so changes are not lost during any future upgrades ?

Thanks

NOS

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Overscan settings not held on reboot
« Reply #1 on: November 15, 2006, 11:05:38 am »
It's not planned and at least I didn't even know of the programs that you mention. What are the exact changes that you made? Can you give details on behavior? I think that we take another approach on this, by reducing the size of the Orbiter (when you run A/V Wizard at boot) instead of managing the drivers directly.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Overscan settings not held on reboot
« Reply #2 on: November 15, 2006, 11:51:31 pm »
@radu.c

Thanks for the reply, I have posted details below

nvidia-settings is a utility for directly manipulating nvidia cards based upon geforce 4 and above GPUs.  In our case it provides substantial control of the overscan features provided.

The application is designed to be run as an X-Windows based utility but can also be run from the command line to read a config file and then exit quietly.

The application can be installed by issuing the following command:

Code: newbielink:javascript:void(0); [nonactive]
apt-get install nvidia-settings

To run the application I normally use the computing option from the media director and select pluto admin website.  I then go to a terminal window or use a ssh command prompt to issue the following command:

Code: newbielink:javascript:void(0); [nonactive]
nvidia-settings --display=:0

Using the media director I can now change a whole range of video card settings, and when happy select save settings.

The settings are written to /root/nvidia-settings.rc

I then modify /usr/pluto/bin/Start_IceWM.sh to include the following line before starting the Window Manager:

Code: newbielink:javascript:void(0); [nonactive]
/usr/bin/nvidia-settings --display=:0 -l

This tells the application to read and apply the settings file and then exit.

It would be easy for your AV Wizard to use this program to allow users to tweak their video card settings as all you need to do is update the nvidia-settings.rc file and then call the application as above, the change is applied immediately.

For earlier geforce cards I use nvtv which has limited controls but I have managed to get excellent results on tv out using the same principle as above.

here is the line that I use with nvtv, even though my TV is PAL-I so it is worth trying the various modes available:

Code: newbielink:javascript:void(0); [nonactive]
nvtv -t -r 800,600 -s Large -S PAL-M

Hopefully this post will help other users get perfect tv-out displays on nvidia cards

NOS.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Overscan settings not held on reboot
« Reply #3 on: November 17, 2006, 07:40:54 pm »
NOS:

Could you please post your findings and advices to Wiki ? - I'm sure a lot of users will benefit from that...

Regards,

Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Overscan settings not held on reboot
« Reply #4 on: November 18, 2006, 12:49:37 pm »
Rob,

I will post a wiki tomorrow with more information, will also try and add some stuff regarding ATI cards.

Thanks

NOS