Comment # 7 on bug 92039 from mikolaj.chadzynski@mobica.com

It looks like the screen created by gallium/drivers/radeon/si_pipe.c is not
getting correct configuration from the driver (or display controller ?).
Which part of the system is responsible for creating visuals in the screen ?

XGetVisualInfo from XServer is returning only 3 X visuals (two 24bits depth and
1 32 bits depth) - checked with xdpyinfo.

Then xGLXGetVisualConfigs returns 0 visuals - checked with glxinfo  which shows
0 GLX Visuals and al GLXFBConfigs have VisDepth = 0.

I'm using Yocto distribution for PPC where the default mesa is 9.2.5.
Here is my investigation with different versions of mesa:
9.2.5:
Visuals are created correctly and SW rendering works but switching on HW
rendering (loading radeonsi_dri.so) is causing GPU error.
10.1.2:
No GLX Visuals unable to run SW rendering, GPU error while loading
radeonsi_dri.so
10.4.4:
No GLX Visuals, No gpu error
10.6.1:
No GLX Visuals, No gpu error

In all cases there is no error in XOrg.0.log. It shows:
...
RADEON(0): Direct rendering enabled
RADEON(0): Use GLAMOR acceleration.
RADEON(0): Acceleration enabled
...
AIGLX: Loaded and initialized radeonsi