https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #116 from Alex Deucher ---
(In reply to Norbert Pfeiler from comment #115)
> I donât think thatâs it because I tried that with earlier kernel versions
> (I
> also hardcoded the dpcd in several places and that didnât work).
>
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #115 from Norbert Pfeiler ---
(In reply to Christian AÃfalg from comment #114)
> Actually, for me on Arch it works with 4.1.4, too. I tried 4.2 RC5 as well
> and that works too.
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #114 from Christian AÃfalg ---
Actually, for me on Arch it works with 4.1.4, too. I tried 4.2 RC5 as well and
that works too. That's great!
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #113 from Alex Deucher ---
(In reply to Paul Menzel from comment #112)
> Could somebody please reference the corresponding commits, so it can be
> checked, if they are marked to go into the stable Linux kernels?
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #112 from Paul Menzel ---
(In reply to N.Leiten from comment #111)
> At this point I see that problem was fixed with linux kernel 4.2.0-rc4.
Thank you for checking this!
Could somebody please reference the corresponding commits, so
https://bugs.freedesktop.org/show_bug.cgi?id=73530
N.Leiten changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=73530
Norbert Pfeiler changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #109 from Alex Deucher ---
(In reply to N.Leiten from comment #108)
> (In reply to Alex Deucher from comment #102)
> > Created attachment 115802 [details] [review] [review]
> > retry dpcd fetch
> >
> > Does this patch help?
>
> It
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #108 from N.Leiten ---
(In reply to Alex Deucher from comment #102)
> Created attachment 115802 [details] [review]
> retry dpcd fetch
>
> Does this patch help?
It didn't work for me, trying some other changes for now.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #107 from Alex Deucher ---
(In reply to Samir IbradžiÄ from comment #105)
> Here is dmesg with 88, 93, 95 & 97 applied, it looks strange as non-zero
> DPCD values are reported from beginning and they never change.
I don't think
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #106 from Samir IbradžiÄ ---
Created attachment 115838
--> https://bugs.freedesktop.org/attachment.cgi?id=115838=edit
dmesg with debug patches from comments 88, 93, 95, 97 & 99 applied, without
set_rx_power_state
(In reply to
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #105 from Samir IbradžiÄ ---
Created attachment 115837
--> https://bugs.freedesktop.org/attachment.cgi?id=115837=edit
dmesg with debug patches from comments 88, 93, 95 & 97 applied
(In reply to Alex Deucher from comment #97)
>
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #104 from Nicolas Werner ---
(In reply to Alex Deucher from comment #102)
> Created attachment 115802 [details] [review]
> retry dpcd fetch
>
> Does this patch help?
Yep, this one works!
[2.869482] [drm] Initialized drm 1.1.0
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #103 from Nicolas Werner ---
(In reply to Alex Deucher from comment #101)
> Created attachment 115801 [details] [review]
> leave panel power on all th time
>
> (In reply to Nicolas Werner from comment #98)
> Does this patch help
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #102 from Alex Deucher ---
Created attachment 115802
--> https://bugs.freedesktop.org/attachment.cgi?id=115802=edit
retry dpcd fetch
Does this patch help?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #101 from Alex Deucher ---
Created attachment 115801
--> https://bugs.freedesktop.org/attachment.cgi?id=115801=edit
leave panel power on all th time
(In reply to Nicolas Werner from comment #98)
> [5.722365]
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #100 from Nicolas Werner ---
(In reply to Alex Deucher from comment #99)
> Created attachment 115786 [details] [review]
> more debugging
>
> Does this patch help? Please include all the radeon related output. The
> pointers are
https://bugs.freedesktop.org/show_bug.cgi?id=73530
Alex Deucher changed:
What|Removed |Added
Attachment #115782|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #98 from Nicolas Werner ---
(In reply to Alex Deucher from comment #97)
> Created attachment 115782 [details] [review]
> more debugging
>
> Can you attach your dmesg output with the attached patch? Please include
> all the radeon
https://bugs.freedesktop.org/show_bug.cgi?id=73530
Alex Deucher changed:
What|Removed |Added
Attachment #115780|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #96 from Nicolas Werner ---
(In reply to Alex Deucher from comment #95)
> Created attachment 115780 [details] [review]
> add some debugging output
>
> Can you attach the dmesg output with the attached patch?
Seems like we're
https://bugs.freedesktop.org/show_bug.cgi?id=73530
Alex Deucher changed:
What|Removed |Added
Attachment #115774|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #94 from Nicolas Werner ---
(In reply to Alex Deucher from comment #93)
> Created attachment 115778 [details] [review]
> debuging patch
>
> Your dpcd is indeed getting corrupted somehow. I can't see how though. The
> attached
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #93 from Alex Deucher ---
Created attachment 115778
--> https://bugs.freedesktop.org/attachment.cgi?id=115778=edit
debuging patch
Your dpcd is indeed getting corrupted somehow. I can't see how though. The
attached patch (please
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #92 from Nicolas Werner ---
I accidently truncated the dmesg output, here's everything containing drm:
[2.430644] [drm] Initialized drm 1.1.0 20060810
[2.461050] [drm] radeon kernel modesetting enabled.
[2.467555] fb:
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #91 from Nicolas Werner ---
(In reply to Alex Deucher from comment #90)
> (In reply to Nicolas Werner from comment #89)
> > (In reply to Alex Deucher from comment #88)
> > > Created attachment 115774 [details] [review] [review]
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #90 from Alex Deucher ---
(In reply to Nicolas Werner from comment #89)
> (In reply to Alex Deucher from comment #88)
> > Created attachment 115774 [details] [review] [review]
> > add some debugging output
> >
> > Can you attach
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #89 from Nicolas Werner ---
(In reply to Alex Deucher from comment #88)
> Created attachment 115774 [details] [review]
> add some debugging output
>
> Can you attach your dmesg output with this patch attached? It should help
>
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #88 from Alex Deucher ---
Created attachment 115774
--> https://bugs.freedesktop.org/attachment.cgi?id=115774=edit
add some debugging output
Can you attach your dmesg output with this patch attached? It should help
narrow down
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #87 from Samir IbradžiÄ ---
Well, forcing radeon_dp_get_dp_lane_number to return 2 did not help in my case
(https://bugs.freedesktop.org/show_bug.cgi?id=90320) which means the bugs
aren't necessarily related :| My (unpatched) dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #86 from N.Leiten ---
(In reply to Alex Deucher from comment #85)
> (In reply to N.Leiten from comment #84)
> > (In reply to Alex Deucher from comment #83)
> > > Created attachment 115699 [details] [review] [review] [review]
> > >
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #85 from Alex Deucher ---
(In reply to N.Leiten from comment #84)
> (In reply to Alex Deucher from comment #83)
> > Created attachment 115699 [details] [review] [review]
> > possible fix
> >
> > Is the dpcd information always wrong
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #84 from N.Leiten ---
(In reply to Alex Deucher from comment #83)
> Created attachment 115699 [details] [review]
> possible fix
>
> Is the dpcd information always wrong or just sometimes? If it's always
> wrong, the attached patch
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #83 from Alex Deucher ---
Created attachment 115699
--> https://bugs.freedesktop.org/attachment.cgi?id=115699=edit
possible fix
Is the dpcd information always wrong or just sometimes? If it's always wrong,
the attached patch
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #82 from N.Leiten ---
Yes, it seems this bug https://bugs.freedesktop.org/show_bug.cgi?id=90320 is
connected with our BUG.
As for this moment, no changes in SS and DPMS_ON/DPMS_OFF needed to get working
display. It is only a matter
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #81 from Nicolas Werner ---
I can confirm that hacking radeon_dp_get_dp_lane_number to return 2 does yield
a working display (and acceleration), great find!
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #80 from N.Leiten ---
For long time digging radeon drivers I got it working perfectly.
As I mentioned above, the problem is in DP initialization. Somewhere in code
DPCD get NULL'ed and function radeon_dp_get_dp_lane_number in
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #79 from N.Leiten ---
(In reply to Alex Deucher from comment #78)
> Please note that DP is not direct clocked. The link runs at either 1.62 or
> 2.7 Ghz depending on the bandwidth requirements.
Yes, thanks, I figured it out from
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #78 from Alex Deucher ---
Please note that DP is not direct clocked. The link runs at either 1.62 or 2.7
Ghz depending on the bandwidth requirements.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73530
N.Leiten changed:
What|Removed |Added
CC||nickleiten at gmail.com
--- Comment #77 from
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #76 from Nicolas Werner ---
Created attachment 115626
--> https://bugs.freedesktop.org/attachment.cgi?id=115626=edit
dmesg drm debug kernel 3.18
I am also interested in providing help to fix this bug.
I even tried to bisect it,
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #75 from N.Leiten ---
Can anyone provide me with some devel tools to make research of this problem?
I've already tried to play with delays in linux-4.0.1, tried drm-next with no
success.
At this point I have two variants - to
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #74 from Paul Menzel ---
(In reply to Alex Deucher from comment #73)
> (In reply to Benjamin from comment #72)
> > I'm having the same issue, but it seems to be getting worse with newer
> > kernels. I was able to do the
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #73 from Alex Deucher ---
(In reply to Benjamin from comment #72)
> I'm having the same issue, but it seems to be getting worse with newer
> kernels. I was able to do the suspend/resume trick to get a working screen,
> but this seems
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #72 from Benjamin ---
I'm having the same issue, but it seems to be getting worse with newer kernels.
I was able to do the suspend/resume trick to get a working screen, but this
seems to have stopped working with kernel 3.16 and
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #71 from Nicolas Werner ---
Created attachment 109638
--> https://bugs.freedesktop.org/attachment.cgi?id=109638=edit
dmesg with drm/radeon: add locking around atombios scratch space usage
(In reply to Alex Deucher from comment
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #70 from Alex Deucher ---
(In reply to Nicolas Werner from comment #69)
>
> I also have the same problem. (same notebook, so not surprising)
>
> I tried everything you recommended (in comment #65), in order, nothing
> helps. Any
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #69 from Nicolas Werner ---
(In reply to Alex Deucher from comment #65)
> *snip*
>
> In reply to Christian AÃfalg from comment #63)
> > I think / guess that I am having the same issues. I've got the same laptop,
> > running Arch
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #68 from Florentin Raud ---
I also had problem with this laptop.
I fixed it by enabling CSM in the BIOS.
Here is a horrible picture of the bios setting in question: imgur.com/4p6ziEo
I had the issue with mint 16/17
The screen was
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #67 from Christian A?falg ---
@comment65 Thanks for those hints. Trying that will take a couple of days. I
need to figure out how to compile kernel modules in arch first.
Is there a dev (you?) who lives in germany by any chance?
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #66 from Christian A?falg ---
Well, turns out that I may have said that too soon. ;) Gnome does not work
anymore (gnome-session quits right after login), that may be an issue with
gnome 3.14 and catalyst, not 100% sure. For some
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #65 from Alex Deucher ---
(In reply to Christian A?falg from comment #63)
> I think / guess that I am having the same issues. I've got the same laptop,
> running Arch Linux. Mostly, I've been using the proprietary catalyst driver,
>
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #64 from Paul Menzel ---
(In reply to Christian A?falg from comment #63)
> I think / guess that I am having the same issues. I've got the same laptop,
> running Arch Linux. Mostly, I've been using the proprietary catalyst driver,
>
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #63 from Christian A?falg ---
I think / guess that I am having the same issues. I've got the same laptop,
running Arch Linux. Mostly, I've been using the proprietary catalyst driver,
since I never got the free driver working. The
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #62 from Paul Menzel ---
I forgot to thank you for all your help and it makes me sad that I had to come
to the conclusion.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #61 from Paul Menzel ---
I tried to finally get a usable laptop by using FGLRX, but neither 13.12 nor
14.1~beta1.3-1 worked with my Debian installation. That means, GNU/Linux is
unusable with this AMD based laptop and, jugdging from
https://bugs.freedesktop.org/show_bug.cgi?id=73530
Paul Menzel changed:
What|Removed |Added
Summary|Asus U38N: Black screen |Asus U38N: Black screen
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #60 from Paul Menzel ---
Just an update that I get the same behavior with Dave?s drm-fixes branch, which
has Linux 3.14-rc1 included.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #59 from Paul Menzel ---
One other though, could you talk with your appartment to get you an Asus
U38N-C4010 laptop so you can work with it (probably quicker than relying on and
relaying stuff to me) and so you also have it in your
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #58 from Paul Menzel ---
Created attachment 93164
--> https://bugs.freedesktop.org/attachment.cgi?id=93164=edit
Linux kernel log 3.13 with patch from previous comment (200 ?s) after xrandr
--off/--auto cycle
Display worked after
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #57 from Paul Menzel ---
Created attachment 93163
--> https://bugs.freedesktop.org/attachment.cgi?id=93163=edit
Linux kernel log 3.13 with patch from previous comment (200 ?s)
Same behavior, backlight turned on but everything was
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #56 from Paul Menzel ---
In the Linux kernel log after the xrandr cycle and a working display afterward,
the following is shown, which is not shown during start-up.
Feb 1 09:46:31 my_asus_u38n_system kernel: [ 86.286840]
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #55 from Paul Menzel ---
Changing the 400 ?s to 800 ?s and 400 ?s did not change anything.
diff --git a/drivers/gpu/drm/radeon/atombios_dp.c
b/drivers/gpu/drm/radeon/atombios_dp.c
index 676ddf8..3e533bb 100644
---
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #54 from Alex Deucher ---
I think you need to be a vesa member to download the DP specs. There may be
some older copies floating around on the internet. They are also available to
Xorg members if you wanted to become an Xorg
https://bugs.freedesktop.org/show_bug.cgi?id=73530
--- Comment #53 from Paul Menzel ---
So where can I get the specifications about DisplayPort link training? Is it in
[1]?
[1] http://www.vesa.org/vesa-standards/free-standards/
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=73530
Paul Menzel changed:
What|Removed |Added
Summary|Asus U38N: Black screen |Asus U38N: Black screen
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=edit
`/var/log/kern.log` from 3.13 with debug and delay patch
Here are the errors.
[ 297.778990]
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
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
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,
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
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
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
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
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=edit
Picture of another wrong timing(?)
This morning I noticed the same behavior with the same patch.
commit
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=edit
Picture of a wrong timing(?)
With
commit 7424173698775ad90a039d8e00cbee333de536ec
Author: Alex Deucher
Date: Tue
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
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
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:
> >
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
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=edit
possible fix
There's nothing in your logs indicating a link failure when setting up the DP
link. It seems like your
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
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
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
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
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
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
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
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
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
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
1 - 100 of 118 matches
Mail list logo