Author Topic: Problems with AVWIZARD (Custom Resolution)  (Read 2152 times)

LuCkY

  • First post!
  • Posts: 1
    • View Profile
Problems with AVWIZARD (Custom Resolution)
« on: August 06, 2008, 10:12:56 pm »
Hi all,
i needed a custom resolution (1680x1050). So i first wanted to prevent LinuxMCE from modifying the xorg.conf, but i saw that i can edit the template(xorg.conf.in + Resolution.conf)
I did done this with:http://wiki.linuxmce.org/index.php/Custom_Display_Resolutions

Here are my modifications:
xorg.conf.in
Code: [Select]
71c71
<       Driver          "fglrx"
---
>       Driver          "vesa"
77c77
<       Option          "UseEDID"                       "true"
---
>       Option          "UseEDID"                       "false"
Resolution.conf:
Code: [Select]
159,161c159,161
<       name = "abc"
<       width = 1680
<       height = 1050
---
>       name = "1080p"
>       width = 1920
>       height = 1080
239,256d238
<       name = "1680x1050"
<       width = 1680
<       height = 1050
<       aspect_ratio = "16:9"
<       modeline
<       {
<               refresh = 60
<               builtin = true
<       }
<       modeline
<       {
<               refresh = 75
<               builtin = true
<       }
<       visible = true
< }


After setting the custom resolution in the AVWIZARD(Step1) there comes an interesting warning message:

Warning option: 'WindowWidth' not stored because it gets an empty value+ WizSet WindowHeight ' '
Warning option: 'WindowHeight' not stored because it gets an empty value+ WizSet VideoOutput DVI


It looks like WindowWidth var is empty and the WindowHeight gets the worng input from the var VideoOutput

Does any one see my Problem?:O)

Thanks for help

stallione

  • Veteran
  • ***
  • Posts: 63
    • View Profile
Re: Problems with AVWIZARD (Custom Resolution)
« Reply #1 on: August 06, 2008, 10:38:55 pm »
I am not in front of my box, but I know that there are 3 places you'll have to edit and replace on the xorg.conf file and then do a reboot, you'll see that your new resolution kicks in. (I am running it on my box.)
Cheers!