What package is used in Fedora 29 to install xblacklight?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

0

I installed Fedora 29 and do not use the wayland Gnome. I use x11 with i3. However, when I went to use xblacklight to adjust my laptop backlight, the command was not found. I also tried using it as sudo and even searched for it with find and grep. I looked online and tried to find the package and could not.

share|improve this question

  • 3

    sudo dnf whatprovides xbacklight shows the fedora repo contains this.

    – JRFerguson
    Feb 25 at 12:24

0

I installed Fedora 29 and do not use the wayland Gnome. I use x11 with i3. However, when I went to use xblacklight to adjust my laptop backlight, the command was not found. I also tried using it as sudo and even searched for it with find and grep. I looked online and tried to find the package and could not.

share|improve this question

  • 3

    sudo dnf whatprovides xbacklight shows the fedora repo contains this.

    – JRFerguson
    Feb 25 at 12:24

0

0

0

I installed Fedora 29 and do not use the wayland Gnome. I use x11 with i3. However, when I went to use xblacklight to adjust my laptop backlight, the command was not found. I also tried using it as sudo and even searched for it with find and grep. I looked online and tried to find the package and could not.

share|improve this question

I installed Fedora 29 and do not use the wayland Gnome. I use x11 with i3. However, when I went to use xblacklight to adjust my laptop backlight, the command was not found. I also tried using it as sudo and even searched for it with find and grep. I looked online and tried to find the package and could not.

fedora xorg

share|improve this question

share|improve this question

share|improve this question

share|improve this question

asked Feb 25 at 12:18

aminamin

31

31

  • 3

    sudo dnf whatprovides xbacklight shows the fedora repo contains this.

    – JRFerguson
    Feb 25 at 12:24

  • 3

    sudo dnf whatprovides xbacklight shows the fedora repo contains this.

    – JRFerguson
    Feb 25 at 12:24

3

3

sudo dnf whatprovides xbacklight shows the fedora repo contains this.

– JRFerguson
Feb 25 at 12:24

sudo dnf whatprovides xbacklight shows the fedora repo contains this.

– JRFerguson
Feb 25 at 12:24

1 Answer
1

active

oldest

votes

0

It is xbacklight, if you had a typo. What does it says, when you type dnf install xbacklight?

share|improve this answer

  • That was it, I misspelled it

    – amin
    Feb 25 at 12:53

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: “”.split(” “),
id: “106”
};
initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

StackExchange.using(“externalEditor”, function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using(“snippets”, function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: ‘answer’,
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: “”,
imageUploader: {
brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
allowUrls: true
},
onDemand: true,
discardSelector: “.discard-answer”
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved
draft discarded

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f502866%2fwhat-package-is-used-in-fedora-29-to-install-xblacklight%23new-answer’, ‘question_page’);
}
);

Post as a guest

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

active

oldest

votes

active

oldest

votes

0

It is xbacklight, if you had a typo. What does it says, when you type dnf install xbacklight?

share|improve this answer

  • That was it, I misspelled it

    – amin
    Feb 25 at 12:53

0

It is xbacklight, if you had a typo. What does it says, when you type dnf install xbacklight?

share|improve this answer

  • That was it, I misspelled it

    – amin
    Feb 25 at 12:53

0

0

0

It is xbacklight, if you had a typo. What does it says, when you type dnf install xbacklight?

share|improve this answer

It is xbacklight, if you had a typo. What does it says, when you type dnf install xbacklight?

share|improve this answer

share|improve this answer

share|improve this answer

answered Feb 25 at 12:27

RussellBRussellB

286312

286312

  • That was it, I misspelled it

    – amin
    Feb 25 at 12:53

  • That was it, I misspelled it

    – amin
    Feb 25 at 12:53

That was it, I misspelled it

– amin
Feb 25 at 12:53

That was it, I misspelled it

– amin
Feb 25 at 12:53

draft saved
draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

  • Please be sure to answer the question. Provide details and share your research!

But avoid

  • Asking for help, clarification, or responding to other answers.
  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f502866%2fwhat-package-is-used-in-fedora-29-to-install-xblacklight%23new-answer’, ‘question_page’);
}
);

Post as a guest

Required, but never shown

Required, but never shown

Required, but never shown

Required, but never shown

Required, but never shown

Required, but never shown

Required, but never shown

Required, but never shown

Required, but never shown

Service ‘org.kde.konsole-1060’ does not exist

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

0

Every non-KDE terminal (everyone except Konsole), once started, gives me this error:

Service 'org.kde.konsole-[different number everytime]' does not exist.

The full error being:

Service 'org.kde.konsole-1371' does not exist.
xprop: -id requires an argument

usage:  xprop [-options ...] [[format [dformat]] atom] ...

 where options include:
    -grammar                       print out full grammar for command line
    -display host:dpy              the X server to contact
    -id id                         resource id of window to examine
    -name name                     name of window to examine
    -font name                     name of font to examine
    -remove propname               remove a property
    -set propname value            set a property to a given value
    -root                          examine the root window
    -len n                         display at most n bytes of any property
    -notype                        do not display the type field
    -fs filename                   where to look for formats for properties
    -frame                         don't ignore window manager frames
    -f propname format [dformat]   formats to use for property of given name
    -spy                           examine window properties forever
    -version                       print program version

This error shows up no matter what Desktop Environment I am using (currently not KDE), and no matter what terminal I am using (except, as said before, Konsole).

share|improve this question

    0

    Every non-KDE terminal (everyone except Konsole), once started, gives me this error:

    Service 'org.kde.konsole-[different number everytime]' does not exist.
    

    The full error being:

    Service 'org.kde.konsole-1371' does not exist.
    xprop: -id requires an argument
    
    usage:  xprop [-options ...] [[format [dformat]] atom] ...
    
     where options include:
        -grammar                       print out full grammar for command line
        -display host:dpy              the X server to contact
        -id id                         resource id of window to examine
        -name name                     name of window to examine
        -font name                     name of font to examine
        -remove propname               remove a property
        -set propname value            set a property to a given value
        -root                          examine the root window
        -len n                         display at most n bytes of any property
        -notype                        do not display the type field
        -fs filename                   where to look for formats for properties
        -frame                         don't ignore window manager frames
        -f propname format [dformat]   formats to use for property of given name
        -spy                           examine window properties forever
        -version                       print program version
    

    This error shows up no matter what Desktop Environment I am using (currently not KDE), and no matter what terminal I am using (except, as said before, Konsole).

    share|improve this question

      0

      0

      0

      Every non-KDE terminal (everyone except Konsole), once started, gives me this error:

      Service 'org.kde.konsole-[different number everytime]' does not exist.
      

      The full error being:

      Service 'org.kde.konsole-1371' does not exist.
      xprop: -id requires an argument
      
      usage:  xprop [-options ...] [[format [dformat]] atom] ...
      
       where options include:
          -grammar                       print out full grammar for command line
          -display host:dpy              the X server to contact
          -id id                         resource id of window to examine
          -name name                     name of window to examine
          -font name                     name of font to examine
          -remove propname               remove a property
          -set propname value            set a property to a given value
          -root                          examine the root window
          -len n                         display at most n bytes of any property
          -notype                        do not display the type field
          -fs filename                   where to look for formats for properties
          -frame                         don't ignore window manager frames
          -f propname format [dformat]   formats to use for property of given name
          -spy                           examine window properties forever
          -version                       print program version
      

      This error shows up no matter what Desktop Environment I am using (currently not KDE), and no matter what terminal I am using (except, as said before, Konsole).

      share|improve this question

      Every non-KDE terminal (everyone except Konsole), once started, gives me this error:

      Service 'org.kde.konsole-[different number everytime]' does not exist.
      

      The full error being:

      Service 'org.kde.konsole-1371' does not exist.
      xprop: -id requires an argument
      
      usage:  xprop [-options ...] [[format [dformat]] atom] ...
      
       where options include:
          -grammar                       print out full grammar for command line
          -display host:dpy              the X server to contact
          -id id                         resource id of window to examine
          -name name                     name of window to examine
          -font name                     name of font to examine
          -remove propname               remove a property
          -set propname value            set a property to a given value
          -root                          examine the root window
          -len n                         display at most n bytes of any property
          -notype                        do not display the type field
          -fs filename                   where to look for formats for properties
          -frame                         don't ignore window manager frames
          -f propname format [dformat]   formats to use for property of given name
          -spy                           examine window properties forever
          -version                       print program version
      

      This error shows up no matter what Desktop Environment I am using (currently not KDE), and no matter what terminal I am using (except, as said before, Konsole).

      terminal xorg kde desktop-environment konsole

      share|improve this question

      share|improve this question

      share|improve this question

      share|improve this question

      edited Feb 23 at 12:35

      fra-san

      1,8731520

      1,8731520

      asked Feb 23 at 11:57

      SamSam

      11

      11

          0

          active

          oldest

          votes

          Your Answer

          StackExchange.ready(function() {
          var channelOptions = {
          tags: “”.split(” “),
          id: “106”
          };
          initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

          StackExchange.using(“externalEditor”, function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using(“snippets”, function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: ‘answer’,
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: “”,
          imageUploader: {
          brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
          contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
          allowUrls: true
          },
          onDemand: true,
          discardSelector: “.discard-answer”
          ,immediatelyShowMarkdownHelp:true
          });

          }
          });

          draft saved
          draft discarded

          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f502504%2fservice-org-kde-konsole-1060-does-not-exist%23new-answer’, ‘question_page’);
          }
          );

          Post as a guest

          Required, but never shown

          0

          active

          oldest

          votes

          0

          active

          oldest

          votes

          active

          oldest

          votes

          active

          oldest

          votes

          draft saved
          draft discarded

          Thanks for contributing an answer to Unix & Linux Stack Exchange!

          • Please be sure to answer the question. Provide details and share your research!

          But avoid

          • Asking for help, clarification, or responding to other answers.
          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.

          draft saved

          draft discarded

          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f502504%2fservice-org-kde-konsole-1060-does-not-exist%23new-answer’, ‘question_page’);
          }
          );

          Post as a guest

          Required, but never shown

          Required, but never shown

          Required, but never shown

          Required, but never shown

          Required, but never shown

          Required, but never shown

          Required, but never shown

          Required, but never shown

          Required, but never shown

          xorg not working

          The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

          0

          Yesterday, my xorg was working but it was using integrated graphics. I tried to get nvidia working. Now, when I run startx, I get a screen on tty3 which shows the output of the last tty I was in. For example, I hit ctrl+alt+f1, type startx and am moved to tty3 where I get a black screen with a solid cursor. If I go back to tty0 I can see the output of startx which shows no errors (besides minor gtk css warning) and a blinking cursor. When I go back to tty3, I see the same thing with a solid cursor.

          Info:

          uname -a:

          Linux Hermes 4.8.7-1-ARCH #1 SMP PREEMPT Mon Nov 15 10:14:30 CET 2016 x86_64 GNU/Linux
          

          .xinitrc:

          if [ -d /etc/X11/xinit/xinitrc.d ] ; then
              for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
                  [ -x "$f" ] && . "$f"
              done
              unset f
          fi
          
          conky &
          exec startxfce4
          

          /var/log/Xorg.0.log:

          [  1743.684] 
          X.Org X Server 1.18.4
          Release Date: 2016-07-19
          [  1743.684] X Protocol Version 11, Revision 0
          [  1743.684] Build Operating System: Linux 4.5.4-1-ARCH x86_64 
          [  1743.684] Current Operating System: Linux Hermes 4.8.7-1-ARCH #1 SMP PREEMPT Thu Nov 10 17:22:48 CET 2016 x86_64
          [  1743.684] Kernel command line: vmlinuz-linux ro root=UUID=1d746b96-3184-49ac-a204-0f9deda59c87 pci=nomsi initrd=initramfs-linux.img
          [  1743.684] Build Date: 19 July 2016  05:54:24PM
          [  1743.684]  
          [  1743.684] Current version of pixman: 0.34.0
          [  1743.684]    Before reporting problems, check http://wiki.x.org
              to make sure that you have the latest version.
          [  1743.684] Markers: (--) probed, (**) from config file, (==) default setting,
              (++) from command line, (!!) notice, (II) informational,
              (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
          [  1743.684] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 15 10:24:19 2016
          [  1743.684] (==) Using config file: "/etc/X11/xorg.conf"
          [  1743.684] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
          [  1743.684] (==) ServerLayout "Layout0"
          [  1743.684] (**) |-->Screen "Screen0" (0)
          [  1743.684] (**) |   |-->Monitor "<default monitor>"
          [  1743.684] (==) No device specified for screen "Screen0".
              Using the first device section listed.
          [  1743.684] (**) |   |-->Device "DiscreteNvidia"
          [  1743.684] (==) No monitor specified for screen "Screen0".
              Using a default monitor configuration.
          [  1743.684] (**) |-->Input Device "Keyboard0"
          [  1743.684] (**) |-->Input Device "Mouse0"
          [  1743.684] (==) Automatically adding devices
          [  1743.684] (==) Automatically enabling devices
          [  1743.684] (==) Automatically adding GPU devices
          [  1743.684] (==) Max clients allowed: 256, resource mask: 0x1fffff
          [  1743.684] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
          [  1743.684]    Entry deleted from font path.
          [  1743.684] (==) FontPath set to:
              /usr/share/fonts/misc/,
              /usr/share/fonts/TTF/,
              /usr/share/fonts/OTF/,
              /usr/share/fonts/100dpi/,
              /usr/share/fonts/75dpi/
          [  1743.684] (==) ModulePath set to "/usr/lib/xorg/modules"
          [  1743.684] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
          [  1743.684] (WW) Disabling Keyboard0
          [  1743.684] (WW) Disabling Mouse0
          [  1743.684] (II) Loader magic: 0x821d40
          [  1743.684] (II) Module ABI versions:
          [  1743.684]    X.Org ANSI C Emulation: 0.4
          [  1743.684]    X.Org Video Driver: 20.0
          [  1743.684]    X.Org XInput driver : 22.1
          [  1743.684]    X.Org Server Extension : 9.0
          [  1743.685] (--) using VT number 7
          
          [  1743.685] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
          [  1743.686] (II) xfree86: Adding drm device (/dev/dri/card1)
          [  1743.686] (II) xfree86: Adding drm device (/dev/dri/card0)
          [  1743.704] (--) PCI:*(0:0:2:0) 8086:191b:1462:115a rev 6, Mem @ 0xdd000000/16777216, 0xb0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
          [  1743.704] (--) PCI: (0:1:0:0) 10de:139b:1462:115a rev 162, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
          [  1743.704] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
          [  1743.704] (II) LoadModule: "glx"
          [  1743.705] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
          [  1743.710] (II) Module glx: vendor="NVIDIA Corporation"
          [  1743.710]    compiled for 4.0.2, module version = 1.0.0
          [  1743.710]    Module class: X.Org Server Extension
          [  1743.710] (II) NVIDIA GLX Module  375.10  Fri Oct 14 10:01:22 PDT 2016
          [  1743.710] (II) LoadModule: "nvidia"
          [  1743.710] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
          [  1743.710] (II) Module nvidia: vendor="NVIDIA Corporation"
          [  1743.710]    compiled for 4.0.2, module version = 1.0.0
          [  1743.710]    Module class: X.Org Video Driver
          [  1743.710] (II) NVIDIA dlloader X Driver  375.10  Fri Oct 14 09:38:17 PDT 2016
          [  1743.710] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
          [  1743.739] (II) Loading sub module "fb"
          [  1743.739] (II) LoadModule: "fb"
          [  1743.739] (II) Loading /usr/lib/xorg/modules/libfb.so
          [  1743.739] (II) Module fb: vendor="X.Org Foundation"
          [  1743.739]    compiled for 1.18.4, module version = 1.0.0
          [  1743.739]    ABI class: X.Org ANSI C Emulation, version 0.4
          [  1743.739] (II) Loading sub module "wfb"
          [  1743.739] (II) LoadModule: "wfb"
          [  1743.739] (II) Loading /usr/lib/xorg/modules/libwfb.so
          [  1743.739] (II) Module wfb: vendor="X.Org Foundation"
          [  1743.739]    compiled for 1.18.4, module version = 1.0.0
          [  1743.739]    ABI class: X.Org ANSI C Emulation, version 0.4
          [  1743.739] (II) Loading sub module "ramdac"
          [  1743.739] (II) LoadModule: "ramdac"
          [  1743.739] (II) Module "ramdac" already built-in
          [  1743.740] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
          [  1743.740] (==) NVIDIA(0): RGB weight 888
          [  1743.740] (==) NVIDIA(0): Default visual is TrueColor
          [  1743.740] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
          [  1743.740] (**) NVIDIA(0): Enabling 2D acceleration
          [  1744.067] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 960M (GM107-A) at PCI:1:0:0 (GPU-0)
          [  1744.067] (--) NVIDIA(0): Memory: 2097152 kBytes
          [  1744.067] (--) NVIDIA(0): VideoBIOS: 82.07.94.00.0e
          [  1744.067] (II) NVIDIA(0): Detected PCI Express Link width: 16X
          [  1744.067] (II) NVIDIA(0): Validated MetaModes:
          [  1744.067] (II) NVIDIA(0):     "NULL"
          [  1744.067] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
          [  1744.067] (WW) NVIDIA(0): Unable to get display device for DPI computation.
          [  1744.067] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
          [  1744.067] (--) Depth 24 pixmap format is 32 bpp
          [  1744.068] (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
          [  1744.068] (II) NVIDIA:     access.
          [  1744.071] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
          [  1744.071] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
          [  1744.071] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
          [  1744.071] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
          [  1744.071] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
          [  1744.071] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
          [  1744.071] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
          [  1744.071] (II) NVIDIA(0):     Config Options in the README.
          [  1744.088] (II) NVIDIA(0): Built-in logo is bigger than the screen.
          [  1744.088] (II) NVIDIA(0): Setting mode "NULL"
          [  1744.092] (==) NVIDIA(0): Disabling shared memory pixmaps
          [  1744.092] (==) NVIDIA(0): Backing store enabled
          [  1744.092] (==) NVIDIA(0): Silken mouse enabled
          [  1744.093] (==) NVIDIA(0): DPMS enabled
          [  1744.093] (II) Loading sub module "dri2"
          [  1744.093] (II) LoadModule: "dri2"
          [  1744.093] (II) Module "dri2" already built-in
          [  1744.093] (II) NVIDIA(0): [DRI2] Setup complete
          [  1744.093] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
          [  1744.093] (--) RandR disabled
          [  1744.095] (II) Initializing extension GLX
          [  1744.095] (II) Indirect GLX disabled.
          [  1744.145] (II) config/udev: Adding input device Power Button (/dev/input/event4)
          [  1744.145] (**) Power Button: Applying InputClass "evdev keyboard catchall"
          [  1744.145] (**) Power Button: Applying InputClass "libinput keyboard catchall"
          [  1744.145] (II) LoadModule: "libinput"
          [  1744.145] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
          [  1744.146] (II) Module libinput: vendor="X.Org Foundation"
          [  1744.146]    compiled for 1.18.4, module version = 0.22.0
          [  1744.146]    Module class: X.Org XInput Driver
          [  1744.146]    ABI class: X.Org XInput driver, version 22.1
          [  1744.146] (II) Using input driver 'libinput' for 'Power Button'
          [  1744.146] (**) Power Button: always reports core events
          [  1744.146] (**) Option "Device" "/dev/input/event4"
          [  1744.146] (**) Option "_source" "server/udev"
          [  1744.146] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
          [  1744.146] (II) input device 'Power Button', /dev/input/event4 is a keyboard
          [  1744.163] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4"
          [  1744.163] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
          [  1744.163] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
          [  1744.163] (II) input device 'Power Button', /dev/input/event4 is a keyboard
          [  1744.163] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
          [  1744.163] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
          [  1744.163] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
          [  1744.163] (II) Using input driver 'libinput' for 'Video Bus'
          [  1744.163] (**) Video Bus: always reports core events
          [  1744.163] (**) Option "Device" "/dev/input/event7"
          [  1744.163] (**) Option "_source" "server/udev"
          [  1744.164] (II) input device 'Video Bus', /dev/input/event7 is tagged by udev as: Keyboard
          [  1744.164] (II) input device 'Video Bus', /dev/input/event7 is a keyboard
          [  1744.186] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9/event7"
          [  1744.186] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
          [  1744.187] (II) input device 'Video Bus', /dev/input/event7 is tagged by udev as: Keyboard
          [  1744.187] (II) input device 'Video Bus', /dev/input/event7 is a keyboard
          [  1744.187] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
          [  1744.187] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
          [  1744.187] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
          [  1744.187] (II) Using input driver 'libinput' for 'Video Bus'
          [  1744.187] (**) Video Bus: always reports core events
          [  1744.187] (**) Option "Device" "/dev/input/event8"
          [  1744.187] (**) Option "_source" "server/udev"
          [  1744.188] (II) input device 'Video Bus', /dev/input/event8 is tagged by udev as: Keyboard
          [  1744.188] (II) input device 'Video Bus', /dev/input/event8 is a keyboard
          [  1744.203] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input10/event8"
          [  1744.203] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
          [  1744.204] (II) input device 'Video Bus', /dev/input/event8 is tagged by udev as: Keyboard
          [  1744.204] (II) input device 'Video Bus', /dev/input/event8 is a keyboard
          [  1744.205] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
          [  1744.205] (II) No input driver specified, ignoring this device.
          [  1744.205] (II) This device may have been added with another device file.
          [  1744.205] (II) config/udev: Adding input device Power Button (/dev/input/event3)
          [  1744.205] (**) Power Button: Applying InputClass "evdev keyboard catchall"
          [  1744.205] (**) Power Button: Applying InputClass "libinput keyboard catchall"
          [  1744.205] (II) Using input driver 'libinput' for 'Power Button'
          [  1744.205] (**) Power Button: always reports core events
          [  1744.205] (**) Option "Device" "/dev/input/event3"
          [  1744.205] (**) Option "_source" "server/udev"
          [  1744.206] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
          [  1744.206] (II) input device 'Power Button', /dev/input/event3 is a keyboard
          [  1744.223] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4/event3"
          [  1744.223] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
          [  1744.224] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
          [  1744.224] (II) input device 'Power Button', /dev/input/event3 is a keyboard
          [  1744.224] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
          [  1744.225] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
          [  1744.225] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
          [  1744.225] (II) Using input driver 'libinput' for 'Sleep Button'
          [  1744.225] (**) Sleep Button: always reports core events
          [  1744.225] (**) Option "Device" "/dev/input/event2"
          [  1744.225] (**) Option "_source" "server/udev"
          [  1744.225] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
          [  1744.225] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
          [  1744.243] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3/event2"
          [  1744.243] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10)
          [  1744.244] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
          [  1744.244] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
          [  1744.246] (II) config/udev: Adding input device Logitech M325 (/dev/input/event9)
          [  1744.246] (**) Logitech M325: Applying InputClass "evdev pointer catchall"
          [  1744.246] (**) Logitech M325: Applying InputClass "libinput pointer catchall"
          [  1744.246] (II) Using input driver 'libinput' for 'Logitech M325'
          [  1744.246] (**) Logitech M325: always reports core events
          [  1744.246] (**) Option "Device" "/dev/input/event9"
          [  1744.246] (**) Option "_source" "server/udev"
          [  1744.246] (II) input device 'Logitech M325', /dev/input/event9 is tagged by udev as: Mouse
          [  1744.247] (II) Device 'Logitech M325' set to 600 DPI
          [  1744.247] (II) input device 'Logitech M325', /dev/input/event9 is a pointer caps
          [  1744.293] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.2/0003:046D:C52B.0004/0003:046D:400A.0005/input/input11/event9"
          [  1744.293] (II) XINPUT: Adding extended input device "Logitech M325" (type: MOUSE, id 11)
          [  1744.293] (**) Option "AccelerationScheme" "none"
          [  1744.293] (**) Logitech M325: (accel) selected scheme none/0
          [  1744.293] (**) Logitech M325: (accel) acceleration factor: 2.000
          [  1744.293] (**) Logitech M325: (accel) acceleration threshold: 4
          [  1744.294] (II) input device 'Logitech M325', /dev/input/event9 is tagged by udev as: Mouse
          [  1744.294] (II) Device 'Logitech M325' set to 600 DPI
          [  1744.294] (II) input device 'Logitech M325', /dev/input/event9 is a pointer caps
          [  1744.295] (II) config/udev: Adding input device Logitech M325 (/dev/input/mouse0)
          [  1744.295] (II) No input driver specified, ignoring this device.
          [  1744.295] (II) This device may have been added with another device file.
          [  1744.296] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
          [  1744.296] (II) No input driver specified, ignoring this device.
          [  1744.296] (II) This device may have been added with another device file.
          [  1744.296] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
          [  1744.296] (II) No input driver specified, ignoring this device.
          [  1744.296] (II) This device may have been added with another device file.
          [  1744.297] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event13)
          [  1744.297] (II) No input driver specified, ignoring this device.
          [  1744.297] (II) This device may have been added with another device file.
          [  1744.297] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event14)
          [  1744.297] (II) No input driver specified, ignoring this device.
          [  1744.297] (II) This device may have been added with another device file.
          [  1744.298] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event15)
          [  1744.298] (II) No input driver specified, ignoring this device.
          [  1744.298] (II) This device may have been added with another device file.
          [  1744.299] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
          [  1744.299] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
          [  1744.299] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
          [  1744.299] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
          [  1744.299] (**) AT Translated Set 2 keyboard: always reports core events
          [  1744.299] (**) Option "Device" "/dev/input/event0"
          [  1744.299] (**) Option "_source" "server/udev"
          [  1744.299] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
          [  1744.299] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
          [  1744.343] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
          [  1744.343] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
          [  1744.344] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
          [  1744.344] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
          [  1744.345] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event10)
          [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
          [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
          [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
          [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
          [  1744.345] (II) LoadModule: "synaptics"
          [  1744.345] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
          [  1744.345] (II) Module synaptics: vendor="X.Org Foundation"
          [  1744.345]    compiled for 1.18.3, module version = 1.8.99
          [  1744.345]    Module class: X.Org XInput Driver
          [  1744.345]    ABI class: X.Org XInput driver, version 22.1
          [  1744.345] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
          [  1744.345] (**) SynPS/2 Synaptics TouchPad: always reports core events
          [  1744.345] (**) Option "Device" "/dev/input/event10"
          [  1744.383] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
          [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5706 (res 44)
          [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4800 (res 65)
          [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
          [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
          [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
          [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
          [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
          [  1744.383] (**) SynPS/2 Synaptics TouchPad: always reports core events
          [  1744.423] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event10"
          [  1744.423] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
          [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
          [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
          [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.037
          [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
          [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
          [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
          [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
          [  1744.423] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
          [  1744.424] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
          [  1744.424] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
          [  1744.425] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
          [  1744.425] (II) No input driver specified, ignoring this device.
          [  1744.425] (II) This device may have been added with another device file.
          [  1744.426] (II) config/udev: Adding input device MSI WMI hotkeys (/dev/input/event6)
          [  1744.426] (**) MSI WMI hotkeys: Applying InputClass "evdev keyboard catchall"
          [  1744.426] (**) MSI WMI hotkeys: Applying InputClass "libinput keyboard catchall"
          [  1744.426] (II) Using input driver 'libinput' for 'MSI WMI hotkeys'
          [  1744.426] (**) MSI WMI hotkeys: always reports core events
          [  1744.426] (**) Option "Device" "/dev/input/event6"
          [  1744.426] (**) Option "_source" "server/udev"
          [  1744.426] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is tagged by udev as: Keyboard
          [  1744.426] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is a keyboard
          [  1744.443] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event6"
          [  1744.443] (II) XINPUT: Adding extended input device "MSI WMI hotkeys" (type: KEYBOARD, id 14)
          [  1744.444] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is tagged by udev as: Keyboard
          [  1744.444] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is a keyboard
          [  1744.708] (II) UnloadModule: "libinput"
          [  1744.708] (II) UnloadModule: "synaptics"
          [  1744.708] (II) UnloadModule: "libinput"
          [  1744.708] (II) UnloadModule: "libinput"
          [  1744.708] (II) UnloadModule: "libinput"
          [  1744.708] (II) UnloadModule: "libinput"
          [  1744.708] (II) UnloadModule: "libinput"
          [  1744.708] (II) UnloadModule: "libinput"
          [  1744.709] (II) UnloadModule: "libinput"
          [  1744.736] (II) NVIDIA(GPU-0): Deleting GPU-0
          [  1744.807] (II) Server terminated successfully (0). Closing log file.
          

          /etc/X11/xorg.conf:

          # nvidia-xconfig: X configuration file generated by nvidia-xconfig
          # nvidia-xconfig:  version 375.10  (buildmeister@swio-display-x86-rhel47-09)  Fri Oct 14 11:11:07 PDT 2016
          
          Section "ServerLayout"
              Identifier     "Layout0"
              Screen      0  "Screen0"
              InputDevice    "Keyboard0" "CoreKeyboard"
              InputDevice    "Mouse0" "CorePointer"
          EndSection
          
          #Section "Files"
          #EndSection
          
          Section "InputDevice"
              # generated from default
              Identifier     "Mouse0"
              Driver         "mouse"
              Option         "Protocol" "auto"
              Option         "Device" "/dev/psaux"
             Option         "Emulate3Buttons" "no"
              Option         "ZAxisMapping" "4 5"
          EndSection
          
          Section "InputDevice"
          # generated from default
              Identifier     "Keyboard0"
              Driver         "kbd"
          EndSection
          
          Section "Monitor"
              Identifier     "Monitor1"
          #    VendorName     "Unknown"
          #    ModelName      "Unknown"
          #    HorizSync       28.0 - 33.0
          #    VertRefresh     43.0 - 72.0
          #    Option         "DPMS"
          EndSection
          
          Section "Device"
              Identifier     "DiscreteNvidia"
              Driver         "nvidia"
              VendorName     "NVIDIA Corporation"
              BoardName      "GeForce GTX 960M"
              BusID      "PCI:1:0:0"
          EndSection
          
          Section "Screen"
              Identifier     "Screen0"
              Device         "Device0"
              Monitor        "Monitor0"
              DefaultDepth    24
              SubSection     "Display"
                 Depth       24
              EndSubSection
          EndSection
          

          share|improve this question

            0

            Yesterday, my xorg was working but it was using integrated graphics. I tried to get nvidia working. Now, when I run startx, I get a screen on tty3 which shows the output of the last tty I was in. For example, I hit ctrl+alt+f1, type startx and am moved to tty3 where I get a black screen with a solid cursor. If I go back to tty0 I can see the output of startx which shows no errors (besides minor gtk css warning) and a blinking cursor. When I go back to tty3, I see the same thing with a solid cursor.

            Info:

            uname -a:

            Linux Hermes 4.8.7-1-ARCH #1 SMP PREEMPT Mon Nov 15 10:14:30 CET 2016 x86_64 GNU/Linux
            

            .xinitrc:

            if [ -d /etc/X11/xinit/xinitrc.d ] ; then
                for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
                    [ -x "$f" ] && . "$f"
                done
                unset f
            fi
            
            conky &
            exec startxfce4
            

            /var/log/Xorg.0.log:

            [  1743.684] 
            X.Org X Server 1.18.4
            Release Date: 2016-07-19
            [  1743.684] X Protocol Version 11, Revision 0
            [  1743.684] Build Operating System: Linux 4.5.4-1-ARCH x86_64 
            [  1743.684] Current Operating System: Linux Hermes 4.8.7-1-ARCH #1 SMP PREEMPT Thu Nov 10 17:22:48 CET 2016 x86_64
            [  1743.684] Kernel command line: vmlinuz-linux ro root=UUID=1d746b96-3184-49ac-a204-0f9deda59c87 pci=nomsi initrd=initramfs-linux.img
            [  1743.684] Build Date: 19 July 2016  05:54:24PM
            [  1743.684]  
            [  1743.684] Current version of pixman: 0.34.0
            [  1743.684]    Before reporting problems, check http://wiki.x.org
                to make sure that you have the latest version.
            [  1743.684] Markers: (--) probed, (**) from config file, (==) default setting,
                (++) from command line, (!!) notice, (II) informational,
                (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
            [  1743.684] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 15 10:24:19 2016
            [  1743.684] (==) Using config file: "/etc/X11/xorg.conf"
            [  1743.684] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
            [  1743.684] (==) ServerLayout "Layout0"
            [  1743.684] (**) |-->Screen "Screen0" (0)
            [  1743.684] (**) |   |-->Monitor "<default monitor>"
            [  1743.684] (==) No device specified for screen "Screen0".
                Using the first device section listed.
            [  1743.684] (**) |   |-->Device "DiscreteNvidia"
            [  1743.684] (==) No monitor specified for screen "Screen0".
                Using a default monitor configuration.
            [  1743.684] (**) |-->Input Device "Keyboard0"
            [  1743.684] (**) |-->Input Device "Mouse0"
            [  1743.684] (==) Automatically adding devices
            [  1743.684] (==) Automatically enabling devices
            [  1743.684] (==) Automatically adding GPU devices
            [  1743.684] (==) Max clients allowed: 256, resource mask: 0x1fffff
            [  1743.684] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
            [  1743.684]    Entry deleted from font path.
            [  1743.684] (==) FontPath set to:
                /usr/share/fonts/misc/,
                /usr/share/fonts/TTF/,
                /usr/share/fonts/OTF/,
                /usr/share/fonts/100dpi/,
                /usr/share/fonts/75dpi/
            [  1743.684] (==) ModulePath set to "/usr/lib/xorg/modules"
            [  1743.684] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
            [  1743.684] (WW) Disabling Keyboard0
            [  1743.684] (WW) Disabling Mouse0
            [  1743.684] (II) Loader magic: 0x821d40
            [  1743.684] (II) Module ABI versions:
            [  1743.684]    X.Org ANSI C Emulation: 0.4
            [  1743.684]    X.Org Video Driver: 20.0
            [  1743.684]    X.Org XInput driver : 22.1
            [  1743.684]    X.Org Server Extension : 9.0
            [  1743.685] (--) using VT number 7
            
            [  1743.685] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
            [  1743.686] (II) xfree86: Adding drm device (/dev/dri/card1)
            [  1743.686] (II) xfree86: Adding drm device (/dev/dri/card0)
            [  1743.704] (--) PCI:*(0:0:2:0) 8086:191b:1462:115a rev 6, Mem @ 0xdd000000/16777216, 0xb0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
            [  1743.704] (--) PCI: (0:1:0:0) 10de:139b:1462:115a rev 162, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
            [  1743.704] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
            [  1743.704] (II) LoadModule: "glx"
            [  1743.705] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
            [  1743.710] (II) Module glx: vendor="NVIDIA Corporation"
            [  1743.710]    compiled for 4.0.2, module version = 1.0.0
            [  1743.710]    Module class: X.Org Server Extension
            [  1743.710] (II) NVIDIA GLX Module  375.10  Fri Oct 14 10:01:22 PDT 2016
            [  1743.710] (II) LoadModule: "nvidia"
            [  1743.710] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
            [  1743.710] (II) Module nvidia: vendor="NVIDIA Corporation"
            [  1743.710]    compiled for 4.0.2, module version = 1.0.0
            [  1743.710]    Module class: X.Org Video Driver
            [  1743.710] (II) NVIDIA dlloader X Driver  375.10  Fri Oct 14 09:38:17 PDT 2016
            [  1743.710] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
            [  1743.739] (II) Loading sub module "fb"
            [  1743.739] (II) LoadModule: "fb"
            [  1743.739] (II) Loading /usr/lib/xorg/modules/libfb.so
            [  1743.739] (II) Module fb: vendor="X.Org Foundation"
            [  1743.739]    compiled for 1.18.4, module version = 1.0.0
            [  1743.739]    ABI class: X.Org ANSI C Emulation, version 0.4
            [  1743.739] (II) Loading sub module "wfb"
            [  1743.739] (II) LoadModule: "wfb"
            [  1743.739] (II) Loading /usr/lib/xorg/modules/libwfb.so
            [  1743.739] (II) Module wfb: vendor="X.Org Foundation"
            [  1743.739]    compiled for 1.18.4, module version = 1.0.0
            [  1743.739]    ABI class: X.Org ANSI C Emulation, version 0.4
            [  1743.739] (II) Loading sub module "ramdac"
            [  1743.739] (II) LoadModule: "ramdac"
            [  1743.739] (II) Module "ramdac" already built-in
            [  1743.740] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
            [  1743.740] (==) NVIDIA(0): RGB weight 888
            [  1743.740] (==) NVIDIA(0): Default visual is TrueColor
            [  1743.740] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
            [  1743.740] (**) NVIDIA(0): Enabling 2D acceleration
            [  1744.067] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 960M (GM107-A) at PCI:1:0:0 (GPU-0)
            [  1744.067] (--) NVIDIA(0): Memory: 2097152 kBytes
            [  1744.067] (--) NVIDIA(0): VideoBIOS: 82.07.94.00.0e
            [  1744.067] (II) NVIDIA(0): Detected PCI Express Link width: 16X
            [  1744.067] (II) NVIDIA(0): Validated MetaModes:
            [  1744.067] (II) NVIDIA(0):     "NULL"
            [  1744.067] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
            [  1744.067] (WW) NVIDIA(0): Unable to get display device for DPI computation.
            [  1744.067] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
            [  1744.067] (--) Depth 24 pixmap format is 32 bpp
            [  1744.068] (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
            [  1744.068] (II) NVIDIA:     access.
            [  1744.071] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
            [  1744.071] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
            [  1744.071] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
            [  1744.071] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
            [  1744.071] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
            [  1744.071] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
            [  1744.071] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
            [  1744.071] (II) NVIDIA(0):     Config Options in the README.
            [  1744.088] (II) NVIDIA(0): Built-in logo is bigger than the screen.
            [  1744.088] (II) NVIDIA(0): Setting mode "NULL"
            [  1744.092] (==) NVIDIA(0): Disabling shared memory pixmaps
            [  1744.092] (==) NVIDIA(0): Backing store enabled
            [  1744.092] (==) NVIDIA(0): Silken mouse enabled
            [  1744.093] (==) NVIDIA(0): DPMS enabled
            [  1744.093] (II) Loading sub module "dri2"
            [  1744.093] (II) LoadModule: "dri2"
            [  1744.093] (II) Module "dri2" already built-in
            [  1744.093] (II) NVIDIA(0): [DRI2] Setup complete
            [  1744.093] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
            [  1744.093] (--) RandR disabled
            [  1744.095] (II) Initializing extension GLX
            [  1744.095] (II) Indirect GLX disabled.
            [  1744.145] (II) config/udev: Adding input device Power Button (/dev/input/event4)
            [  1744.145] (**) Power Button: Applying InputClass "evdev keyboard catchall"
            [  1744.145] (**) Power Button: Applying InputClass "libinput keyboard catchall"
            [  1744.145] (II) LoadModule: "libinput"
            [  1744.145] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
            [  1744.146] (II) Module libinput: vendor="X.Org Foundation"
            [  1744.146]    compiled for 1.18.4, module version = 0.22.0
            [  1744.146]    Module class: X.Org XInput Driver
            [  1744.146]    ABI class: X.Org XInput driver, version 22.1
            [  1744.146] (II) Using input driver 'libinput' for 'Power Button'
            [  1744.146] (**) Power Button: always reports core events
            [  1744.146] (**) Option "Device" "/dev/input/event4"
            [  1744.146] (**) Option "_source" "server/udev"
            [  1744.146] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
            [  1744.146] (II) input device 'Power Button', /dev/input/event4 is a keyboard
            [  1744.163] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4"
            [  1744.163] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
            [  1744.163] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
            [  1744.163] (II) input device 'Power Button', /dev/input/event4 is a keyboard
            [  1744.163] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
            [  1744.163] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
            [  1744.163] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
            [  1744.163] (II) Using input driver 'libinput' for 'Video Bus'
            [  1744.163] (**) Video Bus: always reports core events
            [  1744.163] (**) Option "Device" "/dev/input/event7"
            [  1744.163] (**) Option "_source" "server/udev"
            [  1744.164] (II) input device 'Video Bus', /dev/input/event7 is tagged by udev as: Keyboard
            [  1744.164] (II) input device 'Video Bus', /dev/input/event7 is a keyboard
            [  1744.186] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9/event7"
            [  1744.186] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
            [  1744.187] (II) input device 'Video Bus', /dev/input/event7 is tagged by udev as: Keyboard
            [  1744.187] (II) input device 'Video Bus', /dev/input/event7 is a keyboard
            [  1744.187] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
            [  1744.187] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
            [  1744.187] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
            [  1744.187] (II) Using input driver 'libinput' for 'Video Bus'
            [  1744.187] (**) Video Bus: always reports core events
            [  1744.187] (**) Option "Device" "/dev/input/event8"
            [  1744.187] (**) Option "_source" "server/udev"
            [  1744.188] (II) input device 'Video Bus', /dev/input/event8 is tagged by udev as: Keyboard
            [  1744.188] (II) input device 'Video Bus', /dev/input/event8 is a keyboard
            [  1744.203] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input10/event8"
            [  1744.203] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
            [  1744.204] (II) input device 'Video Bus', /dev/input/event8 is tagged by udev as: Keyboard
            [  1744.204] (II) input device 'Video Bus', /dev/input/event8 is a keyboard
            [  1744.205] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
            [  1744.205] (II) No input driver specified, ignoring this device.
            [  1744.205] (II) This device may have been added with another device file.
            [  1744.205] (II) config/udev: Adding input device Power Button (/dev/input/event3)
            [  1744.205] (**) Power Button: Applying InputClass "evdev keyboard catchall"
            [  1744.205] (**) Power Button: Applying InputClass "libinput keyboard catchall"
            [  1744.205] (II) Using input driver 'libinput' for 'Power Button'
            [  1744.205] (**) Power Button: always reports core events
            [  1744.205] (**) Option "Device" "/dev/input/event3"
            [  1744.205] (**) Option "_source" "server/udev"
            [  1744.206] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
            [  1744.206] (II) input device 'Power Button', /dev/input/event3 is a keyboard
            [  1744.223] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4/event3"
            [  1744.223] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
            [  1744.224] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
            [  1744.224] (II) input device 'Power Button', /dev/input/event3 is a keyboard
            [  1744.224] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
            [  1744.225] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
            [  1744.225] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
            [  1744.225] (II) Using input driver 'libinput' for 'Sleep Button'
            [  1744.225] (**) Sleep Button: always reports core events
            [  1744.225] (**) Option "Device" "/dev/input/event2"
            [  1744.225] (**) Option "_source" "server/udev"
            [  1744.225] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
            [  1744.225] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
            [  1744.243] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3/event2"
            [  1744.243] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10)
            [  1744.244] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
            [  1744.244] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
            [  1744.246] (II) config/udev: Adding input device Logitech M325 (/dev/input/event9)
            [  1744.246] (**) Logitech M325: Applying InputClass "evdev pointer catchall"
            [  1744.246] (**) Logitech M325: Applying InputClass "libinput pointer catchall"
            [  1744.246] (II) Using input driver 'libinput' for 'Logitech M325'
            [  1744.246] (**) Logitech M325: always reports core events
            [  1744.246] (**) Option "Device" "/dev/input/event9"
            [  1744.246] (**) Option "_source" "server/udev"
            [  1744.246] (II) input device 'Logitech M325', /dev/input/event9 is tagged by udev as: Mouse
            [  1744.247] (II) Device 'Logitech M325' set to 600 DPI
            [  1744.247] (II) input device 'Logitech M325', /dev/input/event9 is a pointer caps
            [  1744.293] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.2/0003:046D:C52B.0004/0003:046D:400A.0005/input/input11/event9"
            [  1744.293] (II) XINPUT: Adding extended input device "Logitech M325" (type: MOUSE, id 11)
            [  1744.293] (**) Option "AccelerationScheme" "none"
            [  1744.293] (**) Logitech M325: (accel) selected scheme none/0
            [  1744.293] (**) Logitech M325: (accel) acceleration factor: 2.000
            [  1744.293] (**) Logitech M325: (accel) acceleration threshold: 4
            [  1744.294] (II) input device 'Logitech M325', /dev/input/event9 is tagged by udev as: Mouse
            [  1744.294] (II) Device 'Logitech M325' set to 600 DPI
            [  1744.294] (II) input device 'Logitech M325', /dev/input/event9 is a pointer caps
            [  1744.295] (II) config/udev: Adding input device Logitech M325 (/dev/input/mouse0)
            [  1744.295] (II) No input driver specified, ignoring this device.
            [  1744.295] (II) This device may have been added with another device file.
            [  1744.296] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
            [  1744.296] (II) No input driver specified, ignoring this device.
            [  1744.296] (II) This device may have been added with another device file.
            [  1744.296] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
            [  1744.296] (II) No input driver specified, ignoring this device.
            [  1744.296] (II) This device may have been added with another device file.
            [  1744.297] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event13)
            [  1744.297] (II) No input driver specified, ignoring this device.
            [  1744.297] (II) This device may have been added with another device file.
            [  1744.297] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event14)
            [  1744.297] (II) No input driver specified, ignoring this device.
            [  1744.297] (II) This device may have been added with another device file.
            [  1744.298] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event15)
            [  1744.298] (II) No input driver specified, ignoring this device.
            [  1744.298] (II) This device may have been added with another device file.
            [  1744.299] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
            [  1744.299] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
            [  1744.299] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
            [  1744.299] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
            [  1744.299] (**) AT Translated Set 2 keyboard: always reports core events
            [  1744.299] (**) Option "Device" "/dev/input/event0"
            [  1744.299] (**) Option "_source" "server/udev"
            [  1744.299] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
            [  1744.299] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
            [  1744.343] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
            [  1744.343] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
            [  1744.344] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
            [  1744.344] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
            [  1744.345] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event10)
            [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
            [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
            [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
            [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
            [  1744.345] (II) LoadModule: "synaptics"
            [  1744.345] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
            [  1744.345] (II) Module synaptics: vendor="X.Org Foundation"
            [  1744.345]    compiled for 1.18.3, module version = 1.8.99
            [  1744.345]    Module class: X.Org XInput Driver
            [  1744.345]    ABI class: X.Org XInput driver, version 22.1
            [  1744.345] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
            [  1744.345] (**) SynPS/2 Synaptics TouchPad: always reports core events
            [  1744.345] (**) Option "Device" "/dev/input/event10"
            [  1744.383] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
            [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5706 (res 44)
            [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4800 (res 65)
            [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
            [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
            [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
            [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
            [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
            [  1744.383] (**) SynPS/2 Synaptics TouchPad: always reports core events
            [  1744.423] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event10"
            [  1744.423] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
            [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
            [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
            [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.037
            [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
            [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
            [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
            [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
            [  1744.423] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
            [  1744.424] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
            [  1744.424] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
            [  1744.425] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
            [  1744.425] (II) No input driver specified, ignoring this device.
            [  1744.425] (II) This device may have been added with another device file.
            [  1744.426] (II) config/udev: Adding input device MSI WMI hotkeys (/dev/input/event6)
            [  1744.426] (**) MSI WMI hotkeys: Applying InputClass "evdev keyboard catchall"
            [  1744.426] (**) MSI WMI hotkeys: Applying InputClass "libinput keyboard catchall"
            [  1744.426] (II) Using input driver 'libinput' for 'MSI WMI hotkeys'
            [  1744.426] (**) MSI WMI hotkeys: always reports core events
            [  1744.426] (**) Option "Device" "/dev/input/event6"
            [  1744.426] (**) Option "_source" "server/udev"
            [  1744.426] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is tagged by udev as: Keyboard
            [  1744.426] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is a keyboard
            [  1744.443] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event6"
            [  1744.443] (II) XINPUT: Adding extended input device "MSI WMI hotkeys" (type: KEYBOARD, id 14)
            [  1744.444] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is tagged by udev as: Keyboard
            [  1744.444] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is a keyboard
            [  1744.708] (II) UnloadModule: "libinput"
            [  1744.708] (II) UnloadModule: "synaptics"
            [  1744.708] (II) UnloadModule: "libinput"
            [  1744.708] (II) UnloadModule: "libinput"
            [  1744.708] (II) UnloadModule: "libinput"
            [  1744.708] (II) UnloadModule: "libinput"
            [  1744.708] (II) UnloadModule: "libinput"
            [  1744.708] (II) UnloadModule: "libinput"
            [  1744.709] (II) UnloadModule: "libinput"
            [  1744.736] (II) NVIDIA(GPU-0): Deleting GPU-0
            [  1744.807] (II) Server terminated successfully (0). Closing log file.
            

            /etc/X11/xorg.conf:

            # nvidia-xconfig: X configuration file generated by nvidia-xconfig
            # nvidia-xconfig:  version 375.10  (buildmeister@swio-display-x86-rhel47-09)  Fri Oct 14 11:11:07 PDT 2016
            
            Section "ServerLayout"
                Identifier     "Layout0"
                Screen      0  "Screen0"
                InputDevice    "Keyboard0" "CoreKeyboard"
                InputDevice    "Mouse0" "CorePointer"
            EndSection
            
            #Section "Files"
            #EndSection
            
            Section "InputDevice"
                # generated from default
                Identifier     "Mouse0"
                Driver         "mouse"
                Option         "Protocol" "auto"
                Option         "Device" "/dev/psaux"
               Option         "Emulate3Buttons" "no"
                Option         "ZAxisMapping" "4 5"
            EndSection
            
            Section "InputDevice"
            # generated from default
                Identifier     "Keyboard0"
                Driver         "kbd"
            EndSection
            
            Section "Monitor"
                Identifier     "Monitor1"
            #    VendorName     "Unknown"
            #    ModelName      "Unknown"
            #    HorizSync       28.0 - 33.0
            #    VertRefresh     43.0 - 72.0
            #    Option         "DPMS"
            EndSection
            
            Section "Device"
                Identifier     "DiscreteNvidia"
                Driver         "nvidia"
                VendorName     "NVIDIA Corporation"
                BoardName      "GeForce GTX 960M"
                BusID      "PCI:1:0:0"
            EndSection
            
            Section "Screen"
                Identifier     "Screen0"
                Device         "Device0"
                Monitor        "Monitor0"
                DefaultDepth    24
                SubSection     "Display"
                   Depth       24
                EndSubSection
            EndSection
            

            share|improve this question

              0

              0

              0

              Yesterday, my xorg was working but it was using integrated graphics. I tried to get nvidia working. Now, when I run startx, I get a screen on tty3 which shows the output of the last tty I was in. For example, I hit ctrl+alt+f1, type startx and am moved to tty3 where I get a black screen with a solid cursor. If I go back to tty0 I can see the output of startx which shows no errors (besides minor gtk css warning) and a blinking cursor. When I go back to tty3, I see the same thing with a solid cursor.

              Info:

              uname -a:

              Linux Hermes 4.8.7-1-ARCH #1 SMP PREEMPT Mon Nov 15 10:14:30 CET 2016 x86_64 GNU/Linux
              

              .xinitrc:

              if [ -d /etc/X11/xinit/xinitrc.d ] ; then
                  for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
                      [ -x "$f" ] && . "$f"
                  done
                  unset f
              fi
              
              conky &
              exec startxfce4
              

              /var/log/Xorg.0.log:

              [  1743.684] 
              X.Org X Server 1.18.4
              Release Date: 2016-07-19
              [  1743.684] X Protocol Version 11, Revision 0
              [  1743.684] Build Operating System: Linux 4.5.4-1-ARCH x86_64 
              [  1743.684] Current Operating System: Linux Hermes 4.8.7-1-ARCH #1 SMP PREEMPT Thu Nov 10 17:22:48 CET 2016 x86_64
              [  1743.684] Kernel command line: vmlinuz-linux ro root=UUID=1d746b96-3184-49ac-a204-0f9deda59c87 pci=nomsi initrd=initramfs-linux.img
              [  1743.684] Build Date: 19 July 2016  05:54:24PM
              [  1743.684]  
              [  1743.684] Current version of pixman: 0.34.0
              [  1743.684]    Before reporting problems, check http://wiki.x.org
                  to make sure that you have the latest version.
              [  1743.684] Markers: (--) probed, (**) from config file, (==) default setting,
                  (++) from command line, (!!) notice, (II) informational,
                  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
              [  1743.684] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 15 10:24:19 2016
              [  1743.684] (==) Using config file: "/etc/X11/xorg.conf"
              [  1743.684] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
              [  1743.684] (==) ServerLayout "Layout0"
              [  1743.684] (**) |-->Screen "Screen0" (0)
              [  1743.684] (**) |   |-->Monitor "<default monitor>"
              [  1743.684] (==) No device specified for screen "Screen0".
                  Using the first device section listed.
              [  1743.684] (**) |   |-->Device "DiscreteNvidia"
              [  1743.684] (==) No monitor specified for screen "Screen0".
                  Using a default monitor configuration.
              [  1743.684] (**) |-->Input Device "Keyboard0"
              [  1743.684] (**) |-->Input Device "Mouse0"
              [  1743.684] (==) Automatically adding devices
              [  1743.684] (==) Automatically enabling devices
              [  1743.684] (==) Automatically adding GPU devices
              [  1743.684] (==) Max clients allowed: 256, resource mask: 0x1fffff
              [  1743.684] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
              [  1743.684]    Entry deleted from font path.
              [  1743.684] (==) FontPath set to:
                  /usr/share/fonts/misc/,
                  /usr/share/fonts/TTF/,
                  /usr/share/fonts/OTF/,
                  /usr/share/fonts/100dpi/,
                  /usr/share/fonts/75dpi/
              [  1743.684] (==) ModulePath set to "/usr/lib/xorg/modules"
              [  1743.684] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
              [  1743.684] (WW) Disabling Keyboard0
              [  1743.684] (WW) Disabling Mouse0
              [  1743.684] (II) Loader magic: 0x821d40
              [  1743.684] (II) Module ABI versions:
              [  1743.684]    X.Org ANSI C Emulation: 0.4
              [  1743.684]    X.Org Video Driver: 20.0
              [  1743.684]    X.Org XInput driver : 22.1
              [  1743.684]    X.Org Server Extension : 9.0
              [  1743.685] (--) using VT number 7
              
              [  1743.685] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
              [  1743.686] (II) xfree86: Adding drm device (/dev/dri/card1)
              [  1743.686] (II) xfree86: Adding drm device (/dev/dri/card0)
              [  1743.704] (--) PCI:*(0:0:2:0) 8086:191b:1462:115a rev 6, Mem @ 0xdd000000/16777216, 0xb0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
              [  1743.704] (--) PCI: (0:1:0:0) 10de:139b:1462:115a rev 162, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
              [  1743.704] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
              [  1743.704] (II) LoadModule: "glx"
              [  1743.705] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
              [  1743.710] (II) Module glx: vendor="NVIDIA Corporation"
              [  1743.710]    compiled for 4.0.2, module version = 1.0.0
              [  1743.710]    Module class: X.Org Server Extension
              [  1743.710] (II) NVIDIA GLX Module  375.10  Fri Oct 14 10:01:22 PDT 2016
              [  1743.710] (II) LoadModule: "nvidia"
              [  1743.710] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
              [  1743.710] (II) Module nvidia: vendor="NVIDIA Corporation"
              [  1743.710]    compiled for 4.0.2, module version = 1.0.0
              [  1743.710]    Module class: X.Org Video Driver
              [  1743.710] (II) NVIDIA dlloader X Driver  375.10  Fri Oct 14 09:38:17 PDT 2016
              [  1743.710] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
              [  1743.739] (II) Loading sub module "fb"
              [  1743.739] (II) LoadModule: "fb"
              [  1743.739] (II) Loading /usr/lib/xorg/modules/libfb.so
              [  1743.739] (II) Module fb: vendor="X.Org Foundation"
              [  1743.739]    compiled for 1.18.4, module version = 1.0.0
              [  1743.739]    ABI class: X.Org ANSI C Emulation, version 0.4
              [  1743.739] (II) Loading sub module "wfb"
              [  1743.739] (II) LoadModule: "wfb"
              [  1743.739] (II) Loading /usr/lib/xorg/modules/libwfb.so
              [  1743.739] (II) Module wfb: vendor="X.Org Foundation"
              [  1743.739]    compiled for 1.18.4, module version = 1.0.0
              [  1743.739]    ABI class: X.Org ANSI C Emulation, version 0.4
              [  1743.739] (II) Loading sub module "ramdac"
              [  1743.739] (II) LoadModule: "ramdac"
              [  1743.739] (II) Module "ramdac" already built-in
              [  1743.740] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
              [  1743.740] (==) NVIDIA(0): RGB weight 888
              [  1743.740] (==) NVIDIA(0): Default visual is TrueColor
              [  1743.740] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
              [  1743.740] (**) NVIDIA(0): Enabling 2D acceleration
              [  1744.067] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 960M (GM107-A) at PCI:1:0:0 (GPU-0)
              [  1744.067] (--) NVIDIA(0): Memory: 2097152 kBytes
              [  1744.067] (--) NVIDIA(0): VideoBIOS: 82.07.94.00.0e
              [  1744.067] (II) NVIDIA(0): Detected PCI Express Link width: 16X
              [  1744.067] (II) NVIDIA(0): Validated MetaModes:
              [  1744.067] (II) NVIDIA(0):     "NULL"
              [  1744.067] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
              [  1744.067] (WW) NVIDIA(0): Unable to get display device for DPI computation.
              [  1744.067] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
              [  1744.067] (--) Depth 24 pixmap format is 32 bpp
              [  1744.068] (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
              [  1744.068] (II) NVIDIA:     access.
              [  1744.071] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
              [  1744.071] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
              [  1744.071] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
              [  1744.071] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
              [  1744.071] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
              [  1744.071] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
              [  1744.071] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
              [  1744.071] (II) NVIDIA(0):     Config Options in the README.
              [  1744.088] (II) NVIDIA(0): Built-in logo is bigger than the screen.
              [  1744.088] (II) NVIDIA(0): Setting mode "NULL"
              [  1744.092] (==) NVIDIA(0): Disabling shared memory pixmaps
              [  1744.092] (==) NVIDIA(0): Backing store enabled
              [  1744.092] (==) NVIDIA(0): Silken mouse enabled
              [  1744.093] (==) NVIDIA(0): DPMS enabled
              [  1744.093] (II) Loading sub module "dri2"
              [  1744.093] (II) LoadModule: "dri2"
              [  1744.093] (II) Module "dri2" already built-in
              [  1744.093] (II) NVIDIA(0): [DRI2] Setup complete
              [  1744.093] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
              [  1744.093] (--) RandR disabled
              [  1744.095] (II) Initializing extension GLX
              [  1744.095] (II) Indirect GLX disabled.
              [  1744.145] (II) config/udev: Adding input device Power Button (/dev/input/event4)
              [  1744.145] (**) Power Button: Applying InputClass "evdev keyboard catchall"
              [  1744.145] (**) Power Button: Applying InputClass "libinput keyboard catchall"
              [  1744.145] (II) LoadModule: "libinput"
              [  1744.145] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
              [  1744.146] (II) Module libinput: vendor="X.Org Foundation"
              [  1744.146]    compiled for 1.18.4, module version = 0.22.0
              [  1744.146]    Module class: X.Org XInput Driver
              [  1744.146]    ABI class: X.Org XInput driver, version 22.1
              [  1744.146] (II) Using input driver 'libinput' for 'Power Button'
              [  1744.146] (**) Power Button: always reports core events
              [  1744.146] (**) Option "Device" "/dev/input/event4"
              [  1744.146] (**) Option "_source" "server/udev"
              [  1744.146] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
              [  1744.146] (II) input device 'Power Button', /dev/input/event4 is a keyboard
              [  1744.163] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4"
              [  1744.163] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
              [  1744.163] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
              [  1744.163] (II) input device 'Power Button', /dev/input/event4 is a keyboard
              [  1744.163] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
              [  1744.163] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
              [  1744.163] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
              [  1744.163] (II) Using input driver 'libinput' for 'Video Bus'
              [  1744.163] (**) Video Bus: always reports core events
              [  1744.163] (**) Option "Device" "/dev/input/event7"
              [  1744.163] (**) Option "_source" "server/udev"
              [  1744.164] (II) input device 'Video Bus', /dev/input/event7 is tagged by udev as: Keyboard
              [  1744.164] (II) input device 'Video Bus', /dev/input/event7 is a keyboard
              [  1744.186] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9/event7"
              [  1744.186] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
              [  1744.187] (II) input device 'Video Bus', /dev/input/event7 is tagged by udev as: Keyboard
              [  1744.187] (II) input device 'Video Bus', /dev/input/event7 is a keyboard
              [  1744.187] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
              [  1744.187] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
              [  1744.187] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
              [  1744.187] (II) Using input driver 'libinput' for 'Video Bus'
              [  1744.187] (**) Video Bus: always reports core events
              [  1744.187] (**) Option "Device" "/dev/input/event8"
              [  1744.187] (**) Option "_source" "server/udev"
              [  1744.188] (II) input device 'Video Bus', /dev/input/event8 is tagged by udev as: Keyboard
              [  1744.188] (II) input device 'Video Bus', /dev/input/event8 is a keyboard
              [  1744.203] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input10/event8"
              [  1744.203] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
              [  1744.204] (II) input device 'Video Bus', /dev/input/event8 is tagged by udev as: Keyboard
              [  1744.204] (II) input device 'Video Bus', /dev/input/event8 is a keyboard
              [  1744.205] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
              [  1744.205] (II) No input driver specified, ignoring this device.
              [  1744.205] (II) This device may have been added with another device file.
              [  1744.205] (II) config/udev: Adding input device Power Button (/dev/input/event3)
              [  1744.205] (**) Power Button: Applying InputClass "evdev keyboard catchall"
              [  1744.205] (**) Power Button: Applying InputClass "libinput keyboard catchall"
              [  1744.205] (II) Using input driver 'libinput' for 'Power Button'
              [  1744.205] (**) Power Button: always reports core events
              [  1744.205] (**) Option "Device" "/dev/input/event3"
              [  1744.205] (**) Option "_source" "server/udev"
              [  1744.206] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
              [  1744.206] (II) input device 'Power Button', /dev/input/event3 is a keyboard
              [  1744.223] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4/event3"
              [  1744.223] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
              [  1744.224] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
              [  1744.224] (II) input device 'Power Button', /dev/input/event3 is a keyboard
              [  1744.224] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
              [  1744.225] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
              [  1744.225] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
              [  1744.225] (II) Using input driver 'libinput' for 'Sleep Button'
              [  1744.225] (**) Sleep Button: always reports core events
              [  1744.225] (**) Option "Device" "/dev/input/event2"
              [  1744.225] (**) Option "_source" "server/udev"
              [  1744.225] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
              [  1744.225] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
              [  1744.243] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3/event2"
              [  1744.243] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10)
              [  1744.244] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
              [  1744.244] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
              [  1744.246] (II) config/udev: Adding input device Logitech M325 (/dev/input/event9)
              [  1744.246] (**) Logitech M325: Applying InputClass "evdev pointer catchall"
              [  1744.246] (**) Logitech M325: Applying InputClass "libinput pointer catchall"
              [  1744.246] (II) Using input driver 'libinput' for 'Logitech M325'
              [  1744.246] (**) Logitech M325: always reports core events
              [  1744.246] (**) Option "Device" "/dev/input/event9"
              [  1744.246] (**) Option "_source" "server/udev"
              [  1744.246] (II) input device 'Logitech M325', /dev/input/event9 is tagged by udev as: Mouse
              [  1744.247] (II) Device 'Logitech M325' set to 600 DPI
              [  1744.247] (II) input device 'Logitech M325', /dev/input/event9 is a pointer caps
              [  1744.293] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.2/0003:046D:C52B.0004/0003:046D:400A.0005/input/input11/event9"
              [  1744.293] (II) XINPUT: Adding extended input device "Logitech M325" (type: MOUSE, id 11)
              [  1744.293] (**) Option "AccelerationScheme" "none"
              [  1744.293] (**) Logitech M325: (accel) selected scheme none/0
              [  1744.293] (**) Logitech M325: (accel) acceleration factor: 2.000
              [  1744.293] (**) Logitech M325: (accel) acceleration threshold: 4
              [  1744.294] (II) input device 'Logitech M325', /dev/input/event9 is tagged by udev as: Mouse
              [  1744.294] (II) Device 'Logitech M325' set to 600 DPI
              [  1744.294] (II) input device 'Logitech M325', /dev/input/event9 is a pointer caps
              [  1744.295] (II) config/udev: Adding input device Logitech M325 (/dev/input/mouse0)
              [  1744.295] (II) No input driver specified, ignoring this device.
              [  1744.295] (II) This device may have been added with another device file.
              [  1744.296] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
              [  1744.296] (II) No input driver specified, ignoring this device.
              [  1744.296] (II) This device may have been added with another device file.
              [  1744.296] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
              [  1744.296] (II) No input driver specified, ignoring this device.
              [  1744.296] (II) This device may have been added with another device file.
              [  1744.297] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event13)
              [  1744.297] (II) No input driver specified, ignoring this device.
              [  1744.297] (II) This device may have been added with another device file.
              [  1744.297] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event14)
              [  1744.297] (II) No input driver specified, ignoring this device.
              [  1744.297] (II) This device may have been added with another device file.
              [  1744.298] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event15)
              [  1744.298] (II) No input driver specified, ignoring this device.
              [  1744.298] (II) This device may have been added with another device file.
              [  1744.299] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
              [  1744.299] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
              [  1744.299] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
              [  1744.299] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
              [  1744.299] (**) AT Translated Set 2 keyboard: always reports core events
              [  1744.299] (**) Option "Device" "/dev/input/event0"
              [  1744.299] (**) Option "_source" "server/udev"
              [  1744.299] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
              [  1744.299] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
              [  1744.343] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
              [  1744.343] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
              [  1744.344] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
              [  1744.344] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
              [  1744.345] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event10)
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
              [  1744.345] (II) LoadModule: "synaptics"
              [  1744.345] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
              [  1744.345] (II) Module synaptics: vendor="X.Org Foundation"
              [  1744.345]    compiled for 1.18.3, module version = 1.8.99
              [  1744.345]    Module class: X.Org XInput Driver
              [  1744.345]    ABI class: X.Org XInput driver, version 22.1
              [  1744.345] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: always reports core events
              [  1744.345] (**) Option "Device" "/dev/input/event10"
              [  1744.383] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5706 (res 44)
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4800 (res 65)
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
              [  1744.383] (**) SynPS/2 Synaptics TouchPad: always reports core events
              [  1744.423] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event10"
              [  1744.423] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
              [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
              [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
              [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.037
              [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
              [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
              [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
              [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
              [  1744.423] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
              [  1744.424] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
              [  1744.424] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
              [  1744.425] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
              [  1744.425] (II) No input driver specified, ignoring this device.
              [  1744.425] (II) This device may have been added with another device file.
              [  1744.426] (II) config/udev: Adding input device MSI WMI hotkeys (/dev/input/event6)
              [  1744.426] (**) MSI WMI hotkeys: Applying InputClass "evdev keyboard catchall"
              [  1744.426] (**) MSI WMI hotkeys: Applying InputClass "libinput keyboard catchall"
              [  1744.426] (II) Using input driver 'libinput' for 'MSI WMI hotkeys'
              [  1744.426] (**) MSI WMI hotkeys: always reports core events
              [  1744.426] (**) Option "Device" "/dev/input/event6"
              [  1744.426] (**) Option "_source" "server/udev"
              [  1744.426] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is tagged by udev as: Keyboard
              [  1744.426] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is a keyboard
              [  1744.443] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event6"
              [  1744.443] (II) XINPUT: Adding extended input device "MSI WMI hotkeys" (type: KEYBOARD, id 14)
              [  1744.444] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is tagged by udev as: Keyboard
              [  1744.444] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is a keyboard
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "synaptics"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.709] (II) UnloadModule: "libinput"
              [  1744.736] (II) NVIDIA(GPU-0): Deleting GPU-0
              [  1744.807] (II) Server terminated successfully (0). Closing log file.
              

              /etc/X11/xorg.conf:

              # nvidia-xconfig: X configuration file generated by nvidia-xconfig
              # nvidia-xconfig:  version 375.10  (buildmeister@swio-display-x86-rhel47-09)  Fri Oct 14 11:11:07 PDT 2016
              
              Section "ServerLayout"
                  Identifier     "Layout0"
                  Screen      0  "Screen0"
                  InputDevice    "Keyboard0" "CoreKeyboard"
                  InputDevice    "Mouse0" "CorePointer"
              EndSection
              
              #Section "Files"
              #EndSection
              
              Section "InputDevice"
                  # generated from default
                  Identifier     "Mouse0"
                  Driver         "mouse"
                  Option         "Protocol" "auto"
                  Option         "Device" "/dev/psaux"
                 Option         "Emulate3Buttons" "no"
                  Option         "ZAxisMapping" "4 5"
              EndSection
              
              Section "InputDevice"
              # generated from default
                  Identifier     "Keyboard0"
                  Driver         "kbd"
              EndSection
              
              Section "Monitor"
                  Identifier     "Monitor1"
              #    VendorName     "Unknown"
              #    ModelName      "Unknown"
              #    HorizSync       28.0 - 33.0
              #    VertRefresh     43.0 - 72.0
              #    Option         "DPMS"
              EndSection
              
              Section "Device"
                  Identifier     "DiscreteNvidia"
                  Driver         "nvidia"
                  VendorName     "NVIDIA Corporation"
                  BoardName      "GeForce GTX 960M"
                  BusID      "PCI:1:0:0"
              EndSection
              
              Section "Screen"
                  Identifier     "Screen0"
                  Device         "Device0"
                  Monitor        "Monitor0"
                  DefaultDepth    24
                  SubSection     "Display"
                     Depth       24
                  EndSubSection
              EndSection
              

              share|improve this question

              Yesterday, my xorg was working but it was using integrated graphics. I tried to get nvidia working. Now, when I run startx, I get a screen on tty3 which shows the output of the last tty I was in. For example, I hit ctrl+alt+f1, type startx and am moved to tty3 where I get a black screen with a solid cursor. If I go back to tty0 I can see the output of startx which shows no errors (besides minor gtk css warning) and a blinking cursor. When I go back to tty3, I see the same thing with a solid cursor.

              Info:

              uname -a:

              Linux Hermes 4.8.7-1-ARCH #1 SMP PREEMPT Mon Nov 15 10:14:30 CET 2016 x86_64 GNU/Linux
              

              .xinitrc:

              if [ -d /etc/X11/xinit/xinitrc.d ] ; then
                  for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
                      [ -x "$f" ] && . "$f"
                  done
                  unset f
              fi
              
              conky &
              exec startxfce4
              

              /var/log/Xorg.0.log:

              [  1743.684] 
              X.Org X Server 1.18.4
              Release Date: 2016-07-19
              [  1743.684] X Protocol Version 11, Revision 0
              [  1743.684] Build Operating System: Linux 4.5.4-1-ARCH x86_64 
              [  1743.684] Current Operating System: Linux Hermes 4.8.7-1-ARCH #1 SMP PREEMPT Thu Nov 10 17:22:48 CET 2016 x86_64
              [  1743.684] Kernel command line: vmlinuz-linux ro root=UUID=1d746b96-3184-49ac-a204-0f9deda59c87 pci=nomsi initrd=initramfs-linux.img
              [  1743.684] Build Date: 19 July 2016  05:54:24PM
              [  1743.684]  
              [  1743.684] Current version of pixman: 0.34.0
              [  1743.684]    Before reporting problems, check http://wiki.x.org
                  to make sure that you have the latest version.
              [  1743.684] Markers: (--) probed, (**) from config file, (==) default setting,
                  (++) from command line, (!!) notice, (II) informational,
                  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
              [  1743.684] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 15 10:24:19 2016
              [  1743.684] (==) Using config file: "/etc/X11/xorg.conf"
              [  1743.684] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
              [  1743.684] (==) ServerLayout "Layout0"
              [  1743.684] (**) |-->Screen "Screen0" (0)
              [  1743.684] (**) |   |-->Monitor "<default monitor>"
              [  1743.684] (==) No device specified for screen "Screen0".
                  Using the first device section listed.
              [  1743.684] (**) |   |-->Device "DiscreteNvidia"
              [  1743.684] (==) No monitor specified for screen "Screen0".
                  Using a default monitor configuration.
              [  1743.684] (**) |-->Input Device "Keyboard0"
              [  1743.684] (**) |-->Input Device "Mouse0"
              [  1743.684] (==) Automatically adding devices
              [  1743.684] (==) Automatically enabling devices
              [  1743.684] (==) Automatically adding GPU devices
              [  1743.684] (==) Max clients allowed: 256, resource mask: 0x1fffff
              [  1743.684] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
              [  1743.684]    Entry deleted from font path.
              [  1743.684] (==) FontPath set to:
                  /usr/share/fonts/misc/,
                  /usr/share/fonts/TTF/,
                  /usr/share/fonts/OTF/,
                  /usr/share/fonts/100dpi/,
                  /usr/share/fonts/75dpi/
              [  1743.684] (==) ModulePath set to "/usr/lib/xorg/modules"
              [  1743.684] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
              [  1743.684] (WW) Disabling Keyboard0
              [  1743.684] (WW) Disabling Mouse0
              [  1743.684] (II) Loader magic: 0x821d40
              [  1743.684] (II) Module ABI versions:
              [  1743.684]    X.Org ANSI C Emulation: 0.4
              [  1743.684]    X.Org Video Driver: 20.0
              [  1743.684]    X.Org XInput driver : 22.1
              [  1743.684]    X.Org Server Extension : 9.0
              [  1743.685] (--) using VT number 7
              
              [  1743.685] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
              [  1743.686] (II) xfree86: Adding drm device (/dev/dri/card1)
              [  1743.686] (II) xfree86: Adding drm device (/dev/dri/card0)
              [  1743.704] (--) PCI:*(0:0:2:0) 8086:191b:1462:115a rev 6, Mem @ 0xdd000000/16777216, 0xb0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
              [  1743.704] (--) PCI: (0:1:0:0) 10de:139b:1462:115a rev 162, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
              [  1743.704] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
              [  1743.704] (II) LoadModule: "glx"
              [  1743.705] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
              [  1743.710] (II) Module glx: vendor="NVIDIA Corporation"
              [  1743.710]    compiled for 4.0.2, module version = 1.0.0
              [  1743.710]    Module class: X.Org Server Extension
              [  1743.710] (II) NVIDIA GLX Module  375.10  Fri Oct 14 10:01:22 PDT 2016
              [  1743.710] (II) LoadModule: "nvidia"
              [  1743.710] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
              [  1743.710] (II) Module nvidia: vendor="NVIDIA Corporation"
              [  1743.710]    compiled for 4.0.2, module version = 1.0.0
              [  1743.710]    Module class: X.Org Video Driver
              [  1743.710] (II) NVIDIA dlloader X Driver  375.10  Fri Oct 14 09:38:17 PDT 2016
              [  1743.710] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
              [  1743.739] (II) Loading sub module "fb"
              [  1743.739] (II) LoadModule: "fb"
              [  1743.739] (II) Loading /usr/lib/xorg/modules/libfb.so
              [  1743.739] (II) Module fb: vendor="X.Org Foundation"
              [  1743.739]    compiled for 1.18.4, module version = 1.0.0
              [  1743.739]    ABI class: X.Org ANSI C Emulation, version 0.4
              [  1743.739] (II) Loading sub module "wfb"
              [  1743.739] (II) LoadModule: "wfb"
              [  1743.739] (II) Loading /usr/lib/xorg/modules/libwfb.so
              [  1743.739] (II) Module wfb: vendor="X.Org Foundation"
              [  1743.739]    compiled for 1.18.4, module version = 1.0.0
              [  1743.739]    ABI class: X.Org ANSI C Emulation, version 0.4
              [  1743.739] (II) Loading sub module "ramdac"
              [  1743.739] (II) LoadModule: "ramdac"
              [  1743.739] (II) Module "ramdac" already built-in
              [  1743.740] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
              [  1743.740] (==) NVIDIA(0): RGB weight 888
              [  1743.740] (==) NVIDIA(0): Default visual is TrueColor
              [  1743.740] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
              [  1743.740] (**) NVIDIA(0): Enabling 2D acceleration
              [  1744.067] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 960M (GM107-A) at PCI:1:0:0 (GPU-0)
              [  1744.067] (--) NVIDIA(0): Memory: 2097152 kBytes
              [  1744.067] (--) NVIDIA(0): VideoBIOS: 82.07.94.00.0e
              [  1744.067] (II) NVIDIA(0): Detected PCI Express Link width: 16X
              [  1744.067] (II) NVIDIA(0): Validated MetaModes:
              [  1744.067] (II) NVIDIA(0):     "NULL"
              [  1744.067] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
              [  1744.067] (WW) NVIDIA(0): Unable to get display device for DPI computation.
              [  1744.067] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
              [  1744.067] (--) Depth 24 pixmap format is 32 bpp
              [  1744.068] (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
              [  1744.068] (II) NVIDIA:     access.
              [  1744.071] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
              [  1744.071] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
              [  1744.071] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
              [  1744.071] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
              [  1744.071] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
              [  1744.071] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
              [  1744.071] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
              [  1744.071] (II) NVIDIA(0):     Config Options in the README.
              [  1744.088] (II) NVIDIA(0): Built-in logo is bigger than the screen.
              [  1744.088] (II) NVIDIA(0): Setting mode "NULL"
              [  1744.092] (==) NVIDIA(0): Disabling shared memory pixmaps
              [  1744.092] (==) NVIDIA(0): Backing store enabled
              [  1744.092] (==) NVIDIA(0): Silken mouse enabled
              [  1744.093] (==) NVIDIA(0): DPMS enabled
              [  1744.093] (II) Loading sub module "dri2"
              [  1744.093] (II) LoadModule: "dri2"
              [  1744.093] (II) Module "dri2" already built-in
              [  1744.093] (II) NVIDIA(0): [DRI2] Setup complete
              [  1744.093] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
              [  1744.093] (--) RandR disabled
              [  1744.095] (II) Initializing extension GLX
              [  1744.095] (II) Indirect GLX disabled.
              [  1744.145] (II) config/udev: Adding input device Power Button (/dev/input/event4)
              [  1744.145] (**) Power Button: Applying InputClass "evdev keyboard catchall"
              [  1744.145] (**) Power Button: Applying InputClass "libinput keyboard catchall"
              [  1744.145] (II) LoadModule: "libinput"
              [  1744.145] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
              [  1744.146] (II) Module libinput: vendor="X.Org Foundation"
              [  1744.146]    compiled for 1.18.4, module version = 0.22.0
              [  1744.146]    Module class: X.Org XInput Driver
              [  1744.146]    ABI class: X.Org XInput driver, version 22.1
              [  1744.146] (II) Using input driver 'libinput' for 'Power Button'
              [  1744.146] (**) Power Button: always reports core events
              [  1744.146] (**) Option "Device" "/dev/input/event4"
              [  1744.146] (**) Option "_source" "server/udev"
              [  1744.146] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
              [  1744.146] (II) input device 'Power Button', /dev/input/event4 is a keyboard
              [  1744.163] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4"
              [  1744.163] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
              [  1744.163] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
              [  1744.163] (II) input device 'Power Button', /dev/input/event4 is a keyboard
              [  1744.163] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
              [  1744.163] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
              [  1744.163] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
              [  1744.163] (II) Using input driver 'libinput' for 'Video Bus'
              [  1744.163] (**) Video Bus: always reports core events
              [  1744.163] (**) Option "Device" "/dev/input/event7"
              [  1744.163] (**) Option "_source" "server/udev"
              [  1744.164] (II) input device 'Video Bus', /dev/input/event7 is tagged by udev as: Keyboard
              [  1744.164] (II) input device 'Video Bus', /dev/input/event7 is a keyboard
              [  1744.186] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9/event7"
              [  1744.186] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
              [  1744.187] (II) input device 'Video Bus', /dev/input/event7 is tagged by udev as: Keyboard
              [  1744.187] (II) input device 'Video Bus', /dev/input/event7 is a keyboard
              [  1744.187] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
              [  1744.187] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
              [  1744.187] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
              [  1744.187] (II) Using input driver 'libinput' for 'Video Bus'
              [  1744.187] (**) Video Bus: always reports core events
              [  1744.187] (**) Option "Device" "/dev/input/event8"
              [  1744.187] (**) Option "_source" "server/udev"
              [  1744.188] (II) input device 'Video Bus', /dev/input/event8 is tagged by udev as: Keyboard
              [  1744.188] (II) input device 'Video Bus', /dev/input/event8 is a keyboard
              [  1744.203] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input10/event8"
              [  1744.203] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
              [  1744.204] (II) input device 'Video Bus', /dev/input/event8 is tagged by udev as: Keyboard
              [  1744.204] (II) input device 'Video Bus', /dev/input/event8 is a keyboard
              [  1744.205] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
              [  1744.205] (II) No input driver specified, ignoring this device.
              [  1744.205] (II) This device may have been added with another device file.
              [  1744.205] (II) config/udev: Adding input device Power Button (/dev/input/event3)
              [  1744.205] (**) Power Button: Applying InputClass "evdev keyboard catchall"
              [  1744.205] (**) Power Button: Applying InputClass "libinput keyboard catchall"
              [  1744.205] (II) Using input driver 'libinput' for 'Power Button'
              [  1744.205] (**) Power Button: always reports core events
              [  1744.205] (**) Option "Device" "/dev/input/event3"
              [  1744.205] (**) Option "_source" "server/udev"
              [  1744.206] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
              [  1744.206] (II) input device 'Power Button', /dev/input/event3 is a keyboard
              [  1744.223] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4/event3"
              [  1744.223] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
              [  1744.224] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
              [  1744.224] (II) input device 'Power Button', /dev/input/event3 is a keyboard
              [  1744.224] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
              [  1744.225] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
              [  1744.225] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
              [  1744.225] (II) Using input driver 'libinput' for 'Sleep Button'
              [  1744.225] (**) Sleep Button: always reports core events
              [  1744.225] (**) Option "Device" "/dev/input/event2"
              [  1744.225] (**) Option "_source" "server/udev"
              [  1744.225] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
              [  1744.225] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
              [  1744.243] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3/event2"
              [  1744.243] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10)
              [  1744.244] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
              [  1744.244] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
              [  1744.246] (II) config/udev: Adding input device Logitech M325 (/dev/input/event9)
              [  1744.246] (**) Logitech M325: Applying InputClass "evdev pointer catchall"
              [  1744.246] (**) Logitech M325: Applying InputClass "libinput pointer catchall"
              [  1744.246] (II) Using input driver 'libinput' for 'Logitech M325'
              [  1744.246] (**) Logitech M325: always reports core events
              [  1744.246] (**) Option "Device" "/dev/input/event9"
              [  1744.246] (**) Option "_source" "server/udev"
              [  1744.246] (II) input device 'Logitech M325', /dev/input/event9 is tagged by udev as: Mouse
              [  1744.247] (II) Device 'Logitech M325' set to 600 DPI
              [  1744.247] (II) input device 'Logitech M325', /dev/input/event9 is a pointer caps
              [  1744.293] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.2/0003:046D:C52B.0004/0003:046D:400A.0005/input/input11/event9"
              [  1744.293] (II) XINPUT: Adding extended input device "Logitech M325" (type: MOUSE, id 11)
              [  1744.293] (**) Option "AccelerationScheme" "none"
              [  1744.293] (**) Logitech M325: (accel) selected scheme none/0
              [  1744.293] (**) Logitech M325: (accel) acceleration factor: 2.000
              [  1744.293] (**) Logitech M325: (accel) acceleration threshold: 4
              [  1744.294] (II) input device 'Logitech M325', /dev/input/event9 is tagged by udev as: Mouse
              [  1744.294] (II) Device 'Logitech M325' set to 600 DPI
              [  1744.294] (II) input device 'Logitech M325', /dev/input/event9 is a pointer caps
              [  1744.295] (II) config/udev: Adding input device Logitech M325 (/dev/input/mouse0)
              [  1744.295] (II) No input driver specified, ignoring this device.
              [  1744.295] (II) This device may have been added with another device file.
              [  1744.296] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
              [  1744.296] (II) No input driver specified, ignoring this device.
              [  1744.296] (II) This device may have been added with another device file.
              [  1744.296] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
              [  1744.296] (II) No input driver specified, ignoring this device.
              [  1744.296] (II) This device may have been added with another device file.
              [  1744.297] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event13)
              [  1744.297] (II) No input driver specified, ignoring this device.
              [  1744.297] (II) This device may have been added with another device file.
              [  1744.297] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event14)
              [  1744.297] (II) No input driver specified, ignoring this device.
              [  1744.297] (II) This device may have been added with another device file.
              [  1744.298] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event15)
              [  1744.298] (II) No input driver specified, ignoring this device.
              [  1744.298] (II) This device may have been added with another device file.
              [  1744.299] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
              [  1744.299] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
              [  1744.299] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
              [  1744.299] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
              [  1744.299] (**) AT Translated Set 2 keyboard: always reports core events
              [  1744.299] (**) Option "Device" "/dev/input/event0"
              [  1744.299] (**) Option "_source" "server/udev"
              [  1744.299] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
              [  1744.299] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
              [  1744.343] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
              [  1744.343] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
              [  1744.344] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
              [  1744.344] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
              [  1744.345] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event10)
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
              [  1744.345] (II) LoadModule: "synaptics"
              [  1744.345] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
              [  1744.345] (II) Module synaptics: vendor="X.Org Foundation"
              [  1744.345]    compiled for 1.18.3, module version = 1.8.99
              [  1744.345]    Module class: X.Org XInput Driver
              [  1744.345]    ABI class: X.Org XInput driver, version 22.1
              [  1744.345] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
              [  1744.345] (**) SynPS/2 Synaptics TouchPad: always reports core events
              [  1744.345] (**) Option "Device" "/dev/input/event10"
              [  1744.383] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5706 (res 44)
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4800 (res 65)
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
              [  1744.383] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
              [  1744.383] (**) SynPS/2 Synaptics TouchPad: always reports core events
              [  1744.423] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event10"
              [  1744.423] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
              [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
              [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
              [  1744.423] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.037
              [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
              [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
              [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
              [  1744.423] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
              [  1744.423] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
              [  1744.424] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
              [  1744.424] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
              [  1744.425] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
              [  1744.425] (II) No input driver specified, ignoring this device.
              [  1744.425] (II) This device may have been added with another device file.
              [  1744.426] (II) config/udev: Adding input device MSI WMI hotkeys (/dev/input/event6)
              [  1744.426] (**) MSI WMI hotkeys: Applying InputClass "evdev keyboard catchall"
              [  1744.426] (**) MSI WMI hotkeys: Applying InputClass "libinput keyboard catchall"
              [  1744.426] (II) Using input driver 'libinput' for 'MSI WMI hotkeys'
              [  1744.426] (**) MSI WMI hotkeys: always reports core events
              [  1744.426] (**) Option "Device" "/dev/input/event6"
              [  1744.426] (**) Option "_source" "server/udev"
              [  1744.426] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is tagged by udev as: Keyboard
              [  1744.426] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is a keyboard
              [  1744.443] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event6"
              [  1744.443] (II) XINPUT: Adding extended input device "MSI WMI hotkeys" (type: KEYBOARD, id 14)
              [  1744.444] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is tagged by udev as: Keyboard
              [  1744.444] (II) input device 'MSI WMI hotkeys', /dev/input/event6 is a keyboard
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "synaptics"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.708] (II) UnloadModule: "libinput"
              [  1744.709] (II) UnloadModule: "libinput"
              [  1744.736] (II) NVIDIA(GPU-0): Deleting GPU-0
              [  1744.807] (II) Server terminated successfully (0). Closing log file.
              

              /etc/X11/xorg.conf:

              # nvidia-xconfig: X configuration file generated by nvidia-xconfig
              # nvidia-xconfig:  version 375.10  (buildmeister@swio-display-x86-rhel47-09)  Fri Oct 14 11:11:07 PDT 2016
              
              Section "ServerLayout"
                  Identifier     "Layout0"
                  Screen      0  "Screen0"
                  InputDevice    "Keyboard0" "CoreKeyboard"
                  InputDevice    "Mouse0" "CorePointer"
              EndSection
              
              #Section "Files"
              #EndSection
              
              Section "InputDevice"
                  # generated from default
                  Identifier     "Mouse0"
                  Driver         "mouse"
                  Option         "Protocol" "auto"
                  Option         "Device" "/dev/psaux"
                 Option         "Emulate3Buttons" "no"
                  Option         "ZAxisMapping" "4 5"
              EndSection
              
              Section "InputDevice"
              # generated from default
                  Identifier     "Keyboard0"
                  Driver         "kbd"
              EndSection
              
              Section "Monitor"
                  Identifier     "Monitor1"
              #    VendorName     "Unknown"
              #    ModelName      "Unknown"
              #    HorizSync       28.0 - 33.0
              #    VertRefresh     43.0 - 72.0
              #    Option         "DPMS"
              EndSection
              
              Section "Device"
                  Identifier     "DiscreteNvidia"
                  Driver         "nvidia"
                  VendorName     "NVIDIA Corporation"
                  BoardName      "GeForce GTX 960M"
                  BusID      "PCI:1:0:0"
              EndSection
              
              Section "Screen"
                  Identifier     "Screen0"
                  Device         "Device0"
                  Monitor        "Monitor0"
                  DefaultDepth    24
                  SubSection     "Display"
                     Depth       24
                  EndSubSection
              EndSection
              

              arch-linux xorg

              share|improve this question

              share|improve this question

              share|improve this question

              share|improve this question

              asked Nov 15 ’16 at 14:37

              MarcelMarcel

              1251118

              1251118

                  1 Answer
                  1

                  active

                  oldest

                  votes

                  0

                  Welcome to the Nvidia vs. Linux war!

                  1- First off purge all Nvidia drivers:

                  • sudo apt-get purge nvidia-*

                  2- Next, reconfigure your xorg:

                  • Make a copy and save it in a safe place >this file> /etc/X11/xorg.conf. If things go wrong you might need it later again:

                  sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.BACKUP

                  The next steps will reconfigure your xorg and install nouveau drivers(intel GPU)

                  sudo apt-get install nouveau-firmware

                  sudo dpkg-reconfigure xserver-xorg

                  Now to get Nvidia on your Linux system you need BumbleBee!

                  share|improve this answer

                  • I am using arch. I don’t have apt. Do you know the equivalent commands? Is there really no way to use nvidia drivers? I have to use my integrated gpu? I have had success before with nvidia drivers.

                    – Marcel
                    Nov 15 ’16 at 15:05

                  • My bad I assumed you had Ubuntu. Try this and see pacman -Ss xf86-video

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:07

                  • wiki.archlinux.org/index.php/nouveau

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:16

                  • Nvidia gave me a headache back in the day on Ubuntu. If you still want to use them check out bumblebee-project.org . The only way to get them running without errors.

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:20

                  Your Answer

                  StackExchange.ready(function() {
                  var channelOptions = {
                  tags: “”.split(” “),
                  id: “106”
                  };
                  initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                  StackExchange.using(“externalEditor”, function() {
                  // Have to fire editor after snippets, if snippets enabled
                  if (StackExchange.settings.snippets.snippetsEnabled) {
                  StackExchange.using(“snippets”, function() {
                  createEditor();
                  });
                  }
                  else {
                  createEditor();
                  }
                  });

                  function createEditor() {
                  StackExchange.prepareEditor({
                  heartbeatType: ‘answer’,
                  autoActivateHeartbeat: false,
                  convertImagesToLinks: false,
                  noModals: true,
                  showLowRepImageUploadWarning: true,
                  reputationToPostImages: null,
                  bindNavPrevention: true,
                  postfix: “”,
                  imageUploader: {
                  brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                  contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                  allowUrls: true
                  },
                  onDemand: true,
                  discardSelector: “.discard-answer”
                  ,immediatelyShowMarkdownHelp:true
                  });

                  }
                  });

                  draft saved
                  draft discarded

                  StackExchange.ready(
                  function () {
                  StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f323439%2fxorg-not-working%23new-answer’, ‘question_page’);
                  }
                  );

                  Post as a guest

                  Required, but never shown

                  1 Answer
                  1

                  active

                  oldest

                  votes

                  1 Answer
                  1

                  active

                  oldest

                  votes

                  active

                  oldest

                  votes

                  active

                  oldest

                  votes

                  0

                  Welcome to the Nvidia vs. Linux war!

                  1- First off purge all Nvidia drivers:

                  • sudo apt-get purge nvidia-*

                  2- Next, reconfigure your xorg:

                  • Make a copy and save it in a safe place >this file> /etc/X11/xorg.conf. If things go wrong you might need it later again:

                  sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.BACKUP

                  The next steps will reconfigure your xorg and install nouveau drivers(intel GPU)

                  sudo apt-get install nouveau-firmware

                  sudo dpkg-reconfigure xserver-xorg

                  Now to get Nvidia on your Linux system you need BumbleBee!

                  share|improve this answer

                  • I am using arch. I don’t have apt. Do you know the equivalent commands? Is there really no way to use nvidia drivers? I have to use my integrated gpu? I have had success before with nvidia drivers.

                    – Marcel
                    Nov 15 ’16 at 15:05

                  • My bad I assumed you had Ubuntu. Try this and see pacman -Ss xf86-video

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:07

                  • wiki.archlinux.org/index.php/nouveau

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:16

                  • Nvidia gave me a headache back in the day on Ubuntu. If you still want to use them check out bumblebee-project.org . The only way to get them running without errors.

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:20

                  0

                  Welcome to the Nvidia vs. Linux war!

                  1- First off purge all Nvidia drivers:

                  • sudo apt-get purge nvidia-*

                  2- Next, reconfigure your xorg:

                  • Make a copy and save it in a safe place >this file> /etc/X11/xorg.conf. If things go wrong you might need it later again:

                  sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.BACKUP

                  The next steps will reconfigure your xorg and install nouveau drivers(intel GPU)

                  sudo apt-get install nouveau-firmware

                  sudo dpkg-reconfigure xserver-xorg

                  Now to get Nvidia on your Linux system you need BumbleBee!

                  share|improve this answer

                  • I am using arch. I don’t have apt. Do you know the equivalent commands? Is there really no way to use nvidia drivers? I have to use my integrated gpu? I have had success before with nvidia drivers.

                    – Marcel
                    Nov 15 ’16 at 15:05

                  • My bad I assumed you had Ubuntu. Try this and see pacman -Ss xf86-video

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:07

                  • wiki.archlinux.org/index.php/nouveau

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:16

                  • Nvidia gave me a headache back in the day on Ubuntu. If you still want to use them check out bumblebee-project.org . The only way to get them running without errors.

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:20

                  0

                  0

                  0

                  Welcome to the Nvidia vs. Linux war!

                  1- First off purge all Nvidia drivers:

                  • sudo apt-get purge nvidia-*

                  2- Next, reconfigure your xorg:

                  • Make a copy and save it in a safe place >this file> /etc/X11/xorg.conf. If things go wrong you might need it later again:

                  sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.BACKUP

                  The next steps will reconfigure your xorg and install nouveau drivers(intel GPU)

                  sudo apt-get install nouveau-firmware

                  sudo dpkg-reconfigure xserver-xorg

                  Now to get Nvidia on your Linux system you need BumbleBee!

                  share|improve this answer

                  Welcome to the Nvidia vs. Linux war!

                  1- First off purge all Nvidia drivers:

                  • sudo apt-get purge nvidia-*

                  2- Next, reconfigure your xorg:

                  • Make a copy and save it in a safe place >this file> /etc/X11/xorg.conf. If things go wrong you might need it later again:

                  sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.BACKUP

                  The next steps will reconfigure your xorg and install nouveau drivers(intel GPU)

                  sudo apt-get install nouveau-firmware

                  sudo dpkg-reconfigure xserver-xorg

                  Now to get Nvidia on your Linux system you need BumbleBee!

                  share|improve this answer

                  share|improve this answer

                  share|improve this answer

                  edited Nov 15 ’16 at 15:05

                  answered Nov 15 ’16 at 15:03

                  MichaelMMeskhiMichaelMMeskhi

                  1012

                  1012

                  • I am using arch. I don’t have apt. Do you know the equivalent commands? Is there really no way to use nvidia drivers? I have to use my integrated gpu? I have had success before with nvidia drivers.

                    – Marcel
                    Nov 15 ’16 at 15:05

                  • My bad I assumed you had Ubuntu. Try this and see pacman -Ss xf86-video

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:07

                  • wiki.archlinux.org/index.php/nouveau

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:16

                  • Nvidia gave me a headache back in the day on Ubuntu. If you still want to use them check out bumblebee-project.org . The only way to get them running without errors.

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:20

                  • I am using arch. I don’t have apt. Do you know the equivalent commands? Is there really no way to use nvidia drivers? I have to use my integrated gpu? I have had success before with nvidia drivers.

                    – Marcel
                    Nov 15 ’16 at 15:05

                  • My bad I assumed you had Ubuntu. Try this and see pacman -Ss xf86-video

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:07

                  • wiki.archlinux.org/index.php/nouveau

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:16

                  • Nvidia gave me a headache back in the day on Ubuntu. If you still want to use them check out bumblebee-project.org . The only way to get them running without errors.

                    – MichaelMMeskhi
                    Nov 15 ’16 at 15:20

                  I am using arch. I don’t have apt. Do you know the equivalent commands? Is there really no way to use nvidia drivers? I have to use my integrated gpu? I have had success before with nvidia drivers.

                  – Marcel
                  Nov 15 ’16 at 15:05

                  I am using arch. I don’t have apt. Do you know the equivalent commands? Is there really no way to use nvidia drivers? I have to use my integrated gpu? I have had success before with nvidia drivers.

                  – Marcel
                  Nov 15 ’16 at 15:05

                  My bad I assumed you had Ubuntu. Try this and see pacman -Ss xf86-video

                  – MichaelMMeskhi
                  Nov 15 ’16 at 15:07

                  My bad I assumed you had Ubuntu. Try this and see pacman -Ss xf86-video

                  – MichaelMMeskhi
                  Nov 15 ’16 at 15:07

                  wiki.archlinux.org/index.php/nouveau

                  – MichaelMMeskhi
                  Nov 15 ’16 at 15:16

                  wiki.archlinux.org/index.php/nouveau

                  – MichaelMMeskhi
                  Nov 15 ’16 at 15:16

                  Nvidia gave me a headache back in the day on Ubuntu. If you still want to use them check out bumblebee-project.org . The only way to get them running without errors.

                  – MichaelMMeskhi
                  Nov 15 ’16 at 15:20

                  Nvidia gave me a headache back in the day on Ubuntu. If you still want to use them check out bumblebee-project.org . The only way to get them running without errors.

                  – MichaelMMeskhi
                  Nov 15 ’16 at 15:20

                  draft saved
                  draft discarded

                  Thanks for contributing an answer to Unix & Linux Stack Exchange!

                  • Please be sure to answer the question. Provide details and share your research!

                  But avoid

                  • Asking for help, clarification, or responding to other answers.
                  • Making statements based on opinion; back them up with references or personal experience.

                  To learn more, see our tips on writing great answers.

                  draft saved

                  draft discarded

                  StackExchange.ready(
                  function () {
                  StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f323439%2fxorg-not-working%23new-answer’, ‘question_page’);
                  }
                  );

                  Post as a guest

                  Required, but never shown

                  Required, but never shown

                  Required, but never shown

                  Required, but never shown

                  Required, but never shown

                  Required, but never shown

                  Required, but never shown

                  Required, but never shown

                  Required, but never shown

                  Installing Nvidia drivers causes system to boot to tty1 only. What am I doing wrong?

                  The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                  0

                  When I do a clean install of Kali 1.0.9, it will work for a few minutes until I start up something like system settings, or iceweasel, it will then crash my graphics and give me weird dots all over the screen. So I force reboot and go through the steps to install nvidia drivers, and when rebooted to blacklist the nouveau driver, all I get is the tty1 console. Purging nvidia drivers and starting up with nomodeset will get it working stable, but the graphics are terrible and its only in 4:3. I’m out of ideas with what to do.

                  when running:

                   lspci | grep VGA
                  

                  I get

                   VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150se nForce 430] (rev a2)
                  

                  my processor is an AMD Athlon 64×2 dual core

                  share|improve this question

                    0

                    When I do a clean install of Kali 1.0.9, it will work for a few minutes until I start up something like system settings, or iceweasel, it will then crash my graphics and give me weird dots all over the screen. So I force reboot and go through the steps to install nvidia drivers, and when rebooted to blacklist the nouveau driver, all I get is the tty1 console. Purging nvidia drivers and starting up with nomodeset will get it working stable, but the graphics are terrible and its only in 4:3. I’m out of ideas with what to do.

                    when running:

                     lspci | grep VGA
                    

                    I get

                     VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150se nForce 430] (rev a2)
                    

                    my processor is an AMD Athlon 64×2 dual core

                    share|improve this question

                      0

                      0

                      0

                      When I do a clean install of Kali 1.0.9, it will work for a few minutes until I start up something like system settings, or iceweasel, it will then crash my graphics and give me weird dots all over the screen. So I force reboot and go through the steps to install nvidia drivers, and when rebooted to blacklist the nouveau driver, all I get is the tty1 console. Purging nvidia drivers and starting up with nomodeset will get it working stable, but the graphics are terrible and its only in 4:3. I’m out of ideas with what to do.

                      when running:

                       lspci | grep VGA
                      

                      I get

                       VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150se nForce 430] (rev a2)
                      

                      my processor is an AMD Athlon 64×2 dual core

                      share|improve this question

                      When I do a clean install of Kali 1.0.9, it will work for a few minutes until I start up something like system settings, or iceweasel, it will then crash my graphics and give me weird dots all over the screen. So I force reboot and go through the steps to install nvidia drivers, and when rebooted to blacklist the nouveau driver, all I get is the tty1 console. Purging nvidia drivers and starting up with nomodeset will get it working stable, but the graphics are terrible and its only in 4:3. I’m out of ideas with what to do.

                      when running:

                       lspci | grep VGA
                      

                      I get

                       VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150se nForce 430] (rev a2)
                      

                      my processor is an AMD Athlon 64×2 dual core

                      xorg nvidia kali-linux

                      share|improve this question

                      share|improve this question

                      share|improve this question

                      share|improve this question

                      edited Nov 18 ’14 at 6:20

                      Anthon

                      61.1k17104168

                      61.1k17104168

                      asked Nov 18 ’14 at 5:42

                      TannerTanner

                      11

                      11

                          1 Answer
                          1

                          active

                          oldest

                          votes

                          0

                          Found it. NVIDIA offers their drivers on their website. I went to my other computer and downloaded the specific driver for my graphics card. Transferred it to my machine and right clicked > properties > permissions. Then checked “allow executing file as a program”. after doing this i saved it to my home folder. then switched to tty1 with ctrl-alt-f1. logged in as root and shutdown the graphical interface with

                          service gdm3 stop
                          

                          (after doing this, to save some time, it would be best to shut down the default nouveau driver as well, i didnt. But during the install it will do it for you and you’ll have to reboot and shutdown the GUI again through tty1.)

                          from there i entered in

                          ./NVIDIA-Linux-x86_64-304.123.run
                          

                          which is the file name for the device driver, and it started up the install in terminal. asks some basic yes or no questions. and even offers to automatically reconfigure your nvidia-xconfig file. Allow it to do this so you wont have to do it manually. then you’ll reboot and youll have full graphics support. only took me 4 days to get here. was especially difficult to find the proper service to shut down the GUI but was a great learning opportunity. Hopefully my struggles can help some others.

                          share|improve this answer

                            Your Answer

                            StackExchange.ready(function() {
                            var channelOptions = {
                            tags: “”.split(” “),
                            id: “106”
                            };
                            initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                            StackExchange.using(“externalEditor”, function() {
                            // Have to fire editor after snippets, if snippets enabled
                            if (StackExchange.settings.snippets.snippetsEnabled) {
                            StackExchange.using(“snippets”, function() {
                            createEditor();
                            });
                            }
                            else {
                            createEditor();
                            }
                            });

                            function createEditor() {
                            StackExchange.prepareEditor({
                            heartbeatType: ‘answer’,
                            autoActivateHeartbeat: false,
                            convertImagesToLinks: false,
                            noModals: true,
                            showLowRepImageUploadWarning: true,
                            reputationToPostImages: null,
                            bindNavPrevention: true,
                            postfix: “”,
                            imageUploader: {
                            brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                            contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                            allowUrls: true
                            },
                            onDemand: true,
                            discardSelector: “.discard-answer”
                            ,immediatelyShowMarkdownHelp:true
                            });

                            }
                            });

                            draft saved
                            draft discarded

                            StackExchange.ready(
                            function () {
                            StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f168591%2finstalling-nvidia-drivers-causes-system-to-boot-to-tty1-only-what-am-i-doing-wr%23new-answer’, ‘question_page’);
                            }
                            );

                            Post as a guest

                            Required, but never shown

                            1 Answer
                            1

                            active

                            oldest

                            votes

                            1 Answer
                            1

                            active

                            oldest

                            votes

                            active

                            oldest

                            votes

                            active

                            oldest

                            votes

                            0

                            Found it. NVIDIA offers their drivers on their website. I went to my other computer and downloaded the specific driver for my graphics card. Transferred it to my machine and right clicked > properties > permissions. Then checked “allow executing file as a program”. after doing this i saved it to my home folder. then switched to tty1 with ctrl-alt-f1. logged in as root and shutdown the graphical interface with

                            service gdm3 stop
                            

                            (after doing this, to save some time, it would be best to shut down the default nouveau driver as well, i didnt. But during the install it will do it for you and you’ll have to reboot and shutdown the GUI again through tty1.)

                            from there i entered in

                            ./NVIDIA-Linux-x86_64-304.123.run
                            

                            which is the file name for the device driver, and it started up the install in terminal. asks some basic yes or no questions. and even offers to automatically reconfigure your nvidia-xconfig file. Allow it to do this so you wont have to do it manually. then you’ll reboot and youll have full graphics support. only took me 4 days to get here. was especially difficult to find the proper service to shut down the GUI but was a great learning opportunity. Hopefully my struggles can help some others.

                            share|improve this answer

                              0

                              Found it. NVIDIA offers their drivers on their website. I went to my other computer and downloaded the specific driver for my graphics card. Transferred it to my machine and right clicked > properties > permissions. Then checked “allow executing file as a program”. after doing this i saved it to my home folder. then switched to tty1 with ctrl-alt-f1. logged in as root and shutdown the graphical interface with

                              service gdm3 stop
                              

                              (after doing this, to save some time, it would be best to shut down the default nouveau driver as well, i didnt. But during the install it will do it for you and you’ll have to reboot and shutdown the GUI again through tty1.)

                              from there i entered in

                              ./NVIDIA-Linux-x86_64-304.123.run
                              

                              which is the file name for the device driver, and it started up the install in terminal. asks some basic yes or no questions. and even offers to automatically reconfigure your nvidia-xconfig file. Allow it to do this so you wont have to do it manually. then you’ll reboot and youll have full graphics support. only took me 4 days to get here. was especially difficult to find the proper service to shut down the GUI but was a great learning opportunity. Hopefully my struggles can help some others.

                              share|improve this answer

                                0

                                0

                                0

                                Found it. NVIDIA offers their drivers on their website. I went to my other computer and downloaded the specific driver for my graphics card. Transferred it to my machine and right clicked > properties > permissions. Then checked “allow executing file as a program”. after doing this i saved it to my home folder. then switched to tty1 with ctrl-alt-f1. logged in as root and shutdown the graphical interface with

                                service gdm3 stop
                                

                                (after doing this, to save some time, it would be best to shut down the default nouveau driver as well, i didnt. But during the install it will do it for you and you’ll have to reboot and shutdown the GUI again through tty1.)

                                from there i entered in

                                ./NVIDIA-Linux-x86_64-304.123.run
                                

                                which is the file name for the device driver, and it started up the install in terminal. asks some basic yes or no questions. and even offers to automatically reconfigure your nvidia-xconfig file. Allow it to do this so you wont have to do it manually. then you’ll reboot and youll have full graphics support. only took me 4 days to get here. was especially difficult to find the proper service to shut down the GUI but was a great learning opportunity. Hopefully my struggles can help some others.

                                share|improve this answer

                                Found it. NVIDIA offers their drivers on their website. I went to my other computer and downloaded the specific driver for my graphics card. Transferred it to my machine and right clicked > properties > permissions. Then checked “allow executing file as a program”. after doing this i saved it to my home folder. then switched to tty1 with ctrl-alt-f1. logged in as root and shutdown the graphical interface with

                                service gdm3 stop
                                

                                (after doing this, to save some time, it would be best to shut down the default nouveau driver as well, i didnt. But during the install it will do it for you and you’ll have to reboot and shutdown the GUI again through tty1.)

                                from there i entered in

                                ./NVIDIA-Linux-x86_64-304.123.run
                                

                                which is the file name for the device driver, and it started up the install in terminal. asks some basic yes or no questions. and even offers to automatically reconfigure your nvidia-xconfig file. Allow it to do this so you wont have to do it manually. then you’ll reboot and youll have full graphics support. only took me 4 days to get here. was especially difficult to find the proper service to shut down the GUI but was a great learning opportunity. Hopefully my struggles can help some others.

                                share|improve this answer

                                share|improve this answer

                                share|improve this answer

                                answered Nov 18 ’14 at 10:58

                                TannerTanner

                                11

                                11

                                    draft saved
                                    draft discarded

                                    Thanks for contributing an answer to Unix & Linux Stack Exchange!

                                    • Please be sure to answer the question. Provide details and share your research!

                                    But avoid

                                    • Asking for help, clarification, or responding to other answers.
                                    • Making statements based on opinion; back them up with references or personal experience.

                                    To learn more, see our tips on writing great answers.

                                    draft saved

                                    draft discarded

                                    StackExchange.ready(
                                    function () {
                                    StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f168591%2finstalling-nvidia-drivers-causes-system-to-boot-to-tty1-only-what-am-i-doing-wr%23new-answer’, ‘question_page’);
                                    }
                                    );

                                    Post as a guest

                                    Required, but never shown

                                    Required, but never shown

                                    Required, but never shown

                                    Required, but never shown

                                    Required, but never shown

                                    Required, but never shown

                                    Required, but never shown

                                    Required, but never shown

                                    Required, but never shown

                                    xfce4-panel and Xorg using 100% CPU when the panel Background set to ‘None (use system style)’

                                    The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                    0

                                    When, I use some specific themes like the Vimix theme, xfce4 and xorg combined are using more than 90% of CPU!

                                    If I go to Panel Preferences -> Appearance -> and change Background Style from ‘None’ (use system style), to ‘something else’ the the CPU usage reduces to normal.

                                    I have modded the vimix theme it can be found: Here

                                    This theme also wastes > 90% of CPU, what is causing it? How can I fix this bug?

                                    share|improve this question

                                      0

                                      When, I use some specific themes like the Vimix theme, xfce4 and xorg combined are using more than 90% of CPU!

                                      If I go to Panel Preferences -> Appearance -> and change Background Style from ‘None’ (use system style), to ‘something else’ the the CPU usage reduces to normal.

                                      I have modded the vimix theme it can be found: Here

                                      This theme also wastes > 90% of CPU, what is causing it? How can I fix this bug?

                                      share|improve this question

                                        0

                                        0

                                        0

                                        When, I use some specific themes like the Vimix theme, xfce4 and xorg combined are using more than 90% of CPU!

                                        If I go to Panel Preferences -> Appearance -> and change Background Style from ‘None’ (use system style), to ‘something else’ the the CPU usage reduces to normal.

                                        I have modded the vimix theme it can be found: Here

                                        This theme also wastes > 90% of CPU, what is causing it? How can I fix this bug?

                                        share|improve this question

                                        When, I use some specific themes like the Vimix theme, xfce4 and xorg combined are using more than 90% of CPU!

                                        If I go to Panel Preferences -> Appearance -> and change Background Style from ‘None’ (use system style), to ‘something else’ the the CPU usage reduces to normal.

                                        I have modded the vimix theme it can be found: Here

                                        This theme also wastes > 90% of CPU, what is causing it? How can I fix this bug?

                                        xorg xfce theme

                                        share|improve this question

                                        share|improve this question

                                        share|improve this question

                                        share|improve this question

                                        edited Feb 15 at 3:50

                                        S.Goswami

                                        asked Feb 15 at 3:25

                                        S.GoswamiS.Goswami

                                        226

                                        226

                                            0

                                            active

                                            oldest

                                            votes

                                            Your Answer

                                            StackExchange.ready(function() {
                                            var channelOptions = {
                                            tags: “”.split(” “),
                                            id: “106”
                                            };
                                            initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                            StackExchange.using(“externalEditor”, function() {
                                            // Have to fire editor after snippets, if snippets enabled
                                            if (StackExchange.settings.snippets.snippetsEnabled) {
                                            StackExchange.using(“snippets”, function() {
                                            createEditor();
                                            });
                                            }
                                            else {
                                            createEditor();
                                            }
                                            });

                                            function createEditor() {
                                            StackExchange.prepareEditor({
                                            heartbeatType: ‘answer’,
                                            autoActivateHeartbeat: false,
                                            convertImagesToLinks: false,
                                            noModals: true,
                                            showLowRepImageUploadWarning: true,
                                            reputationToPostImages: null,
                                            bindNavPrevention: true,
                                            postfix: “”,
                                            imageUploader: {
                                            brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                            contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                            allowUrls: true
                                            },
                                            onDemand: true,
                                            discardSelector: “.discard-answer”
                                            ,immediatelyShowMarkdownHelp:true
                                            });

                                            }
                                            });

                                            draft saved
                                            draft discarded

                                            StackExchange.ready(
                                            function () {
                                            StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f500771%2fxfce4-panel-and-xorg-using-100-cpu-when-the-panel-background-set-to-none-use%23new-answer’, ‘question_page’);
                                            }
                                            );

                                            Post as a guest

                                            Required, but never shown

                                            0

                                            active

                                            oldest

                                            votes

                                            0

                                            active

                                            oldest

                                            votes

                                            active

                                            oldest

                                            votes

                                            active

                                            oldest

                                            votes

                                            draft saved
                                            draft discarded

                                            Thanks for contributing an answer to Unix & Linux Stack Exchange!

                                            • Please be sure to answer the question. Provide details and share your research!

                                            But avoid

                                            • Asking for help, clarification, or responding to other answers.
                                            • Making statements based on opinion; back them up with references or personal experience.

                                            To learn more, see our tips on writing great answers.

                                            draft saved

                                            draft discarded

                                            StackExchange.ready(
                                            function () {
                                            StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f500771%2fxfce4-panel-and-xorg-using-100-cpu-when-the-panel-background-set-to-none-use%23new-answer’, ‘question_page’);
                                            }
                                            );

                                            Post as a guest

                                            Required, but never shown

                                            Required, but never shown

                                            Required, but never shown

                                            Required, but never shown

                                            Required, but never shown

                                            Required, but never shown

                                            Required, but never shown

                                            Required, but never shown

                                            Required, but never shown

                                            Black screen after installing Nvidia drivers on Debian Stretch

                                            The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                            1

                                            I have installed latest Debian Stretch on my MSI laptop and I want to install Nvidia proprietary drivers for my GTX 1060 graphics card.

                                            I followed this guide on Debian’s wiki: https://wiki.debian.org/NvidiaGraphicsDrivers.

                                            Here are the steps I followed on my fresh install:

                                            First I added stretch-backports and ‘contrib non-free’ postfix. My /etc/apt/sources.list dump:

                                            # 
                                            
                                            # deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main
                                            
                                            #deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main
                                            
                                            deb http://ftp.hu.debian.org/debian/ stretch main contrib non-free
                                            deb-src http://ftp.hu.debian.org/debian/ stretch main
                                            
                                            deb http://security.debian.org/debian-security stretch/updates main contrib non-free
                                            deb-src http://security.debian.org/debian-security stretch/updates main
                                            
                                            # stretch-updates, previously known as 'volatile'
                                            deb http://ftp.hu.debian.org/debian/ stretch-updates main contrib non-free
                                            deb-src http://ftp.hu.debian.org/debian/ stretch-updates main
                                            
                                            # stretch-backports
                                            deb http://httpredir.debian.org/debian stretch-backports main contrib non-free
                                            

                                            Then I ran the followings as root:

                                            $ dpkg --add-architecture i386
                                            $ apt-get update
                                            $ apt-get install build-essential
                                            $ apt-get install linux-headers-$(uname -r|sed 's/[^-]*-[^-]*-//')
                                            $ apt-get -t stretch-backports install nvidia-driver
                                            

                                            I rebooted the system but on boot where gnome should have started I see a black screen without a cursor. I do have access to other terminals. Here is my Xorg.0.log:

                                            [    23.138] (--) Log file renamed from "/var/log/Xorg.pid-823.log" to "/var/log/Xorg.0.log"
                                            [    23.140] 
                                            X.Org X Server 1.19.2
                                            Release Date: 2017-03-02
                                            [    23.140] X Protocol Version 11, Revision 0
                                            [    23.140] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
                                            [    23.140] Current Operating System: Linux zion 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
                                            [    23.140] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-8-amd64 root=UUID=79569e63-703c-4939-ae49-32f4997c9c72 ro quiet
                                            [    23.140] Build Date: 03 November 2018  03:09:11AM
                                            [    23.140] xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support) 
                                            [    23.140] Current version of pixman: 0.34.0
                                            [    23.140]    Before reporting problems, check http://wiki.x.org
                                                to make sure that you have the latest version.
                                            [    23.140] Markers: (--) probed, (**) from config file, (==) default setting,
                                                (++) from command line, (!!) notice, (II) informational,
                                                (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
                                            [    23.140] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 13 20:06:40 2019
                                            [    23.143] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
                                            [    23.145] (==) No Layout section.  Using the first Screen section.
                                            [    23.145] (==) No screen section available. Using defaults.
                                            [    23.145] (**) |-->Screen "Default Screen Section" (0)
                                            [    23.145] (**) |   |-->Monitor "<default monitor>"
                                            [    23.146] (==) No monitor specified for screen "Default Screen Section".
                                                Using a default monitor configuration.
                                            [    23.146] (==) Automatically adding devices
                                            [    23.146] (==) Automatically enabling devices
                                            [    23.146] (==) Automatically adding GPU devices
                                            [    23.146] (==) Max clients allowed: 256, resource mask: 0x1fffff
                                            [    23.148] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
                                            [    23.148]    Entry deleted from font path.
                                            [    23.152] (==) FontPath set to:
                                                /usr/share/fonts/X11/misc,
                                                /usr/share/fonts/X11/100dpi/:unscaled,
                                                /usr/share/fonts/X11/75dpi/:unscaled,
                                                /usr/share/fonts/X11/Type1,
                                                /usr/share/fonts/X11/100dpi,
                                                /usr/share/fonts/X11/75dpi,
                                                built-ins
                                            [    23.152] (**) ModulePath set to "/usr/lib/xorg/modules/linux,/usr/lib/xorg/modules"
                                            [    23.152] (II) The server relies on udev to provide the list of input devices.
                                                If no devices become available, reconfigure udev or disable AutoAddDevices.
                                            [    23.152] (II) Loader magic: 0x555783fdbe00
                                            [    23.152] (II) Module ABI versions:
                                            [    23.152]    X.Org ANSI C Emulation: 0.4
                                            [    23.152]    X.Org Video Driver: 23.0
                                            [    23.152]    X.Org XInput driver : 24.1
                                            [    23.152]    X.Org Server Extension : 10.0
                                            [    23.154] (++) using VT number 1
                                            
                                            [    23.159] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
                                            [    23.159] (II) xfree86: Adding drm device (/dev/dri/card0)
                                            [    23.161] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
                                            [    23.165] (--) PCI:*(0:0:2:0) 8086:3e9b:1462:1223 rev 0, Mem @ 0xa2000000/16777216, 0x80000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
                                            [    23.165] (--) PCI: (0:1:0:0) 10de:1c20:1462:1223 rev 161, Mem @ 0xa3000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
                                            [    23.165] (II) LoadModule: "glx"
                                            [    23.167] (II) Loading /usr/lib/xorg/modules/linux/libglx.so
                                            [    23.215] (II) Module glx: vendor="NVIDIA Corporation"
                                            [    23.215]    compiled for 4.0.2, module version = 1.0.0
                                            [    23.215]    Module class: X.Org Server Extension
                                            [    23.215] (II) NVIDIA GLX Module  390.87  Tue Aug 21 16:10:56 PDT 2018
                                            [    23.216] (II) Applying OutputClass "nvidia" to /dev/dri/card0
                                            [    23.216]    loading driver: nvidia
                                            [    23.216] (==) Matched nvidia as autoconfigured driver 0
                                            [    23.216] (==) Matched nouveau as autoconfigured driver 1
                                            [    23.216] (==) Matched nv as autoconfigured driver 2
                                            [    23.216] (==) Matched modesetting as autoconfigured driver 3
                                            [    23.216] (==) Matched fbdev as autoconfigured driver 4
                                            [    23.216] (==) Matched vesa as autoconfigured driver 5
                                            [    23.216] (==) Assigned the driver to the xf86ConfigLayout
                                            [    23.216] (II) LoadModule: "nvidia"
                                            [    23.216] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
                                            [    23.221] (II) Module nvidia: vendor="NVIDIA Corporation"
                                            [    23.221]    compiled for 4.0.2, module version = 1.0.0
                                            [    23.221]    Module class: X.Org Video Driver
                                            [    23.221] (II) LoadModule: "nouveau"
                                            [    23.221] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
                                            [    23.223] (II) Module nouveau: vendor="X.Org Foundation"
                                            [    23.223]    compiled for 1.19.3, module version = 1.0.13
                                            [    23.223]    Module class: X.Org Video Driver
                                            [    23.223]    ABI class: X.Org Video Driver, version 23.0
                                            [    23.223] (II) LoadModule: "nv"
                                            [    23.223] (WW) Warning, couldn't open module nv
                                            [    23.223] (II) UnloadModule: "nv"
                                            [    23.223] (II) Unloading nv
                                            [    23.223] (EE) Failed to load module "nv" (module does not exist, 0)
                                            [    23.223] (II) LoadModule: "modesetting"
                                            [    23.223] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
                                            [    23.224] (II) Module modesetting: vendor="X.Org Foundation"
                                            [    23.224]    compiled for 1.19.2, module version = 1.19.2
                                            [    23.224]    Module class: X.Org Video Driver
                                            [    23.224]    ABI class: X.Org Video Driver, version 23.0
                                            [    23.224] (II) LoadModule: "fbdev"
                                            [    23.224] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
                                            [    23.224] (II) Module fbdev: vendor="X.Org Foundation"
                                            [    23.224]    compiled for 1.19.0, module version = 0.4.4
                                            [    23.224]    Module class: X.Org Video Driver
                                            [    23.224]    ABI class: X.Org Video Driver, version 23.0
                                            [    23.224] (II) LoadModule: "vesa"
                                            [    23.224] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
                                            [    23.225] (II) Module vesa: vendor="X.Org Foundation"
                                            [    23.225]    compiled for 1.19.0, module version = 2.3.4
                                            [    23.225]    Module class: X.Org Video Driver
                                            [    23.225]    ABI class: X.Org Video Driver, version 23.0
                                            [    23.225] (II) NVIDIA dlloader X Driver  390.87  Tue Aug 21 15:44:49 PDT 2018
                                            [    23.225] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
                                            [    23.225] (II) NOUVEAU driver Date:   Tue Sep 20 00:31:06 2016 -0400
                                            [    23.225] (II) NOUVEAU driver for NVIDIA chipset families :
                                            [    23.225]    RIVA TNT        (NV04)
                                            [    23.225]    RIVA TNT2       (NV05)
                                            [    23.226]    GeForce 256     (NV10)
                                            [    23.226]    GeForce 2       (NV11, NV15)
                                            [    23.226]    GeForce 4MX     (NV17, NV18)
                                            [    23.226]    GeForce 3       (NV20)
                                            [    23.226]    GeForce 4Ti     (NV25, NV28)
                                            [    23.226]    GeForce FX      (NV3x)
                                            [    23.226]    GeForce 6       (NV4x)
                                            [    23.226]    GeForce 7       (G7x)
                                            [    23.226]    GeForce 8       (G8x)
                                            [    23.226]    GeForce GTX 200 (NVA0)
                                            [    23.226]    GeForce GTX 400 (NVC0)
                                            [    23.226] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
                                            [    23.226] (II) FBDEV: driver for framebuffer: fbdev
                                            [    23.226] (II) VESA: driver for VESA chipsets: vesa
                                            [    23.226] (II) systemd-logind: releasing fd for 226:0
                                            [    23.226] (EE) [drm] Failed to open DRM device for (null): -2
                                            [    23.226] (WW) Falling back to old probe method for modesetting
                                            [    23.226] (II) Loading sub module "fbdevhw"
                                            [    23.226] (II) LoadModule: "fbdevhw"
                                            [    23.226] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
                                            [    23.227] (II) Module fbdevhw: vendor="X.Org Foundation"
                                            [    23.227]    compiled for 1.19.2, module version = 0.0.2
                                            [    23.227]    ABI class: X.Org Video Driver, version 23.0
                                            [    23.227] (**) FBDEV(1): claimed PCI slot 0@0:2:0
                                            [    23.227] (II) FBDEV(1): using default device
                                            [    23.227] (WW) Falling back to old probe method for vesa
                                            [    23.227] (EE) Screen 0 deleted because of no matching config section.
                                            [    23.227] (II) UnloadModule: "modesetting"
                                            [    23.227] (II) FBDEV(0): Creating default Display subsection in Screen section
                                                "Default Screen Section" for depth/fbbpp 24/32
                                            [    23.227] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
                                            [    23.227] (==) FBDEV(0): RGB weight 888
                                            [    23.227] (==) FBDEV(0): Default visual is TrueColor
                                            [    23.227] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
                                            [    23.227] (II) FBDEV(0): hardware: EFI VGA (video memory: 1920kB)
                                            [    23.227] (II) FBDEV(0): checking modes against framebuffer device...
                                            [    23.227] (II) FBDEV(0): checking modes against monitor...
                                            [    23.227] (--) FBDEV(0): Virtual size is 800x600 (pitch 800)
                                            [    23.227] (**) FBDEV(0):  Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz
                                            [    23.227] (II) FBDEV(0): Modeline "current"x0.0   48.00  800 832 928 1024  600 604 608 624 -hsync -vsync -csync (46.9 kHz b)
                                            [    23.227] (==) FBDEV(0): DPI set to (96, 96)
                                            [    23.227] (II) Loading sub module "fb"
                                            [    23.227] (II) LoadModule: "fb"
                                            [    23.227] (II) Loading /usr/lib/xorg/modules/libfb.so
                                            [    23.228] (II) Module fb: vendor="X.Org Foundation"
                                            [    23.228]    compiled for 1.19.2, module version = 1.0.0
                                            [    23.228]    ABI class: X.Org ANSI C Emulation, version 0.4
                                            [    23.228] (**) FBDEV(0): using shadow framebuffer
                                            [    23.228] (II) Loading sub module "shadow"
                                            [    23.228] (II) LoadModule: "shadow"
                                            [    23.228] (II) Loading /usr/lib/xorg/modules/libshadow.so
                                            [    23.228] (II) Module shadow: vendor="X.Org Foundation"
                                            [    23.228]    compiled for 1.19.2, module version = 1.1.0
                                            [    23.228]    ABI class: X.Org ANSI C Emulation, version 0.4
                                            [    23.228] (II) UnloadModule: "vesa"
                                            [    23.228] (II) Unloading vesa
                                            [    23.228] (==) Depth 24 pixmap format is 32 bpp
                                            [    23.228] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
                                            [    23.230] (==) FBDEV(0): Backing store enabled
                                            [    23.231] (==) FBDEV(0): DPMS enabled
                                            [    23.231] (==) RandR enabled
                                            [    23.233] (II) SELinux: Disabled on system
                                            [    23.233] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
                                            [    23.283] (II) config/udev: Adding input device Power Button (/dev/input/event5)
                                            [    23.283] (**) Power Button: Applying InputClass "libinput keyboard catchall"
                                            [    23.283] (II) LoadModule: "libinput"
                                            [    23.283] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
                                            [    23.284] (II) Module libinput: vendor="X.Org Foundation"
                                            [    23.284]    compiled for 1.19.0, module version = 0.23.0
                                            [    23.284]    Module class: X.Org XInput Driver
                                            [    23.284]    ABI class: X.Org XInput driver, version 24.1
                                            [    23.284] (II) Using input driver 'libinput' for 'Power Button'
                                            [    23.285] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 22 paused 0
                                            [    23.285] (**) Power Button: always reports core events
                                            [    23.285] (**) Option "Device" "/dev/input/event5"
                                            [    23.285] (**) Option "_source" "server/udev"
                                            [    23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                            [    23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                            [    23.285] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event5"
                                            [    23.285] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
                                            [    23.285] (**) Option "xkb_model" "pc105"
                                            [    23.285] (**) Option "xkb_layout" "us"
                                            [    23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                            [    23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                            [    23.286] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
                                            [    23.286] (II) No input driver specified, ignoring this device.
                                            [    23.286] (II) This device may have been added with another device file.
                                            [    23.286] (II) config/udev: Adding input device Power Button (/dev/input/event4)
                                            [    23.286] (**) Power Button: Applying InputClass "libinput keyboard catchall"
                                            [    23.286] (II) Using input driver 'libinput' for 'Power Button'
                                            [    23.286] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 25 paused 0
                                            [    23.286] (**) Power Button: always reports core events
                                            [    23.286] (**) Option "Device" "/dev/input/event4"
                                            [    23.286] (**) Option "_source" "server/udev"
                                            [    23.286] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                            [    23.286] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                            [    23.286] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5/event4"
                                            [    23.286] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
                                            [    23.286] (**) Option "xkb_model" "pc105"
                                            [    23.286] (**) Option "xkb_layout" "us"
                                            [    23.287] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                            [    23.287] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                            [    23.287] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
                                            [    23.287] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
                                            [    23.287] (II) Using input driver 'libinput' for 'Sleep Button'
                                            [    23.287] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 26 paused 0
                                            [    23.287] (**) Sleep Button: always reports core events
                                            [    23.287] (**) Option "Device" "/dev/input/event3"
                                            [    23.287] (**) Option "_source" "server/udev"
                                            [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                            [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                            [    23.287] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4/event3"
                                            [    23.287] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
                                            [    23.287] (**) Option "xkb_model" "pc105"
                                            [    23.287] (**) Option "xkb_layout" "us"
                                            [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                            [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                            [    23.288] (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event9)
                                            [    23.288] (II) No input driver specified, ignoring this device.
                                            [    23.288] (II) This device may have been added with another device file.
                                            [    23.288] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event8)
                                            [    23.288] (II) No input driver specified, ignoring this device.
                                            [    23.288] (II) This device may have been added with another device file.
                                            [    23.288] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
                                            [    23.288] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
                                            [    23.288] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
                                            [    23.288] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 27 paused 0
                                            [    23.289] (**) AT Translated Set 2 keyboard: always reports core events
                                            [    23.289] (**) Option "Device" "/dev/input/event0"
                                            [    23.289] (**) Option "_source" "server/udev"
                                            [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                            [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                            [    23.289] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
                                            [    23.289] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
                                            [    23.289] (**) Option "xkb_model" "pc105"
                                            [    23.289] (**) Option "xkb_layout" "us"
                                            [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                            [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                            [    23.289] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event1)
                                            [    23.289] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
                                            [    23.289] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics TouchPad'
                                            [    23.290] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 28 paused 0
                                            [    23.290] (**) SynPS/2 Synaptics TouchPad: always reports core events
                                            [    23.290] (**) Option "Device" "/dev/input/event1"
                                            [    23.290] (**) Option "_source" "server/udev"
                                            [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                            [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                            [    23.290] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input2/event1"
                                            [    23.290] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 10)
                                            [    23.290] (**) Option "AccelerationScheme" "none"
                                            [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) selected scheme none/0
                                            [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
                                            [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
                                            [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                            [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                            [    23.290] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
                                            [    23.290] (II) No input driver specified, ignoring this device.
                                            [    23.290] (II) This device may have been added with another device file.
                                            [    23.290] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
                                            [    23.291] (II) No input driver specified, ignoring this device.
                                            [    23.291] (II) This device may have been added with another device file.
                                            [    23.291] (II) config/udev: Adding input device MSI WMI hotkeys (/dev/input/event7)
                                            [    23.291] (**) MSI WMI hotkeys: Applying InputClass "libinput keyboard catchall"
                                            [    23.291] (II) Using input driver 'libinput' for 'MSI WMI hotkeys'
                                            [    23.291] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 29 paused 0
                                            [    23.291] (**) MSI WMI hotkeys: always reports core events
                                            [    23.291] (**) Option "Device" "/dev/input/event7"
                                            [    23.291] (**) Option "_source" "server/udev"
                                            [    23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                            [    23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                            [    23.291] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event7"
                                            [    23.291] (II) XINPUT: Adding extended input device "MSI WMI hotkeys" (type: KEYBOARD, id 11)
                                            [    23.291] (**) Option "xkb_model" "pc105"
                                            [    23.291] (**) Option "xkb_layout" "us"
                                            [    23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                            [    23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                            [    36.511] (**) Option "fd" "22"
                                            [    36.511] (**) Option "fd" "25"
                                            [    36.511] (**) Option "fd" "26"
                                            [    36.512] (**) Option "fd" "27"
                                            [    36.512] (**) Option "fd" "28"
                                            [    36.512] (**) Option "fd" "29"
                                            [    36.515] (II) systemd-logind: got pause for 13:64
                                            [    36.515] (II) systemd-logind: got pause for 13:67
                                            [    36.515] (II) systemd-logind: got pause for 13:69
                                            [    36.515] (II) systemd-logind: got pause for 13:68
                                            [    36.515] (II) systemd-logind: got pause for 13:65
                                            [    36.515] (II) systemd-logind: got pause for 13:71
                                            [    55.096] (II) systemd-logind: got resume for 13:64
                                            [    55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                            [    55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                            [    55.120] (II) systemd-logind: got resume for 13:67
                                            [    55.121] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                            [    55.121] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                            [    55.140] (II) systemd-logind: got resume for 13:69
                                            [    55.141] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                            [    55.141] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                            [    55.156] (II) systemd-logind: got resume for 13:68
                                            [    55.157] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                            [    55.157] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                            [    55.176] (II) systemd-logind: got resume for 13:65
                                            [    55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                            [    55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                            [    55.192] (II) systemd-logind: got resume for 13:71
                                            [    55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                            [    55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                            [    57.379] (**) Option "fd" "26"
                                            [    57.379] (**) Option "fd" "27"
                                            [    57.379] (**) Option "fd" "25"
                                            [    57.379] (**) Option "fd" "22"
                                            [    57.379] (**) Option "fd" "28"
                                            [    57.380] (**) Option "fd" "29"
                                            [    57.383] (II) systemd-logind: got pause for 13:64
                                            [    57.383] (II) systemd-logind: got pause for 13:67
                                            [    57.383] (II) systemd-logind: got pause for 13:69
                                            [    57.383] (II) systemd-logind: got pause for 13:68
                                            [    57.383] (II) systemd-logind: got pause for 13:65
                                            [    57.383] (II) systemd-logind: got pause for 13:71
                                            

                                            And related messages from dmesg:

                                            .
                                            .
                                            [   20.051031] nvidia: loading out-of-tree module taints kernel.
                                            [   20.051034] nvidia: module license 'NVIDIA' taints kernel.
                                            [   20.051035] Disabling lock debugging due to kernel taint
                                            [   20.058235] nvidia-nvlink: Nvlink Core is being initialized, major device number 248
                                            [   20.058370] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
                                            [   20.058443] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
                                            [   20.058489] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts)
                                            [   20.069920] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  390.87  Tue Aug 21 16:16:14 PDT 2018
                                            [   20.075365] [drm] Initialized
                                            [   20.079182] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:00/PNP0C0D:00/input/input3
                                            [   20.079488] ACPI: Lid Switch [LID0]
                                            [   20.079844] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4
                                            [   20.079848] ACPI: Sleep Button [SLPB]
                                            [   20.079889] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
                                            [   20.079891] ACPI: Power Button [PWRB]
                                            [   20.079937] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
                                            [   20.079938] ACPI: Power Button [PWRF]
                                            [   20.087606] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
                                            [   20.087913] ACPI: AC Adapter [ADP1] (on-line)
                                            .
                                            .
                                            .
                                            [   22.621804] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
                                            [   22.622573] alx 0000:02:00.0 enp2s0: NIC Up: 100 Mbps Full
                                            [   22.622829] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
                                            [   23.754442] gnome-session-f[870]: segfault at 0 ip 00007f7cef889e19 sp 00007ffd529ea4e0 error 4 in libgtk-3.so.0.2200.11[7f7cef5a7000+700000]
                                            [   33.821642] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
                                            [   33.821643] Bluetooth: BNEP filters: protocol multicast
                                            [   33.821645] Bluetooth: BNEP socket layer initialized
                                            

                                            Do you have any idea what may be the problem?

                                            Update: If I wait long enough on black screen, I get a curser.

                                            share|improve this question

                                              1

                                              I have installed latest Debian Stretch on my MSI laptop and I want to install Nvidia proprietary drivers for my GTX 1060 graphics card.

                                              I followed this guide on Debian’s wiki: https://wiki.debian.org/NvidiaGraphicsDrivers.

                                              Here are the steps I followed on my fresh install:

                                              First I added stretch-backports and ‘contrib non-free’ postfix. My /etc/apt/sources.list dump:

                                              # 
                                              
                                              # deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main
                                              
                                              #deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main
                                              
                                              deb http://ftp.hu.debian.org/debian/ stretch main contrib non-free
                                              deb-src http://ftp.hu.debian.org/debian/ stretch main
                                              
                                              deb http://security.debian.org/debian-security stretch/updates main contrib non-free
                                              deb-src http://security.debian.org/debian-security stretch/updates main
                                              
                                              # stretch-updates, previously known as 'volatile'
                                              deb http://ftp.hu.debian.org/debian/ stretch-updates main contrib non-free
                                              deb-src http://ftp.hu.debian.org/debian/ stretch-updates main
                                              
                                              # stretch-backports
                                              deb http://httpredir.debian.org/debian stretch-backports main contrib non-free
                                              

                                              Then I ran the followings as root:

                                              $ dpkg --add-architecture i386
                                              $ apt-get update
                                              $ apt-get install build-essential
                                              $ apt-get install linux-headers-$(uname -r|sed 's/[^-]*-[^-]*-//')
                                              $ apt-get -t stretch-backports install nvidia-driver
                                              

                                              I rebooted the system but on boot where gnome should have started I see a black screen without a cursor. I do have access to other terminals. Here is my Xorg.0.log:

                                              [    23.138] (--) Log file renamed from "/var/log/Xorg.pid-823.log" to "/var/log/Xorg.0.log"
                                              [    23.140] 
                                              X.Org X Server 1.19.2
                                              Release Date: 2017-03-02
                                              [    23.140] X Protocol Version 11, Revision 0
                                              [    23.140] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
                                              [    23.140] Current Operating System: Linux zion 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
                                              [    23.140] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-8-amd64 root=UUID=79569e63-703c-4939-ae49-32f4997c9c72 ro quiet
                                              [    23.140] Build Date: 03 November 2018  03:09:11AM
                                              [    23.140] xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support) 
                                              [    23.140] Current version of pixman: 0.34.0
                                              [    23.140]    Before reporting problems, check http://wiki.x.org
                                                  to make sure that you have the latest version.
                                              [    23.140] Markers: (--) probed, (**) from config file, (==) default setting,
                                                  (++) from command line, (!!) notice, (II) informational,
                                                  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
                                              [    23.140] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 13 20:06:40 2019
                                              [    23.143] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
                                              [    23.145] (==) No Layout section.  Using the first Screen section.
                                              [    23.145] (==) No screen section available. Using defaults.
                                              [    23.145] (**) |-->Screen "Default Screen Section" (0)
                                              [    23.145] (**) |   |-->Monitor "<default monitor>"
                                              [    23.146] (==) No monitor specified for screen "Default Screen Section".
                                                  Using a default monitor configuration.
                                              [    23.146] (==) Automatically adding devices
                                              [    23.146] (==) Automatically enabling devices
                                              [    23.146] (==) Automatically adding GPU devices
                                              [    23.146] (==) Max clients allowed: 256, resource mask: 0x1fffff
                                              [    23.148] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
                                              [    23.148]    Entry deleted from font path.
                                              [    23.152] (==) FontPath set to:
                                                  /usr/share/fonts/X11/misc,
                                                  /usr/share/fonts/X11/100dpi/:unscaled,
                                                  /usr/share/fonts/X11/75dpi/:unscaled,
                                                  /usr/share/fonts/X11/Type1,
                                                  /usr/share/fonts/X11/100dpi,
                                                  /usr/share/fonts/X11/75dpi,
                                                  built-ins
                                              [    23.152] (**) ModulePath set to "/usr/lib/xorg/modules/linux,/usr/lib/xorg/modules"
                                              [    23.152] (II) The server relies on udev to provide the list of input devices.
                                                  If no devices become available, reconfigure udev or disable AutoAddDevices.
                                              [    23.152] (II) Loader magic: 0x555783fdbe00
                                              [    23.152] (II) Module ABI versions:
                                              [    23.152]    X.Org ANSI C Emulation: 0.4
                                              [    23.152]    X.Org Video Driver: 23.0
                                              [    23.152]    X.Org XInput driver : 24.1
                                              [    23.152]    X.Org Server Extension : 10.0
                                              [    23.154] (++) using VT number 1
                                              
                                              [    23.159] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
                                              [    23.159] (II) xfree86: Adding drm device (/dev/dri/card0)
                                              [    23.161] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
                                              [    23.165] (--) PCI:*(0:0:2:0) 8086:3e9b:1462:1223 rev 0, Mem @ 0xa2000000/16777216, 0x80000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
                                              [    23.165] (--) PCI: (0:1:0:0) 10de:1c20:1462:1223 rev 161, Mem @ 0xa3000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
                                              [    23.165] (II) LoadModule: "glx"
                                              [    23.167] (II) Loading /usr/lib/xorg/modules/linux/libglx.so
                                              [    23.215] (II) Module glx: vendor="NVIDIA Corporation"
                                              [    23.215]    compiled for 4.0.2, module version = 1.0.0
                                              [    23.215]    Module class: X.Org Server Extension
                                              [    23.215] (II) NVIDIA GLX Module  390.87  Tue Aug 21 16:10:56 PDT 2018
                                              [    23.216] (II) Applying OutputClass "nvidia" to /dev/dri/card0
                                              [    23.216]    loading driver: nvidia
                                              [    23.216] (==) Matched nvidia as autoconfigured driver 0
                                              [    23.216] (==) Matched nouveau as autoconfigured driver 1
                                              [    23.216] (==) Matched nv as autoconfigured driver 2
                                              [    23.216] (==) Matched modesetting as autoconfigured driver 3
                                              [    23.216] (==) Matched fbdev as autoconfigured driver 4
                                              [    23.216] (==) Matched vesa as autoconfigured driver 5
                                              [    23.216] (==) Assigned the driver to the xf86ConfigLayout
                                              [    23.216] (II) LoadModule: "nvidia"
                                              [    23.216] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
                                              [    23.221] (II) Module nvidia: vendor="NVIDIA Corporation"
                                              [    23.221]    compiled for 4.0.2, module version = 1.0.0
                                              [    23.221]    Module class: X.Org Video Driver
                                              [    23.221] (II) LoadModule: "nouveau"
                                              [    23.221] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
                                              [    23.223] (II) Module nouveau: vendor="X.Org Foundation"
                                              [    23.223]    compiled for 1.19.3, module version = 1.0.13
                                              [    23.223]    Module class: X.Org Video Driver
                                              [    23.223]    ABI class: X.Org Video Driver, version 23.0
                                              [    23.223] (II) LoadModule: "nv"
                                              [    23.223] (WW) Warning, couldn't open module nv
                                              [    23.223] (II) UnloadModule: "nv"
                                              [    23.223] (II) Unloading nv
                                              [    23.223] (EE) Failed to load module "nv" (module does not exist, 0)
                                              [    23.223] (II) LoadModule: "modesetting"
                                              [    23.223] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
                                              [    23.224] (II) Module modesetting: vendor="X.Org Foundation"
                                              [    23.224]    compiled for 1.19.2, module version = 1.19.2
                                              [    23.224]    Module class: X.Org Video Driver
                                              [    23.224]    ABI class: X.Org Video Driver, version 23.0
                                              [    23.224] (II) LoadModule: "fbdev"
                                              [    23.224] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
                                              [    23.224] (II) Module fbdev: vendor="X.Org Foundation"
                                              [    23.224]    compiled for 1.19.0, module version = 0.4.4
                                              [    23.224]    Module class: X.Org Video Driver
                                              [    23.224]    ABI class: X.Org Video Driver, version 23.0
                                              [    23.224] (II) LoadModule: "vesa"
                                              [    23.224] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
                                              [    23.225] (II) Module vesa: vendor="X.Org Foundation"
                                              [    23.225]    compiled for 1.19.0, module version = 2.3.4
                                              [    23.225]    Module class: X.Org Video Driver
                                              [    23.225]    ABI class: X.Org Video Driver, version 23.0
                                              [    23.225] (II) NVIDIA dlloader X Driver  390.87  Tue Aug 21 15:44:49 PDT 2018
                                              [    23.225] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
                                              [    23.225] (II) NOUVEAU driver Date:   Tue Sep 20 00:31:06 2016 -0400
                                              [    23.225] (II) NOUVEAU driver for NVIDIA chipset families :
                                              [    23.225]    RIVA TNT        (NV04)
                                              [    23.225]    RIVA TNT2       (NV05)
                                              [    23.226]    GeForce 256     (NV10)
                                              [    23.226]    GeForce 2       (NV11, NV15)
                                              [    23.226]    GeForce 4MX     (NV17, NV18)
                                              [    23.226]    GeForce 3       (NV20)
                                              [    23.226]    GeForce 4Ti     (NV25, NV28)
                                              [    23.226]    GeForce FX      (NV3x)
                                              [    23.226]    GeForce 6       (NV4x)
                                              [    23.226]    GeForce 7       (G7x)
                                              [    23.226]    GeForce 8       (G8x)
                                              [    23.226]    GeForce GTX 200 (NVA0)
                                              [    23.226]    GeForce GTX 400 (NVC0)
                                              [    23.226] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
                                              [    23.226] (II) FBDEV: driver for framebuffer: fbdev
                                              [    23.226] (II) VESA: driver for VESA chipsets: vesa
                                              [    23.226] (II) systemd-logind: releasing fd for 226:0
                                              [    23.226] (EE) [drm] Failed to open DRM device for (null): -2
                                              [    23.226] (WW) Falling back to old probe method for modesetting
                                              [    23.226] (II) Loading sub module "fbdevhw"
                                              [    23.226] (II) LoadModule: "fbdevhw"
                                              [    23.226] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
                                              [    23.227] (II) Module fbdevhw: vendor="X.Org Foundation"
                                              [    23.227]    compiled for 1.19.2, module version = 0.0.2
                                              [    23.227]    ABI class: X.Org Video Driver, version 23.0
                                              [    23.227] (**) FBDEV(1): claimed PCI slot 0@0:2:0
                                              [    23.227] (II) FBDEV(1): using default device
                                              [    23.227] (WW) Falling back to old probe method for vesa
                                              [    23.227] (EE) Screen 0 deleted because of no matching config section.
                                              [    23.227] (II) UnloadModule: "modesetting"
                                              [    23.227] (II) FBDEV(0): Creating default Display subsection in Screen section
                                                  "Default Screen Section" for depth/fbbpp 24/32
                                              [    23.227] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
                                              [    23.227] (==) FBDEV(0): RGB weight 888
                                              [    23.227] (==) FBDEV(0): Default visual is TrueColor
                                              [    23.227] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
                                              [    23.227] (II) FBDEV(0): hardware: EFI VGA (video memory: 1920kB)
                                              [    23.227] (II) FBDEV(0): checking modes against framebuffer device...
                                              [    23.227] (II) FBDEV(0): checking modes against monitor...
                                              [    23.227] (--) FBDEV(0): Virtual size is 800x600 (pitch 800)
                                              [    23.227] (**) FBDEV(0):  Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz
                                              [    23.227] (II) FBDEV(0): Modeline "current"x0.0   48.00  800 832 928 1024  600 604 608 624 -hsync -vsync -csync (46.9 kHz b)
                                              [    23.227] (==) FBDEV(0): DPI set to (96, 96)
                                              [    23.227] (II) Loading sub module "fb"
                                              [    23.227] (II) LoadModule: "fb"
                                              [    23.227] (II) Loading /usr/lib/xorg/modules/libfb.so
                                              [    23.228] (II) Module fb: vendor="X.Org Foundation"
                                              [    23.228]    compiled for 1.19.2, module version = 1.0.0
                                              [    23.228]    ABI class: X.Org ANSI C Emulation, version 0.4
                                              [    23.228] (**) FBDEV(0): using shadow framebuffer
                                              [    23.228] (II) Loading sub module "shadow"
                                              [    23.228] (II) LoadModule: "shadow"
                                              [    23.228] (II) Loading /usr/lib/xorg/modules/libshadow.so
                                              [    23.228] (II) Module shadow: vendor="X.Org Foundation"
                                              [    23.228]    compiled for 1.19.2, module version = 1.1.0
                                              [    23.228]    ABI class: X.Org ANSI C Emulation, version 0.4
                                              [    23.228] (II) UnloadModule: "vesa"
                                              [    23.228] (II) Unloading vesa
                                              [    23.228] (==) Depth 24 pixmap format is 32 bpp
                                              [    23.228] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
                                              [    23.230] (==) FBDEV(0): Backing store enabled
                                              [    23.231] (==) FBDEV(0): DPMS enabled
                                              [    23.231] (==) RandR enabled
                                              [    23.233] (II) SELinux: Disabled on system
                                              [    23.233] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
                                              [    23.283] (II) config/udev: Adding input device Power Button (/dev/input/event5)
                                              [    23.283] (**) Power Button: Applying InputClass "libinput keyboard catchall"
                                              [    23.283] (II) LoadModule: "libinput"
                                              [    23.283] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
                                              [    23.284] (II) Module libinput: vendor="X.Org Foundation"
                                              [    23.284]    compiled for 1.19.0, module version = 0.23.0
                                              [    23.284]    Module class: X.Org XInput Driver
                                              [    23.284]    ABI class: X.Org XInput driver, version 24.1
                                              [    23.284] (II) Using input driver 'libinput' for 'Power Button'
                                              [    23.285] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 22 paused 0
                                              [    23.285] (**) Power Button: always reports core events
                                              [    23.285] (**) Option "Device" "/dev/input/event5"
                                              [    23.285] (**) Option "_source" "server/udev"
                                              [    23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                              [    23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                              [    23.285] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event5"
                                              [    23.285] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
                                              [    23.285] (**) Option "xkb_model" "pc105"
                                              [    23.285] (**) Option "xkb_layout" "us"
                                              [    23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                              [    23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                              [    23.286] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
                                              [    23.286] (II) No input driver specified, ignoring this device.
                                              [    23.286] (II) This device may have been added with another device file.
                                              [    23.286] (II) config/udev: Adding input device Power Button (/dev/input/event4)
                                              [    23.286] (**) Power Button: Applying InputClass "libinput keyboard catchall"
                                              [    23.286] (II) Using input driver 'libinput' for 'Power Button'
                                              [    23.286] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 25 paused 0
                                              [    23.286] (**) Power Button: always reports core events
                                              [    23.286] (**) Option "Device" "/dev/input/event4"
                                              [    23.286] (**) Option "_source" "server/udev"
                                              [    23.286] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                              [    23.286] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                              [    23.286] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5/event4"
                                              [    23.286] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
                                              [    23.286] (**) Option "xkb_model" "pc105"
                                              [    23.286] (**) Option "xkb_layout" "us"
                                              [    23.287] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                              [    23.287] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                              [    23.287] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
                                              [    23.287] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
                                              [    23.287] (II) Using input driver 'libinput' for 'Sleep Button'
                                              [    23.287] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 26 paused 0
                                              [    23.287] (**) Sleep Button: always reports core events
                                              [    23.287] (**) Option "Device" "/dev/input/event3"
                                              [    23.287] (**) Option "_source" "server/udev"
                                              [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                              [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                              [    23.287] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4/event3"
                                              [    23.287] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
                                              [    23.287] (**) Option "xkb_model" "pc105"
                                              [    23.287] (**) Option "xkb_layout" "us"
                                              [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                              [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                              [    23.288] (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event9)
                                              [    23.288] (II) No input driver specified, ignoring this device.
                                              [    23.288] (II) This device may have been added with another device file.
                                              [    23.288] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event8)
                                              [    23.288] (II) No input driver specified, ignoring this device.
                                              [    23.288] (II) This device may have been added with another device file.
                                              [    23.288] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
                                              [    23.288] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
                                              [    23.288] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
                                              [    23.288] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 27 paused 0
                                              [    23.289] (**) AT Translated Set 2 keyboard: always reports core events
                                              [    23.289] (**) Option "Device" "/dev/input/event0"
                                              [    23.289] (**) Option "_source" "server/udev"
                                              [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                              [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                              [    23.289] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
                                              [    23.289] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
                                              [    23.289] (**) Option "xkb_model" "pc105"
                                              [    23.289] (**) Option "xkb_layout" "us"
                                              [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                              [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                              [    23.289] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event1)
                                              [    23.289] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
                                              [    23.289] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics TouchPad'
                                              [    23.290] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 28 paused 0
                                              [    23.290] (**) SynPS/2 Synaptics TouchPad: always reports core events
                                              [    23.290] (**) Option "Device" "/dev/input/event1"
                                              [    23.290] (**) Option "_source" "server/udev"
                                              [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                              [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                              [    23.290] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input2/event1"
                                              [    23.290] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 10)
                                              [    23.290] (**) Option "AccelerationScheme" "none"
                                              [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) selected scheme none/0
                                              [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
                                              [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
                                              [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                              [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                              [    23.290] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
                                              [    23.290] (II) No input driver specified, ignoring this device.
                                              [    23.290] (II) This device may have been added with another device file.
                                              [    23.290] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
                                              [    23.291] (II) No input driver specified, ignoring this device.
                                              [    23.291] (II) This device may have been added with another device file.
                                              [    23.291] (II) config/udev: Adding input device MSI WMI hotkeys (/dev/input/event7)
                                              [    23.291] (**) MSI WMI hotkeys: Applying InputClass "libinput keyboard catchall"
                                              [    23.291] (II) Using input driver 'libinput' for 'MSI WMI hotkeys'
                                              [    23.291] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 29 paused 0
                                              [    23.291] (**) MSI WMI hotkeys: always reports core events
                                              [    23.291] (**) Option "Device" "/dev/input/event7"
                                              [    23.291] (**) Option "_source" "server/udev"
                                              [    23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                              [    23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                              [    23.291] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event7"
                                              [    23.291] (II) XINPUT: Adding extended input device "MSI WMI hotkeys" (type: KEYBOARD, id 11)
                                              [    23.291] (**) Option "xkb_model" "pc105"
                                              [    23.291] (**) Option "xkb_layout" "us"
                                              [    23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                              [    23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                              [    36.511] (**) Option "fd" "22"
                                              [    36.511] (**) Option "fd" "25"
                                              [    36.511] (**) Option "fd" "26"
                                              [    36.512] (**) Option "fd" "27"
                                              [    36.512] (**) Option "fd" "28"
                                              [    36.512] (**) Option "fd" "29"
                                              [    36.515] (II) systemd-logind: got pause for 13:64
                                              [    36.515] (II) systemd-logind: got pause for 13:67
                                              [    36.515] (II) systemd-logind: got pause for 13:69
                                              [    36.515] (II) systemd-logind: got pause for 13:68
                                              [    36.515] (II) systemd-logind: got pause for 13:65
                                              [    36.515] (II) systemd-logind: got pause for 13:71
                                              [    55.096] (II) systemd-logind: got resume for 13:64
                                              [    55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                              [    55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                              [    55.120] (II) systemd-logind: got resume for 13:67
                                              [    55.121] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                              [    55.121] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                              [    55.140] (II) systemd-logind: got resume for 13:69
                                              [    55.141] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                              [    55.141] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                              [    55.156] (II) systemd-logind: got resume for 13:68
                                              [    55.157] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                              [    55.157] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                              [    55.176] (II) systemd-logind: got resume for 13:65
                                              [    55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                              [    55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                              [    55.192] (II) systemd-logind: got resume for 13:71
                                              [    55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                              [    55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                              [    57.379] (**) Option "fd" "26"
                                              [    57.379] (**) Option "fd" "27"
                                              [    57.379] (**) Option "fd" "25"
                                              [    57.379] (**) Option "fd" "22"
                                              [    57.379] (**) Option "fd" "28"
                                              [    57.380] (**) Option "fd" "29"
                                              [    57.383] (II) systemd-logind: got pause for 13:64
                                              [    57.383] (II) systemd-logind: got pause for 13:67
                                              [    57.383] (II) systemd-logind: got pause for 13:69
                                              [    57.383] (II) systemd-logind: got pause for 13:68
                                              [    57.383] (II) systemd-logind: got pause for 13:65
                                              [    57.383] (II) systemd-logind: got pause for 13:71
                                              

                                              And related messages from dmesg:

                                              .
                                              .
                                              [   20.051031] nvidia: loading out-of-tree module taints kernel.
                                              [   20.051034] nvidia: module license 'NVIDIA' taints kernel.
                                              [   20.051035] Disabling lock debugging due to kernel taint
                                              [   20.058235] nvidia-nvlink: Nvlink Core is being initialized, major device number 248
                                              [   20.058370] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
                                              [   20.058443] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
                                              [   20.058489] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts)
                                              [   20.069920] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  390.87  Tue Aug 21 16:16:14 PDT 2018
                                              [   20.075365] [drm] Initialized
                                              [   20.079182] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:00/PNP0C0D:00/input/input3
                                              [   20.079488] ACPI: Lid Switch [LID0]
                                              [   20.079844] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4
                                              [   20.079848] ACPI: Sleep Button [SLPB]
                                              [   20.079889] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
                                              [   20.079891] ACPI: Power Button [PWRB]
                                              [   20.079937] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
                                              [   20.079938] ACPI: Power Button [PWRF]
                                              [   20.087606] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
                                              [   20.087913] ACPI: AC Adapter [ADP1] (on-line)
                                              .
                                              .
                                              .
                                              [   22.621804] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
                                              [   22.622573] alx 0000:02:00.0 enp2s0: NIC Up: 100 Mbps Full
                                              [   22.622829] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
                                              [   23.754442] gnome-session-f[870]: segfault at 0 ip 00007f7cef889e19 sp 00007ffd529ea4e0 error 4 in libgtk-3.so.0.2200.11[7f7cef5a7000+700000]
                                              [   33.821642] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
                                              [   33.821643] Bluetooth: BNEP filters: protocol multicast
                                              [   33.821645] Bluetooth: BNEP socket layer initialized
                                              

                                              Do you have any idea what may be the problem?

                                              Update: If I wait long enough on black screen, I get a curser.

                                              share|improve this question

                                                1

                                                1

                                                1

                                                I have installed latest Debian Stretch on my MSI laptop and I want to install Nvidia proprietary drivers for my GTX 1060 graphics card.

                                                I followed this guide on Debian’s wiki: https://wiki.debian.org/NvidiaGraphicsDrivers.

                                                Here are the steps I followed on my fresh install:

                                                First I added stretch-backports and ‘contrib non-free’ postfix. My /etc/apt/sources.list dump:

                                                # 
                                                
                                                # deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main
                                                
                                                #deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main
                                                
                                                deb http://ftp.hu.debian.org/debian/ stretch main contrib non-free
                                                deb-src http://ftp.hu.debian.org/debian/ stretch main
                                                
                                                deb http://security.debian.org/debian-security stretch/updates main contrib non-free
                                                deb-src http://security.debian.org/debian-security stretch/updates main
                                                
                                                # stretch-updates, previously known as 'volatile'
                                                deb http://ftp.hu.debian.org/debian/ stretch-updates main contrib non-free
                                                deb-src http://ftp.hu.debian.org/debian/ stretch-updates main
                                                
                                                # stretch-backports
                                                deb http://httpredir.debian.org/debian stretch-backports main contrib non-free
                                                

                                                Then I ran the followings as root:

                                                $ dpkg --add-architecture i386
                                                $ apt-get update
                                                $ apt-get install build-essential
                                                $ apt-get install linux-headers-$(uname -r|sed 's/[^-]*-[^-]*-//')
                                                $ apt-get -t stretch-backports install nvidia-driver
                                                

                                                I rebooted the system but on boot where gnome should have started I see a black screen without a cursor. I do have access to other terminals. Here is my Xorg.0.log:

                                                [    23.138] (--) Log file renamed from "/var/log/Xorg.pid-823.log" to "/var/log/Xorg.0.log"
                                                [    23.140] 
                                                X.Org X Server 1.19.2
                                                Release Date: 2017-03-02
                                                [    23.140] X Protocol Version 11, Revision 0
                                                [    23.140] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
                                                [    23.140] Current Operating System: Linux zion 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
                                                [    23.140] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-8-amd64 root=UUID=79569e63-703c-4939-ae49-32f4997c9c72 ro quiet
                                                [    23.140] Build Date: 03 November 2018  03:09:11AM
                                                [    23.140] xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support) 
                                                [    23.140] Current version of pixman: 0.34.0
                                                [    23.140]    Before reporting problems, check http://wiki.x.org
                                                    to make sure that you have the latest version.
                                                [    23.140] Markers: (--) probed, (**) from config file, (==) default setting,
                                                    (++) from command line, (!!) notice, (II) informational,
                                                    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
                                                [    23.140] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 13 20:06:40 2019
                                                [    23.143] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
                                                [    23.145] (==) No Layout section.  Using the first Screen section.
                                                [    23.145] (==) No screen section available. Using defaults.
                                                [    23.145] (**) |-->Screen "Default Screen Section" (0)
                                                [    23.145] (**) |   |-->Monitor "<default monitor>"
                                                [    23.146] (==) No monitor specified for screen "Default Screen Section".
                                                    Using a default monitor configuration.
                                                [    23.146] (==) Automatically adding devices
                                                [    23.146] (==) Automatically enabling devices
                                                [    23.146] (==) Automatically adding GPU devices
                                                [    23.146] (==) Max clients allowed: 256, resource mask: 0x1fffff
                                                [    23.148] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
                                                [    23.148]    Entry deleted from font path.
                                                [    23.152] (==) FontPath set to:
                                                    /usr/share/fonts/X11/misc,
                                                    /usr/share/fonts/X11/100dpi/:unscaled,
                                                    /usr/share/fonts/X11/75dpi/:unscaled,
                                                    /usr/share/fonts/X11/Type1,
                                                    /usr/share/fonts/X11/100dpi,
                                                    /usr/share/fonts/X11/75dpi,
                                                    built-ins
                                                [    23.152] (**) ModulePath set to "/usr/lib/xorg/modules/linux,/usr/lib/xorg/modules"
                                                [    23.152] (II) The server relies on udev to provide the list of input devices.
                                                    If no devices become available, reconfigure udev or disable AutoAddDevices.
                                                [    23.152] (II) Loader magic: 0x555783fdbe00
                                                [    23.152] (II) Module ABI versions:
                                                [    23.152]    X.Org ANSI C Emulation: 0.4
                                                [    23.152]    X.Org Video Driver: 23.0
                                                [    23.152]    X.Org XInput driver : 24.1
                                                [    23.152]    X.Org Server Extension : 10.0
                                                [    23.154] (++) using VT number 1
                                                
                                                [    23.159] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
                                                [    23.159] (II) xfree86: Adding drm device (/dev/dri/card0)
                                                [    23.161] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
                                                [    23.165] (--) PCI:*(0:0:2:0) 8086:3e9b:1462:1223 rev 0, Mem @ 0xa2000000/16777216, 0x80000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
                                                [    23.165] (--) PCI: (0:1:0:0) 10de:1c20:1462:1223 rev 161, Mem @ 0xa3000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
                                                [    23.165] (II) LoadModule: "glx"
                                                [    23.167] (II) Loading /usr/lib/xorg/modules/linux/libglx.so
                                                [    23.215] (II) Module glx: vendor="NVIDIA Corporation"
                                                [    23.215]    compiled for 4.0.2, module version = 1.0.0
                                                [    23.215]    Module class: X.Org Server Extension
                                                [    23.215] (II) NVIDIA GLX Module  390.87  Tue Aug 21 16:10:56 PDT 2018
                                                [    23.216] (II) Applying OutputClass "nvidia" to /dev/dri/card0
                                                [    23.216]    loading driver: nvidia
                                                [    23.216] (==) Matched nvidia as autoconfigured driver 0
                                                [    23.216] (==) Matched nouveau as autoconfigured driver 1
                                                [    23.216] (==) Matched nv as autoconfigured driver 2
                                                [    23.216] (==) Matched modesetting as autoconfigured driver 3
                                                [    23.216] (==) Matched fbdev as autoconfigured driver 4
                                                [    23.216] (==) Matched vesa as autoconfigured driver 5
                                                [    23.216] (==) Assigned the driver to the xf86ConfigLayout
                                                [    23.216] (II) LoadModule: "nvidia"
                                                [    23.216] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
                                                [    23.221] (II) Module nvidia: vendor="NVIDIA Corporation"
                                                [    23.221]    compiled for 4.0.2, module version = 1.0.0
                                                [    23.221]    Module class: X.Org Video Driver
                                                [    23.221] (II) LoadModule: "nouveau"
                                                [    23.221] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
                                                [    23.223] (II) Module nouveau: vendor="X.Org Foundation"
                                                [    23.223]    compiled for 1.19.3, module version = 1.0.13
                                                [    23.223]    Module class: X.Org Video Driver
                                                [    23.223]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.223] (II) LoadModule: "nv"
                                                [    23.223] (WW) Warning, couldn't open module nv
                                                [    23.223] (II) UnloadModule: "nv"
                                                [    23.223] (II) Unloading nv
                                                [    23.223] (EE) Failed to load module "nv" (module does not exist, 0)
                                                [    23.223] (II) LoadModule: "modesetting"
                                                [    23.223] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
                                                [    23.224] (II) Module modesetting: vendor="X.Org Foundation"
                                                [    23.224]    compiled for 1.19.2, module version = 1.19.2
                                                [    23.224]    Module class: X.Org Video Driver
                                                [    23.224]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.224] (II) LoadModule: "fbdev"
                                                [    23.224] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
                                                [    23.224] (II) Module fbdev: vendor="X.Org Foundation"
                                                [    23.224]    compiled for 1.19.0, module version = 0.4.4
                                                [    23.224]    Module class: X.Org Video Driver
                                                [    23.224]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.224] (II) LoadModule: "vesa"
                                                [    23.224] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
                                                [    23.225] (II) Module vesa: vendor="X.Org Foundation"
                                                [    23.225]    compiled for 1.19.0, module version = 2.3.4
                                                [    23.225]    Module class: X.Org Video Driver
                                                [    23.225]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.225] (II) NVIDIA dlloader X Driver  390.87  Tue Aug 21 15:44:49 PDT 2018
                                                [    23.225] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
                                                [    23.225] (II) NOUVEAU driver Date:   Tue Sep 20 00:31:06 2016 -0400
                                                [    23.225] (II) NOUVEAU driver for NVIDIA chipset families :
                                                [    23.225]    RIVA TNT        (NV04)
                                                [    23.225]    RIVA TNT2       (NV05)
                                                [    23.226]    GeForce 256     (NV10)
                                                [    23.226]    GeForce 2       (NV11, NV15)
                                                [    23.226]    GeForce 4MX     (NV17, NV18)
                                                [    23.226]    GeForce 3       (NV20)
                                                [    23.226]    GeForce 4Ti     (NV25, NV28)
                                                [    23.226]    GeForce FX      (NV3x)
                                                [    23.226]    GeForce 6       (NV4x)
                                                [    23.226]    GeForce 7       (G7x)
                                                [    23.226]    GeForce 8       (G8x)
                                                [    23.226]    GeForce GTX 200 (NVA0)
                                                [    23.226]    GeForce GTX 400 (NVC0)
                                                [    23.226] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
                                                [    23.226] (II) FBDEV: driver for framebuffer: fbdev
                                                [    23.226] (II) VESA: driver for VESA chipsets: vesa
                                                [    23.226] (II) systemd-logind: releasing fd for 226:0
                                                [    23.226] (EE) [drm] Failed to open DRM device for (null): -2
                                                [    23.226] (WW) Falling back to old probe method for modesetting
                                                [    23.226] (II) Loading sub module "fbdevhw"
                                                [    23.226] (II) LoadModule: "fbdevhw"
                                                [    23.226] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
                                                [    23.227] (II) Module fbdevhw: vendor="X.Org Foundation"
                                                [    23.227]    compiled for 1.19.2, module version = 0.0.2
                                                [    23.227]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.227] (**) FBDEV(1): claimed PCI slot 0@0:2:0
                                                [    23.227] (II) FBDEV(1): using default device
                                                [    23.227] (WW) Falling back to old probe method for vesa
                                                [    23.227] (EE) Screen 0 deleted because of no matching config section.
                                                [    23.227] (II) UnloadModule: "modesetting"
                                                [    23.227] (II) FBDEV(0): Creating default Display subsection in Screen section
                                                    "Default Screen Section" for depth/fbbpp 24/32
                                                [    23.227] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
                                                [    23.227] (==) FBDEV(0): RGB weight 888
                                                [    23.227] (==) FBDEV(0): Default visual is TrueColor
                                                [    23.227] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
                                                [    23.227] (II) FBDEV(0): hardware: EFI VGA (video memory: 1920kB)
                                                [    23.227] (II) FBDEV(0): checking modes against framebuffer device...
                                                [    23.227] (II) FBDEV(0): checking modes against monitor...
                                                [    23.227] (--) FBDEV(0): Virtual size is 800x600 (pitch 800)
                                                [    23.227] (**) FBDEV(0):  Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz
                                                [    23.227] (II) FBDEV(0): Modeline "current"x0.0   48.00  800 832 928 1024  600 604 608 624 -hsync -vsync -csync (46.9 kHz b)
                                                [    23.227] (==) FBDEV(0): DPI set to (96, 96)
                                                [    23.227] (II) Loading sub module "fb"
                                                [    23.227] (II) LoadModule: "fb"
                                                [    23.227] (II) Loading /usr/lib/xorg/modules/libfb.so
                                                [    23.228] (II) Module fb: vendor="X.Org Foundation"
                                                [    23.228]    compiled for 1.19.2, module version = 1.0.0
                                                [    23.228]    ABI class: X.Org ANSI C Emulation, version 0.4
                                                [    23.228] (**) FBDEV(0): using shadow framebuffer
                                                [    23.228] (II) Loading sub module "shadow"
                                                [    23.228] (II) LoadModule: "shadow"
                                                [    23.228] (II) Loading /usr/lib/xorg/modules/libshadow.so
                                                [    23.228] (II) Module shadow: vendor="X.Org Foundation"
                                                [    23.228]    compiled for 1.19.2, module version = 1.1.0
                                                [    23.228]    ABI class: X.Org ANSI C Emulation, version 0.4
                                                [    23.228] (II) UnloadModule: "vesa"
                                                [    23.228] (II) Unloading vesa
                                                [    23.228] (==) Depth 24 pixmap format is 32 bpp
                                                [    23.228] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
                                                [    23.230] (==) FBDEV(0): Backing store enabled
                                                [    23.231] (==) FBDEV(0): DPMS enabled
                                                [    23.231] (==) RandR enabled
                                                [    23.233] (II) SELinux: Disabled on system
                                                [    23.233] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
                                                [    23.283] (II) config/udev: Adding input device Power Button (/dev/input/event5)
                                                [    23.283] (**) Power Button: Applying InputClass "libinput keyboard catchall"
                                                [    23.283] (II) LoadModule: "libinput"
                                                [    23.283] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
                                                [    23.284] (II) Module libinput: vendor="X.Org Foundation"
                                                [    23.284]    compiled for 1.19.0, module version = 0.23.0
                                                [    23.284]    Module class: X.Org XInput Driver
                                                [    23.284]    ABI class: X.Org XInput driver, version 24.1
                                                [    23.284] (II) Using input driver 'libinput' for 'Power Button'
                                                [    23.285] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 22 paused 0
                                                [    23.285] (**) Power Button: always reports core events
                                                [    23.285] (**) Option "Device" "/dev/input/event5"
                                                [    23.285] (**) Option "_source" "server/udev"
                                                [    23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                                [    23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                                [    23.285] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event5"
                                                [    23.285] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
                                                [    23.285] (**) Option "xkb_model" "pc105"
                                                [    23.285] (**) Option "xkb_layout" "us"
                                                [    23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                                [    23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                                [    23.286] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
                                                [    23.286] (II) No input driver specified, ignoring this device.
                                                [    23.286] (II) This device may have been added with another device file.
                                                [    23.286] (II) config/udev: Adding input device Power Button (/dev/input/event4)
                                                [    23.286] (**) Power Button: Applying InputClass "libinput keyboard catchall"
                                                [    23.286] (II) Using input driver 'libinput' for 'Power Button'
                                                [    23.286] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 25 paused 0
                                                [    23.286] (**) Power Button: always reports core events
                                                [    23.286] (**) Option "Device" "/dev/input/event4"
                                                [    23.286] (**) Option "_source" "server/udev"
                                                [    23.286] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                                [    23.286] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                                [    23.286] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5/event4"
                                                [    23.286] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
                                                [    23.286] (**) Option "xkb_model" "pc105"
                                                [    23.286] (**) Option "xkb_layout" "us"
                                                [    23.287] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                                [    23.287] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                                [    23.287] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
                                                [    23.287] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
                                                [    23.287] (II) Using input driver 'libinput' for 'Sleep Button'
                                                [    23.287] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 26 paused 0
                                                [    23.287] (**) Sleep Button: always reports core events
                                                [    23.287] (**) Option "Device" "/dev/input/event3"
                                                [    23.287] (**) Option "_source" "server/udev"
                                                [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                                [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                                [    23.287] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4/event3"
                                                [    23.287] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
                                                [    23.287] (**) Option "xkb_model" "pc105"
                                                [    23.287] (**) Option "xkb_layout" "us"
                                                [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                                [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                                [    23.288] (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event9)
                                                [    23.288] (II) No input driver specified, ignoring this device.
                                                [    23.288] (II) This device may have been added with another device file.
                                                [    23.288] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event8)
                                                [    23.288] (II) No input driver specified, ignoring this device.
                                                [    23.288] (II) This device may have been added with another device file.
                                                [    23.288] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
                                                [    23.288] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
                                                [    23.288] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
                                                [    23.288] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 27 paused 0
                                                [    23.289] (**) AT Translated Set 2 keyboard: always reports core events
                                                [    23.289] (**) Option "Device" "/dev/input/event0"
                                                [    23.289] (**) Option "_source" "server/udev"
                                                [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                                [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                                [    23.289] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
                                                [    23.289] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
                                                [    23.289] (**) Option "xkb_model" "pc105"
                                                [    23.289] (**) Option "xkb_layout" "us"
                                                [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                                [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                                [    23.289] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event1)
                                                [    23.289] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
                                                [    23.289] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics TouchPad'
                                                [    23.290] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 28 paused 0
                                                [    23.290] (**) SynPS/2 Synaptics TouchPad: always reports core events
                                                [    23.290] (**) Option "Device" "/dev/input/event1"
                                                [    23.290] (**) Option "_source" "server/udev"
                                                [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                                [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                                [    23.290] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input2/event1"
                                                [    23.290] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 10)
                                                [    23.290] (**) Option "AccelerationScheme" "none"
                                                [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) selected scheme none/0
                                                [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
                                                [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
                                                [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                                [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                                [    23.290] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
                                                [    23.290] (II) No input driver specified, ignoring this device.
                                                [    23.290] (II) This device may have been added with another device file.
                                                [    23.290] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
                                                [    23.291] (II) No input driver specified, ignoring this device.
                                                [    23.291] (II) This device may have been added with another device file.
                                                [    23.291] (II) config/udev: Adding input device MSI WMI hotkeys (/dev/input/event7)
                                                [    23.291] (**) MSI WMI hotkeys: Applying InputClass "libinput keyboard catchall"
                                                [    23.291] (II) Using input driver 'libinput' for 'MSI WMI hotkeys'
                                                [    23.291] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 29 paused 0
                                                [    23.291] (**) MSI WMI hotkeys: always reports core events
                                                [    23.291] (**) Option "Device" "/dev/input/event7"
                                                [    23.291] (**) Option "_source" "server/udev"
                                                [    23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                                [    23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                                [    23.291] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event7"
                                                [    23.291] (II) XINPUT: Adding extended input device "MSI WMI hotkeys" (type: KEYBOARD, id 11)
                                                [    23.291] (**) Option "xkb_model" "pc105"
                                                [    23.291] (**) Option "xkb_layout" "us"
                                                [    23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                                [    23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                                [    36.511] (**) Option "fd" "22"
                                                [    36.511] (**) Option "fd" "25"
                                                [    36.511] (**) Option "fd" "26"
                                                [    36.512] (**) Option "fd" "27"
                                                [    36.512] (**) Option "fd" "28"
                                                [    36.512] (**) Option "fd" "29"
                                                [    36.515] (II) systemd-logind: got pause for 13:64
                                                [    36.515] (II) systemd-logind: got pause for 13:67
                                                [    36.515] (II) systemd-logind: got pause for 13:69
                                                [    36.515] (II) systemd-logind: got pause for 13:68
                                                [    36.515] (II) systemd-logind: got pause for 13:65
                                                [    36.515] (II) systemd-logind: got pause for 13:71
                                                [    55.096] (II) systemd-logind: got resume for 13:64
                                                [    55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                                [    55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                                [    55.120] (II) systemd-logind: got resume for 13:67
                                                [    55.121] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                                [    55.121] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                                [    55.140] (II) systemd-logind: got resume for 13:69
                                                [    55.141] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                                [    55.141] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                                [    55.156] (II) systemd-logind: got resume for 13:68
                                                [    55.157] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                                [    55.157] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                                [    55.176] (II) systemd-logind: got resume for 13:65
                                                [    55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                                [    55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                                [    55.192] (II) systemd-logind: got resume for 13:71
                                                [    55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                                [    55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                                [    57.379] (**) Option "fd" "26"
                                                [    57.379] (**) Option "fd" "27"
                                                [    57.379] (**) Option "fd" "25"
                                                [    57.379] (**) Option "fd" "22"
                                                [    57.379] (**) Option "fd" "28"
                                                [    57.380] (**) Option "fd" "29"
                                                [    57.383] (II) systemd-logind: got pause for 13:64
                                                [    57.383] (II) systemd-logind: got pause for 13:67
                                                [    57.383] (II) systemd-logind: got pause for 13:69
                                                [    57.383] (II) systemd-logind: got pause for 13:68
                                                [    57.383] (II) systemd-logind: got pause for 13:65
                                                [    57.383] (II) systemd-logind: got pause for 13:71
                                                

                                                And related messages from dmesg:

                                                .
                                                .
                                                [   20.051031] nvidia: loading out-of-tree module taints kernel.
                                                [   20.051034] nvidia: module license 'NVIDIA' taints kernel.
                                                [   20.051035] Disabling lock debugging due to kernel taint
                                                [   20.058235] nvidia-nvlink: Nvlink Core is being initialized, major device number 248
                                                [   20.058370] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
                                                [   20.058443] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
                                                [   20.058489] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts)
                                                [   20.069920] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  390.87  Tue Aug 21 16:16:14 PDT 2018
                                                [   20.075365] [drm] Initialized
                                                [   20.079182] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:00/PNP0C0D:00/input/input3
                                                [   20.079488] ACPI: Lid Switch [LID0]
                                                [   20.079844] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4
                                                [   20.079848] ACPI: Sleep Button [SLPB]
                                                [   20.079889] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
                                                [   20.079891] ACPI: Power Button [PWRB]
                                                [   20.079937] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
                                                [   20.079938] ACPI: Power Button [PWRF]
                                                [   20.087606] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
                                                [   20.087913] ACPI: AC Adapter [ADP1] (on-line)
                                                .
                                                .
                                                .
                                                [   22.621804] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
                                                [   22.622573] alx 0000:02:00.0 enp2s0: NIC Up: 100 Mbps Full
                                                [   22.622829] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
                                                [   23.754442] gnome-session-f[870]: segfault at 0 ip 00007f7cef889e19 sp 00007ffd529ea4e0 error 4 in libgtk-3.so.0.2200.11[7f7cef5a7000+700000]
                                                [   33.821642] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
                                                [   33.821643] Bluetooth: BNEP filters: protocol multicast
                                                [   33.821645] Bluetooth: BNEP socket layer initialized
                                                

                                                Do you have any idea what may be the problem?

                                                Update: If I wait long enough on black screen, I get a curser.

                                                share|improve this question

                                                I have installed latest Debian Stretch on my MSI laptop and I want to install Nvidia proprietary drivers for my GTX 1060 graphics card.

                                                I followed this guide on Debian’s wiki: https://wiki.debian.org/NvidiaGraphicsDrivers.

                                                Here are the steps I followed on my fresh install:

                                                First I added stretch-backports and ‘contrib non-free’ postfix. My /etc/apt/sources.list dump:

                                                # 
                                                
                                                # deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main
                                                
                                                #deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main
                                                
                                                deb http://ftp.hu.debian.org/debian/ stretch main contrib non-free
                                                deb-src http://ftp.hu.debian.org/debian/ stretch main
                                                
                                                deb http://security.debian.org/debian-security stretch/updates main contrib non-free
                                                deb-src http://security.debian.org/debian-security stretch/updates main
                                                
                                                # stretch-updates, previously known as 'volatile'
                                                deb http://ftp.hu.debian.org/debian/ stretch-updates main contrib non-free
                                                deb-src http://ftp.hu.debian.org/debian/ stretch-updates main
                                                
                                                # stretch-backports
                                                deb http://httpredir.debian.org/debian stretch-backports main contrib non-free
                                                

                                                Then I ran the followings as root:

                                                $ dpkg --add-architecture i386
                                                $ apt-get update
                                                $ apt-get install build-essential
                                                $ apt-get install linux-headers-$(uname -r|sed 's/[^-]*-[^-]*-//')
                                                $ apt-get -t stretch-backports install nvidia-driver
                                                

                                                I rebooted the system but on boot where gnome should have started I see a black screen without a cursor. I do have access to other terminals. Here is my Xorg.0.log:

                                                [    23.138] (--) Log file renamed from "/var/log/Xorg.pid-823.log" to "/var/log/Xorg.0.log"
                                                [    23.140] 
                                                X.Org X Server 1.19.2
                                                Release Date: 2017-03-02
                                                [    23.140] X Protocol Version 11, Revision 0
                                                [    23.140] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
                                                [    23.140] Current Operating System: Linux zion 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
                                                [    23.140] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-8-amd64 root=UUID=79569e63-703c-4939-ae49-32f4997c9c72 ro quiet
                                                [    23.140] Build Date: 03 November 2018  03:09:11AM
                                                [    23.140] xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support) 
                                                [    23.140] Current version of pixman: 0.34.0
                                                [    23.140]    Before reporting problems, check http://wiki.x.org
                                                    to make sure that you have the latest version.
                                                [    23.140] Markers: (--) probed, (**) from config file, (==) default setting,
                                                    (++) from command line, (!!) notice, (II) informational,
                                                    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
                                                [    23.140] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 13 20:06:40 2019
                                                [    23.143] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
                                                [    23.145] (==) No Layout section.  Using the first Screen section.
                                                [    23.145] (==) No screen section available. Using defaults.
                                                [    23.145] (**) |-->Screen "Default Screen Section" (0)
                                                [    23.145] (**) |   |-->Monitor "<default monitor>"
                                                [    23.146] (==) No monitor specified for screen "Default Screen Section".
                                                    Using a default monitor configuration.
                                                [    23.146] (==) Automatically adding devices
                                                [    23.146] (==) Automatically enabling devices
                                                [    23.146] (==) Automatically adding GPU devices
                                                [    23.146] (==) Max clients allowed: 256, resource mask: 0x1fffff
                                                [    23.148] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
                                                [    23.148]    Entry deleted from font path.
                                                [    23.152] (==) FontPath set to:
                                                    /usr/share/fonts/X11/misc,
                                                    /usr/share/fonts/X11/100dpi/:unscaled,
                                                    /usr/share/fonts/X11/75dpi/:unscaled,
                                                    /usr/share/fonts/X11/Type1,
                                                    /usr/share/fonts/X11/100dpi,
                                                    /usr/share/fonts/X11/75dpi,
                                                    built-ins
                                                [    23.152] (**) ModulePath set to "/usr/lib/xorg/modules/linux,/usr/lib/xorg/modules"
                                                [    23.152] (II) The server relies on udev to provide the list of input devices.
                                                    If no devices become available, reconfigure udev or disable AutoAddDevices.
                                                [    23.152] (II) Loader magic: 0x555783fdbe00
                                                [    23.152] (II) Module ABI versions:
                                                [    23.152]    X.Org ANSI C Emulation: 0.4
                                                [    23.152]    X.Org Video Driver: 23.0
                                                [    23.152]    X.Org XInput driver : 24.1
                                                [    23.152]    X.Org Server Extension : 10.0
                                                [    23.154] (++) using VT number 1
                                                
                                                [    23.159] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
                                                [    23.159] (II) xfree86: Adding drm device (/dev/dri/card0)
                                                [    23.161] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
                                                [    23.165] (--) PCI:*(0:0:2:0) 8086:3e9b:1462:1223 rev 0, Mem @ 0xa2000000/16777216, 0x80000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
                                                [    23.165] (--) PCI: (0:1:0:0) 10de:1c20:1462:1223 rev 161, Mem @ 0xa3000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
                                                [    23.165] (II) LoadModule: "glx"
                                                [    23.167] (II) Loading /usr/lib/xorg/modules/linux/libglx.so
                                                [    23.215] (II) Module glx: vendor="NVIDIA Corporation"
                                                [    23.215]    compiled for 4.0.2, module version = 1.0.0
                                                [    23.215]    Module class: X.Org Server Extension
                                                [    23.215] (II) NVIDIA GLX Module  390.87  Tue Aug 21 16:10:56 PDT 2018
                                                [    23.216] (II) Applying OutputClass "nvidia" to /dev/dri/card0
                                                [    23.216]    loading driver: nvidia
                                                [    23.216] (==) Matched nvidia as autoconfigured driver 0
                                                [    23.216] (==) Matched nouveau as autoconfigured driver 1
                                                [    23.216] (==) Matched nv as autoconfigured driver 2
                                                [    23.216] (==) Matched modesetting as autoconfigured driver 3
                                                [    23.216] (==) Matched fbdev as autoconfigured driver 4
                                                [    23.216] (==) Matched vesa as autoconfigured driver 5
                                                [    23.216] (==) Assigned the driver to the xf86ConfigLayout
                                                [    23.216] (II) LoadModule: "nvidia"
                                                [    23.216] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
                                                [    23.221] (II) Module nvidia: vendor="NVIDIA Corporation"
                                                [    23.221]    compiled for 4.0.2, module version = 1.0.0
                                                [    23.221]    Module class: X.Org Video Driver
                                                [    23.221] (II) LoadModule: "nouveau"
                                                [    23.221] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
                                                [    23.223] (II) Module nouveau: vendor="X.Org Foundation"
                                                [    23.223]    compiled for 1.19.3, module version = 1.0.13
                                                [    23.223]    Module class: X.Org Video Driver
                                                [    23.223]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.223] (II) LoadModule: "nv"
                                                [    23.223] (WW) Warning, couldn't open module nv
                                                [    23.223] (II) UnloadModule: "nv"
                                                [    23.223] (II) Unloading nv
                                                [    23.223] (EE) Failed to load module "nv" (module does not exist, 0)
                                                [    23.223] (II) LoadModule: "modesetting"
                                                [    23.223] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
                                                [    23.224] (II) Module modesetting: vendor="X.Org Foundation"
                                                [    23.224]    compiled for 1.19.2, module version = 1.19.2
                                                [    23.224]    Module class: X.Org Video Driver
                                                [    23.224]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.224] (II) LoadModule: "fbdev"
                                                [    23.224] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
                                                [    23.224] (II) Module fbdev: vendor="X.Org Foundation"
                                                [    23.224]    compiled for 1.19.0, module version = 0.4.4
                                                [    23.224]    Module class: X.Org Video Driver
                                                [    23.224]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.224] (II) LoadModule: "vesa"
                                                [    23.224] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
                                                [    23.225] (II) Module vesa: vendor="X.Org Foundation"
                                                [    23.225]    compiled for 1.19.0, module version = 2.3.4
                                                [    23.225]    Module class: X.Org Video Driver
                                                [    23.225]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.225] (II) NVIDIA dlloader X Driver  390.87  Tue Aug 21 15:44:49 PDT 2018
                                                [    23.225] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
                                                [    23.225] (II) NOUVEAU driver Date:   Tue Sep 20 00:31:06 2016 -0400
                                                [    23.225] (II) NOUVEAU driver for NVIDIA chipset families :
                                                [    23.225]    RIVA TNT        (NV04)
                                                [    23.225]    RIVA TNT2       (NV05)
                                                [    23.226]    GeForce 256     (NV10)
                                                [    23.226]    GeForce 2       (NV11, NV15)
                                                [    23.226]    GeForce 4MX     (NV17, NV18)
                                                [    23.226]    GeForce 3       (NV20)
                                                [    23.226]    GeForce 4Ti     (NV25, NV28)
                                                [    23.226]    GeForce FX      (NV3x)
                                                [    23.226]    GeForce 6       (NV4x)
                                                [    23.226]    GeForce 7       (G7x)
                                                [    23.226]    GeForce 8       (G8x)
                                                [    23.226]    GeForce GTX 200 (NVA0)
                                                [    23.226]    GeForce GTX 400 (NVC0)
                                                [    23.226] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
                                                [    23.226] (II) FBDEV: driver for framebuffer: fbdev
                                                [    23.226] (II) VESA: driver for VESA chipsets: vesa
                                                [    23.226] (II) systemd-logind: releasing fd for 226:0
                                                [    23.226] (EE) [drm] Failed to open DRM device for (null): -2
                                                [    23.226] (WW) Falling back to old probe method for modesetting
                                                [    23.226] (II) Loading sub module "fbdevhw"
                                                [    23.226] (II) LoadModule: "fbdevhw"
                                                [    23.226] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
                                                [    23.227] (II) Module fbdevhw: vendor="X.Org Foundation"
                                                [    23.227]    compiled for 1.19.2, module version = 0.0.2
                                                [    23.227]    ABI class: X.Org Video Driver, version 23.0
                                                [    23.227] (**) FBDEV(1): claimed PCI slot 0@0:2:0
                                                [    23.227] (II) FBDEV(1): using default device
                                                [    23.227] (WW) Falling back to old probe method for vesa
                                                [    23.227] (EE) Screen 0 deleted because of no matching config section.
                                                [    23.227] (II) UnloadModule: "modesetting"
                                                [    23.227] (II) FBDEV(0): Creating default Display subsection in Screen section
                                                    "Default Screen Section" for depth/fbbpp 24/32
                                                [    23.227] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
                                                [    23.227] (==) FBDEV(0): RGB weight 888
                                                [    23.227] (==) FBDEV(0): Default visual is TrueColor
                                                [    23.227] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
                                                [    23.227] (II) FBDEV(0): hardware: EFI VGA (video memory: 1920kB)
                                                [    23.227] (II) FBDEV(0): checking modes against framebuffer device...
                                                [    23.227] (II) FBDEV(0): checking modes against monitor...
                                                [    23.227] (--) FBDEV(0): Virtual size is 800x600 (pitch 800)
                                                [    23.227] (**) FBDEV(0):  Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz
                                                [    23.227] (II) FBDEV(0): Modeline "current"x0.0   48.00  800 832 928 1024  600 604 608 624 -hsync -vsync -csync (46.9 kHz b)
                                                [    23.227] (==) FBDEV(0): DPI set to (96, 96)
                                                [    23.227] (II) Loading sub module "fb"
                                                [    23.227] (II) LoadModule: "fb"
                                                [    23.227] (II) Loading /usr/lib/xorg/modules/libfb.so
                                                [    23.228] (II) Module fb: vendor="X.Org Foundation"
                                                [    23.228]    compiled for 1.19.2, module version = 1.0.0
                                                [    23.228]    ABI class: X.Org ANSI C Emulation, version 0.4
                                                [    23.228] (**) FBDEV(0): using shadow framebuffer
                                                [    23.228] (II) Loading sub module "shadow"
                                                [    23.228] (II) LoadModule: "shadow"
                                                [    23.228] (II) Loading /usr/lib/xorg/modules/libshadow.so
                                                [    23.228] (II) Module shadow: vendor="X.Org Foundation"
                                                [    23.228]    compiled for 1.19.2, module version = 1.1.0
                                                [    23.228]    ABI class: X.Org ANSI C Emulation, version 0.4
                                                [    23.228] (II) UnloadModule: "vesa"
                                                [    23.228] (II) Unloading vesa
                                                [    23.228] (==) Depth 24 pixmap format is 32 bpp
                                                [    23.228] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
                                                [    23.230] (==) FBDEV(0): Backing store enabled
                                                [    23.231] (==) FBDEV(0): DPMS enabled
                                                [    23.231] (==) RandR enabled
                                                [    23.233] (II) SELinux: Disabled on system
                                                [    23.233] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
                                                [    23.283] (II) config/udev: Adding input device Power Button (/dev/input/event5)
                                                [    23.283] (**) Power Button: Applying InputClass "libinput keyboard catchall"
                                                [    23.283] (II) LoadModule: "libinput"
                                                [    23.283] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
                                                [    23.284] (II) Module libinput: vendor="X.Org Foundation"
                                                [    23.284]    compiled for 1.19.0, module version = 0.23.0
                                                [    23.284]    Module class: X.Org XInput Driver
                                                [    23.284]    ABI class: X.Org XInput driver, version 24.1
                                                [    23.284] (II) Using input driver 'libinput' for 'Power Button'
                                                [    23.285] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 22 paused 0
                                                [    23.285] (**) Power Button: always reports core events
                                                [    23.285] (**) Option "Device" "/dev/input/event5"
                                                [    23.285] (**) Option "_source" "server/udev"
                                                [    23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                                [    23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                                [    23.285] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event5"
                                                [    23.285] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
                                                [    23.285] (**) Option "xkb_model" "pc105"
                                                [    23.285] (**) Option "xkb_layout" "us"
                                                [    23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                                [    23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                                [    23.286] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
                                                [    23.286] (II) No input driver specified, ignoring this device.
                                                [    23.286] (II) This device may have been added with another device file.
                                                [    23.286] (II) config/udev: Adding input device Power Button (/dev/input/event4)
                                                [    23.286] (**) Power Button: Applying InputClass "libinput keyboard catchall"
                                                [    23.286] (II) Using input driver 'libinput' for 'Power Button'
                                                [    23.286] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 25 paused 0
                                                [    23.286] (**) Power Button: always reports core events
                                                [    23.286] (**) Option "Device" "/dev/input/event4"
                                                [    23.286] (**) Option "_source" "server/udev"
                                                [    23.286] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                                [    23.286] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                                [    23.286] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5/event4"
                                                [    23.286] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
                                                [    23.286] (**) Option "xkb_model" "pc105"
                                                [    23.286] (**) Option "xkb_layout" "us"
                                                [    23.287] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                                [    23.287] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                                [    23.287] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
                                                [    23.287] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
                                                [    23.287] (II) Using input driver 'libinput' for 'Sleep Button'
                                                [    23.287] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 26 paused 0
                                                [    23.287] (**) Sleep Button: always reports core events
                                                [    23.287] (**) Option "Device" "/dev/input/event3"
                                                [    23.287] (**) Option "_source" "server/udev"
                                                [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                                [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                                [    23.287] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4/event3"
                                                [    23.287] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
                                                [    23.287] (**) Option "xkb_model" "pc105"
                                                [    23.287] (**) Option "xkb_layout" "us"
                                                [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                                [    23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                                [    23.288] (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event9)
                                                [    23.288] (II) No input driver specified, ignoring this device.
                                                [    23.288] (II) This device may have been added with another device file.
                                                [    23.288] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event8)
                                                [    23.288] (II) No input driver specified, ignoring this device.
                                                [    23.288] (II) This device may have been added with another device file.
                                                [    23.288] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
                                                [    23.288] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
                                                [    23.288] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
                                                [    23.288] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 27 paused 0
                                                [    23.289] (**) AT Translated Set 2 keyboard: always reports core events
                                                [    23.289] (**) Option "Device" "/dev/input/event0"
                                                [    23.289] (**) Option "_source" "server/udev"
                                                [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                                [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                                [    23.289] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
                                                [    23.289] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
                                                [    23.289] (**) Option "xkb_model" "pc105"
                                                [    23.289] (**) Option "xkb_layout" "us"
                                                [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                                [    23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                                [    23.289] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event1)
                                                [    23.289] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
                                                [    23.289] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics TouchPad'
                                                [    23.290] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 28 paused 0
                                                [    23.290] (**) SynPS/2 Synaptics TouchPad: always reports core events
                                                [    23.290] (**) Option "Device" "/dev/input/event1"
                                                [    23.290] (**) Option "_source" "server/udev"
                                                [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                                [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                                [    23.290] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input2/event1"
                                                [    23.290] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 10)
                                                [    23.290] (**) Option "AccelerationScheme" "none"
                                                [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) selected scheme none/0
                                                [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
                                                [    23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
                                                [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                                [    23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                                [    23.290] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
                                                [    23.290] (II) No input driver specified, ignoring this device.
                                                [    23.290] (II) This device may have been added with another device file.
                                                [    23.290] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
                                                [    23.291] (II) No input driver specified, ignoring this device.
                                                [    23.291] (II) This device may have been added with another device file.
                                                [    23.291] (II) config/udev: Adding input device MSI WMI hotkeys (/dev/input/event7)
                                                [    23.291] (**) MSI WMI hotkeys: Applying InputClass "libinput keyboard catchall"
                                                [    23.291] (II) Using input driver 'libinput' for 'MSI WMI hotkeys'
                                                [    23.291] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 29 paused 0
                                                [    23.291] (**) MSI WMI hotkeys: always reports core events
                                                [    23.291] (**) Option "Device" "/dev/input/event7"
                                                [    23.291] (**) Option "_source" "server/udev"
                                                [    23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                                [    23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                                [    23.291] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event7"
                                                [    23.291] (II) XINPUT: Adding extended input device "MSI WMI hotkeys" (type: KEYBOARD, id 11)
                                                [    23.291] (**) Option "xkb_model" "pc105"
                                                [    23.291] (**) Option "xkb_layout" "us"
                                                [    23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                                [    23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                                [    36.511] (**) Option "fd" "22"
                                                [    36.511] (**) Option "fd" "25"
                                                [    36.511] (**) Option "fd" "26"
                                                [    36.512] (**) Option "fd" "27"
                                                [    36.512] (**) Option "fd" "28"
                                                [    36.512] (**) Option "fd" "29"
                                                [    36.515] (II) systemd-logind: got pause for 13:64
                                                [    36.515] (II) systemd-logind: got pause for 13:67
                                                [    36.515] (II) systemd-logind: got pause for 13:69
                                                [    36.515] (II) systemd-logind: got pause for 13:68
                                                [    36.515] (II) systemd-logind: got pause for 13:65
                                                [    36.515] (II) systemd-logind: got pause for 13:71
                                                [    55.096] (II) systemd-logind: got resume for 13:64
                                                [    55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
                                                [    55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
                                                [    55.120] (II) systemd-logind: got resume for 13:67
                                                [    55.121] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard
                                                [    55.121] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard
                                                [    55.140] (II) systemd-logind: got resume for 13:69
                                                [    55.141] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
                                                [    55.141] (II) input device 'Power Button', /dev/input/event5 is a keyboard
                                                [    55.156] (II) systemd-logind: got resume for 13:68
                                                [    55.157] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
                                                [    55.157] (II) input device 'Power Button', /dev/input/event4 is a keyboard
                                                [    55.176] (II) systemd-logind: got resume for 13:65
                                                [    55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad
                                                [    55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad
                                                [    55.192] (II) systemd-logind: got resume for 13:71
                                                [    55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard
                                                [    55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard
                                                [    57.379] (**) Option "fd" "26"
                                                [    57.379] (**) Option "fd" "27"
                                                [    57.379] (**) Option "fd" "25"
                                                [    57.379] (**) Option "fd" "22"
                                                [    57.379] (**) Option "fd" "28"
                                                [    57.380] (**) Option "fd" "29"
                                                [    57.383] (II) systemd-logind: got pause for 13:64
                                                [    57.383] (II) systemd-logind: got pause for 13:67
                                                [    57.383] (II) systemd-logind: got pause for 13:69
                                                [    57.383] (II) systemd-logind: got pause for 13:68
                                                [    57.383] (II) systemd-logind: got pause for 13:65
                                                [    57.383] (II) systemd-logind: got pause for 13:71
                                                

                                                And related messages from dmesg:

                                                .
                                                .
                                                [   20.051031] nvidia: loading out-of-tree module taints kernel.
                                                [   20.051034] nvidia: module license 'NVIDIA' taints kernel.
                                                [   20.051035] Disabling lock debugging due to kernel taint
                                                [   20.058235] nvidia-nvlink: Nvlink Core is being initialized, major device number 248
                                                [   20.058370] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
                                                [   20.058443] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
                                                [   20.058489] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts)
                                                [   20.069920] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  390.87  Tue Aug 21 16:16:14 PDT 2018
                                                [   20.075365] [drm] Initialized
                                                [   20.079182] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:00/PNP0C0D:00/input/input3
                                                [   20.079488] ACPI: Lid Switch [LID0]
                                                [   20.079844] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4
                                                [   20.079848] ACPI: Sleep Button [SLPB]
                                                [   20.079889] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
                                                [   20.079891] ACPI: Power Button [PWRB]
                                                [   20.079937] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
                                                [   20.079938] ACPI: Power Button [PWRF]
                                                [   20.087606] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
                                                [   20.087913] ACPI: AC Adapter [ADP1] (on-line)
                                                .
                                                .
                                                .
                                                [   22.621804] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
                                                [   22.622573] alx 0000:02:00.0 enp2s0: NIC Up: 100 Mbps Full
                                                [   22.622829] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
                                                [   23.754442] gnome-session-f[870]: segfault at 0 ip 00007f7cef889e19 sp 00007ffd529ea4e0 error 4 in libgtk-3.so.0.2200.11[7f7cef5a7000+700000]
                                                [   33.821642] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
                                                [   33.821643] Bluetooth: BNEP filters: protocol multicast
                                                [   33.821645] Bluetooth: BNEP socket layer initialized
                                                

                                                Do you have any idea what may be the problem?

                                                Update: If I wait long enough on black screen, I get a curser.

                                                debian xorg drivers nvidia

                                                share|improve this question

                                                share|improve this question

                                                share|improve this question

                                                share|improve this question

                                                edited Feb 13 at 18:35

                                                paddlesteamer

                                                asked Feb 13 at 17:47

                                                paddlesteamerpaddlesteamer

                                                62

                                                62

                                                    1 Answer
                                                    1

                                                    active

                                                    oldest

                                                    votes

                                                    0

                                                    I ran into this problem on Manjaro and it was caused by a problem with ACPI. In order to get my laptop to boot to the desktop, I had to add the following kernel parameter:

                                                    acpi_rev_override=5
                                                    

                                                    After I added this parameter, my system booted fine using the nVidia driver.

                                                    share|improve this answer

                                                    • I think I don’t have any problem related to ACPI. Nevertheless, I tried it but nothing is changed.

                                                      – paddlesteamer
                                                      Feb 13 at 18:12

                                                    • The only other thing I can see is that the Nouveau driver is loading. In some distros, this has been known to cause issues with the nVidia driver loading. you might want to try disabling it on start by trying this kernel parameter: modprobe.blacklist=nouveau If that does not work, I am sorry.

                                                      – Mark Lines
                                                      Feb 13 at 18:19

                                                    • I agree with the above comment, but also wish to add that you should reconfigure X after that.

                                                      – Michael Prokopec
                                                      Feb 13 at 21:36

                                                    • Actually nouveau is blacklisted. When I do apt-get install nvidia-driver nouveau is added to blacklist and I can confirm that nouveau is not loaded with my lsmod output.

                                                      – paddlesteamer
                                                      Feb 13 at 22:23

                                                    Your Answer

                                                    StackExchange.ready(function() {
                                                    var channelOptions = {
                                                    tags: “”.split(” “),
                                                    id: “106”
                                                    };
                                                    initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                                    StackExchange.using(“externalEditor”, function() {
                                                    // Have to fire editor after snippets, if snippets enabled
                                                    if (StackExchange.settings.snippets.snippetsEnabled) {
                                                    StackExchange.using(“snippets”, function() {
                                                    createEditor();
                                                    });
                                                    }
                                                    else {
                                                    createEditor();
                                                    }
                                                    });

                                                    function createEditor() {
                                                    StackExchange.prepareEditor({
                                                    heartbeatType: ‘answer’,
                                                    autoActivateHeartbeat: false,
                                                    convertImagesToLinks: false,
                                                    noModals: true,
                                                    showLowRepImageUploadWarning: true,
                                                    reputationToPostImages: null,
                                                    bindNavPrevention: true,
                                                    postfix: “”,
                                                    imageUploader: {
                                                    brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                                    contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                                    allowUrls: true
                                                    },
                                                    onDemand: true,
                                                    discardSelector: “.discard-answer”
                                                    ,immediatelyShowMarkdownHelp:true
                                                    });

                                                    }
                                                    });

                                                    draft saved
                                                    draft discarded

                                                    StackExchange.ready(
                                                    function () {
                                                    StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f500446%2fblack-screen-after-installing-nvidia-drivers-on-debian-stretch%23new-answer’, ‘question_page’);
                                                    }
                                                    );

                                                    Post as a guest

                                                    Required, but never shown

                                                    1 Answer
                                                    1

                                                    active

                                                    oldest

                                                    votes

                                                    1 Answer
                                                    1

                                                    active

                                                    oldest

                                                    votes

                                                    active

                                                    oldest

                                                    votes

                                                    active

                                                    oldest

                                                    votes

                                                    0

                                                    I ran into this problem on Manjaro and it was caused by a problem with ACPI. In order to get my laptop to boot to the desktop, I had to add the following kernel parameter:

                                                    acpi_rev_override=5
                                                    

                                                    After I added this parameter, my system booted fine using the nVidia driver.

                                                    share|improve this answer

                                                    • I think I don’t have any problem related to ACPI. Nevertheless, I tried it but nothing is changed.

                                                      – paddlesteamer
                                                      Feb 13 at 18:12

                                                    • The only other thing I can see is that the Nouveau driver is loading. In some distros, this has been known to cause issues with the nVidia driver loading. you might want to try disabling it on start by trying this kernel parameter: modprobe.blacklist=nouveau If that does not work, I am sorry.

                                                      – Mark Lines
                                                      Feb 13 at 18:19

                                                    • I agree with the above comment, but also wish to add that you should reconfigure X after that.

                                                      – Michael Prokopec
                                                      Feb 13 at 21:36

                                                    • Actually nouveau is blacklisted. When I do apt-get install nvidia-driver nouveau is added to blacklist and I can confirm that nouveau is not loaded with my lsmod output.

                                                      – paddlesteamer
                                                      Feb 13 at 22:23

                                                    0

                                                    I ran into this problem on Manjaro and it was caused by a problem with ACPI. In order to get my laptop to boot to the desktop, I had to add the following kernel parameter:

                                                    acpi_rev_override=5
                                                    

                                                    After I added this parameter, my system booted fine using the nVidia driver.

                                                    share|improve this answer

                                                    • I think I don’t have any problem related to ACPI. Nevertheless, I tried it but nothing is changed.

                                                      – paddlesteamer
                                                      Feb 13 at 18:12

                                                    • The only other thing I can see is that the Nouveau driver is loading. In some distros, this has been known to cause issues with the nVidia driver loading. you might want to try disabling it on start by trying this kernel parameter: modprobe.blacklist=nouveau If that does not work, I am sorry.

                                                      – Mark Lines
                                                      Feb 13 at 18:19

                                                    • I agree with the above comment, but also wish to add that you should reconfigure X after that.

                                                      – Michael Prokopec
                                                      Feb 13 at 21:36

                                                    • Actually nouveau is blacklisted. When I do apt-get install nvidia-driver nouveau is added to blacklist and I can confirm that nouveau is not loaded with my lsmod output.

                                                      – paddlesteamer
                                                      Feb 13 at 22:23

                                                    0

                                                    0

                                                    0

                                                    I ran into this problem on Manjaro and it was caused by a problem with ACPI. In order to get my laptop to boot to the desktop, I had to add the following kernel parameter:

                                                    acpi_rev_override=5
                                                    

                                                    After I added this parameter, my system booted fine using the nVidia driver.

                                                    share|improve this answer

                                                    I ran into this problem on Manjaro and it was caused by a problem with ACPI. In order to get my laptop to boot to the desktop, I had to add the following kernel parameter:

                                                    acpi_rev_override=5
                                                    

                                                    After I added this parameter, my system booted fine using the nVidia driver.

                                                    share|improve this answer

                                                    share|improve this answer

                                                    share|improve this answer

                                                    answered Feb 13 at 17:57

                                                    Mark LinesMark Lines

                                                    12

                                                    12

                                                    • I think I don’t have any problem related to ACPI. Nevertheless, I tried it but nothing is changed.

                                                      – paddlesteamer
                                                      Feb 13 at 18:12

                                                    • The only other thing I can see is that the Nouveau driver is loading. In some distros, this has been known to cause issues with the nVidia driver loading. you might want to try disabling it on start by trying this kernel parameter: modprobe.blacklist=nouveau If that does not work, I am sorry.

                                                      – Mark Lines
                                                      Feb 13 at 18:19

                                                    • I agree with the above comment, but also wish to add that you should reconfigure X after that.

                                                      – Michael Prokopec
                                                      Feb 13 at 21:36

                                                    • Actually nouveau is blacklisted. When I do apt-get install nvidia-driver nouveau is added to blacklist and I can confirm that nouveau is not loaded with my lsmod output.

                                                      – paddlesteamer
                                                      Feb 13 at 22:23

                                                    • I think I don’t have any problem related to ACPI. Nevertheless, I tried it but nothing is changed.

                                                      – paddlesteamer
                                                      Feb 13 at 18:12

                                                    • The only other thing I can see is that the Nouveau driver is loading. In some distros, this has been known to cause issues with the nVidia driver loading. you might want to try disabling it on start by trying this kernel parameter: modprobe.blacklist=nouveau If that does not work, I am sorry.

                                                      – Mark Lines
                                                      Feb 13 at 18:19

                                                    • I agree with the above comment, but also wish to add that you should reconfigure X after that.

                                                      – Michael Prokopec
                                                      Feb 13 at 21:36

                                                    • Actually nouveau is blacklisted. When I do apt-get install nvidia-driver nouveau is added to blacklist and I can confirm that nouveau is not loaded with my lsmod output.

                                                      – paddlesteamer
                                                      Feb 13 at 22:23

                                                    I think I don’t have any problem related to ACPI. Nevertheless, I tried it but nothing is changed.

                                                    – paddlesteamer
                                                    Feb 13 at 18:12

                                                    I think I don’t have any problem related to ACPI. Nevertheless, I tried it but nothing is changed.

                                                    – paddlesteamer
                                                    Feb 13 at 18:12

                                                    The only other thing I can see is that the Nouveau driver is loading. In some distros, this has been known to cause issues with the nVidia driver loading. you might want to try disabling it on start by trying this kernel parameter: modprobe.blacklist=nouveau If that does not work, I am sorry.

                                                    – Mark Lines
                                                    Feb 13 at 18:19

                                                    The only other thing I can see is that the Nouveau driver is loading. In some distros, this has been known to cause issues with the nVidia driver loading. you might want to try disabling it on start by trying this kernel parameter: modprobe.blacklist=nouveau If that does not work, I am sorry.

                                                    – Mark Lines
                                                    Feb 13 at 18:19

                                                    I agree with the above comment, but also wish to add that you should reconfigure X after that.

                                                    – Michael Prokopec
                                                    Feb 13 at 21:36

                                                    I agree with the above comment, but also wish to add that you should reconfigure X after that.

                                                    – Michael Prokopec
                                                    Feb 13 at 21:36

                                                    Actually nouveau is blacklisted. When I do apt-get install nvidia-driver nouveau is added to blacklist and I can confirm that nouveau is not loaded with my lsmod output.

                                                    – paddlesteamer
                                                    Feb 13 at 22:23

                                                    Actually nouveau is blacklisted. When I do apt-get install nvidia-driver nouveau is added to blacklist and I can confirm that nouveau is not loaded with my lsmod output.

                                                    – paddlesteamer
                                                    Feb 13 at 22:23

                                                    draft saved
                                                    draft discarded

                                                    Thanks for contributing an answer to Unix & Linux Stack Exchange!

                                                    • Please be sure to answer the question. Provide details and share your research!

                                                    But avoid

                                                    • Asking for help, clarification, or responding to other answers.
                                                    • Making statements based on opinion; back them up with references or personal experience.

                                                    To learn more, see our tips on writing great answers.

                                                    draft saved

                                                    draft discarded

                                                    StackExchange.ready(
                                                    function () {
                                                    StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f500446%2fblack-screen-after-installing-nvidia-drivers-on-debian-stretch%23new-answer’, ‘question_page’);
                                                    }
                                                    );

                                                    Post as a guest

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    How do I find the video memory region(s) representing what’s on my screen, from within the Linux kernel?

                                                    The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                                    0

                                                    About 5-20 times a day I am presented with brief visual glitches and heisenbugs caused by race conditions that only occur under high I/O load. These disappear off the screen far too quickly for me to grab a camera in time, so I am looking to find/build a screenshotting/screen-recording tool that acts/responds with the lowest possible delay after I press a hotkey/shortcut.

                                                    Critically, this tool’s high-responsiveness needs to be negligibly (ideally not at all) impacted by high I/O activity, like 10-second load averages of 20-40.

                                                    A fair argument could be made about loading PREEMPT_RT and running Xorg and a homemade screenshot dæmon as realtime. This would work… except for the bit about running X realtime; I actually do want to get work done on my computer. 🙂

                                                    Thing is, I can confidently run any code I like in realtime on my computer, just by putting it inside the Linux kernel. So, kernel module time!! To reiterate my question,

                                                    How do I find, access and grok the memory region(s) representing the pixels on my screen, all from within a Linux kernel module?

                                                    I’ve found that trying to read /dev/fb0 while X is running just produces a black image, so that apparently won’t work.

                                                    Unfortunately https://dri.freedesktop.org/docs/drm/gpu/index.html doesn’t show anything obviously related to framebuffer read-back, but I have no experience with this API, so I don’t really know what I’m looking for.

                                                    I accept that driver-specific code will likely be needed (since there’s unlikely a driver-agnostic canonical spot in memory representing what’s actually on screen), and this fine. I’m using an Intel-GPU-based machine at the moment, and I am happy to start specifically coding for that.

                                                    FWIW, I asked a differently-worded version of this question just under two years ago. That question only attracted one comment about HDCP and was never answered, but as I am still dealing with this problem up to 20 times a day even two years later, I’m having another go.

                                                    (My current approach (scrot launched by i3‘s hotkey binder) very often takes up to 20 (!!) seconds to take a single screenshot on systems experiencing high I/O load.)

                                                    share|improve this question

                                                    • It may depend on what video driver and kernel sub-system you are using. Running X.org 2D or 3D acceleration or simple frame buffer? Places like /dev/dri /dev/fbx /dev/mem /dev/nvidia0 and others.

                                                      – jc__
                                                      Feb 12 at 16:03

                                                    • @jc__: I’m using the intel driver – as I noted – and presume this provides 2D and basic 3D accel. I’ve already had a look at the DRI docs. I noted that /dev/fb0 produced a black image when X is running. I am genuinely curious, do you think /dev/mem might include VRAM? (That would be awesome.) I don’t have an Nvidia GPU.

                                                      – i336_
                                                      Feb 12 at 22:48

                                                    • @jc__: Genuinely appreciate the assistance

                                                      – i336_
                                                      Feb 12 at 22:48

                                                    0

                                                    About 5-20 times a day I am presented with brief visual glitches and heisenbugs caused by race conditions that only occur under high I/O load. These disappear off the screen far too quickly for me to grab a camera in time, so I am looking to find/build a screenshotting/screen-recording tool that acts/responds with the lowest possible delay after I press a hotkey/shortcut.

                                                    Critically, this tool’s high-responsiveness needs to be negligibly (ideally not at all) impacted by high I/O activity, like 10-second load averages of 20-40.

                                                    A fair argument could be made about loading PREEMPT_RT and running Xorg and a homemade screenshot dæmon as realtime. This would work… except for the bit about running X realtime; I actually do want to get work done on my computer. 🙂

                                                    Thing is, I can confidently run any code I like in realtime on my computer, just by putting it inside the Linux kernel. So, kernel module time!! To reiterate my question,

                                                    How do I find, access and grok the memory region(s) representing the pixels on my screen, all from within a Linux kernel module?

                                                    I’ve found that trying to read /dev/fb0 while X is running just produces a black image, so that apparently won’t work.

                                                    Unfortunately https://dri.freedesktop.org/docs/drm/gpu/index.html doesn’t show anything obviously related to framebuffer read-back, but I have no experience with this API, so I don’t really know what I’m looking for.

                                                    I accept that driver-specific code will likely be needed (since there’s unlikely a driver-agnostic canonical spot in memory representing what’s actually on screen), and this fine. I’m using an Intel-GPU-based machine at the moment, and I am happy to start specifically coding for that.

                                                    FWIW, I asked a differently-worded version of this question just under two years ago. That question only attracted one comment about HDCP and was never answered, but as I am still dealing with this problem up to 20 times a day even two years later, I’m having another go.

                                                    (My current approach (scrot launched by i3‘s hotkey binder) very often takes up to 20 (!!) seconds to take a single screenshot on systems experiencing high I/O load.)

                                                    share|improve this question

                                                    • It may depend on what video driver and kernel sub-system you are using. Running X.org 2D or 3D acceleration or simple frame buffer? Places like /dev/dri /dev/fbx /dev/mem /dev/nvidia0 and others.

                                                      – jc__
                                                      Feb 12 at 16:03

                                                    • @jc__: I’m using the intel driver – as I noted – and presume this provides 2D and basic 3D accel. I’ve already had a look at the DRI docs. I noted that /dev/fb0 produced a black image when X is running. I am genuinely curious, do you think /dev/mem might include VRAM? (That would be awesome.) I don’t have an Nvidia GPU.

                                                      – i336_
                                                      Feb 12 at 22:48

                                                    • @jc__: Genuinely appreciate the assistance

                                                      – i336_
                                                      Feb 12 at 22:48

                                                    0

                                                    0

                                                    0

                                                    About 5-20 times a day I am presented with brief visual glitches and heisenbugs caused by race conditions that only occur under high I/O load. These disappear off the screen far too quickly for me to grab a camera in time, so I am looking to find/build a screenshotting/screen-recording tool that acts/responds with the lowest possible delay after I press a hotkey/shortcut.

                                                    Critically, this tool’s high-responsiveness needs to be negligibly (ideally not at all) impacted by high I/O activity, like 10-second load averages of 20-40.

                                                    A fair argument could be made about loading PREEMPT_RT and running Xorg and a homemade screenshot dæmon as realtime. This would work… except for the bit about running X realtime; I actually do want to get work done on my computer. 🙂

                                                    Thing is, I can confidently run any code I like in realtime on my computer, just by putting it inside the Linux kernel. So, kernel module time!! To reiterate my question,

                                                    How do I find, access and grok the memory region(s) representing the pixels on my screen, all from within a Linux kernel module?

                                                    I’ve found that trying to read /dev/fb0 while X is running just produces a black image, so that apparently won’t work.

                                                    Unfortunately https://dri.freedesktop.org/docs/drm/gpu/index.html doesn’t show anything obviously related to framebuffer read-back, but I have no experience with this API, so I don’t really know what I’m looking for.

                                                    I accept that driver-specific code will likely be needed (since there’s unlikely a driver-agnostic canonical spot in memory representing what’s actually on screen), and this fine. I’m using an Intel-GPU-based machine at the moment, and I am happy to start specifically coding for that.

                                                    FWIW, I asked a differently-worded version of this question just under two years ago. That question only attracted one comment about HDCP and was never answered, but as I am still dealing with this problem up to 20 times a day even two years later, I’m having another go.

                                                    (My current approach (scrot launched by i3‘s hotkey binder) very often takes up to 20 (!!) seconds to take a single screenshot on systems experiencing high I/O load.)

                                                    share|improve this question

                                                    About 5-20 times a day I am presented with brief visual glitches and heisenbugs caused by race conditions that only occur under high I/O load. These disappear off the screen far too quickly for me to grab a camera in time, so I am looking to find/build a screenshotting/screen-recording tool that acts/responds with the lowest possible delay after I press a hotkey/shortcut.

                                                    Critically, this tool’s high-responsiveness needs to be negligibly (ideally not at all) impacted by high I/O activity, like 10-second load averages of 20-40.

                                                    A fair argument could be made about loading PREEMPT_RT and running Xorg and a homemade screenshot dæmon as realtime. This would work… except for the bit about running X realtime; I actually do want to get work done on my computer. 🙂

                                                    Thing is, I can confidently run any code I like in realtime on my computer, just by putting it inside the Linux kernel. So, kernel module time!! To reiterate my question,

                                                    How do I find, access and grok the memory region(s) representing the pixels on my screen, all from within a Linux kernel module?

                                                    I’ve found that trying to read /dev/fb0 while X is running just produces a black image, so that apparently won’t work.

                                                    Unfortunately https://dri.freedesktop.org/docs/drm/gpu/index.html doesn’t show anything obviously related to framebuffer read-back, but I have no experience with this API, so I don’t really know what I’m looking for.

                                                    I accept that driver-specific code will likely be needed (since there’s unlikely a driver-agnostic canonical spot in memory representing what’s actually on screen), and this fine. I’m using an Intel-GPU-based machine at the moment, and I am happy to start specifically coding for that.

                                                    FWIW, I asked a differently-worded version of this question just under two years ago. That question only attracted one comment about HDCP and was never answered, but as I am still dealing with this problem up to 20 times a day even two years later, I’m having another go.

                                                    (My current approach (scrot launched by i3‘s hotkey binder) very often takes up to 20 (!!) seconds to take a single screenshot on systems experiencing high I/O load.)

                                                    linux xorg screenshot drm kms

                                                    share|improve this question

                                                    share|improve this question

                                                    share|improve this question

                                                    share|improve this question

                                                    edited Feb 12 at 13:01

                                                    Rui F Ribeiro

                                                    41.2k1481139

                                                    41.2k1481139

                                                    asked Feb 12 at 12:53

                                                    i336_i336_

                                                    351317

                                                    351317

                                                    • It may depend on what video driver and kernel sub-system you are using. Running X.org 2D or 3D acceleration or simple frame buffer? Places like /dev/dri /dev/fbx /dev/mem /dev/nvidia0 and others.

                                                      – jc__
                                                      Feb 12 at 16:03

                                                    • @jc__: I’m using the intel driver – as I noted – and presume this provides 2D and basic 3D accel. I’ve already had a look at the DRI docs. I noted that /dev/fb0 produced a black image when X is running. I am genuinely curious, do you think /dev/mem might include VRAM? (That would be awesome.) I don’t have an Nvidia GPU.

                                                      – i336_
                                                      Feb 12 at 22:48

                                                    • @jc__: Genuinely appreciate the assistance

                                                      – i336_
                                                      Feb 12 at 22:48

                                                    • It may depend on what video driver and kernel sub-system you are using. Running X.org 2D or 3D acceleration or simple frame buffer? Places like /dev/dri /dev/fbx /dev/mem /dev/nvidia0 and others.

                                                      – jc__
                                                      Feb 12 at 16:03

                                                    • @jc__: I’m using the intel driver – as I noted – and presume this provides 2D and basic 3D accel. I’ve already had a look at the DRI docs. I noted that /dev/fb0 produced a black image when X is running. I am genuinely curious, do you think /dev/mem might include VRAM? (That would be awesome.) I don’t have an Nvidia GPU.

                                                      – i336_
                                                      Feb 12 at 22:48

                                                    • @jc__: Genuinely appreciate the assistance

                                                      – i336_
                                                      Feb 12 at 22:48

                                                    It may depend on what video driver and kernel sub-system you are using. Running X.org 2D or 3D acceleration or simple frame buffer? Places like /dev/dri /dev/fbx /dev/mem /dev/nvidia0 and others.

                                                    – jc__
                                                    Feb 12 at 16:03

                                                    It may depend on what video driver and kernel sub-system you are using. Running X.org 2D or 3D acceleration or simple frame buffer? Places like /dev/dri /dev/fbx /dev/mem /dev/nvidia0 and others.

                                                    – jc__
                                                    Feb 12 at 16:03

                                                    @jc__: I’m using the intel driver – as I noted – and presume this provides 2D and basic 3D accel. I’ve already had a look at the DRI docs. I noted that /dev/fb0 produced a black image when X is running. I am genuinely curious, do you think /dev/mem might include VRAM? (That would be awesome.) I don’t have an Nvidia GPU.

                                                    – i336_
                                                    Feb 12 at 22:48

                                                    @jc__: I’m using the intel driver – as I noted – and presume this provides 2D and basic 3D accel. I’ve already had a look at the DRI docs. I noted that /dev/fb0 produced a black image when X is running. I am genuinely curious, do you think /dev/mem might include VRAM? (That would be awesome.) I don’t have an Nvidia GPU.

                                                    – i336_
                                                    Feb 12 at 22:48

                                                    @jc__: Genuinely appreciate the assistance

                                                    – i336_
                                                    Feb 12 at 22:48

                                                    @jc__: Genuinely appreciate the assistance

                                                    – i336_
                                                    Feb 12 at 22:48

                                                    0

                                                    active

                                                    oldest

                                                    votes

                                                    Your Answer

                                                    StackExchange.ready(function() {
                                                    var channelOptions = {
                                                    tags: “”.split(” “),
                                                    id: “106”
                                                    };
                                                    initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                                    StackExchange.using(“externalEditor”, function() {
                                                    // Have to fire editor after snippets, if snippets enabled
                                                    if (StackExchange.settings.snippets.snippetsEnabled) {
                                                    StackExchange.using(“snippets”, function() {
                                                    createEditor();
                                                    });
                                                    }
                                                    else {
                                                    createEditor();
                                                    }
                                                    });

                                                    function createEditor() {
                                                    StackExchange.prepareEditor({
                                                    heartbeatType: ‘answer’,
                                                    autoActivateHeartbeat: false,
                                                    convertImagesToLinks: false,
                                                    noModals: true,
                                                    showLowRepImageUploadWarning: true,
                                                    reputationToPostImages: null,
                                                    bindNavPrevention: true,
                                                    postfix: “”,
                                                    imageUploader: {
                                                    brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                                    contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                                    allowUrls: true
                                                    },
                                                    onDemand: true,
                                                    discardSelector: “.discard-answer”
                                                    ,immediatelyShowMarkdownHelp:true
                                                    });

                                                    }
                                                    });

                                                    draft saved
                                                    draft discarded

                                                    StackExchange.ready(
                                                    function () {
                                                    StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f500167%2fhow-do-i-find-the-video-memory-regions-representing-whats-on-my-screen-from%23new-answer’, ‘question_page’);
                                                    }
                                                    );

                                                    Post as a guest

                                                    Required, but never shown

                                                    0

                                                    active

                                                    oldest

                                                    votes

                                                    0

                                                    active

                                                    oldest

                                                    votes

                                                    active

                                                    oldest

                                                    votes

                                                    active

                                                    oldest

                                                    votes

                                                    draft saved
                                                    draft discarded

                                                    Thanks for contributing an answer to Unix & Linux Stack Exchange!

                                                    • Please be sure to answer the question. Provide details and share your research!

                                                    But avoid

                                                    • Asking for help, clarification, or responding to other answers.
                                                    • Making statements based on opinion; back them up with references or personal experience.

                                                    To learn more, see our tips on writing great answers.

                                                    draft saved

                                                    draft discarded

                                                    StackExchange.ready(
                                                    function () {
                                                    StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f500167%2fhow-do-i-find-the-video-memory-regions-representing-whats-on-my-screen-from%23new-answer’, ‘question_page’);
                                                    }
                                                    );

                                                    Post as a guest

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    What is the command to close a window?

                                                    The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                                    6

                                                    I want to set a keyboard shortcut to close the current window in Ubuntu 16.04. I am aware that alt+f4 already does this and that I can redefine this shortcut if I want to, but what I really want is to add an additional shortcut to perform the same function.

                                                    The reason being; I have a keyboard without designated function keys (a 60%). Instead the function keys are activated via a keyboard shortcut that toggles the row of number keys between number and function keys (for example 4 to f4 and vice versa).

                                                    I am deep in the habit of quickly closing windows using alt+f4 and want it to work regardless of whether I am in function key or number key mode, but can’t seem to find what I should enter in the command field when setting a new keyboard shortcut.

                                                    I have found a good workaround to my particular problem and posted it in the answers below. Still open to more elegant solutions.

                                                    Edit: To clarify, the machine is running X11.

                                                    share|improve this question

                                                    • 1

                                                      Possible duplicate of How to close application from terminal same way as exiting it properly

                                                      – karel
                                                      Feb 26 at 12:39

                                                    6

                                                    I want to set a keyboard shortcut to close the current window in Ubuntu 16.04. I am aware that alt+f4 already does this and that I can redefine this shortcut if I want to, but what I really want is to add an additional shortcut to perform the same function.

                                                    The reason being; I have a keyboard without designated function keys (a 60%). Instead the function keys are activated via a keyboard shortcut that toggles the row of number keys between number and function keys (for example 4 to f4 and vice versa).

                                                    I am deep in the habit of quickly closing windows using alt+f4 and want it to work regardless of whether I am in function key or number key mode, but can’t seem to find what I should enter in the command field when setting a new keyboard shortcut.

                                                    I have found a good workaround to my particular problem and posted it in the answers below. Still open to more elegant solutions.

                                                    Edit: To clarify, the machine is running X11.

                                                    share|improve this question

                                                    • 1

                                                      Possible duplicate of How to close application from terminal same way as exiting it properly

                                                      – karel
                                                      Feb 26 at 12:39

                                                    6

                                                    6

                                                    6

                                                    1

                                                    I want to set a keyboard shortcut to close the current window in Ubuntu 16.04. I am aware that alt+f4 already does this and that I can redefine this shortcut if I want to, but what I really want is to add an additional shortcut to perform the same function.

                                                    The reason being; I have a keyboard without designated function keys (a 60%). Instead the function keys are activated via a keyboard shortcut that toggles the row of number keys between number and function keys (for example 4 to f4 and vice versa).

                                                    I am deep in the habit of quickly closing windows using alt+f4 and want it to work regardless of whether I am in function key or number key mode, but can’t seem to find what I should enter in the command field when setting a new keyboard shortcut.

                                                    I have found a good workaround to my particular problem and posted it in the answers below. Still open to more elegant solutions.

                                                    Edit: To clarify, the machine is running X11.

                                                    share|improve this question

                                                    I want to set a keyboard shortcut to close the current window in Ubuntu 16.04. I am aware that alt+f4 already does this and that I can redefine this shortcut if I want to, but what I really want is to add an additional shortcut to perform the same function.

                                                    The reason being; I have a keyboard without designated function keys (a 60%). Instead the function keys are activated via a keyboard shortcut that toggles the row of number keys between number and function keys (for example 4 to f4 and vice versa).

                                                    I am deep in the habit of quickly closing windows using alt+f4 and want it to work regardless of whether I am in function key or number key mode, but can’t seem to find what I should enter in the command field when setting a new keyboard shortcut.

                                                    I have found a good workaround to my particular problem and posted it in the answers below. Still open to more elegant solutions.

                                                    Edit: To clarify, the machine is running X11.

                                                    keyboard shortcut-keys xorg

                                                    share|improve this question

                                                    share|improve this question

                                                    share|improve this question

                                                    share|improve this question

                                                    edited Feb 11 at 14:10

                                                    FinleyGibson

                                                    asked Feb 11 at 12:32

                                                    FinleyGibsonFinleyGibson

                                                    416

                                                    416

                                                    • 1

                                                      Possible duplicate of How to close application from terminal same way as exiting it properly

                                                      – karel
                                                      Feb 26 at 12:39

                                                    • 1

                                                      Possible duplicate of How to close application from terminal same way as exiting it properly

                                                      – karel
                                                      Feb 26 at 12:39

                                                    1

                                                    1

                                                    Possible duplicate of How to close application from terminal same way as exiting it properly

                                                    – karel
                                                    Feb 26 at 12:39

                                                    Possible duplicate of How to close application from terminal same way as exiting it properly

                                                    – karel
                                                    Feb 26 at 12:39

                                                    4 Answers
                                                    4

                                                    active

                                                    oldest

                                                    votes

                                                    4

                                                    wmctrl -c <win>

                                                       wmctrl - interact with a EWMH/NetWM compatible X Window Manager.
                                                    
                                                       -c <WIN>
                                                              Close the window <WIN> gracefully.
                                                    

                                                    (from man wmctrl. But note: I use XFCE so haven’t tested this on Unity as found in default Ubuntu 16.04, and I wouldn’t expect it to work if using Wayland on 17.10 upwards)

                                                    share|improve this answer

                                                    • I am using X11, and having installed wmctrl, and applied your suggestion, it does work sort of. But The command does more than close the active window. Entering wmctrl -c WIN in terminal does close the current window, but it also seems to perform some kind of refresh of X11: the screen blinks and all open windows are moved to workspace 1. Is there something I am doing wrong here? Or is there another way to specify the exact functionality of alt+f4?

                                                      – FinleyGibson
                                                      Feb 11 at 13:03

                                                    • the <win> should be replaced by the window you want to close. I’ve only used it in shell scripts, and have known what workspaces (i usually use it to effect workspaces more than windows) I want to add/delete/switch-to. It takes some play to get to understand it, and I’d have your shortcut run a shell.script that closed the window (not sure how you’d work out current window, it’s a case I never considered in using wmctrl as its not how I use it as the windows I’ve closed are ones I’ve opened with my scripts)

                                                      – guiverc
                                                      Feb 11 at 13:07

                                                    • For example, I have a folder with photos open (in thunar as I’m using XFCE currently), and select one to view so open it. It opens in gpicview (my preferred viewer for that type of file). To close the window I can ctrl+alt+T to open a terminal and enter the command wmctrl -c P1000403.JPG (the P1000403.JPG being the name of the picture I was viewing in this example). On pressing enter the gpicview window containing my photo closes. <win> was replaced by the ‘title’ of my ‘window’ in this example. The ‘<>’ characters were copied from the man page representing values you change.

                                                      – guiverc
                                                      Feb 11 at 13:27

                                                    • I see what you are saying. In order to implement what I want in this way, I would then need a means of getting the name of the currently active window. But I can’t seem to find a way.

                                                      – FinleyGibson
                                                      Feb 11 at 13:39

                                                    • It’s after midnight my local time, what you’ve got is the best I can provide from my tired-brain given I want to go to bed (and don’t want to find my scripts to look for clues). the moment I’ve found the photo I want, it’s being posted & I’m off to bed

                                                      – guiverc
                                                      Feb 11 at 13:47

                                                    2

                                                    Had you try to use CTRL+Q

                                                    I was use to press these keys to close windows, never added a keyboard shortcut, seems to be the default at least in the distros I used(always debian based)

                                                    but I see the point of your question

                                                    share|improve this answer

                                                    • Nice Idea, but ctrl +Q does nothing for me.

                                                      – FinleyGibson
                                                      Feb 11 at 13:21

                                                    2

                                                    the other work around i found along with @FinleyGibson answer is

                                                    open dconf-editor (if dconf-editor is not installed, install with below command
                                                    sudo apt install dconf-editor)

                                                    search key word “close”

                                                    enter image description here

                                                    then edit the custom value to ['<Alt>F4', '<Alt>4']

                                                    enter image description here

                                                    share|improve this answer

                                                    • That looks like a good workaround. Not going accept it as the answer since there could still be a way to get the original command, but it does look like a tidy solution and I will use it in the future.

                                                      – FinleyGibson
                                                      Feb 12 at 16:23

                                                    1

                                                    I found a good solution to my problem, though it does not exactly answer the question I originally asked, I’m posting it here as a workaround for anyone that encounters a similar issue.

                                                    The solution I found was to use xdotool to execute the alt+f4 shortcut as a command, and to set this as the command for alt+4. To do this first isntall xdotool if you don’t have it already:

                                                    sudo apt-get install xdotool
                                                    

                                                    Then go to keyboard shortcuts in the settings menu, and add a custom shortcut. In the command field enter:

                                                    xdotool key Alt+F4
                                                    

                                                    And set the shortcut to Alt+4.

                                                    This works well, but I’m leaving the question as is, in case someone has a more elegant solution, using the exact command called by the close window shortcut by default.

                                                    share|improve this answer

                                                    • 1

                                                      Did you try xkill ? I’d say it is more advanced for me and kills just about anything 😀 you can launch it either from terminal or creating a shortcut.

                                                      – JoKeR
                                                      Feb 12 at 13:30

                                                    • 2

                                                      I did look into that. The problem with xkill is that it kills the whole process tree. So if you have 2 terminal windows open, both will be closed. This is not the functionality of alt+F4 and is not quite what I was looking for.

                                                      – FinleyGibson
                                                      Feb 12 at 16:20

                                                    • xdotool is a good solution for this issue. If you ever need to do something a bit more involved, take a look at AutoKey. It allows you to setup hotkeys and trigger phrases which can do anything from a simple text insertion to running an arbitrarily complex Python script which can use the keyboard and mouse for you to perform multiple actions.

                                                      – Joe
                                                      Feb 14 at 18:34

                                                    Your Answer

                                                    StackExchange.ready(function() {
                                                    var channelOptions = {
                                                    tags: “”.split(” “),
                                                    id: “89”
                                                    };
                                                    initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                                    StackExchange.using(“externalEditor”, function() {
                                                    // Have to fire editor after snippets, if snippets enabled
                                                    if (StackExchange.settings.snippets.snippetsEnabled) {
                                                    StackExchange.using(“snippets”, function() {
                                                    createEditor();
                                                    });
                                                    }
                                                    else {
                                                    createEditor();
                                                    }
                                                    });

                                                    function createEditor() {
                                                    StackExchange.prepareEditor({
                                                    heartbeatType: ‘answer’,
                                                    autoActivateHeartbeat: false,
                                                    convertImagesToLinks: true,
                                                    noModals: true,
                                                    showLowRepImageUploadWarning: true,
                                                    reputationToPostImages: 10,
                                                    bindNavPrevention: true,
                                                    postfix: “”,
                                                    imageUploader: {
                                                    brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                                    contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                                    allowUrls: true
                                                    },
                                                    onDemand: true,
                                                    discardSelector: “.discard-answer”
                                                    ,immediatelyShowMarkdownHelp:true
                                                    });

                                                    }
                                                    });

                                                    draft saved
                                                    draft discarded

                                                    StackExchange.ready(
                                                    function () {
                                                    StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2faskubuntu.com%2fquestions%2f1117353%2fwhat-is-the-command-to-close-a-window%23new-answer’, ‘question_page’);
                                                    }
                                                    );

                                                    Post as a guest

                                                    Required, but never shown

                                                    4 Answers
                                                    4

                                                    active

                                                    oldest

                                                    votes

                                                    4 Answers
                                                    4

                                                    active

                                                    oldest

                                                    votes

                                                    active

                                                    oldest

                                                    votes

                                                    active

                                                    oldest

                                                    votes

                                                    4

                                                    wmctrl -c <win>

                                                       wmctrl - interact with a EWMH/NetWM compatible X Window Manager.
                                                    
                                                       -c <WIN>
                                                              Close the window <WIN> gracefully.
                                                    

                                                    (from man wmctrl. But note: I use XFCE so haven’t tested this on Unity as found in default Ubuntu 16.04, and I wouldn’t expect it to work if using Wayland on 17.10 upwards)

                                                    share|improve this answer

                                                    • I am using X11, and having installed wmctrl, and applied your suggestion, it does work sort of. But The command does more than close the active window. Entering wmctrl -c WIN in terminal does close the current window, but it also seems to perform some kind of refresh of X11: the screen blinks and all open windows are moved to workspace 1. Is there something I am doing wrong here? Or is there another way to specify the exact functionality of alt+f4?

                                                      – FinleyGibson
                                                      Feb 11 at 13:03

                                                    • the <win> should be replaced by the window you want to close. I’ve only used it in shell scripts, and have known what workspaces (i usually use it to effect workspaces more than windows) I want to add/delete/switch-to. It takes some play to get to understand it, and I’d have your shortcut run a shell.script that closed the window (not sure how you’d work out current window, it’s a case I never considered in using wmctrl as its not how I use it as the windows I’ve closed are ones I’ve opened with my scripts)

                                                      – guiverc
                                                      Feb 11 at 13:07

                                                    • For example, I have a folder with photos open (in thunar as I’m using XFCE currently), and select one to view so open it. It opens in gpicview (my preferred viewer for that type of file). To close the window I can ctrl+alt+T to open a terminal and enter the command wmctrl -c P1000403.JPG (the P1000403.JPG being the name of the picture I was viewing in this example). On pressing enter the gpicview window containing my photo closes. <win> was replaced by the ‘title’ of my ‘window’ in this example. The ‘<>’ characters were copied from the man page representing values you change.

                                                      – guiverc
                                                      Feb 11 at 13:27

                                                    • I see what you are saying. In order to implement what I want in this way, I would then need a means of getting the name of the currently active window. But I can’t seem to find a way.

                                                      – FinleyGibson
                                                      Feb 11 at 13:39

                                                    • It’s after midnight my local time, what you’ve got is the best I can provide from my tired-brain given I want to go to bed (and don’t want to find my scripts to look for clues). the moment I’ve found the photo I want, it’s being posted & I’m off to bed

                                                      – guiverc
                                                      Feb 11 at 13:47

                                                    4

                                                    wmctrl -c <win>

                                                       wmctrl - interact with a EWMH/NetWM compatible X Window Manager.
                                                    
                                                       -c <WIN>
                                                              Close the window <WIN> gracefully.
                                                    

                                                    (from man wmctrl. But note: I use XFCE so haven’t tested this on Unity as found in default Ubuntu 16.04, and I wouldn’t expect it to work if using Wayland on 17.10 upwards)

                                                    share|improve this answer

                                                    • I am using X11, and having installed wmctrl, and applied your suggestion, it does work sort of. But The command does more than close the active window. Entering wmctrl -c WIN in terminal does close the current window, but it also seems to perform some kind of refresh of X11: the screen blinks and all open windows are moved to workspace 1. Is there something I am doing wrong here? Or is there another way to specify the exact functionality of alt+f4?

                                                      – FinleyGibson
                                                      Feb 11 at 13:03

                                                    • the <win> should be replaced by the window you want to close. I’ve only used it in shell scripts, and have known what workspaces (i usually use it to effect workspaces more than windows) I want to add/delete/switch-to. It takes some play to get to understand it, and I’d have your shortcut run a shell.script that closed the window (not sure how you’d work out current window, it’s a case I never considered in using wmctrl as its not how I use it as the windows I’ve closed are ones I’ve opened with my scripts)

                                                      – guiverc
                                                      Feb 11 at 13:07

                                                    • For example, I have a folder with photos open (in thunar as I’m using XFCE currently), and select one to view so open it. It opens in gpicview (my preferred viewer for that type of file). To close the window I can ctrl+alt+T to open a terminal and enter the command wmctrl -c P1000403.JPG (the P1000403.JPG being the name of the picture I was viewing in this example). On pressing enter the gpicview window containing my photo closes. <win> was replaced by the ‘title’ of my ‘window’ in this example. The ‘<>’ characters were copied from the man page representing values you change.

                                                      – guiverc
                                                      Feb 11 at 13:27

                                                    • I see what you are saying. In order to implement what I want in this way, I would then need a means of getting the name of the currently active window. But I can’t seem to find a way.

                                                      – FinleyGibson
                                                      Feb 11 at 13:39

                                                    • It’s after midnight my local time, what you’ve got is the best I can provide from my tired-brain given I want to go to bed (and don’t want to find my scripts to look for clues). the moment I’ve found the photo I want, it’s being posted & I’m off to bed

                                                      – guiverc
                                                      Feb 11 at 13:47

                                                    4

                                                    4

                                                    4

                                                    wmctrl -c <win>

                                                       wmctrl - interact with a EWMH/NetWM compatible X Window Manager.
                                                    
                                                       -c <WIN>
                                                              Close the window <WIN> gracefully.
                                                    

                                                    (from man wmctrl. But note: I use XFCE so haven’t tested this on Unity as found in default Ubuntu 16.04, and I wouldn’t expect it to work if using Wayland on 17.10 upwards)

                                                    share|improve this answer

                                                    wmctrl -c <win>

                                                       wmctrl - interact with a EWMH/NetWM compatible X Window Manager.
                                                    
                                                       -c <WIN>
                                                              Close the window <WIN> gracefully.
                                                    

                                                    (from man wmctrl. But note: I use XFCE so haven’t tested this on Unity as found in default Ubuntu 16.04, and I wouldn’t expect it to work if using Wayland on 17.10 upwards)

                                                    share|improve this answer

                                                    share|improve this answer

                                                    share|improve this answer

                                                    answered Feb 11 at 12:42

                                                    guivercguiverc

                                                    4,84621623

                                                    4,84621623

                                                    • I am using X11, and having installed wmctrl, and applied your suggestion, it does work sort of. But The command does more than close the active window. Entering wmctrl -c WIN in terminal does close the current window, but it also seems to perform some kind of refresh of X11: the screen blinks and all open windows are moved to workspace 1. Is there something I am doing wrong here? Or is there another way to specify the exact functionality of alt+f4?

                                                      – FinleyGibson
                                                      Feb 11 at 13:03

                                                    • the <win> should be replaced by the window you want to close. I’ve only used it in shell scripts, and have known what workspaces (i usually use it to effect workspaces more than windows) I want to add/delete/switch-to. It takes some play to get to understand it, and I’d have your shortcut run a shell.script that closed the window (not sure how you’d work out current window, it’s a case I never considered in using wmctrl as its not how I use it as the windows I’ve closed are ones I’ve opened with my scripts)

                                                      – guiverc
                                                      Feb 11 at 13:07

                                                    • For example, I have a folder with photos open (in thunar as I’m using XFCE currently), and select one to view so open it. It opens in gpicview (my preferred viewer for that type of file). To close the window I can ctrl+alt+T to open a terminal and enter the command wmctrl -c P1000403.JPG (the P1000403.JPG being the name of the picture I was viewing in this example). On pressing enter the gpicview window containing my photo closes. <win> was replaced by the ‘title’ of my ‘window’ in this example. The ‘<>’ characters were copied from the man page representing values you change.

                                                      – guiverc
                                                      Feb 11 at 13:27

                                                    • I see what you are saying. In order to implement what I want in this way, I would then need a means of getting the name of the currently active window. But I can’t seem to find a way.

                                                      – FinleyGibson
                                                      Feb 11 at 13:39

                                                    • It’s after midnight my local time, what you’ve got is the best I can provide from my tired-brain given I want to go to bed (and don’t want to find my scripts to look for clues). the moment I’ve found the photo I want, it’s being posted & I’m off to bed

                                                      – guiverc
                                                      Feb 11 at 13:47

                                                    • I am using X11, and having installed wmctrl, and applied your suggestion, it does work sort of. But The command does more than close the active window. Entering wmctrl -c WIN in terminal does close the current window, but it also seems to perform some kind of refresh of X11: the screen blinks and all open windows are moved to workspace 1. Is there something I am doing wrong here? Or is there another way to specify the exact functionality of alt+f4?

                                                      – FinleyGibson
                                                      Feb 11 at 13:03

                                                    • the <win> should be replaced by the window you want to close. I’ve only used it in shell scripts, and have known what workspaces (i usually use it to effect workspaces more than windows) I want to add/delete/switch-to. It takes some play to get to understand it, and I’d have your shortcut run a shell.script that closed the window (not sure how you’d work out current window, it’s a case I never considered in using wmctrl as its not how I use it as the windows I’ve closed are ones I’ve opened with my scripts)

                                                      – guiverc
                                                      Feb 11 at 13:07

                                                    • For example, I have a folder with photos open (in thunar as I’m using XFCE currently), and select one to view so open it. It opens in gpicview (my preferred viewer for that type of file). To close the window I can ctrl+alt+T to open a terminal and enter the command wmctrl -c P1000403.JPG (the P1000403.JPG being the name of the picture I was viewing in this example). On pressing enter the gpicview window containing my photo closes. <win> was replaced by the ‘title’ of my ‘window’ in this example. The ‘<>’ characters were copied from the man page representing values you change.

                                                      – guiverc
                                                      Feb 11 at 13:27

                                                    • I see what you are saying. In order to implement what I want in this way, I would then need a means of getting the name of the currently active window. But I can’t seem to find a way.

                                                      – FinleyGibson
                                                      Feb 11 at 13:39

                                                    • It’s after midnight my local time, what you’ve got is the best I can provide from my tired-brain given I want to go to bed (and don’t want to find my scripts to look for clues). the moment I’ve found the photo I want, it’s being posted & I’m off to bed

                                                      – guiverc
                                                      Feb 11 at 13:47

                                                    I am using X11, and having installed wmctrl, and applied your suggestion, it does work sort of. But The command does more than close the active window. Entering wmctrl -c WIN in terminal does close the current window, but it also seems to perform some kind of refresh of X11: the screen blinks and all open windows are moved to workspace 1. Is there something I am doing wrong here? Or is there another way to specify the exact functionality of alt+f4?

                                                    – FinleyGibson
                                                    Feb 11 at 13:03

                                                    I am using X11, and having installed wmctrl, and applied your suggestion, it does work sort of. But The command does more than close the active window. Entering wmctrl -c WIN in terminal does close the current window, but it also seems to perform some kind of refresh of X11: the screen blinks and all open windows are moved to workspace 1. Is there something I am doing wrong here? Or is there another way to specify the exact functionality of alt+f4?

                                                    – FinleyGibson
                                                    Feb 11 at 13:03

                                                    the <win> should be replaced by the window you want to close. I’ve only used it in shell scripts, and have known what workspaces (i usually use it to effect workspaces more than windows) I want to add/delete/switch-to. It takes some play to get to understand it, and I’d have your shortcut run a shell.script that closed the window (not sure how you’d work out current window, it’s a case I never considered in using wmctrl as its not how I use it as the windows I’ve closed are ones I’ve opened with my scripts)

                                                    – guiverc
                                                    Feb 11 at 13:07

                                                    the <win> should be replaced by the window you want to close. I’ve only used it in shell scripts, and have known what workspaces (i usually use it to effect workspaces more than windows) I want to add/delete/switch-to. It takes some play to get to understand it, and I’d have your shortcut run a shell.script that closed the window (not sure how you’d work out current window, it’s a case I never considered in using wmctrl as its not how I use it as the windows I’ve closed are ones I’ve opened with my scripts)

                                                    – guiverc
                                                    Feb 11 at 13:07

                                                    For example, I have a folder with photos open (in thunar as I’m using XFCE currently), and select one to view so open it. It opens in gpicview (my preferred viewer for that type of file). To close the window I can ctrl+alt+T to open a terminal and enter the command wmctrl -c P1000403.JPG (the P1000403.JPG being the name of the picture I was viewing in this example). On pressing enter the gpicview window containing my photo closes. <win> was replaced by the ‘title’ of my ‘window’ in this example. The ‘<>’ characters were copied from the man page representing values you change.

                                                    – guiverc
                                                    Feb 11 at 13:27

                                                    For example, I have a folder with photos open (in thunar as I’m using XFCE currently), and select one to view so open it. It opens in gpicview (my preferred viewer for that type of file). To close the window I can ctrl+alt+T to open a terminal and enter the command wmctrl -c P1000403.JPG (the P1000403.JPG being the name of the picture I was viewing in this example). On pressing enter the gpicview window containing my photo closes. <win> was replaced by the ‘title’ of my ‘window’ in this example. The ‘<>’ characters were copied from the man page representing values you change.

                                                    – guiverc
                                                    Feb 11 at 13:27

                                                    I see what you are saying. In order to implement what I want in this way, I would then need a means of getting the name of the currently active window. But I can’t seem to find a way.

                                                    – FinleyGibson
                                                    Feb 11 at 13:39

                                                    I see what you are saying. In order to implement what I want in this way, I would then need a means of getting the name of the currently active window. But I can’t seem to find a way.

                                                    – FinleyGibson
                                                    Feb 11 at 13:39

                                                    It’s after midnight my local time, what you’ve got is the best I can provide from my tired-brain given I want to go to bed (and don’t want to find my scripts to look for clues). the moment I’ve found the photo I want, it’s being posted & I’m off to bed

                                                    – guiverc
                                                    Feb 11 at 13:47

                                                    It’s after midnight my local time, what you’ve got is the best I can provide from my tired-brain given I want to go to bed (and don’t want to find my scripts to look for clues). the moment I’ve found the photo I want, it’s being posted & I’m off to bed

                                                    – guiverc
                                                    Feb 11 at 13:47

                                                    2

                                                    Had you try to use CTRL+Q

                                                    I was use to press these keys to close windows, never added a keyboard shortcut, seems to be the default at least in the distros I used(always debian based)

                                                    but I see the point of your question

                                                    share|improve this answer

                                                    • Nice Idea, but ctrl +Q does nothing for me.

                                                      – FinleyGibson
                                                      Feb 11 at 13:21

                                                    2

                                                    Had you try to use CTRL+Q

                                                    I was use to press these keys to close windows, never added a keyboard shortcut, seems to be the default at least in the distros I used(always debian based)

                                                    but I see the point of your question

                                                    share|improve this answer

                                                    • Nice Idea, but ctrl +Q does nothing for me.

                                                      – FinleyGibson
                                                      Feb 11 at 13:21

                                                    2

                                                    2

                                                    2

                                                    Had you try to use CTRL+Q

                                                    I was use to press these keys to close windows, never added a keyboard shortcut, seems to be the default at least in the distros I used(always debian based)

                                                    but I see the point of your question

                                                    share|improve this answer

                                                    Had you try to use CTRL+Q

                                                    I was use to press these keys to close windows, never added a keyboard shortcut, seems to be the default at least in the distros I used(always debian based)

                                                    but I see the point of your question

                                                    share|improve this answer

                                                    share|improve this answer

                                                    share|improve this answer

                                                    answered Feb 11 at 13:05

                                                    leselese

                                                    1,755158

                                                    1,755158

                                                    • Nice Idea, but ctrl +Q does nothing for me.

                                                      – FinleyGibson
                                                      Feb 11 at 13:21

                                                    • Nice Idea, but ctrl +Q does nothing for me.

                                                      – FinleyGibson
                                                      Feb 11 at 13:21

                                                    Nice Idea, but ctrl +Q does nothing for me.

                                                    – FinleyGibson
                                                    Feb 11 at 13:21

                                                    Nice Idea, but ctrl +Q does nothing for me.

                                                    – FinleyGibson
                                                    Feb 11 at 13:21

                                                    2

                                                    the other work around i found along with @FinleyGibson answer is

                                                    open dconf-editor (if dconf-editor is not installed, install with below command
                                                    sudo apt install dconf-editor)

                                                    search key word “close”

                                                    enter image description here

                                                    then edit the custom value to ['<Alt>F4', '<Alt>4']

                                                    enter image description here

                                                    share|improve this answer

                                                    • That looks like a good workaround. Not going accept it as the answer since there could still be a way to get the original command, but it does look like a tidy solution and I will use it in the future.

                                                      – FinleyGibson
                                                      Feb 12 at 16:23

                                                    2

                                                    the other work around i found along with @FinleyGibson answer is

                                                    open dconf-editor (if dconf-editor is not installed, install with below command
                                                    sudo apt install dconf-editor)

                                                    search key word “close”

                                                    enter image description here

                                                    then edit the custom value to ['<Alt>F4', '<Alt>4']

                                                    enter image description here

                                                    share|improve this answer

                                                    • That looks like a good workaround. Not going accept it as the answer since there could still be a way to get the original command, but it does look like a tidy solution and I will use it in the future.

                                                      – FinleyGibson
                                                      Feb 12 at 16:23

                                                    2

                                                    2

                                                    2

                                                    the other work around i found along with @FinleyGibson answer is

                                                    open dconf-editor (if dconf-editor is not installed, install with below command
                                                    sudo apt install dconf-editor)

                                                    search key word “close”

                                                    enter image description here

                                                    then edit the custom value to ['<Alt>F4', '<Alt>4']

                                                    enter image description here

                                                    share|improve this answer

                                                    the other work around i found along with @FinleyGibson answer is

                                                    open dconf-editor (if dconf-editor is not installed, install with below command
                                                    sudo apt install dconf-editor)

                                                    search key word “close”

                                                    enter image description here

                                                    then edit the custom value to ['<Alt>F4', '<Alt>4']

                                                    enter image description here

                                                    share|improve this answer

                                                    share|improve this answer

                                                    share|improve this answer

                                                    answered Feb 12 at 12:52

                                                    PRATAPPRATAP

                                                    2,9432828

                                                    2,9432828

                                                    • That looks like a good workaround. Not going accept it as the answer since there could still be a way to get the original command, but it does look like a tidy solution and I will use it in the future.

                                                      – FinleyGibson
                                                      Feb 12 at 16:23

                                                    • That looks like a good workaround. Not going accept it as the answer since there could still be a way to get the original command, but it does look like a tidy solution and I will use it in the future.

                                                      – FinleyGibson
                                                      Feb 12 at 16:23

                                                    That looks like a good workaround. Not going accept it as the answer since there could still be a way to get the original command, but it does look like a tidy solution and I will use it in the future.

                                                    – FinleyGibson
                                                    Feb 12 at 16:23

                                                    That looks like a good workaround. Not going accept it as the answer since there could still be a way to get the original command, but it does look like a tidy solution and I will use it in the future.

                                                    – FinleyGibson
                                                    Feb 12 at 16:23

                                                    1

                                                    I found a good solution to my problem, though it does not exactly answer the question I originally asked, I’m posting it here as a workaround for anyone that encounters a similar issue.

                                                    The solution I found was to use xdotool to execute the alt+f4 shortcut as a command, and to set this as the command for alt+4. To do this first isntall xdotool if you don’t have it already:

                                                    sudo apt-get install xdotool
                                                    

                                                    Then go to keyboard shortcuts in the settings menu, and add a custom shortcut. In the command field enter:

                                                    xdotool key Alt+F4
                                                    

                                                    And set the shortcut to Alt+4.

                                                    This works well, but I’m leaving the question as is, in case someone has a more elegant solution, using the exact command called by the close window shortcut by default.

                                                    share|improve this answer

                                                    • 1

                                                      Did you try xkill ? I’d say it is more advanced for me and kills just about anything 😀 you can launch it either from terminal or creating a shortcut.

                                                      – JoKeR
                                                      Feb 12 at 13:30

                                                    • 2

                                                      I did look into that. The problem with xkill is that it kills the whole process tree. So if you have 2 terminal windows open, both will be closed. This is not the functionality of alt+F4 and is not quite what I was looking for.

                                                      – FinleyGibson
                                                      Feb 12 at 16:20

                                                    • xdotool is a good solution for this issue. If you ever need to do something a bit more involved, take a look at AutoKey. It allows you to setup hotkeys and trigger phrases which can do anything from a simple text insertion to running an arbitrarily complex Python script which can use the keyboard and mouse for you to perform multiple actions.

                                                      – Joe
                                                      Feb 14 at 18:34

                                                    1

                                                    I found a good solution to my problem, though it does not exactly answer the question I originally asked, I’m posting it here as a workaround for anyone that encounters a similar issue.

                                                    The solution I found was to use xdotool to execute the alt+f4 shortcut as a command, and to set this as the command for alt+4. To do this first isntall xdotool if you don’t have it already:

                                                    sudo apt-get install xdotool
                                                    

                                                    Then go to keyboard shortcuts in the settings menu, and add a custom shortcut. In the command field enter:

                                                    xdotool key Alt+F4
                                                    

                                                    And set the shortcut to Alt+4.

                                                    This works well, but I’m leaving the question as is, in case someone has a more elegant solution, using the exact command called by the close window shortcut by default.

                                                    share|improve this answer

                                                    • 1

                                                      Did you try xkill ? I’d say it is more advanced for me and kills just about anything 😀 you can launch it either from terminal or creating a shortcut.

                                                      – JoKeR
                                                      Feb 12 at 13:30

                                                    • 2

                                                      I did look into that. The problem with xkill is that it kills the whole process tree. So if you have 2 terminal windows open, both will be closed. This is not the functionality of alt+F4 and is not quite what I was looking for.

                                                      – FinleyGibson
                                                      Feb 12 at 16:20

                                                    • xdotool is a good solution for this issue. If you ever need to do something a bit more involved, take a look at AutoKey. It allows you to setup hotkeys and trigger phrases which can do anything from a simple text insertion to running an arbitrarily complex Python script which can use the keyboard and mouse for you to perform multiple actions.

                                                      – Joe
                                                      Feb 14 at 18:34

                                                    1

                                                    1

                                                    1

                                                    I found a good solution to my problem, though it does not exactly answer the question I originally asked, I’m posting it here as a workaround for anyone that encounters a similar issue.

                                                    The solution I found was to use xdotool to execute the alt+f4 shortcut as a command, and to set this as the command for alt+4. To do this first isntall xdotool if you don’t have it already:

                                                    sudo apt-get install xdotool
                                                    

                                                    Then go to keyboard shortcuts in the settings menu, and add a custom shortcut. In the command field enter:

                                                    xdotool key Alt+F4
                                                    

                                                    And set the shortcut to Alt+4.

                                                    This works well, but I’m leaving the question as is, in case someone has a more elegant solution, using the exact command called by the close window shortcut by default.

                                                    share|improve this answer

                                                    I found a good solution to my problem, though it does not exactly answer the question I originally asked, I’m posting it here as a workaround for anyone that encounters a similar issue.

                                                    The solution I found was to use xdotool to execute the alt+f4 shortcut as a command, and to set this as the command for alt+4. To do this first isntall xdotool if you don’t have it already:

                                                    sudo apt-get install xdotool
                                                    

                                                    Then go to keyboard shortcuts in the settings menu, and add a custom shortcut. In the command field enter:

                                                    xdotool key Alt+F4
                                                    

                                                    And set the shortcut to Alt+4.

                                                    This works well, but I’m leaving the question as is, in case someone has a more elegant solution, using the exact command called by the close window shortcut by default.

                                                    share|improve this answer

                                                    share|improve this answer

                                                    share|improve this answer

                                                    edited Feb 11 at 18:03

                                                    answered Feb 11 at 13:50

                                                    FinleyGibsonFinleyGibson

                                                    416

                                                    416

                                                    • 1

                                                      Did you try xkill ? I’d say it is more advanced for me and kills just about anything 😀 you can launch it either from terminal or creating a shortcut.

                                                      – JoKeR
                                                      Feb 12 at 13:30

                                                    • 2

                                                      I did look into that. The problem with xkill is that it kills the whole process tree. So if you have 2 terminal windows open, both will be closed. This is not the functionality of alt+F4 and is not quite what I was looking for.

                                                      – FinleyGibson
                                                      Feb 12 at 16:20

                                                    • xdotool is a good solution for this issue. If you ever need to do something a bit more involved, take a look at AutoKey. It allows you to setup hotkeys and trigger phrases which can do anything from a simple text insertion to running an arbitrarily complex Python script which can use the keyboard and mouse for you to perform multiple actions.

                                                      – Joe
                                                      Feb 14 at 18:34

                                                    • 1

                                                      Did you try xkill ? I’d say it is more advanced for me and kills just about anything 😀 you can launch it either from terminal or creating a shortcut.

                                                      – JoKeR
                                                      Feb 12 at 13:30

                                                    • 2

                                                      I did look into that. The problem with xkill is that it kills the whole process tree. So if you have 2 terminal windows open, both will be closed. This is not the functionality of alt+F4 and is not quite what I was looking for.

                                                      – FinleyGibson
                                                      Feb 12 at 16:20

                                                    • xdotool is a good solution for this issue. If you ever need to do something a bit more involved, take a look at AutoKey. It allows you to setup hotkeys and trigger phrases which can do anything from a simple text insertion to running an arbitrarily complex Python script which can use the keyboard and mouse for you to perform multiple actions.

                                                      – Joe
                                                      Feb 14 at 18:34

                                                    1

                                                    1

                                                    Did you try xkill ? I’d say it is more advanced for me and kills just about anything 😀 you can launch it either from terminal or creating a shortcut.

                                                    – JoKeR
                                                    Feb 12 at 13:30

                                                    Did you try xkill ? I’d say it is more advanced for me and kills just about anything 😀 you can launch it either from terminal or creating a shortcut.

                                                    – JoKeR
                                                    Feb 12 at 13:30

                                                    2

                                                    2

                                                    I did look into that. The problem with xkill is that it kills the whole process tree. So if you have 2 terminal windows open, both will be closed. This is not the functionality of alt+F4 and is not quite what I was looking for.

                                                    – FinleyGibson
                                                    Feb 12 at 16:20

                                                    I did look into that. The problem with xkill is that it kills the whole process tree. So if you have 2 terminal windows open, both will be closed. This is not the functionality of alt+F4 and is not quite what I was looking for.

                                                    – FinleyGibson
                                                    Feb 12 at 16:20

                                                    xdotool is a good solution for this issue. If you ever need to do something a bit more involved, take a look at AutoKey. It allows you to setup hotkeys and trigger phrases which can do anything from a simple text insertion to running an arbitrarily complex Python script which can use the keyboard and mouse for you to perform multiple actions.

                                                    – Joe
                                                    Feb 14 at 18:34

                                                    xdotool is a good solution for this issue. If you ever need to do something a bit more involved, take a look at AutoKey. It allows you to setup hotkeys and trigger phrases which can do anything from a simple text insertion to running an arbitrarily complex Python script which can use the keyboard and mouse for you to perform multiple actions.

                                                    – Joe
                                                    Feb 14 at 18:34

                                                    draft saved
                                                    draft discarded

                                                    Thanks for contributing an answer to Ask Ubuntu!

                                                    • Please be sure to answer the question. Provide details and share your research!

                                                    But avoid

                                                    • Asking for help, clarification, or responding to other answers.
                                                    • Making statements based on opinion; back them up with references or personal experience.

                                                    To learn more, see our tips on writing great answers.

                                                    draft saved

                                                    draft discarded

                                                    StackExchange.ready(
                                                    function () {
                                                    StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2faskubuntu.com%2fquestions%2f1117353%2fwhat-is-the-command-to-close-a-window%23new-answer’, ‘question_page’);
                                                    }
                                                    );

                                                    Post as a guest

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Required, but never shown

                                                    Xorg.conf leaves me with no visible output

                                                    The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                                    3

                                                    I have yet another laptop which is a casualty of the proprietary Nvidia driver. I would like to do CUDA development on the laptop (Dell Precision 5510 with Quadro M1000M and 4k display), so I want the proprietary driver.

                                                    I have tried for several hours now, even reading through this, and I just don’t know how to configure xorg when it won’t autoconfigure. I used nvidia-xconfig to set my xorg.conf initially, then I had to add a BusID setting to the Device section in order to find the card. Now, startx runs without errors (and I can verify things are actually working), but it’s like it’s only showing on a ghost screen. I can run DISPLAY=:0 xrandr remotely and I get a 8×8 virtual screen with no outputs:

                                                    Screen 0: minimum 8 x 8, current 8 x 8, maximum 16384 x 16384
                                                    

                                                    I get the following chunk of Nvidia-related output in my xorg log file, with a couple of suspicious NULL values:

                                                    (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 16 22:35:15 2016
                                                    (==) Using config file: "/etc/X11/xorg.conf"
                                                    (==) Using system config directory "/usr/share/X11/xorg.conf.d"
                                                    (==) ServerLayout "Layout0"
                                                    (**) |-->Screen "Screen0" (0)
                                                    (**) |   |-->Monitor "Monitor0"
                                                    (**) |   |-->Device "Device0"
                                                    (**) |-->Input Device "Keyboard0"
                                                    (**) |-->Input Device "Mouse0"
                                                    
                                                    ...
                                                    
                                                    (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
                                                    (==) NVIDIA(0): RGB weight 888
                                                    (==) NVIDIA(0): Default visual is TrueColor
                                                    (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
                                                    (**) NVIDIA(0): Enabling 2D acceleration
                                                    (II) NVIDIA(0): NVIDIA GPU Quadro M1000M (GM107GL-A) at PCI:1:0:0 (GPU-0)
                                                    (--) NVIDIA(0): Memory: 2097152 kBytes
                                                    (--) NVIDIA(0): VideoBIOS: 82.07.82.00.23
                                                    (II) NVIDIA(0): Detected PCI Express Link width: 16X
                                                    (II) NVIDIA(0): Validated MetaModes:
                                                    (II) NVIDIA(0):     "NULL"
                                                    (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
                                                    (WW) NVIDIA(0): Unable to get display device for DPI computation.
                                                    (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
                                                    (--) Depth 24 pixmap format is 32 bpp
                                                    (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
                                                    (II) NVIDIA:     access.
                                                    (WW) NVIDIA(0): ACPI: AC power state information is not available under
                                                    (WW) NVIDIA(0):     /sys/class/power_supply/ , nor under
                                                    (WW) NVIDIA(0):     /proc/acpi/ac_adapter/
                                                    (II) NVIDIA(0): Built-in logo is bigger than the screen.
                                                    (II) NVIDIA(0): Setting mode "NULL"
                                                    (==) NVIDIA(0): Disabling shared memory pixmaps
                                                    (==) NVIDIA(0): Backing store enabled
                                                    (==) NVIDIA(0): Silken mouse enabled
                                                    (**) NVIDIA(0): DPMS enabled
                                                    

                                                    Here is my current xorg.conf:

                                                    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
                                                    # nvidia-xconfig:  version 367.35  (buildmeister@swio-display-x64-rhel04-01)  Mon Jul 11 23:51:45 PDT 2016
                                                    
                                                    
                                                    Section "ServerLayout"
                                                        Identifier     "Layout0"
                                                        Screen      0  "Screen0" 0 0
                                                        InputDevice    "Keyboard0" "CoreKeyboard"
                                                        InputDevice    "Mouse0" "CorePointer"
                                                    EndSection
                                                    
                                                    Section "InputDevice"
                                                    
                                                        # generated from default
                                                        Identifier     "Mouse0"
                                                        Driver         "mouse"
                                                        Option         "Protocol" "auto"
                                                        Option         "Device" "/dev/psaux"
                                                        Option         "Emulate3Buttons" "no"
                                                        Option         "ZAxisMapping" "4 5"
                                                    EndSection
                                                    
                                                    Section "InputDevice"
                                                    
                                                        # generated from default
                                                        Identifier     "Keyboard0"
                                                        Driver         "kbd"
                                                    EndSection
                                                    
                                                    Section "Monitor"
                                                        Identifier     "Monitor0"
                                                        VendorName     "LaptopBuiltin"
                                                        ModelName      "eDP1"
                                                        HorizSync       28.0 - 33.0
                                                        VertRefresh     43.0 - 72.0
                                                        Option         "DPMS"
                                                    EndSection
                                                    
                                                    Section "Device"
                                                        Identifier     "Device0"
                                                        Driver         "nvidia"
                                                        VendorName     "NVIDIA Corporation"
                                                        #BusId          "PCI:1:0:0"
                                                    EndSection
                                                    
                                                    Section "Screen"
                                                        Identifier     "Screen0"
                                                        Device         "Device0"
                                                        Monitor        "Monitor0"
                                                        DefaultDepth    24
                                                        SubSection     "Display"
                                                            Depth       24
                                                        EndSubSection
                                                    EndSection
                                                    

                                                    share|improve this question

                                                      3

                                                      I have yet another laptop which is a casualty of the proprietary Nvidia driver. I would like to do CUDA development on the laptop (Dell Precision 5510 with Quadro M1000M and 4k display), so I want the proprietary driver.

                                                      I have tried for several hours now, even reading through this, and I just don’t know how to configure xorg when it won’t autoconfigure. I used nvidia-xconfig to set my xorg.conf initially, then I had to add a BusID setting to the Device section in order to find the card. Now, startx runs without errors (and I can verify things are actually working), but it’s like it’s only showing on a ghost screen. I can run DISPLAY=:0 xrandr remotely and I get a 8×8 virtual screen with no outputs:

                                                      Screen 0: minimum 8 x 8, current 8 x 8, maximum 16384 x 16384
                                                      

                                                      I get the following chunk of Nvidia-related output in my xorg log file, with a couple of suspicious NULL values:

                                                      (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 16 22:35:15 2016
                                                      (==) Using config file: "/etc/X11/xorg.conf"
                                                      (==) Using system config directory "/usr/share/X11/xorg.conf.d"
                                                      (==) ServerLayout "Layout0"
                                                      (**) |-->Screen "Screen0" (0)
                                                      (**) |   |-->Monitor "Monitor0"
                                                      (**) |   |-->Device "Device0"
                                                      (**) |-->Input Device "Keyboard0"
                                                      (**) |-->Input Device "Mouse0"
                                                      
                                                      ...
                                                      
                                                      (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
                                                      (==) NVIDIA(0): RGB weight 888
                                                      (==) NVIDIA(0): Default visual is TrueColor
                                                      (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
                                                      (**) NVIDIA(0): Enabling 2D acceleration
                                                      (II) NVIDIA(0): NVIDIA GPU Quadro M1000M (GM107GL-A) at PCI:1:0:0 (GPU-0)
                                                      (--) NVIDIA(0): Memory: 2097152 kBytes
                                                      (--) NVIDIA(0): VideoBIOS: 82.07.82.00.23
                                                      (II) NVIDIA(0): Detected PCI Express Link width: 16X
                                                      (II) NVIDIA(0): Validated MetaModes:
                                                      (II) NVIDIA(0):     "NULL"
                                                      (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
                                                      (WW) NVIDIA(0): Unable to get display device for DPI computation.
                                                      (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
                                                      (--) Depth 24 pixmap format is 32 bpp
                                                      (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
                                                      (II) NVIDIA:     access.
                                                      (WW) NVIDIA(0): ACPI: AC power state information is not available under
                                                      (WW) NVIDIA(0):     /sys/class/power_supply/ , nor under
                                                      (WW) NVIDIA(0):     /proc/acpi/ac_adapter/
                                                      (II) NVIDIA(0): Built-in logo is bigger than the screen.
                                                      (II) NVIDIA(0): Setting mode "NULL"
                                                      (==) NVIDIA(0): Disabling shared memory pixmaps
                                                      (==) NVIDIA(0): Backing store enabled
                                                      (==) NVIDIA(0): Silken mouse enabled
                                                      (**) NVIDIA(0): DPMS enabled
                                                      

                                                      Here is my current xorg.conf:

                                                      # nvidia-xconfig: X configuration file generated by nvidia-xconfig
                                                      # nvidia-xconfig:  version 367.35  (buildmeister@swio-display-x64-rhel04-01)  Mon Jul 11 23:51:45 PDT 2016
                                                      
                                                      
                                                      Section "ServerLayout"
                                                          Identifier     "Layout0"
                                                          Screen      0  "Screen0" 0 0
                                                          InputDevice    "Keyboard0" "CoreKeyboard"
                                                          InputDevice    "Mouse0" "CorePointer"
                                                      EndSection
                                                      
                                                      Section "InputDevice"
                                                      
                                                          # generated from default
                                                          Identifier     "Mouse0"
                                                          Driver         "mouse"
                                                          Option         "Protocol" "auto"
                                                          Option         "Device" "/dev/psaux"
                                                          Option         "Emulate3Buttons" "no"
                                                          Option         "ZAxisMapping" "4 5"
                                                      EndSection
                                                      
                                                      Section "InputDevice"
                                                      
                                                          # generated from default
                                                          Identifier     "Keyboard0"
                                                          Driver         "kbd"
                                                      EndSection
                                                      
                                                      Section "Monitor"
                                                          Identifier     "Monitor0"
                                                          VendorName     "LaptopBuiltin"
                                                          ModelName      "eDP1"
                                                          HorizSync       28.0 - 33.0
                                                          VertRefresh     43.0 - 72.0
                                                          Option         "DPMS"
                                                      EndSection
                                                      
                                                      Section "Device"
                                                          Identifier     "Device0"
                                                          Driver         "nvidia"
                                                          VendorName     "NVIDIA Corporation"
                                                          #BusId          "PCI:1:0:0"
                                                      EndSection
                                                      
                                                      Section "Screen"
                                                          Identifier     "Screen0"
                                                          Device         "Device0"
                                                          Monitor        "Monitor0"
                                                          DefaultDepth    24
                                                          SubSection     "Display"
                                                              Depth       24
                                                          EndSubSection
                                                      EndSection
                                                      

                                                      share|improve this question

                                                        3

                                                        3

                                                        3

                                                        I have yet another laptop which is a casualty of the proprietary Nvidia driver. I would like to do CUDA development on the laptop (Dell Precision 5510 with Quadro M1000M and 4k display), so I want the proprietary driver.

                                                        I have tried for several hours now, even reading through this, and I just don’t know how to configure xorg when it won’t autoconfigure. I used nvidia-xconfig to set my xorg.conf initially, then I had to add a BusID setting to the Device section in order to find the card. Now, startx runs without errors (and I can verify things are actually working), but it’s like it’s only showing on a ghost screen. I can run DISPLAY=:0 xrandr remotely and I get a 8×8 virtual screen with no outputs:

                                                        Screen 0: minimum 8 x 8, current 8 x 8, maximum 16384 x 16384
                                                        

                                                        I get the following chunk of Nvidia-related output in my xorg log file, with a couple of suspicious NULL values:

                                                        (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 16 22:35:15 2016
                                                        (==) Using config file: "/etc/X11/xorg.conf"
                                                        (==) Using system config directory "/usr/share/X11/xorg.conf.d"
                                                        (==) ServerLayout "Layout0"
                                                        (**) |-->Screen "Screen0" (0)
                                                        (**) |   |-->Monitor "Monitor0"
                                                        (**) |   |-->Device "Device0"
                                                        (**) |-->Input Device "Keyboard0"
                                                        (**) |-->Input Device "Mouse0"
                                                        
                                                        ...
                                                        
                                                        (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
                                                        (==) NVIDIA(0): RGB weight 888
                                                        (==) NVIDIA(0): Default visual is TrueColor
                                                        (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
                                                        (**) NVIDIA(0): Enabling 2D acceleration
                                                        (II) NVIDIA(0): NVIDIA GPU Quadro M1000M (GM107GL-A) at PCI:1:0:0 (GPU-0)
                                                        (--) NVIDIA(0): Memory: 2097152 kBytes
                                                        (--) NVIDIA(0): VideoBIOS: 82.07.82.00.23
                                                        (II) NVIDIA(0): Detected PCI Express Link width: 16X
                                                        (II) NVIDIA(0): Validated MetaModes:
                                                        (II) NVIDIA(0):     "NULL"
                                                        (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
                                                        (WW) NVIDIA(0): Unable to get display device for DPI computation.
                                                        (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
                                                        (--) Depth 24 pixmap format is 32 bpp
                                                        (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
                                                        (II) NVIDIA:     access.
                                                        (WW) NVIDIA(0): ACPI: AC power state information is not available under
                                                        (WW) NVIDIA(0):     /sys/class/power_supply/ , nor under
                                                        (WW) NVIDIA(0):     /proc/acpi/ac_adapter/
                                                        (II) NVIDIA(0): Built-in logo is bigger than the screen.
                                                        (II) NVIDIA(0): Setting mode "NULL"
                                                        (==) NVIDIA(0): Disabling shared memory pixmaps
                                                        (==) NVIDIA(0): Backing store enabled
                                                        (==) NVIDIA(0): Silken mouse enabled
                                                        (**) NVIDIA(0): DPMS enabled
                                                        

                                                        Here is my current xorg.conf:

                                                        # nvidia-xconfig: X configuration file generated by nvidia-xconfig
                                                        # nvidia-xconfig:  version 367.35  (buildmeister@swio-display-x64-rhel04-01)  Mon Jul 11 23:51:45 PDT 2016
                                                        
                                                        
                                                        Section "ServerLayout"
                                                            Identifier     "Layout0"
                                                            Screen      0  "Screen0" 0 0
                                                            InputDevice    "Keyboard0" "CoreKeyboard"
                                                            InputDevice    "Mouse0" "CorePointer"
                                                        EndSection
                                                        
                                                        Section "InputDevice"
                                                        
                                                            # generated from default
                                                            Identifier     "Mouse0"
                                                            Driver         "mouse"
                                                            Option         "Protocol" "auto"
                                                            Option         "Device" "/dev/psaux"
                                                            Option         "Emulate3Buttons" "no"
                                                            Option         "ZAxisMapping" "4 5"
                                                        EndSection
                                                        
                                                        Section "InputDevice"
                                                        
                                                            # generated from default
                                                            Identifier     "Keyboard0"
                                                            Driver         "kbd"
                                                        EndSection
                                                        
                                                        Section "Monitor"
                                                            Identifier     "Monitor0"
                                                            VendorName     "LaptopBuiltin"
                                                            ModelName      "eDP1"
                                                            HorizSync       28.0 - 33.0
                                                            VertRefresh     43.0 - 72.0
                                                            Option         "DPMS"
                                                        EndSection
                                                        
                                                        Section "Device"
                                                            Identifier     "Device0"
                                                            Driver         "nvidia"
                                                            VendorName     "NVIDIA Corporation"
                                                            #BusId          "PCI:1:0:0"
                                                        EndSection
                                                        
                                                        Section "Screen"
                                                            Identifier     "Screen0"
                                                            Device         "Device0"
                                                            Monitor        "Monitor0"
                                                            DefaultDepth    24
                                                            SubSection     "Display"
                                                                Depth       24
                                                            EndSubSection
                                                        EndSection
                                                        

                                                        share|improve this question

                                                        I have yet another laptop which is a casualty of the proprietary Nvidia driver. I would like to do CUDA development on the laptop (Dell Precision 5510 with Quadro M1000M and 4k display), so I want the proprietary driver.

                                                        I have tried for several hours now, even reading through this, and I just don’t know how to configure xorg when it won’t autoconfigure. I used nvidia-xconfig to set my xorg.conf initially, then I had to add a BusID setting to the Device section in order to find the card. Now, startx runs without errors (and I can verify things are actually working), but it’s like it’s only showing on a ghost screen. I can run DISPLAY=:0 xrandr remotely and I get a 8×8 virtual screen with no outputs:

                                                        Screen 0: minimum 8 x 8, current 8 x 8, maximum 16384 x 16384
                                                        

                                                        I get the following chunk of Nvidia-related output in my xorg log file, with a couple of suspicious NULL values:

                                                        (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 16 22:35:15 2016
                                                        (==) Using config file: "/etc/X11/xorg.conf"
                                                        (==) Using system config directory "/usr/share/X11/xorg.conf.d"
                                                        (==) ServerLayout "Layout0"
                                                        (**) |-->Screen "Screen0" (0)
                                                        (**) |   |-->Monitor "Monitor0"
                                                        (**) |   |-->Device "Device0"
                                                        (**) |-->Input Device "Keyboard0"
                                                        (**) |-->Input Device "Mouse0"
                                                        
                                                        ...
                                                        
                                                        (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
                                                        (==) NVIDIA(0): RGB weight 888
                                                        (==) NVIDIA(0): Default visual is TrueColor
                                                        (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
                                                        (**) NVIDIA(0): Enabling 2D acceleration
                                                        (II) NVIDIA(0): NVIDIA GPU Quadro M1000M (GM107GL-A) at PCI:1:0:0 (GPU-0)
                                                        (--) NVIDIA(0): Memory: 2097152 kBytes
                                                        (--) NVIDIA(0): VideoBIOS: 82.07.82.00.23
                                                        (II) NVIDIA(0): Detected PCI Express Link width: 16X
                                                        (II) NVIDIA(0): Validated MetaModes:
                                                        (II) NVIDIA(0):     "NULL"
                                                        (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
                                                        (WW) NVIDIA(0): Unable to get display device for DPI computation.
                                                        (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
                                                        (--) Depth 24 pixmap format is 32 bpp
                                                        (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
                                                        (II) NVIDIA:     access.
                                                        (WW) NVIDIA(0): ACPI: AC power state information is not available under
                                                        (WW) NVIDIA(0):     /sys/class/power_supply/ , nor under
                                                        (WW) NVIDIA(0):     /proc/acpi/ac_adapter/
                                                        (II) NVIDIA(0): Built-in logo is bigger than the screen.
                                                        (II) NVIDIA(0): Setting mode "NULL"
                                                        (==) NVIDIA(0): Disabling shared memory pixmaps
                                                        (==) NVIDIA(0): Backing store enabled
                                                        (==) NVIDIA(0): Silken mouse enabled
                                                        (**) NVIDIA(0): DPMS enabled
                                                        

                                                        Here is my current xorg.conf:

                                                        # nvidia-xconfig: X configuration file generated by nvidia-xconfig
                                                        # nvidia-xconfig:  version 367.35  (buildmeister@swio-display-x64-rhel04-01)  Mon Jul 11 23:51:45 PDT 2016
                                                        
                                                        
                                                        Section "ServerLayout"
                                                            Identifier     "Layout0"
                                                            Screen      0  "Screen0" 0 0
                                                            InputDevice    "Keyboard0" "CoreKeyboard"
                                                            InputDevice    "Mouse0" "CorePointer"
                                                        EndSection
                                                        
                                                        Section "InputDevice"
                                                        
                                                            # generated from default
                                                            Identifier     "Mouse0"
                                                            Driver         "mouse"
                                                            Option         "Protocol" "auto"
                                                            Option         "Device" "/dev/psaux"
                                                            Option         "Emulate3Buttons" "no"
                                                            Option         "ZAxisMapping" "4 5"
                                                        EndSection
                                                        
                                                        Section "InputDevice"
                                                        
                                                            # generated from default
                                                            Identifier     "Keyboard0"
                                                            Driver         "kbd"
                                                        EndSection
                                                        
                                                        Section "Monitor"
                                                            Identifier     "Monitor0"
                                                            VendorName     "LaptopBuiltin"
                                                            ModelName      "eDP1"
                                                            HorizSync       28.0 - 33.0
                                                            VertRefresh     43.0 - 72.0
                                                            Option         "DPMS"
                                                        EndSection
                                                        
                                                        Section "Device"
                                                            Identifier     "Device0"
                                                            Driver         "nvidia"
                                                            VendorName     "NVIDIA Corporation"
                                                            #BusId          "PCI:1:0:0"
                                                        EndSection
                                                        
                                                        Section "Screen"
                                                            Identifier     "Screen0"
                                                            Device         "Device0"
                                                            Monitor        "Monitor0"
                                                            DefaultDepth    24
                                                            SubSection     "Display"
                                                                Depth       24
                                                            EndSubSection
                                                        EndSection
                                                        

                                                        xorg nvidia

                                                        share|improve this question

                                                        share|improve this question

                                                        share|improve this question

                                                        share|improve this question

                                                        asked Jul 17 ’16 at 5:46

                                                        rexronirexroni

                                                        693617

                                                        693617

                                                            1 Answer
                                                            1

                                                            active

                                                            oldest

                                                            votes

                                                            0

                                                            If you’re saying that you previously had no xorg.conf, and that you created it with that content, then I would start simpler. You don’t need all that.

                                                            All you should need to utilize the nvidia driver is:

                                                            Section "Device"
                                                                Identifier "nvidia"
                                                                Driver "nvidia"
                                                            EndSection
                                                            

                                                            You might also need the following for OpenGL:

                                                            Section "Files"
                                                                ModulePath "/usr/lib64/opengl/nvidia"
                                                            EndSection
                                                            

                                                            (exact value depends on your system paths)

                                                            If that still doesn’t work, please post the entire xorg log.

                                                            share|improve this answer

                                                            • Thanks for helping! I tried that xorg file, and it was the same effect as before I put in the BusID: it says it doesn’t find any nvidia devices, and then my xserver works but I don’t have any GLX support (though in the log I can see it tried to do GLX). I also didn’t find any opengl folder except in something related to LibreOffice. On the other hand, if I specify the BusID, I get the same situation as mentioned above, with GLX working but no visible X server. Would you like the with- or without-BusID xorg log file? Or both?

                                                              – rexroni
                                                              Jul 17 ’16 at 19:24

                                                            Your Answer

                                                            StackExchange.ready(function() {
                                                            var channelOptions = {
                                                            tags: “”.split(” “),
                                                            id: “106”
                                                            };
                                                            initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                                            StackExchange.using(“externalEditor”, function() {
                                                            // Have to fire editor after snippets, if snippets enabled
                                                            if (StackExchange.settings.snippets.snippetsEnabled) {
                                                            StackExchange.using(“snippets”, function() {
                                                            createEditor();
                                                            });
                                                            }
                                                            else {
                                                            createEditor();
                                                            }
                                                            });

                                                            function createEditor() {
                                                            StackExchange.prepareEditor({
                                                            heartbeatType: ‘answer’,
                                                            autoActivateHeartbeat: false,
                                                            convertImagesToLinks: false,
                                                            noModals: true,
                                                            showLowRepImageUploadWarning: true,
                                                            reputationToPostImages: null,
                                                            bindNavPrevention: true,
                                                            postfix: “”,
                                                            imageUploader: {
                                                            brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                                            contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                                            allowUrls: true
                                                            },
                                                            onDemand: true,
                                                            discardSelector: “.discard-answer”
                                                            ,immediatelyShowMarkdownHelp:true
                                                            });

                                                            }
                                                            });

                                                            draft saved
                                                            draft discarded

                                                            StackExchange.ready(
                                                            function () {
                                                            StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f296406%2fxorg-conf-leaves-me-with-no-visible-output%23new-answer’, ‘question_page’);
                                                            }
                                                            );

                                                            Post as a guest

                                                            Required, but never shown

                                                            1 Answer
                                                            1

                                                            active

                                                            oldest

                                                            votes

                                                            1 Answer
                                                            1

                                                            active

                                                            oldest

                                                            votes

                                                            active

                                                            oldest

                                                            votes

                                                            active

                                                            oldest

                                                            votes

                                                            0

                                                            If you’re saying that you previously had no xorg.conf, and that you created it with that content, then I would start simpler. You don’t need all that.

                                                            All you should need to utilize the nvidia driver is:

                                                            Section "Device"
                                                                Identifier "nvidia"
                                                                Driver "nvidia"
                                                            EndSection
                                                            

                                                            You might also need the following for OpenGL:

                                                            Section "Files"
                                                                ModulePath "/usr/lib64/opengl/nvidia"
                                                            EndSection
                                                            

                                                            (exact value depends on your system paths)

                                                            If that still doesn’t work, please post the entire xorg log.

                                                            share|improve this answer

                                                            • Thanks for helping! I tried that xorg file, and it was the same effect as before I put in the BusID: it says it doesn’t find any nvidia devices, and then my xserver works but I don’t have any GLX support (though in the log I can see it tried to do GLX). I also didn’t find any opengl folder except in something related to LibreOffice. On the other hand, if I specify the BusID, I get the same situation as mentioned above, with GLX working but no visible X server. Would you like the with- or without-BusID xorg log file? Or both?

                                                              – rexroni
                                                              Jul 17 ’16 at 19:24

                                                            0

                                                            If you’re saying that you previously had no xorg.conf, and that you created it with that content, then I would start simpler. You don’t need all that.

                                                            All you should need to utilize the nvidia driver is:

                                                            Section "Device"
                                                                Identifier "nvidia"
                                                                Driver "nvidia"
                                                            EndSection
                                                            

                                                            You might also need the following for OpenGL:

                                                            Section "Files"
                                                                ModulePath "/usr/lib64/opengl/nvidia"
                                                            EndSection
                                                            

                                                            (exact value depends on your system paths)

                                                            If that still doesn’t work, please post the entire xorg log.

                                                            share|improve this answer

                                                            • Thanks for helping! I tried that xorg file, and it was the same effect as before I put in the BusID: it says it doesn’t find any nvidia devices, and then my xserver works but I don’t have any GLX support (though in the log I can see it tried to do GLX). I also didn’t find any opengl folder except in something related to LibreOffice. On the other hand, if I specify the BusID, I get the same situation as mentioned above, with GLX working but no visible X server. Would you like the with- or without-BusID xorg log file? Or both?

                                                              – rexroni
                                                              Jul 17 ’16 at 19:24

                                                            0

                                                            0

                                                            0

                                                            If you’re saying that you previously had no xorg.conf, and that you created it with that content, then I would start simpler. You don’t need all that.

                                                            All you should need to utilize the nvidia driver is:

                                                            Section "Device"
                                                                Identifier "nvidia"
                                                                Driver "nvidia"
                                                            EndSection
                                                            

                                                            You might also need the following for OpenGL:

                                                            Section "Files"
                                                                ModulePath "/usr/lib64/opengl/nvidia"
                                                            EndSection
                                                            

                                                            (exact value depends on your system paths)

                                                            If that still doesn’t work, please post the entire xorg log.

                                                            share|improve this answer

                                                            If you’re saying that you previously had no xorg.conf, and that you created it with that content, then I would start simpler. You don’t need all that.

                                                            All you should need to utilize the nvidia driver is:

                                                            Section "Device"
                                                                Identifier "nvidia"
                                                                Driver "nvidia"
                                                            EndSection
                                                            

                                                            You might also need the following for OpenGL:

                                                            Section "Files"
                                                                ModulePath "/usr/lib64/opengl/nvidia"
                                                            EndSection
                                                            

                                                            (exact value depends on your system paths)

                                                            If that still doesn’t work, please post the entire xorg log.

                                                            share|improve this answer

                                                            share|improve this answer

                                                            share|improve this answer

                                                            answered Jul 17 ’16 at 6:16

                                                            PatrickPatrick

                                                            50.8k11132181

                                                            50.8k11132181

                                                            • Thanks for helping! I tried that xorg file, and it was the same effect as before I put in the BusID: it says it doesn’t find any nvidia devices, and then my xserver works but I don’t have any GLX support (though in the log I can see it tried to do GLX). I also didn’t find any opengl folder except in something related to LibreOffice. On the other hand, if I specify the BusID, I get the same situation as mentioned above, with GLX working but no visible X server. Would you like the with- or without-BusID xorg log file? Or both?

                                                              – rexroni
                                                              Jul 17 ’16 at 19:24

                                                            • Thanks for helping! I tried that xorg file, and it was the same effect as before I put in the BusID: it says it doesn’t find any nvidia devices, and then my xserver works but I don’t have any GLX support (though in the log I can see it tried to do GLX). I also didn’t find any opengl folder except in something related to LibreOffice. On the other hand, if I specify the BusID, I get the same situation as mentioned above, with GLX working but no visible X server. Would you like the with- or without-BusID xorg log file? Or both?

                                                              – rexroni
                                                              Jul 17 ’16 at 19:24

                                                            Thanks for helping! I tried that xorg file, and it was the same effect as before I put in the BusID: it says it doesn’t find any nvidia devices, and then my xserver works but I don’t have any GLX support (though in the log I can see it tried to do GLX). I also didn’t find any opengl folder except in something related to LibreOffice. On the other hand, if I specify the BusID, I get the same situation as mentioned above, with GLX working but no visible X server. Would you like the with- or without-BusID xorg log file? Or both?

                                                            – rexroni
                                                            Jul 17 ’16 at 19:24

                                                            Thanks for helping! I tried that xorg file, and it was the same effect as before I put in the BusID: it says it doesn’t find any nvidia devices, and then my xserver works but I don’t have any GLX support (though in the log I can see it tried to do GLX). I also didn’t find any opengl folder except in something related to LibreOffice. On the other hand, if I specify the BusID, I get the same situation as mentioned above, with GLX working but no visible X server. Would you like the with- or without-BusID xorg log file? Or both?

                                                            – rexroni
                                                            Jul 17 ’16 at 19:24

                                                            draft saved
                                                            draft discarded

                                                            Thanks for contributing an answer to Unix & Linux Stack Exchange!

                                                            • Please be sure to answer the question. Provide details and share your research!

                                                            But avoid

                                                            • Asking for help, clarification, or responding to other answers.
                                                            • Making statements based on opinion; back them up with references or personal experience.

                                                            To learn more, see our tips on writing great answers.

                                                            draft saved

                                                            draft discarded

                                                            StackExchange.ready(
                                                            function () {
                                                            StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f296406%2fxorg-conf-leaves-me-with-no-visible-output%23new-answer’, ‘question_page’);
                                                            }
                                                            );

                                                            Post as a guest

                                                            Required, but never shown

                                                            Required, but never shown

                                                            Required, but never shown

                                                            Required, but never shown

                                                            Required, but never shown

                                                            Required, but never shown

                                                            Required, but never shown

                                                            Required, but never shown

                                                            Required, but never shown

                                                            A tool for automatically applying RandR configuration when external display is plugged in

                                                            The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

                                                            50

                                                            is there a tool which enables one to:

                                                            • remember current RandR configuration (position, orientation, resolution etc) on per-monitor basis,
                                                            • automatically apply last known good configuration as soon as the display is plugged in, with no need to muck around with applets or xrandr(1)?

                                                            The configurations would have to be applied on a per-user, per-display basis.

                                                            If there is no such tool in the wild, I’d like to throw together one myself, but as far as I can see, there’s no way to tell that a monitor has been plugged in. Do I have to poll with xrandr -q once in a while to figure out that an output was connected or disconnected, or is there a more efficient way to do it? Can udev be tuned to do just that?

                                                            share|improve this question

                                                            • Are you sure there is no way to tell that a monitor has been plugged in with your card. Try running udevadm monitor --property from the terminal and plugging the monitor in. With my card, I see an event when it is plugged in. You may be able to use a +RUN rule in udev and some bash scripting to get what you want. However, I’m not sure how you would be able to implement this on a per user basis using udev.

                                                              – Steven D
                                                              Dec 3 ’10 at 1:58

                                                            • @Steven: Your comment should be an answer. It’s not a complete answer, but it does make significant progress. If udev does see a hardware event, it should notify hal which sends a dbus event which can be seen by user code.

                                                              – Gilles
                                                              Dec 3 ’10 at 19:39

                                                            50

                                                            is there a tool which enables one to:

                                                            • remember current RandR configuration (position, orientation, resolution etc) on per-monitor basis,
                                                            • automatically apply last known good configuration as soon as the display is plugged in, with no need to muck around with applets or xrandr(1)?

                                                            The configurations would have to be applied on a per-user, per-display basis.

                                                            If there is no such tool in the wild, I’d like to throw together one myself, but as far as I can see, there’s no way to tell that a monitor has been plugged in. Do I have to poll with xrandr -q once in a while to figure out that an output was connected or disconnected, or is there a more efficient way to do it? Can udev be tuned to do just that?

                                                            share|improve this question

                                                            • Are you sure there is no way to tell that a monitor has been plugged in with your card. Try running udevadm monitor --property from the terminal and plugging the monitor in. With my card, I see an event when it is plugged in. You may be able to use a +RUN rule in udev and some bash scripting to get what you want. However, I’m not sure how you would be able to implement this on a per user basis using udev.

                                                              – Steven D
                                                              Dec 3 ’10 at 1:58

                                                            • @Steven: Your comment should be an answer. It’s not a complete answer, but it does make significant progress. If udev does see a hardware event, it should notify hal which sends a dbus event which can be seen by user code.

                                                              – Gilles
                                                              Dec 3 ’10 at 19:39

                                                            50

                                                            50

                                                            50

                                                            23

                                                            is there a tool which enables one to:

                                                            • remember current RandR configuration (position, orientation, resolution etc) on per-monitor basis,
                                                            • automatically apply last known good configuration as soon as the display is plugged in, with no need to muck around with applets or xrandr(1)?

                                                            The configurations would have to be applied on a per-user, per-display basis.

                                                            If there is no such tool in the wild, I’d like to throw together one myself, but as far as I can see, there’s no way to tell that a monitor has been plugged in. Do I have to poll with xrandr -q once in a while to figure out that an output was connected or disconnected, or is there a more efficient way to do it? Can udev be tuned to do just that?

                                                            share|improve this question

                                                            is there a tool which enables one to:

                                                            • remember current RandR configuration (position, orientation, resolution etc) on per-monitor basis,
                                                            • automatically apply last known good configuration as soon as the display is plugged in, with no need to muck around with applets or xrandr(1)?

                                                            The configurations would have to be applied on a per-user, per-display basis.

                                                            If there is no such tool in the wild, I’d like to throw together one myself, but as far as I can see, there’s no way to tell that a monitor has been plugged in. Do I have to poll with xrandr -q once in a while to figure out that an output was connected or disconnected, or is there a more efficient way to do it? Can udev be tuned to do just that?

                                                            linux xorg udev xrandr

                                                            share|improve this question

                                                            share|improve this question

                                                            share|improve this question

                                                            share|improve this question

                                                            asked Dec 2 ’10 at 14:12

                                                            Yaroslav FedevychYaroslav Fedevych

                                                            383137

                                                            383137

                                                            • Are you sure there is no way to tell that a monitor has been plugged in with your card. Try running udevadm monitor --property from the terminal and plugging the monitor in. With my card, I see an event when it is plugged in. You may be able to use a +RUN rule in udev and some bash scripting to get what you want. However, I’m not sure how you would be able to implement this on a per user basis using udev.

                                                              – Steven D
                                                              Dec 3 ’10 at 1:58

                                                            • @Steven: Your comment should be an answer. It’s not a complete answer, but it does make significant progress. If udev does see a hardware event, it should notify hal which sends a dbus event which can be seen by user code.

                                                              – Gilles
                                                              Dec 3 ’10 at 19:39

                                                            • Are you sure there is no way to tell that a monitor has been plugged in with your card. Try running udevadm monitor --property from the terminal and plugging the monitor in. With my card, I see an event when it is plugged in. You may be able to use a +RUN rule in udev and some bash scripting to get what you want. However, I’m not sure how you would be able to implement this on a per user basis using udev.

                                                              – Steven D
                                                              Dec 3 ’10 at 1:58

                                                            • @Steven: Your comment should be an answer. It’s not a complete answer, but it does make significant progress. If udev does see a hardware event, it should notify hal which sends a dbus event which can be seen by user code.

                                                              – Gilles
                                                              Dec 3 ’10 at 19:39

                                                            Are you sure there is no way to tell that a monitor has been plugged in with your card. Try running udevadm monitor --property from the terminal and plugging the monitor in. With my card, I see an event when it is plugged in. You may be able to use a +RUN rule in udev and some bash scripting to get what you want. However, I’m not sure how you would be able to implement this on a per user basis using udev.

                                                            – Steven D
                                                            Dec 3 ’10 at 1:58

                                                            Are you sure there is no way to tell that a monitor has been plugged in with your card. Try running udevadm monitor --property from the terminal and plugging the monitor in. With my card, I see an event when it is plugged in. You may be able to use a +RUN rule in udev and some bash scripting to get what you want. However, I’m not sure how you would be able to implement this on a per user basis using udev.

                                                            – Steven D
                                                            Dec 3 ’10 at 1:58

                                                            @Steven: Your comment should be an answer. It’s not a complete answer, but it does make significant progress. If udev does see a hardware event, it should notify hal which sends a dbus event which can be seen by user code.

                                                            – Gilles
                                                            Dec 3 ’10 at 19:39

                                                            @Steven: Your comment should be an answer. It’s not a complete answer, but it does make significant progress. If udev does see a hardware event, it should notify hal which sends a dbus event which can be seen by user code.

                                                            – Gilles
                                                            Dec 3 ’10 at 19:39

                                                            11 Answers
                                                            11

                                                            active

                                                            oldest

                                                            votes

                                                            17

                                                            +50

                                                            I’m using this simple (homemade) script that keeps polling RandR and switches between LVDS1 and VGA1 when VGA gets connected/disconnected. (For HDMI outputs, in the following script file, change all the VGA1 to HDMI1)

                                                            It’s a dirty solution, yet it’s working just fine.

                                                            It’s customized for my setup: you’ll most likely need to change RandR output names (LVDS1 and VGA1) and unlike me you’ll probably be fine with your RandR default mode for VGA.

                                                            #!/bin/bash
                                                            
                                                            # setting up new mode for my VGA
                                                            xrandr --newmode "1920x1080" 148.5 1920 2008 2052 2200 1080 1089 1095 1125 +hsync +vsync
                                                            xrandr --addmode VGA1 1920x1080
                                                            
                                                            # default monitor is LVDS1
                                                            MONITOR=LVDS1
                                                            
                                                            # functions to switch from LVDS1 to VGA and vice versa
                                                            function ActivateVGA {
                                                                echo "Switching to VGA1"
                                                                xrandr --output VGA1 --mode 1920x1080 --dpi 160 --output LVDS1 --off
                                                                MONITOR=VGA1
                                                            }
                                                            function DeactivateVGA {
                                                                echo "Switching to LVDS1"
                                                                xrandr --output VGA1 --off --output LVDS1 --auto
                                                                MONITOR=LVDS1
                                                            }
                                                            
                                                            # functions to check if VGA is connected and in use
                                                            function VGAActive {
                                                                [ $MONITOR = "VGA1" ]
                                                            }
                                                            function VGAConnected {
                                                                ! xrandr | grep "^VGA1" | grep disconnected
                                                            }
                                                            
                                                            # actual script
                                                            while true
                                                            do
                                                                if ! VGAActive && VGAConnected
                                                                then
                                                                    ActivateVGA
                                                                fi
                                                            
                                                                if VGAActive && ! VGAConnected
                                                                then
                                                                    DeactivateVGA
                                                                fi
                                                            
                                                                sleep 1s
                                                            done
                                                            

                                                            Full Steps:

                                                            1. Open Terminal by pressing Ctrl+Alt+t
                                                            2. Navigate to a good location to make and store the auto-switching shell script. Example

                                                              cd ./Desktop/

                                                            3. Create and edit the .sh file with your desired text editor (here, I used pluma. You can try nano, vim, etc). Name it to your convenience. Example

                                                              sudo pluma homemadeMonitor.sh

                                                            4. Edit the file and copy paste everything from the above mentioned script (the one with #!/bin/bash)

                                                            5. Make the .sh file executable by typing the following command in the terminal

                                                              sudo chmod +x homemadeMonitor.sh

                                                            6. Run the .sh file

                                                              ./homemadeMonitor.sh

                                                            share|improve this answer

                                                            • Good script! Thanks, I needed something like this. I just copied it and set it up to run automatically. Thanks!

                                                              – Linuxios
                                                              Jan 31 ’12 at 23:20

                                                            21

                                                            Responding to the “[a] way to tell that a monitor has been plugged in” part of the question:

                                                            The support still varies quite a bit, but with recent kernels there is some support for generating udev events when a display hotplug occurs. With kernel 2.6.38 and ATI X1400 hardware, I get an event the first time I connect a VGA display but no events on subsequent disconnects or reconnects of the display. Intel hardware may have better support. The NVIDIA proprietary driver does not currently support KMS; I haven’t tried looking for hotplug events on NVIDIA hardware, but I’m doubtful it would work.

                                                            If you want to experiment with udev you could try the following steps:

                                                            • update to the newest kernel
                                                            • make sure that kernel mode setting (KMS) is enabled. If enabled, it should be reported in your kernel output. Mine says [drm] radeon kernel modesetting enabled and [drm] initializing kernel modesetting
                                                            • run udevadm monitor --property and see if events are reported when you (dis-)connect displays

                                                            If you are getting udev events on display hotplug, you can trigger a script with a udev rule like:

                                                            ACTION=="change", SUBSYSTEM=="drm", HOTPLUG=="1", RUN+="/path/to/hotplug.sh"
                                                            

                                                            Note: This will not work if you use an nVIDIA GPU with the proprietary binary driver, since it does not use KMS. You will not get any udev events.

                                                            share|improve this answer

                                                              18

                                                              Regarding a tool which can store monitor configuration profiles on a per-user and per-display basis, autorandr will do exactly that. https://github.com/wertarbyte/autorandr.

                                                              My laptop has an NVIDIA card, so I use the disper backend instead of xrandr: http://willem.engen.nl/projects/disper/. Autorandr will use disper as the backend to manage your monitors if you call it as autodisper. For the rest of this post though, I’ll refer to it as autorandr for consistency.

                                                              You can save profiles with autorandr --save profile_name. Running autorandr by itself will then give you a list of profiles, and identify which one is detected as the current configuration.

                                                              For instance:

                                                              $ autorandr
                                                              laptop
                                                              syncmaster19 (detected)
                                                              

                                                              You can tell it to automatically load the appropriate profile for the current configuration with autorandr --change. This command, paired with a udev rule to run it when it is hotplugged, would do what you requested.

                                                              As an added precaution I’ve appended --default laptop to that command, which will make it default to the laptop’s display if there is no saved profile that matches the current configuration. So the full command I use to switch displays is:

                                                              autorandr --change --default laptop
                                                              

                                                              Unfortunately my machine doesn’t give any udev output when I hotplug my monitor. I’m using the NVIDIA proprietary drivers, so that isn’t surprising. So I have bound it to the XF68Display key (Fn-F8) for now, which is almost as good.

                                                              share|improve this answer

                                                              • 1

                                                                autorandr was a waste of time, bad documented, random monitor blinks, no install/uninstall instructions. Could solve it using udev

                                                                – Leo Gallucci
                                                                Jan 26 ’14 at 15:38

                                                              • 4

                                                                Just in case, there’s a nice maintained rewritten-in-Python fork of autorandr: github.com/phillipberndt/autorandr

                                                                – Olegs Jeremejevs
                                                                Nov 17 ’17 at 13:14

                                                              7

                                                              I used the udev rule suggested above along with a shell script that looks like

                                                              #!/bin/sh
                                                              
                                                              dmode="$(cat /sys/class/drm/card0-VGA-1/status)"
                                                              export DISPLAY=:0
                                                              export XAUTHORITY=/home/yourusername/.Xauthority
                                                              
                                                              if [ "${dmode}" = disconnected ]; then
                                                                   /usr/bin/xrandr --auto
                                                              elif [ "${dmode}" = connected ];then
                                                                   /usr/bin/xrandr --output VGA1 --auto --right-of LVDS1
                                                              else /usr/bin/xrandr --auto
                                                              fi
                                                              

                                                              The Xauthority part is essential as well as the export DISPLAY, you can use echo $DISPLAY to see which number it’s equal to. Use xrandr -q to see the external monitors you have. The last else statement is just to make sure that you’re never stuck without a display.

                                                              share|improve this answer

                                                                6

                                                                A small program that waits for the X server to notify it about changed monitor configuration, and then executes a given command (e.g. the autorandr mentioned in another answer) is available at: https://bitbucket.org/portix/srandrd/overview

                                                                This seems to be a cleaner solution that using udev (where you have to worry about finding the right X server etc.)

                                                                share|improve this answer

                                                                  3

                                                                  If you must have it automatically detect the display when it is plugged in, it seems that the cleanest solution is to add a UDEV rule to run a script containing your xrandr commands. Here is an example from one user’s solution1:

                                                                  Monitor (output) UDEV events with udevadm
                                                                  This step will be most important for each user. Run udevadm monitor --environment --udev. Then connect your HDMI cable.

                                                                  UDEV rule
                                                                  Based on the output from the above command, the user created this UDEV rule at /etc/udev/rules.d/95-monitor-hotplug.rules.

                                                                  KERNEL=="card0", SUBSYSTEM=="drm", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="/home/dan/.Xauthority", RUN+="/usr/local/bin/hotplug_monitor.sh"
                                                                  

                                                                  Note the environment variables used so xrandr will be run under the user profile.

                                                                  xrandr script hotplug_monitor.sh

                                                                  You may want to adjust the xrandr options to suit your needs.

                                                                  #! /usr/bin/bash
                                                                  
                                                                  export DISPLAY=:0
                                                                  export XAUTHORITY=/home/dan/.Xauthority
                                                                  
                                                                  function connect(){
                                                                      xrandr --output HDMI1 --right-of LVDS1 --preferred --primary --output LVDS1 --preferred 
                                                                  }
                                                                  
                                                                  function disconnect(){
                                                                        xrandr --output HDMI1 --off
                                                                  }
                                                                  
                                                                  xrandr | grep "HDMI1 connected" &> /dev/null && connect || disconnect
                                                                  

                                                                  share|improve this answer

                                                                    3

                                                                    For those who, for whatever reason, don’t want to take the hotplug route, it is still possible to not poll within a script using inotifywait:

                                                                    #!/bin/bash
                                                                    
                                                                    SCREEN_LEFT=DP2
                                                                    SCREEN_RIGHT=eDP1
                                                                    START_DELAY=5
                                                                    
                                                                    renice +19 $$ >/dev/null
                                                                    
                                                                    sleep $START_DELAY
                                                                    
                                                                    OLD_DUAL="dummy"
                                                                    
                                                                    while [ 1 ]; do
                                                                        DUAL=$(cat /sys/class/drm/card0-DP-2/status)
                                                                    
                                                                        if [ "$OLD_DUAL" != "$DUAL" ]; then
                                                                            if [ "$DUAL" == "connected" ]; then
                                                                                echo 'Dual monitor setup'
                                                                                xrandr --output $SCREEN_LEFT --auto --rotate normal --pos 0x0 --output $SCREEN_RIGHT --auto --rotate normal --below $SCREEN_LEFT
                                                                            else
                                                                                echo 'Single monitor setup'
                                                                                xrandr --auto
                                                                            fi
                                                                    
                                                                            OLD_DUAL="$DUAL"
                                                                        fi
                                                                    
                                                                        inotifywait -q -e close /sys/class/drm/card0-DP-2/status >/dev/null
                                                                    done
                                                                    
                                                                    

                                                                    Polling with xrandr gave serious usability issues on my brand new laptop (mouse would stall periodically).

                                                                    share|improve this answer

                                                                      1

                                                                      When using peoro’s solution, I got some extra output from xrandr, so I used the -c option for grep which counts the number of matches. I adapted it for HDMI and added audio switch as well:

                                                                      #!/bin/bash
                                                                      # adapted from http://unix.stackexchange.com/questions/4489/
                                                                      
                                                                      # default monitor is LVDS1
                                                                      MONITOR=LVDS1
                                                                      
                                                                      # functions to switch from LVDS1 to HDMI1
                                                                      function ActivateHDMI {
                                                                          xrandr --output HDMI1 --mode 1920x1080 --dpi 160 --output LVDS1 --off
                                                                          pactl set-card-profile 0 output:hdmi-stereo-extra1
                                                                          MONITOR=HDMI1
                                                                      }
                                                                      function DeactivateHDMI {
                                                                          xrandr --output HDMI1 --off --output LVDS1 --auto
                                                                          pactl set-card-profile 0 output:analog-stereo
                                                                          MONITOR=LVDS1
                                                                      }
                                                                      
                                                                      # functions to check if HDMI is connected and in use
                                                                      function HDMIActive {
                                                                          [ $MONITOR = "HDMI1" ]
                                                                      }
                                                                      function HDMIConnected {
                                                                          [[ `xrandr | grep "^HDMI1" | grep -c disconnected` -eq 0 ]]
                                                                      }
                                                                      
                                                                      # actual script
                                                                      while true
                                                                      do
                                                                          if ! HDMIActive && HDMIConnected
                                                                          then
                                                                              ActivateHDMI
                                                                          fi
                                                                      
                                                                          if HDMIActive && ! HDMIConnected
                                                                          then
                                                                              DeactivateHDMI
                                                                          fi
                                                                      
                                                                          sleep 1s
                                                                      done
                                                                      

                                                                      share|improve this answer

                                                                        1

                                                                        I guess people looking at this question are not those that want to use GNOME, and those that use GNOME wouldn’t have to look at this question, but in the interest of completeness:

                                                                        GNOME has this functionality built-in. If you change the setup via gnome-control-center, gnome-settings-daemon remembers it (in .config/monitors.xml) and automatically applies it when a monitor is plugged in or out.

                                                                        Sadly the configuration in monitors.xml file is not well documented. See question here. The gnome display tooling also has no means of setting up panning, scaling per monitor and it doesn’t do zoom-out. As many people are using a HiDPI laptop screen together with a regular DPI screen the tools are not enough to get a workable solution.

                                                                        I have seen this mentioned as a roadmap item for Wayland though so when it finally comes we might see a fix for the issues mentioned. Till then on Gnome I just run a startup script after a delay to setup xrandr manually.

                                                                        share|improve this answer

                                                                          1

                                                                          To simplify in Xfce for example please install “arandr” which should be available in your distro packages. Configure your display using “arandr” then save it as “displayLayout” for example. Arandr should add for you “.sh” extension so it can be directly used in “function connect()” as written in the script “hotplug_monitor.sh” mentioned by iyrin above, for example:

                                                                          function connect(){
                                                                           /path/to/displayLayout.sh
                                                                          }
                                                                          

                                                                          To use disconnect mechanism add at the top of the script just below “#!/bin/bash” like so:

                                                                          #!/bin/bash
                                                                          #
                                                                          PLUGGED_EXTERNAL=`xrandr | awk /"connected [0-9]"/'{print $1}'`
                                                                          

                                                                          xrandr will detect the display and pass output to awk which will filter it based on regular expression “connected” followed by a digit which in essence is what we want. In my opinion it is not necessary to match exact resolution in regular expression because primary display is reported as “connected primary” followed by number i.e. resolution. Then awk “print $1” will print only first column which is the name of external monitor in this case and this will be stored in PLUGGED_EXTERNAL variable. Next instead of fixed display name “HDMI1” in the script $PLUGGED_EXTERNAL can be used like so:

                                                                          function disconnect(){
                                                                            xrandr --output $PLUGGED_EXTERNAL --off
                                                                          }
                                                                          
                                                                          xrandr | grep "$PLUGGED_EXTERNAL connected" &> /dev/null && connect || disconnect
                                                                          

                                                                          share|improve this answer

                                                                            0

                                                                            Editing my answer to make it simpler to setup.

                                                                            Install autorandr to automate screen layout in xrandr, grab latest .deb from https://github.com/nalipaz/autorandr/releases and run:

                                                                            dpkg -i [file]
                                                                            

                                                                            Setup autorandr with stored screen layouts

                                                                            autorandr --save [docked|mobile|home|etc]
                                                                            

                                                                            As an example, on my laptop without any monitors plugged in, I setup arandr the way I want it, then ran:

                                                                            autorandr --save mobile
                                                                            

                                                                            Then plugged in my hdmi and reconfigured arandr, then ran:

                                                                            autorandr --save docked
                                                                            

                                                                            After setting up each of your layouts you can run (replace ‘mobile’ with previous favored name, I used mobile):

                                                                            autorandr --default mobile
                                                                            

                                                                            Now that autorandr is all setup you can automate the process by installing a package which will poll for connected displays and run autorandr --change upon detection. Yes, I know about udev and you can set that up if it works for you, but in my testing udev didn’t work for my hdmi consistently. It only worked 1 out of every 20 plugs/unplugs or so, and sometimes it just stopped altogether.

                                                                            Download the latest .deb from here: https://github.com/nalipaz/poll-xrandr/releases/ then install with

                                                                            dpkg -i [file]
                                                                            

                                                                            It is most likely necessary that you run more tasks upon completion of autorandr --change, autorandr allows for these commands to be inserted into a file called ~/.autorandr/postswitch. Do as follows:

                                                                            cd ~/.autorandr/ && touch postswitch && chmod +x postswitch
                                                                            

                                                                            Now edit the postswitch file to have something similar to the following:

                                                                            #!/bin/bash
                                                                            if pidof conky > /dev/null 2>&1; then
                                                                              killall conky
                                                                            fi
                                                                            (sleep 2s && xrandr-adjust-brightness restore -q) &
                                                                            (sleep 2s && nitrogen --restore) &
                                                                            (sleep 3s && conky -q) &
                                                                            

                                                                            Additionally you will likely want to add autorandr and poll-xrandr to your startups, something like the following two commands:

                                                                            autorandr --change &
                                                                            poll-xrandr &
                                                                            

                                                                            Unplug or plug in a monitor and watch the magic!

                                                                            share|improve this answer

                                                                              Your Answer

                                                                              StackExchange.ready(function() {
                                                                              var channelOptions = {
                                                                              tags: “”.split(” “),
                                                                              id: “106”
                                                                              };
                                                                              initTagRenderer(“”.split(” “), “”.split(” “), channelOptions);

                                                                              StackExchange.using(“externalEditor”, function() {
                                                                              // Have to fire editor after snippets, if snippets enabled
                                                                              if (StackExchange.settings.snippets.snippetsEnabled) {
                                                                              StackExchange.using(“snippets”, function() {
                                                                              createEditor();
                                                                              });
                                                                              }
                                                                              else {
                                                                              createEditor();
                                                                              }
                                                                              });

                                                                              function createEditor() {
                                                                              StackExchange.prepareEditor({
                                                                              heartbeatType: ‘answer’,
                                                                              autoActivateHeartbeat: false,
                                                                              convertImagesToLinks: false,
                                                                              noModals: true,
                                                                              showLowRepImageUploadWarning: true,
                                                                              reputationToPostImages: null,
                                                                              bindNavPrevention: true,
                                                                              postfix: “”,
                                                                              imageUploader: {
                                                                              brandingHtml: “Powered by u003ca class=”icon-imgur-white” href=”https://imgur.com/”u003eu003c/au003e”,
                                                                              contentPolicyHtml: “User contributions licensed under u003ca href=”https://creativecommons.org/licenses/by-sa/3.0/”u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href=”https://stackoverflow.com/legal/content-policy”u003e(content policy)u003c/au003e”,
                                                                              allowUrls: true
                                                                              },
                                                                              onDemand: true,
                                                                              discardSelector: “.discard-answer”
                                                                              ,immediatelyShowMarkdownHelp:true
                                                                              });

                                                                              }
                                                                              });

                                                                              draft saved
                                                                              draft discarded

                                                                              StackExchange.ready(
                                                                              function () {
                                                                              StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f4489%2fa-tool-for-automatically-applying-randr-configuration-when-external-display-is-p%23new-answer’, ‘question_page’);
                                                                              }
                                                                              );

                                                                              Post as a guest

                                                                              Required, but never shown

                                                                              11 Answers
                                                                              11

                                                                              active

                                                                              oldest

                                                                              votes

                                                                              11 Answers
                                                                              11

                                                                              active

                                                                              oldest

                                                                              votes

                                                                              active

                                                                              oldest

                                                                              votes

                                                                              active

                                                                              oldest

                                                                              votes

                                                                              17

                                                                              +50

                                                                              I’m using this simple (homemade) script that keeps polling RandR and switches between LVDS1 and VGA1 when VGA gets connected/disconnected. (For HDMI outputs, in the following script file, change all the VGA1 to HDMI1)

                                                                              It’s a dirty solution, yet it’s working just fine.

                                                                              It’s customized for my setup: you’ll most likely need to change RandR output names (LVDS1 and VGA1) and unlike me you’ll probably be fine with your RandR default mode for VGA.

                                                                              #!/bin/bash
                                                                              
                                                                              # setting up new mode for my VGA
                                                                              xrandr --newmode "1920x1080" 148.5 1920 2008 2052 2200 1080 1089 1095 1125 +hsync +vsync
                                                                              xrandr --addmode VGA1 1920x1080
                                                                              
                                                                              # default monitor is LVDS1
                                                                              MONITOR=LVDS1
                                                                              
                                                                              # functions to switch from LVDS1 to VGA and vice versa
                                                                              function ActivateVGA {
                                                                                  echo "Switching to VGA1"
                                                                                  xrandr --output VGA1 --mode 1920x1080 --dpi 160 --output LVDS1 --off
                                                                                  MONITOR=VGA1
                                                                              }
                                                                              function DeactivateVGA {
                                                                                  echo "Switching to LVDS1"
                                                                                  xrandr --output VGA1 --off --output LVDS1 --auto
                                                                                  MONITOR=LVDS1
                                                                              }
                                                                              
                                                                              # functions to check if VGA is connected and in use
                                                                              function VGAActive {
                                                                                  [ $MONITOR = "VGA1" ]
                                                                              }
                                                                              function VGAConnected {
                                                                                  ! xrandr | grep "^VGA1" | grep disconnected
                                                                              }
                                                                              
                                                                              # actual script
                                                                              while true
                                                                              do
                                                                                  if ! VGAActive && VGAConnected
                                                                                  then
                                                                                      ActivateVGA
                                                                                  fi
                                                                              
                                                                                  if VGAActive && ! VGAConnected
                                                                                  then
                                                                                      DeactivateVGA
                                                                                  fi
                                                                              
                                                                                  sleep 1s
                                                                              done
                                                                              

                                                                              Full Steps:

                                                                              1. Open Terminal by pressing Ctrl+Alt+t
                                                                              2. Navigate to a good location to make and store the auto-switching shell script. Example

                                                                                cd ./Desktop/

                                                                              3. Create and edit the .sh file with your desired text editor (here, I used pluma. You can try nano, vim, etc). Name it to your convenience. Example

                                                                                sudo pluma homemadeMonitor.sh

                                                                              4. Edit the file and copy paste everything from the above mentioned script (the one with #!/bin/bash)

                                                                              5. Make the .sh file executable by typing the following command in the terminal

                                                                                sudo chmod +x homemadeMonitor.sh

                                                                              6. Run the .sh file

                                                                                ./homemadeMonitor.sh

                                                                              share|improve this answer

                                                                              • Good script! Thanks, I needed something like this. I just copied it and set it up to run automatically. Thanks!

                                                                                – Linuxios
                                                                                Jan 31 ’12 at 23:20

                                                                              17

                                                                              +50

                                                                              I’m using this simple (homemade) script that keeps polling RandR and switches between LVDS1 and VGA1 when VGA gets connected/disconnected. (For HDMI outputs, in the following script file, change all the VGA1 to HDMI1)

                                                                              It’s a dirty solution, yet it’s working just fine.

                                                                              It’s customized for my setup: you’ll most likely need to change RandR output names (LVDS1 and VGA1) and unlike me you’ll probably be fine with your RandR default mode for VGA.

                                                                              #!/bin/bash
                                                                              
                                                                              # setting up new mode for my VGA
                                                                              xrandr --newmode "1920x1080" 148.5 1920 2008 2052 2200 1080 1089 1095 1125 +hsync +vsync
                                                                              xrandr --addmode VGA1 1920x1080
                                                                              
                                                                              # default monitor is LVDS1
                                                                              MONITOR=LVDS1
                                                                              
                                                                              # functions to switch from LVDS1 to VGA and vice versa
                                                                              function ActivateVGA {
                                                                                  echo "Switching to VGA1"
                                                                                  xrandr --output VGA1 --mode 1920x1080 --dpi 160 --output LVDS1 --off
                                                                                  MONITOR=VGA1
                                                                              }
                                                                              function DeactivateVGA {
                                                                                  echo "Switching to LVDS1"
                                                                                  xrandr --output VGA1 --off --output LVDS1 --auto
                                                                                  MONITOR=LVDS1
                                                                              }
                                                                              
                                                                              # functions to check if VGA is connected and in use
                                                                              function VGAActive {
                                                                                  [ $MONITOR = "VGA1" ]
                                                                              }
                                                                              function VGAConnected {
                                                                                  ! xrandr | grep "^VGA1" | grep disconnected
                                                                              }
                                                                              
                                                                              # actual script
                                                                              while true
                                                                              do
                                                                                  if ! VGAActive && VGAConnected
                                                                                  then
                                                                                      ActivateVGA
                                                                                  fi
                                                                              
                                                                                  if VGAActive && ! VGAConnected
                                                                                  then
                                                                                      DeactivateVGA
                                                                                  fi
                                                                              
                                                                                  sleep 1s
                                                                              done
                                                                              

                                                                              Full Steps:

                                                                              1. Open Terminal by pressing Ctrl+Alt+t
                                                                              2. Navigate to a good location to make and store the auto-switching shell script. Example

                                                                                cd ./Desktop/

                                                                              3. Create and edit the .sh file with your desired text editor (here, I used pluma. You can try nano, vim, etc). Name it to your convenience. Example

                                                                                sudo pluma homemadeMonitor.sh

                                                                              4. Edit the file and copy paste everything from the above mentioned script (the one with #!/bin/bash)

                                                                              5. Make the .sh file executable by typing the following command in the terminal

                                                                                sudo chmod +x homemadeMonitor.sh

                                                                              6. Run the .sh file

                                                                                ./homemadeMonitor.sh

                                                                              share|improve this answer

                                                                              • Good script! Thanks, I needed something like this. I just copied it and set it up to run automatically. Thanks!

                                                                                – Linuxios
                                                                                Jan 31 ’12 at 23:20

                                                                              17

                                                                              +50

                                                                              17

                                                                              +50
                                                                              17

                                                                              +50

                                                                              I’m using this simple (homemade) script that keeps polling RandR and switches between LVDS1 and VGA1 when VGA gets connected/disconnected. (For HDMI outputs, in the following script file, change all the VGA1 to HDMI1)

                                                                              It’s a dirty solution, yet it’s working just fine.

                                                                              It’s customized for my setup: you’ll most likely need to change RandR output names (LVDS1 and VGA1) and unlike me you’ll probably be fine with your RandR default mode for VGA.

                                                                              #!/bin/bash
                                                                              
                                                                              # setting up new mode for my VGA
                                                                              xrandr --newmode "1920x1080" 148.5 1920 2008 2052 2200 1080 1089 1095 1125 +hsync +vsync
                                                                              xrandr --addmode VGA1 1920x1080
                                                                              
                                                                              # default monitor is LVDS1
                                                                              MONITOR=LVDS1
                                                                              
                                                                              # functions to switch from LVDS1 to VGA and vice versa
                                                                              function ActivateVGA {
                                                                                  echo "Switching to VGA1"
                                                                                  xrandr --output VGA1 --mode 1920x1080 --dpi 160 --output LVDS1 --off
                                                                                  MONITOR=VGA1
                                                                              }
                                                                              function DeactivateVGA {
                                                                                  echo "Switching to LVDS1"
                                                                                  xrandr --output VGA1 --off --output LVDS1 --auto
                                                                                  MONITOR=LVDS1
                                                                              }
                                                                              
                                                                              # functions to check if VGA is connected and in use
                                                                              function VGAActive {
                                                                                  [ $MONITOR = "VGA1" ]
                                                                              }
                                                                              function VGAConnected {
                                                                                  ! xrandr | grep "^VGA1" | grep disconnected
                                                                              }
                                                                              
                                                                              # actual script
                                                                              while true
                                                                              do
                                                                                  if ! VGAActive && VGAConnected
                                                                                  then
                                                                                      ActivateVGA
                                                                                  fi
                                                                              
                                                                                  if VGAActive && ! VGAConnected
                                                                                  then
                                                                                      DeactivateVGA
                                                                                  fi
                                                                              
                                                                                  sleep 1s
                                                                              done
                                                                              

                                                                              Full Steps:

                                                                              1. Open Terminal by pressing Ctrl+Alt+t
                                                                              2. Navigate to a good location to make and store the auto-switching shell script. Example

                                                                                cd ./Desktop/

                                                                              3. Create and edit the .sh file with your desired text editor (here, I used pluma. You can try nano, vim, etc). Name it to your convenience. Example

                                                                                sudo pluma homemadeMonitor.sh

                                                                              4. Edit the file and copy paste everything from the above mentioned script (the one with #!/bin/bash)

                                                                              5. Make the .sh file executable by typing the following command in the terminal

                                                                                sudo chmod +x homemadeMonitor.sh

                                                                              6. Run the .sh file

                                                                                ./homemadeMonitor.sh

                                                                              share|improve this answer

                                                                              I’m using this simple (homemade) script that keeps polling RandR and switches between LVDS1 and VGA1 when VGA gets connected/disconnected. (For HDMI outputs, in the following script file, change all the VGA1 to HDMI1)

                                                                              It’s a dirty solution, yet it’s working just fine.

                                                                              It’s customized for my setup: you’ll most likely need to change RandR output names (LVDS1 and VGA1) and unlike me you’ll probably be fine with your RandR default mode for VGA.

                                                                              #!/bin/bash
                                                                              
                                                                              # setting up new mode for my VGA
                                                                              xrandr --newmode "1920x1080" 148.5 1920 2008 2052 2200 1080 1089 1095 1125 +hsync +vsync
                                                                              xrandr --addmode VGA1 1920x1080
                                                                              
                                                                              # default monitor is LVDS1
                                                                              MONITOR=LVDS1
                                                                              
                                                                              # functions to switch from LVDS1 to VGA and vice versa
                                                                              function ActivateVGA {
                                                                                  echo "Switching to VGA1"
                                                                                  xrandr --output VGA1 --mode 1920x1080 --dpi 160 --output LVDS1 --off
                                                                                  MONITOR=VGA1
                                                                              }
                                                                              function DeactivateVGA {
                                                                                  echo "Switching to LVDS1"
                                                                                  xrandr --output VGA1 --off --output LVDS1 --auto
                                                                                  MONITOR=LVDS1
                                                                              }
                                                                              
                                                                              # functions to check if VGA is connected and in use
                                                                              function VGAActive {
                                                                                  [ $MONITOR = "VGA1" ]
                                                                              }
                                                                              function VGAConnected {
                                                                                  ! xrandr | grep "^VGA1" | grep disconnected
                                                                              }
                                                                              
                                                                              # actual script
                                                                              while true
                                                                              do
                                                                                  if ! VGAActive && VGAConnected
                                                                                  then
                                                                                      ActivateVGA
                                                                                  fi
                                                                              
                                                                                  if VGAActive && ! VGAConnected
                                                                                  then
                                                                                      DeactivateVGA
                                                                                  fi
                                                                              
                                                                                  sleep 1s
                                                                              done
                                                                              

                                                                              Full Steps:

                                                                              1. Open Terminal by pressing Ctrl+Alt+t
                                                                              2. Navigate to a good location to make and store the auto-switching shell script. Example

                                                                                cd ./Desktop/

                                                                              3. Create and edit the .sh file with your desired text editor (here, I used pluma. You can try nano, vim, etc). Name it to your convenience. Example

                                                                                sudo pluma homemadeMonitor.sh

                                                                              4. Edit the file and copy paste everything from the above mentioned script (the one with #!/bin/bash)

                                                                              5. Make the .sh file executable by typing the following command in the terminal

                                                                                sudo chmod +x homemadeMonitor.sh

                                                                              6. Run the .sh file

                                                                                ./homemadeMonitor.sh

                                                                              share|improve this answer

                                                                              share|improve this answer

                                                                              share|improve this answer

                                                                              edited Feb 9 at 9:53

                                                                              Abdulla Masud

                                                                              32

                                                                              32

                                                                              answered Apr 23 ’11 at 20:08

                                                                              peoropeoro

                                                                              1,61922523

                                                                              1,61922523

                                                                              • Good script! Thanks, I needed something like this. I just copied it and set it up to run automatically. Thanks!

                                                                                – Linuxios
                                                                                Jan 31 ’12 at 23:20

                                                                              • Good script! Thanks, I needed something like this. I just copied it and set it up to run automatically. Thanks!

                                                                                – Linuxios
                                                                                Jan 31 ’12 at 23:20

                                                                              Good script! Thanks, I needed something like this. I just copied it and set it up to run automatically. Thanks!

                                                                              – Linuxios
                                                                              Jan 31 ’12 at 23:20

                                                                              Good script! Thanks, I needed something like this. I just copied it and set it up to run automatically. Thanks!

                                                                              – Linuxios
                                                                              Jan 31 ’12 at 23:20