Hi. I have the same problem here on openSuse 42.3 also with a Gainward card (GTX 770)
The problem seems to be unrelated to the DE, it happens in Plasma5 as well as in XFCE
Can we get nvidia bug report log file?
Here you go:
https://killkenny.spdns.org/nextcloud/index.php/s/hU09mPBr7ttvPhA
I couldn’t find an attach button…
01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
http://www.gainward.com/main/vgapro.php?id=913&lang=en
Memory:
2 GB
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 331.38 (buildmeister@swio-display-x64-rhel04-15) Wed Jan 8 19:53:14 PST 2014
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
# InputDevice "Keyboard0" "CoreKeyboard"
# InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
ModulePath "/usr/lib32/opengl/nvidia"
ModulePath "/usr/lib32/xorg/modules"
ModulePath "/usr/lib64/opengl/nvidia"
ModulePath "/usr/lib64/xorg/modules"
EndSection
#Section "InputDevice"
# # generated from data in "/etc/conf.d/gpm"
# Identifier "Mouse0"
# Driver "mouse"
# Option "Protocol"
# Option "Device" "/dev/input/mice"
# Option "Emulate3Buttons" "no"
# Option "ZAxisMapping" "4 5"
#EndSection
#Section "InputDevice"
# # generated from default
# Identifier "Keyboard0"
# Driver "kbd"
# Option "XkbRules" "xorg"
# Option "XbkModel" "pc105"
# Option "XkbLayout" "de"
#EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "nvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "GlyphCache" "1"
# Option "InitialPixmapPlacement" "2"
Option "NoLogo" "1"
Option "RenderAccel" "1"
#greedy might improve performance, always is default
#greedy for desktop
#always for gaming
# Option "MigrationHeuristic" "greedy"
#by default on - on new enough X-servers, 24bit, 32bit
Option "AddARGBGLXVisuals" "1"
# Option "TripleBuffer" "1"
Option "DamageEvents" "1"
Option "BackingStore" "1"
Option "OnDemandVBlankInterrupts" "1"
# Option "UseEDID" "false"
#security relevant
Option "AllowIndirectGLXProtocol" "0"
Option "Coolbits" "1"
Option "RegistryDwords" "OGL_MaxFramesAllowed=0x0"
Option "ConnectToAcpid" "0"
# Option "RegistryDwords" "OGL_MaxFramesAllowed=0x0; EnableBrightnessControl=1; PowerMizerEnable=0x1; PerfLevelSrc=0x2222; PowerMizerDefaultAC=0x1"
# # Force proper vsync - i.e. no flicker in Firefox
# Option "metamodes" "nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
# Option "metamodes" "nvidia-auto-select +0+0 { ForceCompositionPipeline = On }"
EndSection
Section "Screen"
Identifier "Screen0"
Device "nvidia"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "ServerFlags"
Option "AIGLX" "on"
#Option "AllowDeactivateGrabs" "true"
Option "XEVIE" "Enable"
Option "Xinerama" "0"
EndSection
No difference if UseEDID is set to false or true
Kernel was 4.12.4 based with btrfs changes + VRQ scheduler (Commits · cchalpha/linux-gc · GitHub)
DE:
Xfce 4.12 ,
WM:
xfwm4 (4.13.0) [compositing was enabled if I recall correctly], compiz 0.9.13 r4103
also occurred with root account and Xfce with xfwm4 (compositing enabled ?)
Issue seemed to NOT occur while browsing with chromium (w. gpu acceleration activated), so this at least seems to confirm = higher power states, doesn’t appear,
while idle or reading a text = appears
Distribution:
~amd64 GNU Gentoo Linux
Further commands passed to kernel:
nowatchdog intel_pstate=disable snd-hda-intel.enable_msi=1 intel_iommu=on console=tty1 memory_corruption_check=1 threadirqs modprobe.blacklist=nouveau modprobe.blacklist=intel modprobe.blacklist=ttm modprobe.blacklist=drm nomodeset cgroup_disable=memory zswap.zpool=z3fold nmi_watchdog=0 nowatchdog nosoftlockup
cpu governor is performance
CPU:
Intel(R) Xeon(R) CPU E3-1245 v3 @ 3.40GHz
Monitor is
Samsung SyncMaster BX2240
Resolution is “Auto” / max:
1920x1080
will upload the bug-report once I find time to install the new driver again
Now compositing is disabled so perhaps that is a hint, will see if it also occurs with compositing disabled
Hi, I have the same problem with Palit GeForce GTX 770 JetStream 4GB on Arch Gnome 3.24.2
have you some news ?
So, how to upload a bug-report ?
I don’t see an option to add an attachment anywhere ?
Anyway …
will delete those after some time
are there lots of connects and disconnects or am I imagining that ?
Hope those logs help to shine some light on this mystery …
On the right upper corner - I see :)
thanks !
Hi,
this also happens on Windows 10, so it’s not exclusive to the Linux part of the driver.
Specs
- CPU : Intel Xeon E3 1231 v3
- Graphics Card: Palit GeForce GTX 770 JetStream, 4GB GDDR5, 2x DVI, HDMI
- Motherboard : ASRock H97 Pro4
- Ram : 16 GB
OS
- Arch Linux
- Windows 10 Home 64bit Version 1607 Build 14393.1593
On both systems (Linux 384.59, Windows 384.94) the screen starts to flicker and after a while it goes black without recovering.
I have to reboot to get something on the screen again. Version 382.x works fine on both systems.
Cannot confirm for 385.28 on Windows 10 Pro,
previous driver was 382.33
both work fine,
issue for me is only on Linux with 384.59
Specs
- CPU: Intel Xeon E3-1245 v3 GPU: Gainward GeForce GTX 760 Phantom, 2 GB MB: Asus P9D WS RAM: ECC 32GB
OS
- Gentoo Linux, 4.12.y kernel [affected] Windows 10 Pro 64bit Version 1703 (Creators Update) [afaik, have to take a look when I'm back in Win] [non-affected]
will see if I find some time to test 384.59 on windows ^^
Yeah, Windows Build 1703,
seems like there’s also an issue with 385.28, yesterday the screen turned black after session of 1-2 hours of ME:Andromedia Multiplayer,
the keyboard status of numlock still changed, so the system was sort of still in a working state - at the beginning the keyboard status was slow to react.
I “locked” the screen via windows + l, then it reacted quicker
No way to “revive” the system or reset the display state
could be close to the issue Edishtron mentioned,
still no observation of flickering though
gtx 760 performance level 0 flickering
I have a similar problem.
#lspci -v
01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Palit Microsystems Inc. GK104 [GeForce GTX 760]
#lspci -vn
01:00.0 0300: 10de:1187 (rev a1) (prog-if 00 [VGA controller])
Subsystem: 1569:1187
#uname -a
Linux fred 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
#cat /etc/issue
Ubuntu 16.04.3 LTS
#aptitude show nvidia-381
Version: 381.22-0ubuntu0~gpu16.04.2
381 works fine, no flicker at Performance level 0,1,2,3.
#aptitude show nvidia-384
Version: 384.69-0ubuntu0~gpu16.04.1
384 shows flicker at performance level 0. It is OK at level 1,2,3.
In nvidia-settings:
Set it to “Performance” and it keeps the card at level 3, so no flicker.
Set it to “Auto” and if you are running nothing apart from nvidia-settings, it moves down to 2->1->0, and when at 0, it flickers.
Switching back to “Performance”, and thus back to level 3 results in no flicker.
It appears to me just the same as in the previously posted clip:
The flicker shows itself on both DVI connections, and also the HDMI connection.
I am not able to test any other connections.
The only other difference I notice is the resolution of the boot up screen, where it lists, in text mode, each part of the system starting.
On nvidia-381, the text is larger than on nvidia-384.
I am a Linux Kernel developer so I should be able to help if you need a more technical investigation done. Please ask me what you need.
I’m using simplefb + UEFI mode, btw
the following lines are in /etc/modprobe.d/nvidia.conf
# Nvidia drivers support
alias char-major-195 nvidia
alias /dev/nvidiactl char-major-195
options nvidia NVreg_DeviceFileMode=432 NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=27 NVreg_ModifyDeviceFiles=1
options nvidia NVreg_EnableMSI=1
options nvidia NVreg_RegisterForACPIEvents=0
options nvidia NVreg_UsePageAttributeTable=1
no issues with MTRR / PAT
dmesg | grep -i mtrr
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] Found optimal setting for mtrr clean up
The following “tweak” is used alongside
threadirqs
argument after starting the desktop environment
peth=$(pgrep "irq/.*-eth")
[[ -n $peth ]] && chrt -f -p 75 $peth
# ehci instead of uhci
pmouse=$(pgrep "irq/23-ehci")
[[ -n $pmouse ]] && chrt -f -p 79 $pmouse
pmouse=$(pgrep "irq/20-ehci")
[[ -n $pmouse ]] && chrt -f -p 79 $pmouse
#pmouse=$(pgrep "irq/19-uhci")
#[[ -n $pmouse ]] && chrt -f -p 59 $pmouse
# ehci instead of uhci
pkey=$(pgrep "irq/23-ehci")
[[ -n $pkey ]] && chrt -f -p 79 $pkey
pmouse=$(pgrep "irq/20-ehci")
[[ -n $pkey ]] && chrt -f -p 79 $pkey
psnd=$(pgrep "irq/.*-snd_")
[[ -n $psnd ]] && chrt -f -p 85 $psnd
#pnouveau=$(pgrep "irq/.*-nouveau")
#[[ -n $pnouveau ]] && chrt -f -p 80 $pnouveau
pnvkm=$(pgrep "irq/.*-nvkm")
[[ -n $pnvkm ]] && chrt -f -p 84 $pnvkm
pnvkm=$(pgrep "irq/.*-i915")
[[ -n $pi915 ]] && chrt -f -p 84 $pi915
pnvidia=$(pgrep "irq/.*-nvidia")
[[ -n $pnvidia ]] && chrt -f -p 84 $pnvidia
prtc=$(pgrep "irq/.*-rtc0")
[[ -n $prtc ]] && chrt -f -p 90 $prtc
desktop environment is run from user context via startx (no xdm, no daemon running, X still with root (suid ?) permissions though, etc.)
@sandipt I hope that’s starting to become enough information for you guys to reproduce :)
Hi kernelOfTruth, Is this issue also reproduce if you remove all the Register Keys you are using with xorg.conf and at other areas and removing argument after starting the desktop environment? Just backup you exiting xorg.conf file and generate default xorg.conf with nvidia-xconfig and reboot system and test. Make sure to blacklist nouveau driver. I’m trying to find of simple config and reproduction steps that can trigger this issue.
Hi sandipt,
yes, it still happens,
the newly created xorg.conf looks as follows (currently on 381.22 and no issues):
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 384.69 (buildmeister@swio-display-x86-rhel47-06) Wed Aug 16 20:57:01 PDT 2017
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from data in "/etc/conf.d/gpm"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
this time I tried out the 384.69 driver and the same issue: heavy flickering,
the flickering happens as root user, when X is launched via startx as root,
or as user via startx.
Compositing also doesn’t seem to make a difference (e.g. of xfwm4 as root),
when idle it still flickers.
So it’s clearly related to the power state, as soon as it drops to state 0 (monitored via nvidia-settings app) it begins to flicker heavily.
It doesn’t matter if I comment out the following entries in /etc/modprobe.d/nvidia.conf or leave them in (tested with module unloading in between):
options nvidia NVreg_DeviceFileMode=432 NVreg_DeviceFileUID=0 NVreg_DeviceFi$
15 options nvidia NVreg_EnableMSI=1
16 options nvidia NVreg_RegisterForACPIEvents=0
17 options nvidia NVreg_UsePageAttributeTable=1
with settings in modprobe.conf.d
[ 69.904861] NVRM: Your system is not currently configured to drive a VGA console
on the primary VGA device. The NVIDIA Linux graphics driver
requires the use of a text-mode VGA console. Use of other console
drivers including, but not limited to, vesafb, may result in
corruption and stability problems, and is not supported.
[ 69.321503] nvidia-nvlink: Nvlink Core is being initialized, major device number 243
[ 69.321818] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[ 69.321884] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 384.69 Wed Aug 16 19:34:54 PDT 2017 (using threaded interrupts)
without settings in modprobe.conf.d
[ 255.900404] nvidia-nvlink: Nvlink Core is being initialized, major device number 243
[ 255.900633] nvidia 0000:01:00.0: enabling bus mastering
[ 255.900636] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=io+mem
[ 255.900688] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 384.69 Wed Aug 16 19:34:54 PDT 2017 (using threaded interrupts)
[ 256.459606] NVRM: Your system is not currently configured to drive a VGA console
on the primary VGA device. The NVIDIA Linux graphics driver
requires the use of a text-mode VGA console. Use of other console
drivers including, but not limited to, vesafb, may result in
corruption and stability problems, and is not supported.
[ 256.465916] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 384.69 Wed Aug 16 19:39:44 PDT 2017
[ 256.467648] nvidia-modeset: Allocated GPU:0 (GPU-d99d8f91-a286-ebc2-1bbb-637e31f6df04) @ PCI:0000:01:00.0
nvidia-bug-report_384.69.log.gz (217 KB)
nvidia-bug-report_384.69_2.log.gz (217 KB)
Hi,
Given that while running the “nvidia-bug-report” script, the flickering stops, and it returns to performance level 3 for the duration of the running of “nvidia-bug-report”.
I would suggest that “nvidia-bug-report” is not a suitable tool for diagnosing this problem.
+1
I can confirm that this is a major bug (OS breaking) on the driver 384.69 for 980TI.