Raptor Computing Systems Hardware > Blackbird
[amdgpu] [Fiji] Fedora 32 Linux kernel 5.7.x crashes
MauryG5:
I doubt you will have the drivers available in a short time to be able to use big ships on Power ... For Navi 10/14 we had to wait a long time ...
pocock:
Which drivers?
Something in the kernel or something in Xorg?
For some things, like OBS Studio, the code was there but nobody had created a package. If it is a problem like that then it is very easy for me to make a package and put it in a repository.
If you can provide specific links to mailing list discussions or changelog entries that can help me understand the actual issues involved.
pocock:
I found a Phoronix article about RX 6000 support on GNU/Linux
It looks like the issues are the same for every architecture, not only POWER9
Some things are already done, for example, the kernel 5.9 is in Fedora 33. Debian stable-backports has 5.8 but sooner or later it will get 5.9.
The other things mentioned in the article (LLVM, GFX, Mesa) appear to be available in Debian unstable so it may be possible to simply run unstable or backport them to buster.
People can actually upgrade to Fedora 33, upgrade to Debian unstable or start running the newer kernel and/or preparing backports of these things before getting the RX 6000 series cards. So you can see if everything else on your computer works normally with the new kernel and libraries before spending money on hardware.
Once you have all that software installed/upgraded, you may simply be able to insert the card and it works immediately, whether you are on x86 or POWER9
MauryG5:
I hope that's how I tell you. Before using Navi 10 we had to wait months and among other things they had to compile a custom kernel before it became usable in the official one. In any case to date the Navi 10 problems on new kernels continue and they told me that it must be one of you Power developers who must find the problem because AMD doesn't even consider us ...
pocock:
There are many bugs that are not so hard to fix.
Sometimes a bug that is only visible on one platform today reveals a quality issue that might cause future problems on other platforms. Experienced developers usually know this and will be keen to resolve it if they have some hints from the people impacted by the bug.
It is related to the thread I started about having a critical mass of developers. It is also a chicken-and-egg problem: the more developers tinkering with things on the platform, the more attractive it is for additional developers to join.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version