thanks to the work the community does on porting the Chromium browser
to ppc64le, we can have also the qt5-qtwebengine library available.
Currently there are ~20 packages that are excluded on ppc64le due the
unavailability of the webengine.
My "talos" COPR repository  contains now the main qt5-qtwebengine
package, pyqtwebengine bindings for Python and also the qmapshack app.
Building calibre fails in a test, investigating now. If there are other
apps you would like to be made available, let me know.
The plan is to merge the ppc64le support into the official Fedora rpms,
but it can take some time and depends on support from the maintainers of
the QT stack.
Hi, I can connect with a second Linux machine, only I don't know the commands to give once I'm inside the Blackbird. You should kindly write me the exact syntax of the commands you want me to give from the second computer in SSH Root mode and I can run and then send the results of those commands. Thanks
It is possible that I am not registered, however, you are sending me now in the Raptor forum link where I have already performed the procedure to install the 5.5.0.RC1 + kernel and in fact I still use that Kernel with AMD Navi1o without problems. Instead, I wanted to understand why the official Fedora 32 Kernel where it is said that the same Patch has been inserted which contains the Kernel I used or the 5.5.0.RC1 +, it is not yet functional and has a bug still not resolved for the Navi10. 5.6.14 has just been released but the problem persists ...
I forgot to tell you, about the quick reboot, I have rebooted the quick reboot in the petit boot because I have long used that modified kernel that you see in the guide that you also posted. It is the first operation that is performed before carrying out the whole procedure to install Kernel 5.5.0.RC1 + which brings the Navi 10 patch with me. I still use this Kernel successfully today but I was hoping to be able to use the official one now, here because I ask you to understand what happens in the new official Kernels ...
I use the Blackbird motherboard and the Navi 10 GPU. It does not work with the Petitboot but it starts working after loading Fedora. The patch is located in the Kernel and therefore once I load Fedora and consequently the Kernel, the graphics card starts to work regularly. Using a patched kernel, the kernel works smoothly and gives me the ability to use Navi 10 on Fedora. They told me that from the Fedora 32 kernel, or from 5.6.6 onwards, the patch that we have used so far in the modified Kernels was already installed but it turned out that there was a bug when it was inserted and so it doesn't work. In fact, if I try to start one of the official Fedora 32 kernels, at the end of the load, the system remains stuck and never starts. He completes the loading of the operating system but then fails to start and remains on the loading screen without doing anything anymore, he has to reset and restart it. Is there a way to fix this bug and make the official kernel work with Navi 10 regularly? The information I have is this, I don't have anything else.
I don't know how to give you more information on this thing, the problem
was found also on void linux and a developer has solved it and says he
has made it available to everyone but it must be the various Kernel
manufacturers that must apply it. I can't tell you anything else, your
Kernel developers should do a test with Navi 10 and see the problem in
my opinion otherwise we will never get to grips with it if they don't do
field tests. I can only tell you that to date 5.6.13 with Navi 10
enabled by the Xorg file it does not work and you have to restart with
another Kernel that contains the patch and that has no operating bug ...
I can post you what he wrote in a forum about the resolution of the
problem and the link he posted together with the message:
I made the fix, and submitted it to the kernel. AMD then accepted and
merged it. Void Linux ships the fix ahead of time (included in 5.6.8
there) but other distros are free to pick it up if they want to. Or
eventually, it'll appear in some 5.6 bugfix release, I don't know which.
The problem has been solved for some time by a developer who made
available the change he made. It is up to you now to make this change.
He also contacted AMD directly to let him know about the change he made
and AMD gave his good stere ... It's up to you now to fix this problem ...
I wrote directly to him and told him to tell me how to show you his
solution, I'm waiting for you to know what to do ... Thanks