Graphics problems on Asus EEE 1101 HA, Precise Pangolin











up vote
0
down vote

favorite












I installed Precise Pangolin x386 Desktop version via USB stick without incident.



There are two, possibly related, problems:




  1. After suspend (e.g. closing the lid), the graphics are corrupted as shown in this pic: http://imgur.com/hoIBQ. The only solution seems to be a complete reboot.


  2. Upon booting, the following happens: The screen goes black. After a while the little sound notification is heard. By switching to a text terminal (Ctrl+Alt+F5) and then immediately back (Ctrl+Alt+F7) I get the X session. However, the graphics are corrupted. Only the top half of the screen is used, and both halves of the desktop are rendered on top of each other. The mouse movement wrap around the top and bottom of the screen. The only solution is to log in, then log out again. After doing this the graphics are normal until next suspend or power-off.



I have tried disabling desktop effect, logging in with Unity 2D, and uninstalling Compiz, without success.



I've had this computer for years without successfully being able to run Linux on it, please help!










share|improve this question
























  • Suspend/Hibernation is disabled on 12.04 by default.Pls read this wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop. About graphics, please run the "additional driver" from system>Preference if possible (if not, please run lspci -v in terminal and post the output for your video card here)and do install the "recommended".Please update your post after these tweaks.
    – beeju
    May 1 '12 at 7:21












  • Only "suspend to disk" is disabled. Normal suspend is enabled by default.
    – erikjber
    May 1 '12 at 7:54










  • Output of lspci -v: '00:02.0 VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 83ce Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at f3f80000 (32-bit, non-prefetchable) [size=512K] I/O ports at c880 [size=8] Memory at d0000000 (32-bit, non-prefetchable) [size=256M] Memory at f3f40000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: gma500 Kernel modules: psb_gfx '
    – erikjber
    May 1 '12 at 8:10








  • 1




    Please remember to post your solution as an answer when the system lets you, thanks!
    – Jorge Castro
    May 1 '12 at 13:07















up vote
0
down vote

favorite












I installed Precise Pangolin x386 Desktop version via USB stick without incident.



There are two, possibly related, problems:




  1. After suspend (e.g. closing the lid), the graphics are corrupted as shown in this pic: http://imgur.com/hoIBQ. The only solution seems to be a complete reboot.


  2. Upon booting, the following happens: The screen goes black. After a while the little sound notification is heard. By switching to a text terminal (Ctrl+Alt+F5) and then immediately back (Ctrl+Alt+F7) I get the X session. However, the graphics are corrupted. Only the top half of the screen is used, and both halves of the desktop are rendered on top of each other. The mouse movement wrap around the top and bottom of the screen. The only solution is to log in, then log out again. After doing this the graphics are normal until next suspend or power-off.



I have tried disabling desktop effect, logging in with Unity 2D, and uninstalling Compiz, without success.



I've had this computer for years without successfully being able to run Linux on it, please help!










share|improve this question
























  • Suspend/Hibernation is disabled on 12.04 by default.Pls read this wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop. About graphics, please run the "additional driver" from system>Preference if possible (if not, please run lspci -v in terminal and post the output for your video card here)and do install the "recommended".Please update your post after these tweaks.
    – beeju
    May 1 '12 at 7:21












  • Only "suspend to disk" is disabled. Normal suspend is enabled by default.
    – erikjber
    May 1 '12 at 7:54










  • Output of lspci -v: '00:02.0 VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 83ce Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at f3f80000 (32-bit, non-prefetchable) [size=512K] I/O ports at c880 [size=8] Memory at d0000000 (32-bit, non-prefetchable) [size=256M] Memory at f3f40000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: gma500 Kernel modules: psb_gfx '
    – erikjber
    May 1 '12 at 8:10








  • 1




    Please remember to post your solution as an answer when the system lets you, thanks!
    – Jorge Castro
    May 1 '12 at 13:07













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I installed Precise Pangolin x386 Desktop version via USB stick without incident.



There are two, possibly related, problems:




  1. After suspend (e.g. closing the lid), the graphics are corrupted as shown in this pic: http://imgur.com/hoIBQ. The only solution seems to be a complete reboot.


  2. Upon booting, the following happens: The screen goes black. After a while the little sound notification is heard. By switching to a text terminal (Ctrl+Alt+F5) and then immediately back (Ctrl+Alt+F7) I get the X session. However, the graphics are corrupted. Only the top half of the screen is used, and both halves of the desktop are rendered on top of each other. The mouse movement wrap around the top and bottom of the screen. The only solution is to log in, then log out again. After doing this the graphics are normal until next suspend or power-off.



I have tried disabling desktop effect, logging in with Unity 2D, and uninstalling Compiz, without success.



I've had this computer for years without successfully being able to run Linux on it, please help!










share|improve this question















I installed Precise Pangolin x386 Desktop version via USB stick without incident.



There are two, possibly related, problems:




  1. After suspend (e.g. closing the lid), the graphics are corrupted as shown in this pic: http://imgur.com/hoIBQ. The only solution seems to be a complete reboot.


  2. Upon booting, the following happens: The screen goes black. After a while the little sound notification is heard. By switching to a text terminal (Ctrl+Alt+F5) and then immediately back (Ctrl+Alt+F7) I get the X session. However, the graphics are corrupted. Only the top half of the screen is used, and both halves of the desktop are rendered on top of each other. The mouse movement wrap around the top and bottom of the screen. The only solution is to log in, then log out again. After doing this the graphics are normal until next suspend or power-off.



I have tried disabling desktop effect, logging in with Unity 2D, and uninstalling Compiz, without success.



I've had this computer for years without successfully being able to run Linux on it, please help!







xorg intel-graphics asus poulsbo






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 28 '16 at 2:43









chaskes

13k74059




13k74059










asked May 1 '12 at 7:01









erikjber

124




124












  • Suspend/Hibernation is disabled on 12.04 by default.Pls read this wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop. About graphics, please run the "additional driver" from system>Preference if possible (if not, please run lspci -v in terminal and post the output for your video card here)and do install the "recommended".Please update your post after these tweaks.
    – beeju
    May 1 '12 at 7:21












  • Only "suspend to disk" is disabled. Normal suspend is enabled by default.
    – erikjber
    May 1 '12 at 7:54










  • Output of lspci -v: '00:02.0 VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 83ce Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at f3f80000 (32-bit, non-prefetchable) [size=512K] I/O ports at c880 [size=8] Memory at d0000000 (32-bit, non-prefetchable) [size=256M] Memory at f3f40000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: gma500 Kernel modules: psb_gfx '
    – erikjber
    May 1 '12 at 8:10








  • 1




    Please remember to post your solution as an answer when the system lets you, thanks!
    – Jorge Castro
    May 1 '12 at 13:07


















  • Suspend/Hibernation is disabled on 12.04 by default.Pls read this wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop. About graphics, please run the "additional driver" from system>Preference if possible (if not, please run lspci -v in terminal and post the output for your video card here)and do install the "recommended".Please update your post after these tweaks.
    – beeju
    May 1 '12 at 7:21












  • Only "suspend to disk" is disabled. Normal suspend is enabled by default.
    – erikjber
    May 1 '12 at 7:54










  • Output of lspci -v: '00:02.0 VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 83ce Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at f3f80000 (32-bit, non-prefetchable) [size=512K] I/O ports at c880 [size=8] Memory at d0000000 (32-bit, non-prefetchable) [size=256M] Memory at f3f40000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: gma500 Kernel modules: psb_gfx '
    – erikjber
    May 1 '12 at 8:10








  • 1




    Please remember to post your solution as an answer when the system lets you, thanks!
    – Jorge Castro
    May 1 '12 at 13:07
















Suspend/Hibernation is disabled on 12.04 by default.Pls read this wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop. About graphics, please run the "additional driver" from system>Preference if possible (if not, please run lspci -v in terminal and post the output for your video card here)and do install the "recommended".Please update your post after these tweaks.
– beeju
May 1 '12 at 7:21






Suspend/Hibernation is disabled on 12.04 by default.Pls read this wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop. About graphics, please run the "additional driver" from system>Preference if possible (if not, please run lspci -v in terminal and post the output for your video card here)and do install the "recommended".Please update your post after these tweaks.
– beeju
May 1 '12 at 7:21














Only "suspend to disk" is disabled. Normal suspend is enabled by default.
– erikjber
May 1 '12 at 7:54




Only "suspend to disk" is disabled. Normal suspend is enabled by default.
– erikjber
May 1 '12 at 7:54












Output of lspci -v: '00:02.0 VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 83ce Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at f3f80000 (32-bit, non-prefetchable) [size=512K] I/O ports at c880 [size=8] Memory at d0000000 (32-bit, non-prefetchable) [size=256M] Memory at f3f40000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: gma500 Kernel modules: psb_gfx '
– erikjber
May 1 '12 at 8:10






Output of lspci -v: '00:02.0 VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 83ce Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at f3f80000 (32-bit, non-prefetchable) [size=512K] I/O ports at c880 [size=8] Memory at d0000000 (32-bit, non-prefetchable) [size=256M] Memory at f3f40000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: gma500 Kernel modules: psb_gfx '
– erikjber
May 1 '12 at 8:10






1




1




Please remember to post your solution as an answer when the system lets you, thanks!
– Jorge Castro
May 1 '12 at 13:07




Please remember to post your solution as an answer when the system lets you, thanks!
– Jorge Castro
May 1 '12 at 13:07










2 Answers
2






active

oldest

votes

















up vote
0
down vote













I found probably the best solution to fix graphic error: add "service lightdm restart" line to rc.local.



gksudo gedit /etc/rc.local


Add to new line after coments and before "exit 0":




service lightdm restart







share|improve this answer




























    up vote
    0
    down vote













    After implementing the first two options in this post, issue 2 is now resolved.



    Issue 1 was resolved after fixing a minor formatting error in the above link.



    The command should be



    ADD_PARAMETERS='--quirk-vbemode-restore'


    not ADD_PARAMETERS='–quirk-vbemode-restore'






    share|improve this answer























      Your Answer








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

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

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      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%2f129129%2fgraphics-problems-on-asus-eee-1101-ha-precise-pangolin%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      0
      down vote













      I found probably the best solution to fix graphic error: add "service lightdm restart" line to rc.local.



      gksudo gedit /etc/rc.local


      Add to new line after coments and before "exit 0":




      service lightdm restart







      share|improve this answer

























        up vote
        0
        down vote













        I found probably the best solution to fix graphic error: add "service lightdm restart" line to rc.local.



        gksudo gedit /etc/rc.local


        Add to new line after coments and before "exit 0":




        service lightdm restart







        share|improve this answer























          up vote
          0
          down vote










          up vote
          0
          down vote









          I found probably the best solution to fix graphic error: add "service lightdm restart" line to rc.local.



          gksudo gedit /etc/rc.local


          Add to new line after coments and before "exit 0":




          service lightdm restart







          share|improve this answer












          I found probably the best solution to fix graphic error: add "service lightdm restart" line to rc.local.



          gksudo gedit /etc/rc.local


          Add to new line after coments and before "exit 0":




          service lightdm restart








          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 7 '13 at 6:37









          AmarLite

          1




          1
























              up vote
              0
              down vote













              After implementing the first two options in this post, issue 2 is now resolved.



              Issue 1 was resolved after fixing a minor formatting error in the above link.



              The command should be



              ADD_PARAMETERS='--quirk-vbemode-restore'


              not ADD_PARAMETERS='–quirk-vbemode-restore'






              share|improve this answer



























                up vote
                0
                down vote













                After implementing the first two options in this post, issue 2 is now resolved.



                Issue 1 was resolved after fixing a minor formatting error in the above link.



                The command should be



                ADD_PARAMETERS='--quirk-vbemode-restore'


                not ADD_PARAMETERS='–quirk-vbemode-restore'






                share|improve this answer

























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  After implementing the first two options in this post, issue 2 is now resolved.



                  Issue 1 was resolved after fixing a minor formatting error in the above link.



                  The command should be



                  ADD_PARAMETERS='--quirk-vbemode-restore'


                  not ADD_PARAMETERS='–quirk-vbemode-restore'






                  share|improve this answer














                  After implementing the first two options in this post, issue 2 is now resolved.



                  Issue 1 was resolved after fixing a minor formatting error in the above link.



                  The command should be



                  ADD_PARAMETERS='--quirk-vbemode-restore'


                  not ADD_PARAMETERS='–quirk-vbemode-restore'







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  answered Sep 28 '16 at 2:42


























                  community wiki





                  chaskes































                      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%2f129129%2fgraphics-problems-on-asus-eee-1101-ha-precise-pangolin%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?

                      迪纳利

                      南乌拉尔铁路局