Hi everyone. I have a Ubuntu 18.04 box with a Radeon VII, AMD 1600, and 16 GB of memory. In the last several weeks, my box stopped running XCOM2. But still runs XCOM: Enemy Unknown. I reinstalled the AMD Radeon Pro drivers. I installed kernel Linux 5.2.3-050203-generic. Can I get some advise on how to troubleshoot this issue?
Related, this is a multi-purpose box. And isn’t a dedicated gaming machine.
Also, why would one game work and not the other one?
Last, I don’t get a correct MESA version. For example:
Yeah, from everything i ever read on AMD under Linux: You never need the Pro driver, unless you are running FirePro GPU’s to do rendering or such.
For anything else, just never install drivers and you should be good.
You mentioned that it is not a dedicated rig. What else does it do? You can hybrid install the Pro driver with parts of the opensource stack. If you do not need the Pro stack just use the opensource driver. If you need OpenCL or other compute components, then hybrid install or run ROCm.
Thank you so much. I installed the latest AMD-Open driver and it worked! Thank you Thank you Thank you Thank you. I want to say I tried the Open driver and it didn’t work las year. But maybe I am more confused that I think I am.
It’s kind of a game server using Steam Remote Play.
It’s kind of a VM host by running KVM.
It’s kind of a storage host by having an LSI HBA flashed to IT Mode and a bunch of drives.
It’s a work in progress, but that’s what I’ve got planned so far. The VMs include PfSense, Emby, and I’m working on FreeIPA.
Not embarrassing at all. Not all of us have the monies to make dedicated rigs for all of our interests. You sound like most of us.
I was asking that question in case you were doing machine learning or the like. I could help you figure out the hybrid install if you need the pro drivers for OpenCL or TensorFlow, and etc.
Thanks. That’s surprising you mention the open drivers. My box just crashed. It wasn’t a problem with the pro drivers. I’m about to open a ticket with AMD support. Do you have any recommendations about troubleshooting the open driver?
You need to pull logs to figure out what the system is complaining about. Also you need to provide a description of what you were doing when it happened.
You want to write dmesg to a file sudo dmesg > /path/to/your/home/dmesg.log and you want to look at journalctl to see what happened in the last boot (when the issue occured). https://wiki.archlinux.org/index.php/Systemd/Journal.
Essentially you need to provide some context to the issue. We and/or AMD will need something to look at. Your hardware is still bleeding edge in regards to the *nix world and the drivers are still a work in progress so you may be running into corner cases that can help improve the usage of all VII users on *nix. Happy hunting!
If you did a fresh install of Ubuntu like you said, it could be possible that you are missing the newest firmware needed for the kernel 5.2 that you have installed.
Could you do the following and see what you get as well, sudo apt show firmware-linux
Which version are you showing? If you do not show it as manual installed, go ahead and run sudo apt update && sudo apt install linux-firmware
I’m srprised to see they don’t have anything besides Windows 7/10 support listed on the ASRock website.
$ sudo apt show firmware-linux
Package: firmware-linux
State: not a real package (virtual)
N: Can’t select candidate version from package firmware-linux as it has no candidate
N: Can’t select versions from package ‘firmware-linux’ as it is purely virtual
N: No packages found
$ sudo apt show firmware-linux
Package: firmware-linux
State: not a real package (virtual)
N: Can’t select candidate version from package firmware-linux as it has no candidate
N: Can’t select versions from package ‘firmware-linux’ as it is purely virtual
N: No packages found
I am a Debian SID and ArchLinux user. Ubuntu is Debian based and used apt. I am surprised that Ubuntu apt is not able to list details about virtual packages.
In regards to firmware, I meant the firmware for the gpu. You CPU and GPU run microcode that is updated in the linux-firmware-* packages. If your kernel is too new or the mesa package is too new and invokes routines or expects results that the currently loaded firmware does not work with, it can cause issues. The firmware is usually packages in the kernel sources so I would assume that whoever built your kernel packaged that as well. I am out of ideas on that.
You could be very well having an ubuntu specific issue as last year is when they officially switched over to gnome3 and wayland from unity and mir. As Canonical tends to do, they were doing things their own way instead of just repackaging the debian binaries and have run into issues with gnome3 and wayland. I would add my issues to that person’s bug report.
