Software > User Zone

Graphics Card install

<< < (4/28) > >>

MauryG5:
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 ...

nglevin:
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

MauryG5:
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

q66:
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.

madscientist159:

--- Quote from: q66 on December 01, 2019, 10:39:09 am ---DMA issues (assuming you need the 32-bit DMA thing) are a completely unrelated thing and will affect very few people.

--- End quote ---
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.


--- Quote from: q66 on December 01, 2019, 10:39:09 am ---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)

--- End quote ---

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. ;)

Navigation

[0] Message Index

[#] Next page

[*] Previous page