Re: Need help to make a Radeon HD6970 to work on a G5

John Paul Adrian Glaubitz <[email protected]>
Newsgroups gmane.linux.debian.ports.powerpc
Message-ID <d2f4f818f1328294ec3b6e273e02de46793d575c.camel@physik.fu-berlin.de>
Hi Link,

On Wed, 2024-09-11 at 19:44 -0300, Link Electronics wrote:
> I would like to thank Adrian Glaubitz in advance for his many years of
> continuing to support the PowerPC platform on Debian Linux.

You're very welcome. I'm glad it's useful to you.

> I have a PowerMac G5 Late 2005, been using it for a few months now and was
> using the geforce 6600LE video card that came with it, I compiled some projects
> like DevilutionX, SpaceCadet Pinball, Nblood, Sonic decompilation games Mupen64plus
> etc and made them run with the geforce, but the performance is bad.

Good to hear that lots of the stuff actually works.

> Few days ago I changed it to a Radeon HD6970, it's a Cayman XT, I have the
> xserver-xorg-video-radeon and ati installed, but when loading LightDM or XFCE4,
> the image crashes with artifacts, I can switch to a tty console, in dmesg radeon
> says GPU lockup in ring 0 several times and in the end there is an error in
> drm:v1_0_ib_test and drm:radeon_ib_ring_tests, listing in lspci -k , it says
> kernel in use: radeon and kernel modules: radeon, amdgpu.

This may or may not be a bug in the radeon or amdgpu drivers. I assume they are
rarely tested on big-endian targets.

> I'm using linux-image-6.10.9-powerpc64 (4kb pagesize?)

Yes, that's the 4k pagesize kernel. The 64k pagesize kernel has the -64k suffix.

> I can make the screen work with the framebuffer but no hw acceleration then.
> What can I do to try to resolve this?

Can you try to gather more information from the logs, i.e. the Xorg.0.log file?

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.