How can I fix broken i915 drivers for Intel GPUs?












15














I've got troubles getting the i915 drivers to work correctly on my laptop (HP Pavilion DM4 2101ea).



Specifically, the laptop screen goes black and stays black after the splash graphic when booting both from USB key and from harddrive.



To get anything on to the display after the splash screen I have to boot either with




  • acpi=off

  • nomodeset

  • i915.modeset=0


I'd rather not turn ACPI off because I like my fans spinning and nomodeset is a bit overkill, so for now I'm booting with i915.modeset=0.



Unfortunately, this turns off KMS and my current maximum resolution on the laptop screen is fixed to 1024x768 instead of its real capability.



When not setting any of the above boot flags and I plug in an external monitor, the external monitor works fine. When booting with the flags, the external monitor works fine too, but can only do 1024x768 and can't do anything else than mirroring the laptop display.



I did upgrade the i915 drivers from 2.17 that ship with Precise to 2.19 which are the most recent ones but without luck of getting anything to display.



Here's my lspci output:



00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5116 PCI Express Card Reader (rev 01)
08:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)


Here's lshw -C video



  *-display UNCLAIMED     
description: VGA compatible controller
product: 2nd Generation Core Processor Family Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 09
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list
configuration: latency=0
resources: memory:c0000000-c03fffff memory:b0000000-bfffffff ioport:4000(size=64)


Both outputs are generated after booting with i915.modeset=0.



Here's a complete Xorg.log file from a boot into a black screen: https://gist.github.com/479ce06454e47d6123e1



The graphics card is a Intel HD 3000 integrated GPU.



I've never had problems with Intel hardware on Ubuntu before so this is very surprising.



If you could




  • provide a method to make i915 work,

  • suggest alternative drivers

  • a way to boot with i915.modeset=0 but higher resolutions and KMS on

  • or explain what is happening and how to fix it


I'll give you an answer badge. :)



Thanks










share|improve this question





























    15














    I've got troubles getting the i915 drivers to work correctly on my laptop (HP Pavilion DM4 2101ea).



    Specifically, the laptop screen goes black and stays black after the splash graphic when booting both from USB key and from harddrive.



    To get anything on to the display after the splash screen I have to boot either with




    • acpi=off

    • nomodeset

    • i915.modeset=0


    I'd rather not turn ACPI off because I like my fans spinning and nomodeset is a bit overkill, so for now I'm booting with i915.modeset=0.



    Unfortunately, this turns off KMS and my current maximum resolution on the laptop screen is fixed to 1024x768 instead of its real capability.



    When not setting any of the above boot flags and I plug in an external monitor, the external monitor works fine. When booting with the flags, the external monitor works fine too, but can only do 1024x768 and can't do anything else than mirroring the laptop display.



    I did upgrade the i915 drivers from 2.17 that ship with Precise to 2.19 which are the most recent ones but without luck of getting anything to display.



    Here's my lspci output:



    00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
    00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
    00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
    00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
    00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
    00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
    00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
    00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
    00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05)
    00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
    00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
    01:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
    02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5116 PCI Express Card Reader (rev 01)
    08:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)


    Here's lshw -C video



      *-display UNCLAIMED     
    description: VGA compatible controller
    product: 2nd Generation Core Processor Family Integrated Graphics Controller
    vendor: Intel Corporation
    physical id: 2
    bus info: pci@0000:00:02.0
    version: 09
    width: 64 bits
    clock: 33MHz
    capabilities: msi pm vga_controller bus_master cap_list
    configuration: latency=0
    resources: memory:c0000000-c03fffff memory:b0000000-bfffffff ioport:4000(size=64)


    Both outputs are generated after booting with i915.modeset=0.



    Here's a complete Xorg.log file from a boot into a black screen: https://gist.github.com/479ce06454e47d6123e1



    The graphics card is a Intel HD 3000 integrated GPU.



    I've never had problems with Intel hardware on Ubuntu before so this is very surprising.



    If you could




    • provide a method to make i915 work,

    • suggest alternative drivers

    • a way to boot with i915.modeset=0 but higher resolutions and KMS on

    • or explain what is happening and how to fix it


    I'll give you an answer badge. :)



    Thanks










    share|improve this question



























      15












      15








      15


      9





      I've got troubles getting the i915 drivers to work correctly on my laptop (HP Pavilion DM4 2101ea).



      Specifically, the laptop screen goes black and stays black after the splash graphic when booting both from USB key and from harddrive.



      To get anything on to the display after the splash screen I have to boot either with




      • acpi=off

      • nomodeset

      • i915.modeset=0


      I'd rather not turn ACPI off because I like my fans spinning and nomodeset is a bit overkill, so for now I'm booting with i915.modeset=0.



      Unfortunately, this turns off KMS and my current maximum resolution on the laptop screen is fixed to 1024x768 instead of its real capability.



      When not setting any of the above boot flags and I plug in an external monitor, the external monitor works fine. When booting with the flags, the external monitor works fine too, but can only do 1024x768 and can't do anything else than mirroring the laptop display.



      I did upgrade the i915 drivers from 2.17 that ship with Precise to 2.19 which are the most recent ones but without luck of getting anything to display.



      Here's my lspci output:



      00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
      00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
      00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
      00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
      00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
      00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
      00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
      00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
      00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
      00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05)
      00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
      00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
      01:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
      02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5116 PCI Express Card Reader (rev 01)
      08:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)


      Here's lshw -C video



        *-display UNCLAIMED     
      description: VGA compatible controller
      product: 2nd Generation Core Processor Family Integrated Graphics Controller
      vendor: Intel Corporation
      physical id: 2
      bus info: pci@0000:00:02.0
      version: 09
      width: 64 bits
      clock: 33MHz
      capabilities: msi pm vga_controller bus_master cap_list
      configuration: latency=0
      resources: memory:c0000000-c03fffff memory:b0000000-bfffffff ioport:4000(size=64)


      Both outputs are generated after booting with i915.modeset=0.



      Here's a complete Xorg.log file from a boot into a black screen: https://gist.github.com/479ce06454e47d6123e1



      The graphics card is a Intel HD 3000 integrated GPU.



      I've never had problems with Intel hardware on Ubuntu before so this is very surprising.



      If you could




      • provide a method to make i915 work,

      • suggest alternative drivers

      • a way to boot with i915.modeset=0 but higher resolutions and KMS on

      • or explain what is happening and how to fix it


      I'll give you an answer badge. :)



      Thanks










      share|improve this question















      I've got troubles getting the i915 drivers to work correctly on my laptop (HP Pavilion DM4 2101ea).



      Specifically, the laptop screen goes black and stays black after the splash graphic when booting both from USB key and from harddrive.



      To get anything on to the display after the splash screen I have to boot either with




      • acpi=off

      • nomodeset

      • i915.modeset=0


      I'd rather not turn ACPI off because I like my fans spinning and nomodeset is a bit overkill, so for now I'm booting with i915.modeset=0.



      Unfortunately, this turns off KMS and my current maximum resolution on the laptop screen is fixed to 1024x768 instead of its real capability.



      When not setting any of the above boot flags and I plug in an external monitor, the external monitor works fine. When booting with the flags, the external monitor works fine too, but can only do 1024x768 and can't do anything else than mirroring the laptop display.



      I did upgrade the i915 drivers from 2.17 that ship with Precise to 2.19 which are the most recent ones but without luck of getting anything to display.



      Here's my lspci output:



      00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
      00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
      00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
      00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
      00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
      00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
      00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
      00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
      00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
      00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05)
      00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
      00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
      01:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
      02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5116 PCI Express Card Reader (rev 01)
      08:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)


      Here's lshw -C video



        *-display UNCLAIMED     
      description: VGA compatible controller
      product: 2nd Generation Core Processor Family Integrated Graphics Controller
      vendor: Intel Corporation
      physical id: 2
      bus info: pci@0000:00:02.0
      version: 09
      width: 64 bits
      clock: 33MHz
      capabilities: msi pm vga_controller bus_master cap_list
      configuration: latency=0
      resources: memory:c0000000-c03fffff memory:b0000000-bfffffff ioport:4000(size=64)


      Both outputs are generated after booting with i915.modeset=0.



      Here's a complete Xorg.log file from a boot into a black screen: https://gist.github.com/479ce06454e47d6123e1



      The graphics card is a Intel HD 3000 integrated GPU.



      I've never had problems with Intel hardware on Ubuntu before so this is very surprising.



      If you could




      • provide a method to make i915 work,

      • suggest alternative drivers

      • a way to boot with i915.modeset=0 but higher resolutions and KMS on

      • or explain what is happening and how to fix it


      I'll give you an answer badge. :)



      Thanks







      drivers graphics screen i915






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 14 '12 at 13:44

























      asked May 14 '12 at 0:28









      Alen Mujezinovic

      78116




      78116






















          9 Answers
          9






          active

          oldest

          votes


















          3














          For me this was a backlight issue. See the article for toubleshooting and reporting instructions.



          https://wiki.ubuntu.com/Kernel/Debugging/Backlight






          share|improve this answer





























            3














            Try turning off the bootloader graphics. Run this command in a Terminal window:



            gksudo xdiagnose


            Click the checkbox labeled "Disable bootloader graphics", hit Apply, then reboot.



            enter image description here



            If you want to report a bug on this, I'd suggest turning on the graphics debug messages (first checkbox above), reproducing the bug, and then collecting the output of dmesg.



            Beyond that, see http://wiki.ubuntu.com/X/Troubleshooting/BlankScreen for other common ways to diagnose these types of issues. I also have a more in-depth explanation of what happens to cause blank / black screens written up there, if you really want to know what's going on.






            share|improve this answer



















            • 1




              While it's probably OK to run xdiagnose with straight sudo because it doesn't use configuration files in the home directory, it's generally preferable, and often quite important, to use a graphical sudo frontend like gksu, gksudo, or kdesu when running graphical programs as root.
              – Eliah Kagan
              Jun 29 '12 at 10:06










            • Good point; answer updated.
              – Bryce
              Jun 29 '12 at 17:43



















            3














            Im working through similar issues with my x230, but more focussed on getting external screens running. I had to use the nomodeset flag to get installed. Here is what I have so far:
            display port on x230 not working



            my steps so far to get closer to working:




            1. Dont use nomodeset or modeset=0, as it throws off KMS and you wont be able to do anything.


            2. sudo vi /etc/initramfs-tools/modules and add in the i915 and intel_agp drivers, save, and rebuild by running update-initramfs -u


            Ive also made a custom x config stub in /usr/share/X11/xorg.conf.d/ to load the intel driver and give it some specifications, and a monitor config for all my devices. However, I still cant get my second monitor running!



            Also - Ive used arandr to create a shell script that sets all my resolutions nicely, except it too wont cause my displayport-connected monitor to function...



            Hope that helps,






            share|improve this answer































              2














              In /etc/rc.local, just before exit 0, put a line setpci -s 00:02.0 F4.B=30.



              This will turn on the backlight, to brightness 30 (where 00 is full bright and FF is full dark). The boot process will be dark but the light will come on immediately after the login screen appears.



              nomodeset is not used with this method, so the native screen resolution is available. I like the results, but still can't adjust my screen brightness with the Fn key.



              BTW I got this from http://ubuntuforums.org/showthread.php?t=1744809. To help explain the command above, lspcishows the Intel VGA controller at pci bus address 00:02.0.






              share|improve this answer































                2














                Be careful setting i915.modeset=0.



                All versions since 2.15 of the Intel-driver only support KMS. If you've deactivated KMS e.g. by adding the option i915.modeset=0 to the file /etc/default/grub, please reactivate KMS by deleting this option.



                Source: https://launchpad.net/~glasen/+archive/intel-driver






                share|improve this answer























                • Link is broken.
                  – ceving
                  Jun 6 at 7:43



















                2














                Here is how I made i915 work in 14.04:



                I downloaded the intel-linux-graphics-installer from 01.org, ran the same program and followed the instructions. The program downgraded one package and installed a number of new packages. Eventually, I was prompted to reboot. I opened the site that normally causes my screen to go blank in google chrome. Since I observed no more crashes I take it the problem is resolved.



                Note that I have no more command line options added to grub. Also note that I run kernel 3.13.0-44 and Ubuntu 14.04.






                share|improve this answer































                  0














                  i have a gateway nv78 with the black screen after the splash from the infamous intel mobile 4 chipset - actually it is the backlight - it is backwards? idek



                  external monitors work ok so you may need to use one to do this



                  anyway, boot the computer, and as root, edit the file /etc/rc.local

                  just before the exit 0 line, add the line
                  setpci -s 00:02.0 F4.B=00



                  save it



                  take out all the other things you've tried lol - be sure to run update-grub if you remove stuff from the grub quiet slpash part



                  reboot - the screen will go blank for a few seconds at boot like it used to do, but then about the time the mouse pointer arrow thing shows up the screen light will suddenly come back on and all is well



                  this works better than nomodeset as it gives you all the display modes and not just vesa 1280*720 - it now will detect plugged in monitors too and everything will work correctly






                  share|improve this answer





























                    0














                    I ran into this problem on my Dell Inspiron 3000. (The little 11' sub-$200 one, thanks Dell for reusing model numbers -_-)



                    Using 'nomodeset' did allow me to boot, but it had no GL acceleration and it was almost unbearable to use. On a whim, I changed a setting in the bios about legacy boot ROM (or something similar, I can't get the exact name without rebooting). After that was disabled, I was able to boot without issues. No black screen, and no need for 'nomodeset' that ruined the GL acceleration. I now have a very usable little laptop for configuring electronics in my model shop. o/






                    share|improve this answer





























                      0














                      My mobo is Intel D2500HN which has only 1 VGA port and no LVDS-1.
                      My distro: Lubuntu 18.04



                      ~$ modinfo i915
                      modinfo: ERROR: Module i915 not found.


                      Make sure that both your /lib/firmware/i915/ and /lib/modules/'uname -r'/ are populated with files



                      ~$ sudo apt install --reinstall linux-modules-'uname -r' linux-modules-extra-'uname -r'


                      My problem description:



                      4.15.0-20-generic: displaying FHD1920x1080 ok



                      4.15.0-42-generic: blank screen after a few lines appear after grub screen



                      ~$ sudo lspci -v | grep -A 10 -i vga <p>
                      00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) <p> (prog-if 00 [VGA controller])
                      Subsystem: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller
                      Flags: bus master, fast devsel, latency 0, IRQ 28
                      Memory at d0100000 (32-bit, non-prefetchable) [size=1M]
                      I/O ports at 20d0 [size=8]
                      [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
                      Capabilities: <access denied>
                      Kernel driver in use: gma500
                      Kernel modules: gma500_gfx


                      My solution:



                      ~$ sudo <your_editor> /etc/default/grub
                      ##video=LVDS-1:d is disabling LVDS-1 port which some kernel version might be directing the video to that port on default despite your mobo might not have such a port available to you
                      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 video=LVDS-1:d"


                      My problem solved, credit due to Loading Arch on Intel D2500CC board - i915 complaining about / Installation / Arch Linux Forums
                      which in turn drew his solution from
                      Mageia support for GMA 3600 (Cedar Trail Atom)






                      share|improve this answer










                      New contributor




                      Wilson Wong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.


















                        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%2f136593%2fhow-can-i-fix-broken-i915-drivers-for-intel-gpus%23new-answer', 'question_page');
                        }
                        );

                        Post as a guest















                        Required, but never shown

























                        9 Answers
                        9






                        active

                        oldest

                        votes








                        9 Answers
                        9






                        active

                        oldest

                        votes









                        active

                        oldest

                        votes






                        active

                        oldest

                        votes









                        3














                        For me this was a backlight issue. See the article for toubleshooting and reporting instructions.



                        https://wiki.ubuntu.com/Kernel/Debugging/Backlight






                        share|improve this answer


























                          3














                          For me this was a backlight issue. See the article for toubleshooting and reporting instructions.



                          https://wiki.ubuntu.com/Kernel/Debugging/Backlight






                          share|improve this answer
























                            3












                            3








                            3






                            For me this was a backlight issue. See the article for toubleshooting and reporting instructions.



                            https://wiki.ubuntu.com/Kernel/Debugging/Backlight






                            share|improve this answer












                            For me this was a backlight issue. See the article for toubleshooting and reporting instructions.



                            https://wiki.ubuntu.com/Kernel/Debugging/Backlight







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Dec 31 '13 at 7:22









                            Tomi

                            461




                            461

























                                3














                                Try turning off the bootloader graphics. Run this command in a Terminal window:



                                gksudo xdiagnose


                                Click the checkbox labeled "Disable bootloader graphics", hit Apply, then reboot.



                                enter image description here



                                If you want to report a bug on this, I'd suggest turning on the graphics debug messages (first checkbox above), reproducing the bug, and then collecting the output of dmesg.



                                Beyond that, see http://wiki.ubuntu.com/X/Troubleshooting/BlankScreen for other common ways to diagnose these types of issues. I also have a more in-depth explanation of what happens to cause blank / black screens written up there, if you really want to know what's going on.






                                share|improve this answer



















                                • 1




                                  While it's probably OK to run xdiagnose with straight sudo because it doesn't use configuration files in the home directory, it's generally preferable, and often quite important, to use a graphical sudo frontend like gksu, gksudo, or kdesu when running graphical programs as root.
                                  – Eliah Kagan
                                  Jun 29 '12 at 10:06










                                • Good point; answer updated.
                                  – Bryce
                                  Jun 29 '12 at 17:43
















                                3














                                Try turning off the bootloader graphics. Run this command in a Terminal window:



                                gksudo xdiagnose


                                Click the checkbox labeled "Disable bootloader graphics", hit Apply, then reboot.



                                enter image description here



                                If you want to report a bug on this, I'd suggest turning on the graphics debug messages (first checkbox above), reproducing the bug, and then collecting the output of dmesg.



                                Beyond that, see http://wiki.ubuntu.com/X/Troubleshooting/BlankScreen for other common ways to diagnose these types of issues. I also have a more in-depth explanation of what happens to cause blank / black screens written up there, if you really want to know what's going on.






                                share|improve this answer



















                                • 1




                                  While it's probably OK to run xdiagnose with straight sudo because it doesn't use configuration files in the home directory, it's generally preferable, and often quite important, to use a graphical sudo frontend like gksu, gksudo, or kdesu when running graphical programs as root.
                                  – Eliah Kagan
                                  Jun 29 '12 at 10:06










                                • Good point; answer updated.
                                  – Bryce
                                  Jun 29 '12 at 17:43














                                3












                                3








                                3






                                Try turning off the bootloader graphics. Run this command in a Terminal window:



                                gksudo xdiagnose


                                Click the checkbox labeled "Disable bootloader graphics", hit Apply, then reboot.



                                enter image description here



                                If you want to report a bug on this, I'd suggest turning on the graphics debug messages (first checkbox above), reproducing the bug, and then collecting the output of dmesg.



                                Beyond that, see http://wiki.ubuntu.com/X/Troubleshooting/BlankScreen for other common ways to diagnose these types of issues. I also have a more in-depth explanation of what happens to cause blank / black screens written up there, if you really want to know what's going on.






                                share|improve this answer














                                Try turning off the bootloader graphics. Run this command in a Terminal window:



                                gksudo xdiagnose


                                Click the checkbox labeled "Disable bootloader graphics", hit Apply, then reboot.



                                enter image description here



                                If you want to report a bug on this, I'd suggest turning on the graphics debug messages (first checkbox above), reproducing the bug, and then collecting the output of dmesg.



                                Beyond that, see http://wiki.ubuntu.com/X/Troubleshooting/BlankScreen for other common ways to diagnose these types of issues. I also have a more in-depth explanation of what happens to cause blank / black screens written up there, if you really want to know what's going on.







                                share|improve this answer














                                share|improve this answer



                                share|improve this answer








                                edited Jun 29 '12 at 17:42

























                                answered Jun 28 '12 at 22:19









                                Bryce

                                4,0411841




                                4,0411841








                                • 1




                                  While it's probably OK to run xdiagnose with straight sudo because it doesn't use configuration files in the home directory, it's generally preferable, and often quite important, to use a graphical sudo frontend like gksu, gksudo, or kdesu when running graphical programs as root.
                                  – Eliah Kagan
                                  Jun 29 '12 at 10:06










                                • Good point; answer updated.
                                  – Bryce
                                  Jun 29 '12 at 17:43














                                • 1




                                  While it's probably OK to run xdiagnose with straight sudo because it doesn't use configuration files in the home directory, it's generally preferable, and often quite important, to use a graphical sudo frontend like gksu, gksudo, or kdesu when running graphical programs as root.
                                  – Eliah Kagan
                                  Jun 29 '12 at 10:06










                                • Good point; answer updated.
                                  – Bryce
                                  Jun 29 '12 at 17:43








                                1




                                1




                                While it's probably OK to run xdiagnose with straight sudo because it doesn't use configuration files in the home directory, it's generally preferable, and often quite important, to use a graphical sudo frontend like gksu, gksudo, or kdesu when running graphical programs as root.
                                – Eliah Kagan
                                Jun 29 '12 at 10:06




                                While it's probably OK to run xdiagnose with straight sudo because it doesn't use configuration files in the home directory, it's generally preferable, and often quite important, to use a graphical sudo frontend like gksu, gksudo, or kdesu when running graphical programs as root.
                                – Eliah Kagan
                                Jun 29 '12 at 10:06












                                Good point; answer updated.
                                – Bryce
                                Jun 29 '12 at 17:43




                                Good point; answer updated.
                                – Bryce
                                Jun 29 '12 at 17:43











                                3














                                Im working through similar issues with my x230, but more focussed on getting external screens running. I had to use the nomodeset flag to get installed. Here is what I have so far:
                                display port on x230 not working



                                my steps so far to get closer to working:




                                1. Dont use nomodeset or modeset=0, as it throws off KMS and you wont be able to do anything.


                                2. sudo vi /etc/initramfs-tools/modules and add in the i915 and intel_agp drivers, save, and rebuild by running update-initramfs -u


                                Ive also made a custom x config stub in /usr/share/X11/xorg.conf.d/ to load the intel driver and give it some specifications, and a monitor config for all my devices. However, I still cant get my second monitor running!



                                Also - Ive used arandr to create a shell script that sets all my resolutions nicely, except it too wont cause my displayport-connected monitor to function...



                                Hope that helps,






                                share|improve this answer




























                                  3














                                  Im working through similar issues with my x230, but more focussed on getting external screens running. I had to use the nomodeset flag to get installed. Here is what I have so far:
                                  display port on x230 not working



                                  my steps so far to get closer to working:




                                  1. Dont use nomodeset or modeset=0, as it throws off KMS and you wont be able to do anything.


                                  2. sudo vi /etc/initramfs-tools/modules and add in the i915 and intel_agp drivers, save, and rebuild by running update-initramfs -u


                                  Ive also made a custom x config stub in /usr/share/X11/xorg.conf.d/ to load the intel driver and give it some specifications, and a monitor config for all my devices. However, I still cant get my second monitor running!



                                  Also - Ive used arandr to create a shell script that sets all my resolutions nicely, except it too wont cause my displayport-connected monitor to function...



                                  Hope that helps,






                                  share|improve this answer


























                                    3












                                    3








                                    3






                                    Im working through similar issues with my x230, but more focussed on getting external screens running. I had to use the nomodeset flag to get installed. Here is what I have so far:
                                    display port on x230 not working



                                    my steps so far to get closer to working:




                                    1. Dont use nomodeset or modeset=0, as it throws off KMS and you wont be able to do anything.


                                    2. sudo vi /etc/initramfs-tools/modules and add in the i915 and intel_agp drivers, save, and rebuild by running update-initramfs -u


                                    Ive also made a custom x config stub in /usr/share/X11/xorg.conf.d/ to load the intel driver and give it some specifications, and a monitor config for all my devices. However, I still cant get my second monitor running!



                                    Also - Ive used arandr to create a shell script that sets all my resolutions nicely, except it too wont cause my displayport-connected monitor to function...



                                    Hope that helps,






                                    share|improve this answer














                                    Im working through similar issues with my x230, but more focussed on getting external screens running. I had to use the nomodeset flag to get installed. Here is what I have so far:
                                    display port on x230 not working



                                    my steps so far to get closer to working:




                                    1. Dont use nomodeset or modeset=0, as it throws off KMS and you wont be able to do anything.


                                    2. sudo vi /etc/initramfs-tools/modules and add in the i915 and intel_agp drivers, save, and rebuild by running update-initramfs -u


                                    Ive also made a custom x config stub in /usr/share/X11/xorg.conf.d/ to load the intel driver and give it some specifications, and a monitor config for all my devices. However, I still cant get my second monitor running!



                                    Also - Ive used arandr to create a shell script that sets all my resolutions nicely, except it too wont cause my displayport-connected monitor to function...



                                    Hope that helps,







                                    share|improve this answer














                                    share|improve this answer



                                    share|improve this answer








                                    edited Apr 13 '17 at 12:24









                                    Community

                                    1




                                    1










                                    answered Sep 27 '12 at 1:25









                                    user92965

                                    1161




                                    1161























                                        2














                                        In /etc/rc.local, just before exit 0, put a line setpci -s 00:02.0 F4.B=30.



                                        This will turn on the backlight, to brightness 30 (where 00 is full bright and FF is full dark). The boot process will be dark but the light will come on immediately after the login screen appears.



                                        nomodeset is not used with this method, so the native screen resolution is available. I like the results, but still can't adjust my screen brightness with the Fn key.



                                        BTW I got this from http://ubuntuforums.org/showthread.php?t=1744809. To help explain the command above, lspcishows the Intel VGA controller at pci bus address 00:02.0.






                                        share|improve this answer




























                                          2














                                          In /etc/rc.local, just before exit 0, put a line setpci -s 00:02.0 F4.B=30.



                                          This will turn on the backlight, to brightness 30 (where 00 is full bright and FF is full dark). The boot process will be dark but the light will come on immediately after the login screen appears.



                                          nomodeset is not used with this method, so the native screen resolution is available. I like the results, but still can't adjust my screen brightness with the Fn key.



                                          BTW I got this from http://ubuntuforums.org/showthread.php?t=1744809. To help explain the command above, lspcishows the Intel VGA controller at pci bus address 00:02.0.






                                          share|improve this answer


























                                            2












                                            2








                                            2






                                            In /etc/rc.local, just before exit 0, put a line setpci -s 00:02.0 F4.B=30.



                                            This will turn on the backlight, to brightness 30 (where 00 is full bright and FF is full dark). The boot process will be dark but the light will come on immediately after the login screen appears.



                                            nomodeset is not used with this method, so the native screen resolution is available. I like the results, but still can't adjust my screen brightness with the Fn key.



                                            BTW I got this from http://ubuntuforums.org/showthread.php?t=1744809. To help explain the command above, lspcishows the Intel VGA controller at pci bus address 00:02.0.






                                            share|improve this answer














                                            In /etc/rc.local, just before exit 0, put a line setpci -s 00:02.0 F4.B=30.



                                            This will turn on the backlight, to brightness 30 (where 00 is full bright and FF is full dark). The boot process will be dark but the light will come on immediately after the login screen appears.



                                            nomodeset is not used with this method, so the native screen resolution is available. I like the results, but still can't adjust my screen brightness with the Fn key.



                                            BTW I got this from http://ubuntuforums.org/showthread.php?t=1744809. To help explain the command above, lspcishows the Intel VGA controller at pci bus address 00:02.0.







                                            share|improve this answer














                                            share|improve this answer



                                            share|improve this answer








                                            edited Jun 29 '12 at 10:00









                                            Eliah Kagan

                                            81.2k20227364




                                            81.2k20227364










                                            answered Jun 28 '12 at 21:59









                                            Ben C.

                                            211




                                            211























                                                2














                                                Be careful setting i915.modeset=0.



                                                All versions since 2.15 of the Intel-driver only support KMS. If you've deactivated KMS e.g. by adding the option i915.modeset=0 to the file /etc/default/grub, please reactivate KMS by deleting this option.



                                                Source: https://launchpad.net/~glasen/+archive/intel-driver






                                                share|improve this answer























                                                • Link is broken.
                                                  – ceving
                                                  Jun 6 at 7:43
















                                                2














                                                Be careful setting i915.modeset=0.



                                                All versions since 2.15 of the Intel-driver only support KMS. If you've deactivated KMS e.g. by adding the option i915.modeset=0 to the file /etc/default/grub, please reactivate KMS by deleting this option.



                                                Source: https://launchpad.net/~glasen/+archive/intel-driver






                                                share|improve this answer























                                                • Link is broken.
                                                  – ceving
                                                  Jun 6 at 7:43














                                                2












                                                2








                                                2






                                                Be careful setting i915.modeset=0.



                                                All versions since 2.15 of the Intel-driver only support KMS. If you've deactivated KMS e.g. by adding the option i915.modeset=0 to the file /etc/default/grub, please reactivate KMS by deleting this option.



                                                Source: https://launchpad.net/~glasen/+archive/intel-driver






                                                share|improve this answer














                                                Be careful setting i915.modeset=0.



                                                All versions since 2.15 of the Intel-driver only support KMS. If you've deactivated KMS e.g. by adding the option i915.modeset=0 to the file /etc/default/grub, please reactivate KMS by deleting this option.



                                                Source: https://launchpad.net/~glasen/+archive/intel-driver







                                                share|improve this answer














                                                share|improve this answer



                                                share|improve this answer








                                                edited Jun 29 '12 at 10:02









                                                Eliah Kagan

                                                81.2k20227364




                                                81.2k20227364










                                                answered May 15 '12 at 18:31









                                                Jason

                                                3,769399




                                                3,769399












                                                • Link is broken.
                                                  – ceving
                                                  Jun 6 at 7:43


















                                                • Link is broken.
                                                  – ceving
                                                  Jun 6 at 7:43
















                                                Link is broken.
                                                – ceving
                                                Jun 6 at 7:43




                                                Link is broken.
                                                – ceving
                                                Jun 6 at 7:43











                                                2














                                                Here is how I made i915 work in 14.04:



                                                I downloaded the intel-linux-graphics-installer from 01.org, ran the same program and followed the instructions. The program downgraded one package and installed a number of new packages. Eventually, I was prompted to reboot. I opened the site that normally causes my screen to go blank in google chrome. Since I observed no more crashes I take it the problem is resolved.



                                                Note that I have no more command line options added to grub. Also note that I run kernel 3.13.0-44 and Ubuntu 14.04.






                                                share|improve this answer




























                                                  2














                                                  Here is how I made i915 work in 14.04:



                                                  I downloaded the intel-linux-graphics-installer from 01.org, ran the same program and followed the instructions. The program downgraded one package and installed a number of new packages. Eventually, I was prompted to reboot. I opened the site that normally causes my screen to go blank in google chrome. Since I observed no more crashes I take it the problem is resolved.



                                                  Note that I have no more command line options added to grub. Also note that I run kernel 3.13.0-44 and Ubuntu 14.04.






                                                  share|improve this answer


























                                                    2












                                                    2








                                                    2






                                                    Here is how I made i915 work in 14.04:



                                                    I downloaded the intel-linux-graphics-installer from 01.org, ran the same program and followed the instructions. The program downgraded one package and installed a number of new packages. Eventually, I was prompted to reboot. I opened the site that normally causes my screen to go blank in google chrome. Since I observed no more crashes I take it the problem is resolved.



                                                    Note that I have no more command line options added to grub. Also note that I run kernel 3.13.0-44 and Ubuntu 14.04.






                                                    share|improve this answer














                                                    Here is how I made i915 work in 14.04:



                                                    I downloaded the intel-linux-graphics-installer from 01.org, ran the same program and followed the instructions. The program downgraded one package and installed a number of new packages. Eventually, I was prompted to reboot. I opened the site that normally causes my screen to go blank in google chrome. Since I observed no more crashes I take it the problem is resolved.



                                                    Note that I have no more command line options added to grub. Also note that I run kernel 3.13.0-44 and Ubuntu 14.04.







                                                    share|improve this answer














                                                    share|improve this answer



                                                    share|improve this answer








                                                    edited Feb 11 '15 at 6:30









                                                    A J

                                                    5,798153356




                                                    5,798153356










                                                    answered Feb 10 '15 at 23:33









                                                    dzmanto

                                                    211




                                                    211























                                                        0














                                                        i have a gateway nv78 with the black screen after the splash from the infamous intel mobile 4 chipset - actually it is the backlight - it is backwards? idek



                                                        external monitors work ok so you may need to use one to do this



                                                        anyway, boot the computer, and as root, edit the file /etc/rc.local

                                                        just before the exit 0 line, add the line
                                                        setpci -s 00:02.0 F4.B=00



                                                        save it



                                                        take out all the other things you've tried lol - be sure to run update-grub if you remove stuff from the grub quiet slpash part



                                                        reboot - the screen will go blank for a few seconds at boot like it used to do, but then about the time the mouse pointer arrow thing shows up the screen light will suddenly come back on and all is well



                                                        this works better than nomodeset as it gives you all the display modes and not just vesa 1280*720 - it now will detect plugged in monitors too and everything will work correctly






                                                        share|improve this answer


























                                                          0














                                                          i have a gateway nv78 with the black screen after the splash from the infamous intel mobile 4 chipset - actually it is the backlight - it is backwards? idek



                                                          external monitors work ok so you may need to use one to do this



                                                          anyway, boot the computer, and as root, edit the file /etc/rc.local

                                                          just before the exit 0 line, add the line
                                                          setpci -s 00:02.0 F4.B=00



                                                          save it



                                                          take out all the other things you've tried lol - be sure to run update-grub if you remove stuff from the grub quiet slpash part



                                                          reboot - the screen will go blank for a few seconds at boot like it used to do, but then about the time the mouse pointer arrow thing shows up the screen light will suddenly come back on and all is well



                                                          this works better than nomodeset as it gives you all the display modes and not just vesa 1280*720 - it now will detect plugged in monitors too and everything will work correctly






                                                          share|improve this answer
























                                                            0












                                                            0








                                                            0






                                                            i have a gateway nv78 with the black screen after the splash from the infamous intel mobile 4 chipset - actually it is the backlight - it is backwards? idek



                                                            external monitors work ok so you may need to use one to do this



                                                            anyway, boot the computer, and as root, edit the file /etc/rc.local

                                                            just before the exit 0 line, add the line
                                                            setpci -s 00:02.0 F4.B=00



                                                            save it



                                                            take out all the other things you've tried lol - be sure to run update-grub if you remove stuff from the grub quiet slpash part



                                                            reboot - the screen will go blank for a few seconds at boot like it used to do, but then about the time the mouse pointer arrow thing shows up the screen light will suddenly come back on and all is well



                                                            this works better than nomodeset as it gives you all the display modes and not just vesa 1280*720 - it now will detect plugged in monitors too and everything will work correctly






                                                            share|improve this answer












                                                            i have a gateway nv78 with the black screen after the splash from the infamous intel mobile 4 chipset - actually it is the backlight - it is backwards? idek



                                                            external monitors work ok so you may need to use one to do this



                                                            anyway, boot the computer, and as root, edit the file /etc/rc.local

                                                            just before the exit 0 line, add the line
                                                            setpci -s 00:02.0 F4.B=00



                                                            save it



                                                            take out all the other things you've tried lol - be sure to run update-grub if you remove stuff from the grub quiet slpash part



                                                            reboot - the screen will go blank for a few seconds at boot like it used to do, but then about the time the mouse pointer arrow thing shows up the screen light will suddenly come back on and all is well



                                                            this works better than nomodeset as it gives you all the display modes and not just vesa 1280*720 - it now will detect plugged in monitors too and everything will work correctly







                                                            share|improve this answer












                                                            share|improve this answer



                                                            share|improve this answer










                                                            answered Nov 27 '13 at 4:32









                                                            yee hue hue

                                                            1




                                                            1























                                                                0














                                                                I ran into this problem on my Dell Inspiron 3000. (The little 11' sub-$200 one, thanks Dell for reusing model numbers -_-)



                                                                Using 'nomodeset' did allow me to boot, but it had no GL acceleration and it was almost unbearable to use. On a whim, I changed a setting in the bios about legacy boot ROM (or something similar, I can't get the exact name without rebooting). After that was disabled, I was able to boot without issues. No black screen, and no need for 'nomodeset' that ruined the GL acceleration. I now have a very usable little laptop for configuring electronics in my model shop. o/






                                                                share|improve this answer


























                                                                  0














                                                                  I ran into this problem on my Dell Inspiron 3000. (The little 11' sub-$200 one, thanks Dell for reusing model numbers -_-)



                                                                  Using 'nomodeset' did allow me to boot, but it had no GL acceleration and it was almost unbearable to use. On a whim, I changed a setting in the bios about legacy boot ROM (or something similar, I can't get the exact name without rebooting). After that was disabled, I was able to boot without issues. No black screen, and no need for 'nomodeset' that ruined the GL acceleration. I now have a very usable little laptop for configuring electronics in my model shop. o/






                                                                  share|improve this answer
























                                                                    0












                                                                    0








                                                                    0






                                                                    I ran into this problem on my Dell Inspiron 3000. (The little 11' sub-$200 one, thanks Dell for reusing model numbers -_-)



                                                                    Using 'nomodeset' did allow me to boot, but it had no GL acceleration and it was almost unbearable to use. On a whim, I changed a setting in the bios about legacy boot ROM (or something similar, I can't get the exact name without rebooting). After that was disabled, I was able to boot without issues. No black screen, and no need for 'nomodeset' that ruined the GL acceleration. I now have a very usable little laptop for configuring electronics in my model shop. o/






                                                                    share|improve this answer












                                                                    I ran into this problem on my Dell Inspiron 3000. (The little 11' sub-$200 one, thanks Dell for reusing model numbers -_-)



                                                                    Using 'nomodeset' did allow me to boot, but it had no GL acceleration and it was almost unbearable to use. On a whim, I changed a setting in the bios about legacy boot ROM (or something similar, I can't get the exact name without rebooting). After that was disabled, I was able to boot without issues. No black screen, and no need for 'nomodeset' that ruined the GL acceleration. I now have a very usable little laptop for configuring electronics in my model shop. o/







                                                                    share|improve this answer












                                                                    share|improve this answer



                                                                    share|improve this answer










                                                                    answered Sep 24 '16 at 8:46









                                                                    Scott

                                                                    91




                                                                    91























                                                                        0














                                                                        My mobo is Intel D2500HN which has only 1 VGA port and no LVDS-1.
                                                                        My distro: Lubuntu 18.04



                                                                        ~$ modinfo i915
                                                                        modinfo: ERROR: Module i915 not found.


                                                                        Make sure that both your /lib/firmware/i915/ and /lib/modules/'uname -r'/ are populated with files



                                                                        ~$ sudo apt install --reinstall linux-modules-'uname -r' linux-modules-extra-'uname -r'


                                                                        My problem description:



                                                                        4.15.0-20-generic: displaying FHD1920x1080 ok



                                                                        4.15.0-42-generic: blank screen after a few lines appear after grub screen



                                                                        ~$ sudo lspci -v | grep -A 10 -i vga <p>
                                                                        00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) <p> (prog-if 00 [VGA controller])
                                                                        Subsystem: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller
                                                                        Flags: bus master, fast devsel, latency 0, IRQ 28
                                                                        Memory at d0100000 (32-bit, non-prefetchable) [size=1M]
                                                                        I/O ports at 20d0 [size=8]
                                                                        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
                                                                        Capabilities: <access denied>
                                                                        Kernel driver in use: gma500
                                                                        Kernel modules: gma500_gfx


                                                                        My solution:



                                                                        ~$ sudo <your_editor> /etc/default/grub
                                                                        ##video=LVDS-1:d is disabling LVDS-1 port which some kernel version might be directing the video to that port on default despite your mobo might not have such a port available to you
                                                                        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 video=LVDS-1:d"


                                                                        My problem solved, credit due to Loading Arch on Intel D2500CC board - i915 complaining about / Installation / Arch Linux Forums
                                                                        which in turn drew his solution from
                                                                        Mageia support for GMA 3600 (Cedar Trail Atom)






                                                                        share|improve this answer










                                                                        New contributor




                                                                        Wilson Wong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                                        Check out our Code of Conduct.























                                                                          0














                                                                          My mobo is Intel D2500HN which has only 1 VGA port and no LVDS-1.
                                                                          My distro: Lubuntu 18.04



                                                                          ~$ modinfo i915
                                                                          modinfo: ERROR: Module i915 not found.


                                                                          Make sure that both your /lib/firmware/i915/ and /lib/modules/'uname -r'/ are populated with files



                                                                          ~$ sudo apt install --reinstall linux-modules-'uname -r' linux-modules-extra-'uname -r'


                                                                          My problem description:



                                                                          4.15.0-20-generic: displaying FHD1920x1080 ok



                                                                          4.15.0-42-generic: blank screen after a few lines appear after grub screen



                                                                          ~$ sudo lspci -v | grep -A 10 -i vga <p>
                                                                          00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) <p> (prog-if 00 [VGA controller])
                                                                          Subsystem: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller
                                                                          Flags: bus master, fast devsel, latency 0, IRQ 28
                                                                          Memory at d0100000 (32-bit, non-prefetchable) [size=1M]
                                                                          I/O ports at 20d0 [size=8]
                                                                          [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
                                                                          Capabilities: <access denied>
                                                                          Kernel driver in use: gma500
                                                                          Kernel modules: gma500_gfx


                                                                          My solution:



                                                                          ~$ sudo <your_editor> /etc/default/grub
                                                                          ##video=LVDS-1:d is disabling LVDS-1 port which some kernel version might be directing the video to that port on default despite your mobo might not have such a port available to you
                                                                          GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 video=LVDS-1:d"


                                                                          My problem solved, credit due to Loading Arch on Intel D2500CC board - i915 complaining about / Installation / Arch Linux Forums
                                                                          which in turn drew his solution from
                                                                          Mageia support for GMA 3600 (Cedar Trail Atom)






                                                                          share|improve this answer










                                                                          New contributor




                                                                          Wilson Wong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                                          Check out our Code of Conduct.





















                                                                            0












                                                                            0








                                                                            0






                                                                            My mobo is Intel D2500HN which has only 1 VGA port and no LVDS-1.
                                                                            My distro: Lubuntu 18.04



                                                                            ~$ modinfo i915
                                                                            modinfo: ERROR: Module i915 not found.


                                                                            Make sure that both your /lib/firmware/i915/ and /lib/modules/'uname -r'/ are populated with files



                                                                            ~$ sudo apt install --reinstall linux-modules-'uname -r' linux-modules-extra-'uname -r'


                                                                            My problem description:



                                                                            4.15.0-20-generic: displaying FHD1920x1080 ok



                                                                            4.15.0-42-generic: blank screen after a few lines appear after grub screen



                                                                            ~$ sudo lspci -v | grep -A 10 -i vga <p>
                                                                            00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) <p> (prog-if 00 [VGA controller])
                                                                            Subsystem: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller
                                                                            Flags: bus master, fast devsel, latency 0, IRQ 28
                                                                            Memory at d0100000 (32-bit, non-prefetchable) [size=1M]
                                                                            I/O ports at 20d0 [size=8]
                                                                            [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
                                                                            Capabilities: <access denied>
                                                                            Kernel driver in use: gma500
                                                                            Kernel modules: gma500_gfx


                                                                            My solution:



                                                                            ~$ sudo <your_editor> /etc/default/grub
                                                                            ##video=LVDS-1:d is disabling LVDS-1 port which some kernel version might be directing the video to that port on default despite your mobo might not have such a port available to you
                                                                            GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 video=LVDS-1:d"


                                                                            My problem solved, credit due to Loading Arch on Intel D2500CC board - i915 complaining about / Installation / Arch Linux Forums
                                                                            which in turn drew his solution from
                                                                            Mageia support for GMA 3600 (Cedar Trail Atom)






                                                                            share|improve this answer










                                                                            New contributor




                                                                            Wilson Wong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                                            Check out our Code of Conduct.









                                                                            My mobo is Intel D2500HN which has only 1 VGA port and no LVDS-1.
                                                                            My distro: Lubuntu 18.04



                                                                            ~$ modinfo i915
                                                                            modinfo: ERROR: Module i915 not found.


                                                                            Make sure that both your /lib/firmware/i915/ and /lib/modules/'uname -r'/ are populated with files



                                                                            ~$ sudo apt install --reinstall linux-modules-'uname -r' linux-modules-extra-'uname -r'


                                                                            My problem description:



                                                                            4.15.0-20-generic: displaying FHD1920x1080 ok



                                                                            4.15.0-42-generic: blank screen after a few lines appear after grub screen



                                                                            ~$ sudo lspci -v | grep -A 10 -i vga <p>
                                                                            00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) <p> (prog-if 00 [VGA controller])
                                                                            Subsystem: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller
                                                                            Flags: bus master, fast devsel, latency 0, IRQ 28
                                                                            Memory at d0100000 (32-bit, non-prefetchable) [size=1M]
                                                                            I/O ports at 20d0 [size=8]
                                                                            [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
                                                                            Capabilities: <access denied>
                                                                            Kernel driver in use: gma500
                                                                            Kernel modules: gma500_gfx


                                                                            My solution:



                                                                            ~$ sudo <your_editor> /etc/default/grub
                                                                            ##video=LVDS-1:d is disabling LVDS-1 port which some kernel version might be directing the video to that port on default despite your mobo might not have such a port available to you
                                                                            GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=1 video=LVDS-1:d"


                                                                            My problem solved, credit due to Loading Arch on Intel D2500CC board - i915 complaining about / Installation / Arch Linux Forums
                                                                            which in turn drew his solution from
                                                                            Mageia support for GMA 3600 (Cedar Trail Atom)







                                                                            share|improve this answer










                                                                            New contributor




                                                                            Wilson Wong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                                            Check out our Code of Conduct.









                                                                            share|improve this answer



                                                                            share|improve this answer








                                                                            edited Dec 20 at 8:10









                                                                            Kulfy

                                                                            3,25531039




                                                                            3,25531039






                                                                            New contributor




                                                                            Wilson Wong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                                            Check out our Code of Conduct.









                                                                            answered Dec 20 at 7:42









                                                                            Wilson Wong

                                                                            11




                                                                            11




                                                                            New contributor




                                                                            Wilson Wong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                                            Check out our Code of Conduct.





                                                                            New contributor





                                                                            Wilson Wong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                                            Check out our Code of Conduct.






                                                                            Wilson Wong is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                                                            Check out our Code of Conduct.






























                                                                                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.





                                                                                Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                                                                                Please pay close attention to the following guidance:


                                                                                • 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%2f136593%2fhow-can-i-fix-broken-i915-drivers-for-intel-gpus%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

                                                                                How did Captain America manage to do this?

                                                                                迪纳利

                                                                                南乌拉尔铁路局