X won't start with Nvidia or Nouveau drivers on GTX 860M

As per the NixOS manual, I tried to enable the Nvidia driver using
services.xserver.videoDrivers = [ "nvidia" ];

After rebuilding and rebooting, X doesn't start. I tried to check the display manager service:
$ systemctl status display-manager
● display-manager.service - X11 Server
   Loaded: loaded (/nix/store/zacnf54ph45ghlgg5axiqizrc827q390-unit-display-manager.service/display-manager.service)
   Active: active (running) since Mon 2015-05-04 18:10:48 CEST; 1min 1s ago
  Process: 1626 ExecStartPre=/nix/store/m0nmfbpwcb5zf3r7qbmpjc486r43ksnn-unit-script/bin/display-manager-pre-start (code=exited, status=0/SUCCESS)
 Main PID: 1640 (gdm)
   CGroup: /system.slice/display-manager.service
           └─1640 /nix/store/1nnnvi056hkkiffz49yplgl5g2dyic1g-gdm-3.12.2/sbin/gdm

May 04 18:10:48 viktor.zareason.nixos gdm-Xorg-:5[1694]: (EE)
May 04 18:10:48 viktor.zareason.nixos gdm-Xorg-:5[1694]: Please consult the The X.Org Foundation support
May 04 18:10:48 viktor.zareason.nixos gdm-Xorg-:5[1694]: at http://wiki.x.org
May 04 18:10:48 viktor.zareason.nixos gdm-Xorg-:5[1694]: for help.
May 04 18:10:48 viktor.zareason.nixos gdm-Xorg-:5[1694]: (EE) Please also check the log file at "/var/log/X.0.log" for additional information.
May 04 18:10:48 viktor.zareason.nixos gdm-Xorg-:5[1694]: (EE)
May 04 18:10:48 viktor.zareason.nixos gdm-Xorg-:5[1694]: (EE) Server terminated with error (1). Closing log file.
May 04 18:10:48 viktor.zareason.nixos display-manager-start[1640]: Child process 1694 was already dead.
May 04 18:10:48 viktor.zareason.nixos display-manager-start[1640]: GdmDisplay: display lasted 0.042872 seconds
May 04 18:10:48 viktor.zareason.nixos display-manager-start[1640]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors

X.0.log:
[     5.011]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[     5.011] X Protocol Version 11, Revision 0
[     5.011] Build Operating System: Linux 3.12.27 x86_64
[     5.011] Current Operating System: Linux viktor.zareason.nixos 3.14.34 #1-NixOS SMP Thu Jan 1 00:00:01 UTC 1970 x86_64
[     5.011] Kernel command line: BOOT_IMAGE=(hd0,msdos4)/nix/store/2g0dz7iapq7fynpngqyr33pj09bkq9zk-linux-3.14.34/bzImage systemConfig=/nix/store/ikr7al2havs36hla1n0v7qg7sdn5g1n4-nixos-14.12.496.5f7d374 init=/nix/store/ikr7al2havs36hla1n0v7qg7sdn5g1n4-nixos-14.12.496.5f7d374/init loglevel=4
[     5.011] Build Date: 01 March 2015  04:27:12AM
[     5.011]
[     5.011] Current version of pixman: 0.32.6
[     5.011]    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[     5.011] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     5.011] (++) Log file: "/var/log/X.0.log", Time: Mon May  4 18:10:48 2015
[     5.012] (++) Using config file: "/nix/store/23p9nmyqay94895yyxq121v9287kvmzd-xserver.conf"
[     5.012] (==) Using system config directory "/nix/store/byfwj18c0vqv7z23grqjb4zdjkcdfwp5-xorg-server-1.16.4/share/X11/xorg.conf.d"
[     5.012] (==) ServerLayout "Layout[all]"
[     5.012] (**) |-->Screen "Screen-nvidia[0]" (0)
[     5.012] (**) |   |-->Monitor "<default monitor>"
[     5.012] (**) |   |-->Device "Device-nvidia[0]"
[     5.012] (==) No monitor specified for screen "Screen-nvidia[0]".
    Using a default monitor configuration.
[     5.012] (**) Option "AllowMouseOpenFail" "on"
[     5.012] (==) Automatically adding devices
[     5.012] (==) Automatically enabling devices
[     5.012] (==) Automatically adding GPU devices
[     5.012] (**) FontPath set to:
    /nix/store/3pbnv5fsknh53cfjwqb89n0s75ywmkny-font-bh-ttf-1.0.3/lib/X11/fonts/TTF,
    /nix/store/id3pjhddh4iy42yml928f54wr585s8mn-font-bh-lucidatypewriter-100dpi-1.0.3/lib/X11/fonts/100dpi,
    /nix/store/iycwkhsz5im0wjq9kb54yxig0049frm1-font-bh-lucidatypewriter-75dpi-1.0.3/lib/X11/fonts/75dpi,
    /nix/store/l8rcr4dnps5c4rjsdbsbn9a5znlw0hd9-font-bh-100dpi-1.0.3/lib/X11/fonts/100dpi,
    /nix/store/nwxwvz3z4qxb6ljaxrcbnphkxdl3cjh4-font-misc-misc-1.1.2/lib/X11/fonts/misc,
    /nix/store/9qfd5x9pbbjgnmrqwrhcwkjxw8b9k9ym-font-cursor-misc-1.0.3/lib/X11/fonts/misc,
    /nix/store/bq4i16p6jhzcm4i1pqarwzyjlxv9ma4v-font-adobe-100dpi-1.0.3/lib/X11/fonts/100dpi,
    /nix/store/rrnyihgrhwjxnasp6jaira12rmarwd7r-font-adobe-75dpi-1.0.3/lib/X11/fonts/75dpi
[     5.012] (**) ModulePath set to "/nix/store/3536xcs59rhrdkj6h286y9pxngv1xnf2-nvidia-x11-340.65-3.14.34/lib,/nix/store/3536xcs59rhrdkj6h286y9pxngv1xnf2-nvidia-x11-340.65-3.14.34/lib/xorg/modules,/nix/store/3536xcs59rhrdkj6h286y9pxngv1xnf2-nvidia-x11-340.65-3.14.34/lib/xorg/modules/drivers,/nix/store/3536xcs59rhrdkj6h286y9pxngv1xnf2-nvidia-x11-340.65-3.14.34/lib/xorg/modules/extensions,/nix/store/3536xcs59rhrdkj6h286y9pxngv1xnf2-nvidia-x11-340.65-3.14.34/lib/tls,/nix/store/byfwj18c0vqv7z23grqjb4zdjkcdfwp5-xorg-server-1.16.4/lib/xorg/modules,/nix/store/byfwj18c0vqv7z23grqjb4zdjkcdfwp5-xorg-server-1.16.4/lib/xorg/modules/extensions,/nix/store/byfwj18c0vqv7z23grqjb4zdjkcdfwp5-xorg-server-1.16.4/lib/xorg/modules/multimedia,/nix/store/g1awh0crnm8770ydfp17g22vpr26n4v4-xf86-input-evdev-2.9.1/lib/xorg/modules/input,/nix/store/hlw13bfcq7czs7h23m9ykkw87rypimb1-xf86-input-synaptics-1.8.1/lib/xorg/modules/input"
[     5.012] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
[     5.012] (II) Loader magic: 0x80d9c0
[     5.012] (II) Module ABI versions:
[     5.012]    X.Org ANSI C Emulation: 0.4
[     5.012]    X.Org Video Driver: 18.0
[     5.012]    X.Org XInput driver : 21.0
[     5.012]    X.Org Server Extension : 8.0
[     5.013] (EE) systemd-logind: failed to get session: PID 1694 does not belong to any known session
[     5.013] (II) xfree86: Adding drm device (/dev/dri/card1)
[     5.013] (II) xfree86: Adding drm device (/dev/dri/card0)
[     5.014] (--) PCI:*(0:0:2:0) 8086:0416:1558:2300 rev 6, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[     5.014] (--) PCI: (0:1:0:0) 10de:1392:1558:2300 rev 162, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[     5.014] (II) Open ACPI successful (/var/run/acpid.socket)
[     5.014] (II) "glx" will be loaded by default.
[     5.014] (II) LoadModule: "glx"
[     5.014] (II) Loading /nix/store/3536xcs59rhrdkj6h286y9pxngv1xnf2-nvidia-x11-340.65-3.14.34/lib/xorg/modules/extensions/libglx.so
[     5.022] (II) Module glx: vendor="NVIDIA Corporation"
[     5.022]    compiled for 4.0.2, module version = 1.0.0
[     5.022]    Module class: X.Org Server Extension
[     5.022] (II) NVIDIA GLX Module  340.65  Tue Dec  2 09:10:06 PST 2014
[     5.022] (II) LoadModule: "nvidia"
[     5.023] (II) Loading /nix/store/3536xcs59rhrdkj6h286y9pxngv1xnf2-nvidia-x11-340.65-3.14.34/lib/xorg/modules/drivers/nvidia_drv.so
[     5.023] (II) Module nvidia: vendor="NVIDIA Corporation"
[     5.023]    compiled for 4.0.2, module version = 1.0.0
[     5.023]    Module class: X.Org Video Driver
[     5.023] (II) NVIDIA dlloader X Driver  340.65  Tue Dec  2 08:47:36 PST 2014
[     5.023] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     5.023] (++) using VT number 7

[     5.028] (EE) No devices detected.
[     5.028] (EE)
Fatal server error:
[     5.028] (EE) no screens found(EE)
[     5.028] (EE)
Please consult the The X.Org Foundation support
     at http://wiki.x.org
 for help.
[     5.028] (EE) Please also check the log file at "/var/log/X.0.log" for additional information.
[     5.028] (EE)

I am guessing you are using a 'stable' release which still has 340.xx as the default nvidia driver, it doesn't have the newer short/long lived drivers (they need to be back ported).

OK, I will try one of the non-stable releases and report back...

No luck... I added the unstable channel and rebuilt, but got the same behavior and same error.

Actually... let me try one more time.

If it fails again can you provide a snippet of the X.0.log, if it updated to the unstable channel it should have 346.xx instead of 340.xx, in the paths in the log, e.g. Loading /nix/store/3536xcs59rhrdkj6h286y9pxngv1xnf2-nvidia-x11-340.65-3.14.34/...

try
dmesg |grep -i nvidia
to check whether kernel module of nvidia has been loaded

I ran into the same errors after doing a clean install of the NixOS 15.05pre61665.4c01e6d unstable channel.
X.0.log:
[     4.098]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[     4.098] X Protocol Version 11, Revision 0
[     4.098] Build Operating System: Linux 3.14.36 x86_64
[     4.098] Current Operating System: Linux viktor.nixos 3.18.12 #1-NixOS SMP Thu Jan 1 00:00:01 UTC 1970 x86_64
[     4.098] Kernel command line: BOOT_IMAGE=(hd0,msdos4)/nix/store/p7zird1zm9ldxdsgsfq41x9q1zp4svhi-linux-3.18.12/bzImage systemConfig=/nix/store/7ndc5lspx5jpk3axxhgpqkkl5dm0rjl4-nixos-15.05pre61665.4c01e6d init=/nix/store/7ndc5lspx5jpk3axxhgpqkkl5dm0rjl4-nixos-15.05pre61665.4c01e6d/init loglevel=4
[     4.098] Build Date: 24 April 2015  04:53:17AM
[     4.098]
[     4.098] Current version of pixman: 0.32.6
[     4.098] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     4.098] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     4.099] (++) Log file: "/var/log/X.0.log", Time: Tue May  5 10:05:56 2015
[     4.099] (++) Using config file: "/nix/store/rbsdvchyp31f0mzjx49586090n112p29-xserver.conf"
[     4.099] (==) Using system config directory "/nix/store/z06j0qa4z8klvy81fy9z22fmhycinfm4-xorg-server-1.16.4/share/X11/xorg.conf.d"
[     4.099] (==) ServerLayout "Layout[all]"
[     4.099] (**) |-->Screen "Screen-nvidia[0]" (0)
[     4.099] (**) |   |-->Monitor "<default monitor>"
[     4.099] (**) |   |-->Device "Device-nvidia[0]"
[     4.099] (==) No monitor specified for screen "Screen-nvidia[0]".
	Using a default monitor configuration.
[     4.099] (**) Option "AllowMouseOpenFail" "on"
[     4.099] (==) Automatically adding devices
[     4.099] (==) Automatically enabling devices
[     4.099] (==) Automatically adding GPU devices
[     4.099] (**) FontPath set to:
	/nix/store/lr2mapbgchdlrldlcgzmjnnrnwq7ijrp-font-bh-ttf-1.0.3/lib/X11/fonts/TTF,
	/nix/store/r4adxjkwq3g8gq06yl5w9jcc06m0z5sw-font-bh-lucidatypewriter-100dpi-1.0.3/lib/X11/fonts/100dpi,
	/nix/store/9vxdbarq2dx0b6mzfkwp5lwd01dgvv7z-font-bh-lucidatypewriter-75dpi-1.0.3/lib/X11/fonts/75dpi,
	/nix/store/if66sslh4yywfr3gph8d1nq7gqjbhpzd-font-bh-100dpi-1.0.3/lib/X11/fonts/100dpi,
	/nix/store/k3as755n0aq58dby56banjb6971bqnkw-font-misc-misc-1.1.2/lib/X11/fonts/misc,
	/nix/store/fm1v7ia144vcg6pqxh02v1qnv37lpbc7-font-cursor-misc-1.0.3/lib/X11/fonts/misc,
	/nix/store/dp51hcr529psw3bv2x7rypbx6fp6pxi3-font-adobe-100dpi-1.0.3/lib/X11/fonts/100dpi,
	/nix/store/cn6r677pjf5plcvr2igfq53vnwkbn8v6-font-adobe-75dpi-1.0.3/lib/X11/fonts/75dpi
[     4.099] (**) ModulePath set to "/nix/store/0smrdfnk2dvz1qmhbgdya8yff4izfhcn-nvidia-x11-346.59-3.18.12/lib,/nix/store/0smrdfnk2dvz1qmhbgdya8yff4izfhcn-nvidia-x11-346.59-3.18.12/lib/tls,/nix/store/0smrdfnk2dvz1qmhbgdya8yff4izfhcn-nvidia-x11-346.59-3.18.12/lib/xorg/modules,/nix/store/0smrdfnk2dvz1qmhbgdya8yff4izfhcn-nvidia-x11-346.59-3.18.12/lib/xorg/modules/extensions,/nix/store/0smrdfnk2dvz1qmhbgdya8yff4izfhcn-nvidia-x11-346.59-3.18.12/lib/xorg/modules/drivers,/nix/store/z06j0qa4z8klvy81fy9z22fmhycinfm4-xorg-server-1.16.4/lib/xorg/modules,/nix/store/z06j0qa4z8klvy81fy9z22fmhycinfm4-xorg-server-1.16.4/lib/xorg/modules/extensions,/nix/store/z06j0qa4z8klvy81fy9z22fmhycinfm4-xorg-server-1.16.4/lib/xorg/modules/multimedia,/nix/store/3d2fh17r0v8b773m8wlrhmx3wyg6vyyp-xf86-input-evdev-2.9.1/lib/xorg/modules/input,/nix/store/gkpqh1sqfizbf3v230df2xnkgissvij9-xf86-input-synaptics-1.8.1/lib/xorg/modules/input"
[     4.099] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     4.099] (II) Loader magic: 0x80d960
[     4.099] (II) Module ABI versions:
[     4.099] 	X.Org ANSI C Emulation: 0.4
[     4.099] 	X.Org Video Driver: 18.0
[     4.099] 	X.Org XInput driver : 21.0
[     4.099] 	X.Org Server Extension : 8.0
[     4.099] (EE) systemd-logind: failed to get session: PID 817 does not belong to any known session
[     4.100] (II) xfree86: Adding drm device (/dev/dri/card0)
[     4.100] (II) xfree86: Adding drm device (/dev/dri/card1)
[     4.100] (--) PCI:*(0:0:2:0) 8086:0416:1558:2300 rev 6, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[     4.100] (--) PCI: (0:1:0:0) 10de:1392:1558:2300 rev 162, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[     4.101] (II) Open ACPI successful (/var/run/acpid.socket)
[     4.101] (II) "glx" will be loaded by default.
[     4.101] (II) LoadModule: "glx"
[     4.101] (II) Loading /nix/store/0smrdfnk2dvz1qmhbgdya8yff4izfhcn-nvidia-x11-346.59-3.18.12/lib/xorg/modules/extensions/libglx.so
[     4.107] (II) Module glx: vendor="NVIDIA Corporation"
[     4.107] 	compiled for 4.0.2, module version = 1.0.0
[     4.107] 	Module class: X.Org Server Extension
[     4.107] (II) NVIDIA GLX Module  346.59  Tue Mar 31 13:38:58 PDT 2015
[     4.107] (II) LoadModule: "nvidia"
[     4.107] (II) Loading /nix/store/0smrdfnk2dvz1qmhbgdya8yff4izfhcn-nvidia-x11-346.59-3.18.12/lib/xorg/modules/drivers/nvidia_drv.so
[     4.107] (II) Module nvidia: vendor="NVIDIA Corporation"
[     4.107] 	compiled for 4.0.2, module version = 1.0.0
[     4.107] 	Module class: X.Org Video Driver
[     4.107] (II) NVIDIA dlloader X Driver  346.59  Tue Mar 31 13:17:41 PDT 2015
[     4.107] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     4.107] (++) using VT number 7

[     4.111] (EE) No devices detected.
[     4.111] (EE)
Fatal server error:
[     4.111] (EE) no screens found(EE)
[     4.111] (EE)
Please consult the The X.Org Foundation support
	 at http://wiki.x.org
 for help.
[     4.111] (EE) Please also check the log file at "/var/log/X.0.log" for additional information.
[     4.111] (EE)

dmesg | grep -i nvidia:
[    1.240985] nvidia: module license 'NVIDIA' taints kernel.
[    1.246329] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 0
[    1.246332] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  346.59  Tue Mar 31 14:10:31 PDT 2015
[    1.250605] nvidia_uvm: Loaded the UVM driver, major device number 251

It seems that server can not find the correct monitor device:
[     4.099] () |   |-->Device "Device-nvidia[0]"
[     4.099] (==) No monitor specified for screen "Screen-nvidia[0]".
Using a default monitor configuration.
[     4.099] () Option "AllowMouseOpenFail" "on"
....
[     4.111] (EE) No devices detected.
[     4.111] (EE)
Fatal server error:
[     4.111] (EE) no screens found(EE)
[     4.111] (EE)
Please consult the The X.Org Foundation support
you may need to add monitor specification in your screen section and add a monitor section. You may also need to specify your monitor parameters.

Is there any way to generate those parameters automatically?

Also, for what it's worth, I changed to services.xserver.videoDrivers = [ "nouveau" ]; and encountered the same error: (EE) No devices detected. ... (EE) no screens found.

I've been affected by this for a while as well with the same errors. I saw something about generating the config with nvidia-settings?

Maybe this is related to you having actually two usable GPUs – one in CPU and another discrete one. It might at least start X if you use videoDrivers = [ "intel" ]; instead.
I have no experience with that and I don't see any documentation even on our wiki. Maybe authors know: @coreyoconnor, @ktosiek.

Try running sudo lspci -v to see if your GPU is powered up, and if there's any kernel driver claiming it. If it's not powered up, you'll probably want to use bumblebee.
I don't have any nVidia GPUs around, so I can't check if the bumblebee stuff still works.

I have the same problem when enabling nvidia in the videoDrivers options...that being said..in hardware-configuration.nix autogenerated I have
  boot.initrd.availableKernelModules = [ "xhci_hcd" "ehci_pci" "ahci" "usbhid" "usb_storage" ];
  boot.kernelModules = [ "kvm-intel" ];

So I hope the nvidia part in the videoDrivers option adds nvidia to the kernel Modules...Also I'm using Bumblebee now, but can't run optirun because I get this error
$ optirun glxgears                                                            ~
[   52.610361] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) systemd-logind: failed to get session: PID 2061 does not belong to any known session

[   52.610388] [ERROR]Aborting because fallback start is disabled.

I'm in unstable channel and I tried it he stable channel too and on luck.

I'm having the same problems with at least the nvidia driver and this card:
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [NVS 5400M] (rev ff)

optirun works for me though as far as I can see.

I would also like to add that this issue has absolutely plagued me for over
5 years on linux using laptops :S
On Tue, Aug 25, 2015 at 1:10 PM, Robin Gloster<EMAIL_ADDRESS>wrote:

I'm having the same problems with at least the nvidia driver and this card:
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [NVS 5400M] (rev ff)
optirun works for me though as far as I can see.
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/7696#issuecomment-134689626.

Same issue here:
02:00.0 VGA compatible controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev a1)

This seemed to work for me:  services.xserver.videoDrivers = [ "nvidiaBeta" ];

@sjmackenzie
The beta driver is currently just and alias to the default driver.
https://github.com/NixOS/nixpkgs/blob/2ac4dba0fb4d82d526ece4d99937330b428ccbf5/pkgs/top-level/all-packages.nix#L10643

Well I cannot explain it:
this
services.xserver.videoDrivers = [ "nvidia" ];

results in a black screen for me.
this:
services.xserver.videoDrivers = [ "nvidiaBeta" ];

this works perfectly well, with smooth 3d support.

I have a gtx 660M. I spent all weekend trying to get it to work again
(something I've done many times). I belive the nvidiaBeta driver is 362. I
think support for our Optimus graphics cards doesn't really work until 364.
I plan on modifying the nix expression this afternoon to test my theory.
If anyone tests it first, please let me know if it works.
On Jun 20, 2016 2:00 AM, "Davy Duperron"<EMAIL_ADDRESS>wrote:

Hi,
I'm a newcomer in the NixOS world (and so far that's pretty amazing!) and
I'm also fighting against my laptop (Lenovo Z50) which has two CG (an
Nvidia discrete one and an Intel one on the CPU). I've enabled Bumblebee
and tried first with videoDrivers = [ "nvidia" ]; without success.
Switching to videoDrivers = [ "intel" ]; obviously solves the issue as
described previously but I want to find a way to get it working.
Is there any update on that topic? Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/7696#issuecomment-227064377, or mute
the thread
https://github.com/notifications/unsubscribe/AANyN0pstwEKTUq8_gmTn1G7qI09JVJ0ks5qNjqfgaJpZM4EPd01
.

As mentioned earlier, I switched to videoDrivers = [ "nvidiaBeta" ]; with success!

Same issue. Xorg doesn't start when services.xserver.videoDrivers = [ "nvidia" ]. "nvidiaBeta" does not work either. NVidia video card is "GT 630M". The laptop I'm trying this on has both NVidea and Intel video cards.  I'm trying to use make NVidia driver available for use with bumblebee and optirun. Perhaps, we are doing it wrong and this shouldn't be done though "services.xserver.videoDrivers"?

@DonManley here is my current configuration (with Bumblebee and Optirun perfectly running): https://github.com/yamafaktory/nixos-configuration/blob/master/configuration.nix#L33

@yamafaktory Holy Bajesus! That was a fast reply and everything works perfectly. Thanks!
So, the solution is to also add intel like services.xserver.videoDrivers = [ "intel" "nvidea" ].

Sorry to revive an ancient thread but I'm having exactly (?) the same problem on NixOS master, 17.09, and 17.03 at the moment. I'm using a Nvidia GTX 980 and it used to work on NixOS on this machine but has suddenly (?) stopped working - no signal on DVI port - and I'm seeing the same things in the logs (two PCI devices detected, no devices found, no screens found.)
I have tried twiddling the X drivers list with combinations of intel/nvidia/nvidiaBeta but it hasn't worked for me as it has for others. Help?

Miiight be related to #73804
Can you check the output of nvidia-smi?

ah indeed. some overlap
@mdedetrich says "It seems like unless you have intel nixos can't even detect any screens."
try adding the intel video driver? xserver.videoDrivers = [ "intel" "nvidia" ];

Yeah I had the same issue on my Thinkpad P1 Gen 2 laptop, I had to add "intel" to my videoDrivers section, the wiki has also been updated.

If any one comes across this, I was able to get mine working with videoDrivers = [ "modesetting" "nvidia" ]; instead of ["intel" "nvidia"]


How I Can Display PointCloud Map?

Hello,
I Want Use This Tool Display PointCloud Map, But This Map has Too Many Point(~16M), So I Can Not Send This Map EveryTime: For Example The PointCloud Map Like This:

Hello,
I Want Use This Tool Display PointCloud Map, But This Map has Too Many Point(~16M), So I Can Not Send This Map EveryTime: For Example The PointCloud Map Like This:

Hello, Have you solved this problem yet？

Hello,
I Want Use This Tool Display PointCloud Map, But This Map has Too Many Point(~16M), So I Can Not Send This Map EveryTime: For Example The PointCloud Map Like This:

Hello, Have you solved this problem yet？

no, because the web side not buffer this map, if you not send everytime, then this map will not display


pathchk: move from getopts to clap

Code is in:
https://github.com/uutils/coreutils/blob/master/src/uu/pathchk/src/pathchk.rs
Tests:
https://github.com/uutils/coreutils/blob/master/tests/by-util/test_pathchk.rs
As example:
https://github.com/uutils/coreutils/commit/9081e120d6b866c94679d9e29c7bdb17ccccb4d0

Let me give it a shot.

@sylvestre How do I run the test? cargo test doesn't seem to run the above mentioned test.

@sivachandran probably cargo test --features feat_os_unix

Able to run the test with command cargo test --features feat_os_unix test_pathchk. Thanks!

Another one that can be closed @sylvestre. Thank you!


Use communications buckeet

The new bucket layout is:
bucket name: digitalmarketplace-{bucket_short_name}-{stage}-{environment}
path structure: {framework_slug}/{bucket_short_name}/{path}

Are old bucket config variables used anywhere else or can we remove them now from config and test_env/run_app scripts?

:+1:


Multiplication and division that produce non-integer values throw an Error

Simple example:
const example = { amount: 500, currency: 'USD' }

Dinero(example).divide(3) // Throws
Dinero(example).divide(2) // Returns valid Dinero object

Dinero(example).multiply(2.01) // Throws
Dinero(example).multiply(2) // Returns valid Dinero object

I assume there should be some intermediate rounding that should be happening, and I'd be happy to write a PR that adds some property-based tests and a rounding solution, but wanted a little bit of direction on precision here.

Hi @scotttrinh and thanks for offering to help. This issue was raised in #6 and the intermediate rounding was my first idea as well. A few things to consider:

This should happen in the multiply and divide methods, not as a Dinero object is being created.
The rounding mode to use. It feels like the least biased solution would be to use Banker's rounding.
A note should be added to the docs (for multiply and divide) so users expect rounding to happen when non-integers results are produced.

Please make sure to check contributing rules.

Are you cool with adding a property-based testing library like JSVerify to aiding in finding edge cases? I'll definitely add specific unit tests as well, but since problem can have some weird edge cases, seems like a good use of property-based tests. If you're unsure, I'll be happy to add them in the PR and we can discuss!

@scotttrinh I'm not familiar with property-based testing but from a few reads, it sounds interesting. It would need to be Jest-compatible though (or use Jest directly if it has property-based capabilities).
Let's give it a try in the PR and see!

Luckily, JSVerify is really easy to use with most testing platforms and seems to work like a charm with Jest! PR is incoming after writing some more test cases.

FWIW, chaining multiple #multiply/#divide operations starts to get kind of lossy since we're rounding each intermediate Dinero amount.
Perhaps we ought to suggest in the documentation that if an amount is going to be multiplied and divided a lot that you get the value first, do your multiplication and division and re-wrap the rounded amount?

@scotttrinh Rounding will always lead to losses, so that's to be expected. We could define public rounding rules in a separate module, use one by default following Banker's rounding, and provide the possibility for users to pick another via parameter.
Example:
multiply(multiplier, roundingMode = ROUND_HALF_UP) { ... }

We of course should still warn in the docs that losses may happen and that rounding modes are available for users to pick depending on their use cases.

The lossiness would be a little less if we only rounded the final result rather than each time, which is what I was referring to. Having said that aloud, rounding as you go is probably "more correct" from an accounting standpoint since you wouldn't perform some mix of floating point math and rounding in an accounting situation.
Interesting idea about allowing the user to specify the rounding function. I think that is similar to how decimal.js does it, too. Maybe we keep their rounding mode names and use their rounding function for compatibility? Or, we could hav a default but allow one to optionally provide a rounding function, similar to how Array.prototype#sort allows you to specify a sorting function?
I'm open to whatever direction suits your style/aesthetic. As a user, I'd be fine with either way.

@scotttrinh I agree, but that's more on the user to make that decision. Whether the user performs one or ten chained multiply, this isn't something we have any control over. The only thing we can do is ensure a new object is created with a valid set of parameters, and that it's a valid monetary representation.
Here's what would be my approach so far: create a round method in the calculator which would round a value to a precision and with a rounding mode (can be a string or a number, doesn't really matter). This would determine which algorithm to use (by default, rounding half values to the even closest integer).

@scotttrinh Just noticed your PR 👍 Will review when I get a chance.

:tada: This issue has been resolved in version 1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Error with nested classes

In nested class get incomplete reference to nested property:
The example:
public class Gatos
{
	public string name {get; set;}
	public Color colores {get; set;}

	public class Color
	{
		public string[] color {get; set;}
	}
}

Get this:
Gatos gatos = new Gatos() {
name = "",
colores = new Color(),
};

Instead this:
Gatos gatos = new Gatos(){
name="",
colores=new Gatos.Color(){
color=new string[]{}
}
};

Best regards!

Oh that is a special case that is not yet handled, if anyone's interested in implementing a solution let me know, or else I will look into it later on