https://bugs.freedesktop.org/show_bug.cgi?id=105433
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #11 from Thomas R. ---
Created attachment 143978
--> https://bugs.freedesktop.org/attachment.cgi?id=143978&action=edit
Kernel log with debug of 4.19.20+ after patch, including screen reset that does
nothing
--
You are receiving t
https://bugs.freedesktop.org/show_bug.cgi?id=105433
Thomas R. changed:
What|Removed |Added
Attachment #137980|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #9 from Thomas R. ---
I'm unsure if I should file a new bug at this point, but here is an update for
the LTS kernel:
4.19.20 breaks functionality again, now the second screen is reliably dead at
1080p (native resolution). I could bi
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #8 from Thomas R. ---
Apart from bootup, coming back from suspend also has that one screen dead at
first, and also fixable by changing resolution and back.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #7 from Thomas R. ---
I've got news! With 4.19, the first modeset will still disable the second
monitor, including when going into X (without mode change), but after changing
the resolution to something else and back again, it now c
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #6 from Thomas R. ---
Tested with 4.18.5, same behaviour.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.o
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #5 from Thomas R. ---
Hm. Well the current state of this machine is: I got an old working AMD DC
kernel (4.11) that is starting to give me trouble, and nothing current that
works. I'd be willing to bisect from there to current, but t
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #4 from Michel Dänzer ---
(In reply to Thomas R. from comment #3)
> [drm] dce_get_required_clocks_state: clocks unsupported disp_clk 681000
> pix_clk 148500
FWIW, I get the same message with Tonga, with a single DVI connection. I
ha
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #3 from Thomas R. ---
As you can see, I still get
[drm] dce_get_required_clocks_state: clocks unsupported disp_clk 681000 pix_clk
148500
Is there anything I can do to give you more information?
--
You are receiving this mail beca
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #2 from Thomas R. ---
Created attachment 139608
--> https://bugs.freedesktop.org/attachment.cgi?id=139608&action=edit
dmesg of boot, start of X, xrandr with current staging
Still persists in commit dbf4f8b16fde from Tuesday, see d
https://bugs.freedesktop.org/show_bug.cgi?id=105433
--- Comment #1 from Thomas R. ---
Created attachment 137980
--> https://bugs.freedesktop.org/attachment.cgi?id=137980&action=edit
dmesg of boot, start of X and xrandr
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=105433
Bug ID: 105433
Summary: Unreliable Modesetting on Tonga with two DVI Screens
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
13 matches
Mail list logo
