[Solved] Bad performance of Nvidia 3080/ cannot change resolution, refresh rate

Hello there,

Just recently got into the linux scene, so bear with me :smiley:
I installed Zorin 16 Pro and have been having a hard time with my Nvidia drivers it seems. My monitor is also kinda not really recognized? In the trial version of Zorin I was able to change my resolution and refresh rate, but now I cant.

As you can see in the screenshot Im kinda limited :smiley:
Next to that, It seems like I am unable to get any good performance on any video game, say Minecraft or World of Warcraft, all these games run like trash for some reason.

Thank you in advance for all the help.

Hi, have you tried nvidia-settings for switching resolution? Which driver are you using? (guessing it's v. 470 with that powerhorse card you have). I don't know if your card is supported in driver v.460 but I have glitches with my 1070 card on v.470 so I switch driver.

Correct! Im using the 470 right now, I also tried swapping to 470 server if that resolved something, but nope.
With Nvidia settings, you mean the Nvidia X server settings program? Otherwise I cant find the program that youre referring to :slight_smile:

Try in terminal;

nvidia-settings

Yup, that gives me this:
Schermafdruk van 2021-08-21 17-16-27
Kinda weird how its blank

Hmm, I also tried the 460 driver as you suggested, but no cigar :frowning: Still a blank Settings menu and bad performance. Am I doomed to go back to windows? :frowning:

sudo apt-get install nvidia-current \ nvidia-current-modaliases nvidia-settings

sudo nvidia-xconfig

any love, there?

wessel@wessel-MD35081:~$ sudo apt-get install nvidia-current \ nvidia-current-modaliases nvidia-settings
[sudo] wachtwoord voor wessel:         
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd       
De statusinformatie wordt gelezen... Klaar
Pakket nvidia-current is niet beschikbaar, hoewel er naar verwezen wordt door
een ander pakket. Mogelijk betekent dit dat het pakket ontbreekt,
verouderd is, of enkel beschikbaar is van een andere bron

E: Pakket 'nvidia-current' heeft geen kandidaat voor installatie
E: Kan pakket  nvidia-current-modaliases niet vinden
wessel@wessel-MD35081:~$ sudo nvidia-xconfig

WARNING: Unable to locate/open X configuration file.

Package xorg-server was not found in the pkg-config search path.
Perhaps you should add the directory containing `xorg-server.pc'
to the PKG_CONFIG_PATH environment variable
No package 'xorg-server' found
New X configuration file written to '/etc/X11/xorg.conf'

I took the liberty of throwing it through DeepL, so its not in Dutch :wink:

Package lists are being read in... Ready
    Tree of requirements is being built       
    Status information is being read... Ready
    Package nvidia-current is not available, although it is referenced by
    another package. Possibly this means that the package is missing,
    outdated, or is only available from another source

    E: Package 'nvidia-current' has no candidate for installation
    E: Could not find package 'nvidia-current-modaliases

Soo, I guess also no? :frowning:

1 Like

You already have bad performance, so no need to avoid risk... Ensure Secure Boot is disabled, first.
If your fallback graphics is intel:

prime-select intel

Then

sudo ubuntu-drivers devices

sudo ubuntu-drivers autoinstall

Reboot and test...

What is kind of weird is when I disable secure boot, I come sort of come into the Zorin login menu if that makes sense?
Normally you select your name etc with login, where without secure boot, I end up at a blurry screenshot of my background without the ability to put in my login credentials.

Perhaps it makes it easier if I add my complete PC specs, I honestly have no clue if there is an integrated intel backup for my GPU.

Specs:
https://www.vergelijkdesktops.nl/desktop/medion/medion-erazer-hunter-x62-md35081/specificaties

Under Grafische kaart:
Dedicated

Processor:
Intel Core i9

Nice machine.

Did you set up a password for Secure Boot in your EFI settings? OR is there one that came with the machine?

Thank you :slight_smile:
I only put a secure boot password up during installation of Zorin, which is also always asked when I try to change the driver settings :smiley: so maybe that might be the case?
My installation is pretty fresh, so I can always reinstall without a password set for the secure boot, and hence removing this issue?

1 Like

I would absolutely go for this. Maybe it won't work but... It seems the best shot.

A password on MB's secure boot... Yeah I can see how that would block proper driver performance easily.
Even if it doesn't resolve the issue at hand, it may prevent others.

Alright! Then Im going to do a fresh install, Ill report back once its completed! Fingers crossed :smiley:

1 Like

Ok, this is a weird one.

I reinstalled the system with secure boot disabled, and guess what, when I try to log in again, I get to this screen, same as before, weirdest thing I have ever seen :smiley:
When I re-enable secure boot I am able to log in to the fresh install session.

See attached screenshot, any ideas?

Yeah, it's uhh... it's blue.

2 Likes

Very blue XD

1 Like

Are you Dual Booting another OS? Windows?
Terminal output of

mokutil --list-enrolled

Nope, only Zorin 16 Pro at the moment!

wessel@MD35081:~$ mokutil --list-enrolled
[key 1]
SHA1 Fingerprint: 76:a0:92:06:58:00:bf:37:69:01:c3:72:cd:55:a9:0e:1f:de:d2:e0
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            b9:41:24:a0:18:2c:92:67
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=GB, ST=Isle of Man, L=Douglas, O=Canonical Ltd., CN=Canonical Ltd. Master Certificate Authority
        Validity
            Not Before: Apr 12 11:12:51 2012 GMT
            Not After : Apr 11 11:12:51 2042 GMT
        Subject: C=GB, ST=Isle of Man, L=Douglas, O=Canonical Ltd., CN=Canonical Ltd. Master Certificate Authority
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                RSA Public-Key: (2048 bit)
                Modulus:
                    00:bf:5b:3a:16:74:ee:21:5d:ae:61:ed:9d:56:ac:
                    bd:de:de:72:f3:dd:7e:2d:4c:62:0f:ac:c0:6d:48:
                    08:11:cf:8d:8b:fb:61:1f:27:cc:11:6e:d9:55:3d:
                    39:54:eb:40:3b:b1:bb:e2:85:34:79:ca:f7:7b:bf:
                    ba:7a:c8:10:2d:19:7d:ad:59:cf:a6:d4:e9:4e:0f:
                    da:ae:52:ea:4c:9e:90:ce:c6:99:0d:4e:67:65:78:
                    5d:f9:d1:d5:38:4a:4a:7a:8f:93:9c:7f:1a:a3:85:
                    db:ce:fa:8b:f7:c2:a2:21:2d:9b:54:41:35:10:57:
                    13:8d:6c:bc:29:06:50:4a:7e:ea:99:a9:68:a7:3b:
                    c7:07:1b:32:9e:a0:19:87:0e:79:bb:68:99:2d:7e:
                    93:52:e5:f6:eb:c9:9b:f9:2b:ed:b8:68:49:bc:d9:
                    95:50:40:5b:c5:b2:71:aa:eb:5c:57:de:71:f9:40:
                    0a:dd:5b:ac:1e:84:2d:50:1a:52:d6:e1:f3:6b:6e:
                    90:64:4f:5b:b4:eb:20:e4:61:10:da:5a:f0:ea:e4:
                    42:d7:01:c4:fe:21:1f:d9:b9:c0:54:95:42:81:52:
                    72:1f:49:64:7a:c8:6c:24:f1:08:70:0b:4d:a5:a0:
                    32:d1:a0:1c:57:a8:4d:e3:af:a5:8e:05:05:3e:10:
                    43:a1
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Subject Key Identifier: 
                AD:91:99:0B:C2:2A:B1:F5:17:04:8C:23:B6:65:5A:26:8E:34:5A:63
            X509v3 Authority Key Identifier: 
                keyid:AD:91:99:0B:C2:2A:B1:F5:17:04:8C:23:B6:65:5A:26:8E:34:5A:63

            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Key Usage: 
                Digital Signature, Certificate Sign, CRL Sign
            X509v3 CRL Distribution Points: 

                Full Name:
                  URI:http://www.canonical.com/secure-boot-master-ca.crl

    Signature Algorithm: sha256WithRSAEncryption
         3f:7d:f6:76:a5:b3:83:b4:2b:7a:d0:6d:52:1a:03:83:c4:12:
         a7:50:9c:47:92:cc:c0:94:77:82:d2:ae:57:b3:99:04:f5:32:
         3a:c6:55:1d:07:db:12:a9:56:fa:d8:d4:76:20:eb:e4:c3:51:
         db:9a:5c:9c:92:3f:18:73:da:94:6a:a1:99:38:8c:a4:88:6d:
         c1:fc:39:71:d0:74:76:16:03:3e:56:23:35:d5:55:47:5b:1a:
         1d:41:c2:d3:12:4c:dc:ff:ae:0a:92:9c:62:0a:17:01:9c:73:
         e0:5e:b1:fd:bc:d6:b5:19:11:7a:7e:cd:3e:03:7e:66:db:5b:
         a8:c9:39:48:51:ff:53:e1:9c:31:53:91:1b:3b:10:75:03:17:
         ba:e6:81:02:80:94:70:4c:46:b7:94:b0:3d:15:cd:1f:8e:02:
         e0:68:02:8f:fb:f9:47:1d:7d:a2:01:c6:07:51:c4:9a:cc:ed:
         dd:cf:a3:5d:ed:92:bb:be:d1:fd:e6:ec:1f:33:51:73:04:be:
         3c:72:b0:7d:08:f8:01:ff:98:7d:cb:9c:e0:69:39:77:25:47:
         71:88:b1:8d:27:a5:2e:a8:f7:3f:5f:80:69:97:3e:a9:f4:99:
         14:db:ce:03:0e:0b:66:c4:1c:6d:bd:b8:27:77:c1:42:94:bd:
         fc:6a:0a:bc

Your cause for blue screen.

I think just disabling the Secure boot and reinstalling the OS (Which is separate from the Motherboards OS that governs secure boot) is not enough.