On Thu, May 14, 2015 at 11:52 PM, Dave Jones wrote:
> On Thu, May 14, 2015 at 09:49:52AM -0400, Alex Deucher wrote:
> > On Tue, May 12, 2015 at 8:04 PM, Dave Jones
> wrote:
> > > On Mon, May 11, 2015 at 03:59:55PM -0400, Alex Deucher wrote:
> > >
> > > > > I tried tweaking the delays in
>
On 15.05.2015 12:52, Dave Jones wrote:
>
> The only remaining problem is there are some visible glitches, mostly
> noticable
> while scrolling a terminal.
What kind of glitches? If it's tearing, with current xf86-video-ati Git
you can try Option "TearFree".
--
Earthling Michel Dänzer
On Fri, May 15, 2015 at 06:16:59PM +0900, Michel Dänzer wrote:
> On 15.05.2015 12:52, Dave Jones wrote:
> >
> > The only remaining problem is there are some visible glitches, mostly
> > noticable
> > while scrolling a terminal.
>
> What kind of glitches? If it's tearing, with current xf8
On Thu, May 14, 2015 at 09:49:52AM -0400, Alex Deucher wrote:
> On Tue, May 12, 2015 at 8:04 PM, Dave Jones
> wrote:
> > On Mon, May 11, 2015 at 03:59:55PM -0400, Alex Deucher wrote:
> >
> > > > I tried tweaking the delays in
> > drm_dp_link_train_clock_recovery_delay, without any noticab
On Thu, May 14, 2015 at 09:49:52AM -0400, Alex Deucher wrote:
> On Tue, May 12, 2015 at 8:04 PM, Dave Jones
> wrote:
> > On Mon, May 11, 2015 at 03:59:55PM -0400, Alex Deucher wrote:
> >
> > > > I tried tweaking the delays in
> > drm_dp_link_train_clock_recovery_delay, without any noticab
On Tue, May 12, 2015 at 8:04 PM, Dave Jones wrote:
> On Mon, May 11, 2015 at 03:59:55PM -0400, Alex Deucher wrote:
>
> > > I tried tweaking the delays in drm_dp_link_train_clock_recovery_delay,
> without any noticable
> > > difference. Is there something else I can try to make it try harder
>
On Mon, May 11, 2015 at 03:59:55PM -0400, Alex Deucher wrote:
> > I tried tweaking the delays in drm_dp_link_train_clock_recovery_delay,
> > without any noticable
> > difference. Is there something else I can try to make it try harder
> > before giving up?
> >
>
> Can you attach your bo
On Mon, May 11, 2015 at 03:59:55PM -0400, Alex Deucher wrote:
> Can you attach your boot dmesg output with drm.debug=0xf set?
Strange, haven't seen this happen before.
[8.437431] [drm:drm_calc_vbltimestamp_from_scanoutpos] crtc 5: Noop due to
uninitialized mode.
[8.437433] [drm:drm_upd
On Mon, May 11, 2015 at 03:59:55PM -0400, Alex Deucher wrote:
> > > > The link training with the monitor seems to fail periodically. You
> > may have to play with the timing in the link training sequence. It looks
> > like you also have some power management related issues. Does booting
On Mon, May 11, 2015 at 2:40 PM, Dave Jones wrote:
> On Fri, May 08, 2015 at 11:40:55AM -0400, Dave Jones wrote:
> > On Fri, May 08, 2015 at 01:23:59PM +, Deucher, Alexander wrote:
>
> > > > I just bought a new radeon (1002:682c), to pair with my shiny new
> displayport
> > > > monitor.
On Fri, May 08, 2015 at 11:40:55AM -0400, Dave Jones wrote:
> On Fri, May 08, 2015 at 01:23:59PM +, Deucher, Alexander wrote:
> > > I just bought a new radeon (1002:682c), to pair with my shiny new
> displayport
> > > monitor.
> > > It shows a display during through the BIOS POST, and
> -Original Message-
> From: Dave Jones [mailto:davej at codemonkey.org.uk]
> Sent: Thursday, May 07, 2015 7:48 PM
> To: dri-devel at lists.freedesktop.org
> Cc: Deucher, Alexander; Koenig, Christian
> Subject: Radeon Verde displayport failure.
>
> I just bought
, Alexander; Koenig, Christian
> > Subject: Radeon Verde displayport failure.
> >
> > I just bought a new radeon (1002:682c), to pair with my shiny new
> > displayport
> > monitor.
> > It shows a display during through the BIOS POST, and grub, but when the
I just bought a new radeon (1002:682c), to pair with my shiny new displayport
monitor.
It shows a display during through the BIOS POST, and grub, but when the kernel
starts up, it's a coin toss whether or not I get anything.
Sometimes it just goes straight into power saving.
When I do get somethi
14 matches
Mail list logo
