https://bugzilla.kernel.org/show_bug.cgi?id=71461
Tom Yan changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #31 from Tom Yan ---
(In reply to Alex Deucher from comment #29)
> Can you also try the attached patch which reverses the hpd polarity?
Unfortunately the patch doesn't work (with or without the dp-specific code).
Maybe you should tr
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #30 from Tom Yan ---
Created attachment 131971
--> https://bugzilla.kernel.org/attachment.cgi?id=131971&action=edit
vbios
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #29 from Alex Deucher ---
Created attachment 131821
--> https://bugzilla.kernel.org/attachment.cgi?id=131821&action=edit
reverse hpd polarity
It sounds like your board by have the hpd pin polarity reversed (so plug events
looks like
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #28 from Tom Yan ---
(In reply to Alex Deucher from comment #24)
> In your case we need to find out why it's not working properly for you. You
> mentioned that it works properly in the console but not in X. That sounds
> like maybe y
https://bugzilla.kernel.org/show_bug.cgi?id=71461
Tom Yan changed:
What|Removed |Added
Kernel Version|3.13.5 |3.13.8
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #27 from Tom Yan ---
(In reply to Alex Deucher from comment #25)
> (In reply to Tom Yan from comment #23)
> > Btw, is it something not implemented yet or a bug, that it won't do the
> > modesetting later if no device plugged before boo
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #26 from Tom Yan ---
(In reply to Alex Deucher from comment #24)
> It works for the vast majority of users and removing it would break unplug
> and replug of DP displays. Without that code you would have to manually
> disable and re-e
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #25 from Alex Deucher ---
(In reply to Tom Yan from comment #23)
> Btw, is it something not implemented yet or a bug, that it won't do the
> modesetting later if no device plugged before boot? Why does it have to go
> 1024x768? I mean,
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #24 from Alex Deucher ---
(In reply to Tom Yan from comment #22)
> Do you have any case that the code would do something positive? Or
> ultimately, would you consider removing the code upstream?
It works for the vast majority of users
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #23 from Tom Yan ---
Btw, is it something not implemented yet or a bug, that it won't do the
modesetting later if no device plugged before boot? Why does it have to go
1024x768? I mean, why does it require a device to initialize "dynam
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #22 from Tom Yan ---
Do you have any case that the code would do something positive? Or ultimately,
would you consider removing the code upstream?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #21 from Alex Deucher ---
(In reply to Tom Yan from comment #20)
> I did some more tests. Seems to me that the blank occured with
> dis/reconnection in X is also related to DPMS toggling. Any similar code in
> ddx driver I can try remo
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #20 from Tom Yan ---
I did some more tests. Seems to me that the blank occured with dis/reconnection
in X is also related to DPMS toggling. Any similar code in ddx driver I can try
removing? Since in console everything is fine so far :
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #19 from Tom Yan ---
(In reply to Alex Deucher from comment #18)
> It's required to re-establish the DP link if you physically disconnect and
> reconnect an active display since DP requires link training while other
> digital links do
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #18 from Alex Deucher ---
(In reply to Tom Yan from comment #16)
> I tried to remove the DisplayPort-specific code in
> radeon_connector_hotplug() of radeon_connector.c and everything seems to
> work like a charm. What is the code supp
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #17 from Tom Yan ---
One thing to add, unplugging it physically in X still makes it blank. It
happens no matter the code is removed or not.
Also, HDMI doesn't work all time yet, seems that if the TV is powered off and
it goes into DPM
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #16 from Tom Yan ---
I tried to remove the DisplayPort-specific code in radeon_connector_hotplug()
of radeon_connector.c and everything seems to work like a charm. What is the
code supposed to do actually?
Though, btw, it seems that o
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #15 from Tom Yan ---
(In reply to Tom Yan from comment #14)
> The problem with DisplayPort seems to related to DPMS. All I need to do to
> get back the display is to make sure that there is a state change after the
> monitor is turned
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #14 from Tom Yan ---
The problem with DisplayPort seems to related to DPMS. All I need to do to get
back the display is to make sure that there is a state change after the monitor
is turned on again.
--
You are receiving this mail be
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #13 from Tom Yan ---
Unfortunately, no.
Yet it seems that now (with kernel 3.13.6) disconnecting HDMI and DVI doesn't
shows a problem anymore. Only DisplayPort still got issue. (Though, if I don't
have anything connected before boot,
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #12 from Alex Deucher ---
Does booting with radeon.runpm=0 on the kernel command line in grub help?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #11 from Tom Yan ---
One of my other machines with an HD6450 shows similar issue. I unplugged the
DVI connector before boot up and I can't get any display when I connect it
again afterwards.
--
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #10 from Tom Yan ---
Switching modes with xrandr can also bring back display.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #9 from Tom Yan ---
Created attachment 127921
--> https://bugzilla.kernel.org/attachment.cgi?id=127921&action=edit
xorg log when not working
Sorry I was doing stupid thing. Here is the xorg log captured after I turn the
monitor off
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #8 from Tom Yan ---
By "with HDMI" I mean only HDMI is connected.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #7 from Tom Yan ---
All the above outputs were captured when only DisplayPort is connected. Similar
sympton were observed with HDMI.
Also, sometimes toggling others connectors afterwards makes it work again. Like
if HDMI is plugged in
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #6 from Tom Yan ---
Created attachment 127911
--> https://bugzilla.kernel.org/attachment.cgi?id=127911&action=edit
Xorg.0.log
Maybe it's because I have some misconcept about xorg log, it doesn't seem to
vary between cases. Anyway th
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #5 from Tom Yan ---
Created attachment 127901
--> https://bugzilla.kernel.org/attachment.cgi?id=127901&action=edit
dmesg (monitor on when boot, turn off afterwards)
`diff on_at_start off_afterwards`
858a859
> [ 49.713776] pci_pm_r
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #4 from Tom Yan ---
Created attachment 127891
--> https://bugzilla.kernel.org/attachment.cgi?id=127891&action=edit
dmesg (monitor on when boot, working before off)
--
You are receiving this mail because:
You are watching the assign
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #3 from Tom Yan ---
Created attachment 127881
--> https://bugzilla.kernel.org/attachment.cgi?id=127881&action=edit
dmesg (monitor off when boot, not work when turn on afterwards)
--
You are receiving this mail because:
You are watc
https://bugzilla.kernel.org/show_bug.cgi?id=71461
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #2 fr
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #1 from Tom Yan ---
The card has 4 connectors: 1 HDMI, 1 DisplayPort and 2 DVI
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71461
Tom Yan changed:
What|Removed |Added
Summary|monitor doesn't get |monitor doesn't get
|detected
34 matches
Mail list logo
