Quoting: johndoe

Quoting: RussianNeuroMancer

Quoting: johndoeWhats the outcome?

Outcome described in bugreport. This bug is unrelated to DDX, issue occur on lower lewel.

Ehhh, this Artikel/Blog is from 2016.
I also remember having some troubles with modesetting years ago and setting up dual-screen with it.
But these problems do not apply anymore.
With Debian Stretch (stock Xorg 1.19.2 and stock 4.9.x kernel) there should be not problems.

And to be honest I think that a Linux user should be able/learn to compile a newer Xorg server - it's really easy.
Linux gives the user ALL freedom which Windows does NOT.
This is my opinion - nothing more.

https://bugs.freedesktop.org/show_bug.cgi?id=103229 [External Link]

09-14-2018 is pretty current. Compiling Xorg is not something that should be done on a normal distro, but on Linux From Scratch or something like that (Gentoo). Just compiling a small program causes dependency problems after a while. Can I compile Xorg, sure, can I compile the kernel as well, sure, do I want to spend all my time compiling all the different parts of my distro and fixing what breaks because I've got custom compiled stuff all over the place instead of using what's in the distro repo's..... no

View this comment - View article - View full comments

Quoting: RussianNeuroMancer

Quoting: Leopard

Quoting: m2mg2

Quoting: RussianNeuroMancer

Quoting: GuestThey've not been ignoring anything.

You forgot BayTrail/CherryTrail SoC drivers fiasco - as soon as management pull the plug for Atom series, almost all Intel's own Atom development efforts stopped, including Windows (no drivers updates since year 2016) and Linux drivers (left unusable; devboards was tested and supported, tablets and laptops - not). Only occasional GPU driver fixes left, and not as fast as one would expect [External Link]. Couple of years later BayTrail/CherryTrail devices gets usable, but only because external (and some internal [External Link]) developers polished drivers in their own free time.

So, Intel do ignore hardware they intentionally left behind, and they ignore it on Linux too. And I not even talking about (drivers for) boards and IoT platforms they introduce, just to kill it year of two later.

On topic: BayTrail Vulkan drivers allow to play Talos Principle with Vulkan API and 20+ fps even on low-end laptop with Z3735F, which is kind of unexpected from unfinished experimental driver (BayTrail share GPU with Ivybridge). Running same game in OpenGL mode produce empty skybox with few objects, so seems like OpenGL implementation for BayTrail is more buggy than Vulkan implementation. It's will be interesting to see how DXVK would perform on such low-end devices.

There is an intel graphics driver bug that affects my laptop that has been there since fedora 27. I have to use the Fedora 26 kernel in Fedora 28 or my screen flickers constantly. I have had so many issues like this with intel graphics. They should just work, but whatever machine I'm working with almost always happens to be affected by some bug where the intel graphics driver doesn't work right. My laptop isn't even that old, it's a Latitude 5480.

By flicker , you mean tearing?

If it is , you can change your accel to UXA

https://wiki.archlinux.org/index.php/intel_graphics#SNA_issues [External Link]

I pretty sure he mean "flicker". I have same issue on HP EliteBook Folio G1 on anything newer than Linux 4.15. Workaround is disabling rc6, but this kills power management [External Link], which is unacceptable for laptop, disabling rc6 is impossible with newer kernels, so stuck with 4.15 for now. This bug, of course, was reported [External Link].

Yes, it is flickering not tearing. I saw the power management work arounds, which as you say are unacceptable. Yes it is a known bug which has been reported, acknowledged and reconfirmed many times as still being there, it just hasn't been fixed or even had a reasonable workaround available as far as I know. So I'm stuck on the F26 kernel hoping, but not confident, that it will get fixed.

View this comment - View article - View full comments

Quoting: RussianNeuroMancer

Quoting: GuestThey've not been ignoring anything.

You forgot BayTrail/CherryTrail SoC drivers fiasco - as soon as management pull the plug for Atom series, almost all Intel's own Atom development efforts stopped, including Windows (no drivers updates since year 2016) and Linux drivers (left unusable; devboards was tested and supported, tablets and laptops - not). Only occasional GPU driver fixes left, and not as fast as one would expect [External Link]. Couple of years later BayTrail/CherryTrail devices gets usable, but only because external (and some internal [External Link]) developers polished drivers in their own free time.

So, Intel do ignore hardware they intentionally left behind, and they ignore it on Linux too. And I not even talking about (drivers for) boards and IoT platforms they introduce, just to kill it year of two later.

On topic: BayTrail Vulkan drivers allow to play Talos Principle with Vulkan API and 20+ fps even on low-end laptop with Z3735F, which is kind of unexpected from unfinished experimental driver (BayTrail share GPU with Ivybridge). Running same game in OpenGL mode produce empty skybox with few objects, so seems like OpenGL implementation for BayTrail is more buggy than Vulkan implementation. It's will be interesting to see how DXVK would perform on such low-end devices.

There is an intel graphics driver bug that affects my laptop that has been there since fedora 27. I have to use the Fedora 26 kernel in Fedora 28 or my screen flickers constantly. I have had so many issues like this with intel graphics. They should just work, but whatever machine I'm working with almost always happens to be affected by some bug where the intel graphics driver doesn't work right. My laptop isn't even that old, it's a Latitude 5480.

View this comment - View article - View full comments

Quoting: baccilus

Quoting: XpanderGTA V on the other hand went from 70-90fps to 90-110FPS in the GPU bound situations (which are the most situations for me with 2560x1440) and the GPU utilization is now a bit lower also, around 90% while it was constantly 100% before

Is there anything special I need to do to get GTA V to work with Steam Play? It doesn't have great rating at the SPCR website [External Link]. I have a GTX 1060 6GB card with Intel 2500K and 24GB RAM. I don't want to download such a big game to find out that it doesn't work. I am only interested in the Single player.

It works but takes some tinkering. You need ms fonts (either in your distro or in wine/proton through winetricks), a special dxvk config option and set msdmo to builtin (with winecfg).

https://github.com/ValveSoftware/Proton/issues/37#issuecomment-420495098 [External Link]

I'm about 30% through the game, plays great. You can get by without the msdmo fix for single player but you have to pass on offline only option to the game or the social club hangs.

View this comment - View article - View full comments

A really big problem with native linux ports has been cross platform multiplayer. To some extent if you can't make cross platform multiplayer work native but you can with Proton, Proton makes more since. Seems to me if you want to do a native port, you need to design it that way from the start, including cross-platform multiplayer. If you aren't going to do that you should probably focus on Proton. I think native is better, but if you are only going to half *** i, it isn't. Unfortunately too many devs/publishers have been half ***ing it. Feral is great, but if you make your game with technology that can't do cross platform multiplayer with reasonable effort even Feral can't help you. If Proton can show true Linux usage numbers (remove Wine sales/use from Windows and give them to Linux) and bring some new users maybe it will be enough for some of these companies to stop half ***ing it.

View this comment - View article - View full comments

Looks like they fixed my issue. I had to switch back from the beta channel to the normal channel. I had switched to the beta because the normal version didn't work.

View this comment - View article - View full comments

Unfortunately not Rise of the Tomb Raider. Still crashes on my machine.

View this comment - View article - View full comments

Still broken for me:(

View this comment - View article - View full comments

Quoting: jens

Quoting: m2mg2

Quoting: jens

Quoting: tuubi

Quoting: lucifertdark

Quoting: Comandante Ñoñardo

Quoting: m2mg2Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-

I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.

Not quite that simple. For starters, with 390.48 the game gobbles up several gigabytes more memory, which explains some of the problems on systems with only 8 gigs of RAM. For me the 396.18 beta is almost perfect with this game on Mint 18.3, whereas 390.48 caused me to almost give up and wait for a fix.

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.

Yeah, seems to be very system dependent which driver works well. I'm running the 390.48 driver on Fedora without any issues for ROTTR. That said I have 32GB RAM, which supports your observation. No micro stutters either, but could be that they are there, but me just does not noticing them that much due to having a fast system.

What version of Fedora are you running?

Fedora 27 fully updated, thus now kernel 4.16.3-200.fc27.x86_64.
I'm using negativo17 repositories for Nvidia, Steam and some other packages (https://negativo17.org/repositories/ [External Link]). I do not use rpmfusion.

Almost the same as me, although I do use rpmfusion. I have a GTX 980. I was using negativo for NVIDIA drivers, but I removed them to manually install the 396 BETA drivers. Game didn't work with either set of drivers. All other Feral games work fine. Must be hardware/driver issues, hopefully Feral get it sorted out soon. I've sent crash logs and I'm sure they have plenty of others.

View this comment - View article - View full comments

Quoting: jens

Quoting: tuubi

Quoting: lucifertdark

Quoting: Comandante Ñoñardo

Quoting: m2mg2Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-

I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.

Not quite that simple. For starters, with 390.48 the game gobbles up several gigabytes more memory, which explains some of the problems on systems with only 8 gigs of RAM. For me the 396.18 beta is almost perfect with this game on Mint 18.3, whereas 390.48 caused me to almost give up and wait for a fix.

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.

Yeah, seems to be very system dependent which driver works well. I'm running the 390.48 driver on Fedora without any issues for ROTTR. That said I have 32GB RAM, which supports your observation. No micro stutters either, but could be that they are there, but me just does not noticing them that much due to having a fast system.

What version of Fedora are you running?

View this comment - View article - View full comments