Force VESA driver in Ubuntu 16.10











up vote
2
down vote

favorite












My Ubuntu 16.10 uses i915 driver. For some reasons I have troubles with it. So I want to force X to use VESA.



I tried:




  1. blacklist i915 in /etc/modprobe.d/blacklist.conf. Then sudo update-initramfs -u. Doesn't work.


  2. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash modprobe.blacklist=i915" in /etc/default/grub. Then update-grub2. Doesn't work



  3. Added new file 20-foo.conf in /usr/etc/X11/xorg.conf.d with content:



    Section "Device"
    Identifier "Configured Video Device"
    Driver "vesa"
    EndSection



Doesn't work.



Guys, how on the Earth one could make an OS that requires such an effort just to switch video driver? Maybe I'm doing something wrong?










share|improve this question
























  • Try adding "sisfb" to the /etc/modules file, or even renaming/moving all xorg-related config files.
    – negusp
    Nov 15 '16 at 3:11












  • Didn't work. Also tried to add vesa. Moving xorg.conf.d caused X to not work at all.
    – user1748526
    Nov 15 '16 at 12:37















up vote
2
down vote

favorite












My Ubuntu 16.10 uses i915 driver. For some reasons I have troubles with it. So I want to force X to use VESA.



I tried:




  1. blacklist i915 in /etc/modprobe.d/blacklist.conf. Then sudo update-initramfs -u. Doesn't work.


  2. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash modprobe.blacklist=i915" in /etc/default/grub. Then update-grub2. Doesn't work



  3. Added new file 20-foo.conf in /usr/etc/X11/xorg.conf.d with content:



    Section "Device"
    Identifier "Configured Video Device"
    Driver "vesa"
    EndSection



Doesn't work.



Guys, how on the Earth one could make an OS that requires such an effort just to switch video driver? Maybe I'm doing something wrong?










share|improve this question
























  • Try adding "sisfb" to the /etc/modules file, or even renaming/moving all xorg-related config files.
    – negusp
    Nov 15 '16 at 3:11












  • Didn't work. Also tried to add vesa. Moving xorg.conf.d caused X to not work at all.
    – user1748526
    Nov 15 '16 at 12:37













up vote
2
down vote

favorite









up vote
2
down vote

favorite











My Ubuntu 16.10 uses i915 driver. For some reasons I have troubles with it. So I want to force X to use VESA.



I tried:




  1. blacklist i915 in /etc/modprobe.d/blacklist.conf. Then sudo update-initramfs -u. Doesn't work.


  2. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash modprobe.blacklist=i915" in /etc/default/grub. Then update-grub2. Doesn't work



  3. Added new file 20-foo.conf in /usr/etc/X11/xorg.conf.d with content:



    Section "Device"
    Identifier "Configured Video Device"
    Driver "vesa"
    EndSection



Doesn't work.



Guys, how on the Earth one could make an OS that requires such an effort just to switch video driver? Maybe I'm doing something wrong?










share|improve this question















My Ubuntu 16.10 uses i915 driver. For some reasons I have troubles with it. So I want to force X to use VESA.



I tried:




  1. blacklist i915 in /etc/modprobe.d/blacklist.conf. Then sudo update-initramfs -u. Doesn't work.


  2. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash modprobe.blacklist=i915" in /etc/default/grub. Then update-grub2. Doesn't work



  3. Added new file 20-foo.conf in /usr/etc/X11/xorg.conf.d with content:



    Section "Device"
    Identifier "Configured Video Device"
    Driver "vesa"
    EndSection



Doesn't work.



Guys, how on the Earth one could make an OS that requires such an effort just to switch video driver? Maybe I'm doing something wrong?







drivers graphics xorg video-driver i915






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 14 '16 at 21:23

























asked Nov 14 '16 at 20:28









user1748526

1113




1113












  • Try adding "sisfb" to the /etc/modules file, or even renaming/moving all xorg-related config files.
    – negusp
    Nov 15 '16 at 3:11












  • Didn't work. Also tried to add vesa. Moving xorg.conf.d caused X to not work at all.
    – user1748526
    Nov 15 '16 at 12:37


















  • Try adding "sisfb" to the /etc/modules file, or even renaming/moving all xorg-related config files.
    – negusp
    Nov 15 '16 at 3:11












  • Didn't work. Also tried to add vesa. Moving xorg.conf.d caused X to not work at all.
    – user1748526
    Nov 15 '16 at 12:37
















Try adding "sisfb" to the /etc/modules file, or even renaming/moving all xorg-related config files.
– negusp
Nov 15 '16 at 3:11






Try adding "sisfb" to the /etc/modules file, or even renaming/moving all xorg-related config files.
– negusp
Nov 15 '16 at 3:11














Didn't work. Also tried to add vesa. Moving xorg.conf.d caused X to not work at all.
– user1748526
Nov 15 '16 at 12:37




Didn't work. Also tried to add vesa. Moving xorg.conf.d caused X to not work at all.
– user1748526
Nov 15 '16 at 12:37










1 Answer
1






active

oldest

votes

















up vote
0
down vote













I had the same issue with a different card and Ubuntu 16.04.



I had luck appending a kernel parameter at boot: vga=791



The vga parameter sets the framebuffer to VESA mode 791 (1024x768 16bit).



To add kernel parameters: this answer or the wiki.



HTH






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%2f849481%2fforce-vesa-driver-in-ubuntu-16-10%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    I had the same issue with a different card and Ubuntu 16.04.



    I had luck appending a kernel parameter at boot: vga=791



    The vga parameter sets the framebuffer to VESA mode 791 (1024x768 16bit).



    To add kernel parameters: this answer or the wiki.



    HTH






    share|improve this answer



























      up vote
      0
      down vote













      I had the same issue with a different card and Ubuntu 16.04.



      I had luck appending a kernel parameter at boot: vga=791



      The vga parameter sets the framebuffer to VESA mode 791 (1024x768 16bit).



      To add kernel parameters: this answer or the wiki.



      HTH






      share|improve this answer

























        up vote
        0
        down vote










        up vote
        0
        down vote









        I had the same issue with a different card and Ubuntu 16.04.



        I had luck appending a kernel parameter at boot: vga=791



        The vga parameter sets the framebuffer to VESA mode 791 (1024x768 16bit).



        To add kernel parameters: this answer or the wiki.



        HTH






        share|improve this answer














        I had the same issue with a different card and Ubuntu 16.04.



        I had luck appending a kernel parameter at boot: vga=791



        The vga parameter sets the framebuffer to VESA mode 791 (1024x768 16bit).



        To add kernel parameters: this answer or the wiki.



        HTH







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Apr 13 '17 at 12:23









        Community

        1




        1










        answered Jan 13 '17 at 19:40









        Paolo

        63741538




        63741538






























            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%2f849481%2fforce-vesa-driver-in-ubuntu-16-10%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

            Ellipse (mathématiques)

            Quarter-circle Tiles

            Mont Emei