UPDATE 1: Updated glxgears output after running it not synced to vsync
As many of our readers may already be aware, both 2D and now 3D acceleration are working with the nouveau driver on PPC! However, with a couple of hopefully temporary caveats that should hopefully disappear over time. The caveats include the following:
1. You can only try/test this out by upgrading your system to
Stretch (the next stable release of Debian still in development/testing) or
Sid ( forever unstable). Eventually Stretch will become the next stable release (sometime early 2017) and by then let us hope that whatever version of mesa and its related libraries included in the release still has working 3D and 2D acceleration with nouveau.
You could also try to compile the latest versions yourself using the instructions
here, but keep in mind this route is difficult even for more experienced Linux users.
2. As exciting as this news is, the current performance is still lacking, but with regards to G5 machines, this should also be improved with the move to 64 KB page sizes in the future among many other things relevant to just nouveau and PPC development in general. Sadly, still no update on the
64 KB page size mapping bug yet either, but I am trying to keep in touch with the developers.
As first reported, by again, Peter Saisanas, in a comment from my last
post, it appears the fix was included in Mesa's
11.0.3 release back in November. He has also posted about his testing on the Debian PPC mailing list
here. One of the included fixes that may have resolved the remaining issues with 3D acceleration with nouveau on PPC in that release by Mesa developer Ilia Mirkin was "
nv30: always go through translate module on big-endian." That is the current theory anyways as looking through the rest of the fixes over that same release as well other recent releases, this one appears to be the most relevant.
I figured I would conduct my own testing as well by first upgrading to Stretch from Jessie (8.3) to Stretch. I skipped backing up my current install as nothing on it is all that crucial. Most of my crucial files and configurations live on my G4 QS at the current time. Since Stretch or Sid can be (is) unstable at times, you may not want to use it on a production system. Choose your set up wisely. I plan to eventually either partition my current SSD to host both Jessie and Stretch on separate dedicated partitions or use a drive in each available drive bay to host each release of Debian (one for testing and one for stable) so I can always fall back to one or the other in case something breaks.
Speaking of instability, there are issues when doing upgrades to or fresh installs of Stretch as the current kernel included with the release is broken on PPC. So you if you want to test this out, I would highly recommend first instaling Jessie and then downloading and installing one of the pre-built kernels available from Peter's
Google Drive before doing the upgrade. I opted to use his latest kernel (at the time of this writing) 4.5.0-rc2. Just download the kernel-image deb and install it using the following command:
sudo dpkg -i linux-image-4.5.0-rc2-powerpc64_2_powerpc.deb
With that out of the way, you will want to update your /etc/yaboot.conf file to either contain a new entry for the newly installed kernel or replace your existing one.
Here is an excerpt from my yaboot.conf file with the new kernel configuration:
image=/vmlinux-4.5.0-rc2-powerpc64
label=Linux
read-only
initrd=/initrd.img-4.5.0-rc2-powerpc64
Save your changes and run the following:
sudo ybin -v
Next, go ahead reboot to the new kernel using whatever label you assigned to it in your yaboot configuration.
The kernels he has available work with a wide range of G5 towers and nVidia cards but if you are curious to see what has worked for others up to this point, see
this post on the Debian PPC mailing list.
Once that is out of the way, upgrading to Stretch was simple enough as all it requires is editing your /etc/apt/sources.list file by replacing all occurrences of the word Jessie with Stretch. If you are using vim for your text editing tool you can use the following trick once you have the file opened for editing:
:%s/jessie/stretch/
The %s basically means every occurrence of the string jessie with the string stretch. Easy enough. Save your changes run apt-get update and apt-get dist-upgrade per usual. This will update the list of packages from the stretch repositories and start the upgrade to testing.
Once the upgrade is complete, I would recommend rebooting one more time for good measure. Once logged in, make sure mesa-utils or hardinfo (if you prefer a GUI to view what currently active renderer) is installed. Here is the output from my system:
br0c0l1@TheMaster:~$ glxinfo | grep -i renderer
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Gallium 0.4 on NV47
As you can see we are using version 0.4 of Gallium on NV47 (my G5 machine's Quadro 4500FX nVidia card) to provide graphics rendering.
Here is the output when running glxgears:
br0c0l1@TheMaster:~$ vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
1840 frames in 5.0 seconds = 367.913 FPS
1861 frames in 5.0 seconds = 372.069 FPS
1828 frames in 5.0 seconds = 365.374 FPS
1823 frames in 5.0 seconds = 364.437 FPS
So again, not spectacular in terms of performance, but it is definitely a worthy start. It is comforting and exciting to know we have made it this far. One thing I think I should make clear is that having 3D acceleration does not improve video playback performance as that is already optimized to its fullest with 2D acceleration. 3D acceleration helps considerably though if you are into gaming and OpenGL/WebGl projects.
I cannot thank Peter Saisanas enough for the work he puts into nouvea and PPC and kudos to the nouveau developers for not leaving us PPC users in the dust!
I encourage you to try this out and report your findings with either 3D acceleration on nouvea and/or Peter's pre-built G5 kernels either here in the comments or on the Debian PowerPC mailing list.
And finally, as I always say, let the rest of us due our due diligence and report bugs!
