I created a combo runtime patch for NVIDIA 410.73 on Kernel 4.20-rc1, by combining the changes identified in my previous article ( see http://rglinuxtech.com/?p=2426 ) with the pm patch (see http://rglinuxtech.com/?p=2421 ).

The result ran – eventually – after blanking/refreshing the display, with garbage characters at top/bottom, so all was obviously not OK..

...........................
[ 121.826292] [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver
[ 121.972324] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d8000-0x000dbfff window]
[ 121.972471] caller _nv001126rm+0xe3/0x1d0 [nvidia] mapping multiple BARs
[ 125.546191] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[ 125.565592] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 125.565593] [drm] No driver support for vblank timestamp query.
[ 125.646943] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:02:00.0 on minor 0
[ 135.550609] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[ 138.805999] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[ 142.181899] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[ 199.227105] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[ 202.773576] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[ 206.041776] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
...........................

The (KDE/Plasma) screen seemed to be OK after that, but this is obviously not an ideal solution!

Robert Gadsdon.   November 5, 2018.