https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #52 from Paul Menzel ---
Created attachment 93042
--> https://bugs.freedesktop.org/attachment.cgi?id=93042&action=edit
`/var/log/kern.log` from 3.13 with debug and delay patch
Here are the errors.
[ 297.778990] [drm:radeon_dp
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #51 from Paul Menzel ---
I tried Linux 3.13 with the patch below and I could not get the display to work
at all with the following script.
while true; do xrandr --output eDP --off && xrandr --output eDP --auto &&
sleep 4; done
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #50 from Paul Menzel ---
That line was the same testing the same built Linux kernel a second time.
[drm:radeon_fixup_lvds_native_mode], Native mode: 1920x1080-138780
It also took one xrandr off/auto cycle to get the display work
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #49 from Paul Menzel ---
With the debug patch applied to your 3.14-wip branch (based on 3.13-rc4), the
following is printed by the Linux kernel.
[ 12.005985] [drm:radeon_fixup_lvds_native_mode], Native mode:
1920x1080-138780
T
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #48 from Alex Deucher ---
You might try adjusting the delays in radeon_dp_link_train() and the functions
it calls. Some panels are really picky about the timing during the training
sequence.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #47 from Paul Menzel ---
Looking at the panel/monitor CMN 1343, I found a list with more information
[1].
Chi Mei Innolux N133HSE-EA1
Asus U38N(-C4010H)
Asus Zenbook UX31A, UX32VD
Clevo W230ST
1920x1080, IPS, matt
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #46 from Paul Menzel ---
Current status is that I mostly get it to work after the first xrandr off/auto
cycle, meaning 80 % of the cases.
The other 19 % of the cases it takes longer and in 1 % it works right away.
I still do not und
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #45 from Paul Menzel ---
Anything I should try/look at over the weekend?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #44 from Alex Deucher ---
(In reply to comment #43)
> Would other tests like using a different modeline 1680x1050 be useful? Can
> that be set on the Linux command line? Reading `/sbin/modinfo radeon` I
> could not find the parameter.
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #43 from Paul Menzel ---
Would other tests like using a different modeline 1680x1050 be useful? Can that
be set on the Linux command line? Reading `/sbin/modinfo radeon` I could not
find the parameter.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #42 from Paul Menzel ---
Do you still need the debugging output of the native(?) mode lines and want me
to apply your patch and test it?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next p
https://bugs.freedesktop.org/show_bug.cgi?id=73530
Alex Deucher changed:
What|Removed |Added
Attachment #92264|text/plain |image/jpeg
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #41 from Paul Menzel ---
Created attachment 92264
--> https://bugs.freedesktop.org/attachment.cgi?id=92264&action=edit
Picture of another wrong timing(?)
This morning I noticed the same behavior with the same patch.
commit 7424173
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #40 from Paul Menzel ---
Created attachment 92262
--> https://bugs.freedesktop.org/attachment.cgi?id=92262&action=edit
Picture of a wrong timing(?)
With
commit 7424173698775ad90a039d8e00cbee333de536ec
Author: Alex Deucher
Date:
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #39 from Paul Menzel ---
Once the display works, it seems to work always during consecutive off/on
cycles.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML att
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #38 from Paul Menzel ---
Is there a way to look at the Windows driver to know what the timing should be?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attac
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #37 from Paul Menzel ---
(In reply to comment #36)
> (In reply to comment #35)
[?]
> > I've also pushed a branch with some other DP related patches that might help
> > if you want to try it:
> > http://cgit.freedesktop.org/~agd5f/li
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #36 from Paul Menzel ---
(In reply to comment #35)
> Created attachment 92230 [details] [review]
> possible fix
>
> There's nothing in your logs indicating a link failure when setting up the
> DP link. It seems like your panel is ju
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #35 from Alex Deucher ---
Created attachment 92230
--> https://bugs.freedesktop.org/attachment.cgi?id=92230&action=edit
possible fix
There's nothing in your logs indicating a link failure when setting up the DP
link. It seems like
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #34 from Paul Menzel ---
No idea, if it?ll give a clue, but often the display did not work even after
turning it off and on more than five times. Blindly logging out again, which
closes the X session, goes to tty1 and then back to the
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #33 from Paul Menzel ---
Only testing patch 2/2 also did not fix the issue. The display was just black
and I had to do the `xrandr` dance to get it to work.
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #32 from Paul Menzel ---
Applying both patches 1/2 and 2/2 did not help anything with the situation. I
had to run `xrandr --output eDP --off` and `xrandr --output eDP --auto` three
times to get the display to work.
--
You are receiv
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #31 from Paul Menzel ---
Sorry, I missed the two patches. I?ll test them now.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #30 from Alex Deucher ---
Have you tested the patch in attachment 92172? Does it help at all?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #29 from Paul Menzel ---
Do you want me to test something else or can we assume that no Linux kernel
patch is needed and the display has to be dealt with? As commented, turning it
off and on does not always get it to work.
--
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #28 from Paul Menzel ---
I was able to get the display to work with Debian?s Linux kernel 3.12.6 (with
none of your patches applied) using `xrandr --output eDP --off` and `xrandr
--output eDP --auto`. So it looks like no patch is need
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #27 from Paul Menzel ---
So turning the display off and on with xrandr or xset does not always work even
with the patched Linux kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next pa
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #26 from Alex Deucher ---
(In reply to comment #25)
> Alex, thank you for the quick replies!
>
> When doing the tests, should I save certain logs? Do you want me to pass
> special debug parameters?
I don't need any logs at the momen
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #25 from Paul Menzel ---
Alex, thank you for the quick replies!
When doing the tests, should I save certain logs? Do you want me to pass
special debug parameters?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #24 from Alex Deucher ---
(In reply to comment #23)
> Turning the display off and on again, the display works fine.
>
> $ xrandr --output eDP --off
> $ xrandr --output eDP --auto
Does that work without patches or only with o
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #23 from Paul Menzel ---
Turning the display off and on again, the display works fine.
$ xrandr --output eDP --off
$ xrandr --output eDP --auto
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #22 from Alex Deucher ---
Does forcing a dpms cycle help? e.g.,
sleep 5; xset dpms force off
and then after the monitor blanks, move the mouse to trigger a wake up.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #21 from Alex Deucher ---
(In reply to comment #20)
> I guess I spoke too soon. :( Now starting the system a second time, the
> display is black again with the backlight enabled. I was able to login
> blindly into GNOME using GDM, so
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #20 from Paul Menzel ---
I guess I spoke too soon. :( Now starting the system a second time, the display
is black again with the backlight enabled. I was able to login blindly into
GNOME using GDM, so X is running. I?ll post the log f
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #19 from Alex Deucher ---
Created attachment 92172
--> https://bugs.freedesktop.org/attachment.cgi?id=92172&action=edit
patch 2/2
Patch 2/2. The actual fix for this bug.
--
You are receiving this mail because:
You are the assign
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #18 from Alex Deucher ---
Created attachment 92171
--> https://bugs.freedesktop.org/attachment.cgi?id=92171&action=edit
patch 1/2
Can you try the two attached patches and see if they help? Patch 2/2 is the
actual fix. If you have
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #17 from Alex Deucher ---
(In reply to comment #16)
> (In reply to comment #15)
> > (In reply to comment #13)
> > > One other question, how does MS Windows figure out the correct modelines
> > > when the EDID of the monitor is incorre
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #16 from Paul Menzel ---
(In reply to comment #15)
> (In reply to comment #13)
> > One other question, how does MS Windows figure out the correct modelines
> > when the EDID of the monitor is incorrect? (I did not try the shipped
> >
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #15 from Alex Deucher ---
(In reply to comment #13)
> One other question, how does MS Windows figure out the correct modelines
> when the EDID of the monitor is incorrect? (I did not try the shipped
> Windows 8 at all but assume it wo
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #14 from Alex Deucher ---
(In reply to comment #9)
> Applying your patch to disable ss to Linux 3.13-rc8 worked. The monitor
> displays now something even with KMS. Thanks!
>
> It could still be that something else fixed it in Linux
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #13 from Paul Menzel ---
One other question, how does MS Windows figure out the correct modelines when
the EDID of the monitor is incorrect? (I did not try the shipped Windows 8 at
all but assume it works.)
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #12 from Paul Menzel ---
Alex, please tell me if you still need the Linux output with your second patch
applied or anything else. Thanks again!
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #11 from Paul Menzel ---
Created attachment 92128
--> https://bugs.freedesktop.org/attachment.cgi?id=92128&action=edit
X server log file with Linux 3.13-rc8-disable-ss
I attached an USB mouse later on.
--
You are receiving this m
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #10 from Paul Menzel ---
Created attachment 92126
--> https://bugs.freedesktop.org/attachment.cgi?id=92126&action=edit
Linux kernel 3.13-rc8+-disable-ss ring buffer (`dmesg`)
Some seconds seem to be missing as the ring buffer overf
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #9 from Paul Menzel ---
Applying your patch to disable ss to Linux 3.13-rc8 worked. The monitor
displays now something even with KMS. Thanks!
It could still be that something else fixed it in Linux 3.13-rc8 which was not
yet in 3.12.
https://bugs.freedesktop.org/show_bug.cgi?id=73530
Paul Menzel changed:
What|Removed |Added
CC||paulepanter at users.sourcefor
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #7 from Alex Deucher ---
Created attachment 92049
--> https://bugs.freedesktop.org/attachment.cgi?id=92049&action=edit
debugging output
Can you also attach the dmesg output with this patch applied?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #6 from Alex Deucher ---
Created attachment 92048
--> https://bugs.freedesktop.org/attachment.cgi?id=92048&action=edit
disable ss
Does this kernel patch help?
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #5 from Alex Deucher ---
It looks like their are also two modes in your EDID for your panel:
[ 1248.508] (II) RADEON(0): Supported detailed timing:
[ 1248.508] (II) RADEON(0): clock: 138.8 MHz Image Size: 282 x 165 mm
[ 1248.50
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #4 from Alex Deucher ---
(In reply to comment #2)
> Created attachment 91918 [details]
> Linux kernel ring buffer (`dmesg`)
>
> Please note the Linux kernel command line, which has `radeon.modeset=0`,
> `drm.debug=14` and `acpi_osi=L
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #3 from Paul Menzel ---
Created attachment 91919
--> https://bugs.freedesktop.org/attachment.cgi?id=91919&action=edit
X server log file
X server log after reloading the Radeon module with modesetting enabled and
then restarting the
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #2 from Paul Menzel ---
Created attachment 91918
--> https://bugs.freedesktop.org/attachment.cgi?id=91918&action=edit
Linux kernel ring buffer (`dmesg`)
Please note the Linux kernel command line, which has `radeon.modeset=0`,
`drm.
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #1 from Paul Menzel ---
*** Bug 73529 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed.
53 matches
Mail list logo