https://bugs.freedesktop.org/show_bug.cgi?id=98974
Bug ID: 98974
Summary: Can't see borders/empires in Stellaris
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: lukas.fuernkranz+bugzilla2(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
I'm using Ubuntu 16.04 and an AMD Radeon 6870 with the drivers from
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers.
In Stellaris (a video game) I can't see the borders/empires on the map. Unless
I set the graphics quality to low that is.
(Temporarily I used an AMD R9 270x---also with the drivers from the oibaf PPA;
radeonsi though---and there I didn't have that problem.)
In case more infos are needed please say so and I'll do my best to provide it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99349
Bug ID: 99349
Summary: Failed to build shader (translation from TGSI)
Product: Mesa
Version: 13.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: balalic.enver(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 128864
--> https://bugs.freedesktop.org/attachment.cgi?id=128864&action=edit
glxinfo
I'm using a Radeon HD6950, it fails to build a shader when playing "War
Thunder", renders the login screen fine, starts to build shaders and then fails
and spams the following in the console:
EE r600_state_common.c:799 r600_shader_select - Failed to build shader variant
(type=1) -1
EE r600_shader.c:183 r600_pipe_shader_create - translation from TGSI failed !
same thing happens a lof of shaders from shadertoy.com.
OS: OpenSUSE Tumbleweed, glxinfo attached
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bug ID: 99353
Summary: Kaveri 7400K shows random colored noise instead of GUI
in X or Wayland
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: vedran(a)miletic.net
QA Contact: dri-devel(a)lists.freedesktop.org
I have a Kaveri 7400K on ASRock FM2A58M-VG3+. Running Fedora 25, KMS works and
it boots nicely, but instead of GDM running on Wayland, I get screen full of
colored noise. Using Xorg makes no difference.
Phoronix claims this APU worked in 2014[1]. It never worked for me with the
open source driver (previously not even KMS worked), however it worked
perfectly with fglrx last time I tried it.
I can try older Mesa and LLVM if that would be useful, but compiling it will
take a while.
[1] https://www.phoronix.com/scan.php?page=article&item=amd_apus_august&num=1
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=100759
Bug ID: 100759
Summary: [r600] System freeze on resume from sleep on battery
with DPM enabled and linux 4.10
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: nicolamori(a)aol.com
Created attachment 130983
--> https://bugs.freedesktop.org/attachment.cgi?id=130983&action=edit
journalctl log for failed resume
Since linux 4.10.1 my system freezes every time when resuming from sleep
(suspend to ram) while on battery. The screen either remains black or displays
garbage, and the only thing to do is a hard poweroff. The problem does not show
up when either:
- running on AC or
- using linux 4.9 (tested with 4.9.11) or
- DPM is not enabled (radeon.dpm=0)
I checked journalctl but it does not contain anything useful. I attach the last
part of the log, starting from the suspend request; it seems nothing from the
failed resume process is logged.
System details:
- Archlinux x86_64
- Mobility Radeon HD 3470
- Plasma desktop 5.9.4
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=101672
Bug ID: 101672
Summary: radeonsi: 3D engines causing frequent GPU lockups
Product: Mesa
Version: 17.1
Hardware: Other
OS: All
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: sonichedgehog_hyperblast00(a)yahoo.com
QA Contact: dri-devel(a)lists.freedesktop.org
A GPU lockup has once again been introduced in Mesa and / or the RadeonSI
driver. As is usual with this sort of thing, the image immediately freezes in
place while audio stops and every form of input becomes unresponsive (including
the NumLock / CapsLock keyboard leds), the only option being to power the
machine off and back on. I started noticing this crash roughly a month ago
after a distribution upgrade (openSUSE Tumbleweed).
The crash only appears to be caused by 3D rendering. It's probabilistic but
very frequent. It is triggered by a variety of game engines, and I've noticed
it with at least the following ones:
- Blender 3D: When opening certain scenes in Blender and going into Weight
Paint mode, the system is bound to crash in at most 5 minutes of usage.
- Second Life: Linux native viewers for Second Life also trigger this, I
believe somewhere between 5 and 30 minutes estimate.
- Xonotic (Darkplaces engine): Starting a game will freeze the machine anywhere
between instantly (the moment a game starts) and 30 minutes at most.
- The Dark Mod (idTech 4 engine): The same freeze will occur when playing
TheDarkMod, anywhere between instantly and roughly 10 minutes at most.
- MineCraft: The native version of Minecraft can also trigger the crash, after
at most 1 hour of playing a game especially on servers with a lot of geometry.
My OS is openSUSE Tumbleweed x64. My current Mesa version is 17.1.3, I can
confirm first noticing this in 17.1.1, but I don't know if the issue was
introduced in 17.1.0 or prior. My video card is a Radeon R7 370 (Gigabyte),
Pitcairn Islands GPU, GCN 1.0, RadeonSI. Official product page:
http://www.gigabyte.com/products/product-page.aspx?pid=5469
Please help to address this issue soon: I am unable to use several applications
due to the risk they pose to my computer! Logs will be attached soon.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=100919
Bug ID: 100919
Summary: "Out of range" on a display connected to a DVI-D
output of RX460 card via DVI-D<=>HDMI-A cable
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: nikola.forro(a)gmail.com
I'm using the latest code from amd-staging-4.9 branch of ~agd5f/linux.
The problem is caused by this commit:
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-4.9&id=2b2d…
After this change, when sink_signal is DVI_DUAL_LINK but pix_clk_khz is lower
than TMDS_MAX_PIXEL_CLOCK_IN_KHZ, stream->signal is set to DVI_DUAL_LINK, while
previously it was being set to DVI_SINGLE_LINK.
As a result, the connected display just reports "Out of range" error.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=98856
Bug ID: 98856
Summary: Dirt: Showdown broken graphics
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: gr.muench(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
For about 4 weeks the game has polygon distortion especially on the Nevada map.
Its not on every map but it can be seen with the ingame benchmark.
Im on:
Radeon HD 7970
OpenGL renderer string: Gallium 0.4 on AMD TAHITI (DRM 2.48.0 /
4.9.0-rc4-gbc33b0c, LLVM 4.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 13.1.0-devel
(git-b27be18)
--
You are receiving this mail because:
You are the assignee for the bug.