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
On Saturday 06 August 201
Now this is downright weird:
as a workaround for the "tearing" bug I decided to use gl2 output for now.
Which works perfectly fine. Got a fast CPU, no problem.
Now I wanted to limit the dynamic range and chainloaded two LADSPA plugins
into my alsa setup (.asoundrc below).
dts tracks now are watc
On 08/05/2011 11:25 AM, Dexter Filmore wrote:
> 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
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.
On Fri, Aug 05, 2011 at 02:03:41AM +0800, Keith Packard wrote:
> On Thu, 4 Aug 2011 17:40:24 +0800, Wu Fengguang
> wrote:
>
> > Right. I actually have this chunk. dmesg shows that in intel_hdmi_detect(),
> >
> > the drm_encoder object is there, however encoder->crtc is NULL at the
> > time.
>
