On Thursday 11 August 2011 04:16:48 Felix Miata wrote:
On 2011/08/11 03:45 (GMT+0200) Dexter Filmore composed:
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
On 2011/08/11 10:10 (GMT-0400) Felix Miata composed:
and if that didn't work, also adding
OptionTargetRefreshRate 60
That was supposed to be
Option TargetRefreshRate 50.
--
The wise are known for their understanding, and pleasant
words are persuasive. Proverbs 16:21
On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed:
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
On 10.08.2011 18:21, Felix Miata wrote:
On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed:
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
On 2011/08/10 19:58 (GMT+0200) Oliver Seitz composed:
Felix Miata wrote:
On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed:
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
On 10.08.2011 20:16, Felix Miata wrote:
On 2011/08/10 19:58 (GMT+0200) Oliver Seitz composed:
Felix Miata wrote:
On 2011/08/10 14:15 (GMT+0200) Oliver Seitz composed:
Configuration of software is not done through conf files anymore, it is
done using hardware. If autodetection gives
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
On Fri, 2011-08-05 at 18:25 +0200, 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)
EDID
On Thursday 11 August 2011 01:04:41 Christopher James Halse Rogers wrote:
On Fri, 2011-08-05 at 18:25 +0200, 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
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
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
11 matches
Mail list logo
