Re: [gentoo-powerpc] Radeon 3D powerpc

It looks like to 3D working with the r300 driver you need set the default
display to 16 in Xorg on gentoo.

rican-linux@ibookG4-gentoo ~ $ LIBGL_DEBUG=verbose glxinfo |grep render
libGL: screen 0 does not appear to be DRI3 capable
libGL: pci id for fd 4: 1002:4e56, driver r300
libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
direct rendering: Yes
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
OpenGL renderer string: Gallium 0.4 on ATI RV350
    GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_conditional_render,
    GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,




On Sat, Apr 18, 2015 at 1:24 PM, Herminio Hernandez, Jr. <
herminio.hernandezjr@×××××.com> wrote:

> I have succesfully applied and installed mesa with the patch.
> I needed to do the following
>
> move the ebuild to my overlay /usr/local/portage/media-libs/mesa
>
> then run the follwoing commands
> ebuild pathtoebuild digest
> ebuild pathtoebuils fetch
> ebuild pathtoebuild unpack
> then manuall apply patches
> ebuild pathtoebuils compile
> ebuild pathtoebuild install
>
> how ever I an still not getting 3D. The only difference I am seeing is
> that in Debian i needed to install linux-frimware-nonfree and I do not have
> that option in gentoo.
>
> rican-linux@ibookG4-gentoo ~/Desktop $ LIBGL_DEBUG=verbose glxinfo |grep
> render
> libGL: screen 0 does not appear to be DRI3 capable
> libGL: pci id for fd 4: 1002:4e56, driver r300
> libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
> libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
> libGL error: No matching fbConfigs or visuals found
> libGL error: failed to load driver: r300
> libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so
> libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so
> libGL error: No matching fbConfigs or visuals found
> libGL error: failed to load driver: swrast
> Error: couldn't find RGB GLX visual or fbconfig
>
>
> On Fri, Apr 17, 2015 at 10:53 AM, Herminio Hernandez, Jr. <
> herminio.hernandezjr@×××××.com> wrote:
>
>> Research on how to create a local overlay on the gentoo site. Will
>> attempt when I get home. Thanks
>>
>> On Fri, Apr 17, 2015 at 5:42 AM, Konstantin Tokarev <annulen@××××××.ru>
>> wrote:
>>
>>>
>>>
>>> 16.04.2015, 20:10, "Herminio Hernandez, Jr." <
>>> herminio.hernandezjr@×××××.com>:
>>> > There is common issue with the r300 driver in Mesa and Radeon cards on
>>> G4 Macs. When you have KMS enabled and to see if useing opengl you get this.
>>> >
>>> > rican-linux@ibookG4-gentoo ~ $ LIBGL_DEBUG=verbose glxinfo |grep
>>> render
>>> > libGL: screen 0 does not appear to be DRI3 capable
>>> > libGL: pci id for fd 4: 1002:4e56, driver r300
>>> > libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
>>> > libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
>>> > libGL error: No matching fbConfigs or visuals found
>>> > libGL error: failed to load driver: r300
>>> > libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so
>>> > libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so
>>> > libGL error: No matching fbConfigs or visuals found
>>> > libGL error: failed to load driver: swrast
>>> > Error: couldn't find RGB GLX visual or fbconfig
>>> >
>>> > There are two ways to resolve this
>>> >
>>> > 1. set you default display to 16 in xorg.conf, but on PowerBook you
>>> really see the drop in depth bot so much in iBooks.
>>> >
>>> > 2. apply a patch found here
>>> >
>>> > I would much rather do option 2 and test that, however I am having
>>> some difficulty learning how to apply patches and reinstall in gentoo. In
>>> debian or ubuntu i would apt-get source the package, apply the patch, then
>>> recompile and reinstall. Can someone point me to resource that can help. I
>>> really cannot find it in the gentoo wiki, but I admit it may be I am not
>>> search for the correct thing. Thanks!
>>>
>>> You create local overlay, copy ebuilds you want to change from main
>>> portage tree to you overlay, modify ebuild (e.g. add patch), then execute
>>> `ebuild filename.ebuild digest`. After that you emerge the same package
>>> name as before and it gets installed from your overlay.
>>>
>>> --
>>> Regards,
>>> Konstantin
>>>
>>
>>
>