Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Driver Manager screenshot [imgur.com]
Keep in mind the Driver manager will look for the drivers which is the most stable, meaning it *could* not be the latest from Nvidia. But there's a way to address that as well: Just add this PPA: ppa:graphics-drivers/ppa which belongs to this package manager[launchpad.net]. Once you've added that ppa, download the latest driver from Update Manager and it will do the rest, from compiling the source, building the installer and getting it installed on your computer. After the newest driver is installed, fire up Driver Manager again and from there, you can tell the system which one you'd like to have enabled.
In my case, the most stable driver is 390.48-0ubuntu3 but I decided to stick to the latest 396.45-0ubuntu0~gpu18.04.2 and never looked back. I hope that helps.
Thank you this does help a lot, sadly I did the same thing and tried various driver versions but the way I did it was much harder than your version so I took note. Went through lots of various old drivers looking for ones that could work. Every time I would get the "Cinnamon just crashed. You are currently running in fallback mode" message until I went to Mate, at which point Mate works but it runs excessively slow and buggy with any drivers I have tried to the point of me going back to Windows for general computer use and gaming.
The funny thing, back with Linux Mint 15 and 16 I had no issues. It was after I got a 1060GTX and tried various versions of Linux Mint 17 and 18 that I had all these issues, my 960GTX doesn't have near as many problems with various Linux OS's.
EDIT: And this is nit-picking but my Asux Xonar DG audio card glitches out all over the place as of Linux Mint 18, I had to enable/disable counter-intuitive options until a certain combination made it so my headset would work but my speakers would never work as long as my headset was left plugged in the front ports. I love Linux, was a Cedega guy back on Ubuntu before Unity ruined that, gamed on Linux Mint for about a year via Steam and WINE, but the recent issues I had a few months ago trying to get Linux Mint to work kinda pushed me to going into the simple "Win7 works after installing factory drivers and I leave it at that" state lol.
Since Linux Mint 19 came out I'm considering installing that on a spare 1TB HDD I had left in my rig to see if I still have the major issues with my 1060GTX and Asus Xonar, definitely need to wait to do it when I'm chilled out and have a high frustration threshhold though based on past experiences.
I also tried Helldivers recently with same problem with internet connection to the servers. Suggests opening a port 443 in firewall... and in offline play choosing mission crashes the game.
ln -s /usr/lib/x86_64-linux-gnu/libgnutls.so.30 ~/.steam/steam/ubuntu12_32/steam-runtime/pinned_libs_64/libgnutls.so.26
And for 32-bit:
ln -s /usr/lib/i386-linux-gnu/libgnutls.so.30 ~/.steam/steam/ubuntu12_32/steam-runtime/pinned_libs_32/libgnutls.so.26
But then Proton 3.16-x became a thing and now, when launching the game, if it detects those symlinked files in pinned_libs, the game will not launch. Instead, it will page fault, rendering the game useless because Helldivers relies heavily and deeply on their gallactic campaign.
Currently there are no workarounds to get multiplayer fixed, but I suggest you follow these Github threads about libgnutls, which is the one to blame for the lack of working multiplayer (no, enabling port 443 in your firewall settings will not fix this problem):
https://github.com/ValveSoftware/Proton/issues/632#issuecomment-445554278
https://github.com/ValveSoftware/Proton/issues/727