On Tue, 03 Mar 2015, "Brian J. Murrell" wrote:
> On Tue, 2015-03-03 at 20:40 +0200, Jani Nikula wrote:
>>
>> You'll lose the flicker with LCD,
>
> Even with an analog DSUB input? I only ask again due to the confusion
> below...
Yes. You may get other artefacts due to the D/A-A/D conversions and
On Tue, 2015-03-03 at 20:40 +0200, Jani Nikula wrote:
>
> You'll lose the flicker with LCD,
Even with an analog DSUB input? I only ask again due to the confusion
below...
> but given a digital source
I don't have a digital source. I have a 15-pin DSUB analog source.
> and a
> digital display
On Tue, 03 Mar 2015, "Brian J. Murrell" wrote:
> Slightly off on a tangent... do LCD screens driven through the DSUB have
> the same flicker issues as CRTs or does that somehow get washed out by
> the difference between LCD and CRT technology?
You'll lose the flicker with LCD, but given a digital
On Tue, 2015-03-03 at 15:31 +0200, Ville Syrjälä wrote:
>
> I suppose any increase is good. But personally I just couldn't stand
> anything below 75Hz when I was still using a CRT.
Yeah. 75Hz is what I was using with the nVidia card I replaced with
this new motherboard and Celeron G1840.
Slight
On Tue, Mar 03, 2015 at 08:16:56AM -0500, Brian J. Murrell wrote:
> On Tue, 2015-03-03 at 15:03 +0200, Ville Syrjälä wrote:
> >
> > Oh that's an a CRT monitor you have there. Been a while since I've
> > come across one of those :)
>
> Heh. Yeah. I have been in the market to replace it but no go
On Tue, 2015-03-03 at 15:03 +0200, Ville Syrjälä wrote:
>
> Oh that's an a CRT monitor you have there. Been a while since I've
> come across one of those :)
Heh. Yeah. I have been in the market to replace it but no good enough
deals yet. :-)
> 65Hz on a CRT sounds like a good way to
> get a h
On Mon, Mar 02, 2015 at 03:16:16PM -0500, Brian J. Murrell wrote:
> On Mon, 2015-03-02 at 20:44 +0200, Ville Syrjälä wrote:
> > On Mon, Mar 02, 2015 at 07:07:47PM +0100, Daniel Vetter wrote:
> > > On Mon, Mar 02, 2015 at 11:33:39AM -0500, Brian J. Murrell wrote:
> > > >
> > > > [ 50.508381] [drm
On Mon, 2015-03-02 at 20:44 +0200, Ville Syrjälä wrote:
> On Mon, Mar 02, 2015 at 07:07:47PM +0100, Daniel Vetter wrote:
> > On Mon, Mar 02, 2015 at 11:33:39AM -0500, Brian J. Murrell wrote:
> > >
> > > [ 50.508381] [drm:drm_mode_debug_printmodeline] Modeline 27:"1600x1200"
> > > 0 202500 1600
On Mon, 2015-03-02 at 19:07 +0100, Daniel Vetter wrote:
> On Mon, Mar 02, 2015 at 11:33:39AM -0500, Brian J. Murrell wrote:
> > On Mon, 2015-03-02 at 09:07 +, Chris Wilson wrote:
> >
> > > Can you please attach dmesg with drm.debug=6 on the command line?
> >
> > Please find it attached. I di
On Mon, Mar 02, 2015 at 07:07:47PM +0100, Daniel Vetter wrote:
> On Mon, Mar 02, 2015 at 11:33:39AM -0500, Brian J. Murrell wrote:
> > On Mon, 2015-03-02 at 09:07 +, Chris Wilson wrote:
> >
> > > Can you please attach dmesg with drm.debug=6 on the command line?
> >
> > Please find it attached
On Mon, 2015-03-02 at 09:07 +, Chris Wilson wrote:
>
> Gut feeling is that this is related to HDMIv1.2 versus later.
I should have mentioned, the monitor that is not getting it's
1600x1200@75Hz timing picked up is on the D-Sub connector, not HDMI.
> For reference the loop in pipe is bug 8534
On Sun, Mar 01, 2015 at 02:12:16PM -0500, Brian J. Murrell wrote:
> I have a dual-head set up here which I've recently changed the
> motherboard out and with it, removed an nVidia GT210 and replaced it
> with the on-board graphics that came on this:
>
> CPU: Intel(R) Celeron(R) CPU G1840 @ 2.80GHz
I have a dual-head set up here which I've recently changed the
motherboard out and with it, removed an nVidia GT210 and replaced it
with the on-board graphics that came on this:
CPU: Intel(R) Celeron(R) CPU G1840 @ 2.80GHz (Family: 6, Model: 60, Stepping: 3)
The monitors have remained the same th
13 matches
Mail list logo
