My 6900xt is getting 4fps in minecraft. I have tried reinstalling drivers, kernel, using optifine. I am not sure what the problem is. Two months ago it was running fine… I booted it up today. Can’t figure out what is happening. Any guidance would be much appreciated.
Have you tried running radeontop to see what the GPU’s actually doing?
4FPS sounds abnormally slow though. Maybe there’s some log in journalctl or dmesg that would give some insight of what’s going on.
Also, does any other game or 3D-acclerated application run slowly?
I can’t imagine it just being minecraft, unless something is severely wrong with java on your installation.
can you remove the mods and see how it goes?
IIRC there are also dependencies for it, those are updated too, right? I removed the mods from my system because it is finicky oftentimes.
2 Likes
Hey, forget what I said earlier, after some research I believe it may be the same problem as over here:
1 Like
Yea I am on windows, until it is fixed I will stay on windows 10. I had daily driven linux for 4 years. But the latest kernel messed it up.
Interesting this happens with 6000 series too. I had assumed it was just a quirk of 7000 series being new(ish). Try openSUSE or Ubuntu/Kubuntu 23.04. Worked fine for me on both. It’s really unclear to me whether this is kernel version-related. 6.1 on Debian 12 and 6.4.9 on Fedora both have this problem, but 6.2 on Kubuntu and 6.4.9 on openSUSE don’t.
I have found a temporary workaround to this (that doesn’t involve distro hopping) that might interest you. My theory is that some distros are shipping with a buggy piece of firmware whereas others seem to have avoided it somehow. OpenSUSE tumbleweed and kubuntu 23.04 seem to be fine. Using distrobox, you can run a containerized version of many different distros from the command line of your distro of choice. Simply install distrobox, create a container image of a distro (like openSUSE or kubuntu) that does not have this buggy firmware, then start up and launch any application (which could be installed outside the container on the host OS) from within the container. It seems to use the firmware of the containerized distro and not the buggy one of the host OS, but it runs at native speed. This is not like virtualization where there is a massive performance hit.
So for me on Fedora where I had already installed the flatpak version of Minecraft the process went like this:
sudo dnf install podman # a dependency of distrobox
# enable repo where distrobox is kept
sudo dnf copr enable alciregi/distrobox
sudo dnf install distrobox
# create container image of openSUSE tumbleweed; could try other distro image here
distrobox create --name tumbleweed-pkg --image registry.opensuse.org/opensuse/distrobox-packaging:latest
# you should now be in an openSUSE container
# set up flatpak in the container
sudo zypper install flatpak
flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
# assumes you already have flatpak Minecraft installed on host OS
# insert any other app here
flatpak run com.mojang.Minecraft
Minecraft should now be running from within the container at native speed without the buggy firmware. For Pop!_OS you would simply substitute dnf for apt and probably the repo where distrobox is kept.
EDIT: When I tried this using an ubuntu 23.04 container and tried flatpak run com.mojang.Minecraft I got the error:
error: Could not connect: No such file or directory
A quick google search of this error showed that this can sometimes happen when trying to run flatpak from within a container, but this seems to be fixed by running dbus-daemon --system, then running the flatpak. Ubuntu 23.04 also does not have this firmware issue.
1 Like
I like your workaround, but I wonder if there’s another solution. Years ago I had to install missing firmware to get my Polaris card running on debian.
https://wiki.debian.org/Firmware#Firmware_after_installation
I wonder if you could replace the faulty firmware binaries with known working ones for a particular generation.
Like, replacing /lib/firmware/amdgpu/navi*.bin files with a different version from:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
I’m not sure if the kernel or mesa versions have problems with newer firmware, but it’s probably better than running a container of an OS inside an otherwise perfectly usable system. 