Raptor Computing Systems Community Forums (BETA)
Software => User Zone => Topic started by: MauryG5 on November 30, 2019, 04:39:07 am
-
Hi everyone, I would like to use my graphics card on my Blackbird system but I didn't understand some passages. They tell me to take the files with the .BIN extension and put them in / lib / firmware / amdgpu but the problem is that I don't know where to take this line or directory, I didn't understand what the / lib / firmware / amdgpu line is exactly, how to put all the .BIN files downloaded. Does anyone know how to proceed? Thanks
-
I don't really know what you're working with, where you are or what instructions you're following. I am also not an expert on this subject. However, with help from the IRC channel, I do have an AMD GPU working with my Blackbird. To help everyone:
Which walkthrough/instructions are you following? Link?
Which distro of Linux are you using? (Typically the Linux distro will have a set of packages available with GPU drivers that you can set up, which can save you significant work in getting that part set up, or at least get you 90% of the way there. Some like Debian will separate that package from the default set of package repositories, as Debian does with "non-free" packages (https://www.debian.org/distrib/packages#note).)
Are you comfortable with using gnome-terminal or xterm?
-
Hi, thanks for the reply, I'm using Fedora 31, recognize my AMD 5700 XT Navi 10 card, I just have to activate it and make it work because at the moment I still haven't managed to make it work and I still have to use the Blackbird HDMI video output . As an ambitious use of GNOME and I like it a lot, I am very well. Raptor told me to take the binaries that are currently related to my GPU and put them all in lib / firmware / amdgpu, only I don't know where to find this path, I didn't understand how to do ...
-
In situations like this it can also be helpful to post dmesg output from the failed driver load, if you can get it. Most Linux drivers are pretty clear about what firmware file(s) they are missing for the installed hardware, and that can help people here figure out the proper instructions.
-
linux-firmware on Fedora 31 has navi10 .bin files. You're likely not missing firmware files.
-
I also imagined that Fedora 31 already had something pre-installed since the card is recognized perfectly, the problem is that I don't know how to activate it, I can't understand how to make it operational ... Raptor says that from the next firmware of the Blackbird, it will be possible to activate it but they also say that we have to wait for the Q1 of 2020 which I think is a bit long to wait and so I wanted to understand if it was possible to do it already without the need to wait for the new firmware ...
-
I also imagined that Fedora 31 already had something pre-installed since the card is recognized perfectly, the problem is that I don't know how to activate it, I can't understand how to make it operational ...
You need to share some logs before we can help triage this.
madscientist159's suggestion to share dmesg (http://www.linfo.org/dmesg.html) output (tutorial (http://www.howtoforge.com/linux-dmesg-command/)) which you can pipe to a file, and share with us via a link with a service like dpaste (http://dpaste.com/) would be a good start.
Raptor says that from the next firmware of the Blackbird, it will be possible to activate it but they also say that we have to wait for the Q1 of 2020 which I think is a bit long to wait and so I wanted to understand if it was possible to do it already without the need to wait for the new firmware ...
Slow down a bit. It sounds like you're talking about the bootloader, aka petitboot, which starts before you load Linux. It sounds like you really want to get the GPU working on Fedora. These are two different problems.
For yourself and future visitors, there is a Wiki for troubleshooting GPU problems (http://wiki.raptorcs.com/wiki/Troubleshooting/GPU#I_want_Petitboot_via_AST_but_the_subsequent_Linux_OS_console_on_a_discrete_GPU) on Talos and Blackbird hardware. That's a good place to check for specific issues you come across, and tips to diagnose.
I've found that this page is a little Debian/Ubuntu focused at the moment, owing to many users of Raptor hardware being users of Debian, though the advice should be applicable for all Linux distros.
-
Maybe I didn't know how to explain myself. I don't know the procedure you're talking about, unfortunately I'm not a Linux expert, I'm just learning to use it now. I need to understand simply how I can activate my AMD Radeon 5700 XT GPU, which the system recognizes perfectly (including 3D acceleration). I need to figure out how to tell the system, which has to use that to give me the video output, thus activating me, both the HDMI output and the others present in the graphics card. My problem is only this ... If there is also the procedure for Ubuntu it is fine as well, I have also installed the one in another HD, I am mainly interested in Fedora but if you know it for Ubuntu, it's ok anyway, meanwhile I begin to understand how to use the GPU ... Thanks
-
You may not be able to use the embedded GPU and the AMD GPU at the same time. There may be DMA issues in having both enabled at the same time.
See: https://wiki.raptorcs.com/wiki/POWER9_Hardware_Compatibility_List/PCIe_Devices#AMD
See: https://wiki.raptorcs.com/wiki/Troubleshooting/GPU#Workaround_1:_Disable_on-board_VGA
Note, as the second link says, it may be necessary to disable the embedded GPU by putting a jumper cap on a specific place on the motherboard. Reference page 37 of the Blackbird manual: https://wiki.raptorcs.com/w/images/c/ce/C1P9S01_users_guide_version_1_0.pdf
There isn't a spare jumper there, so if you don't have one (maybe from the back of a junk IDE hard drive), then you may need to buy some: https://www.amazon.com/dp/B00N552DWK/
Hopefully you don't need to disable onboard. More on that later.
That being said, there's a couple of other notes regardless:
Many AMD GPUs do not honor PCIe device resets, so you might have something working one boot, and not have output after a reboot (vs shutdown and fresh power up). Newer versions of the amdgpu driver have a workaround to reset the card, but for a lot of cards, this seems to work exactly twice. This is probably not what's causing your card to no work in Fedora 31 right now, but this may be interfering with some of your tests if you're rebooting every time. Personally, I'm "avoiding" the issue by configuring skiboot to go through a full power cycle when requested to reboot (run in bootloader):
nvram -p ibm,skiboot --update-config fast-reset=0
Xorg (typically your display server) does some really weird things when multiple GPUs are active. Usually I find that having displays on both GPUs causes both GPUs to need to render the whole desktop (to then show only the part that they are displaying), but doing this usually limits your performance or features to that of the lesser card. Someone on IRC said they had an AMD GPU working with the embedded AST GPU, but they were missing gamma (display brightness) in having both enabled. Since you're using GNOME, you might be using Wayland, which may behave differently (I'm not well versed in Wayland).
You need firmware in your bootloader if you want your bootloader to display, but it may not play nicely with your Linux OS, anyway. Your bootloader probably doesn't display out your AMD GPU. I'm guessing you're using the embedded HDMI because of this. The bootloader is itself another Linux environment with the amdgpu driver, and will want firmware to actually enable the card. The firmware is not already included because it's not open source/auditable and because there isn't enough space to generically include all GPU firmware. Raptor might be telling you to copy the amdgpu firmware into the bootloader to get the bootloader to display, which isn't necessary to get your Linux OS to display. However, AMD cards do not accept firmware more than once (with resets being a possible exception). The specific issue I ran into after installing firmware is:
- the bootloader would display on a fresh boot
- Fedora's amdgpu would reset the card and load their more up to date firmware
- I'd reboot and the bootloader (having an older amdgpu driver that doesn't reset the card) would fail to load the firmware and panic.
Some of us are avoiding these sorts of issues by not installing GPU firmware into the bootloader. I use serial console when I need to interact with my bootloader (serial console will work regardless of functioning GPU, too).
We'll learn more from dmesg (the command that shows Linux kernel logs).
Please:
If Fedora boots and you have a desktop on the embedded GPU, please open a terminal (search "terminal" in GNOME) and run:
dmesgand copy-paste the output here into a code block.
If Fedora boots, but finally ends up at a black screen or something, switch to a virtual terminal by pressing ctrl-alt-F2 (ctrl-alt-F1 will go back to the first desktop on Fedora, or ctrl-alt-F7 on Ubuntu). When you're at a virtual terminal, log in and run:
dmesg | fpaste then go to the link it outputs on another computer, and copy the output from the link (link is only valid for a day).
If Fedora boots but breaks such that you cannot go to a virtual terminal on the embedded card, reboot, press "e" (edit) in bootloader before booting, and add the following to cmdline to temporarily disable using the AMD GPU at all:
rd.driver.blacklist=amdgpu modprobe.blacklist=amdgpu rd.driver.blacklist=amdgpudrmfb modprobe.blacklist=amdgpudrmfbthen, instead of dmesg, run the following and paste that output:
sudo cat /var/log/messages
If you're having a different issue, please give more details.
We'll suggest a fix if dmesg makes it clear why the GPU doesn't start.
-
Hi, I currently use the HDMI video output integrated in the blackbird obviously because it's the only one I can use because if I try to insert the HDMI cable into the 5700 XT output, it doesn't work at the moment. I will try to execute that command and send the result here in the discussion and we'll see what the system says. Thanks
-
you don't need to do any of these complicated things, nor you need to load firmware anywhere, etc.
all you need to do is
1) have your petitboot menu on onboard graphics
2) have the booted OS switch to dedicated graphics - there is no PCIe device reset stuff since the driver was not previously loaded on petitboot screen
to make the final booted OS use the dedicated graphics, you need to add modprobe.blacklist=ast video=offb:off on your kernel command line and that's literally it
-
q66:
PCIe device resets will still affect reboots. It affects me even having the AST GPU disabled by jumper.
Was going to suggest blacklisting ast once it was clear that it was the issue. Other people have AST and AMD working at same time. Also add:
rd.driver.blacklist=astbecause modprobe.blacklist doesn't blacklist from dracut initrd.
I am also not certain that blacklisting it (not jumper disabling) solves DMA issues.
-
AMD GPUs deal fine with reboots as long as the driver/firmware wasn't previously loaded as a different version, I've been using fast reboot for as long as I can remember on both Talos and Blackbird and there have been no issues whatsoever.
Just using `modprobe.blacklist` works fine. Void uses dracut and there have never been any issues with that, nor I experienced them on any other OS. It's a parameter passed on the kernel, and any call to `modprobe` regardless of whether from initramfs or from the target system will not load it unless overridden, and the kernel will not auto-load it either.
DMA issues (assuming you need the 32-bit DMA thing) are a completely unrelated thing and will affect very few people.
Also, RX 5700 cards are extremely problematic on Linux right now (even on x86). To get anywhere near having a remotely stable experience, you need a patched kernel 5.4, LLVM 10 from svn, and mesa from git built against this LLVM, any other configuration will result in frequent hangs (https://gitlab.freedesktop.org/drm/amd/issues/892)
-
AMD GPUs deal fine with reboots as long as the driver/firmware wasn't previously loaded as a different version, I've been using fast reboot for as long as I can remember on both Talos and Blackbird and there have been no issues whatsoever.
You and I discussed this on IRC before. RX Vega 64 is still subject to the two reboot issue even if firmware version hasn't changed.
Just using `modprobe.blacklist` works fine. Void uses dracut and there have never been any issues with that, nor I experienced them on any other OS. It's a parameter passed on the kernel, and any call to `modprobe` regardless of whether from initramfs or from the target system will not load it unless overridden, and the kernel will not auto-load it either.
Ah, okay. I probably made a typo when I had issues in the past, then...
Also, RX 5700 cards are extremely problematic on Linux right now (even on x86). To get anywhere near having a remotely stable experience, you need a patched kernel 5.4, LLVM 10 from svn, and mesa from git built against this LLVM, any other configuration will result in frequent hangs (https://gitlab.freedesktop.org/drm/amd/issues/892)
I was unaware.
-
Either way, before trying anything complicated, I'd simply try blacklisting ast (and disabling offb, as the firmware "helpfully" emulates openfirmware framebuffer by default so you'll get output on ast even if the driver is not loaded) and see whether that does anything. 95% chance it will, and if it doesn't, only then I'd try any further steps.
Definitely don't try to load any firmware into BOOTKERNFW or whatever right now. You don't really need any of that *unless* you want the Petitboot screen to show up on dedicated graphics and even then I wouldn't exactly recommend it since the drivers are problematic with that stuff.
-
I entered that command you told me but it tells me unknown command, I am in root mode in the command shell. I entered modprobe.blacklist = ast video = offb:
says that modeprobe.blacklist is an unknown command ...
-
I'm concerned about offering more advice when you don't seem to know how to get logs out of your system to confirm the problems that we are trying to diagnose.
I've tried giving links on how to use the dmesg command line app from a shell. I'm not certain where you are stuck, or if you are at a point where using the shell is completely foreign to you.
Modifying the bootloader arguments is only a small step up from that in difficulty. If you're going to have trouble using a text editor as root to modify a configuration file, we'll have to direct you towards being more familiar with a Linux shell before offering more advice.
I suggest referencing Zed Shaw's command line crash course and getting familiar with that before we try to get your GPU up and running with Fedora 31. You can find a PDF of that over here; https://www.computervillage.org/articles/CommandLine.pdf (https://www.computervillage.org/articles/CommandLine.pdf)
-
the command I executed, the list is very long and does not go all into a post, I created a file with libreoffice and inserted it all into that file. I didn't post it right away because I was trying with the modeprobe command but it doesn't work because it asks me to specify an argument like -d, -e etc. etc. I try to post the file containing the dmesg command
-
stuff like modprobe.blacklist and so on goes on your *kernel* command line, i.e. petitboot will pass it as extra parameters to kernel on boot. So you need to make sure it gets put in grub.cfg or whatever you're using (usually done using /etc/default/grub). Alternatively, it can be manually appended from petitboot by modifying the menu entry.
-
DMA issues (assuming you need the 32-bit DMA thing) are a completely unrelated thing and will affect very few people.
They're also fixed in 5.4 official. I'm running one of my desktops with 5.4.0 and a Vega 64, no problems and no DMA limitations. Note this has to be 5.4.0 or higher; the 5.4-rc series did have a bug leading to GPU crash / EEH. 5.3.x and below didn't enable the "64-bit DMA" (while GPU DMA is actually 40 or 48 bit for the most part, the kernel was limiting it to 32-bit) -- this worked well enough but did cause issues if lots of windows were open at once.
Also, RX 5700 cards are extremely problematic on Linux right now (even on x86). To get anywhere near having a remotely stable experience, you need a patched kernel 5.4, LLVM 10 from svn, and mesa from git built against this LLVM, any other configuration will result in frequent hangs (https://gitlab.freedesktop.org/drm/amd/issues/892)
Honestly, given the state of the software stack, I'd recommend the OP get an older card that will just work until the problems are sorted out. Having personally lived through unstable AMD GPU drivers, it's just not worth it -- at the time it was the Polaris/Vega that was unstable, and I eventually fell back to a secondhand RX290 until the drivers stabilized. It's just not worth fighting these kinds of problems -- you do eventually get (short term) data loss when the GPU freezes before you can save whatever you were working on, it's just a matter of time -- again, IME, just not worth it.
Let AMD cook the drivers for a few more kernel revisions before trying it again. ;)
-
wait let me understand, the command modeprobe blacklist I have to put it in the petit boot so I should get out of the operating system, go back to petit boot, exit the list of initial options and where it allows me to type I have to enter the command modeprobe.blacklist, I got it right?
-
You start your computer. At first it looks like this while it scans disks:
(https://i.imgur.com/6c6EDai.png)
Then you'll see what it finds and it'll start counting down. Arrow down to your Fedora entry with the asterisk (*)::
(https://i.imgur.com/gYvvkSw.png)
Press "e" for edit, it'll take you here to temporarily change it:
(https://i.imgur.com/B7Rtjmf.png)
You want to change "Boot arguments". Notice that the options are separated by spaces:
(https://i.imgur.com/I9FDLSF.png)
So you want to add "modprobe.blacklist=ast video=offb:off" without spaces between the equals. This is wrong:
(https://i.imgur.com/Oz0jVKB.png)
This is correct:
(https://i.imgur.com/DJyzVnV.png)
Go to "OK", press enter:
(https://i.imgur.com/uRqBhN6.png)
It'll take you back to the menu, with your change applied (for this boot), press enter:
(https://i.imgur.com/gSAcSvG.png)
Let us know if it fixes it. Next step will be to permanently fix the boot arguments.
-
ok I immediately try and let you know, thank you very much
-
Sidenote: your dmesg output does not indicate error:
[ 2.636093] fb0: switching to astdrmfb from OFfb vga
[ 2.636255] [drm] platform has no IO space, trying MMIO
[ 2.636258] [drm] Using device-tree for configuration
[ 2.636258] [drm] AST 2500 detected
[ 2.636261] [drm] Using Sil164 TMDS transmitter
[ 2.636266] [drm] dram MCLK=800 Mhz type=7 bus_width=16 size=01000000
[ 2.639371] ast 0005:02:00.0: fb0: astdrmfb frame buffer device
[ 2.737473] [drm] Initialized ast 0.1.0 20120228 for 0005:02:00.0 on minor 0
[ 2.859718] [drm] amdgpu kernel modesetting enabled.
[ 2.859755] amdgpu 0000:03:00.0: remove_conflicting_pci_framebuffers: bar 0: 0x6000000000000 -> 0x600000fffffff
[ 2.859758] amdgpu 0000:03:00.0: remove_conflicting_pci_framebuffers: bar 2: 0x6000010000000 -> 0x60000101fffff
[ 2.859760] amdgpu 0000:03:00.0: remove_conflicting_pci_framebuffers: bar 5: 0x600c000000000 -> 0x600c00007ffff
[ 2.859775] amdgpu 0000:03:00.0: enabling device (0140 -> 0142)
[ 2.859995] [drm] initializing kernel modesetting (NAVI10 0x1002:0x731F 0x1002:0x0B36 0xC0).
[ 2.860002] [drm] register mmio base: 0x00000000
[ 2.860003] [drm] register mmio size: 524288
[ 2.860003] [drm] PCI I/O BAR is not found.
[ 2.860013] [drm] PCIE atomic ops is not supported
[ 2.902060] [drm] set register base offset for ATHUB
[ 2.902062] [drm] set register base offset for CLKA
[ 2.902063] [drm] set register base offset for CLKA
[ 2.902064] [drm] set register base offset for CLKA
[ 2.902064] [drm] set register base offset for CLKA
[ 2.902065] [drm] set register base offset for CLKA
[ 2.902067] [drm] set register base offset for DF
[ 2.902068] [drm] set register base offset for DMU
[ 2.902069] [drm] set register base offset for GC
[ 2.902070] [drm] set register base offset for HDP
[ 2.902071] [drm] set register base offset for MMHUB
[ 2.902071] [drm] set register base offset for MP0
[ 2.902072] [drm] set register base offset for MP1
[ 2.902073] [drm] set register base offset for NBIF
[ 2.902074] [drm] set register base offset for NBIF
[ 2.902075] [drm] set register base offset for OSSSYS
[ 2.902076] [drm] set register base offset for SDMA0
[ 2.902077] [drm] set register base offset for SDMA1
[ 2.902078] [drm] set register base offset for SMUIO
[ 2.902079] [drm] set register base offset for THM
[ 2.902080] [drm] set register base offset for UVD
[ 2.902083] [drm] add ip block number 0 <nv_common>
[ 2.902084] [drm] add ip block number 1 <gmc_v10_0>
[ 2.902085] [drm] add ip block number 2 <navi10_ih>
[ 2.902086] [drm] add ip block number 3 <psp>
[ 2.902087] [drm] add ip block number 4 <smu>
[ 2.902088] [drm] add ip block number 5 <gfx_v10_0>
[ 2.902089] [drm] add ip block number 6 <sdma_v5_0>
[ 2.902090] [drm] add ip block number 7 <vcn_v2_0>
[ 2.996953] [drm] VCN decode is enabled in VM mode
[ 2.996954] [drm] VCN encode is enabled in VM mode
[ 2.996955] [drm] VCN jpeg decode is enabled in VM mode
[ 2.996958] [drm] GPU posting now...
[ 2.997016] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[ 2.997043] amdgpu 0000:03:00.0: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used)
[ 2.997046] amdgpu 0000:03:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[ 2.997050] [drm] Detected VRAM RAM=8176M, BAR=256M
[ 2.997052] [drm] RAM width 256bits GDDR6
[ 2.997064] [drm] amdgpu: 8176M of VRAM memory ready
[ 2.997068] [drm] amdgpu: 8176M of GTT memory ready.
[ 2.997111] [drm] GART: num cpu pages 8192, num gpu pages 131072
[ 2.997200] [drm] PCIE GART of 512M enabled (table at 0x0000008000000000).
[ 2.997302] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.997303] [drm] Driver supports precise vblank timestamp query.
[ 2.997469] [drm] ppt_offset_bytes: 3
[ 2.997471] [drm] ppt_size_bytes: 262912
[ 2.999386] [drm] use_doorbell being set to: [true]
[ 2.999451] [drm] use_doorbell being set to: [true]
[ 2.999577] [drm] Found VCN firmware Version ENC: 1.4 DEC: 3 VEP: 0 Revision: 0
[ 2.999584] [drm] PSP loading VCN firmware
[ 3.437470] [drm] reserve 0x7200000 from 0x8000400000 for PSP TMR
[ 3.961257] amdgpu: [powerplay] SMU is initialized successfully!
[ 3.961856] [drm] kiq ring mec 2 pipe 1 q 0
[ 3.961980] [drm] ring test on 10 succeeded in 65 usecs
[ 3.962029] [drm] ring test on 10 succeeded in 11 usecs
[ 3.962103] [drm] gfx 0 ring me 0 pipe 0 q 0
[ 3.962123] [drm] ring test on 0 succeeded in 8 usecs
[ 3.962125] [drm] gfx 1 ring me 0 pipe 1 q 0
[ 3.962132] [drm] ring test on 1 succeeded in 1 usecs
[ 3.962134] [drm] compute ring 0 mec 1 pipe 0 q 0
[ 3.962146] [drm] ring test on 2 succeeded in 3 usecs
[ 3.962147] [drm] compute ring 1 mec 1 pipe 1 q 0
[ 3.962161] [drm] ring test on 3 succeeded in 1 usecs
[ 3.962163] [drm] compute ring 2 mec 1 pipe 2 q 0
[ 3.962178] [drm] ring test on 4 succeeded in 1 usecs
[ 3.962179] [drm] compute ring 3 mec 1 pipe 3 q 0
[ 3.962194] [drm] ring test on 5 succeeded in 1 usecs
[ 3.962195] [drm] compute ring 4 mec 1 pipe 0 q 1
[ 3.962210] [drm] ring test on 6 succeeded in 1 usecs
[ 3.962211] [drm] compute ring 5 mec 1 pipe 1 q 1
[ 3.962226] [drm] ring test on 7 succeeded in 1 usecs
[ 3.962227] [drm] compute ring 6 mec 1 pipe 2 q 1
[ 3.962242] [drm] ring test on 8 succeeded in 1 usecs
[ 3.962243] [drm] compute ring 7 mec 1 pipe 3 q 1
[ 3.962258] [drm] ring test on 9 succeeded in 1 usecs
[ 3.962356] [drm] ring test on 11 succeeded in 37 usecs
[ 3.962377] [drm] ring test on 12 succeeded in 5 usecs
[ 3.989875] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ 3.989986] amdgpu 0000:03:00.0: ring 0(gfx_0.0.0) uses VM inv eng 4 on hub 0
[ 3.989988] amdgpu 0000:03:00.0: ring 1(gfx_0.1.0) uses VM inv eng 5 on hub 0
[ 3.989990] amdgpu 0000:03:00.0: ring 2(comp_1.0.0) uses VM inv eng 6 on hub 0
[ 3.989992] amdgpu 0000:03:00.0: ring 3(comp_1.1.0) uses VM inv eng 7 on hub 0
[ 3.989993] amdgpu 0000:03:00.0: ring 4(comp_1.2.0) uses VM inv eng 8 on hub 0
[ 3.989995] amdgpu 0000:03:00.0: ring 5(comp_1.3.0) uses VM inv eng 9 on hub 0
[ 3.989997] amdgpu 0000:03:00.0: ring 6(comp_1.0.1) uses VM inv eng 10 on hub 0
[ 3.989998] amdgpu 0000:03:00.0: ring 7(comp_1.1.1) uses VM inv eng 11 on hub 0
[ 3.990000] amdgpu 0000:03:00.0: ring 8(comp_1.2.1) uses VM inv eng 12 on hub 0
[ 3.990001] amdgpu 0000:03:00.0: ring 9(comp_1.3.1) uses VM inv eng 13 on hub 0
[ 3.990003] amdgpu 0000:03:00.0: ring 10(kiq_2.1.0) uses VM inv eng 14 on hub 0
[ 3.990005] amdgpu 0000:03:00.0: ring 11(sdma0) uses VM inv eng 15 on hub 0
[ 3.990006] amdgpu 0000:03:00.0: ring 12(sdma1) uses VM inv eng 16 on hub 0
[ 3.990008] amdgpu 0000:03:00.0: ring 13(vcn_dec) uses VM inv eng 4 on hub 1
[ 3.990010] amdgpu 0000:03:00.0: ring 14(vcn_enc0) uses VM inv eng 5 on hub 1
[ 3.990011] amdgpu 0000:03:00.0: ring 15(vcn_enc1) uses VM inv eng 6 on hub 1
[ 3.990013] amdgpu 0000:03:00.0: ring 16(vcn_jpeg) uses VM inv eng 7 on hub 1
[ 3.990094] [drm] Initialized amdgpu 3.33.0 20150101 for 0000:03:00.0 on minor 1
[ 5.999221] [drm] ib test on ring 0 succeeded
[ 5.999846] [drm] ib test on ring 1 succeeded
[ 6.000508] [drm] ib test on ring 2 succeeded
[ 6.001142] [drm] ib test on ring 3 succeeded
[ 6.001793] [drm] ib test on ring 4 succeeded
[ 6.002460] [drm] ib test on ring 5 succeeded
[ 6.003114] [drm] ib test on ring 6 succeeded
[ 6.003773] [drm] ib test on ring 7 succeeded
[ 6.004426] [drm] ib test on ring 8 succeeded
[ 6.005088] [drm] ib test on ring 9 succeeded
[ 6.005720] [drm] ib test on ring 10 succeeded
[ 6.006344] [drm] ib test on ring 11 succeeded
[ 6.006995] [drm] ib test on ring 12 succeeded
[ 19.143576] amdgpu 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
However, there is never a line indicating that amd framebuffer was initiallized, like:
[ 10.849100] amdgpu 0000:03:00.0: fb0: amdgpudrmfb frame buffer device
We'll see once you blacklist AST.
-
Press "e" for edit, it'll take you here to temporarily change it:
(https://i.imgur.com/B7Rtjmf.png)
btw, just FYI, there's no ttyS0 for serial console on talos/blackbird or any openpower hardware, as the kernel does no see a physical serial port; the correct serial console is hvc0 (without a baudrate, as it's not a serial console per se) for powernv, or hvsi0 (baudrate 19200) for pseries machines.
-
btw, just FYI, there's no ttyS0 for serial console on talos/blackbird or any openpower hardware, as the kernel does no see a physical serial port; the correct serial console is hvc0 (without a baudrate, as it's not a serial console per se) for powernv, or hvsi0 (baudrate 19200) for pseries machines.
Oh, interesting. I thought hvc0 was for virtual machines and paravirtualized kernels. I'm now noticing that my console output always includes hvc0 regardless of console=*. Perhaps an effect kexec-ing from the bootloader's kernel? (like /sys/devices/virtual/tty/console/active is copied?)
-
the topic of my kernel boot is: root = / dev / mapper / fedora-root ro rd.lvm.lv = fedora / root rd.lvm.lv = fedora / swap rhgb quiet. if I try to put modprobe immediately after quiet, as soon as I try to reboot it gives me a failure error, if I try to delete the boot topic I just reported above and try to put the one posted by you, the system tries to boot but yes irreversibly blocks. Where am I doing wrong?
-
What error? Maybe post picture?
-
he tells me he can't find the kernel startup argument because I added the line, the photo doesn't let me post it because he tells me that there is a 128k limit
-
there is a 128k limit
https://imgur.com/upload
no account needed
-
he tells me he can't find the kernel startup argument because I added the line, the photo doesn't let me post it because he tells me that there is a 128k limit
We've increased the attachment size limit to 1MB. If your images are larger than 1MB, please rescale down.
Thank you!
-
this is the wording that my system carries, where should I put the line you tell me? Second question, should I put it the same as the one I read in your example or should I just put the modprobe blacklist part?
-
Add to the last line that says "Boot arguments". The original line ends in quiet
You add modprobe.blacklist=ast and video=offb:off
Overall, your "Boot arguments" line will look like:
root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet modprobe.blacklist=ast video=offb:off
-
Ok thanks, i try in this mode. as soon as I did I let you know the result, now I'm still at work, this evening Italian time of course, I'll try and write as soon as I get the result ...
-
guys then I tried to insert the topic, wanted to start but it got stuck in the upload ... only that I'm doing all this without having yet touched anything on the Blackbird, I ask you to confirm if I always have to insert that jumper in the motherboard anyway , before executing this procedure ... otherwise if I don't have to then nothing doesn't work ...
-
Make sure you plug a screen into the AMD GPU, because the AST will not show anything since we're disabling it.
Also remove rhgb and quiet to give us more information about where it gets stuck, if we can see anything.
-
yes the connection I already prepared some days ago because I realized that disables the HDMI output of the Blackbird in fact when it is blocked I selected the second output of the monitor where there is connected the HDMI output of Redeon but nothing was black ... Now I try to eliminate those 2 topics and let you know ...
-
guys nothing to do, I removed quiet and rhgb, exactly after swap I entered the line, I started but nothing does not work and hangs exactly like before when I sent the photo ...
-
Anyone know if Navi is still affected by the (in)famous amdgpu.dc=0 / amdgpu.dc=1 bug? The newest card I have is Vega (specifically to avoid these kind of issues) so I don't have hands-on experience with Navi.
@MauryG5, if you're able to get an Xorg.0.log and a dmesg from the system when it fails to start the display that would be quite helpful. Even if you have to get the dmesg and log from the machine while the on-board HDMI is enabled at least it might provide some clue.
-
the dmesg I published in the previous posts, if you go backwards in the first or second page, you find my post with the whole report of the dsemg that I did attached ... You guys didn't answer me anymore after I told you that that change on the topic in the line at the start of Linux does not work ... What news do you give me?
-
the dmesg I published in the previous posts, if you go backwards in the first or second page, you find my post with the whole report of the dsemg that I did attached ... You guys didn't answer me anymore after I told you that that change on the topic in the line at the start of Linux does not work ... What news do you give me?
Yes, I see that, but I would also need to know if a monitor was plugged in to the card when that dmesg was captured, and also it would be very useful to have the Xorg.0.log file contents from trying to start Xorg while a monitor is plugged in to the AMD GPU.
One of the quirks with AMD GPUs is that they will not start an output they don't think is attached to a monitor (well, not without significant effort, anyway). That means if your monitor EDID is broken, you'll never get output, for instance. Log files will help figure out what is wrong, and if you really want to keep using the Navi card despite the various warnings of instability and general brokeness on the Linux driver stack (again, architecture independent -- x86 is just as bad here) I strongly recommend you either obtain SSH access from another computer, or get a null modem serial cable and attach it to another computer. This is so that you can try various things and get logs without constantly rebooting the machine.
Broken display on Linux has always been a major pain to debug, even on x86 -- I remember spending a long time trying to get nouveau working back in the day on an older x86 box without SSH access; I eventually gave up and got SSH through a laptop IIRC because it was nearly impossible to fix when you have no working display. :)
-
the monitor that I currently use correctly works on both the HDMI ports it has, so I don't think it's monitor. The Blackbird itself works regularly via HDMI on this monitor so I don't think it's monitor. You should explain to me then the procedure to get this Xorg better because I don't know it unfortunately. Some advise me to wait for the kernel in version 5.4, they also tell me that the next Blackbird firmware will allow to enable the card from the beginning ...
-
FYI, I tested this our a month or so ago, with build of the kernel / mesa / etc from git and was never able to get it to to work. I've also just re-tested with Fedora rawhide, and am seeing the same behaviour.
Effectively, the graphics card is detected fine, however no output ports are detected when starting X11, and as a result, no screens are found.
Normally, I'd expect to see something like the following in the X11 log:
[ 716.370] (II) AMDGPU(0): Output DisplayPort-0 has no monitor section
[ 716.370] (II) AMDGPU(0): Output DisplayPort-1 has no monitor section
[ 716.370] (II) AMDGPU(0): Output DisplayPort-2 has no monitor section
[ 716.371] (II) AMDGPU(0): Output HDMI-A-0 has no monitor section
[ 716.404] (II) AMDGPU(0): EDID for output DisplayPort-0
With Navi 10 on rawhide, I instead see the following (no outputs type are even detected, so it doesn't probe them):
[ 1002.413] (II) AMDGPU(0): glamor X acceleration enabled on AMD NAVI10 (DRM 3.35.0, 5.4.0-2.fc32.ppc64le, LLVM 9.0.0)
[ 1002.413] (II) AMDGPU(0): glamor detected, initialising EGL layer.
[ 1002.413] (==) AMDGPU(0): TearFree property default: auto
[ 1002.413] (==) AMDGPU(0): VariableRefresh: disabled
[ 1002.413] (II) AMDGPU(0): KMS Pageflipping: enabled
[ 1002.413] (WW) AMDGPU(0): No outputs definitely connected, trying again...
[ 1002.413] (WW) AMDGPU(0): Unable to find connected outputs - setting 1024x768 initial framebuffer
[ 1002.413] (II) AMDGPU(0): mem size init: gart size :1fe810000 vram size: s:1f7b70000 visible:fd50000
[ 1002.413] (==) AMDGPU(0): DPI set to (96, 96)
[ 1002.413] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)
...
Fatal server error:
[ 1002.416] (EE) no screens found(EE)
So, my assumption right now is that the current code has a bug on ppc64 where outputs ports are not detected properly. Note that I'll do some additional tests this weekend, but I expect this will require some sort of fix changes in the kernel/amdgpu driver.
-
FYI, I tested this our a month or so ago, with build of the kernel / mesa / etc from git and was never able to get it to to work. I've also just re-tested with Fedora rawhide, and am seeing the same behaviour.
Effectively, the graphics card is detected fine, however no output ports are detected when starting X11, and as a result, no screens are found.
Normally, I'd expect to see something like the following in the X11 log:
[ 716.370] (II) AMDGPU(0): Output DisplayPort-0 has no monitor section
[ 716.370] (II) AMDGPU(0): Output DisplayPort-1 has no monitor section
[ 716.370] (II) AMDGPU(0): Output DisplayPort-2 has no monitor section
[ 716.371] (II) AMDGPU(0): Output HDMI-A-0 has no monitor section
[ 716.404] (II) AMDGPU(0): EDID for output DisplayPort-0
With Navi 10 on rawhide, I instead see the following (no outputs type are even detected, so it doesn't probe them):
[ 1002.413] (II) AMDGPU(0): glamor X acceleration enabled on AMD NAVI10 (DRM 3.35.0, 5.4.0-2.fc32.ppc64le, LLVM 9.0.0)
[ 1002.413] (II) AMDGPU(0): glamor detected, initialising EGL layer.
[ 1002.413] (==) AMDGPU(0): TearFree property default: auto
[ 1002.413] (==) AMDGPU(0): VariableRefresh: disabled
[ 1002.413] (II) AMDGPU(0): KMS Pageflipping: enabled
[ 1002.413] (WW) AMDGPU(0): No outputs definitely connected, trying again...
[ 1002.413] (WW) AMDGPU(0): Unable to find connected outputs - setting 1024x768 initial framebuffer
[ 1002.413] (II) AMDGPU(0): mem size init: gart size :1fe810000 vram size: s:1f7b70000 visible:fd50000
[ 1002.413] (==) AMDGPU(0): DPI set to (96, 96)
[ 1002.413] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)
...
Fatal server error:
[ 1002.416] (EE) no screens found(EE)
So, my assumption right now is that the current code has a bug on ppc64 where outputs ports are not detected properly. Note that I'll do some additional tests this weekend, but I expect this will require some sort of fix changes in the kernel/amdgpu driver.
No outputs definitely connected, trying again...
This isn't a POWER problem, this is an AMD GPU driver / hardware problem. We're going to need a lot more info including the monitor model etc. -- last time I saw this you had to flip DisplayCore on or off, but Navi may require DisplayCore to operate at all. If the latter is the case, you'll need to contact AMD support to get the driver fixes.
-
ok Merklort then at this point I stop and wait for you to have more information and possibly something correct before doing any operation, with my very little Linux experience I can't do much ... I stay connected let me know thanks
-
No outputs definitely connected, trying again...
This isn't a POWER problem, this is an AMD GPU driver / hardware problem. We're going to need a lot more info including the monitor model etc. -- last time I saw this you had to flip DisplayCore on or off, but Navi may require DisplayCore to operate at all. If the latter is the case, you'll need to contact AMD support to get the driver fixes.
Yes, agreed, it's a problem with the driver (again, I'm assuming it's only a driver issues on ppc64le and not x86_64, but that's only an assumption) as it's not even detecting that there's anything that a monitor could be plugged into.
Note that I did test with amdgpu.dc=1 and amdgpu.dc=0 and there was no change, however my understanding is that navi only works it enabled like you said
Do you know the best way to contact AMD about this? I can run through the appropriate channels to try to get the support improved.
-
no I personally no, since you are more competent in the matter, see if you can understand how to communicate these problems to them. What I would like to understand instead is, AMD only develops for X86 as a rule, how do you request drivers for Power? Also on the site there are only those for X86 ... Maybe they release the source code because they are open source and then someone then develops the drivers for Power or what?
-
but instead I was also thinking about the procedure that Raptor published on Wiki but I didn't understand. This is the configuration of the Xorg.conf file, the procedure that allows you to activate the graphics card via Xorg you can post it in detail as you did with that of the petitboot? I would like to understand if it is possible through that to activate the GPU ...
-
No outputs definitely connected, trying again...
This isn't a POWER problem, this is an AMD GPU driver / hardware problem. We're going to need a lot more info including the monitor model etc. -- last time I saw this you had to flip DisplayCore on or off, but Navi may require DisplayCore to operate at all. If the latter is the case, you'll need to contact AMD support to get the driver fixes.
Yes, agreed, it's a problem with the driver (again, I'm assuming it's only a driver issues on ppc64le and not x86_64, but that's only an assumption) as it's not even detecting that there's anything that a monitor could be plugged into.
Note that I did test with amdgpu.dc=1 and amdgpu.dc=0 and there was no change, however my understanding is that navi only works it enabled like you said
Do you know the best way to contact AMD about this? I can run through the appropriate channels to try to get the support improved.
To be honest I'd be very, very surprised if there was a ppc64le specific bug in the AMD display detection. That code is all straight C, and the bit count and endianness both match x86 exactly.
Probably the first step is for anyone seeing this problem on Navi on POWER to try the exact same kernel version on some old / borrowed x86 system with the same card and monitor. If that also shows the same problem, at least when reported to the kernel bugtracker the devs won't immediately assume it's a POWER bug. :)
-
This issue is due to Navi display support only being enabled for X86.
See here: https://github.com/torvalds/linux/blob/v5.4/drivers/gpu/drm/amd/display/Kconfig#L23
And here: https://github.com/torvalds/linux/blob/v5.4/drivers/gpu/drm/amd/display/dc/calcs/Makefile#L27
And here: https://github.com/torvalds/linux/blob/v5.4/drivers/gpu/drm/amd/display/dc/calcs/dcn_calcs.c#L629
Basically, before this will work the following needs to happen:
Either the DC code needs to be modified to use integer math instead of floating point math or
- The kernel_fpu_begin / kernel_fpu_end APIs need to be added for POWER (currently only supported on x86 and s390)
- The KConfig files need to be updated to enable POWER in addition to X86
- The Makefiles need to be modified to not assume x86 (and sse / sse2)
-
This issue is due to Navi display support only being enabled for X86.
See here: https://github.com/torvalds/linux/blob/v5.4/drivers/gpu/drm/amd/display/Kconfig#L23
And here: https://github.com/torvalds/linux/blob/v5.4/drivers/gpu/drm/amd/display/dc/calcs/Makefile#L27
And here: https://github.com/torvalds/linux/blob/v5.4/drivers/gpu/drm/amd/display/dc/calcs/dcn_calcs.c#L629
Basically, before this will work the following needs to happen:
Either the DC code needs to be modified to use integer match instead of floating point math or
- The kernel_fpu_begin / kernel_fpu_end APIs need to be added for POWER (currently only supported on x86 and s390)
- The KConfig files need to be updated to enable POWER in addition to X86
- The Makefiles need to be modified to not assume x86 (and sse / sse2)
Good catch. It's generally considered bad form to use floating point in kernelspace for a number of reasons; this smells a bit more like a move to soft-lock AMD GPUs to AMD CPUs (thankfully one that can be worked around with developer time, but still not a great move).
@mauryg5 I'd return that card if I were you since I'd wager the box didn't mention the drivers only work on x86 (normally having Linux support means the device works anywhere -- I've only ever seen this once before where a device required x86 due to bad quality drivers, and I got a full refund in that case). Either that or try to get a dev or two interested in fixing up the drivers to be properly compatible, but that might require funding the development or waiting for someone to be personally invested enough to make it happen.
-
are you even telling me that maybe we will never have adequate support on the 5700s? This is a serious thing though ... honestly I'm not sure now what to do ... I might first try writing to AMD for clarification, who knows if they can give me some advice ... it would be a shame not to be able to use it after spending 500 euro and even if it is returned cmq a great sin ...
-
are you even telling me that maybe we will never have adequate support on the 5700s? This is a serious thing though ... honestly I'm not sure now what to do ... I might first try writing to AMD for clarification, who knows if they can give me some advice ... it would be a shame not to be able to use it after spending 500 euro and even if it is returned cmq a great sin ...
No, it will eventually gain support, but Navi is still new. The number of Linux developers that have Navi and a non-x86 system are likely not very high. You could offer to loan the GPU and pay a developer to fix the drivers, or wait until market penetration is high enough that developers can pick up a second hand card on eBay or similar for cheap. There's no shortcut here; it's either money or time unless you're lucky enough to get AMD to care about their broken drivers. Our official stance is that a driver broken in this manner shouldn't have been accepted by the kernel maintainers in the first place, or at least marked Experimental.
-
tell me exactly where I have to write, the address of the AMD support that takes care of the drivers, I have to tell them that the drivers currently in use have bugs that do not allow the correct functioning, to fix the bugs so that they can use the their 5700 cards without problems ... am I right?
-
I've filed a bug report here, feel free to add comments to it:
https://gitlab.freedesktop.org/drm/amd/issues/984
-
ok thanks, in any case I'll try to write directly to AMD to let him know this problem, I want to see what they answer me ...
-
I wrote to AMD support, I told them everything, let's see what they answer ... I also said that the drivers currently have problems and that they need to be reviewed, I also said if it would be possible to receive direct support for Power from them, since the OperPower community they almost only buy their cards ... It will be difficult but I try
-
I wrote to AMD support, I told them everything, let's see what they answer ... I also said that the drivers currently have problems and that they need to be reviewed, I also said if it would be possible to receive direct support for Power from them, since the OperPower community they almost only buy their cards ... It will be difficult but I try
Thanks partly to meklort's initial tracing of the issue, I was able to put together an initial PoC/RFC patch here:
https://lists.freedesktop.org/archives/amd-gfx/2019-December/043611.html
I don't have a Navi card to test with, so if you are able to apply that patch, recompile, and test, I'd appreciate it.
-
no i'm sorry i'm not able to do this, i don't have the necessary skills unfortunately. If anyone has the same card and is able to do it, it would be really good ...
-
@MauryG5
I was able to test the patch from madscientist159 and with some modifications I have the Radeon 5700 XT running my system. We're still working on cleaning up the patch, but Navi is now working on POWER. once we're further along, I'll test on Fedora 31 instead of Rawhide and hopefully get you a kernel build to try.
-
You're giving me good news, thanks a lot to you and Madscientist159 for the work you're doing, you're great! Meanwhile I am exchanging emails with AMD support to inform them about the situation, we hope that they will also move directly ... Monday they will tell me I hope something more ... Let me know then when everything will be ready and what I'll have to do ... Thanks again!
-
I've had success with the patches:
(https://i.imgur.com/WH9MMoI.png)
That said, I had to build LLVM from git as well as Mesa from git, because otherwise Navi is prone to hanging right now, even on x86. It could theoretically get solved in a couple weeks with Mesa 19.3 and LLVM 9.0.1, though not sure if LLVM 9.0.1 has the fixes included.
-
so you too are working to make these 5700 good news work. I think that soon you will have the final solution I'm happy ... Let me know when you can use ...
-
guys I just read on Talospace that Navi 10 support for Power is coming, apparently I'm already aware of the excellent work you're doing and have already published it ...! Great!
-
I do read this board too, y'know. :P
-
wow you are the reviewer of Talospace it's a pleasure to have you here and meet you. In this forum you have the chance to get to know the best Power exponents and all this is fantastic! I asked to give me a hand because I own the Radeon 5700 XT and the guys are giving me a great hand, even the great Tim Pearson himself committed himself and I am immensely grateful to him! I read that Phorinix also learned the news, it went around quickly, great! They are testing the work done, they already work tell me how you can read above, as soon as they finish the tests they will tell me how to activate this beautiful GPU ...
-
To be honest I'd be very, very surprised if there was a ppc64le specific bug in the AMD display detection. That code is all straight C, and the bit count and endianness both match x86 exactly.
Thankfully I don't have to do this very often, but...
(http://pearsoncomputing.net/users/~tpearson/personal/thirdparty/images/eating-crow.jpg)
Used with permission by KnoxTNToday.com
In this case my instincts let me down. I had drilled in my head for so long "don't use floating point in kernel space!" that I didn't even think to look for an x86-only guard around the DCN code. I hope the patches make up for it! ;)
I also have a Navi card coming to play with and help make sure things keep working on the POWER systems in the future.
-
In this case my instincts let me down. I had drilled in my head for so long "don't use floating point in kernel space!" that I didn't even think to look for an x86-only guard around the DCN code. I hope the patches make up for it! ;)
No worries. I didn't really have the time this weekend to work on fixing the issue, so it was certainly good to have you work on it and on upstreaming the fixes.
They are testing the work done, they already work tell me how you can read above, as soon as they finish the tests they will tell me how to activate this beautiful GPU ...
Everything seems to be working reasonably well here on Fedora 32/Rawhide. I'll try to do a fresh Fedora 31 install here (making sure everything works) and put together a quick guide on the steps needed to get Navi 10 working in the next day or two.
-
Ok Meclort thank you, I don't know how do you get Fedora 32 since the 31 was released only now but you're at an advanced level so I don't ask for anything hahaha. A special thank you, of course, to the great Tim who took care of writing this beautiful code, after this, I have another card to activate and I will have to open another treed and see if we can do the same with that and I'm sure you will succeed, meanwhile I wait patiently for the procedures ... you are great anyway!
-
Hi guys, AMD support replied telling me that 1, they don't support Fedora but the systems they currently support are: Ubuntu 18.04.3
RedHat Enterprise Linux 8.0
RedHat Enterprise Linux 7.6
CentOS 8.0
CentOS 7.6
SLED / SLES 15 SP1
As far as support for the Power architecture is concerned, they do not even know what they are talking about, contacting the producers to understand which Hardware to use ...! All this in Italy in any case, I don't know in America, but this is the current situation in Italy. I told him that someone is already working to bring the drivers in the Power version and I told him that in any case the first drivers they released are not good and therefore to work to improve them. I finally tried to explain to them what Power is but I doubt they immediately understand what I'm talking about ...
I hope in you at this point ...
-
@MauryG5
I put together something on the wiki that has instructions on building a patched kernel and installing it. You'll also need to follow the information on enabling the discrete display.
https://wiki.raptorcs.com/wiki/Enabling_Navi_10_On_Fedora_31
Let me know if you run into problems.
-
they are quite a few steps and it won't be easy since I'm still a beginner on Linux, I'll try to perform the whole procedure and if I encounter difficulties I'll let you know ... thanks a lot
-
sorry but after installing the development tools, you have to do everything that the custom kernel compile link reports ?? It seems to me very complex for someone like me ... I don't think I can compile it I don't understand anything unfortunately ... you can't have one already compiled?
-
Meklort you have not answered, I wanted to understand this thing well because it is not clear to me not being a programmer as you are. After installing the development tools, can I go ahead and continue the procedure by copying it from the guide, or do I have to go to the Kernel creation link? Because there is my problem because it is difficult for me to do it ... Let me understand ...
-
The best option would be to follow the guide each step should be listed (in bold). Some steps make take a while to complete. I'd suggest giving it a try before falling back to another method.
If you are unable to get it to work, you can try installing the following prebuilt ones from GigabytePro:
https://files.gigabyteproductions.net/srv/devel/linux-navi10/fedora/f32/try6/kernel-5.4.0-2.fc32.ppc64le/kernel-core-5.4.0-2.fc32.ppc64le.rpm
https://files.gigabyteproductions.net/srv/devel/linux-navi10/fedora/f32/try6/kernel-5.4.0-2.fc32.ppc64le/kernel-modules-5.4.0-2.fc32.ppc64le.rpm
You'll need to use rpm -i kernel-core-5.4.0-2.fc32.ppc64le.rpmand rpm -i kernel-modules-5.4.0-2.fc32.ppc64le.rpmNote that while this is the fedora 32 kernel, it should be OK on fedora 31.
-
but sorry, let me understand, the whole procedure you posted on Wiki, is useful if I have not misunderstood, when you personalize yourself and you compile the Kernel from you, while having this ready, theoretically you don't have to do all those passages anymore, but after executing the 2 commands from petit boot to disable quick recovery, download and then install the kernel with the 2 commands you posted right or not? Let me understand why as I repeat I experience zero on Linux and unfortunately I'm not a programmer so I have more difficulty understanding but I would like to learn something slowly thanks to Linux ...
-
Waiting for me to be able to answer the previous question about the already ready kernel, I'm trying to do the procedure you posted on the wiki, when I try to run the git clone command I'm going to post to you, it tells me a fatal error, too many arguments. ..
[MauryPower9@localhost ~]$ cd git
[MauryPower9@localhost git]$ git clone git: //git.kernel.org/pub/scm/ linux / kernel / git / jwboyer / fedora.git --depth 1 --branch kernel-5.5.0-0.rc1.git0.1.fc32
fatal: too many arguments
where is error?
-
Compare your line with the original one.
Original line:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git --depth 1 --branch kernel-5.5.0-0.rc1.git0.1.fc32
Your line:
git clone git: //git.kernel.org/pub/scm/ linux / kernel / git / jwboyer / fedora.git --depth 1 --branch kernel-5.5.0-0.rc1.git0.1.fc32
@meklort: Thanks for the patch. I have another question, after patching the kernel, will it be replaced in the next update of Fedora or will it remain?
-
you're absolutely right MPC and I had even imagined it, only if you see the guide, the command is punctuated by those spaces you see in my line, I copied it exactly as it was ... Thanks anyway ...
-
nothing to do, it returns a fatal error telling me that it is not possible to read from the remote repository ... the connection is there and it is good to the internet ... it tells me to make sure I have the correct access privileges and that the repository there ...
-
So I think the problem is that I'm not creating the custom kernel. The point is that I have to understand how to do that, I need to know what commands to use exactly, to create this custom kernel where the patches mentioned in the guide are to be applied. In the guide there are several operations and I don't know which of those to follow exactly. Maybe I need to run the following commands: $ git clone git: //git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git
$ git checkout -b my_branch kernel-4.7.4-200.fc24
Afterwards I have to execute the command that I posted that before did not work for me because of too many spaces and then continue with the following points. Am I right or is there any other Meklort?
-
@meklort: Thanks for the patch. I have another question, after patching the kernel, will it be replaced in the next update of Fedora or will it remain?
I believe it would be replaced if you update to the official version from the fedora repos. You'll probably want to change the version string to something custom so that it does not get replaced. To do so, I think you'll want to set the CONFIG_LOCALVERSION value in the .config file
CONFIG_LOCALVERSION="amdgpu"
@MauryG5
You'll need to use the bold commands in the guide.
-
Meclort so you do not make me understand unfortunately, first of all, the commands in bold where on the kernel creation guide? If you don't see commands in bold in that guide but only commands written in red and someone written in blue. Then if that's not what you mean then?
-
You only need to copy/ paste the commands e. g.:
First --> cd ~
Second --> mkdir git
Thrid --> cd git
Fourth --> git clone git://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git --depth 1 --branch kernel-5.5.0-0.rc1.git0.1.fc32
It really isn't that hard. You only have to read carefully and then C&P
@meklort: Thanks, I will try it as soon as I have bought a 5700 or maybe a 5500
-
yes MPC those commands I had already executed them, only that as soon as I make the passage number 4, it returns me error telling me that it does not find the repositories relative to the command or that it is missing connection to internet that instead there is and is regular ... I wanted to understand which commands I have to execute before those you wrote, regarding the fedora guide on kernel customization, that's my problem, I don't understand what I have to do at that point, what commands I have to use, in that guide it talks about many things but I don't know which one to use for me in my case ...
-
If I C&P this line from the wiki: git clone git://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git --depth 1 --branch kernel-5.5.0-0.rc1.git0.1.fc32
I get:
...
remote: Enumerating objects: 70582, done.
remote: Counting objects: 100% (70582/70582), done.
remote: Compressing objects: 100% (67516/67516), done.
remote: Total 70582 (delta 5378), reused 29135 (delta 2240)
...
-
ok then I'll do as you say, I copied the exact line but it is possible that I made some mistakes that I didn't see. Thanks for your clarification MPC, I try and let you know
-
Guys then, I'll update you on the procedure, MPC you were right, obviously I was wrong to write some characters and didn't take the commands, I did the copy and I managed to make some commands operational. However unfortunately arrived at the command user @ bb fedora] $ cp /boot/config-*.ppc64le .config, the system returns me error telling me: cp: the objective '.config' is not a directory
I have always done the copy paste exactly as for all the commands up to here carried out and gone to good time ... How come now it gives me error and doesn't make me continue? Where the hell is the mistake this time? :(
-
I hope you insert the line without the dollar sign? ;)
-
I admit not being practical on linux by now you all know it, but some things I still know I can distinguish ... no, I had even tried to write it directly to the command but nothing always knows the same error to me ... :(
MauryPower9 @ localhost fedora] $ cp /boot/config-*.ppc64le .config
cp: the target '.config' is not a directory
[MauryPower9 @ localhost fedora] $
-
What was your previous step?
-
So I'll give you a summary, after doing those steps where I was stuck, I went to the part where you must first download and then apply the kernel patches.
[user @ bb git] $ cd fedora /
[user @ bb fedora] $ wget https://gitlab.freedesktop.org/drm/amd/uploads/f8c299fc4fd373a8cbc380f348204b61/0001-amdgpu-Prepare-DCN-floating-point-macros-for-generic.patch
[user @ bb fedora] $ wget https://gitlab.freedesktop.org/drm/amd/uploads/7d194992837c8706ca5966b682d5680b/0002-amdgpu-Enable-initial-DCN-support-on-POWER.patch
[user @ bb fedora] $ wget https://gitlab.freedesktop.org/drm/amd/uploads/86353afdb43409add84005cef8c5abc0/0003-amdgpu-Wrap-FPU-dependent-functions-in-dc20.patch
[user @ bb fedora] $ git am * .patch
Up to this point no problem, he did everything according to the guide.
Then he tells me to do this command:
[user @ bb fedora] $ sed -i 's / .num_dsc = 5, // g' drivers / gpu / drm / amd / display / dc / dcn20 / dcn20_resource.c
Without this the system has not returned any error to me and so I went ahead in the procedure and I got to the point where it tells me to configure the kernel and to do it you must enter that famous command that I posted and that does not work ... And I got so stuck ... Last step is the command line that you see immediately above or the one where you talk about drivers and diplay ...
-
Original line from the wiki:
sed -i 's/.num_dsc = 5,//g' drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c
Your line:
sed -i 's / .num_dsc = 5, // g' drivers / gpu / drm / amd / display / dc / dcn20 / dcn20_resource.c
Compare. You should really copy&spate the lines
-
it seems strange to me because I copied exactly without touching anything, the line that comes out in my previous message has different spaces but I don't remember that there were in the original that I copied ... very strange ... I'll check this evening and I see if it is actually how it comes out in my message but in any case it has not even returned errors like too many arguments in the line ... I honestly don't understand ... ???
-
MPC I checked the command line you posted, if you notice the original of the guide, you will notice that it is exactly the one I posted, if I do copy and paste, obviously I don't go to think that there are more spaces otherwise I would go to intervene. Also while in the line that you had previously pointed out to me, it gave me error of excessive arguments, in this case it takes the command and makes you continue so I could not imagine ... In any case this evening I try in the mode you posted and then I go to redo the command that gives me the error of which I spoke yesterday, let's see if correcting the previous line, I can go on. But at this point it is necessary to report to Meclort because even when you do the NVRAM update in petit boot, the line which is then reported as a guide also has too much space and consequently the system returns an error. Too much space is found after 0 at the end of the line ...
# nvram -p ibm, skiboot --update-config fast-reset = 0
this is the line with the extra space at the end that makes you get out of error, on this I realized and I corrected it, on the others I made a copy paste and I didn't realize it
-
Guys I rectify my last message, I'm checking the command line that MPC said was different, actually it was copied exactly, only on the forum did it come up with spaces. Such as. you can see the sequence is correct and when I do the cp command, it returns this error to me ... Merklot you have to intervene and let me kindly understand what is happening because I have copied everything as it is done on the guide, it worked everything up to here, now it is strange that from this error ...
-
@meklort: ATM I'm on Fedora 30.
After: make oldconfig I get:
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/confdata.o
HOSTCC scripts/kconfig/expr.o
LEX scripts/kconfig/lexer.lex.c
YACC scripts/kconfig/parser.tab.[ch]
HOSTCC scripts/kconfig/lexer.lex.o
HOSTCC scripts/kconfig/parser.tab.o
HOSTCC scripts/kconfig/preprocess.o
HOSTCC scripts/kconfig/symbol.o
HOSTCC scripts/kconfig/util.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
.config:6025:warning: symbol value 'm' invalid for REMOTEPROC
*
* Restart config...
*
*
* Platform support
*
IBM PowerNV (Non-Virtualized) platform support (PPC_POWERNV) [Y/n/?] y
OPAL PRD driver (OPAL_PRD) [M/n/y/?] m
Enable removal of RAM from kernel mappings for tracing (PPC_MEMTRACE) [N/y/?] n
IBM Virtual Accelerator Switchboard (VAS) (PPC_VAS) [Y/n/?] y
Expose SCOM controllers via debugfs (SCOM_DEBUGFS) [Y/n/?] y
IBM pSeries & new (POWER5-based) iSeries (PPC_PSERIES) [Y/n/?] y
Support for shared-processor logical partitions (PPC_SPLPAR) [Y/n/?] y
Dispatch Trace Log (DTL) [Y/n/?] y
pSeries energy management capabilities driver (PSERIES_ENERGY) [M/n/y/?] m
Scanlog dump interface (SCANLOG) [Y/n/m/?] y
IO Event Interrupt support (IO_EVENT_IRQ) [Y/n/?] y
LPAR Configuration Data (LPARCFG) [Y/?] y
Support for shared-memory logical partitions (PPC_SMLPAR) [Y/n/?] y
Collaborative memory management (CMM) [Y/n/m/?] y
Hypervisor supplied PMU events (24x7 & GPCI) (HV_PERF_CTRS) [Y/n/?] y
Support for the PAPR Storage Class Memory interface (PAPR_SCM) [M/n/?] m
Secure virtual machine (SVM) support for POWER (PPC_SVM) [N/y/?] (NEW)
.config:6025:warning: symbol value 'm' invalid for REMOTEPROC
-
apparently Meclort has abandoned us now ... guys is there someone else who has done this procedure and knows how to solve our problems?
-
In the meantime, could you figure out why the error message pops-up?
Also do you know what this line means?
cp /boot/config-*.ppc64le .config
-
from what I read in the guide serves to configure the kernel ... but I don't know specifically ... I only say that having followed the guide step by step I wonder why it gives me such an error ... The only thing that comes to me from to think is that the steps to create the customized Kernel are missing, but I don't know how to do anything else, I don't know what to think ... I have no idea ...
-
It looks like I'm ready for Navi
-
great ... good ... something that I can't do myself and I still don't understand why ... 😥
-
Googling a little bit
Linux command cp (https://www.cyberciti.biz/faq/copy-command/)
/boot/ is a folder.
config-*.ppc64le is a file.
There seems to be something wrong with this file. Then go to the folder boot and see what file(s) you find with the name config-*.ppc64le. The * is a placeholder. Then you'll understand what the problem is.
-
ok thanks I'll try to do what you tell me ... I hope to find the problem ... the only thing I still don't understand is why there is an error if I simply made the copy paste from the guide ... not I understand...
-
knowing specifically what the contents of the line are, without seeing the guide I go by logic, obviously I can't put a directory in a file but I have to put the file in the directory ... so theoretically I should invert the two things ... correct me if I'm wrong ...
-
Then go to the folder boot and see what file(s) you find with the name config-*.ppc64le.
Googling a little bit
List file names Linux (https://www.cyberciti.biz/faq/linux-list-just-directories-or-directory-names/)
ls /boot/config-*.ppc64le
/boot/config-5.3.16-200.fc30.ppc64le
/boot/config-5.3.16-300.fc31.ppc64le
What's the problem here?
-
apart from the number 200 for Fedora 30, I can't answer to tell you the truth ...
-
Unless seeing your last line, I'm making the mistake of starting the penultimate version of the kernel which is 5.3.15, instead of directly accessing the last one which is currently 5.3.16 ... I was doing it because I feared that an error would then compromise everything and I could no longer restart as it has happened to me in the past ... If this is the problem then I use 5.3.16 and that's it ...
-
So after thinking about it I think I understand that that line of the guide must be changed according to your installed kernel, as you pointed out to me MPC. I used instead of the line: cp /boot/config-*.ppc64le .config, the line: cp /boot/config-5.3.16-300.fc31.ppc64le .config
I realized that it varies according to the kernel in use, thanks to MPC for this clarification. This is why the system has moved forward and made me do the configuration as seen in the guide. After, however, when I am I have entered the command: $ make -j`nproc`
the system tells me that the -j argument requires a positive integer argument and I'm stuck again ... What should I do at this point?
-
The -j tells the build system how many processors the kernel should build for. Since your power9 can do 4 threads/processor slice then multiply the number of cores in your cpu by 4 and use that number. 4 cores = 16, 8cores =32.
make -j 16 is for a 4 core power9
-
nothing to do ... I have the impression that for me it will be more difficult than expected curse ... I tried both ways but it gives me error ...
-
No 'nproc'
make -j 32
-
yes Xlinder if you look at the first line I put the command as you wrote it but nothing has always been an error ... the one with nproc I wrote it just to show that I tried both ... but the first one I did is the yours and gives me error ...
-
make -j`nproc` doesn't give me an error …
Little bit of googling
difference between nproc "make -j" (https://unix.stackexchange.com/questions/208568/how-to-determine-the-maximum-number-to-pass-to-make-j-option)
Google again
fatal error: openssl/opensslv.h: No such file or directory fedora (https://stackoverflow.com/questions/46008624/how-to-fix-fatal-error-openssl-opensslv-h-no-such-file-or-directory-in-redhat)
Quote from the thread
To install OpenSSL development package on Fedora, CentOS or RHEL
sudo yum install openssl-devel
But it's good that you've made some progress on your own.
-
Stepping in...
As stated before, it would help if you took the time to just go through a book or a tutorial on using a shell like bash on Linux to help with these matters.
make -j`nproc`
That's with backticks, as in the character to the left of a 1 and above the "tab" key in a USA QWERTY keyboard layout (https://en.wikipedia.org/wiki/QWERTY). Not apostrophes. These mean different things.
Backticks can be used to execute the command in between before executing the outer command in shells like zsh.
nproc returns the number of available processing units. This tutorial explains how; https://www.howtoforge.com/linux-nproc-command/
So that's equivalent to:
make -j12
On a computer with 12 logical cores.
Either way, you don't really need the -j argument for make. It's to run your build in parallel, to make it faster.
-
Guys, thanks to everyone for the advice, unfortunately I can't complete the operation, I cleaned up the older kernels and maybe some files went away, I don't know why I saw that I cleaned up the old ones without touching version 16 but in anyway now it gives me error when i run the command: make oldconfig that didn't give me before. I broke down and directly installed the ready-made kernel Merklot had given me. Now to see if you enable the graphics card I could make the changes on Xorg.conf.d but I can't get into it. The directory is already there, I should just make those changes to activate the card and I would like to keep both HDMI outputs active or both the graphics inside the Blackbird and if possible finally, that of the AMD Radeon Navi 10 graphics card. Can you tell me you how to do it since from the wiki guide I can't understand how to do it? Thank you
-
I don't know what command you executed. I don't know what kind of error you got.
-
At the moment, let's leave the mistake alone, I'll post it to you later. I'm interested in knowing now how to open and fix the Xorg.conf.d file to tell the system that there are 2 GPUs and that it must use both. To open the file I wanted to understand in the meantime if I can always use the command "sudo gedit /etc/X11/xorg.conf.d or I have to use other. Then what to put for the system to use both GPUs ...
-
https://wiki.raptorcs.com/wiki/Enabling_Navi_10_On_Fedora_31#Configuring_The_Display
AST: At boot (connecting through ssh or a second display
AMD: On desktop
-
MPC so you are not telling me anything, I had already consulted that guide but I did not understand practically anything in particular ... I would like to understand if I have to open that file I was talking about above, if I have to do it via the "sudo gedit" command and what exactly do I have to put in to tell him that I have 2 GPUs to use ... this is my problem now ... I installed the ready-made kernel that posted Meklort so in theory it should be enough just to enable the card and that's it ...
-
MPC I managed to understand the problem of the error that the "make oldconfig" command gave me, I lacked 2 commands one was "bison" the other I don't remember exactly at the moment in any case I installed them both, I installed openssl devel as you told me to do and at that point the make -j 'nproc' command worked and the computer started a lot of kernel building work. Finally I ran the final installation commands and apparently managed to complete everything. Thanks again for your guidance. I just have to understand that activating it via x11, if someone can better explain how to do it, I would be grateful, I am one step away. I have to keep both video outputs because I work with 3 hard drives and 3 operating systems and I always have to select the boot from the petit boot which obviously still works with the integrated video. I need to understand how to activate NAVI 10 and keep the GPU integrated. Unfortunately I don't understand much in the current guide.
-
MPC looks at this, I did all the final steps, it doesn't give me errors but when checking the kernel version it still gives me 5.3.16 ... Where do you think the error is? I guess I didn't understand maybe how to do the last steps ...
-
so guys, I tried to understand how to activate this graphics card through Xorg, meanwhile I learned that on Fedora there is no Xorg file like on Ubuntu or Debian and that therefore it must be created manually. I used gedit and modified everything to look like this. Now before saving I would like to understand if it is composed correctly or I have to modify something. Above I also posted the result of the grep command in such a way as to make you account for the data that are available to compose this Xorg file ... What do you think? What should be changed in case to be sure it works?
-
Woah... RSS stopped working so I fell behind.
I made packages for the kernel with the patches already applied to make this easy.
While there's no reason to trust me, I tried to make it clean and reproducible.
Original fedora kernel source RPM: https://kojipkgs.fedoraproject.org/packages/kernel/5.4.0/2.fc32/src/kernel-5.4.0-2.fc32.src.rpm
My modified source RPM: https://files.gigabyteproductions.net/srv/devel/linux-navi10/fedora/f32/try6/kernel-5.4.0-2.fc32.ppc64le/kernel-5.4.0-2.fc32.src.rpm
You can rebuild using rpmbuild, or Mock.
See: https://wiki.centos.org/HowTos/RebuildSRPM
See: https://fedoramagazine.org/how-rpm-packages-are-made-the-source-rpm/
See: https://blog.packagecloud.io/eng/2015/05/11/building-rpm-packages-with-mock/#building-an-rpm-with-mock
My pre-built package can be installed like:
sudo dnf install \
'https://files.gigabyteproductions.net/srv/devel/linux-navi10/fedora/f32/try6/kernel-5.4.0-2.fc32.ppc64le/kernel-5.4.0-2.fc32.ppc64le.rpm' \
'https://files.gigabyteproductions.net/srv/devel/linux-navi10/fedora/f32/try6/kernel-5.4.0-2.fc32.ppc64le/kernel-core-5.4.0-2.fc32.ppc64le.rpm' \
'https://files.gigabyteproductions.net/srv/devel/linux-navi10/fedora/f32/try6/kernel-5.4.0-2.fc32.ppc64le/kernel-modules-5.4.0-2.fc32.ppc64le.rpm' \
'https://files.gigabyteproductions.net/srv/devel/linux-navi10/fedora/f32/try6/kernel-5.4.0-2.fc32.ppc64le/kernel-modules-extra-5.4.0-2.fc32.ppc64le.rpm' \
;
-
wow congratulations to you you have done a great job. But listen to a question, what difference is there in your opinion between yours and the one already made published by Merklot on the previous pages, he has both published his with the various steps, and the one already made that you can download from the site and install. ..
-
They're similar. Both are using Fedora's kernel sources (but mine from 2019-12-05). Packages are easier to reproduce and clean up. Package sources contain their own build steps and list of dependencies.
-
Understdood, in any case I installed what Merklot posted, then i'm also trying complete the session of the guide that always posted Merklot to male the Kernel modification by yourself. After all the procedure it still gives me the 5.3.16 Kernel and it's strange because It seems that everything is going we'll, I don't understand why I don't see it in the neofetch command, the modified kernel. In any case I have problems configuring starting the GPU, i'm also asking Raptor why It doesn't work as soon as I insert the configuration file xorg.conf The system hangs and I have to reboot in server mode to remove It... I don't understand... The file is this:
-
Compare your output of
lspci | grep VGA with the lines of the created file.These must be identical.
Note the numbers to the left of the "VGA compatible controller" string. Each of these numbers is the PCI d:B:D.F[note 1] number of the GPU, and is unique to the slot(s) you have your GPU(s) installed in. As a result of this slot dependence, bus IDs may differ from those shown in this example; always use your bus IDs when following the steps below. This slot dependence means that if you move your GPU to a different slot you will need to update the bus ID associated with that GPU.
Locate Bus Numbers (https://wiki.raptorcs.com/wiki/Troubleshooting/GPU#Step_1:_Locate_Bus_Numbers)
-
Hi MPC, happy new year to you and to the whole forum, I have already done what the guide says, as you see above I have reported what the guide says and I showed it to Raptor as well, the problem is which doesn't work unfortunately ... Even if I try to configure the graphical modes, it goes into lockout on restart. I don't know why but there is a problem with the Xorg files, it doesn't read them to me, I sent my Xorg.log.0 file to Raptor to see if they can understand what problem I have ... Listen about do you think the kernel because after the procedure I can't see version 5.5.1 as you and the others see it? It seems that everything went well and yet if I do neofetch it tells me that I still have Kernel 5.3.16 ... Do you have any idea what is missing?
-
guys I finally solved everything, a special thanks to the friend MPC for his very precious help, he says no but he is much ahead of me with Linux and it shows. Great MPC, thank you all! As a kernel I am using the one posted by Merklot ready and it seems that it works well ...
-
After all that, what did you do to fix it?
-
And hello Classic, happy new year, I installed the Kernel 5.4.0.2 ready, then I put the Xorg file that gave me MPC which was correct compared to mine and the graphics card started. My problem was apparently that I deleted the comments in the Xorg file that should be left instead. I thought that they only served to make you understand how to correctly compile the file and instead I was wrong. If you need I place the Xorg file that I put to make the card work. Kernel 5.4.0.2 is what Merklot posted on page 5 of this discussion and should be very similar to that posted by his friend kmarek whom I also thank for his valuable collaboration. Now I have to solve the problem of the sound card but I have the impression that I will have to wait for them because nobody seems to know anything unfortunately ...
-
The comments wasn't the problem. Comments are only comments.
-
YES there will be maybe also the wording of the drivers which was not exact but consider that I got the wording exactly from the output of the grep command | VGA and I reported it on the Xorg file. The PCI bus was correct, I had put 3 too, Raptor had corrected it when I showed him the file. Other I do not know what could have been wrong. In any case we have solved and thank MPC and all for the collaboration. Sew one day Merklort returns to answer I will ask him why, according to him, despite the procedure I was successful on the other hardisk, I still don't have the kernel installed with the path ... It is very strange because when I installed everything that was missing from the system and compiled and installed the kernel correctly from what I saw, I don't understand there must be something in the last few steps that must be reviewed ...
-
Sorry guys, now that we have the modified Kernel, when the official updates of Fedora or any other system arrive, those of the Kernel will also arrive, Fedora are among those that update the most kernels. How should one behave at this point? Updating directly could annoy our modified Kernel, I suppose, so what should we do in this case?
-
Well guys, another personal success, after weeks of errors and various problems, I finally managed to install the modified Merklot 5.5.0.1 kernel as well ... finally ...! 😁
Special thanks to Everyone! Thanks!
-
After a few months of use I can give my first rough impressions. The 5700 XT works very well, so far no blockages or problems. Since she is active, a series of graphic modes have opened which obviously were not there before and if you have a good monitor, you can indulge in using a lot of different graphic modes and having specifically a 4K monitor, the board sets itself to defaut in 4K. I tested the videos on You Tube, I noticed that as AMD said at the time of the release of this card, its best performance is in 2K mode and therefore at 1440 P. In that resolution it works very well and plays videos great, yes obviously hears the fan working because the card at that resolution works harder, but it works very well. If you try to set in 4K then the videos go jerky so I don't think he can do it at that resolution. Another thing that I noticed that the HDMI audio works badly, but I think it's the fault of the original dirver not optimized for the purpose but I obviously don't use that audio so it's okay anyway.