https://bugs.freedesktop.org/show_bug.cgi?id=48772
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #17 from Andy Pillip ---
This is not a cable issue.
I just figured out that for me the issue only occurs on a dual screen setup.
Now I'm running the 3840 resolution on my external screen while switching off
the internal one â with
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #16 from Grigori Goronzy ---
Note that this could also be a cable issue. Bad quality DP cables are prone to
cause various display issues. I once had a bad cable that even had trouble
driving standard 1080p without dropouts. So maybe j
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #15 from Andy Pillip ---
I do have the same issue on Gnome 3, Wayland, F22 with an Intel Graphics Chip.
On 3840 I see the flashes quite often, and the screen sometimes turns off
completely.
On 2560 it's less flashes, and on 1920 the
https://bugs.freedesktop.org/show_bug.cgi?id=48772
Alex Deucher changed:
What|Removed |Added
Attachment #60473|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=48772
Alex Deucher changed:
What|Removed |Added
Attachment #60472|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=48772
Alex Deucher changed:
What|Removed |Added
Attachment #60473|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=48772
Alex Deucher changed:
What|Removed |Added
Attachment #60472|text/x-log |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #14 from Tvrtko Ursulin 2012-04-23
00:52:30 PDT ---
Created attachment 60473
--> https://bugs.freedesktop.org/attachment.cgi?id=60473
DRM related kernel messages
Is this what you had in mind or would you like something more?
--
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #13 from Tvrtko Ursulin 2012-04-23
00:49:03 PDT ---
Created attachment 60472
--> https://bugs.freedesktop.org/attachment.cgi?id=60472
Xorg log running 2560x1440
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #14 from Tvrtko Ursulin 2012-04-23
00:52:30 PDT ---
Created attachment 60473
--> https://bugs.freedesktop.org/attachment.cgi?id=60473
DRM related kernel messages
Is this what you had in mind or would you like something more?
--
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #13 from Tvrtko Ursulin 2012-04-23
00:49:03 PDT ---
Created attachment 60472
--> https://bugs.freedesktop.org/attachment.cgi?id=60472
Xorg log running 2560x1440
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #12 from Alex Deucher 2012-04-20 12:01:54 PDT
---
Can you attach the xorg log and dmesg output with the DP monitor attached?
What's the modeline for the 2560x1440 mode?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #11 from Alex Deucher 2012-04-20 08:19:54 PDT
---
(In reply to comment #9)
>
> I never really understood this problem, not since the days of sdr. Single
> channel ddr3-1066 provides roughly 8 times the raw bandwidth of what a
> 2560
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #12 from Alex Deucher 2012-04-20 12:01:54 PDT ---
Can you attach the xorg log and dmesg output with the DP monitor attached?
What's the modeline for the 2560x1440 mode?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.c
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #10 from Tvrtko Ursulin 2012-04-20
03:43:13 PDT ---
Does the driver know it's memory bandwidth so it could remove modes it cannot
drive from the list?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
-
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #11 from Alex Deucher 2012-04-20 08:19:54 PDT ---
(In reply to comment #9)
>
> I never really understood this problem, not since the days of sdr. Single
> channel ddr3-1066 provides roughly 8 times the raw bandwidth of what a
> 2560x
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #10 from Tvrtko Ursulin 2012-04-20
03:43:13 PDT ---
Does the driver know it's memory bandwidth so it could remove modes it cannot
drive from the list?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
-
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #9 from Roland Scheidegger 2012-04-18
14:21:14 PDT ---
(In reply to comment #8)
> That's the max theoretical mode supported by the chip. Whether or not you can
> drive a monitor that big probably depends on the type and speed of dra
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #9 from Roland Scheidegger 2012-04-18 14:21:14
PDT ---
(In reply to comment #8)
> That's the max theoretical mode supported by the chip. Whether or not you can
> drive a monitor that big probably depends on the type and speed of dra
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #8 from Alex Deucher 2012-04-17 06:18:13 PDT
---
(In reply to comment #7)
> Where does this finding leads us? According to the specifications
> (http://www.amd.com/us/products/notebook/graphics/amd-radeon-6000m/amd-radeon-6300m/pages
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #7 from Tvrtko Ursulin 2012-04-17
03:20:39 PDT ---
(In reply to comment #3)
> Does the proprietary driver work ok with that monitor?
It doesn't. In fact it is even worse than the open source driver which works OK
in 1920x1200, while
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #8 from Alex Deucher 2012-04-17 06:18:13 PDT ---
(In reply to comment #7)
> Where does this finding leads us? According to the specifications
> (http://www.amd.com/us/products/notebook/graphics/amd-radeon-6000m/amd-radeon-6300m/pages/
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #7 from Tvrtko Ursulin 2012-04-17
03:20:39 PDT ---
(In reply to comment #3)
> Does the proprietary driver work ok with that monitor?
It doesn't. In fact it is even worse than the open source driver which works OK
in 1920x1200, while
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #6 from Alex Deucher 2012-04-16 09:11:15 PDT
---
(In reply to comment #5)
> fbdev is linear so that should be equivalent to running X with tiling
> disabled;
> so need to test with tiling disabled.
so NO need to test with tiling d
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #5 from Alex Deucher 2012-04-16 09:10:51 PDT
---
(In reply to comment #4)
>
> > > Is testing with tiling disabled relevant given the problem happens also
> > > without
> > > X running?
> >
> > That should be equivalent.
>
> Not s
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #4 from Tvrtko Ursulin 2012-04-16
08:49:59 PDT ---
(In reply to comment #3)
> (In reply to comment #2)
> > radeon.disp_priority=2 seems to have no effect. Perhaps it decreased the
> > frequency between screen blackouts, but my sample
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #3 from Alex Deucher 2012-04-16 08:43:47 PDT
---
(In reply to comment #2)
> radeon.disp_priority=2 seems to have no effect. Perhaps it decreased the
> frequency between screen blackouts, but my sample size is small and randomness
> o
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #2 from Tvrtko Ursulin 2012-04-16
08:30:32 PDT ---
radeon.disp_priority=2 seems to have no effect. Perhaps it decreased the
frequency between screen blackouts, but my sample size is small and randomness
of the timings makes me uneasy
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #6 from Alex Deucher 2012-04-16 09:11:15 PDT ---
(In reply to comment #5)
> fbdev is linear so that should be equivalent to running X with tiling
> disabled;
> so need to test with tiling disabled.
so NO need to test with tiling di
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #5 from Alex Deucher 2012-04-16 09:10:51 PDT ---
(In reply to comment #4)
>
> > > Is testing with tiling disabled relevant given the problem happens also
> > > without
> > > X running?
> >
> > That should be equivalent.
>
> Not su
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #4 from Tvrtko Ursulin 2012-04-16
08:49:59 PDT ---
(In reply to comment #3)
> (In reply to comment #2)
> > radeon.disp_priority=2 seems to have no effect. Perhaps it decreased the
> > frequency between screen blackouts, but my sample
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #3 from Alex Deucher 2012-04-16 08:43:47 PDT ---
(In reply to comment #2)
> radeon.disp_priority=2 seems to have no effect. Perhaps it decreased the
> frequency between screen blackouts, but my sample size is small and randomness
> of
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #2 from Tvrtko Ursulin 2012-04-16
08:30:32 PDT ---
radeon.disp_priority=2 seems to have no effect. Perhaps it decreased the
frequency between screen blackouts, but my sample size is small and randomness
of the timings makes me uneasy
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #1 from Alex Deucher 2012-04-16 08:13:28 UTC ---
Sounds like display bandwidth/watermark issues. Does booting with
radeon.disp_priority=2 on the kernel command line in grub help? Also does
disabling tiling help?
--
Configure bugma
https://bugs.freedesktop.org/show_bug.cgi?id=48772
--- Comment #1 from Alex Deucher 2012-04-16 08:13:28 UTC
---
Sounds like display bandwidth/watermark issues. Does booting with
radeon.disp_priority=2 on the kernel command line in grub help? Also does
disabling tiling help?
--
Configure bugm
36 matches
Mail list logo
