You are not logged in.

#1 2017-05-06 03:33:50

apetresc
Member
From: Toronto, Canada
Registered: 2017-01-26
Posts: 14
Website

Problems after upgrading to NVidia GTX 1080 Ti

Hey all,

I've been running Arch on my old NVidia GTX 550 Ti for few years without any issues. Today, I upgraded to an NVidia GTX 1080Ti. Since the current stable nvidia driver doesn't recognize the 1080Ti (it just thinks it's a "Generic VGA Adapter"), I installed nvidia-full-beta from AUR (which corresponds to version 381.09 of the binary NVidia driver). This required me to first uninstall nvidia and nvidia-utils, of course.

The driver seems to be working fine. nvidia-settings now correctly identifies my card as an NVidia GTX 1080 Ti, all the diagnostics seem to check out, etc. However, I'm now facing two big problems:

  • One of my two monitors, which had always worked properly on the 550Ti, is suddenly stuck at a 1920x1080 resolution even though its native resolution is 2560x1440. `xrandr --query` also shows only resolutions up to 1920x1080. When I try to manually add the mode to xrandr, I get:

    $ xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync
    $ xrandr --addmode DP-3 "2560x1440_60.00"
    X Error of failed request:  BadMatch (invalid parameter attributes)
      Major opcode of failed request:  140 (RANDR)
      Minor opcode of failed request:  18 (RRAddOutputMode)
      Serial number of failed request:  43
      Current serial number in output stream:  44
  • When I try to run games that used to work just fine (often through wine), they fail with errors like:

    libGL error: No matching fbConfigs or visuals found
    libGL error: failed to load driver: swrast
    X Error of failed request:  BadValue (integer parameter out of range for operation)
      Major opcode of failed request:  154 (GLX)
      Minor opcode of failed request:  3 (X_GLXCreateContext)
      Value in failed request:  0x0
      Serial number of failed request:  166
      Current serial number in output stream:  170
    libGL error: No matching fbConfigs or visuals found
    libGL error: failed to load driver: swrast
    X Error of failed request:  BadValue (integer parameter out of range for operation)
      Major opcode of failed request:  154 (GLX)
      Minor opcode of failed request:  3 (X_GLXCreateContext)
      Value in failed request:  0x0
      Serial number of failed request:  424
      Current serial number in output stream:  428

    This would seem to imply that I haven't installed libgl, but I did install nvidia-libgl-full-beta which presumably would include it.

Can anyone tell what I'm doing wrong? Should I just go back to the normal `nvidia` driver even though it doesn't explicitly recognize my card? What are other people with GTX 1080Ti's on Arch doing?

Thanks!

Last edited by apetresc (2017-05-06 03:35:55)

Offline

#2 2017-05-06 06:05:32

tom.ty89
Member
Registered: 2012-11-15
Posts: 897

Re: Problems after upgrading to NVidia GTX 1080 Ti

For the first problem, you should check xorg log, usually nvidia driver has a reason (valid or not) for not including certain modes from the EDID, and there are xorg conf options that can override the decision.

For the second problem, have you forgotten to install (lib32-)nvidia-utils-full-beta? Also, I can see in the PKGBUILD that it still makes -libgl packages, so I am not sure if (lib32)-libglvnd work well with this. In case it still doesn't work after you installed the -utils package and restarted X, you may want to try replace the libglvnd packages with the -libgl packages.

Last edited by tom.ty89 (2017-05-06 06:06:56)

Offline

#3 2017-05-06 14:16:43

apetresc
Member
From: Toronto, Canada
Registered: 2017-01-26
Posts: 14
Website

Re: Problems after upgrading to NVidia GTX 1080 Ti

tom.ty89 wrote:

For the first problem, you should check xorg log, usually nvidia driver has a reason (valid or not) for not including certain modes from the EDID, and there are xorg conf options that can override the decision.

Hmm, I checked and didn't see anything that looked relevant. Here's a gist to Xorg.0.log, there doesn't seem to be anything out of the ordinary. The monitor with the wrong resolution is the Samsung SMS27A850. It's plugged into the card's DP port using a DP-DVI adapter, if that's relevant?

(Also, out of curiosity, why does Xorg think my mic is a keyboard? It still works! :smile:)

tom.ty89 wrote:

For the second problem, have you forgotten to install (lib32-)nvidia-utils-full-beta? Also, I can see in the PKGBUILD that it still makes -libgl packages, so I am not sure if (lib32)-libglvnd work well with this. In case it still doesn't work after you installed the -utils package and restarted X, you may want to try replace the libglvnd packages with the -libgl packages.

Nope, I had definitely installed lib32-nvidia-utils-full-beta. I'm not sure I understand the second part - I should remove lib32-libglvnd and replace it with which -libgl package?

I've temporarily reverted to the normal nvidia and nvidia-utils packages from extra. This solves problem 2 (libgl stuff works great again), but my monitor is still stuck on the bad resolution sad

Offline

#4 2017-05-06 15:28:17

tom.ty89
Member
Registered: 2012-11-15
Posts: 897

Re: Problems after upgrading to NVidia GTX 1080 Ti

The adapter certainly matters. AFAIK passvie DP->DVI are always single-link DVI. And yours IS:

[    10.047] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-4): 165.0 MHz maximum pixel clock

According to the mode line you tried to add, you certainly need dual-link DVI for it, since the pixel clock is way higher than 165 MHz. (312.5 MHz, precisely 3488 x 1493 x 60 = 312,455,040 Hz)

Even if you calculate from 2560 x 1440 x 60, the pixel clock is much higher than 165 MHz.

(USB mic? Quite some USB Audio devices have HID interface(s), never know what they are really for though)

You simply install the -libgl packages with pacman -U or your aur helper, it should prompt about package conflict and replacing libglvnd with the packages, just say yes to the prompts. To revert, pacman -S libglvnd lib32-libglvnd and react similarly.

Last edited by tom.ty89 (2017-05-06 15:55:16)

Offline

#5 2017-05-06 17:07:48

apetresc
Member
From: Toronto, Canada
Registered: 2017-01-26
Posts: 14
Website

Re: Problems after upgrading to NVidia GTX 1080 Ti

tom.ty89 wrote:

The adapter certainly matters. AFAIK passvie DP->DVI are always single-link DVI. And yours IS:

[    10.047] (--) NVIDIA(GPU-0): Samsung SMS27A850 (DFP-4): 165.0 MHz maximum pixel clock

According to the mode line you tried to add, you certainly need dual-link DVI for it, since the pixel clock is way higher than 165 MHz. (312.5 MHz, precisely 3488 x 1493 x 60 = 312,455,040 Hz)

Even if you calculate from 2560 x 1440 x 60, the pixel clock is much higher than 165 MHz.

Oooh, I see - I didn't know that's what pixel clock is measuring. Thanks for the insight, I know what to fix now, then smile


tom.ty89 wrote:

You simply install the -libgl packages with pacman -U or your aur helper, it should prompt about package conflict and replacing libglvnd with the packages, just say yes to the prompts. To revert, pacman -S libglvnd lib32-libglvnd and react similarly.

Yup, that's exactly what I did; my question was more what do you mean by "-libgl" packages, since there's a dizzying amount of them. Do you mean just lib32-libgl, lib32-mesa-libgl, nvidia-libgl, mesa-libgl, lib32-nvidia-libgl? And then there's permutations of some of those with -beta and -full-beta, etc.

When I had posted this thread, I had installed nvidia-full-beta, nvidia-libgl-full-beta, nvidia-utils-full-beta, lib32-nvidia-libgl-full-beta, and lib32-nvidia-utils-full-beta (and lib32-opencl-nvidia-full-beta for neural network purposes but that's unrelated to this problem). Am I missing anything from this list?

Thanks again for all your patient help, Tom! smile

Offline

#6 2017-05-06 17:31:12

tom.ty89
Member
Registered: 2012-11-15
Posts: 897

Re: Problems after upgrading to NVidia GTX 1080 Ti

apetresc wrote:

my question was more what do you mean by "-libgl" packages

Oh sorry I didn't thought that could be ambiguous to you. I mean the -libgl packages produced with the nvidia-full-beta PKGBUILD.

Just notice that I missing this in your first post:

apetresc wrote:

This would seem to imply that I haven't installed libgl, but I did install nvidia-libgl-full-beta which presumably would include it.

In that case have you tried if (lib32-)libglvnd works instead?

Offline

Board footer

Powered by FluxBB