Fedora 32 Workstation ISO (ppc64le) does not work with Raptor Blackbird system

[Trung Le]

To Fedora team

I was thinking of submitting a bug report about Fedora 32 Workstation 
Live USB failed to boot on Raptor Blackbird system.

Here are the steps I take:

* Download ppc64le Workstation ISO
* dd to write the ISO to USB pendrive
* Reboot with the USB pendrive
* Choose the Start Fedora-Workstation Live 32 (64bit kernel) option at 
Petitboot promp
* Got Error loading kernel image

Have I missed anything required to get it boot correctly?

Great thanks

[Dan Horák]

On Wed, 20 May 2020 00:43:12 +1000
Trung Le <trung.le(a)ruby-journal.com&gt; wrote:

>  To Fedora team
>  
>  I was thinking of submitting a bug report about Fedora 32 Workstation 
>  Live USB failed to boot on Raptor Blackbird system.
>  
>  Here are the steps I take:
>  
>  * Download ppc64le Workstation ISO
>  * dd to write the ISO to USB pendrive
>  * Reboot with the USB pendrive
>  * Choose the Start Fedora-Workstation Live 32 (64bit kernel) option
>  at Petitboot promp
>  * Got Error loading kernel image
>  
>  Have I missed anything required to get it boot correctly? 
no, there are multiple issues, but the image works fine in a VM. The
problem is that petitboot doesn't fully understand the grub config
(/boot/grub/grub.cfg) used in the Live image, same config does work when
processed by grub in a VM. The solution is to keep only 64-bit
versions/paths as we don't produce 32-bit content for a long time, for
details see https://github.com/weldr/lorax/pull/1017. It means it will
be fixed in F-33.

The workaround is to edit the kernel/initrd paths before booting to
be /ppc/ppc64/{vmlinuz,initrd.img} instead of /ppc/ppc. Or maybe there
is a newer/fixed version of petitboot, so also building a new firmware
image could help.


		Dan

[Trung Le]

Great thanks for the prompt reply

Editing the boot option kernel/initrd path is probably the best workaround.

It would be great if Fedora team could provide this workaround in the Common bugs wiki
https://fedoraproject.org/wiki/Common_F32_bugs

Kind regards

[Maurizio Mileto]

Dear Fedora team, I am writing to you because despite the time that has passed since
Fedora 32 was released, the Kernel now arrived at version 5.6.13, still does not work
using AMD NAVI 10 GPUs! I know you have added the Patch that Raptor Computing Sistem, in
the person of Tim Pearson, has kindly developed for us in the Power community, to allow us
to use the AMD Navi 10 GPUs.

Now the question arises spontaneously, are you the one who constantly ignores the problem,
or has no one told you yet that the Kernel that has so far come out of Fedora 32, continue
to always have the same problem ?? !!


I think that once you insert a function into an operating system, you do it to make it
work and not to not make it work otherwise what do you insert it to do ?!


I am still forced to use modified Kernels today because you don't correct this damned
Kernel defect ...!


Waiting to have some feedback from you and hoping that you can finally notice the defect,
I take this opportunity to greet you and to tell you that in any case Fedora for us at
Power I think it is the best Linux distribution, so I hope you will continue to be forever
...

Maurizio
Italy

[Dan Horák]

Hello Maurizio,

On Wed, 20 May 2020 18:01:07 -0000
"Maurizio Mileto" <mjvmil(a)tin.it&gt; wrote:

>  Dear Fedora team, I am writing to you because despite the time that
>  has passed since Fedora 32 was released, the Kernel now arrived at
>  version 5.6.13, still does not work using AMD NAVI 10 GPUs! I know
>  you have added the Patch that Raptor Computing Sistem, in the person
>  of Tim Pearson, has kindly developed for us in the Power community,
>  to allow us to use the AMD Navi 10 GPUs.
>  
>  Now the question arises spontaneously, are you the one who constantly
>  ignores the problem, or has no one told you yet that the Kernel that
>  has so far come out of Fedora 32, continue to always have the same
>  problem ?? !! 
if there is still a problem with recent kernels, then it means there
hasn't been an official fix for such problem yet. Fedora doesn't do
kernel development, but follows the upstream/mainline kernels closely.
If there is a fix targeting some next kernel version, then we can ask
the kernel maintainers about backporting it to the Fedora stable
kernel. Do you have a link for us?


	Thanks,

		Dan

 
> 
> I think that once you insert a function into an operating system, you
> do it to make it work and not to not make it work otherwise what do
> you insert it to do ?!
> 
> 
> I am still forced to use modified Kernels today because you don't
> correct this damned Kernel defect ...!
> 
> 
> Waiting to have some feedback from you and hoping that you can
> finally notice the defect, I take this opportunity to greet you and
> to tell you that in any case Fedora for us at Power I think it is the
> best Linux distribution, so I hope you will continue to be forever ...
> 
> Maurizio
> Italy
> _______________________________________________
> ppc mailing list -- ppc(a)lists.fedoraproject.org
> To unsubscribe send an email to ppc-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List
> Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]