Hi folks,
I’m currently testing again the setup. Not all the issues are fixed but I think I made a mistake with my first try. Since I tested EOS in a virtual machine before installing it on my computer to tests games I took the time to create a script to install all my packages using the --noconfirm option.
Since the Steam install ask for which vulkan library to use, maybe it took choice 1 and took AMD vulkan instead of Nvidia … But I can’t confirm this since I already wipped and reinstalled EOS totally.
So yesterday I make my way to install EOS alongside my current Windows 10 for convenience while testing. They are both on a different SSD with their EFI partition and I had a hard time booting on EOS the system was booting on Windows everytime… If someone run into the same issue, just disconnect your other disk while installing your OS. After that everything worked.
@Joe_Mama @ricklinux After this, I downgraded to nvidia-535xx version but I didn’t had nvidia-dkms and nvidia-settings if I remember correctly (I installed EOS using Nvidia option). Unfortunately it didn’t solve my issue about the “flashing apps” on screens and the game I was using for test was still horribly messed up (Helldivers 2).
I looked on ProtonDB and tried multiple stuffs to make it work, it was better but still not very good but I wanted to test it further.
So I reinstalled again the whole system to use the latest drivers. I know, it’s overkill but I’m a noob about EOS and wanted to be sure everything is set correctly.
I retested my game, it wasn’t worst than with the previous driver but still unplayable.
Today, I had more time. I retried everything I saw on ProtonDB to test Helldivers 2 and noticed the game really doesn’t like me to change anything in the menu, especially graphic options and force me to close the game. I think this could be an issue about the game itself. I managed to set it in “native resolution” and set the same graphic option as I was using on Windows with some more ALT+F4 and reload and apparently the game is now stable. I wanted to post my answer before testing further to avoid the closure of the ticket.
@jake99 you also asked me some infos, here is the result of the inxi command and you’re right! The resolution is in 3840x2160 as it should be!
Below is the glxgears output but I think it’s not correct. I use the Steam FPS counter and when I’m in the game menu I’m more about 30-35FPS.
Summary
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
296 frames in 5.0 seconds = 59.113 FPS
269 frames in 5.0 seconds = 53.644 FPS
291 frames in 5.0 seconds = 58.026 FPS
286 frames in 5.0 seconds = 57.011 FPS
287 frames in 5.0 seconds = 57.379 FPS
282 frames in 5.0 seconds = 56.315 FPS
161 frames in 5.2 seconds = 31.021 FPS
189 frames in 5.0 seconds = 37.711 FPS
263 frames in 5.0 seconds = 52.419 FPS
263 frames in 5.0 seconds = 52.593 FPS
261 frames in 5.0 seconds = 52.027 FPS
258 frames in 5.0 seconds = 51.596 FPS
254 frames in 5.0 seconds = 50.455 FPS
252 frames in 5.0 seconds = 50.216 FPS
254 frames in 5.0 seconds = 50.719 FPS
187 frames in 5.0 seconds = 37.301 FPS
293 frames in 5.0 seconds = 58.508 FPS
298 frames in 5.0 seconds = 59.438 FPS
290 frames in 5.0 seconds = 57.963 FPS
285 frames in 5.0 seconds = 56.808 FPS
261 frames in 5.0 seconds = 52.056 FPS
293 frames in 5.0 seconds = 58.550 FPS
300 frames in 5.0 seconds = 59.799 FPS
292 frames in 5.0 seconds = 58.385 FPS
260 frames in 5.0 seconds = 51.955 FPS
284 frames in 5.0 seconds = 56.730 FPS
286 frames in 5.0 seconds = 57.152 FPS
283 frames in 5.0 seconds = 56.433 FPS
284 frames in 5.0 seconds = 56.592 FPS
287 frames in 5.0 seconds = 57.297 FPS
289 frames in 5.0 seconds = 57.786 FPS
277 frames in 5.0 seconds = 55.365 FPS
278 frames in 5.0 seconds = 55.552 FPS
286 frames in 5.0 seconds = 57.192 FPS
281 frames in 5.0 seconds = 56.077 FPS
283 frames in 5.0 seconds = 56.538 FPS
286 frames in 5.0 seconds = 57.169 FPS
286 frames in 5.0 seconds = 57.167 FPS
286 frames in 5.0 seconds = 57.126 FPS
280 frames in 5.0 seconds = 55.908 FPS
288 frames in 5.0 seconds = 57.478 FPS
287 frames in 5.0 seconds = 57.300 FPS
270 frames in 5.0 seconds = 53.899 FPS
286 frames in 5.0 seconds = 57.164 FPS
285 frames in 5.0 seconds = 56.992 FPS
282 frames in 5.0 seconds = 56.210 FPS
283 frames in 5.0 seconds = 56.571 FPS
286 frames in 5.0 seconds = 57.177 FPS
286 frames in 5.0 seconds = 57.056 FPS
287 frames in 5.0 seconds = 57.353 FPS
281 frames in 5.0 seconds = 56.024 FPS
283 frames in 5.0 seconds = 56.588 FPS
284 frames in 5.0 seconds = 56.786 FPS
288 frames in 5.0 seconds = 57.445 FPS
275 frames in 5.0 seconds = 54.837 FPS
286 frames in 5.0 seconds = 56.949 FPS
287 frames in 5.0 seconds = 57.358 FPS
283 frames in 5.0 seconds = 56.472 FPS
284 frames in 5.0 seconds = 56.758 FPS
285 frames in 5.0 seconds = 57.000 FPS
287 frames in 5.0 seconds = 57.263 FPS
282 frames in 5.0 seconds = 56.353 FPS
For the vk_cube command, it was not recognized in the terminal.
So, I will try to play a bit Helldivers 2 and few others game to see if the issue is resolved for gaming. If yes I will suppose that I was simply dumb and used wrong vulkan librairies initially…
For the app flashing (Firefox mostly) on my side monitors, I still didn’t found the solution.
I did some research and read that some HDMI cable could be the issue if there wasn’t 1.2 but the left screen is using display port and the flashing appear on this one most of the time. Since reinstall I didn’t see any issue on the right side monitor (that is using HDMI).
Sorry for the very long answer, since you guys take time to help me I wanted to be as precise as possible. Thank you very much for your help, it’s greatly appreciated.