| View previous topic :: View next topic |
| Author |
Message |
leylanator
n00b
Joined: 10 May 2024
Posts: 10
|
 Posted: Sun May 12, 2024 12:21 pm Post subject: Issues with Vulkan |
 |
|
Continued from another post over by Unsupported Software: https://forums.gentoo.org/viewtopic-t-1168878.html
So, I have been having issues with Vulkan as described there.
I'll post some info here:
make.conf:
| Code: | # These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
COMMON_FLAGS="-march=native -O2 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
MAKEOPTS="-j16 -l16"
ACCEPT_LICENSE="*"
ACCEPT_KEYWORDS="~amd64"
#FEATURES="candy"
EMERGE_DEFAULT_OPTS="--ask"
VIDEO_CARDS="amdgpu radeon radeonsi"
USE="X alsa bluetooth brotli clang cups dbus extra extras gcc gles2 gpm haptic introspection jack jack-sdk joystick keyboard llvm lv2 mouse opengl osmesa pipewire readline sound ssl touchpad udev vaapi vdpau video vulkan vkd3d vst wacom wayland -networkmanager -ppp -systemd -wow64"
#gpm may need to be unused sometimes
#replace jack-sdk with jack-client if sample rates other than 48K are needed, loses general pipewire graph
INPUT_DEVICES="libinput evdev synaptics joystick"
# NOTE: This stage was built with the bindist Use flag enabled
# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C.utf8
GENTOO_MIRRORS="https://mirror.init7.net/gentoo/ \
rsync://mirror.init7.net/gentoo/ \
https://mirror.bytemark.co.uk/gentoo/ \
rsync://mirror.bytemark.co.uk/gentoo/ \
https://www.mirrorservice.org/sites/distfiles.gentoo.org/ \
ftp://ftp.mirrorservice.org/sites/distfiles.gentoo.org/ \
rsync://rsync.mirrorservice.org/distfiles.gentoo.org/"
GRUB_PLATFORMS="efi-64" |
inxi -Gxx output:
| Code: | Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Sapphire
driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports:
active: DP-1,DP-3 empty: DP-2,HDMI-A-1,Writeback-1 bus-ID: 03:00.0
chip-ID: 1002:73bf
Device-2: AMD Baffin [Radeon Pro WX 4100] vendor: Hewlett-Packard
driver: amdgpu v: kernel arch: GCN-4 pcie: speed: 8 GT/s lanes: 4 ports:
active: none empty: DP-4, DP-5, DP-6, DP-7 bus-ID: 0a:00.0
chip-ID: 1002:67e3
Display: x11 server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 4480x1613
Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,bottom-l
model: Idek Iiyama PL2760Q res: 2560x1440 dpi: 109 diag: 685mm (27")
Monitor-2: DP-3 mapped: DisplayPort-2 pos: top-right model: HP P222va
res: 1920x1080 dpi: 102 diag: 546mm (21.5")
API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 2 drv: swrast
gbm: drv: kms_swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: wayland,device-1
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.6 glx-v: 1.4
direct-render: yes renderer: AMD Radeon RX 6800 XT (radeonsi navi21 LLVM
17.0.6 DRM 3.57 6.8.9-gentoo-dist) device-ID: 1002:73bf
API: Vulkan v: 1.3.280 surfaces: xcb,xlib device: 0 type: discrete-gpu
driver: N/A device-ID: 1002:73bf |
To note: I use a 6800XT, the WX4100 is meant to be set up later for VFIO and is not yet plugged into any monitor.
vulkaninfo is where something interesting happened, here's the output in a pastebin: https://pastebin.com/bwJDZ3Am
When I was pasting this into a file using; | Code: | | echo "$(vulkaninfo)" >> vulkaninfo.txt |
it wrote, but also threw out an error:
| Code: | | ERROR: [../mesa-24.0.6/src/amd/vulkan/radv_physical_device.c:1813] Code 0 : Could not open device /dev/dri/renderD129: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER) |
Maybe this could be related to what's causing some games to break as soon as 3D graphics are rendered?
| Code: | Assertion failed!
Program:
Z:\storage\S3-4TB\extras\SteamLibrary\steamapps\common\TEKKEN 8\Polaris\Binaries\Win64\Polaris-Win64\Shipping.exe
File: ../src-wine/dlls/winevulkan/loader_thunks.c
Line: 98
Expression "!status && "vkBeginCommandBuffer""
Press OK to exit the program, or Cancel to start the Wine debugger. |
I've also noticed that Red Dead Redemption 2 is flashing white lights a lot, and it's in Vulkan rendering mode. So I'm thinking I've got issues with Vulkan, rather than the previously expected WINE or Steam Proton - though, either of them could also have their own, separate or related, problems.
Any and all help is greatly appreciated  |
|
| Back to top |
|
 |
builder_247
n00b
Joined: 12 May 2024
Posts: 1
|
|
| Back to top |
|
|
leylanator
n00b
Joined: 10 May 2024
Posts: 10
|
| Posted: Sun May 12, 2024 6:05 pm Post subject: |
|
|
It's looking like I need to update my BIOS, as I'm using the 2019 version. What's a good way of doing it? I don't want to unintentionally brick my motherboard is why I ask.
I'm thinking of borrowing a friend's Windows machine to flash the BIOS files onto a thumb drive, since I don't want to risk messing anything up.
Looks like I'll have to play affected games in Debian for the time being, looking like it's a kernel bug? |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6103
Location: Dallas area
|
| Posted: Sun May 12, 2024 8:14 pm Post subject: |
|
|
If you are going to use the wx4100 only for vfio, then set it so that the amdgpu driver doesn't grab it.
I would set up vfio pci id options in /etc/modprobe.d/options.conf
I don't believe that polaris based chips work with vulkan.
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
| Back to top |
|
|
leylanator
n00b
Joined: 10 May 2024
Posts: 10
|
| Posted: Mon May 13, 2024 9:46 am Post subject: |
|
|
| leylanator wrote: |
It's looking like I need to update my BIOS, as I'm using the 2019 version. What's a good way of doing it? I don't want to unintentionally brick my motherboard is why I ask.
|
I decided to format a spare USB I had with FAT32, and extract the motherboard BIOS files in to update from the BIOS settings screen, and it updated just fine.
However, I'm still experiencing the same issues, even after disabling CSM (I don't know how to check if resizable bar is enabled, but it supposedly is for Gigabyte boards by default unless CSM is enabled).
| Anon-E-moose wrote: | If you are going to use the wx4100 only for vfio, then set it so that the amdgpu driver doesn't grab it.
I would set up vfio pci id options in /etc/modprobe.d/options.conf |
Yeah I'll have to get this done at some point anyways, so it's best to get it done and see if that also has the bonus of fixing my issues. |
|
| Back to top |
|
|
leylanator
n00b
Joined: 10 May 2024
Posts: 10
|
| Posted: Tue May 14, 2024 10:49 am Post subject: |
|
|
| leylanator wrote: | | leylanator wrote: |
It's looking like I need to update my BIOS, as I'm using the 2019 version. What's a good way of doing it? I don't want to unintentionally brick my motherboard is why I ask.
|
I decided to format a spare USB I had with FAT32, and extract the motherboard BIOS files in to update from the BIOS settings screen, and it updated just fine.
However, I'm still experiencing the same issues, even after disabling CSM (I don't know how to check if resizable bar is enabled, but it supposedly is for Gigabyte boards by default unless CSM is enabled).
| Anon-E-moose wrote: | If you are going to use the wx4100 only for vfio, then set it so that the amdgpu driver doesn't grab it.
I would set up vfio pci id options in /etc/modprobe.d/options.conf |
Yeah I'll have to get this done at some point anyways, so it's best to get it done and see if that also has the bonus of fixing my issues. |
Alright, so I've managed not to set up VFIO properly, which I'll get done in its own time, but what I had managed to do was to not find where Resizable BAR settings were in my BIOS. Apparently they were under Misc settings that I missed out! So, while I was in my BIOS settings, I'd found "Above 4G Decoding" was, in fact, there and disabled (I had assumed it was a default unchanging setting). I enabled it and enabled the setting that spawned from it for Resizable BAR. Might have never found that incidentally during my VFIO setup perusing.
Games are working fine now! I'll even post the solution in the previous forum topic I was on.
BIOS update needed (just drag extracted files into a FAT32 flash drive under 32GB, go into BIOS, update from the Q-Flash utility while the flash drive is plugged in (make sure you don't need a specific USB slot, refer to motherboard manual)), (assuming you're using EFI boot) CSM has to be disabled, then in Misc settings the Above 4G Decoding setting has to be enabled for then Resizable BAR support to be set to auto rather than disabled. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
