Date: Sat, 4 Jun 2016 14:52:26 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: FreeBSD Ports <freebsd-ports@freebsd.org>, freebsd-x11@freebsd.org Subject: x11/nvidia-driver and CURRENT: update results in full fan blow on MSI GTX 960 Gaming 4G Message-ID: <20160604145226.57dd078e.ohartman@zedat.fu-berlin.de>
next in thread | raw e-mail | index | archive | help
--Sig_/DDGh/V2d=dt6cZNf_U29rjq Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Three months ago I purchased a new GPU to replace a non-UEFI capable GTX560= Ti (MSI). The choice was the MSI GTX 960 Gaming 4G. Apart from the part, that this GPU do= esn't show the performance boost on FreeBSD CURRENT, even with the most recent BLOB from n= Vidia, 367.18, I realized that after the update from FreeBSD 11-CURRENT r300830 to r300956= (I guess, Forgot the exact revision number, but it was > 300950), the fans of that sp= ecific GPU blow at full speed when xdm/Xorg server has been started. This is annoying,= since the noise is incredible. I tried to recompile the whole ports xorg relies on via portmaster -df xorg xdm hoping, that some sort of bug or API incompatibility could have caused the = problems, but that wasn't at all the case. I run now r301300 and the "problem" is still present. The environmental conditions did not change - not in a way that the full sp= eed fan of the GPU could be explained by raised temperatures of the environment. I tried t= o find via Google some help, but it seems that I'm the first and only one having this = problem, especially with FreeBSD and this type of GPU. I also tried the official sup= ported x11/nvidia-driver (346.96 and the proposed 364.19) with no success. Below, You will find some data I picked up from the kernel environment (if = there are other ways, please tell me) and the logfile of Xorg/X server. [...] hw.nvidia.gpus.0.type: PCIe hw.nvidia.gpus.0.uuid: GPU-85fde95a-7974-9962-f1a4-d7c164413929 hw.nvidia.gpus.0.vbios: 84.06.26.00.21 hw.nvidia.gpus.0.irq: 270 hw.nvidia.gpus.0.model: GeForce GTX 960 hw.nvidia.registry.dwords:=20 hw.nvidia.registry.TCEBypassMode: 0 hw.nvidia.registry.MemoryPoolSize: 0 hw.nvidia.registry.EnablePCIeGen3: 1 hw.nvidia.registry.CheckPCIConfigSpace: 4294967295 hw.nvidia.registry.RegisterForACPIEvents: 1 hw.nvidia.registry.MapRegistersEarly: 0 hw.nvidia.registry.EnableMSI: 1 hw.nvidia.registry.UsePageAttributeTable: 4294967295 hw.nvidia.registry.InitializeSystemMemoryAllocations: 1 hw.nvidia.registry.UpdateMemoryTypes: 4294967295 hw.nvidia.registry.DeviceFileMode: 438 hw.nvidia.registry.DeviceFileGID: 0 hw.nvidia.registry.DeviceFileUID: 0 hw.nvidia.registry.ModifyDeviceFiles: 1 hw.nvidia.registry.RmLogonRC: 1 hw.nvidia.registry.ResmanDebugLevel: 4294967295 hw.nvidia.registry.Mobile: 4294967295 hw.nvidia.version: NVIDIA UNIX x86_64 Kernel Module 367.18 Mon May 16 18:= 13:16 PDT 2016 dev.nvidia.0.%parent: vgapci0 dev.nvidia.0.%pnpinfo:=20 dev.nvidia.0.%location:=20 dev.nvidia.0.%driver: nvidia dev.nvidia.0.%desc: GeForce GTX 960 dev.nvidia.%parent:=20 Hopefully someone can give some hints what could trigger the problem ... Thanks in advance and please CC me (due to not subscribing this list). Kind regards, Oliver --Sig_/DDGh/V2d=dt6cZNf_U29rjq Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXUs8LAAoJEOgBcD7A/5N8zlEH/0zUYxjzLOBd8JuCUG58iuiW mT6bb+7wDnjUsEUwlxUJiB9nKb7AqyqCb7PdxrqYJWyJsdtrk1r1WbAHhAueehYY 3E/A6CkY/gsgLRifpMagwmpIHy31c2QLjEUX8iNf5na9QpsIxbPUlPL5jpKsdXl3 Mncbk1ODNvePqi2NgAmE06tomkG8dwJYwMejLj4avaaIqJsnd8tjACMqsGBH9MkU Nz2gvFZnwA/KzgFmgbSLfWaLw3Nj+5GHeSF/7oRfqDUorvFBi21SeAh0icdhmo91 +REnfFJpi+XpJexAxo9HGV0KFK65UpYPiFNWx/3LLNkGxCVnxEZMj+qtdZsizDY= =rNcL -----END PGP SIGNATURE----- --Sig_/DDGh/V2d=dt6cZNf_U29rjq--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160604145226.57dd078e.ohartman>