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 …
[View More]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.
[View Less]
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
…
[View More] 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.
[View Less]
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/…
[View More]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.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=97530
Bug ID: 97530
Summary: [HD5650][REDWOOD] kernel commit
8c70e1cda04b966b50ddfefafbd0ea376ed8edd5 causing
multiple delays during X server start
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
…
[View More]Assignee: dri-devel(a)lists.freedesktop.org
Reporter: Heiko.Lechner(a)ruhr-uni-bochum.de
Created attachment 126096
--> https://bugs.freedesktop.org/attachment.cgi?id=126096&action=edit
log before reverting the patch
Hi!
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=…
is causing a very long boot delay for me.
I attached a Xorg log before and after reverting the patch in the current linux
kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=97303
Bug ID: 97303
Summary: battery mode for dpm state froze
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: ce-ce-mel(a)hotmail.fr
I try to use the dpm state, but when I …
[View More]set:
echo 'battery' > /sys/class/drm/card0/device/power_dpm_state
while on battery power, laptop freezes after a time.
I tried to add radeon.dpm=1 and (radeon.bapm=1 or radeon.bapm=0) but it does
not fix. Originally, I discovered this issue using TLP (where you can find the
ticket https://github.com/linrunner/TLP/issues/186).
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=97249
Bug ID: 97249
Summary: R290x combined with Mg279q, Dp link fail in ubuntu, in
multihead setup.
Product: Mesa
Version: 11.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
…
[View More]Reporter: ramsland(a)hotmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Epuigpment: CPU Amd fx8350, Mboard: Gigabyte GA-990FXA-UD3, Ram 16 gb. Sapphire
R9 290x.
Monitor setup: 2 monitors, 1 right side (DP-0) Asus MG279q, 1
left(HDMI-0)pb279. Both are 1440p monitors, with the Mq279q have high
refreshrate 144hz.
Using randr for multihead.
OS: Ubuntu 16.04, kernel 4.4.0-31-generic
PPA:Obiaf.
Problem: The right screen is blank, as long as I try to use standard
resolution, meaning 1440p. Can only get it to work in 1080p, at 60hz. It worked
perfectly in the old fgrlx when running ubuntu 14.4, and with radeon in ubuntu
14.4, though it might have been both screens at 60hz with the radeon driver.
When trying with livecd's, the fedora 24 is working at 1440p at 60 hz, but
fails if i try to increase the refresh rate.
Ubuntu live 16.04, fails the same way as my install.
I think its releated to the radeon driver, but i cant be sure.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=97084
Bug ID: 97084
Summary: BUG: scheduling while atomic
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: amarildosjr(a)riseup.net
Created attachment 125330
--> https:…
[View More]//bugs.freedesktop.org/attachment.cgi?id=125330&action=edit
dmesg
Overview: After simulating with X-Plane for a few minutes (can take hours
sometimes), the whole OS freezes upon exiting the simulator.
Steps to Reproduce:
1) Simulate with X-Plane (currently 10.45) with the "AS350 B3+" helicopter. It
could take a few minutes, or it could take several hours (which is normal for a
flight Sim).
2) Exit the Simulator.
Actual Results: The entire OS froze, requiring a hard-reboot.
Expected Results: The Simulator should've just closed.
Build Date & Hardware: Don't remember, but started happening almost a year ago.
Additional Builds and Platforms: Any Linux distro with Kernel 4.1 and onwards
(not being precise on Kernel versioning). Arch, Ubuntu, Mint, Debian
Testing/Sid, OpenSUSE, etc.
Additional Info: Seems related to
https://bugzilla.kernel.org/show_bug.cgi?id=110121
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=96964
Bug ID: 96964
Summary: R290X stuck at 100% GPU load / full core clock on
non-x86 machines
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: kb9vqf(a)pearsoncomputing.…
[View More]net
Our twin Radeon 290X cards are stuck at 100% GPU load (according to radeontop
and Gallium) and full core clock (according to radeon_pm_info) on non-x86
machines such as our POWER8 compute server. The identical card does not show
this behaviour on a test x86 machine.
Forcibly crashing the GPU (causing a soft reset) fixes the issue. Relevant
dmesg output starts at line 4 in this pastebin:
https://bugzilla.kernel.org/show_bug.cgi?id=70651 It is unknown if simply
triggering a soft reset without the GPU crash would also resolve the issue.
I suspect this is related to the atombios x86-specific oprom code only
executing on x86 machines, and related setup therefore not being finalized by
the radeon driver itself on non-x86 machines. However, this is just an
educated guess.
radeontop output of stuck card:
gpu 100.00%, ee 0.00%, vgt 0.00%, ta 0.00%, sx 0.00%, sh 0.00%, spi 0.00%, sc
0.00%, pa 0.00%, db 0.00%, cb 0.00%
radeontop output of "fixed" card after GPU crash / reset, running 3D app:
gpu 4.17%, ee 0.00%, vgt 0.00%, ta 3.33%, sx 3.33%, sh 0.00%, spi 3.33%, sc
3.33%, pa 0.00%, db 3.33%, cb 3.33%, vram 11.72% 479.87mb
Despite the "100% GPU load" indication, there is no sign of actual load being
placed on the GPU. 3D-intensive applications function 100% correctly with no
apparent performance degradation, so it seems the reading is a.) spurious and
b.) causing the core clock to throttle up needlessly.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=96789
Bug ID: 96789
Summary: Black screen with R9 290 and Apple Cinema Display 23"
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: benh(a)kernel.crashing.org
With Radeon (…
[View More]any recent distro version including upstream 4.7-rc5), my Apple
Cinema Display 23" gives a black screen when radeon loads.
The monitor is a fairly old DVI LCD 1920x1200x60. It has a fixed timing, ie, no
scaler. It used to work with earlier versions of radeons but I haven't used it
on a Linux machine for a couple of hears at least.
It works using the agd5f's current amdgpu, but not upstream which doesn't
support the HAWAII. I isolated the difference that makes it work to the PPLL
setting. This one liner fixes it:
--- a/drivers/gpu/drm/radeon/radeon_display.c
+++ b/drivers/gpu/drm/radeon/radeon_display.c
@@ -953,7 +953,7 @@ static void avivo_get_fb_ref_div(unsigned nom, unsigned
den, unsigned post_div,
unsigned *fb_div, unsigned *ref_div)
{
/* limit reference * post divider to a maximum */
- ref_div_max = max(min(100 / post_div, ref_div_max), 1u);
+ ref_div_max = max(min(128 / post_div, ref_div_max), 1u);
/* get matching reference and feedback divider */
*ref_div = min(max(DIV_ROUND_CLOSEST(den, post_div), 1u), ref_div_max);
Here's a log of the working vs. non-working versions of the calculations in
radeon_compute_pll_avivo(). Note that when I did these, I also changed
radeon's max_feedback_div to match amdgpu's value of 0xfff instead of 0x7ff in
current radeon, though that didn't impact the results.
[ 3.471131] fb_div_min/max=4/4095 pll_flags=400
[ 3.471132] by 10 ! fb_div_min/max=40/40950
[ 3.471133] ref_div_min=2 (from 0/2)
[ 3.471133] ref_div_max=1023 (from 0/1023)
[ 3.471134] vco_min/max=600000/1200000
[ 3.471134] post_div_min/max=4/7
[ 3.471135] initial nom=153970, den=2700
[ 3.471136] reduced nom=15397, den=270
[ 3.471136] - trying post_div 4, ref_div_max=32
[ 3.471137] tentative ref_div=32m, fb_div=7299
[ 3.471137] adjusted ref_div=32m, fb_div=7299
[ 3.471138] diff=7, diff_best=-1
[ 3.471138] - trying post_div 5, ref_div_max=25
[ 3.471139] tentative ref_div=25m, fb_div=7128
[ 3.471139] adjusted ref_div=25m, fb_div=7128
[ 3.471139] diff=6, diff_best=7
[ 3.471140] - trying post_div 6, ref_div_max=21
[ 3.471140] tentative ref_div=21m, fb_div=7185
[ 3.471141] adjusted ref_div=21m, fb_div=7185
[ 3.471141] diff=6, diff_best=6
[ 3.471141] - trying post_div 7, ref_div_max=18
[ 3.471142] tentative ref_div=18m, fb_div=7185
[ 3.471142] adjusted ref_div=18m, fb_div=7185
[ 3.471150] diff=6, diff_best=6
[ 3.471150] post_div_best=7
[ 3.471151] - trying post_div 7, ref_div_max=18
[ 3.471151] tentative ref_div=18m, fb_div=7185
[ 3.471152] adjusted ref_div=18m, fb_div=7185
[ 3.471153] [drm:amdgpu_pll_compute] 153970 - 153960, pll dividers - fb:
239.5 ref: 6, post 7
Now this is with radeon *NOTE: I have bumped the max fb div to the same as AMD
GPU when taking that trace but that had no effect:
[ 4.718126] fb_div_min/max=4/4095 pll_flags=410
[ 4.718126] by 10 ! fb_div_min/max=40/40950
[ 4.718127] ref_div_min=2 (from 0/2)
[ 4.718128] ref_div_max=1023 (from 0/1023)
[ 4.718128] vco_min/max=600000/1200000
[ 4.718129] post_div_min/max=4/7
[ 4.718129] initial nom=153970, den=2700
[ 4.718130] reduced nom=15397, den=270
[ 4.718130] - trying post_div 4, ref_div_max=25
[ 4.718131] tentative ref_div=25m, fb_div=5703
[ 4.718131] adjusted ref_div=25m, fb_div=5703
[ 4.718132] diff=11, diff_best=-1
[ 4.718133] - trying post_div 5, ref_div_max=20
[ 4.718133] tentative ref_div=20m, fb_div=5703
[ 4.718133] adjusted ref_div=20m, fb_div=5703
[ 4.718134] diff=11, diff_best=11
[ 4.718134] - trying post_div 6, ref_div_max=16
[ 4.718135] tentative ref_div=16m, fb_div=5474
[ 4.718135] adjusted ref_div=16m, fb_div=5474
[ 4.718136] diff=14, diff_best=11
[ 4.718136] - trying post_div 7, ref_div_max=14
[ 4.718136] tentative ref_div=14m, fb_div=5589
[ 4.718137] adjusted ref_div=14m, fb_div=5589
[ 4.718137] diff=12, diff_best=11
[ 4.718138] post_div_best=5
[ 4.718138] - trying post_div 5, ref_div_max=20
[ 4.718139] tentative ref_div=20m, fb_div=5703
[ 4.718139] adjusted ref_div=20m, fb_div=5703
[ 4.718141] [drm:radeon_compute_pll_avivo] 153970 - 153980, pll dividers -
fb: 570.3 ref: 20, post 5
The modeline is:
Modeline 55:"1920x1200" 60 153970 1920 1968 2000 2080 1200 1203 1209 1235 0x48
0x9
And is consistent between the 2 drivers (different mode number but same
values).
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]