Intel HD graphics 4400 not working properly on Wheezy












3














Upon login, I get the following message:




GNOME 3 Failed to Load



Unfortunately GNOME 3 failed to start properly and started in the fallback mode.



This most likely means your system (graphics hardware or driver) is not capable of delivering the full GNOME 3 experience.




Here's some more information:



$ grep EE /var/log/Xorg.0.log
[ 2.866] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument


(the error message actually shows some tens of times).



$ sudo lspci -vk|grep -A 10 VGA
00:02.0 VGA compatible controller: Intel Corporation Device 041e (rev 06) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 8534
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915

$ uname -a
Linux orestis 3.10-0.bpo.3-amd64 #1 SMP Debian 3.10.11-1~bpo70+1 (2013-09-24) x86_64 GNU/Linux


I seem to have all required packages installed (xserver-xorg-video-intel and i965-va-driver).










share|improve this question






















  • Does it start with startx?
    – MariusMatutiae
    Nov 29 '13 at 14:38










  • No, with startx I have exactly the same symptoms.
    – Antonis Christofides
    Nov 29 '13 at 14:54
















3














Upon login, I get the following message:




GNOME 3 Failed to Load



Unfortunately GNOME 3 failed to start properly and started in the fallback mode.



This most likely means your system (graphics hardware or driver) is not capable of delivering the full GNOME 3 experience.




Here's some more information:



$ grep EE /var/log/Xorg.0.log
[ 2.866] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument


(the error message actually shows some tens of times).



$ sudo lspci -vk|grep -A 10 VGA
00:02.0 VGA compatible controller: Intel Corporation Device 041e (rev 06) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 8534
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915

$ uname -a
Linux orestis 3.10-0.bpo.3-amd64 #1 SMP Debian 3.10.11-1~bpo70+1 (2013-09-24) x86_64 GNU/Linux


I seem to have all required packages installed (xserver-xorg-video-intel and i965-va-driver).










share|improve this question






















  • Does it start with startx?
    – MariusMatutiae
    Nov 29 '13 at 14:38










  • No, with startx I have exactly the same symptoms.
    – Antonis Christofides
    Nov 29 '13 at 14:54














3












3








3







Upon login, I get the following message:




GNOME 3 Failed to Load



Unfortunately GNOME 3 failed to start properly and started in the fallback mode.



This most likely means your system (graphics hardware or driver) is not capable of delivering the full GNOME 3 experience.




Here's some more information:



$ grep EE /var/log/Xorg.0.log
[ 2.866] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument


(the error message actually shows some tens of times).



$ sudo lspci -vk|grep -A 10 VGA
00:02.0 VGA compatible controller: Intel Corporation Device 041e (rev 06) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 8534
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915

$ uname -a
Linux orestis 3.10-0.bpo.3-amd64 #1 SMP Debian 3.10.11-1~bpo70+1 (2013-09-24) x86_64 GNU/Linux


I seem to have all required packages installed (xserver-xorg-video-intel and i965-va-driver).










share|improve this question













Upon login, I get the following message:




GNOME 3 Failed to Load



Unfortunately GNOME 3 failed to start properly and started in the fallback mode.



This most likely means your system (graphics hardware or driver) is not capable of delivering the full GNOME 3 experience.




Here's some more information:



$ grep EE /var/log/Xorg.0.log
[ 2.866] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument


(the error message actually shows some tens of times).



$ sudo lspci -vk|grep -A 10 VGA
00:02.0 VGA compatible controller: Intel Corporation Device 041e (rev 06) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 8534
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915

$ uname -a
Linux orestis 3.10-0.bpo.3-amd64 #1 SMP Debian 3.10.11-1~bpo70+1 (2013-09-24) x86_64 GNU/Linux


I seem to have all required packages installed (xserver-xorg-video-intel and i965-va-driver).







debian gnome3 debian-wheezy intel-graphics






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 29 '13 at 14:00









Antonis ChristofidesAntonis Christofides

283216




283216












  • Does it start with startx?
    – MariusMatutiae
    Nov 29 '13 at 14:38










  • No, with startx I have exactly the same symptoms.
    – Antonis Christofides
    Nov 29 '13 at 14:54


















  • Does it start with startx?
    – MariusMatutiae
    Nov 29 '13 at 14:38










  • No, with startx I have exactly the same symptoms.
    – Antonis Christofides
    Nov 29 '13 at 14:54
















Does it start with startx?
– MariusMatutiae
Nov 29 '13 at 14:38




Does it start with startx?
– MariusMatutiae
Nov 29 '13 at 14:38












No, with startx I have exactly the same symptoms.
– Antonis Christofides
Nov 29 '13 at 14:54




No, with startx I have exactly the same symptoms.
– Antonis Christofides
Nov 29 '13 at 14:54










4 Answers
4






active

oldest

votes


















0














Try as follows:



 sudo apt-get update
sudo apt-get -d install --reinstall gdm
sudo apt-get remove --purge gdm
sudo apt-get install gdm


(now you may be asked to choose your wm, I do not remember exactly, if so choose gdm)



 sudo reboot





share|improve this answer





















  • I did the above, using gdm3 instead of gdm, and also, for the fourth command, I told it sudo apt-get install task-gnome-desktop instead, which installed gdm3 (and gnome and gnome-core, which had been uninstalled together with gdm3). No luck. (This is a fresh clean install of Wheezy, so I didn't think this could work.)
    – Antonis Christofides
    Nov 29 '13 at 14:56










  • @AntonisChristofides Try lightdm?
    – MariusMatutiae
    Nov 29 '13 at 14:57










  • Since I have the same symptoms with startx, isn't it unlikely that the problem is the display manager?
    – Antonis Christofides
    Nov 29 '13 at 14:59










  • @AntonisChristofides yes, but unlikely, not certain, is the key word. It takes 30 seconds to try. The alternative is to re-install, google around and you'll see no other way around this error.
    – MariusMatutiae
    Nov 29 '13 at 15:01










  • Tried it. Same symptoms, same messages in log.
    – Antonis Christofides
    Nov 29 '13 at 15:29



















0














Obviously which Display Manager you use has zero to do with this issue.



Try a 3.12 kernel and if that does not work do the following:




  1. First try a kernel built from intel hd 4400 linux http://cgit.freedesktop.org/~danvet/drm-intel/?h=drm-intel-next


  2. If the solution above fails, bring it up on the developer list intel-gfx at freedesktop







share|improve this answer























  • 3.12 didn't work. I will wait for 3.13.
    – Antonis Christofides
    Dec 31 '13 at 12:54






  • 1




    3.13 doesn't work either.
    – Antonis Christofides
    Feb 14 '14 at 16:40



















0














I had the same issue with wheezy and i3-4130 CPU. I switched to testing and gnome 3 started to work out of the box, without any configuration.






share|improve this answer





























    0














    I had to install a bunch of packages from backports:



    sudo apt-get install -t wheezy-backports linux-image-3.16.0-0.bpo.4-amd64 firmware-linux i965-va-driver xserver-xorg-video-intel
    sudo service gdm3 restart


    I also rebooted a few times and i'm not sure if all the above are necessary.






    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      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%2fsuperuser.com%2fquestions%2f682131%2fintel-hd-graphics-4400-not-working-properly-on-wheezy%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      Try as follows:



       sudo apt-get update
      sudo apt-get -d install --reinstall gdm
      sudo apt-get remove --purge gdm
      sudo apt-get install gdm


      (now you may be asked to choose your wm, I do not remember exactly, if so choose gdm)



       sudo reboot





      share|improve this answer





















      • I did the above, using gdm3 instead of gdm, and also, for the fourth command, I told it sudo apt-get install task-gnome-desktop instead, which installed gdm3 (and gnome and gnome-core, which had been uninstalled together with gdm3). No luck. (This is a fresh clean install of Wheezy, so I didn't think this could work.)
        – Antonis Christofides
        Nov 29 '13 at 14:56










      • @AntonisChristofides Try lightdm?
        – MariusMatutiae
        Nov 29 '13 at 14:57










      • Since I have the same symptoms with startx, isn't it unlikely that the problem is the display manager?
        – Antonis Christofides
        Nov 29 '13 at 14:59










      • @AntonisChristofides yes, but unlikely, not certain, is the key word. It takes 30 seconds to try. The alternative is to re-install, google around and you'll see no other way around this error.
        – MariusMatutiae
        Nov 29 '13 at 15:01










      • Tried it. Same symptoms, same messages in log.
        – Antonis Christofides
        Nov 29 '13 at 15:29
















      0














      Try as follows:



       sudo apt-get update
      sudo apt-get -d install --reinstall gdm
      sudo apt-get remove --purge gdm
      sudo apt-get install gdm


      (now you may be asked to choose your wm, I do not remember exactly, if so choose gdm)



       sudo reboot





      share|improve this answer





















      • I did the above, using gdm3 instead of gdm, and also, for the fourth command, I told it sudo apt-get install task-gnome-desktop instead, which installed gdm3 (and gnome and gnome-core, which had been uninstalled together with gdm3). No luck. (This is a fresh clean install of Wheezy, so I didn't think this could work.)
        – Antonis Christofides
        Nov 29 '13 at 14:56










      • @AntonisChristofides Try lightdm?
        – MariusMatutiae
        Nov 29 '13 at 14:57










      • Since I have the same symptoms with startx, isn't it unlikely that the problem is the display manager?
        – Antonis Christofides
        Nov 29 '13 at 14:59










      • @AntonisChristofides yes, but unlikely, not certain, is the key word. It takes 30 seconds to try. The alternative is to re-install, google around and you'll see no other way around this error.
        – MariusMatutiae
        Nov 29 '13 at 15:01










      • Tried it. Same symptoms, same messages in log.
        – Antonis Christofides
        Nov 29 '13 at 15:29














      0












      0








      0






      Try as follows:



       sudo apt-get update
      sudo apt-get -d install --reinstall gdm
      sudo apt-get remove --purge gdm
      sudo apt-get install gdm


      (now you may be asked to choose your wm, I do not remember exactly, if so choose gdm)



       sudo reboot





      share|improve this answer












      Try as follows:



       sudo apt-get update
      sudo apt-get -d install --reinstall gdm
      sudo apt-get remove --purge gdm
      sudo apt-get install gdm


      (now you may be asked to choose your wm, I do not remember exactly, if so choose gdm)



       sudo reboot






      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Nov 29 '13 at 14:46









      MariusMatutiaeMariusMatutiae

      38.1k95195




      38.1k95195












      • I did the above, using gdm3 instead of gdm, and also, for the fourth command, I told it sudo apt-get install task-gnome-desktop instead, which installed gdm3 (and gnome and gnome-core, which had been uninstalled together with gdm3). No luck. (This is a fresh clean install of Wheezy, so I didn't think this could work.)
        – Antonis Christofides
        Nov 29 '13 at 14:56










      • @AntonisChristofides Try lightdm?
        – MariusMatutiae
        Nov 29 '13 at 14:57










      • Since I have the same symptoms with startx, isn't it unlikely that the problem is the display manager?
        – Antonis Christofides
        Nov 29 '13 at 14:59










      • @AntonisChristofides yes, but unlikely, not certain, is the key word. It takes 30 seconds to try. The alternative is to re-install, google around and you'll see no other way around this error.
        – MariusMatutiae
        Nov 29 '13 at 15:01










      • Tried it. Same symptoms, same messages in log.
        – Antonis Christofides
        Nov 29 '13 at 15:29


















      • I did the above, using gdm3 instead of gdm, and also, for the fourth command, I told it sudo apt-get install task-gnome-desktop instead, which installed gdm3 (and gnome and gnome-core, which had been uninstalled together with gdm3). No luck. (This is a fresh clean install of Wheezy, so I didn't think this could work.)
        – Antonis Christofides
        Nov 29 '13 at 14:56










      • @AntonisChristofides Try lightdm?
        – MariusMatutiae
        Nov 29 '13 at 14:57










      • Since I have the same symptoms with startx, isn't it unlikely that the problem is the display manager?
        – Antonis Christofides
        Nov 29 '13 at 14:59










      • @AntonisChristofides yes, but unlikely, not certain, is the key word. It takes 30 seconds to try. The alternative is to re-install, google around and you'll see no other way around this error.
        – MariusMatutiae
        Nov 29 '13 at 15:01










      • Tried it. Same symptoms, same messages in log.
        – Antonis Christofides
        Nov 29 '13 at 15:29
















      I did the above, using gdm3 instead of gdm, and also, for the fourth command, I told it sudo apt-get install task-gnome-desktop instead, which installed gdm3 (and gnome and gnome-core, which had been uninstalled together with gdm3). No luck. (This is a fresh clean install of Wheezy, so I didn't think this could work.)
      – Antonis Christofides
      Nov 29 '13 at 14:56




      I did the above, using gdm3 instead of gdm, and also, for the fourth command, I told it sudo apt-get install task-gnome-desktop instead, which installed gdm3 (and gnome and gnome-core, which had been uninstalled together with gdm3). No luck. (This is a fresh clean install of Wheezy, so I didn't think this could work.)
      – Antonis Christofides
      Nov 29 '13 at 14:56












      @AntonisChristofides Try lightdm?
      – MariusMatutiae
      Nov 29 '13 at 14:57




      @AntonisChristofides Try lightdm?
      – MariusMatutiae
      Nov 29 '13 at 14:57












      Since I have the same symptoms with startx, isn't it unlikely that the problem is the display manager?
      – Antonis Christofides
      Nov 29 '13 at 14:59




      Since I have the same symptoms with startx, isn't it unlikely that the problem is the display manager?
      – Antonis Christofides
      Nov 29 '13 at 14:59












      @AntonisChristofides yes, but unlikely, not certain, is the key word. It takes 30 seconds to try. The alternative is to re-install, google around and you'll see no other way around this error.
      – MariusMatutiae
      Nov 29 '13 at 15:01




      @AntonisChristofides yes, but unlikely, not certain, is the key word. It takes 30 seconds to try. The alternative is to re-install, google around and you'll see no other way around this error.
      – MariusMatutiae
      Nov 29 '13 at 15:01












      Tried it. Same symptoms, same messages in log.
      – Antonis Christofides
      Nov 29 '13 at 15:29




      Tried it. Same symptoms, same messages in log.
      – Antonis Christofides
      Nov 29 '13 at 15:29













      0














      Obviously which Display Manager you use has zero to do with this issue.



      Try a 3.12 kernel and if that does not work do the following:




      1. First try a kernel built from intel hd 4400 linux http://cgit.freedesktop.org/~danvet/drm-intel/?h=drm-intel-next


      2. If the solution above fails, bring it up on the developer list intel-gfx at freedesktop







      share|improve this answer























      • 3.12 didn't work. I will wait for 3.13.
        – Antonis Christofides
        Dec 31 '13 at 12:54






      • 1




        3.13 doesn't work either.
        – Antonis Christofides
        Feb 14 '14 at 16:40
















      0














      Obviously which Display Manager you use has zero to do with this issue.



      Try a 3.12 kernel and if that does not work do the following:




      1. First try a kernel built from intel hd 4400 linux http://cgit.freedesktop.org/~danvet/drm-intel/?h=drm-intel-next


      2. If the solution above fails, bring it up on the developer list intel-gfx at freedesktop







      share|improve this answer























      • 3.12 didn't work. I will wait for 3.13.
        – Antonis Christofides
        Dec 31 '13 at 12:54






      • 1




        3.13 doesn't work either.
        – Antonis Christofides
        Feb 14 '14 at 16:40














      0












      0








      0






      Obviously which Display Manager you use has zero to do with this issue.



      Try a 3.12 kernel and if that does not work do the following:




      1. First try a kernel built from intel hd 4400 linux http://cgit.freedesktop.org/~danvet/drm-intel/?h=drm-intel-next


      2. If the solution above fails, bring it up on the developer list intel-gfx at freedesktop







      share|improve this answer














      Obviously which Display Manager you use has zero to do with this issue.



      Try a 3.12 kernel and if that does not work do the following:




      1. First try a kernel built from intel hd 4400 linux http://cgit.freedesktop.org/~danvet/drm-intel/?h=drm-intel-next


      2. If the solution above fails, bring it up on the developer list intel-gfx at freedesktop








      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Dec 22 '13 at 11:41









      gronostaj

      28k1368107




      28k1368107










      answered Dec 22 '13 at 7:49









      Mr. MMr. M

      1




      1












      • 3.12 didn't work. I will wait for 3.13.
        – Antonis Christofides
        Dec 31 '13 at 12:54






      • 1




        3.13 doesn't work either.
        – Antonis Christofides
        Feb 14 '14 at 16:40


















      • 3.12 didn't work. I will wait for 3.13.
        – Antonis Christofides
        Dec 31 '13 at 12:54






      • 1




        3.13 doesn't work either.
        – Antonis Christofides
        Feb 14 '14 at 16:40
















      3.12 didn't work. I will wait for 3.13.
      – Antonis Christofides
      Dec 31 '13 at 12:54




      3.12 didn't work. I will wait for 3.13.
      – Antonis Christofides
      Dec 31 '13 at 12:54




      1




      1




      3.13 doesn't work either.
      – Antonis Christofides
      Feb 14 '14 at 16:40




      3.13 doesn't work either.
      – Antonis Christofides
      Feb 14 '14 at 16:40











      0














      I had the same issue with wheezy and i3-4130 CPU. I switched to testing and gnome 3 started to work out of the box, without any configuration.






      share|improve this answer


























        0














        I had the same issue with wheezy and i3-4130 CPU. I switched to testing and gnome 3 started to work out of the box, without any configuration.






        share|improve this answer
























          0












          0








          0






          I had the same issue with wheezy and i3-4130 CPU. I switched to testing and gnome 3 started to work out of the box, without any configuration.






          share|improve this answer












          I had the same issue with wheezy and i3-4130 CPU. I switched to testing and gnome 3 started to work out of the box, without any configuration.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 22 '14 at 7:25









          n0rdn0rd

          1014




          1014























              0














              I had to install a bunch of packages from backports:



              sudo apt-get install -t wheezy-backports linux-image-3.16.0-0.bpo.4-amd64 firmware-linux i965-va-driver xserver-xorg-video-intel
              sudo service gdm3 restart


              I also rebooted a few times and i'm not sure if all the above are necessary.






              share|improve this answer


























                0














                I had to install a bunch of packages from backports:



                sudo apt-get install -t wheezy-backports linux-image-3.16.0-0.bpo.4-amd64 firmware-linux i965-va-driver xserver-xorg-video-intel
                sudo service gdm3 restart


                I also rebooted a few times and i'm not sure if all the above are necessary.






                share|improve this answer
























                  0












                  0








                  0






                  I had to install a bunch of packages from backports:



                  sudo apt-get install -t wheezy-backports linux-image-3.16.0-0.bpo.4-amd64 firmware-linux i965-va-driver xserver-xorg-video-intel
                  sudo service gdm3 restart


                  I also rebooted a few times and i'm not sure if all the above are necessary.






                  share|improve this answer












                  I had to install a bunch of packages from backports:



                  sudo apt-get install -t wheezy-backports linux-image-3.16.0-0.bpo.4-amd64 firmware-linux i965-va-driver xserver-xorg-video-intel
                  sudo service gdm3 restart


                  I also rebooted a few times and i'm not sure if all the above are necessary.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 25 '15 at 23:32









                  anarcatanarcat

                  30929




                  30929






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • 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%2fsuperuser.com%2fquestions%2f682131%2fintel-hd-graphics-4400-not-working-properly-on-wheezy%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

                      Plaza Victoria

                      Puebla de Zaragoza

                      Musa