Trying to set up monitor rotation (nvidia) in 18.04

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








up vote
1
down vote

favorite












I had this working fine in 16.04 on a very similar machine.



What I want: I want to tell X to start with a particular display rotated, if it's present. I also want to use the nvidia driver, not nouveau, and have decent performance without screen-tearing.



I don't care either way about "nvidia Prime", but so far as I can tell it's why this isn't working, so my guess is I want it burned, purged with fire, destroyed, removed, and otherwise completely prevented from ever interacting with me or my laptop again. I do not care about the marginal impact on battery life.



In Ubuntu 16.04, I could set up xorg.conf, and do this:



 "MetaModes" "DFP-3: 2560x1600 +0+0 rotation=left, ForceCompositionPipeline=On, DFP-4: ForceCompositionPipeline=On"


In 18.04, there does not exist any value that works here, because when nvidia comes up, it says that all devices are disconnected; it is a few seconds later, on further study, that it starts finding things with names like "DP-1-1" which can be connected or probed. But those names don't exist yet when the xorg.conf fragments are read. So the MetaModes line is discarded because it doesn't apply to anything.



I can accept that I may be forced to manually run xrandr later, but it seems stupid. I don't care about, or want, prime. If it would go away, and the nvidia driver would just probe displays normally, I would have the intended behavior.



Is there a setting or hook somewhere needed to tell the nvidia driver to stop trying to overthink this? I can't uninstall nvidia-prime; I mean, I can, but everything breaks then. There's a thing called gpu-manager which keeps forcing everything over to using prime, but also has no documentation, and no --help, and is basically exactly the opposite of good software engineering. If I dummy it out (say, by replacing it with a script that just does nothing), it stops actively breaking things, but things don't actually get fixed. If I disable it, and nuke 11-nvidia-prime.conf, it looks like the nvidia driver ends up not being used at all.



nvidia-settings can't generate a config file anymore ("xorg-server was not found in the pkg-config search path"), and any attempt to use a working config from a basically-identical machine running 16.04 gets no valid screens found, because of the "everything probes as disconnected initially" problem.



I'm sort of guessing that the support for prime has caused it to disable all displays until prime gets a chance to tell it to enable them, but I don't know how to get around that or suppress it.



EDIT: Coming back a bit later, I checked more carefully. Other laptop is also using nvidia-prime, so prime itself is not innately the problem. Older laptop is 16.04 with nvidia-384, newer is 18.04 with nvidia-390. Slightly different generations; older is a quadro M2000, new one is a quadro M2200, I think.







share|improve this question


























    up vote
    1
    down vote

    favorite












    I had this working fine in 16.04 on a very similar machine.



    What I want: I want to tell X to start with a particular display rotated, if it's present. I also want to use the nvidia driver, not nouveau, and have decent performance without screen-tearing.



    I don't care either way about "nvidia Prime", but so far as I can tell it's why this isn't working, so my guess is I want it burned, purged with fire, destroyed, removed, and otherwise completely prevented from ever interacting with me or my laptop again. I do not care about the marginal impact on battery life.



    In Ubuntu 16.04, I could set up xorg.conf, and do this:



     "MetaModes" "DFP-3: 2560x1600 +0+0 rotation=left, ForceCompositionPipeline=On, DFP-4: ForceCompositionPipeline=On"


    In 18.04, there does not exist any value that works here, because when nvidia comes up, it says that all devices are disconnected; it is a few seconds later, on further study, that it starts finding things with names like "DP-1-1" which can be connected or probed. But those names don't exist yet when the xorg.conf fragments are read. So the MetaModes line is discarded because it doesn't apply to anything.



    I can accept that I may be forced to manually run xrandr later, but it seems stupid. I don't care about, or want, prime. If it would go away, and the nvidia driver would just probe displays normally, I would have the intended behavior.



    Is there a setting or hook somewhere needed to tell the nvidia driver to stop trying to overthink this? I can't uninstall nvidia-prime; I mean, I can, but everything breaks then. There's a thing called gpu-manager which keeps forcing everything over to using prime, but also has no documentation, and no --help, and is basically exactly the opposite of good software engineering. If I dummy it out (say, by replacing it with a script that just does nothing), it stops actively breaking things, but things don't actually get fixed. If I disable it, and nuke 11-nvidia-prime.conf, it looks like the nvidia driver ends up not being used at all.



    nvidia-settings can't generate a config file anymore ("xorg-server was not found in the pkg-config search path"), and any attempt to use a working config from a basically-identical machine running 16.04 gets no valid screens found, because of the "everything probes as disconnected initially" problem.



    I'm sort of guessing that the support for prime has caused it to disable all displays until prime gets a chance to tell it to enable them, but I don't know how to get around that or suppress it.



    EDIT: Coming back a bit later, I checked more carefully. Other laptop is also using nvidia-prime, so prime itself is not innately the problem. Older laptop is 16.04 with nvidia-384, newer is 18.04 with nvidia-390. Slightly different generations; older is a quadro M2000, new one is a quadro M2200, I think.







    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I had this working fine in 16.04 on a very similar machine.



      What I want: I want to tell X to start with a particular display rotated, if it's present. I also want to use the nvidia driver, not nouveau, and have decent performance without screen-tearing.



      I don't care either way about "nvidia Prime", but so far as I can tell it's why this isn't working, so my guess is I want it burned, purged with fire, destroyed, removed, and otherwise completely prevented from ever interacting with me or my laptop again. I do not care about the marginal impact on battery life.



      In Ubuntu 16.04, I could set up xorg.conf, and do this:



       "MetaModes" "DFP-3: 2560x1600 +0+0 rotation=left, ForceCompositionPipeline=On, DFP-4: ForceCompositionPipeline=On"


      In 18.04, there does not exist any value that works here, because when nvidia comes up, it says that all devices are disconnected; it is a few seconds later, on further study, that it starts finding things with names like "DP-1-1" which can be connected or probed. But those names don't exist yet when the xorg.conf fragments are read. So the MetaModes line is discarded because it doesn't apply to anything.



      I can accept that I may be forced to manually run xrandr later, but it seems stupid. I don't care about, or want, prime. If it would go away, and the nvidia driver would just probe displays normally, I would have the intended behavior.



      Is there a setting or hook somewhere needed to tell the nvidia driver to stop trying to overthink this? I can't uninstall nvidia-prime; I mean, I can, but everything breaks then. There's a thing called gpu-manager which keeps forcing everything over to using prime, but also has no documentation, and no --help, and is basically exactly the opposite of good software engineering. If I dummy it out (say, by replacing it with a script that just does nothing), it stops actively breaking things, but things don't actually get fixed. If I disable it, and nuke 11-nvidia-prime.conf, it looks like the nvidia driver ends up not being used at all.



      nvidia-settings can't generate a config file anymore ("xorg-server was not found in the pkg-config search path"), and any attempt to use a working config from a basically-identical machine running 16.04 gets no valid screens found, because of the "everything probes as disconnected initially" problem.



      I'm sort of guessing that the support for prime has caused it to disable all displays until prime gets a chance to tell it to enable them, but I don't know how to get around that or suppress it.



      EDIT: Coming back a bit later, I checked more carefully. Other laptop is also using nvidia-prime, so prime itself is not innately the problem. Older laptop is 16.04 with nvidia-384, newer is 18.04 with nvidia-390. Slightly different generations; older is a quadro M2000, new one is a quadro M2200, I think.







      share|improve this question














      I had this working fine in 16.04 on a very similar machine.



      What I want: I want to tell X to start with a particular display rotated, if it's present. I also want to use the nvidia driver, not nouveau, and have decent performance without screen-tearing.



      I don't care either way about "nvidia Prime", but so far as I can tell it's why this isn't working, so my guess is I want it burned, purged with fire, destroyed, removed, and otherwise completely prevented from ever interacting with me or my laptop again. I do not care about the marginal impact on battery life.



      In Ubuntu 16.04, I could set up xorg.conf, and do this:



       "MetaModes" "DFP-3: 2560x1600 +0+0 rotation=left, ForceCompositionPipeline=On, DFP-4: ForceCompositionPipeline=On"


      In 18.04, there does not exist any value that works here, because when nvidia comes up, it says that all devices are disconnected; it is a few seconds later, on further study, that it starts finding things with names like "DP-1-1" which can be connected or probed. But those names don't exist yet when the xorg.conf fragments are read. So the MetaModes line is discarded because it doesn't apply to anything.



      I can accept that I may be forced to manually run xrandr later, but it seems stupid. I don't care about, or want, prime. If it would go away, and the nvidia driver would just probe displays normally, I would have the intended behavior.



      Is there a setting or hook somewhere needed to tell the nvidia driver to stop trying to overthink this? I can't uninstall nvidia-prime; I mean, I can, but everything breaks then. There's a thing called gpu-manager which keeps forcing everything over to using prime, but also has no documentation, and no --help, and is basically exactly the opposite of good software engineering. If I dummy it out (say, by replacing it with a script that just does nothing), it stops actively breaking things, but things don't actually get fixed. If I disable it, and nuke 11-nvidia-prime.conf, it looks like the nvidia driver ends up not being used at all.



      nvidia-settings can't generate a config file anymore ("xorg-server was not found in the pkg-config search path"), and any attempt to use a working config from a basically-identical machine running 16.04 gets no valid screens found, because of the "everything probes as disconnected initially" problem.



      I'm sort of guessing that the support for prime has caused it to disable all displays until prime gets a chance to tell it to enable them, but I don't know how to get around that or suppress it.



      EDIT: Coming back a bit later, I checked more carefully. Other laptop is also using nvidia-prime, so prime itself is not innately the problem. Older laptop is 16.04 with nvidia-384, newer is 18.04 with nvidia-390. Slightly different generations; older is a quadro M2000, new one is a quadro M2200, I think.









      share|improve this question













      share|improve this question




      share|improve this question








      edited May 29 at 16:32

























      asked May 24 at 18:29









      Seebs

      62




      62

























          active

          oldest

          votes











          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',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          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%2f1039932%2ftrying-to-set-up-monitor-rotation-nvidia-in-18-04%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes










           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1039932%2ftrying-to-set-up-monitor-rotation-nvidia-in-18-04%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491