https://bugs.freedesktop.org/show_bug.cgi?id=80684
Priority: medium
Bug ID: 80684
Assignee: dri-devel(a)lists.freedesktop.org
Summary: I2C-over-AUX drops single bytes
Severity: normal
Classification: Unclassified
OS: All
Reporter: stefan.bruens(a)rwth-aachen.de
Hardware: Other
Status: NEW
Version: DRI CVS
Component: DRM/Radeon
Product: DRI
I get frequent errors for the EDID checksum, obviously single bytes are dropped
from the EDID.
Good EDID:
Raw EDID:
02 03 1d f1 50 90 05 04 03 02 07 16 01 06 11 12
15 13 14 1f 20 23 09 7f 07 83 01 00 00 02 3a 80
18 71 38 2d 40 58 2c 25 00 55 50 21 00 00 1e 01
1d 80 18 71 1c 16 20 58 2c 25 00 55 50 21 00 00 <--
9e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21
00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 55
50 21 00 00 18 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5d
Bad EDID example:
Raw EDID:
02 03 1d f1 50 90 05 04 03 02 07 16 01 06 11 12
15 13 14 1f 20 23 09 7f 07 83 01 00 00 02 3a 80
18 71 38 2d 40 58 2c 25 00 55 50 21 00 00 1e 01
1d 80 18 1c 16 20 58 2c 25 00 55 50 21 00 00 9e <-- 0x71 is missing
01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21 00
00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 55 50
21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 5d 00
The position of the dropped byte changes, sometimes the EDID is complete,
sometimes several bytes are dropped.
The bad EDIDs are *often* accompanied with [drm:radeon_process_aux_ch]
dp_aux_ch flags not zero messages.
Most probably the common i2c-over-aux code drops the byte, as it starts the
transfer again in case of -EBUSY. If I change radeon_process_aux_ch to return
-EIO in case of (ReplyStatus == 2), I no longer have any bad checksums.
Hardware is Radeon 7750 + Dell U2713HM, connected via DP.
Same monitor with Intel Haswell and different cable works without any errors.
Kernel is 3.15.1, i.e. without the i2c bus mutex, dont know if this fixes the
problems as well.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=92977
Bug ID: 92977
Summary: Display artifacts when using MST
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: dan.doel(a)gmail.com
Created attachment 119730
--> https://bugs.freedesktop.org/attachment.cgi?id=119730&action=edit
image 1 - half of window uses different colors
I've been trying out the support for tiled MST monitors on Radeon drivers, and
seem to be encountering some visual anomalies that seem like they are likely to
be related to this component.
My setup is two UP2414Q monitors, which have native resolutions of 3840x2160.
Over DisplayPort 1.2, they are capable of running as two 1920x2160@60 displays
each. I have a nvidia card that is capable of driving them in this mode, so I
am reasonably sure that the hardware isn't the problem (unless it is the Radeon
card, but that seems unlikely).
First, there seems to be a color anomaly with the primary display. The right
half of the display has different colors from the left (see first image). I
noticed that this may be due to the left half displaying a different color
depth than the right. The second image shows the gnome overlay, and while the
shadows are smooth on the right, there is banding on the left. My second
monitor seems to have both sides in this reduced color mode, and enough
fiddling with settings after a boot causes both halves of the primary monitor
to be configured that way as well, but needless to say, the reduced color depth
(if that's what it is) is undesirable.
Second, the secondary monitor has some visual artifacts to the left of center
(a vertical band about an inch wide) as well as to the far right (a vertical
band around 1/4 inch wide). The third image should give some idea what it looks
like. A better photo might show that things in that region look somewhat
interlaced, and are repeated horizontally.
I apologize for the poor quality of the images, but screenshots don't capture
these artifacts, so I had to use my phone.
I'm running with packages from Fedora 23, so xorg-server 1.18.0, xf86-video-ati
7.6.0-0.4.20150729git5510cd6, kernel 4.2.5-300. If you'd like any other
information, let me know.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=32556
Summary: screen flickers all the time with desktop image
appearing only briefly
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: 3ntr0p13(a)gmail.com
Created an attachment (id=41344)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41344)
dmesg
Machine is the same as in bug report 28331 although with different software
components: Acer Aspire L5100 with an AMD Athlon 64 X2 Dual Core Processor
4000+, this time running a 64 bits debian squeeze.
The machine is a small factor desktop machine designed around laptop
components, so the graphic card is an integrated radeon x1200.
When running a linux vanilla kernel 2.6.37-rc6, the screen flickers all the
time
making the machine unusable, while with debian kernel 2.6.32-5 such "flick to
black" event occur from time to time, making it annoying but usable.
While booting with radeon.modeset=0 the problem doesn't exhibits itself
The following packages version from debian squeeze are installed:
xserver-xorg 1:7.5+8
xserver-xorg-core 2:1.7.7-10
xserver-xorg-video-radeon 1:6.13.1-2+squeeze1
Please find attached Xorg.0.log, dmesg, register dumps for ums and kms for that
machine (when booted on 2.6.37-rc6).
Regards,
Gildas
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=32422
Summary: Large images displayed in Firefox appear corrupted
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: da_fox(a)mad.scientist.com
Created an attachment (id=41150)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41150)
Picture describing a thousand words.
"A picture says more than a thousand words" (aka see attachment)
This is what happens when I try to view the XKCD "Online Communities 2" map
(http://xkcd.com/802_large/) or other large images in firefox.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=97157
Bug ID: 97157
Summary: MST displays fail to wake
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: dan.doel(a)gmail.com
Created attachment 125450
--> https://bugs.freedesktop.org/attachment.cgi?id=125450&action=edit
dmesg output
Since moving to kernel 4.6, I've been having regular problems with my MST
monitors failing to wake after being put to sleep. This only seems to occur
after the machine has been on for a sufficient amount of time, but I usually
experience it within a day of booting, and typically after the displays have
been powered off for an extended period of time.
There are two MST monitors, but typically only one fails to wake. Also, it is
more often that the secondary display is the one that fails. However, I have
had the primary display fail to come back (while the secondary one succeeds),
and I have had both fail to come back as well.
Sometimes, only a complete power off is able to make the monitors wake up; a
reboot is not always sufficient.
The dmesg displays some errors, and I've poked around a bit. It seems likely
that this is related to commit f3d58dccdbf9f8c0a229d555d4b295d52e743039, which
was first included in 4.6. This commit basically causes dpms to work at all
with MST monitors; before it was a no-op that didn't actually put the monitors
into power saving. That doesn't help narrow the problem down much, though,
since a significant portion of the mst dpms code probably wasn't being
exercised before that.
Also, it seems notable that the error message (which seems more like a debug
message) in the STANDBY/SUSPEND/OFF case keeps reporting higher numbers, as
though it keeps going through the ON case, which increments the variable, but
not making it through the portion of the OFF case that decrements the variable.
I'll attach dmesg journal output that might be relevant. I believe the
error/debug messages timestamped 'Jul 31 11:03:49' correspond to the first time
one of the displays failed to wake up. I tried various ways of toggling the
dpms off and on after that, so those are the subsequent error messages in the
log.
As far as specs go, I have:
Radeon HD7870 (Pitcairn)
Kernel 4.6.4 (4.6.3 also affected)
2 UP2414Q mst displays
xorg-server 1.18.4
Modesetting driver
Let me know if there's any more information I can try to provide.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=94153
Bug ID: 94153
Summary: Unresponsive system on boot with radeon + HD 3870
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: g47qk(a)ukr.net
Created attachment 121755
--> https://bugs.freedesktop.org/attachment.cgi?id=121755&action=edit
dmesg.log saved via the serial port
I'm using a HD 3870 with Debian 9 Stretch x64 (Testing). When booting to a
command line, when drivers are loaded, the screen goes into power saving mode,
and the system becomes unresponsive.
Booting with `nomodeset' works OK. If I run "#modprobe radeon modeset=1", the
screen goes power saving mode, the system stops responding and the caps lock
key no longer works (kernel panic?).
I've also tested with a Fedora 23 Workstation Live-CD (64-bit), Ubuntu 15.10
Desktop (64-bit) Live-CD, SystemRescueCd-x86-4.7.0 with the same results
(unresponsive on driver load).
I've tested a ATI X1600 Pro in the same system, and everything works fine.
#lspci -nnn | grep VGA
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] RV670 [Radeon HD 3870] [1002:9501]
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89971
Bug ID: 89971
Summary: HDMI out *not* working with radeon (mobile 8550g)
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: adrianovidiugabor(a)gmail.com
Created attachment 114999
--> https://bugs.freedesktop.org/attachment.cgi?id=114999&action=edit
screen's content
Hi all.
If I'm connecting my laptop's HDMI out to my TV I get a black screen with
garbage on top (see attached pic). This is with mirror mode on. If making the
second screen primary, the pc blocks and I have to restart it. It won't unblock
even if I disconnect the cable.
If switching to one of the virtual consoles, everything works correctly as it
should, so the problem seems to be related somehow to the display server.
The Tv is recognized correctly by xrandr.
Specs: Asus laptop, with AMD A8-5550M, Radeon 8550G(Aruba)/8670M(Hainan), OS
ArchLinux(x64) Xorg-xerver 1.17, kernel 3.19.3, Mesa-git, xf86-ati-git,
llvm-svn.
This doesn't seem to be a regression (experienced it with older versions of the
kernel and userspace components) and it's reproducible on another machine.
HDMI out works on Windows and ChromeOS.
Didn't try Catalyst on Linux.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=80531
Priority: medium
Bug ID: 80531
Assignee: dri-devel(a)lists.freedesktop.org
Summary: 3.16-rc2 hdmi output resolution out of range Cape
Verde PRO [Radeon HD 7750]
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: fredrik(a)obra.se
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 101759
--> https://bugs.freedesktop.org/attachment.cgi?id=101759&action=edit
dmesg with drm.debug=1
With 3.16-rc2 my tripple screen setup breaks.
DisplayPort-0 connected 1920x1200 <- ok
HDMI-0 connected 1920x1080 <- (tv) resolution out of range
DVI-0 connected 1680x1050 <- ok
All screens work during bootup before X starts.
ddx driver 7.3.0.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=75992
Priority: medium
Bug ID: 75992
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Display freezes & corruption with an r7 260x on
3.14-rc6
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: edt(a)aei.ca
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 95520
--> https://bugs.freedesktop.org/attachment.cgi?id=95520&action=edit
log of boot
I recently added a R7 260X to my system. While the card works with 3.13 its
supposed work much better with 14-rc. This is not the case. My system is
unstable without radeon.dpm=0 which was the default in .13.
linux 3.14-rc6 (with an up to date arch, stable X and mesa-git (10.2) mesa 10.1
and 10.0 also show very similar problems.
When X started I did notice some corruption. There are sets of two rectangles
about of a height of 2 or 3 mm, width of 25m or so with a second about a cm
below. The often occurs in chomium especially when scrolling. Runing the
unigine-sanctuary or unigine-tropics demo/benchmark programs also produce the
above problems and eventually stall.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=101213
Bug ID: 101213
Summary: Kernel 4.11: amdgpu regression causes artifacts OLAND
amd gpu gcn 1.0
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: eutychios23(a)gmail.com
The display Manager,part of the desktop and any graphics app i run get severe
artifacts on any kernel 4.11.x version with amdgpu enabled, whereas in 4.10.17
all is working good.
Reproduce:
Install kernel 4.11 and later with SIK=y, blacklist radeon, install
xf86-amdgpu, enable the amdgpu module and boot the kernel.
Same regression existed in kernels 4.10.2 and lower but was fixed after the
4.10.3 update
--
You are receiving this mail because:
You are the assignee for the bug.