Radeon HD, MESA Linux Gallium r600, Light and Shadows Broken #60001

New Issue

noki paike · 2018-12-31T06:45:32+01:00

noki paike commented

2018-12-31 06:45:32 +01:00

System Information
Operating system: Ubuntu 18,10
Graphics card: Radeon HD 7600m
Drivers: MESA Devel 19 (there are better, but some problems on blender? on the drivers? must be solved)
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

Blender Version
Broken:
blender-2.80-d96596de294e-linux-glibc224-x86_64

Worked:
blender-2.80-5e091de0dc6-linux-glibc224-x86_64 ( 30 october 2018)

Short description of error
Linux, Gallium r600, Mesa 19-devel, Light and Shadows Broken totally ..
ESM, VSM shadows not work,
Lights broken

see videos
https://youtu.be/GWEjU51GwVU
https://youtu.be/LtAmDBSXOLQ
https://youtu.be/ruQvL7zqvmQ

I tried an 30 October build with the same drivers and it works (I do not have any more recent ones)
(ESM shadows only thing that did not work with these drivers with this build)

screenshot with the working well October 30 build

system-info.txt

**System Information** Operating system: Ubuntu 18,10 Graphics card: Radeon HD 7600m Drivers: MESA Devel 19 (there are better, but some problems on blender? on the drivers? must be solved) https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers **Blender Version** **Broken:** blender-2.80-d96596de294e-linux-glibc224-x86_64 **Worked:** blender-2.80-5e091de0dc6-linux-glibc224-x86_64 ( 30 october 2018) **Short description of error** Linux, Gallium r600, Mesa 19-devel, Light and Shadows Broken totally .. ESM, VSM shadows not work, Lights broken see videos https://youtu.be/GWEjU51GwVU https://youtu.be/LtAmDBSXOLQ https://youtu.be/ruQvL7zqvmQ I tried an 30 October build with the same drivers and it works (I do not have any more recent ones) (ESM shadows only thing that did not work with these drivers with this build) screenshot with the working well October 30 build ![Schermata del 2018-12-31 06-18-33.png](https://archive.blender.org/developer/F6125428/Schermata_del_2018-12-31_06-18-33.png) [system-info.txt](https://archive.blender.org/developer/F6125479/system-info.txt)

noki paike commented

2018-12-31 06:45:32 +01:00

Added subscriber: @nokipaike

blender-admin commented

2018-12-31 06:45:32 +01:00

#65083 was marked as duplicate of this issue

blender-admin commented

2018-12-31 06:45:32 +01:00

#59776 was marked as duplicate of this issue

Sebastian Parborg commented

2018-12-31 12:55:04 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2018-12-31 12:55:04 +01:00

Attach the output of --debug-gpu and also try if --debug-gpu-force-workarounds helps.

Attach the output of `--debug-gpu` and also try if `--debug-gpu-force-workarounds` helps.

noki paike commented

2019-01-01 01:21:36 +01:00

I tried ... no improvement with "debug - gpu - workaround" and does not produce any results in the console ...
probably these gpu workarounds are useful only for windows ..

with "debug - gpu" ... no improvement, but it produces these results in the console: that from ignorant they seem "clean" .. they do not produce errors in the console ..
debug_gpu.txt
I think they are visual errors, some algorithms that are not well interpreted .. maybe errors of mesa-gallium drivers that have different APIs to produce a certain result ....

in case I sent this bug report to the mesa drivers guys,
someone a few months ago there was dedicated and had greatly improved these drivers on this generation of video cards ...

now the problem with the shadows ESM and VSM has worsened ..
and the problem of lights emerged ..

https://bugzilla.freedesktop.org/show_bug.cgi?id=105371#c18

I tried ... no improvement with "debug - gpu - workaround" and does not produce any results in the console ... probably these gpu workarounds are useful only for windows .. with "debug - gpu" ... no improvement, but it produces these results in the console: that from ignorant they seem "clean" .. they do not produce errors in the console .. [debug_gpu.txt](https://archive.blender.org/developer/F6134207/debug_gpu.txt) I think they are visual errors, some algorithms that are not well interpreted .. maybe errors of mesa-gallium drivers that have different APIs to produce a certain result .... in case I sent this bug report to the mesa drivers guys, someone a few months ago there was dedicated and had greatly improved these drivers on this generation of video cards ... now the problem with the shadows ESM and VSM has worsened .. and the problem of lights emerged .. https://bugzilla.freedesktop.org/show_bug.cgi?id=105371#c18

noki paike commented

2019-01-01 01:25:51 +01:00

Added subscriber: @mano-wii

noki paike commented

2019-01-01 01:25:51 +01:00

I think that only someone who has these GPU with linux can solve this problem ..
perhaps communicating with the boys of MESA-devel Gallium ...

@mano-wii this is bread for your teeth

I think that only someone who has these GPU with linux can solve this problem .. perhaps communicating with the boys of MESA-devel Gallium ... @mano-wii this is bread for your teeth

Clément Foucault was assigned by Sebastian Parborg

2019-01-01 01:58:12 +01:00

Sebastian Parborg commented

2019-01-01 01:58:12 +01:00

Added subscriber: @fclem

Sebastian Parborg commented

2019-01-01 01:58:12 +01:00

From the mesa ticket, this does sound like a driver issue. However, let's hope @fclem can give us some more insight.

noki paike commented

2019-01-01 02:13:53 +01:00

in case it may serve, this is the result of the apitrace https://apitrace.github.io/ as subjected here:
(note* are post made on 2018-08-13)
https://bugzilla.freedesktop.org/show_bug.cgi?id=105371#c10

the file can be analyzed with the apitrace-gui app
https://packages.debian.org/sid/apitrace-gui
blender.trace

in case it may serve, this is the result of the apitrace https://apitrace.github.io/ as subjected here: (note* are post made on 2018-08-13) https://bugzilla.freedesktop.org/show_bug.cgi?id=105371#c10 the file can be analyzed with the apitrace-gui app https://packages.debian.org/sid/apitrace-gui [blender.trace](https://archive.blender.org/developer/F6134454/blender.trace)

noki paike commented

2019-01-01 04:10:06 +01:00

I made a 6 minute video playing with blender and with the console "debug-gpu" in the foreground .. maybe it could be useful to investigate what happens

https://youtu.be/VxLYh-PFdlA

I made a 6 minute video playing with blender and with the console "debug-gpu" in the foreground .. maybe it could be useful to investigate what happens https://youtu.be/VxLYh-PFdlA

Germano Cavalcante commented

2019-01-02 13:32:05 +01:00

In #60001#591025, @nokipaike wrote:
I think that only someone who has these GPU with linux can solve this problem ..
perhaps communicating with the boys of MESA-devel Gallium ...

@mano-wii this is bread for your teeth

The videos are very descriptive and will definitely help!
However I use windows exclusively and I can't replicate the problem.
If Clément doesn't find out what is happening and the problem continues for a long time, I can switch to Linux to replicate and try to solve ;)

> In #60001#591025, @nokipaike wrote: > I think that only someone who has these GPU with linux can solve this problem .. > perhaps communicating with the boys of MESA-devel Gallium ... > > @mano-wii this is bread for your teeth The videos are very descriptive and will definitely help! However I use windows exclusively and I can't replicate the problem. If Clément doesn't find out what is happening and the problem continues for a long time, I can switch to Linux to replicate and try to solve ;)

noki paike commented

2019-01-02 18:34:16 +01:00

hahaha
Come on, @mano-wii put a Mint 19.1 in a flashusb and try what happens without installing anything on the hard disk ...

do not forget this if you have a laptop with two gpu like mine .. otherwise blender starts with the intel gpu

DRI_MODE=1 ./blender
https://www.linuxmint.com/download.php

for mesa-devel drivers updated daily ..
(mint is compatible with ubuntu but more friendly interface for windows users)
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

there is also the ppa padoka .. do not like it .. but on the page there is a list of many features that can be enabled via the console with the gallium drivers ... (also work with oibaf and maybe even with the official mesa)
https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa

hahaha Come on, @mano-wii put a Mint 19.1 in a flashusb and try what happens without installing anything on the hard disk ... do not forget this if you have a laptop with two gpu like mine .. otherwise blender starts with the intel gpu DRI_MODE=1 ./blender https://www.linuxmint.com/download.php for mesa-devel drivers updated daily .. (mint is compatible with ubuntu but more friendly interface for windows users) https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers there is also the ppa padoka .. do not like it .. but on the page there is a list of many features that can be enabled via the console with the gallium drivers ... (also work with oibaf and maybe even with the official mesa) https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa

Brecht Van Lommel commented

2019-01-04 13:41:35 +01:00

Added subscriber: @RPBCACUEAIIBH

Wojtek commented

2019-01-21 00:43:38 +01:00

Added subscriber: @ototto

Wojtek commented

2019-01-21 00:43:38 +01:00

@nokipaike Hello again.
It's been a while, I was really busy and when I actually had the chance to work with Blender, I used a 2.79.
In another thread (https://developer.blender.org/T59996) you've asked me about this kind of viewport bugs. After long and uneven fight with the GPU on my laptop and finally switching it on (problems with oibaf ppa on mint 18.3) I can tell that Eevee renderer looks almost exactly like in the videos above, so... yeah they look glittering-crappy.

--debug-gpu-force-workarounds

this^ suffix doesn't change anything actually.

Please let me know if I could help in any way. Seems like we're somewhat unique about the laptops we use for Blender ;) so maybe I can recreate some of your issues.
Please be patient with my noobie-ness.

My setup for now:
intel i5
HP Pavillion DV7 with Radeon 6770M
Linux Mint 19.1

Blender 2.8 build:
2019-01-17
2757469824

@nokipaike Hello again. It's been a while, I was really busy and when I actually had the chance to work with Blender, I used a 2.79. In another thread (https://developer.blender.org/T59996) you've asked me about this kind of viewport bugs. After long and uneven fight with the GPU on my laptop and finally switching it on (problems with oibaf ppa on mint 18.3) I can tell that Eevee renderer looks almost exactly like in the videos above, so... yeah they look glittering-crappy. ``` --debug-gpu-force-workarounds ``` this^ suffix doesn't change anything actually. Please let me know if I could help in any way. Seems like we're somewhat unique about the laptops we use for Blender ;) so maybe I can recreate some of your issues. Please be patient with my noobie-ness. My setup for now: intel i5 HP Pavillion DV7 with Radeon 6770M Linux Mint 19.1 Blender 2.8 build: 2019-01-17 2757469824bb

Tibor Áser Veres commented

2019-01-21 12:23:52 +01:00

Hi!

I'm a linux only user with an old AMD PC, experiencing the same problem.

System Information
Operating system(s): Ubuntu 17.10 and Ubuntu 18.04
CPU: AMD A10 5800K
RAM: 4x4GB DDR3 1600Mhz
Graphics card: (integrated graphics only: Trinity [Radeon HD 7660D])

Not long ago In another thread ( https://developer.blender.org/T59759 ) I've already posted the errors I'm getting with --debug-gpu-force-workarounds. Let me know If I can help.

Hi! I'm a linux only user with an old AMD PC, experiencing the same problem. System Information Operating system(s): Ubuntu 17.10 and Ubuntu 18.04 CPU: AMD A10 5800K RAM: 4x4GB DDR3 1600Mhz Graphics card: (integrated graphics only: Trinity [Radeon HD 7660D]) Not long ago In another thread ( https://developer.blender.org/T59759 ) I've already posted the errors I'm getting with --debug-gpu-force-workarounds. Let me know If I can help.

noki paike commented

2019-01-22 17:33:03 +01:00

@ototto

Please let me know if I could help in any way.

in addition to the guys of blender to find some solution ...
I think that another way is to urge the boys of mesa devel in some way

https://bugs.freedesktop.org/buglist.cgi?component=Drivers%2FGallium%2Fr600&product=Mesa&resolution=---

@ototto > Please let me know if I could help in any way. in addition to the guys of blender to find some solution ... I think that another way is to urge the boys of mesa devel in some way https://bugs.freedesktop.org/buglist.cgi?component=Drivers%2FGallium%2Fr600&product=Mesa&resolution=---

noki paike commented

2019-02-01 16:42:42 +01:00

good and bad news...

I've just tested the latest blender build with the latest mesa-devel driver..

the standard settings situation remained predominantly the same.
the good news is that if you launch blender with these parameters:
"DRI_PRIME=1 R600_DEBUG=nosb ./blender"
( DRI_PRME=1 ...My radeon gpu is a discrete GPU, and the R600_DEBUG=nosb disable the shader backend acceleration) blender with eevee works perfectly.

the bad news is that the performance goes fuckoff ..

so the problem is of the gallium drivers in particular of the shader compiler ...
in case anyone wants to test ... here some drivers parameters for
R600_DEBUG=

SHADER BACKEND-

  "nosb" Disable sb backend for graphics shaders
  "sbcl" Enable sb backend for compute shaders
  "sbdry" Do not use optimized bytecode (just print the dumps)
  "sbstat" Print optimization for shaders
  "sbdump" Print IR dumps after some optimization passes
  "sbnofallback" Abort on errors instead of fallback
  "sbdisasm" Use sb disassembler for shader dumps
  "sbsafemath" Disable unsafe math optimisations

LOGGING-

  "tex" "Print texture info"
  "texmip" Print texture info (mipmapped only)"
  "compute" Print compute info
  "vm" Print virtual addresses when creating resources
  "trace_cs" Trace cs and write rlockup_&lt;csid&gt;.c file with faulty cs
  "info" Print driver information

SHADERS- (debugging)

  "fs" Print fetch shaders
  "vs" Print vertex shaders
  "gs" Print geometry shaders
  "ps" Print pixel shaders
  "cs" Print compute shaders
  "tcs" Print tessellation control shaders
  "tes" Print tessellation evaluation shaders
  "noir" Don't print the LLVM IR
  "notgsi" Don't print the TGSI
  "noasm" Don't print disassembled shaders

FEATURES-

  "nodma" Disable asynchronous DMA
  "nohyperz" Disable Hyper-Z
  "noinvalrange" (GL uses the word INVALIDATE, gallium uses DISCARD) Disable handling of INVALIDATE_RANGE map flags
  "no2d" Disable 2D tiling
  "notiling" Disable tiling
  "switch_on_eop" Program WD/IA to switch on end-of-packet
  "precompile" Compile one shader variant at shader creation
  "nowc" Disable GTT write combining
  "check_vm" Check VM faults and dump debug information
  "llvm" Enable the LLVM shader compiler
  "sisched" Enable the SI scheduler in the LLVM backend
  "forcedma" Use asynchronous DMA for all operations when possible
  "nocpdma" Disable CP DMA

**good and bad news**... I've just tested the latest blender build with the latest mesa-devel driver.. the standard settings situation remained predominantly the same. **the good news** is that if you launch blender with these parameters: "DRI_PRIME=1 R600_DEBUG=nosb ./blender" ( DRI_PRME=1 ...My radeon gpu is a discrete GPU, and the R600_DEBUG=nosb disable the shader backend acceleration) blender with eevee works perfectly. **the bad news** is that the performance goes fuckoff .. so the problem is of the gallium drivers in particular of the shader compiler ... in case anyone wants to test ... here some drivers parameters for R600_DEBUG= - SHADER BACKEND- ``` "nosb" Disable sb backend for graphics shaders "sbcl" Enable sb backend for compute shaders "sbdry" Do not use optimized bytecode (just print the dumps) "sbstat" Print optimization for shaders "sbdump" Print IR dumps after some optimization passes "sbnofallback" Abort on errors instead of fallback "sbdisasm" Use sb disassembler for shader dumps "sbsafemath" Disable unsafe math optimisations ``` - LOGGING- ``` "tex" "Print texture info" "texmip" Print texture info (mipmapped only)" "compute" Print compute info "vm" Print virtual addresses when creating resources "trace_cs" Trace cs and write rlockup_<csid>.c file with faulty cs "info" Print driver information ``` - SHADERS- (debugging) ``` "fs" Print fetch shaders "vs" Print vertex shaders "gs" Print geometry shaders "ps" Print pixel shaders "cs" Print compute shaders "tcs" Print tessellation control shaders "tes" Print tessellation evaluation shaders "noir" Don't print the LLVM IR "notgsi" Don't print the TGSI "noasm" Don't print disassembled shaders ``` - FEATURES- ``` "nodma" Disable asynchronous DMA "nohyperz" Disable Hyper-Z "noinvalrange" (GL uses the word INVALIDATE, gallium uses DISCARD) Disable handling of INVALIDATE_RANGE map flags "no2d" Disable 2D tiling "notiling" Disable tiling "switch_on_eop" Program WD/IA to switch on end-of-packet "precompile" Compile one shader variant at shader creation "nowc" Disable GTT write combining "check_vm" Check VM faults and dump debug information "llvm" Enable the LLVM shader compiler "sisched" Enable the SI scheduler in the LLVM backend "forcedma" Use asynchronous DMA for all operations when possible "nocpdma" Disable CP DMA

noki paike commented

2019-02-01 18:58:38 +01:00

if someone understands what happens with the damned shader backend compiler ... here the sources ...

https://github.com/mesa3d/mesa/tree/master/src/gallium/drivers/r600/sb

in my opinion it is some trivial parameter wrongly interpreted, which breaks the proper functioning of lights and shadows in blender ...

without the acceleration backend shader, eevee's performances are really poor

if someone understands what happens with the damned shader backend compiler ... here the sources ... https://github.com/mesa3d/mesa/tree/master/src/gallium/drivers/r600/sb in my opinion it is some trivial parameter wrongly interpreted, which breaks the proper functioning of lights and shadows in blender ... without the acceleration backend shader, eevee's performances are really poor

xrg commented

2019-03-02 04:10:16 +01:00

Added subscriber: @xrg

Brecht Van Lommel commented

2019-05-07 13:04:28 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-05-07 13:04:28 +02:00

Closing since we now only officially support AMD graphics cards with GCN 1st gen and later for Blender 2.80.

More information on that decision is here:
https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/

We keep this bug listed in #61936 (EOL GPU problems tracking report) in case anyone is interested in fixing it.

Closing since we now only officially support AMD graphics cards with GCN 1st gen and later for Blender 2.80. More information on that decision is here: https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/ We keep this bug listed in #61936 (EOL GPU problems tracking report) in case anyone is interested in fixing it.

Brecht Van Lommel commented

2019-05-07 13:08:20 +02:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2019-05-07 13:08:20 +02:00

Sebastian Parborg commented

2019-06-20 10:09:22 +02:00

Added subscribers: @JoseBaltazarArriolaOlea, @WilliamReynish

noki paike commented

2019-10-05 09:55:43 +02:00

@brecht this is solvend
https://devtalk.blender.org/t/amd-r600-radeon-hd-mesa-linux-driver-workaround-that-solves-the-problem-scroll-through-the-comments/9294/2

@brecht **this is solvend** https://devtalk.blender.org/t/amd-r600-radeon-hd-mesa-linux-driver-workaround-that-solves-the-problem-scroll-through-the-comments/9294/2

Brecht Van Lommel commented

2019-10-05 09:57:42 +02:00

Changed status from 'Archived' to: 'Resolved'

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Radeon HD, MESA Linux Gallium r600, Light and Shadows Broken #60001