Internal laptop screen not detected when using Nvidia driverHow to get second display to work alongside primary display?Tried every solution but my monitor resolution is still stuck at 640x480How do I enable Extra Visual Effects using an Intel graphics controller?NVidia dual monitor set-up 11.04External monitor does not correctly display on GMA500Rotating one screen with xinerama in a multihead setupCan X.org Load Two Different Drivers? (Triple-Head Setup with Intel and NVidia Card)Wrong display resolution after failed NVIDIA driver update

Reconstructed PIE grammar? Could we be able to speak in Proto-European?

Why do we have to discharge the capacitor before testing it in an LCR Meter?

How to get to these nuts

What is the difference between scissors and shears?

Why are Amex fees allowed in the European Union?

Simulating these special dice on more regular dice

Contraction of a family of loops simultaneously

Do sine waves (pure tones) have overtones?

I wasted six years of my life getting a PhD degree. What should I do, and how will I survive?

Am I obligated to pass on domain knowledge after being let go?

How do professors and lecturers learn to teach?

What's that in front of the overhead panel?

If you were to fly an ILS in a knife edge would you receve GS and LOC be fliped?

Why is Brownian motion useful in finance?

How to interpret classification report of scikit-learn?

Is there a BIOS setting that controls cpu load sharing?

Round up my number

Can't hide object which particles are based on, without losing particles

What are the ramifications of Aasimar PCs being Outsider (Native)?

How can we save ourselves from large drops in stock price?

Pros and cons of playing correspondence chess

Why does atmospheric pressure acts on us?

Has there been clarification of the Random Weight Table in the Player's Handbook?

What is the typical CPU utilization of idle iMac?



Internal laptop screen not detected when using Nvidia driver


How to get second display to work alongside primary display?Tried every solution but my monitor resolution is still stuck at 640x480How do I enable Extra Visual Effects using an Intel graphics controller?NVidia dual monitor set-up 11.04External monitor does not correctly display on GMA500Rotating one screen with xinerama in a multihead setupCan X.org Load Two Different Drivers? (Triple-Head Setup with Intel and NVidia Card)Wrong display resolution after failed NVIDIA driver update






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









0


















So, for a bit of background: I'm using Ubuntu 18.04 on an HP laptop, which uses a dual GPU setup. Before, I have been using it with just the Nouveau driver, but recently I wanted to add in a second monitor so I switched to the proprietary Nvidia driver 390.77 (which was something of an odyssey in itself).



Now the issue is that while the secondary monitor (connected through HDMI) works fine, the primary built-in laptop screen does not. During the boot-sequence, everything is displayed as normal on the laptop screen, including the grub menu and the startup log.



But the moment the log reaches "Started User Manager for UID 120" (at which point presumably the graphics driver is started up), the laptop screen freezes there and all further output is displayed on the secondary monitor. The Ubuntu display settings only recognize a single display (the external monitor), as does nvidia-settings.



What might be noteworthy is that I'm dual-booting this system together with Windows 10, and under Windows this issue doesn't happen, both displays work just fine and like you'd expect over there.



Now, my personal suspicion is that it might have something to do with the dual GPUs, in that the Intel one usually outputs to the laptop screen and the Nvidia one to the HDMI port, but I'm not certain.



I have tried to use the Intel GPU instead, via sudo prime-select intel, but in that case the Nvidia driver didn't load at all, and I could only use the primary laptop screen while the external monitor wasn't recognized (i.e. similar to the behaviour under Nouveau). Additionally, this lead to a very low resolution that could only be circumvented by manually adding a new mode via xrandr.



As for some possibly relevant data, here's the output of lswh -C video:



 *-display 
description: VGA compatible controller
product: GP107M [GeForce GTX 1050 Ti Mobile]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nvidia latency=0
resources: irq:142 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:4000(size=128) memory:b4000000-b407ffff
*-display
description: VGA compatible controller
product: Intel Corporation
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:141 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:5000(size=64) memory:c0000-dffff


And here's xrandr. Noteworthy here is that the usual name of the laptop's display, eDP-1, is not even listed here:



Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
1920x1080 60.00*+ 59.94 50.00 50.00
1680x1050 59.95
1600x900 60.00
1440x900 59.89
1280x1024 60.02
1280x800 59.81
1280x720 60.00 59.94 50.00
1024x768 60.00
800x600 60.32
720x576 50.00
720x480 59.94
640x480 59.94


Finally, here's xorg.conf:



# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 390.77 (buildmeister@swio-display-x64-rhel04-14) Tue Jul 10 23:19:22 PDT 2018


Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
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 "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection









share|improve this question































    0


















    So, for a bit of background: I'm using Ubuntu 18.04 on an HP laptop, which uses a dual GPU setup. Before, I have been using it with just the Nouveau driver, but recently I wanted to add in a second monitor so I switched to the proprietary Nvidia driver 390.77 (which was something of an odyssey in itself).



    Now the issue is that while the secondary monitor (connected through HDMI) works fine, the primary built-in laptop screen does not. During the boot-sequence, everything is displayed as normal on the laptop screen, including the grub menu and the startup log.



    But the moment the log reaches "Started User Manager for UID 120" (at which point presumably the graphics driver is started up), the laptop screen freezes there and all further output is displayed on the secondary monitor. The Ubuntu display settings only recognize a single display (the external monitor), as does nvidia-settings.



    What might be noteworthy is that I'm dual-booting this system together with Windows 10, and under Windows this issue doesn't happen, both displays work just fine and like you'd expect over there.



    Now, my personal suspicion is that it might have something to do with the dual GPUs, in that the Intel one usually outputs to the laptop screen and the Nvidia one to the HDMI port, but I'm not certain.



    I have tried to use the Intel GPU instead, via sudo prime-select intel, but in that case the Nvidia driver didn't load at all, and I could only use the primary laptop screen while the external monitor wasn't recognized (i.e. similar to the behaviour under Nouveau). Additionally, this lead to a very low resolution that could only be circumvented by manually adding a new mode via xrandr.



    As for some possibly relevant data, here's the output of lswh -C video:



     *-display 
    description: VGA compatible controller
    product: GP107M [GeForce GTX 1050 Ti Mobile]
    vendor: NVIDIA Corporation
    physical id: 0
    bus info: pci@0000:01:00.0
    version: a1
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
    configuration: driver=nvidia latency=0
    resources: irq:142 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:4000(size=128) memory:b4000000-b407ffff
    *-display
    description: VGA compatible controller
    product: Intel Corporation
    vendor: Intel Corporation
    physical id: 2
    bus info: pci@0000:00:02.0
    version: 04
    width: 64 bits
    clock: 33MHz
    capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
    configuration: driver=i915 latency=0
    resources: irq:141 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:5000(size=64) memory:c0000-dffff


    And here's xrandr. Noteworthy here is that the usual name of the laptop's display, eDP-1, is not even listed here:



    Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
    HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
    1920x1080 60.00*+ 59.94 50.00 50.00
    1680x1050 59.95
    1600x900 60.00
    1440x900 59.89
    1280x1024 60.02
    1280x800 59.81
    1280x720 60.00 59.94 50.00
    1024x768 60.00
    800x600 60.32
    720x576 50.00
    720x480 59.94
    640x480 59.94


    Finally, here's xorg.conf:



    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 390.77 (buildmeister@swio-display-x64-rhel04-14) Tue Jul 10 23:19:22 PDT 2018


    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    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 "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DPMS"
    EndSection

    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    EndSection

    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection









    share|improve this question



























      0













      0









      0








      So, for a bit of background: I'm using Ubuntu 18.04 on an HP laptop, which uses a dual GPU setup. Before, I have been using it with just the Nouveau driver, but recently I wanted to add in a second monitor so I switched to the proprietary Nvidia driver 390.77 (which was something of an odyssey in itself).



      Now the issue is that while the secondary monitor (connected through HDMI) works fine, the primary built-in laptop screen does not. During the boot-sequence, everything is displayed as normal on the laptop screen, including the grub menu and the startup log.



      But the moment the log reaches "Started User Manager for UID 120" (at which point presumably the graphics driver is started up), the laptop screen freezes there and all further output is displayed on the secondary monitor. The Ubuntu display settings only recognize a single display (the external monitor), as does nvidia-settings.



      What might be noteworthy is that I'm dual-booting this system together with Windows 10, and under Windows this issue doesn't happen, both displays work just fine and like you'd expect over there.



      Now, my personal suspicion is that it might have something to do with the dual GPUs, in that the Intel one usually outputs to the laptop screen and the Nvidia one to the HDMI port, but I'm not certain.



      I have tried to use the Intel GPU instead, via sudo prime-select intel, but in that case the Nvidia driver didn't load at all, and I could only use the primary laptop screen while the external monitor wasn't recognized (i.e. similar to the behaviour under Nouveau). Additionally, this lead to a very low resolution that could only be circumvented by manually adding a new mode via xrandr.



      As for some possibly relevant data, here's the output of lswh -C video:



       *-display 
      description: VGA compatible controller
      product: GP107M [GeForce GTX 1050 Ti Mobile]
      vendor: NVIDIA Corporation
      physical id: 0
      bus info: pci@0000:01:00.0
      version: a1
      width: 64 bits
      clock: 33MHz
      capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
      configuration: driver=nvidia latency=0
      resources: irq:142 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:4000(size=128) memory:b4000000-b407ffff
      *-display
      description: VGA compatible controller
      product: Intel Corporation
      vendor: Intel Corporation
      physical id: 2
      bus info: pci@0000:00:02.0
      version: 04
      width: 64 bits
      clock: 33MHz
      capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
      configuration: driver=i915 latency=0
      resources: irq:141 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:5000(size=64) memory:c0000-dffff


      And here's xrandr. Noteworthy here is that the usual name of the laptop's display, eDP-1, is not even listed here:



      Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
      HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
      1920x1080 60.00*+ 59.94 50.00 50.00
      1680x1050 59.95
      1600x900 60.00
      1440x900 59.89
      1280x1024 60.02
      1280x800 59.81
      1280x720 60.00 59.94 50.00
      1024x768 60.00
      800x600 60.32
      720x576 50.00
      720x480 59.94
      640x480 59.94


      Finally, here's xorg.conf:



      # nvidia-xconfig: X configuration file generated by nvidia-xconfig
      # nvidia-xconfig: version 390.77 (buildmeister@swio-display-x64-rhel04-14) Tue Jul 10 23:19:22 PDT 2018


      Section "ServerLayout"
      Identifier "Layout0"
      Screen 0 "Screen0" 0 0
      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 "Monitor0"
      VendorName "Unknown"
      ModelName "Unknown"
      HorizSync 28.0 - 33.0
      VertRefresh 43.0 - 72.0
      Option "DPMS"
      EndSection

      Section "Device"
      Identifier "Device0"
      Driver "nvidia"
      VendorName "NVIDIA Corporation"
      EndSection

      Section "Screen"
      Identifier "Screen0"
      Device "Device0"
      Monitor "Monitor0"
      DefaultDepth 24
      SubSection "Display"
      Depth 24
      EndSubSection
      EndSection









      share|improve this question














      So, for a bit of background: I'm using Ubuntu 18.04 on an HP laptop, which uses a dual GPU setup. Before, I have been using it with just the Nouveau driver, but recently I wanted to add in a second monitor so I switched to the proprietary Nvidia driver 390.77 (which was something of an odyssey in itself).



      Now the issue is that while the secondary monitor (connected through HDMI) works fine, the primary built-in laptop screen does not. During the boot-sequence, everything is displayed as normal on the laptop screen, including the grub menu and the startup log.



      But the moment the log reaches "Started User Manager for UID 120" (at which point presumably the graphics driver is started up), the laptop screen freezes there and all further output is displayed on the secondary monitor. The Ubuntu display settings only recognize a single display (the external monitor), as does nvidia-settings.



      What might be noteworthy is that I'm dual-booting this system together with Windows 10, and under Windows this issue doesn't happen, both displays work just fine and like you'd expect over there.



      Now, my personal suspicion is that it might have something to do with the dual GPUs, in that the Intel one usually outputs to the laptop screen and the Nvidia one to the HDMI port, but I'm not certain.



      I have tried to use the Intel GPU instead, via sudo prime-select intel, but in that case the Nvidia driver didn't load at all, and I could only use the primary laptop screen while the external monitor wasn't recognized (i.e. similar to the behaviour under Nouveau). Additionally, this lead to a very low resolution that could only be circumvented by manually adding a new mode via xrandr.



      As for some possibly relevant data, here's the output of lswh -C video:



       *-display 
      description: VGA compatible controller
      product: GP107M [GeForce GTX 1050 Ti Mobile]
      vendor: NVIDIA Corporation
      physical id: 0
      bus info: pci@0000:01:00.0
      version: a1
      width: 64 bits
      clock: 33MHz
      capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
      configuration: driver=nvidia latency=0
      resources: irq:142 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:4000(size=128) memory:b4000000-b407ffff
      *-display
      description: VGA compatible controller
      product: Intel Corporation
      vendor: Intel Corporation
      physical id: 2
      bus info: pci@0000:00:02.0
      version: 04
      width: 64 bits
      clock: 33MHz
      capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
      configuration: driver=i915 latency=0
      resources: irq:141 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:5000(size=64) memory:c0000-dffff


      And here's xrandr. Noteworthy here is that the usual name of the laptop's display, eDP-1, is not even listed here:



      Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
      HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
      1920x1080 60.00*+ 59.94 50.00 50.00
      1680x1050 59.95
      1600x900 60.00
      1440x900 59.89
      1280x1024 60.02
      1280x800 59.81
      1280x720 60.00 59.94 50.00
      1024x768 60.00
      800x600 60.32
      720x576 50.00
      720x480 59.94
      640x480 59.94


      Finally, here's xorg.conf:



      # nvidia-xconfig: X configuration file generated by nvidia-xconfig
      # nvidia-xconfig: version 390.77 (buildmeister@swio-display-x64-rhel04-14) Tue Jul 10 23:19:22 PDT 2018


      Section "ServerLayout"
      Identifier "Layout0"
      Screen 0 "Screen0" 0 0
      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 "Monitor0"
      VendorName "Unknown"
      ModelName "Unknown"
      HorizSync 28.0 - 33.0
      VertRefresh 43.0 - 72.0
      Option "DPMS"
      EndSection

      Section "Device"
      Identifier "Device0"
      Driver "nvidia"
      VendorName "NVIDIA Corporation"
      EndSection

      Section "Screen"
      Identifier "Screen0"
      Device "Device0"
      Monitor "Monitor0"
      DefaultDepth 24
      SubSection "Display"
      Depth 24
      EndSubSection
      EndSection






      drivers nvidia graphics multiple-monitors dual-graphics






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jul 27 '18 at 10:21









      HoshiHoshi

      13 bronze badges




      13 bronze badges























          3 Answers
          3






          active

          oldest

          votes


















          2



















          Some similar thing happened to me. It turned out that it was caused by something in the /etc/X11/xorg.conf file. Luckily, there was a default nvidia config file I could use.



          This solved my problem:



          cd /etc/X11
          sudo rm xorg.conf
          sudo cp xorg.conf.nvidia-xconfig-original xorg.conf
          reboot





          share|improve this answer


































            0



















            During my fixing attempts, I ended up launching Ubuntu from a USB stick via "try Ubuntu". As it turned out, in that environment both monitors worked perfectly without needing any further configuration. So I concluded the issue was not necessarily related to any hardware configuration, but rather to some error in my Ubuntu configuration. To that end, the solution turned out to boil down to simply reinstalling Ubuntu wholesale.



            The particular steps I took, in case anybody somehow finds themselves in a similar situation:



            1. Backed up my /home/ folder and any important data from the Ubuntu partition.

            2. Booted from an Ubuntu USB drive, selected "Install Ubuntu", and chose "Erase Ubuntu 18.04 and reinstall".

            3. After the installation, the first boot attempt failed due to the graphics hardware issue. I circumvented this by adding "nouveau.modeset=0" to the grub commandline default. This was only needed the one time to boot and was no longer necessary afterwards.

            4. I installed the Nvidia 390.77 drive through Ubuntu's "Additional Drivers" UI.

            5. Rebooted once again, and everything worked!

            I still have no idea what might have caused the issue, but it shows once again that when in doubt, you might just want to try flattening your system and reinstalling.






            share|improve this answer
































              0



















              Resetting the X11 config file (generated by default by the nvidia-config for 1 monitor only) fixed the same issue for me too:



              sudo > /etc/X11/xorg.conf

              reboot


              Note: this is the same as the solution in the previous comment just because /etc/X11/xorg.conf.nvidia-xconfig-original is empty (zero) file in fact.






              share|improve this answer




























                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/4.0/"u003ecc by-sa 4.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%2f1059965%2finternal-laptop-screen-not-detected-when-using-nvidia-driver%23new-answer', 'question_page');

                );

                Post as a guest















                Required, but never shown


























                3 Answers
                3






                active

                oldest

                votes








                3 Answers
                3






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                2



















                Some similar thing happened to me. It turned out that it was caused by something in the /etc/X11/xorg.conf file. Luckily, there was a default nvidia config file I could use.



                This solved my problem:



                cd /etc/X11
                sudo rm xorg.conf
                sudo cp xorg.conf.nvidia-xconfig-original xorg.conf
                reboot





                share|improve this answer































                  2



















                  Some similar thing happened to me. It turned out that it was caused by something in the /etc/X11/xorg.conf file. Luckily, there was a default nvidia config file I could use.



                  This solved my problem:



                  cd /etc/X11
                  sudo rm xorg.conf
                  sudo cp xorg.conf.nvidia-xconfig-original xorg.conf
                  reboot





                  share|improve this answer





























                    2















                    2











                    2









                    Some similar thing happened to me. It turned out that it was caused by something in the /etc/X11/xorg.conf file. Luckily, there was a default nvidia config file I could use.



                    This solved my problem:



                    cd /etc/X11
                    sudo rm xorg.conf
                    sudo cp xorg.conf.nvidia-xconfig-original xorg.conf
                    reboot





                    share|improve this answer
















                    Some similar thing happened to me. It turned out that it was caused by something in the /etc/X11/xorg.conf file. Luckily, there was a default nvidia config file I could use.



                    This solved my problem:



                    cd /etc/X11
                    sudo rm xorg.conf
                    sudo cp xorg.conf.nvidia-xconfig-original xorg.conf
                    reboot






                    share|improve this answer















                    share|improve this answer




                    share|improve this answer








                    edited Sep 29 at 7:13









                    zx485

                    1,7285 gold badges15 silver badges18 bronze badges




                    1,7285 gold badges15 silver badges18 bronze badges










                    answered Sep 28 at 22:33









                    serdarhakanserdarhakan

                    212 bronze badges




                    212 bronze badges


























                        0



















                        During my fixing attempts, I ended up launching Ubuntu from a USB stick via "try Ubuntu". As it turned out, in that environment both monitors worked perfectly without needing any further configuration. So I concluded the issue was not necessarily related to any hardware configuration, but rather to some error in my Ubuntu configuration. To that end, the solution turned out to boil down to simply reinstalling Ubuntu wholesale.



                        The particular steps I took, in case anybody somehow finds themselves in a similar situation:



                        1. Backed up my /home/ folder and any important data from the Ubuntu partition.

                        2. Booted from an Ubuntu USB drive, selected "Install Ubuntu", and chose "Erase Ubuntu 18.04 and reinstall".

                        3. After the installation, the first boot attempt failed due to the graphics hardware issue. I circumvented this by adding "nouveau.modeset=0" to the grub commandline default. This was only needed the one time to boot and was no longer necessary afterwards.

                        4. I installed the Nvidia 390.77 drive through Ubuntu's "Additional Drivers" UI.

                        5. Rebooted once again, and everything worked!

                        I still have no idea what might have caused the issue, but it shows once again that when in doubt, you might just want to try flattening your system and reinstalling.






                        share|improve this answer





























                          0



















                          During my fixing attempts, I ended up launching Ubuntu from a USB stick via "try Ubuntu". As it turned out, in that environment both monitors worked perfectly without needing any further configuration. So I concluded the issue was not necessarily related to any hardware configuration, but rather to some error in my Ubuntu configuration. To that end, the solution turned out to boil down to simply reinstalling Ubuntu wholesale.



                          The particular steps I took, in case anybody somehow finds themselves in a similar situation:



                          1. Backed up my /home/ folder and any important data from the Ubuntu partition.

                          2. Booted from an Ubuntu USB drive, selected "Install Ubuntu", and chose "Erase Ubuntu 18.04 and reinstall".

                          3. After the installation, the first boot attempt failed due to the graphics hardware issue. I circumvented this by adding "nouveau.modeset=0" to the grub commandline default. This was only needed the one time to boot and was no longer necessary afterwards.

                          4. I installed the Nvidia 390.77 drive through Ubuntu's "Additional Drivers" UI.

                          5. Rebooted once again, and everything worked!

                          I still have no idea what might have caused the issue, but it shows once again that when in doubt, you might just want to try flattening your system and reinstalling.






                          share|improve this answer



























                            0















                            0











                            0









                            During my fixing attempts, I ended up launching Ubuntu from a USB stick via "try Ubuntu". As it turned out, in that environment both monitors worked perfectly without needing any further configuration. So I concluded the issue was not necessarily related to any hardware configuration, but rather to some error in my Ubuntu configuration. To that end, the solution turned out to boil down to simply reinstalling Ubuntu wholesale.



                            The particular steps I took, in case anybody somehow finds themselves in a similar situation:



                            1. Backed up my /home/ folder and any important data from the Ubuntu partition.

                            2. Booted from an Ubuntu USB drive, selected "Install Ubuntu", and chose "Erase Ubuntu 18.04 and reinstall".

                            3. After the installation, the first boot attempt failed due to the graphics hardware issue. I circumvented this by adding "nouveau.modeset=0" to the grub commandline default. This was only needed the one time to boot and was no longer necessary afterwards.

                            4. I installed the Nvidia 390.77 drive through Ubuntu's "Additional Drivers" UI.

                            5. Rebooted once again, and everything worked!

                            I still have no idea what might have caused the issue, but it shows once again that when in doubt, you might just want to try flattening your system and reinstalling.






                            share|improve this answer














                            During my fixing attempts, I ended up launching Ubuntu from a USB stick via "try Ubuntu". As it turned out, in that environment both monitors worked perfectly without needing any further configuration. So I concluded the issue was not necessarily related to any hardware configuration, but rather to some error in my Ubuntu configuration. To that end, the solution turned out to boil down to simply reinstalling Ubuntu wholesale.



                            The particular steps I took, in case anybody somehow finds themselves in a similar situation:



                            1. Backed up my /home/ folder and any important data from the Ubuntu partition.

                            2. Booted from an Ubuntu USB drive, selected "Install Ubuntu", and chose "Erase Ubuntu 18.04 and reinstall".

                            3. After the installation, the first boot attempt failed due to the graphics hardware issue. I circumvented this by adding "nouveau.modeset=0" to the grub commandline default. This was only needed the one time to boot and was no longer necessary afterwards.

                            4. I installed the Nvidia 390.77 drive through Ubuntu's "Additional Drivers" UI.

                            5. Rebooted once again, and everything worked!

                            I still have no idea what might have caused the issue, but it shows once again that when in doubt, you might just want to try flattening your system and reinstalling.







                            share|improve this answer













                            share|improve this answer




                            share|improve this answer










                            answered Jul 30 '18 at 14:48









                            HoshiHoshi

                            13 bronze badges




                            13 bronze badges
























                                0



















                                Resetting the X11 config file (generated by default by the nvidia-config for 1 monitor only) fixed the same issue for me too:



                                sudo > /etc/X11/xorg.conf

                                reboot


                                Note: this is the same as the solution in the previous comment just because /etc/X11/xorg.conf.nvidia-xconfig-original is empty (zero) file in fact.






                                share|improve this answer































                                  0



















                                  Resetting the X11 config file (generated by default by the nvidia-config for 1 monitor only) fixed the same issue for me too:



                                  sudo > /etc/X11/xorg.conf

                                  reboot


                                  Note: this is the same as the solution in the previous comment just because /etc/X11/xorg.conf.nvidia-xconfig-original is empty (zero) file in fact.






                                  share|improve this answer





























                                    0















                                    0











                                    0









                                    Resetting the X11 config file (generated by default by the nvidia-config for 1 monitor only) fixed the same issue for me too:



                                    sudo > /etc/X11/xorg.conf

                                    reboot


                                    Note: this is the same as the solution in the previous comment just because /etc/X11/xorg.conf.nvidia-xconfig-original is empty (zero) file in fact.






                                    share|improve this answer
















                                    Resetting the X11 config file (generated by default by the nvidia-config for 1 monitor only) fixed the same issue for me too:



                                    sudo > /etc/X11/xorg.conf

                                    reboot


                                    Note: this is the same as the solution in the previous comment just because /etc/X11/xorg.conf.nvidia-xconfig-original is empty (zero) file in fact.







                                    share|improve this answer















                                    share|improve this answer




                                    share|improve this answer








                                    edited Nov 20 at 13:30









                                    Thomas

                                    4,5988 gold badges19 silver badges30 bronze badges




                                    4,5988 gold badges19 silver badges30 bronze badges










                                    answered Nov 20 at 12:31









                                    OlegOleg

                                    1




                                    1































                                        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%2f1059965%2finternal-laptop-screen-not-detected-when-using-nvidia-driver%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









                                        Popular posts from this blog

                                        Tamil (spriik) Luke uk diar | Nawigatjuun

                                        Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

                                        Training a classifier when some of the features are unknownWhy does Gradient Boosting regression predict negative values when there are no negative y-values in my training set?How to improve an existing (trained) classifier?What is effect when I set up some self defined predisctor variables?Why Matlab neural network classification returns decimal values on prediction dataset?Fitting and transforming text data in training, testing, and validation setsHow to quantify the performance of the classifier (multi-class SVM) using the test data?How do I control for some patients providing multiple samples in my training data?Training and Test setTraining a convolutional neural network for image denoising in MatlabShouldn't an autoencoder with #(neurons in hidden layer) = #(neurons in input layer) be “perfect”?