Patreon Logo Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal Logo PayPal. You can also buy games using our partner links for GOG and Humble Store.
Latest Comments by TheLinuxPleb
NVIDIA 396.18 beta driver is out with a new Vulkan SPIR-V compiler to reduce shader compilation time
12 Apr 2018 at 10:57 am UTC

Quoting: Leopard
Quoting: Imnotarobot
Quoting: tuubi
Quoting: ImnotarobotThe 390 driver that comes with Ubuntu is horrible. I can't stop the tearing no matter what i do.
It works with 340, but that is old. I think it does not even support Vulkan.
I've had no trouble at all with the 390 series. But you're not the first one to complain here so there must be something to it.

If tearing is your only problem, you could try enabling the Full Composition Pipeline in the Nvidia settings software. This does come with a small performance penalty, but totally worth it in my opinion.

EDIT: Leopard was quicker.
Yeap. Have done that done this and nothing works.
I have a laptop and my gpu is k1000m.

https://www.youtube.com/watch?v=oYWer86A20s&t=9s [External Link]
That is the guide i use to get rid of tearing, but with 390 it's not working. Works with all the other driver versions.

I think that Nvidia should open up their drivers if they can't manage to handle their proprietary ones...

Is there any way i can install 384? every time i put sudo apt install nvidia-384 it just installs the 390 driver.
Because on a laptop , you have to configure PrimeSync.

I told you on my earlier message.

https://forum.linuxmint.net.tr/index.php?topic=8505.0 [External Link]

Just do this.

Change xed parts to your distros editor.
Hmmmm... Prime is for dual graphics. I have Intel one disabled via bios.

I don't have Prime installed, because i have not needed it before with any other driver, because they all used to work.
I have used single gpu and it has worked and still works with older drivers.

Maybe my only option is to update 384 through Nvidias site, because i can't install it from drivers list or through terminal?

Thanks for trying to help though. Oh! BTW. 396 does not work also.
Damn Nvidia is really on a roll. Maybe i need to buy a cpu and a motherboard for my desktop so i can use my 7870 for my tv. :)

NVIDIA 396.18 beta driver is out with a new Vulkan SPIR-V compiler to reduce shader compilation time
12 Apr 2018 at 9:16 am UTC

Quoting: tuubi
Quoting: ImnotarobotThe 390 driver that comes with Ubuntu is horrible. I can't stop the tearing no matter what i do.
It works with 340, but that is old. I think it does not even support Vulkan.
I've had no trouble at all with the 390 series. But you're not the first one to complain here so there must be something to it.

If tearing is your only problem, you could try enabling the Full Composition Pipeline in the Nvidia settings software. This does come with a small performance penalty, but totally worth it in my opinion.

EDIT: Leopard was quicker.
Yeap. Have done that done this and nothing works.
I have a laptop and my gpu is k1000m.

https://www.youtube.com/watch?v=oYWer86A20s&t=9s [External Link]
That is the guide i use to get rid of tearing, but with 390 it's not working. Works with all the other driver versions.

I think that Nvidia should open up their drivers if they can't manage to handle their proprietary ones...

Is there any way i can install 384? every time i put sudo apt install nvidia-384 it just installs the 390 driver.

NVIDIA 396.18 beta driver is out with a new Vulkan SPIR-V compiler to reduce shader compilation time
11 Apr 2018 at 3:25 pm UTC

The 390 driver that comes with Ubuntu is horrible. I can't stop the tearing no matter what i do.
It works with 340, but that is old. I think it does not even support Vulkan.

Khronos Group has released Vulkan API version 1.1 today, new NVIDIA beta driver & AMD driver available
7 Mar 2018 at 9:21 pm UTC Likes: 2

Quoting: Guest
Quoting: FifteenthPenYay, just what I always wanted, built-in DRM support! :/
Might not be what you want, but it is what the rest of the software industry wants.

HLSL support would be excellent.. though I imagine this is more a HLSL -> SPIR-V compiler, which is still excellent. D3D Shader Binary -> SPIR-V bytecode should be easier to do than the current binary->GLSL path.
Rest of the industry wants to hold back progression with cancer. I get it. ;)