** Changed in: xserver-xorg-driver-ati
Status: Confirmed => Unknown
** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #657
https://gitlab.freedesktop.org/drm/amd/issues/657
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Christopher, I believe Wayland is a default display server on Ubuntu nowadays
(at least in 17.10).
As it is some hassle for me to set up the test environment and mess around with
all the cables again, I would like to understand, why the logs I have enclosed
are not good enough.
** Changed in: x
Adrian, you should be able to boot into xorg instead of Wayland via the
login screen.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Christopher:
1) I used to have radeon.dpm=1 to save power (although, I don't have
numbers how much better it is with respect to no parameter).
2) I can't.
My Ubuntu 17.10 (and according to my knowledge it's a trend in the community)
runs with Wayland, not Xorg so there is not Xorg server with i
Adrian:
1) To clarify, do you need to use radeon.dpm=1 for a reason or are you
just testing it to see if it does anything different?
2) While using the latest mainline kernel, please attach dmesg and xorg
in their entierty only for the scenario of when using radeon.mst=1, and
please don't rename
Ubuntu 17.10 with kernel 4.16-rc1, radeon.mst=1, extended display in
GUI.
The screens chained by MST DisplayPort are seen properly as separate
screens. Build screen is seen in the GUI and although enabled there,
remains blank. Periodically (~5s) screens become blank for ~1s.
** Attachment added:
Ubuntu 17.10 with kernel 4.16-rc1, radeon.mst=1 radeon.dpn=1, extended
display in GUI.
The screens chained by MST DisplayPort are seen properly as separate
screens. Build screen is seen in the GUI and although enabled there,
remains blank. Periodically (~5s) screens become blank for ~1s.
** Attac
Ubuntu 17.10 with kernel 4.16-rc1, no kernel parameters, extended
display in GUI.
The screens chained by MST DisplayPort mirror the view and are visible
as a single screen. Build screen is seen as a second screen and works.
No picture blinking.
** Attachment added: "journal_no_param.log"
htt
Ubuntu 17.10 with kernel 4.16-rc1, no kernel parameters: the screens
chained by MST DisplayPort mirror picture, visible as a single screen
** Attachment added: "journal_no_param.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1509997/+attachment/5054160/+files/journa
Adrian:
>"I have tried Ubuntu 17.10 with the upstream kernels (4.15.2 and
4.16-rc1) and both behave similarly:"
Please attach both your dmesg and xorg logs after reproducing the
graphical glitching on the latest mainline kernel. Without logs,
developers can't do anything.
>"no kernel parameters:
Christopher:
I have tried Ubuntu 17.10 with the upstream kernels (4.15.2 and 4.16-rc1) and
both behave similarly:
no kernel parameters: screens chained by MST DisplayPort mirror picture,
visible as a single screen
radeon.mst=1 : screens chained by MST DisplayPort work properly (seen
as separate
Adrian:
1) Presently, to test 4.15 in http://cdimage.ubuntu.com/daily-
live/current/ you would have to install it (not test a live environment)
and enable the Proposed repository.
An alternative is test the latest upstream kernel (now 4.16-rc1) via
https://wiki.ubuntu.com/Kernel/MainlineBuilds .
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509997
Title:
1002:6821 Graphical issues when radeon MST enabled
To manage notifications about this bug go to:
https://bugs.laun
Christopher, I tested the daily build of Ubuntu 18.04 from your link and it
does not work - the problem is still there.
What I noticed, the daily build was based on kernel 4.13. I thought 18.04 will
be based on kernel 4.15 (Chris mentioned the problem is solved for him in this
particular kernel
Adrian, to see if this is already resolved in ubuntu, could you please
test http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results?
** Changed in: xserver-xorg-video-ati (Ubuntu)
Importance: High => Low
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Confirmed =>
** Tags removed: latest-bios-1.12
** Tags added: bios-outdated-1.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509997
Title:
1002:6821 Graphical issues when radeon MST enabled
To manage notific
DisplayPort MST seems to work with open-source drivers on Ubuntu 16.04.3
after installing HWE + latest kernel (4.15.2). No kernel parameters
needed, it just works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Tags removed: 4.13.0-16-lowlatency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509997
Title:
1002:6821 Graphical issues when radeon MST enabled
To manage notifications about this bug go to:
h
Adrian:
1) Regarding tags, while artful is one that is used, 4.13.0-16-lowlatency
isn't. Many tags used may be found at: https://wiki.ubuntu.com/Bugs/Tags
Informally, there are kernel specific tags found at:
https://wiki.ubuntu.com/Kernel/BugTriage/Responses
2) When posting upstream, they want t
** Tags added: 4.13.0-16-lowlatency artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509997
Title:
1002:6821 Graphical issues when radeon MST enabled
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15099
** Description changed:
The kernel was launched with the options: radeon.mst=1 radeon.dpm=1 (however,
I noticed identical symptoms for radeon.mst enabled only)
The setup in total includes 3 screens: laptop's one + 2 times Dell U2715H
(connected by Display Port daisy chain)
I get Ubuntu log
Adrian, it wouldn't hurt to mention in the upstream report that you
tested a much more recent version of the radeon drivers, and fglrx works
fine.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Triaged
** Description changed:
The kernel was launched with the options: rade
Yes, in property drivers (fglrx) the MST feature is implemented
correctly and thus can be considered as a workaround.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Adrian, to clarify, does using fglrx provide a WORKAROUND via
https://help.ubuntu.com/community/BinaryDriverHowto/AMD ?
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509997
Title:
1002:6821 Graphical issues when radeon MST enabled
To manage notifications about this bug go to:
https://bugs.laun
I have tried today’s version of the next Ubuntu (16.04) -> the problem hasn't
been resolved. The system behaves as my current instillation (15.10) before
log-in:
".. two Dell screens, laptop's screens got off. The Dell screens are properly
detected as separate: I can move mouse from one screen
27 matches
Mail list logo
