_emily
25 December 2023 21:20
21
Yes, I did only try Lutris with the Launcher, still, it did not work, I don’t think it would make any difference.
The radeon Driver is not compatible with Vulkan
omano:
_emily:
About the Steam log, it does say that Vulkan couldn’t initialize
vkEnumeratePhysicalDevices failed, unable to init and enumerate GPUs with Vulkan.
BInit - Unable to initialize Vulkan!
Didn’t catch that as it is before the game is started. Anyway back to initial thought, as you’re using the old radeon
driver, start with using amdgpu
driver, and see. Just do one thing at a time to try to pinpoint the issue but this is most likely the issue.
//EDIT: this is also why your other game worked with PROTON_USE_WIND3D
as it would run on OpenGL and not Vulkan and why I thought initially what you said was pointing to you not being able to run Proton games.
So the game would not run with Proton unless I use PROTON_USE_WIND3D %command%
which, at that point, I just might as well use windows, since it would run better.
omano
25 December 2023 21:38
22
You can still try again to manually enable amdgpu
as maybe the amdgpu-experimental
package created issue, because it enables also some other features (and as you reinstalled we can not check what was the issue).
Just run the command from a terminal to create the configuration files.
Then you would need to edit the file /etc/mkinitcpio.conf
with the Kate editor for example, and change the line MODULES=()
to add the amdgpu
module so it is loaded on boot, like that:
MODULES=(amdgpu)
Then run from terminal the command sudo mkinitcpio -P
to regenerate the system boot image.
1 Like
_emily
26 December 2023 06:46
23
omano:
You can still try again to manually enable amdgpu
as maybe the amdgpu-experimental
package created issue, because it enables also some other features (and as you reinstalled we can not check what was the issue).
Just run the command from a terminal to create the configuration files.
Then you would need to edit the file /etc/mkinitcpio.conf
with the Kate editor for example, and change the line MODULES=()
to add the amdgpu
module so it is loaded on boot, like that:
MODULES=(amdgpu)
Then run from terminal the command sudo mkinitcpio -P
to regenerate the system boot image.
If that happens to not work, and I end up with a black screen again. What should I do to fix it? Just in case.
omano
26 December 2023 11:04
24
You should theoretically be able to switch to a TTY for example with CTRL+ALT+F4 and then login with your user, and then remove the changes and rebuild the boot images:
Remove the two config files created
sudo rm /etc/modprobe.d/amdgpu.conf
sudo rm /etc/modprobe.d/radeon.conf
Open mkinitcpio.conf
with nano
editor
sudo nano /etc/mkinitcpio.conf
Remove amdgpu
from MODULES=(amdgpu)
Save and exit from nano
with CTRL +X (read the bottom of the screen, basically you should press Y es to save and ENTER to validate the filename)
Finally, rebuild the images
sudo mkinitcpio -P
And reboot with command reboot
1 Like
_emily
26 December 2023 19:39
25
I did get this while running sudo mkinitcpio -P
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.6.8-2-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
It did finish though
#Edit: Found another post that showed how to check if xhci_pci is needed, nothing came up, so I guess that one’s good, don’t know about the rest.
_emily
27 December 2023 01:33
26
omano:
You can still try again to manually enable amdgpu
as maybe the amdgpu-experimental
package created issue, because it enables also some other features (and as you reinstalled we can not check what was the issue).
Just run the command from a terminal to create the configuration files.
Then you would need to edit the file /etc/mkinitcpio.conf
with the Kate editor for example, and change the line MODULES=()
to add the amdgpu
module so it is loaded on boot, like that:
MODULES=(amdgpu)
Then run from terminal the command sudo mkinitcpio -P
to regenerate the system boot image.
Okay, this fixed the issue, using amdgpu driver made the game open, it’s now running. Though, I have to add, I HAD to use Proton 8, the versions under that one do not work, at least on my particular case, they just make Rockstar’s launcher crash. I haven’t tried experimental, but maybe it could improve over version 8.
#edit: Thanks a lot for the help and the patience by the way, it was really helpful ^-^
1 Like
omano
27 December 2023 06:13
27
Experimental is for testing patches and help development, not for daily usage.
system
Closed
28 December 2023 18:14
28
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.