Skip to contentSkip to conversation

How can I set non-60Hz-Modes?

DISCUSSION Dexter Filmore 5 participants 15 messages Aug 5, 2011 – Aug 11, 2011

lore
Share & tools
lore
#0 lore raw

I used to do that with the nvidia tool on nv, but now I'm a little stuck:
No matter what I do X comes up at 60 Hz. I need to do 50 tho so the attached plasma tv doubles it to 100 (at 60 it flickers, plus pulldown problems)

EDID reports a refresh range of 58-62 Hertz which I overrode in xorg.conf. When I feed it a custom mode with xrandr --newmode / --addmode it does 50hz alright, but I can't make it permanent from xorg.conf.

I tried the Preferred Mode option and "ModeValidation" tho I am not sure the latter is nvidia specific.

X log can be found at:
http://www.vaultofsages.de/~dexterf/xorg60hzlog

xorg.conf below.

Can someone have a look and advise, please?

Dex

Section "ServerLayout"

    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"

EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG Electronics LG TV"
    HorizSync       28.0 - 83.0
    VertRefresh     24.0 - 62.0
    Option         "DPMS"
    Modeline "1920x1080_50"  141.50  1920 2032 2232 2544  1080 1083 1088 
1114 -hsync +vsync
    Modeline "1920x1080_24"   63.00  1920 1976 2160 2400  1080 1083 1088 

1098 -hsync +vsync
Option "PreferredMode" "1920x1080_50"
Option "ModeValidation" "DFP-0: AllowNon60HzDFPModes"
EndSection

Section "Device"

    Identifier     "Device0"
    Driver         "intel"
    VendorName     "intel corp"
    BoardName      "SandyBridge"

EndSection

Section "Screen"

    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"

DefaultDepth 24
Option "TwinView" "0"
Option "DynamicTwinView" "0"
Option "FlatPanelProperties" "Scaling = Native"
SubSection "Display"
Depth 24
EndSubSection

EndSection

Signature · 6 lines
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------
#1 lore raw
Quoted 3 lines · Dexter Filmore

I used to do that with the nvidia tool on nv, but now I'm a little stuck:
No matter what I do X comes up at 60 Hz. I need to do 50 tho so the attached plasma tv doubles it to 100 (at 60 it flickers, plus pulldown problems)

You should be able to use cvt to generate the modeline you need. Then you can use xrandr --newmode to add it, xrandr --addmode to associate it with the appropriate output, and then use xrandr to set the mode.

I've successfully used this technique when my laptop is connected to a projector through a long VGA cable (and possible a switch/splitter) that prevents it from reading the EDID info.

Signature · 4 lines
========================================================================
Ian Pilcher                                         [email protected]
"If you're going to shift my paradigm ... at least buy me dinner first."
========================================================================
#2 lore raw

That's what I do now. Thing is, the same TV provided EDID to an nvidia before and there I could use the settings tool to tweak these things. I'd like the machien to go 50Hz at login tho.
I can tinker a script, but this just does not seem to be working as supposed.

Dex

Quoted 13 lines · On Saturday 06 August 2011 03:23:33 Ian Pilcher wrote:
Quoted 4 lines · Dexter Filmore

I used to do that with the nvidia tool on nv, but now I'm a little stuck:
No matter what I do X comes up at 60 Hz. I need to do 50 tho so the attached plasma tv doubles it to 100 (at 60 it flickers, plus pulldown problems)

You should be able to use cvt to generate the modeline you need. Then you can use xrandr --newmode to add it, xrandr --addmode to associate it with the appropriate output, and then use xrandr to set the mode.

I've successfully used this technique when my laptop is connected to a projector through a long VGA cable (and possible a switch/splitter) that prevents it from reading the EDID info.

Signature · 6 lines
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

#3 lore raw
In reply to Dexter Filmore
Quoted 2 lines

EDID reports a refresh range of 58-62 Hertz which I overrode in xorg.conf.

I've learned that overriding detected values is discouraged. The prefered solution would be to alter the EDID data in your display harwdare or insert a special EDID sending device in the monitor cable.

Configuration of software is not done through conf files anymore, it is done using hardware. If autodetection gives values you do not want, you have to alter the hardware.

The reason for this policy is, if someone succeeds in solving some issue using altered conf files, he might post this solution to the internet, where someone else might find and try it. In certain cases this could even damage hardware.

So it looks like it's safer to leave the user with a hardware that does not run due to lacking setting options than giving the user the possibility to damage his hardware using wrong settings.

Greets,
Kiste

#4 lore raw

On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed:

Quoted 3 lines

Configuration of software is not done through conf files anymore, it is done using hardware. If autodetection gives values you do not want, you have to alter the hardware.

I can't imagine people trying to configure multihead without .conf files. How's that supposed to work?

Signature · 6 lines
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
#5 lore raw
Quoted 8 lines · Felix Miata

On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed:

Quoted 3 lines

Configuration of software is not done through conf files anymore, it is done using hardware. If autodetection gives values you do not want, you have to alter the hardware.

I can't imagine people trying to configure multihead without .conf files. How's that supposed to work?

I've been exaggerating a bit, I must confess... But, to keep things straight, I really did multihead setup using xrandr in a startup script.

Greets,
Kiste

#6 lore raw

On 2011/08/10 19:58 (GMT+0200) Oliver Seitz composed:

Quoted 8 lines
Quoted 5 lines · Felix Miata

On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed:

Quoted 3 lines

Configuration of software is not done through conf files anymore, it is done using hardware. If autodetection gives values you do not want, you have to alter the hardware.

Quoted 5 lines
Quoted 2 lines

I can't imagine people trying to configure multihead without .conf files. How's that supposed to work?

I've been exaggerating a bit, I must confess... But, to keep things straight, I really did multihead setup using xrandr in a startup script.

You think mere mortals are going to find startup scripts, not to mention xrandr, easier to figure out than config files? Plus, in my experience, there are far too many different script file names and locations among various distros than X config files and locations. Not to say .config file setup is easy, because it's not, but to me they're the lesser evil.

Signature · 6 lines
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
#7 lore raw
Quoted 10 lines · Felix Miata

On 2011/08/10 19:58 (GMT+0200) Oliver Seitz composed:

Quoted 7 lines
Quoted 5 lines · Felix Miata

On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed:

Quoted 3 lines

Configuration of software is not done through conf files anymore, it is done using hardware. If autodetection gives values you do not want, you have to alter the hardware.

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

I can't imagine people trying to configure multihead without .conf files. How's that supposed to work?

I've been exaggerating a bit, I must confess... But, to keep things straight, I really did multihead setup using xrandr in a startup script.

You think mere mortals are going to find startup scripts, not to mention xrandr, easier to figure out than config files?

No. I described this situation because it annoys me. I do not like it at all. Nevertheless I have to cope with it in some way as I can't modify the drivers.

Greets,
Kiste

#8 lore raw

I thought of "X without config file" as a bad idea from day one - and each time I have to do something that is based on something not properly reported by hardware or not properly auto-detected by X it so totally proves me right.

Face it, neither are hardware manufacturers capable of adhering to their standards nor is X capable of reading my mind.

Quoted 27 lines · On Wednesday 10 August 2011 21:09:35 Oliver Seitz wrote:
Quoted 7 lines · Felix Miata

On 2011/08/10 19:58 (GMT+0200) Oliver Seitz composed:

Quoted 6 lines
Quoted 5 lines · Felix Miata

On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed:

Quoted 3 lines

Configuration of software is not done through conf files anymore, it is done using hardware. If autodetection gives values you do not want, you have to alter the hardware.

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

I can't imagine people trying to configure multihead without .conf files. How's that supposed to work?

I've been exaggerating a bit, I must confess... But, to keep things straight, I really did multihead setup using xrandr in a startup script.

You think mere mortals are going to find startup scripts, not to mention xrandr, easier to figure out than config files?

No. I described this situation because it annoys me. I do not like it at all. Nevertheless I have to cope with it in some way as I can't modify the drivers.

Greets,
Kiste
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Signature · 6 lines
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

#9 lore raw
In reply to Dexter Filmore
Quoted 7 lines · Dexter Filmore

I used to do that with the nvidia tool on nv, but now I'm a little stuck:
No matter what I do X comes up at 60 Hz. I need to do 50 tho so the attached plasma tv doubles it to 100 (at 60 it flickers, plus pulldown problems)

EDID reports a refresh range of 58-62 Hertz which I overrode in xorg.conf. When I feed it a custom mode with xrandr --newmode / --addmode it does 50hz alright, but I can't make it permanent from xorg.conf.

I've always found the Debian XRandR documentation to be good. Check it
out: http://wiki.debian.org/XStrikeForce/HowToRandR12

Apart from all the nvidia-specific options you've got there, you're missing...

Quoted 57 lines

I tried the Preferred Mode option and "ModeValidation" tho I am not sure the latter is nvidia specific.

X log can be found at:
http://www.vaultofsages.de/~dexterf/xorg60hzlog

xorg.conf below.

Can someone have a look and advise, please?

Dex

Section "ServerLayout"

    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"

EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG Electronics LG TV"
    HorizSync       28.0 - 83.0
    VertRefresh     24.0 - 62.0
    Option         "DPMS"
    Modeline "1920x1080_50"  141.50  1920 2032 2232 2544  1080 1083 1088 
1114 -hsync +vsync
    Modeline "1920x1080_24"   63.00  1920 1976 2160 2400  1080 1083 1088 

1098 -hsync +vsync
Option "PreferredMode" "1920x1080_50"
Option "ModeValidation" "DFP-0: AllowNon60HzDFPModes"
EndSection

Quoted 5 lines

Section "Device"

    Identifier     "Device0"
    Driver         "intel"
    VendorName     "intel corp"
    BoardName      "SandyBridge"

Option "Monitor-HDMI2" "Monitor0"

Quoted 14 lines

EndSection

Section "Screen"

    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"

DefaultDepth 24
Option "TwinView" "0"
Option "DynamicTwinView" "0"
Option "FlatPanelProperties" "Scaling = Native"
SubSection "Display"
Depth 24
EndSubSection

Quoted 2 lines

EndSection

You may have noticed from your Xorg.0.log that your monitor section *was* getting read, and the preferred mode *was* getting applied; just to your VGA output. If you associate your Monitor section with the output you want it to apply to, it should work.

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

#10 lore raw
Quoted 22 lines · On Thursday 11 August 2011 01:04:41 Christopher James Halse Rogers wrote:
Quoted 8 lines · Dexter Filmore

I used to do that with the nvidia tool on nv, but now I'm a little stuck:
No matter what I do X comes up at 60 Hz. I need to do 50 tho so the attached plasma tv doubles it to 100 (at 60 it flickers, plus pulldown problems)

EDID reports a refresh range of 58-62 Hertz which I overrode in xorg.conf. When I feed it a custom mode with xrandr --newmode / --addmode it does 50hz alright, but I can't make it permanent from xorg.conf.

I've always found the Debian XRandR documentation to be good. Check it
out: http://wiki.debian.org/XStrikeForce/HowToRandR12

Apart from all the nvidia-specific options you've got there, you're missing...

Quoted 6 lines

Section "Device"

    Identifier     "Device0"
    Driver         "intel"
    VendorName     "intel corp"
    BoardName      "SandyBridge"
Quoted 8 lines

Option "Monitor-HDMI2" "Monitor0"

Quoted 1 line

EndSection

You may have noticed from your Xorg.0.log that your monitor section *was* getting read, and the preferred mode *was* getting applied; just to your VGA output. If you associate your Monitor section with the output you want it to apply to, it should work.

Figured that meanwhile, too. Still comes up at 60. Beats me. I wrote a little script for mplayer to register and set modes depending on the video so that works for me.

Actually I got bigger problems like xv not properly working... and vmware not working on the .39+ kernels intel needs... and debian testing being the only dist with at leat 2.15 and otherwise being a total bitch about almost anything.. and me not getting mplayer to apply the compressor plugins for dts...
Actually, right now about *all* these problems could be solved by moving the machine to Win7.
</wearyrant>

Signature · 6 lines
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

#11 lore raw

On 2011/08/11 03:45 (GMT+0200) Dexter Filmore composed:

Quoted 2 lines

Actually, right now about *all* these problems could be solved by moving the machine to Win7.

Are you sure? Is it possible only HDMI-1 works at 120, and the others at 60? Did you try plugging into any other HDMI ports? Is there a VGA port to try?

Signature · 6 lines
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
#12 lore raw
Quoted 7 lines · On Thursday 11 August 2011 04:16:48 Felix Miata wrote:

On 2011/08/11 03:45 (GMT+0200) Dexter Filmore composed:

Quoted 2 lines

Actually, right now about *all* these problems could be solved by moving the machine to Win7.

Are you sure? Is it possible only HDMI-1 works at 120, and the others at 60? Did you try plugging into any other HDMI ports? Is there a VGA port to try?

There's pretty much one HDMI output on that board, one DVI, one VGA. And why 120? Who would want 120?

Signature · 6 lines
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

#13 lore raw

On 2011/08/11 13:46 (GMT+0200) Dexter Filmore composed:

Quoted 12 lines · On Thursday 11 August 2011 04:16:48 Felix Miata wrote:
Quoted 9 lines

On 2011/08/11 03:45 (GMT+0200) Dexter Filmore composed:

Quoted 2 lines

Actually, right now about *all* these problems could be solved by moving the machine to Win7.

Are you sure? Is it possible only HDMI-1 works at 120, and the others at 60? Did you try plugging into any other HDMI ports? Is there a VGA port to try?

There's pretty much one HDMI output on that board, one DVI, one VGA.

Christopher James Halse Rogers replied to add 'Option "Monitor-HDMI2" "Monitor0"', making me think there actually was a #2 HDMI port.

Quoted 1 line

And why 120? Who would want 120?

That was an error. I meant to type 100 as a consequence of your plasma's 50 doubling, not the 120 that many panel TVs offer.

How exactly did you try to override VertRefresh? I would have tried something like

	VertRefresh 24-51

and if that didn't work, also adding

    Option	"TargetRefreshRate"	"60"

and/or

    Option	"DDC"	"off"

and/or

Option "DefaultModes" "on"

and/or deleting your explicit modelines, allowing the built in modeline generator to do its job.

Signature · 6 lines
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
#14 lore raw

On 2011/08/11 10:10 (GMT-0400) Felix Miata composed:

Quoted 3 lines

and if that didn't work, also adding

      Option	"TargetRefreshRate"	"60"

That was supposed to be

	Option	"TargetRefreshRate"	"50".
Signature · 6 lines
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/