opensuse 410.73 vs 410.6

Hello,

I bought a dell g7 with 1060GTX mobile and optimus technologies. Three months later I caught up on reading and see that optimus is not very well supported on linux. So at manufacturer suggestion I st it up for prime switching. On the 410.6 driver I was getting around 20,000fps on glx gears.

https://photos.google.com/photo/AF1QipOJwP-ln4l7ovYrtEkruhILTbP7gehxYMUKPDc

Today I just upgraded to 410.73 and my results are:

daryl@G7:~> inxi -G
Graphics:
  Device-1: Intel driver: i915 v: kernel
  Device-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] driver: nvidia v: 410.73
  Display: x11 server: X.Org 1.20.2 driver: modesetting FAILED: nvidia
  resolution: 1920x1080~60Hz
  OpenGL: renderer: llvmpipe (LLVM 6.0 256 bits) v: 3.3 Mesa 18.1.7
daryl@G7:~> glxgears
10782 frames in 5.0 seconds = 2156.336 FPS
11517 frames in 5.0 seconds = 2303.386 FPS
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 87670 requests (87668 known processed) with 0 events remaining.
daryl@G7:~>

Is there anything I can provide that may explain the near 10x loss in performance?

Saw this in /var/log/Xorg.0.log:

19.937] (II) Module fb: vendor="X.Org Foundation"
[    19.937]    compiled for 1.20.2, module version = 1.0.0
[    19.937]    ABI class: X.Org ANSI C Emulation, version 0.4
[    19.950] (==) modeset(G0): Backing store enabled
[    19.950] (==) modeset(G0): Silken mouse enabled
[    19.989] (II) modeset(G0): Initializing kms color map for depth 24, 8 bpc.
[    19.990] (==) modeset(G0): DPMS enabled
[    19.990] (WW) modeset(G0): Option "AllowEmptyInitialConfiguration" is not used
[    19.990] (WW) modeset(G0): Option "UseDisplayDevice" is not used
[    19.991] (II) modeset(G0): [DRI2] Setup complete
[    19.991] (II) modeset(G0): [DRI2]   DRI driver: i965
[    19.991] (II) modeset(G0): [DRI2]   VDPAU driver: i965
[    19.992] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
[    19.992] (II) NVIDIA:     access.
[    19.998] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    19.998] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    19.998] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    19.998] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    19.998] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    19.998] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    19.998] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    19.998] (II) NVIDIA(0):     Config Options in the README.
[    20.011] (II) NVIDIA(0): Setting mode "NULL"
[    20.014] (==) NVIDIA(0): Disabling shared memory pixmaps
[    20.014] (==) NVIDIA(0): Backing store enabled
[    20.014] (==) NVIDIA(0): Silken mouse enabled
[    20.014] (==) NVIDIA(0): DPMS enabled
[    20.014] (II) Loading sub module "dri2"
[    20.014] (II) LoadModule: "dri2"
[    20.014] (II) Module "dri2" already built-in
[    20.014] (II) NVIDIA(0): [DRI2] Setup complete
[    20.014] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    20.014] (II) Initializing extension Generic Event Extension
[    20.014] (II) Initializing extension SHAPE
[    20.014] (II) Initializing extension MIT-SHM
[    20.014] (II) Initializing extension XInputExtension
[    20.015] (II) Initializing extension XTEST
[    20.015] (II) Initializing extension BIG-REQUESTS
[    20.015] (II) Initializing extension SYNC
[    20.015] (II) Initializing extension XKEYBOARD
[    20.015] (II) Initializing extension XC-MISC
[    20.015] (II) Initializing extension SECURITY
[    20.016] (II) Initializing extension XFIXES
[    20.016] (II) Initializing extension RENDER
[    20.016] (II) Initializing extension RANDR
[    20.016] (II) Initializing extension COMPOSITE
[    20.016] (II) Initializing extension DAMAGE
[    20.016] (II) Initializing extension MIT-SCREEN-SAVER
[    20.017] (II) Initializing extension DOUBLE-BUFFER
[    20.017] (II) Initializing extension RECORD
[    20.017] (II) Initializing extension DPMS
[    20.017] (II) Initializing extension Present
[    20.017] (II) Initializing extension DRI3
[    20.017] (II) Initializing extension X-Resource
[    20.017] (II) Initializing extension XVideo
[    20.018] (II) Initializing extension XVideo-MotionCompensation
[    20.018] (II) Initializing extension GLX
[    20.018] (II) AIGLX: Screen 0 is not DRI2 capable
[    20.344] (II) IGLX: Loaded and initialized swrast
[    20.344] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    20.344] (II) Initializing extension XFree86-VidModeExtension
[    20.345] (II) Initializing extension XFree86-DGA
[    20.345] (II) Initializing extension XFree86-DRI
[    20.345] (II) Initializing extension DRI2
[    20.346] (II) Initializing extension NV-GLX
[    20.347] (II) Initializing extension NV-CONTROL
[    20.465] (II) modeset(G0): Damage tracking initialized
[    20.530] randr: falling back to unsynchronized pixmap sharing
[    22.434] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[    22.434] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    22.434] (**) Power Button: Applying InputClass "system-keyboard"
[    22.434] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    22.434] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    22.434] (II) LoadModule: "libinput"
[    22.434] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[    22.439] (II) Module libinput: vendor="X.Org Foundation"
[    22.439]    compiled for 1.20.2, module version = 0.28.1
[    22.439]    Module class: X.Org XInput Driver
[    22.439]    ABI class: X.Org XInput driver, version 24.1

Link to yast hardware report:

https://drive.google.com/open?id=1UWASv5ajKUldPsZCbU2tDVVq3NEKZykQ

Please mark as solved. I ran prime-select to toggle to intel and again to toggle back to nvidia rebooting in between. Seems to have worked. Back up to just under 20k fps in glxgears