[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

Michel D�nzer  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #14 from Michel D�nzer  ---
Resolving per comment 13, thanks for the reminder.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #13 from Mathieu Malaterre  ---
I believe that all r600 issues have now been solved (thx Oded!). The remaining
of the comments relates to r300 (and thus is a dup of #71789). I believe this
bug can be closed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #12 from Alex Perez  ---
I can confirm that the driver fails with no error here as well, on an
e5500-based ppc64 system. Everything works (with acceleration) when depth is
set to 16 bits. I know a handful of other people who have had the same problem
on 32-bit ppc hardware (modern, non-macppc), so we can be reasonably confident
that this is a broad ppc-specific issue (possibly be/byte-swapping related?)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

herminio.hernandezjr at gmail.com changed:

   What|Removed |Added

 CC||herminio.hernandezjr at gmail.
   ||com

--- Comment #11 from herminio.hernandezjr at gmail.com ---
I have installed the test suite piglit on my iBook G4 and have started running
test my Radeon GPU (r300). I am willing to share the tests results if anyone
thinks it will help with this bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #10 from Alex Deucher  ---
(In reply to kristof from comment #9)
> By checking my Xorg.0.log, I realized that "EXA" submodule is loaded instead
> "glamor" ... (noticed in my workaround firmware non-free installed + mesalib
> not patched)
> Since my gpu is a R300 (RV380-X600) family submodule should be "glamor",
> right or mistake from me due to misunderstanding something ?

All pre-SI cards use EXA by default.  I'm not even sure the r300 cards are
capable of using glamor anymore.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #9 from kristof  ---
Hi Alex,

Workaround progress : delete xorg.conf; Why ?
According radeon man page :
http://manpages.debian.org/cgi-bin/man.cgi?sektion=4=radeon=0=sid=en
Option "AccelMethod" "string"
  Chooses  between  available  acceleration  architectures.  Valid
  values are EXA (for pre-TAHITI GPUs) and  glamor  (for  R300  or
  higher). The default is glamor as of TAHITI, otherwise EXA.

By checking my Xorg.0.log, I realized that "EXA" submodule is loaded instead
"glamor" ... (noticed in my workaround firmware non-free installed + mesalib
not patched)
Since my gpu is a R300 (RV380-X600) family submodule should be "glamor", right
or mistake from me due to misunderstanding something ?

Regards and have a nice day,

Kristof

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #8 from kristof  ---
(In reply to Alex Deucher from comment #7)
> All it needs to contain is the following.
> 
> Section "Device"
> Identifier "Radeon"
> Driver "radeon"
> Option "NoAccel" "true"
> EndSection

Hi ALex,

Following your advise, I've putted it in a xorg.conf
Consequence : system disabled Gallium then returns on Software Rasterizer
methode.
It results that it improves perf, glxgears (without vblank=0 option set) run
now 102 fps (60 before)

Regards,

Kristof

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #7 from Alex Deucher  ---
All it needs to contain is the following.

Section "Device"
Identifier "Radeon"
Driver "radeon"
Option "NoAccel" "true"
EndSection

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #6 from kristof  ---
(In reply to Alex Deucher from comment #5)
> (In reply to kristof from comment #4)
> > PS : can someone tells me if it this an "abnornal" things in the last dmesg
> > | egrep 'drm|radeon' please ?
> > 
> > Thanks and have a nice day
> 
> The kernel side looks fine.  It appears to be a problem with the usermode
> stack.  You might be able to work around it by disabling acceleration.  Try
> adding:
> Option "NoAccel" "True"
> to the device section of your xorg config.
> 
> I'm not really sure how well the usermode stuff works on BE systems.
Hi Alex and thanks for response,

Forgot to mention that I don't use :
* xorg.conf
* no options in my yaboot.conf
* all the OS installation stand by default, just patch Mesa-lib

In this case, should I generate a xorg.conf then use it ?

Regards,

Kristof

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #5 from Alex Deucher  ---
(In reply to kristof from comment #4)
> PS : can someone tells me if it this an "abnornal" things in the last dmesg
> | egrep 'drm|radeon' please ?
> 
> Thanks and have a nice day

The kernel side looks fine.  It appears to be a problem with the usermode
stack.  You might be able to work around it by disabling acceleration.  Try
adding:
Option "NoAccel" "True"
to the device section of your xorg config.

I'm not really sure how well the usermode stuff works on BE systems.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #4 from kristof  ---
Hello,

I've successfully install Debian Jessie on iMac G5 revC (iSight)
Facing same issue, I've followed these instructions here in order to downgrad
mesa packages :
http://ppcluddite.blogspot.fr/2012/03/installing-debian-linux-on-ppc-part-iv.html#graphics

uname -a : Linux iMac17c 3.16.0-4-powerpc64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1
(2015-04-24) ppc64 GNU/Linux

:04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RV380 [Radeon X600] (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV380 [Radeon X600]
Flags: bus master, fast devsel, latency 0, IRQ 25
Memory at 9800 (32-bit, prefetchable) [size=128M]
I/O ports at 0400 [size=256]
Memory at 9000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at 9002 [size=128K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: radeon

Workaround :
1) Jessie fresh install graphics results (no firmware non-free installed), able
to log in graphic session :

LIBGL_DEBUG=verbose glxinfo | grep render
libGL: screen 0 does not appear to be DRI3 capable
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
libGL: Can't open configuration file /home/kristof/.drirc: No such file or
directory.
direct rendering: Yes
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_query_renderer, GLX_OML_swap_method, GLX_SGIS_multisample, 
OpenGL renderer string: Software Rasterizer
GL_NV_blend_square, GL_NV_conditional_render, GL_NV_depth_clamp, 

dmesg | egrep 'drm|radeon' complains about microcode :
[   13.715213] [drm] Loading R300 Microcode
[   13.732935] radeon :04:00.0: firmware: failed to load radeon/R300_cp.bin
(-2)
[   13.732962] [drm:r100_cp_init] *ERROR* Failed to load firmware!
[   13.732971] radeon :04:00.0: failed initializing CP (-2).
[   13.732978] radeon :04:00.0: Disabling GPU acceleration


2) then install it with non-free firmware :

dmesg | egrep 'drm|radeon' happy because it find the microcode :-)
[   13.469992] [drm] radeon: irq initialized.
[   13.470031] [drm] Loading R300 Microcode
[   13.560891] radeon :04:00.0: firmware: direct-loading firmware
radeon/R300_cp.bin
[   13.561237] [drm] radeon: ring at 0x7801

but it breaks something :-(

LIBGL_DEBUG=verbose glxinfo | grep render
libGL: screen 0 does not appear to be DRI3 capable
libGL: pci id for fd 4: 1002:5b62, driver r300
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so
libGL: Can't open configuration file /home/kristof/.drirc: No such file or
directory.
libGL: Can't open configuration file /home/kristof/.drirc: No such file or
directory.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: r300
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
libGL: Can't open configuration file /home/kristof/.drirc: No such file or
directory.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Error: couldn't find RGB GLX visual or fbconfig

3) according to the procedure provides in the link above, I've applied patch :

LIBGL_DEBUG=verbose glxinfo | grep render
libGL: screen 0 does not appear to be DRI3 capable
libGL: pci id for fd 4: 1002:5b62, driver r300
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so
libGL: driver does not expose __driDriverGetExtensions_r300():
/usr/lib/powerpc-linux-gnu/dri/r300_dri.so: undefined symbol:
__driDriverGetExtensions_r300
libGL: Can't open configuration file /home/kristof/.drirc: No such file or
directory.
libGL: Can't open configuration file /home/kristof/.drirc: No such file or
directory.
direct rendering: Yes
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
OpenGL renderer string: Gallium 0.4 on ATI RV370
GL_NV_blend_square, GL_NV_conditional_render, GL_NV_fog_distance, 
GL_OES_depth_texture, GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,

dmesg | egrep 'drm|radeon'
[   13.085940] [drm] Initialized drm 1.1.0 20060810
[   13.518475] [drm] radeon kernel modesetting enabled.
[   13.518613] fb: switching to radeondrmfb from OFfb ATY,Aphrod
[   13.542630] fb: switching to radeondrmfb from OFfb ATY,Aphrod
[   13.543441] radeon :04:00.0: enabling device (0006 -> 0007)
[   13.544541] [drm] initializing kernel modesetting (RV380 0x1002:0x5B62
0x1002:0x5B62).

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #3 from 65a  ---
Patches do not work for r600 as they contain r300 specific code

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #2 from 65a  ---
It appears that the same issue as mentioned by Michael Danzer is affecting
Linux. Setting pixel depth to 16 does resolve the issue, and properly reports
Gallium support. I am testing the patches now. Is there any plan to integrate
these patches? What work needs to be done?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

--- Comment #1 from Michel Dänzer  ---
See bug 71789.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

65a  changed:

   What|Removed |Added

 OS|All |Linux (All)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

65a  changed:

   What|Removed |Added

   Hardware|Other   |PowerPC

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 87856] Driver load fails with no error on ppc64 host

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87856

Bug ID: 87856
   Summary: Driver load fails with no error on ppc64 host
   Product: Mesa
   Version: 10.2
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: Drivers/Gallium/r600
  Assignee: dri-devel at lists.freedesktop.org
  Reporter: freedesktopbugs at 63bit.net

Created attachment 111507
  --> https://bugs.freedesktop.org/attachment.cgi?id=111507=edit
Xorg log, dmesg | fgrep radeon, and glxinfo with LIBGL_DEBUG set

I have a PowerPC G5 (ppc64 with 64-bit userland) with working KMS using a
(ostensibly x86) Radeon HD4650. KMS is enabled and the kernel and Xorg parts of
KMS/DRI2 appear to be attaching correctly.

After X starts, running LIBGL_DEBUG=verbose glxinfo outputs the following:
libGL: OpenDriver: trying /usr/lib64/dri/tls/r600_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/r600_dri.so
libGL: driver does not expose __driDriverGetExtensions_r600():
/usr/lib64/dri/r600_dri.so: undefined symbol: __driDriverGetExtensions_r600
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL error: failed to load driver: r600
libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so
libGL: driver does not expose __driDriverGetExtensions_swrast():
/usr/lib64/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL error: failed to load driver: swrast
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig

I am under the impression that the undefined symbol should not be causing
problems after reading this bug: 
https://bugs.freedesktop.org/show_bug.cgi?id=72198

Nonetheless, glxgears will not run, and in general it appears mesa acceleration
is not occurring. Mesa was compiled with support for llvm and the r600
generator.
I am attaching various logs. I would be glad to test patches or hacks :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: