Raptor Computing Systems Community Forums (BETA)
Software => Operating Systems and Porting => Topic started by: tle on April 28, 2020, 07:04:13 pm
-
RedHat and IBM are now under same roof, the future looks bright for OpenPower. Good news is Fedora 32 is now out.
* Notable changes *
- Kernel 5.6.6
- GNOME 3.36 - faster and better in UX
- TRIM is enabled by default
- GCC 10 / LLVM 10 - even before GCC 10 is released! W00t!
- glibc 2.31
- Python 3.8
- Ruby 2.7
- Golang 1.14
- Workstation flavour - for the first time! - this might be helpful for newcomers
Let's hope the 128-bit floats on ppc64le issue would get addressed in future release.
Download links: https://alt.fedoraproject.org/alt/
EDIT: If you get the "Error loading kernel image" at Petitboot, the workaround is to edit the following boot option for the Fedora 32 Live:
* Kernel: ppc/ppc64/linuz
* Initrd: ppc/ppc64/linux
See https://fedoraproject.org/wiki/Common_F32_bugs#Fedora_32_Workstation_.28ppc64le.29_Live_image_failed_to_boot
-
Hi, yes I saw that the update has arrived, the problem for me and for those like me who have the kernel with patch for AMD Navi 10, you can update without losing the patch ... We currently use the modified Kernel 5.5 .0.RC1 + which incorporates the patch written by Tim Pearson to operate the Navi 10 type Radeon 5700 or 5700 XT, or Navi 14 which uses the same patch. Updating to Fedora 32, with Kernel 5.6, MPC7500 says that the patch does not work and therefore for us it becomes a big problem. I don't know how to behave honestly now ...
-
F31 is still going to be supported for a little while, so there's no hurry to upgrade if you're concerned about it.
-
There is nothing stopping you from using a patched Kernel 5.4 / 5.5 on F32. I also don't think that the patched Kernel of F31 will be overwritten by F32.
-
I thank you for the confirmation, I had thought that the Kernel did not touch it but in doubt I asked. MPC sorry but what exactly did you feel to realize that this Kernel does not make Navi 10/14 work? I have not even understood if they have inserted the default patch on Kernel 5.6 or it must always be installed separately ...
-
The patch is included in Kernel 5.6, but it is broken. q66 submitted a fix (https://lists.freedesktop.org/archives/amd-gfx/2020-April/049138.html) a few days ago. Now AMD has applied it. It will be included in the next 5.6.x releases.
-
Here I had imagined that they had implemented it as standard. Do you mean that AMD itself took care of making this fix? This is a really nice thing. Currently I have seen that the version of Kernel available is 5.6.7 do you know if up to this version there is a bug?
For the rest it's great news, it means that as soon as they fix it, we will have the default patch and you don't need to do the whole procedure anymore, really great news, just set up Xorg as we currently have it and I'm done.
Fedora is truly fanstastic, proving once again the best, especially for us at Power, really fabulous!
-
No, 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.
-
hello Q66, I'm finding that in any case, the Kernel version 5.6.7 of Fedora, just doesn't work completely. It is not just a patch problem but the whole Kernel that does not start. I did the Fedora update and I successfully switched to version 32 but as Kernel I always use the modified 5.5.0.rc1 + otherwise it doesn't work completely. I had already noticed with Fedora 31 that this Kernel does not work completely. in fact I believe that the Fedora team must hurry to fix the bug ...
-
guys the 5.6.8 kernel has arrived, too bad that for me personally, it still doesn't work! I have regularly updated Fedora like everyone else but since Kernel 5.6.7, Fedora 31, it no longer works. How's the situation going? Can I believe that something I don't know is missing?
-
I'm having another problem, dnfdragora update is no longer working, continues to always give me 10 updates to do but when I open it, instead of loading the list of available updates, it passes them below with a bar that fills up but in reality it does not does nothing because then I find them the same if I reopen the application or when I log in for a new session ... I don't know if it depends on the Kernel that I am using, being that I cannot use the current 5.6.8, the fact is that now it doesn't go anymore ...
-
Kernel 5.6.8 with AST GPU
-
I tried to remove the Xorg file that contains the enabling of the Navi 10, so in theory the AST of the Blackbird had to start, but nothing, it does not start the same with the 5.6.8 kernel ...
-
Excuse me, but does the DNFDragora 32 update application work for you? I don't like it, when I open it, it fills a lower bar that shows the applications that there are to update but it doesn't do anything, nothing appears in the list, you can't interact with any button of the application and when it finishes scrolling this lower blue bar, the application closes by itself and doesn't update anything. As a matter of fact, if I reopen DNFDragora, I find new applications to update and it does the same things it did before... There's a bug in Fedora 32's DNFDragora as well?
-
I downloaded the Fedora 32 ppc64el Workstation image (from here (http://mirror.math.princeton.edu/pub/fedora-secondary/releases/32/Workstation/ppc64le/iso/)) but got "kernel error" when I tried to load it via Petitboot—anyone else notice the same?
An Ubuntu Server 20.04 image worked fine.
-
I downloaded the Fedora 32 ppc64el Workstation image (from here (http://mirror.math.princeton.edu/pub/fedora-secondary/releases/32/Workstation/ppc64le/iso/)) but got "kernel error" when I tried to load it via Petitboot—anyone else notice the same?
An Ubuntu Server 20.04 image worked fine.
Does it happen with the Server edition? For my case I upgraded from Fedora 31 so I am unsure.
-
Excuse me, but does the DNFDragora 32 update application work for you? I don't like it, when I open it, it fills a lower bar that shows the applications that there are to update but it doesn't do anything, nothing appears in the list, you can't interact with any button of the application and when it finishes scrolling this lower blue bar, the application closes by itself and doesn't update anything. As a matter of fact, if I reopen DNFDragora, I find new applications to update and it does the same things it did before... There's a bug in Fedora 32's DNFDragora as well?
I can confirm that the app works fine for me.
-
No, the list of updates no longer appears to me, I don't know at this point if the fault lies with the fact that I have to use the Kernel 5.5..0.RC1 + to make the Navi 10 work and that on the new Kernels it still doesn't work unfortunately ... If they don't fix the bug for Navi 10 first, I can't use the new Fedora 32 Kernel ...
-
Works fine for me, too. Kernel 5.4.
-
MPC sorry but are you by chance using Kernel 5.4.0.2 what time ago Merklot posted and that was already Fedora 32? I before using the 5.5.0.rc1 + I installed that and it was fine as well with Navi patch, in case I never install that too ...
-
Yes, it's the patched Kernel. 5.4 works, 5.6 works. I hardly guess 5.5 works, too.
-
ok then I will also put that Kernel at the moment, I had already used it before, it works well. Thanks, tonight I'll install it.
-
I guess, this won't solve your problem ...
-
I tried to reinstall all Fedora, until now the update I had done on a secondary Hardisk and then I did the update on this to do all the tests, I put the Kernel 5.4.0.2 but the dnfDragora problem does not change, always the same! I honestly don't understand what the hell it has, I haven't touched anything from 31 to 32 and yet it doesn't work anymore! No button is available apart from TERMINA and nothing appears in the list ...! I can't understand why it works for you and not for me, is there any option to touch on Fedora 32 that I don't know? I'm not really understanding anything ...!
-
I tried to reinstall all Fedora, until now the update I had done on a secondary Hardisk and then I did the update on this to do all the tests, I put the Kernel 5.4.0.2 but the dnfDragora problem does not change, always the same! I honestly don't understand what the hell it has, I haven't touched anything from 31 to 32 and yet it doesn't work anymore! No button is available apart from TERMINA and nothing appears in the list ...! I can't understand why it works for you and not for me, is there any option to touch on Fedora 32 that I don't know? I'm not really understanding anything ...!
I do not know for sure. I highly recommend you try to install Fedora 32 under a VM (libvirt/qemu/kvm) and see if dnfDragora works with stock configuration.
-
Hi, sorry what do you mean to install Fedora on a VM? What exactly is it? I'm not a Linux expert ...
-
Hi, sorry what do you mean to install Fedora on a VM? What exactly is it? I'm not a Linux expert ...
I was implying about installing Fedora virtual machine with libvirt/kvm/qemu. You can check out virt-manager (https://virt-manager.org/) if you are after an intuitive GUI
-
TLE, I have no installation problems because I already use 2 separate and separate Hardisks, one is an SSD where I use the main one and then a spare mechanic that I need to do tests like this that I did or test Fedora 32 before this and then when I saw that it's okay, I update the first one or SSD. Only at the moment I am seeing that this Fedora 32 has 2 problems, the first is that Kernel 5.6 has a bug to make Navi10 work which causes it not to work completely, now it is out 5.6.10 but the problem persists, the developers to date they are still not applying the correction published by Daniel and it is not known when they will. The second problem is that dnfdragora does not work for me personally and this is very strange because it works for you and it doesn't for me and I would like to understand why. I tried to contact the Fedora team to let them know about these problems but I did not find anything in the contacts that leads to writing a simple e-mail to warn them of the situation!
-
You could try to re-install dnfdragora. BTW, if the Software Center works, you don't need dnfdragora.
-
Software Center works, in fact some updates if you do them from that and actually does not need dnfdragora, the fact remains that it is very strange that it does not work for me and you do, I have not done anything different from you. Except that I was thinking, the problem lies in the Server version. It seems to me that you are already using the workstation version while I use the Server version then with the addition of the graphical interface and maybe that's the problem. The server version has dnfdragora with a bug and therefore does not work properly and if not before they correct it it will never work. So Kernel 5.5 had nothing to do with the problem, I thought about the kernel at the beginning because I saw that the only difference between mine and MPC's was this but then I saw that both MPC and others, you are using the workstation version and therefore I deduce that the problem is in the Server version. Do you know how to contact Fedora staff to report this? I have not found direct contacts ...
-
I use the Server-Edition. And now?
-
Strange MPC, when you published your Kernel tests I read Workstations edition ... In fact I tried to use it by downloading it but it still seems that it is not complete and I think you have to wait for the final version. Honestly at this point I don't understand why it doesn't work for me ... Sorry do you know the commands to update from the terminal? I know you have to refresh with "sudo dnf update --refresh" first. Then what command do you use?
-
I also installed successfully Fedora Workstation (https://alt.fedoraproject.org/alt/).
-
I also downloaded it before putting the server edition but at the time of launching it it gave me an error, I don't know if it did it because it had not been copied well to disk, the fact is that I then downloaded the server edition again. Later I will make another ssd hardisk bigger than the current one with a Workstations edition. At the moment I have to understand how to update also via terminal ...
-
The working Navi patch is included as of Kernel 5.6.13 (https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.13).
-
Yes I read your post on Twitter, hopefully well then. We're currently at 5.6.10, I think we'll have to wait a while... Thanks for the information!
-
In any case I had not seen well that by doing the command "sudo dnf update --refresh" the system sees all the updates that are there and then asks if you want to install them. It can be used as an alternative to dnf dragora and software center. I am updating both via terminal and via software center.
-
I've tried out the Fedora 32 Workstation Live USB, sadly it does _not_ work. I've sent Fedora team an email to their mailing list https://lists.fedoraproject.org/archives/list/ppc@lists.fedoraproject.org/thread/FYTZDTC4BCZDIC7Y7UCUZQ4EDDGBVAGY/
And the response is:
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.
-
I downloaded the Fedora 32 ppc64el Workstation image (from here (http://mirror.math.princeton.edu/pub/fedora-secondary/releases/32/Workstation/ppc64le/iso/)) but got "kernel error" when I tried to load it via Petitboot—anyone else notice the same?
An Ubuntu Server 20.04 image worked fine.
To workaround this issue, at Petitboot prompt, please edit the Fedora 32 boot option (press e key after moving the cursor to the entry):
Kernel: ppc/ppc64/vmlinuz
Initrd: ppc/ppc64/initrd.img
-
Tried Kernel 5.6.13 and this doesn't work either. It ends up that at this rate it will never work if someone does not tell the Fedora team that this damned Kernel has a bug in the management of the Navi10, it is not normal that you put support for a graphics card and then you do not solve a small bug that it doesn't make it work, you might as well not put it on the PAtch ...! I will also try to write to that address that Tle posted to see what they answer ...
-
I don't know what your problem is, but the Kernel (Fedora 31) works. Thanks again to q66.
-
MPC I'm talking about the Fedora 32 kernel. If they say they have included the Navi 10/14 patch in the new Kernel, does this mean that the new Fedora 32 kernel must also work or am I wrong? What's the point of inserting a patch if you don't notice that there is a bug and you don't even fix it? I'd like to apologize ... Fedora 31 leave him alone right now. I also use both the modified Kernel 5.5 and the modified 5.4, both have the patch without bugs, but I would like to use the current kernel since they have inserted the patch on that too ... Obviously the correction that Daniel did, they did not still not even looked ...
-
The Kernel is the same no matter which Fedora version is in use.
-
In any case, I wrote directly to them, through that link that posted the friend TLE, I joined the Fedora group and I sent a post to explain the problem, let's see what they answer me. It is always useful to be in contact with them for this and other possible bugs that will arise and will also explain to them the problem encountered by dnfdragora ...
-
Sorry guys, in one of his hard disks where I have Fedora Installed, some time ago to delete the old Kernels I made a mistake or I deleted besides the entries Kernel and Kernel-Core, also the voice Devel and so from what moment on, when updates come, the kernel no longer updates. How can I get the Kernel update back? What should be reinstalled and how? Thanks
-
Hi guys, I finally managed to solve some problems on Fedora 32. I always thank the precious help of my friend MPC 7500 because it always gives me excellent supports to understand many problems. The Kernel problem was that the official Fedora 32 ones do not deactivate the Blackbird GPU when the loading ends and I believed that the system was blocked at that point and instead I had to manually switch to the other monitor output where there is the Navi 10 GPU is connected. The modified Kernels 5.4.0.2 and 5.5.0.RC1 + instead detach AST and the monitor at that point switches the video output from the source where it receives the signal and then goes automatically to the Navi 10. Thanks still at MPC. As for DNFDragora, I found a forum where they had the same problem, or switched to Fedora 32 from 31, Dragora was no longer working. They thus advised to run a command that reads as follows: mv /home/mauriziop9/.config/dnfdragora.yaml /home/mauriziop9/.config/dnfdragora.yaml.old
Obviously after the Home directory, everyone has his name, this is the example in my case. In any case, after this I started Dragora that after uploading those files that it usually does, it has not closed by itself and has given me the various buttons available again and has remained open so I believe that now it finally works for as it should.
-
I have also connected both GPUs to my display. But no matter which Kernel I was using (Kernel 5.4/ 5.5 or Kernel 5.6.13+) I always had to manually switch between the GPUs.
I think that in my case both GPUs are active after switching on. Because every now and then (very rarely) the display switches to the AMD GPU at startup.
-
sorry let me understand, you directly start the AMD GPU rarely but how? At boot to load petit boot can not because the drivers are in the kernel of the operating system, therefore it can not be activated before ...
-
Turned on the Computer. The display switched automatically to the AMD port. Then I got a black screen and I had to switch manually to the AST port to get a screen. After Petitboot I have to switch back to the AMD.
Normally -> Power on -> switch automatically to AST -> after Petitboot switch manually to AMD.
-
understood now, no from me the monitor detects the first output that is active and therefore AST. Then if I use modified Kernel 5.4 or 5.5, then AST is deactivated at the end of the loading of the operating system and at that point the monitor turns black. After a few seconds Navi 10 is activated and the monitor sends the video of Navi 10. With the official Kernels instead AST remains active always and that's why I didn't realize. I asked the Fedora team if it is possible to have this type of function also on the official Kernel or at the end of the upload, disconnect AST
-
Guys I just updated the Kernel to 5.7.6 but it seems that at least for the moment, it doesn't work on 10/14 Ships... I don't know if you've had a chance to try it too, maybe the MPC friend will have had a chance to get the same feedback...
-
The Kernel works.
-
Then I will have had a display problem on the monitor ... I have to see and test better, thanks for the news MPC
-
No guys, the new 5.7.6 kernel doesn't work for me. I also tried to update the other spare Fedora 32 which has a mechanical Hardisk instead of an SSD, but the result does not change. The thing, however, that I understood thanks to the mechanical hardisk is that this time it just doesn't load the operating system. When I use the mechanic, obviously it takes a few seconds to load and you can also see it regularly charging Fedora 32. In this case instead, as soon as I try to start the one with version 5.7.6, as soon as it enters loading it stops almost immediately and ends , stay planted. I don't know if there is any conflict with something that I normally use and that annoys this Kernel, otherwise I won't explain it as up to now and until version 5.6.19, no problem ... I don't know whether to wait for the next version or write to the Fedora team for help ...
-
FWIW there is another bug in the 5.7+ kernels with the amdgpu driver, see https://gitlab.freedesktop.org/drm/amd/-/issues/1171, but workaround exists.
-
Unfortunately up to version 5.7.9, the kernel does not work having mounted the Radeon 5700 Navi 10, I hope that at least with 5.8 they solve this situation ...