How do I increase console-mode resolution?





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







50















I've recently clean-reinstalled Maverick on my computer. It uses propietary Nvidia drivers.



Everything runs just fine, except that I'm seeing lots of ugly text when booting and shutting down Ubuntu.



I don't mind the text at all; in fact, I like seeing the startup/shutting down information.



What I don't like it's its ugliness!



When my computer goes to console mode - (booting up, shutting down or CTRL+ALT+F1) the text is super big - I can't take a screenshot of it, but it looks like a 640x480 resolution. My monitor normally works at 1440x900.



I remember that the console text that appeared while installing from the CD was nice and small.



How can I make the console text look like it looked while booting from the CD?










share|improve this question





























    50















    I've recently clean-reinstalled Maverick on my computer. It uses propietary Nvidia drivers.



    Everything runs just fine, except that I'm seeing lots of ugly text when booting and shutting down Ubuntu.



    I don't mind the text at all; in fact, I like seeing the startup/shutting down information.



    What I don't like it's its ugliness!



    When my computer goes to console mode - (booting up, shutting down or CTRL+ALT+F1) the text is super big - I can't take a screenshot of it, but it looks like a 640x480 resolution. My monitor normally works at 1440x900.



    I remember that the console text that appeared while installing from the CD was nice and small.



    How can I make the console text look like it looked while booting from the CD?










    share|improve this question

























      50












      50








      50


      31






      I've recently clean-reinstalled Maverick on my computer. It uses propietary Nvidia drivers.



      Everything runs just fine, except that I'm seeing lots of ugly text when booting and shutting down Ubuntu.



      I don't mind the text at all; in fact, I like seeing the startup/shutting down information.



      What I don't like it's its ugliness!



      When my computer goes to console mode - (booting up, shutting down or CTRL+ALT+F1) the text is super big - I can't take a screenshot of it, but it looks like a 640x480 resolution. My monitor normally works at 1440x900.



      I remember that the console text that appeared while installing from the CD was nice and small.



      How can I make the console text look like it looked while booting from the CD?










      share|improve this question














      I've recently clean-reinstalled Maverick on my computer. It uses propietary Nvidia drivers.



      Everything runs just fine, except that I'm seeing lots of ugly text when booting and shutting down Ubuntu.



      I don't mind the text at all; in fact, I like seeing the startup/shutting down information.



      What I don't like it's its ugliness!



      When my computer goes to console mode - (booting up, shutting down or CTRL+ALT+F1) the text is super big - I can't take a screenshot of it, but it looks like a 640x480 resolution. My monitor normally works at 1440x900.



      I remember that the console text that appeared while installing from the CD was nice and small.



      How can I make the console text look like it looked while booting from the CD?







      resolution console






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 21 '10 at 23:50









      egarciaegarcia

      7811712




      7811712






















          9 Answers
          9






          active

          oldest

          votes


















          32














          I've found a solution that works from this forum post



          In short:



          Open /etc/default/grub with your favorite editor as root.



          Localize the line that says GRUB_GFXMODE= ... and change it to the resolution you want. Add another line for a new variable called GRUB_GFXPAYLOAD with the same resolution. It should look similar to this:



          GRUB_GFXMODE=1440x900x32
          GRUB_GFXPAYLOAD=1440x900x32


          Save and exit. Then edit as root /etc/grub.d/00_header



          Localize the line that says if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=... . As before, change the resolution there to the one you want and add another line for payload:



          if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=1440x900x32 ; fi
          if [ "x${GRUB_GFXPAYLOAD}" = "x" ] ; then GRUB_GFXPAYLOAD=1440x900x32 ; fi


          Finally, locate the line that says set gfxmode=${GRUB_GFXMODE} and add a line for payload below it. It should look like this:



          set gfxmode=${GRUB_GFXMODE}
          set gfxpayload=${GRUB_GFXPAYLOAD}


          Save and exit.



          Still as root, refresh grub with



          update-grub2


          Reboot, and both the grub menu and the console should have nicer resolutions.



          Finished!






          share|improve this answer





















          • 1





            My solution will only work for grub2, I think. Are you using grub 1, maybe? If yes, try with a lower resolution first - for example 1024x768x32. Regards!

            – egarcia
            Jan 19 '11 at 9:59






          • 1





            unfortunately didn't work for me, running 10.10

            – segfault
            May 24 '11 at 22:12






          • 3





            Looks like that at the moment grub2 doesn't use 'GRUB_GFXPAYLOAD' option, only 'GRUB_GFXPAYLOAD_LINUX'. See the official documentation on grub2: gnu.org/software/grub/manual/grub.html#gfxpayload

            – mbaitoff
            Sep 15 '11 at 9:16






          • 2





            It would be more interesting to see a response that is more generic, that will work with most resolutions.

            – sorin
            Nov 17 '12 at 16:07






          • 2





            This answer is depreciated and did not work for me on Ubuntu Server 12.04 LTS. Furthermore, it involves editing a file named 00_header which really should not be edited.

            – Serge Stroobandt
            Jun 23 '14 at 12:34



















          22














          This helped me on Ubuntu 14.04 with ESXi 5.5 :



          :~$ sudo vi /etc/default/grub


          Change line to:



          GRUB_CMDLINE_LINUX_DEFAULT="splash vga=792"

          :~$ sudo update-grub :~$ sudo reboot -r now


          Use 795 or 799 for higher resolution, and see: http://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/ for more details.






          share|improve this answer





















          • 1





            This solutions worked for me. The splash option froze the login screen and it is unnecessary in my opinion. Btw I really don't like the cryptic options like 792!

            – Kyr
            Jul 10 '15 at 11:52








          • 1





            its deprecated in 15.04

            – Jiří Doubravský
            Aug 21 '15 at 21:57











          • works on fedora 21 too

            – Edward Torvalds
            Aug 31 '15 at 12:09











          • @JiříDoubravský then what to do? other answers dont work

            – Edward Torvalds
            Aug 31 '15 at 12:09






          • 1





            reboot command doesn't like the -r option, anyway.

            – Jin Kwon
            Dec 31 '16 at 16:01



















          14














          Set the graphics mode with GRUB_GFXPAYLOAD_LINUX



          First, install xrandr and run it:



          $ sudo apt-get install xrandr
          $ xrandr


          The available screen modes are listed.



          Now, edit /etc/default/grub:



          $ sudo nano /etc/default/grub


          Assuming a previously unedited file, make the following changes:



          The variable GRUB_CMDLINE_LINUX_DEFAULT should contain at least nomodeset, perhaps in addition to quiet and splash on desktop systems.



          GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"


          On server systems, uncomment GRUB_TERMINAL=console to see more messages passing during boot before entering in the graphics console.



          Leave this line as a comment:



          #GRUB_GFXMODE=640x480


          At the end of the file, add a line:



          GRUB_GFXPAYLOAD_LINUX=1280x1024x16


          or replace the value by any other (comma separated) mode(s) that is(are) supported by your hardware. The values text, keep, auto, vga and ask should also work.



          Finally, after saving the edited /etc/default/grub with Ctrl+O and exiting it with Ctrl+X, issue the following commands:



          $ sudo update-grub
          $ sudo reboot


          This answer will also work to decrease the resolution and/or refresh rate or frame buffer frequency on down-clocked systems. CRT monitors typically show flickering stripes when the refresh frequency is too high.






          share|improve this answer





















          • 1





            there is no hwinfo anymore

            – obayhan
            Feb 12 '16 at 10:05






          • 1





            @obayhan Well noted! You may use xrandr instead.

            – Serge Stroobandt
            Feb 13 '16 at 15:26






          • 1





            Works with 16.04.

            – Jin Kwon
            Dec 31 '16 at 16:22






          • 1





            THIS. This is the only thing that worked for me on 16.10.

            – Siguza
            Mar 7 '17 at 23:58



















          14















          1. Start in the GRUB menu

          2. Press C to go to the GRUB command line

          3. Run vbeinfo and make a decision (e.g. 1920x1200x32).

          4. Start your system again

          5. sudo nano /etc/default/grub

          6. Change GRUB_GFXMODE= (e.g. GRUB_GFXMODE=1920x1200x32)

          7. Set GRUB_GFXPAYLOAD_LINUX to GRUB_GFXPAYLOAD_LINUX=keep

          8. sudo update-grub

          9. reboot your system






          share|improve this answer


























          • among all the answers on this question, this is the one that worked for me with Ubuntu 16.04 server (and it's the simplest one)

            – Seb - SonarSource Team
            Aug 9 '16 at 7:57











          • Wrt step 2 above: I find one should press 'c' for a command-line (not 'E')

            – kaiwan
            Oct 12 '16 at 7:57











          • Doesn't work on VMware Workstation Player with Ubuntu 16.10

            – Sebi2020
            Nov 2 '16 at 23:33











          • @Sebi2020 Now which one? VMware Player or VMware Workstation? Works for me on VMware Workstation 14.0 with Ubuntu 16.04.

            – 0xC0000022L
            Dec 5 '17 at 14:31






          • 1





            @0xC0000022L VMWare Workstation 10

            – Sebi2020
            Dec 8 '17 at 11:22



















          4














          Just some personal background: in my other computer I have no problem with that fancy mode (it's 160 cols x 60 rows, but it has a 4:3 CRT monitor). It's equipped with a TNT2 (yes, I swear), and that mode was promptly displayed on first boot. Problem is, it does this by loading the nouveau driver, and this guy is still a bit faulty (in my case, it hangs the whole system when trying to move windows). So, to have an usable system, I had to downgrade to the old and stable nv driver, and also disabling mode-setting ('cause the kernel would always load nouveau when enabled). Note that I'm not using nVidia proprietary drivers, but like you, I was switched back to 80x25 in console mode.



          This is because the nv driver doesn't use kernel mode-setting. Now, I don't know about the proprietary drivers, but I'm guessing they might have changed your configuration in order to be usable, and possibly that's why you're seeing that "big" mode. Possibly they disabled mode-setting when installed. That's why you see the "small" text mode when booting from the Live CD.



          You could try booting up with a different VESA mode, but that depends a lot on your hardware. For that, please check http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers. For example, if you'd like to try booting your text mode on 1024x640, you'll find that the mode ID is 877.



          So, when booting, hold the SHIFT key (in case you don't have a GRUB timeout) to bring up GRUB's menu. Select the mode which you wish to boot and press 'e' (to edit the commands). At the end of the "kernel" command, add vga=877. The number is the mode ID, if you want to try other modes, replace it with the desired number.



          Also, at that same Wikipedia page, you could also try the helpful "Universal format" right below the modes table. That hwinfo command is quite useful.






          share|improve this answer



















          • 1





            I use grub2, not grub. I didn't know that grub was responsible for the console, so I didn't mention that in my question. Sorry. I've found a solution with grub2. Regards!

            – egarcia
            Dec 22 '10 at 4:55











          • To be true, the solution you found also seem simpler. Glad you sorted it out, and thanks for sharing!

            – Charles Roberto Canato
            Dec 22 '10 at 7:03



















          3














          Why i answer this threat even if it's very old? The answer is pretty easy, because so many other threat refer to it.



          If vbeinfo or hwinfo --framebuffer doesn't show the native resolution of your display, then disable vesa, to do so remove vga= options in:



          sudo nano /etc/default/grub


          Search for GRUB_CMDLINE_LINUX_DEFAULT= and remove vga= if you find it.



          If you have remove the option don't forget to generate a new grub.cfg:



          sudo update-grub


          If you don't know you did it well, then just reboot and open a terminal:



          grep vga /proc/cmdline
          grep -ir vga /etc/modprobe.d/


          If grep doesn't show anything, then you removed the vga= option.



          Now install uvesafb:



          sudo apt-get install v86d


          Make sure the uvesafb module is included into your initrd. Add it to the end of /etc/initramfs-tools/modules:



          sudo sh -c "echo uvesafb >> /etc/initramfs-tools/modules"


          To see what modes are available:



          sudo modprobe uvesafb
          cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes


          Now configure uvesafb mode_option=YOURxResoultion-BitColorMode e.g. 1280x1024-32:



          sudo sh -c "echo options uvesafb mode_option=1280x1024-32 scroll=ywrap > /etc/modprobe.d/uvesafb.conf"


          Don't forget to rebuild your initrd:



          sudo update-initramfs -k all -u


          Now you can reboot!



          See this for more details.
          It is for debian, but it also works for ubuntu.
          I hope it helped you and it should be more generic than using grub2.






          share|improve this answer


























          • +1 no need to change the grub config and uvesafb works for me on Ubuntu 16.04 with a proprietary nvidia driver (recommended in other places KMS is unsupported in this case)

            – jfs
            Sep 14 '16 at 13:31



















          1














          Ubuntu 18 console mode:



          Edit



          GRUB_CMDLINE_LINUX_DEFAULT="splash quite"


          in



          /etc/default/grub


          so new line looks like:



          GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=XXX nomodeset"


          where XXX comes from



          https://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/



          then reload grub config and reboot



          update-grub2
          reboot





          share|improve this answer
























          • It seems like this question has already a many similar answers. Perhaps you could clarify what motivated you to add your answer (i.e. what information was missing from previously posted answers).

            – cauon
            Mar 24 at 11:34











          • It's just simple. And suitable for newest Ubuntu 18

            – Paul Paku
            Mar 24 at 14:21





















          0














          This will not change the font on boot, but for the console on Ctrl+Alt+F[1-6]



          Install the custom Ubuntu fonts for your console:



          sudo apt-get install fonts-ubuntu-font-family-console


          And create a script /usr/local/bin/fontset with this command:



          #!/bin/sh
          setfont /usr/share/consolefonts/Uni3-TerminusBold32x16.psf.gz


          (choose the desired fon out of the folder /usr/share/consolefonts/)



          You can either call fontset each time on your console after using Ctrl+Alt+F1



          or add this line to your /root/.profile



          [ ! -t 0 ] && sleep 1 & /usr/local/bin/fontset


          (don't add this to your users .profile or you get an error on a graphical boot)



          source: Resize font on boot message screen and console






          share|improve this answer

































            0














            The following worked for me on Debian Stretch 4.9.51-1.

            No GUI, only console mode:



            Edit /etc/default/grub and add the following line



            GRUB_CMDLINE_LINUX_DEFAULT="splash vga=795 nomodeset"


            For a list of vga= codes see http://pierre.baudu.in/other/grub.vga.modes.html



            The nomodeset prevents the resolution from changing again after grub initializes [thanks How do I increase console-mode resolution? ]



            EDIT:
            As mentioned by @Videonauth :
            Afterwards do:

            sudo update-grub






            share|improve this answer


























            • To make changes in /etc/default/grub is not enough, you as well need to run afterwards sudo update-grub to make it happen

              – Videonauth
              Oct 26 '17 at 15:51












            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%2f18444%2fhow-do-i-increase-console-mode-resolution%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









            32














            I've found a solution that works from this forum post



            In short:



            Open /etc/default/grub with your favorite editor as root.



            Localize the line that says GRUB_GFXMODE= ... and change it to the resolution you want. Add another line for a new variable called GRUB_GFXPAYLOAD with the same resolution. It should look similar to this:



            GRUB_GFXMODE=1440x900x32
            GRUB_GFXPAYLOAD=1440x900x32


            Save and exit. Then edit as root /etc/grub.d/00_header



            Localize the line that says if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=... . As before, change the resolution there to the one you want and add another line for payload:



            if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=1440x900x32 ; fi
            if [ "x${GRUB_GFXPAYLOAD}" = "x" ] ; then GRUB_GFXPAYLOAD=1440x900x32 ; fi


            Finally, locate the line that says set gfxmode=${GRUB_GFXMODE} and add a line for payload below it. It should look like this:



            set gfxmode=${GRUB_GFXMODE}
            set gfxpayload=${GRUB_GFXPAYLOAD}


            Save and exit.



            Still as root, refresh grub with



            update-grub2


            Reboot, and both the grub menu and the console should have nicer resolutions.



            Finished!






            share|improve this answer





















            • 1





              My solution will only work for grub2, I think. Are you using grub 1, maybe? If yes, try with a lower resolution first - for example 1024x768x32. Regards!

              – egarcia
              Jan 19 '11 at 9:59






            • 1





              unfortunately didn't work for me, running 10.10

              – segfault
              May 24 '11 at 22:12






            • 3





              Looks like that at the moment grub2 doesn't use 'GRUB_GFXPAYLOAD' option, only 'GRUB_GFXPAYLOAD_LINUX'. See the official documentation on grub2: gnu.org/software/grub/manual/grub.html#gfxpayload

              – mbaitoff
              Sep 15 '11 at 9:16






            • 2





              It would be more interesting to see a response that is more generic, that will work with most resolutions.

              – sorin
              Nov 17 '12 at 16:07






            • 2





              This answer is depreciated and did not work for me on Ubuntu Server 12.04 LTS. Furthermore, it involves editing a file named 00_header which really should not be edited.

              – Serge Stroobandt
              Jun 23 '14 at 12:34
















            32














            I've found a solution that works from this forum post



            In short:



            Open /etc/default/grub with your favorite editor as root.



            Localize the line that says GRUB_GFXMODE= ... and change it to the resolution you want. Add another line for a new variable called GRUB_GFXPAYLOAD with the same resolution. It should look similar to this:



            GRUB_GFXMODE=1440x900x32
            GRUB_GFXPAYLOAD=1440x900x32


            Save and exit. Then edit as root /etc/grub.d/00_header



            Localize the line that says if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=... . As before, change the resolution there to the one you want and add another line for payload:



            if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=1440x900x32 ; fi
            if [ "x${GRUB_GFXPAYLOAD}" = "x" ] ; then GRUB_GFXPAYLOAD=1440x900x32 ; fi


            Finally, locate the line that says set gfxmode=${GRUB_GFXMODE} and add a line for payload below it. It should look like this:



            set gfxmode=${GRUB_GFXMODE}
            set gfxpayload=${GRUB_GFXPAYLOAD}


            Save and exit.



            Still as root, refresh grub with



            update-grub2


            Reboot, and both the grub menu and the console should have nicer resolutions.



            Finished!






            share|improve this answer





















            • 1





              My solution will only work for grub2, I think. Are you using grub 1, maybe? If yes, try with a lower resolution first - for example 1024x768x32. Regards!

              – egarcia
              Jan 19 '11 at 9:59






            • 1





              unfortunately didn't work for me, running 10.10

              – segfault
              May 24 '11 at 22:12






            • 3





              Looks like that at the moment grub2 doesn't use 'GRUB_GFXPAYLOAD' option, only 'GRUB_GFXPAYLOAD_LINUX'. See the official documentation on grub2: gnu.org/software/grub/manual/grub.html#gfxpayload

              – mbaitoff
              Sep 15 '11 at 9:16






            • 2





              It would be more interesting to see a response that is more generic, that will work with most resolutions.

              – sorin
              Nov 17 '12 at 16:07






            • 2





              This answer is depreciated and did not work for me on Ubuntu Server 12.04 LTS. Furthermore, it involves editing a file named 00_header which really should not be edited.

              – Serge Stroobandt
              Jun 23 '14 at 12:34














            32












            32








            32







            I've found a solution that works from this forum post



            In short:



            Open /etc/default/grub with your favorite editor as root.



            Localize the line that says GRUB_GFXMODE= ... and change it to the resolution you want. Add another line for a new variable called GRUB_GFXPAYLOAD with the same resolution. It should look similar to this:



            GRUB_GFXMODE=1440x900x32
            GRUB_GFXPAYLOAD=1440x900x32


            Save and exit. Then edit as root /etc/grub.d/00_header



            Localize the line that says if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=... . As before, change the resolution there to the one you want and add another line for payload:



            if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=1440x900x32 ; fi
            if [ "x${GRUB_GFXPAYLOAD}" = "x" ] ; then GRUB_GFXPAYLOAD=1440x900x32 ; fi


            Finally, locate the line that says set gfxmode=${GRUB_GFXMODE} and add a line for payload below it. It should look like this:



            set gfxmode=${GRUB_GFXMODE}
            set gfxpayload=${GRUB_GFXPAYLOAD}


            Save and exit.



            Still as root, refresh grub with



            update-grub2


            Reboot, and both the grub menu and the console should have nicer resolutions.



            Finished!






            share|improve this answer















            I've found a solution that works from this forum post



            In short:



            Open /etc/default/grub with your favorite editor as root.



            Localize the line that says GRUB_GFXMODE= ... and change it to the resolution you want. Add another line for a new variable called GRUB_GFXPAYLOAD with the same resolution. It should look similar to this:



            GRUB_GFXMODE=1440x900x32
            GRUB_GFXPAYLOAD=1440x900x32


            Save and exit. Then edit as root /etc/grub.d/00_header



            Localize the line that says if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=... . As before, change the resolution there to the one you want and add another line for payload:



            if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=1440x900x32 ; fi
            if [ "x${GRUB_GFXPAYLOAD}" = "x" ] ; then GRUB_GFXPAYLOAD=1440x900x32 ; fi


            Finally, locate the line that says set gfxmode=${GRUB_GFXMODE} and add a line for payload below it. It should look like this:



            set gfxmode=${GRUB_GFXMODE}
            set gfxpayload=${GRUB_GFXPAYLOAD}


            Save and exit.



            Still as root, refresh grub with



            update-grub2


            Reboot, and both the grub menu and the console should have nicer resolutions.



            Finished!







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Apr 15 '15 at 7:53









            A.B.

            69.8k12172266




            69.8k12172266










            answered Dec 22 '10 at 4:54









            egarciaegarcia

            7811712




            7811712








            • 1





              My solution will only work for grub2, I think. Are you using grub 1, maybe? If yes, try with a lower resolution first - for example 1024x768x32. Regards!

              – egarcia
              Jan 19 '11 at 9:59






            • 1





              unfortunately didn't work for me, running 10.10

              – segfault
              May 24 '11 at 22:12






            • 3





              Looks like that at the moment grub2 doesn't use 'GRUB_GFXPAYLOAD' option, only 'GRUB_GFXPAYLOAD_LINUX'. See the official documentation on grub2: gnu.org/software/grub/manual/grub.html#gfxpayload

              – mbaitoff
              Sep 15 '11 at 9:16






            • 2





              It would be more interesting to see a response that is more generic, that will work with most resolutions.

              – sorin
              Nov 17 '12 at 16:07






            • 2





              This answer is depreciated and did not work for me on Ubuntu Server 12.04 LTS. Furthermore, it involves editing a file named 00_header which really should not be edited.

              – Serge Stroobandt
              Jun 23 '14 at 12:34














            • 1





              My solution will only work for grub2, I think. Are you using grub 1, maybe? If yes, try with a lower resolution first - for example 1024x768x32. Regards!

              – egarcia
              Jan 19 '11 at 9:59






            • 1





              unfortunately didn't work for me, running 10.10

              – segfault
              May 24 '11 at 22:12






            • 3





              Looks like that at the moment grub2 doesn't use 'GRUB_GFXPAYLOAD' option, only 'GRUB_GFXPAYLOAD_LINUX'. See the official documentation on grub2: gnu.org/software/grub/manual/grub.html#gfxpayload

              – mbaitoff
              Sep 15 '11 at 9:16






            • 2





              It would be more interesting to see a response that is more generic, that will work with most resolutions.

              – sorin
              Nov 17 '12 at 16:07






            • 2





              This answer is depreciated and did not work for me on Ubuntu Server 12.04 LTS. Furthermore, it involves editing a file named 00_header which really should not be edited.

              – Serge Stroobandt
              Jun 23 '14 at 12:34








            1




            1





            My solution will only work for grub2, I think. Are you using grub 1, maybe? If yes, try with a lower resolution first - for example 1024x768x32. Regards!

            – egarcia
            Jan 19 '11 at 9:59





            My solution will only work for grub2, I think. Are you using grub 1, maybe? If yes, try with a lower resolution first - for example 1024x768x32. Regards!

            – egarcia
            Jan 19 '11 at 9:59




            1




            1





            unfortunately didn't work for me, running 10.10

            – segfault
            May 24 '11 at 22:12





            unfortunately didn't work for me, running 10.10

            – segfault
            May 24 '11 at 22:12




            3




            3





            Looks like that at the moment grub2 doesn't use 'GRUB_GFXPAYLOAD' option, only 'GRUB_GFXPAYLOAD_LINUX'. See the official documentation on grub2: gnu.org/software/grub/manual/grub.html#gfxpayload

            – mbaitoff
            Sep 15 '11 at 9:16





            Looks like that at the moment grub2 doesn't use 'GRUB_GFXPAYLOAD' option, only 'GRUB_GFXPAYLOAD_LINUX'. See the official documentation on grub2: gnu.org/software/grub/manual/grub.html#gfxpayload

            – mbaitoff
            Sep 15 '11 at 9:16




            2




            2





            It would be more interesting to see a response that is more generic, that will work with most resolutions.

            – sorin
            Nov 17 '12 at 16:07





            It would be more interesting to see a response that is more generic, that will work with most resolutions.

            – sorin
            Nov 17 '12 at 16:07




            2




            2





            This answer is depreciated and did not work for me on Ubuntu Server 12.04 LTS. Furthermore, it involves editing a file named 00_header which really should not be edited.

            – Serge Stroobandt
            Jun 23 '14 at 12:34





            This answer is depreciated and did not work for me on Ubuntu Server 12.04 LTS. Furthermore, it involves editing a file named 00_header which really should not be edited.

            – Serge Stroobandt
            Jun 23 '14 at 12:34













            22














            This helped me on Ubuntu 14.04 with ESXi 5.5 :



            :~$ sudo vi /etc/default/grub


            Change line to:



            GRUB_CMDLINE_LINUX_DEFAULT="splash vga=792"

            :~$ sudo update-grub :~$ sudo reboot -r now


            Use 795 or 799 for higher resolution, and see: http://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/ for more details.






            share|improve this answer





















            • 1





              This solutions worked for me. The splash option froze the login screen and it is unnecessary in my opinion. Btw I really don't like the cryptic options like 792!

              – Kyr
              Jul 10 '15 at 11:52








            • 1





              its deprecated in 15.04

              – Jiří Doubravský
              Aug 21 '15 at 21:57











            • works on fedora 21 too

              – Edward Torvalds
              Aug 31 '15 at 12:09











            • @JiříDoubravský then what to do? other answers dont work

              – Edward Torvalds
              Aug 31 '15 at 12:09






            • 1





              reboot command doesn't like the -r option, anyway.

              – Jin Kwon
              Dec 31 '16 at 16:01
















            22














            This helped me on Ubuntu 14.04 with ESXi 5.5 :



            :~$ sudo vi /etc/default/grub


            Change line to:



            GRUB_CMDLINE_LINUX_DEFAULT="splash vga=792"

            :~$ sudo update-grub :~$ sudo reboot -r now


            Use 795 or 799 for higher resolution, and see: http://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/ for more details.






            share|improve this answer





















            • 1





              This solutions worked for me. The splash option froze the login screen and it is unnecessary in my opinion. Btw I really don't like the cryptic options like 792!

              – Kyr
              Jul 10 '15 at 11:52








            • 1





              its deprecated in 15.04

              – Jiří Doubravský
              Aug 21 '15 at 21:57











            • works on fedora 21 too

              – Edward Torvalds
              Aug 31 '15 at 12:09











            • @JiříDoubravský then what to do? other answers dont work

              – Edward Torvalds
              Aug 31 '15 at 12:09






            • 1





              reboot command doesn't like the -r option, anyway.

              – Jin Kwon
              Dec 31 '16 at 16:01














            22












            22








            22







            This helped me on Ubuntu 14.04 with ESXi 5.5 :



            :~$ sudo vi /etc/default/grub


            Change line to:



            GRUB_CMDLINE_LINUX_DEFAULT="splash vga=792"

            :~$ sudo update-grub :~$ sudo reboot -r now


            Use 795 or 799 for higher resolution, and see: http://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/ for more details.






            share|improve this answer















            This helped me on Ubuntu 14.04 with ESXi 5.5 :



            :~$ sudo vi /etc/default/grub


            Change line to:



            GRUB_CMDLINE_LINUX_DEFAULT="splash vga=792"

            :~$ sudo update-grub :~$ sudo reboot -r now


            Use 795 or 799 for higher resolution, and see: http://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/ for more details.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited May 22 '14 at 22:37









            belacqua

            16k1474103




            16k1474103










            answered May 22 '14 at 21:24









            vrangervranger

            32123




            32123








            • 1





              This solutions worked for me. The splash option froze the login screen and it is unnecessary in my opinion. Btw I really don't like the cryptic options like 792!

              – Kyr
              Jul 10 '15 at 11:52








            • 1





              its deprecated in 15.04

              – Jiří Doubravský
              Aug 21 '15 at 21:57











            • works on fedora 21 too

              – Edward Torvalds
              Aug 31 '15 at 12:09











            • @JiříDoubravský then what to do? other answers dont work

              – Edward Torvalds
              Aug 31 '15 at 12:09






            • 1





              reboot command doesn't like the -r option, anyway.

              – Jin Kwon
              Dec 31 '16 at 16:01














            • 1





              This solutions worked for me. The splash option froze the login screen and it is unnecessary in my opinion. Btw I really don't like the cryptic options like 792!

              – Kyr
              Jul 10 '15 at 11:52








            • 1





              its deprecated in 15.04

              – Jiří Doubravský
              Aug 21 '15 at 21:57











            • works on fedora 21 too

              – Edward Torvalds
              Aug 31 '15 at 12:09











            • @JiříDoubravský then what to do? other answers dont work

              – Edward Torvalds
              Aug 31 '15 at 12:09






            • 1





              reboot command doesn't like the -r option, anyway.

              – Jin Kwon
              Dec 31 '16 at 16:01








            1




            1





            This solutions worked for me. The splash option froze the login screen and it is unnecessary in my opinion. Btw I really don't like the cryptic options like 792!

            – Kyr
            Jul 10 '15 at 11:52







            This solutions worked for me. The splash option froze the login screen and it is unnecessary in my opinion. Btw I really don't like the cryptic options like 792!

            – Kyr
            Jul 10 '15 at 11:52






            1




            1





            its deprecated in 15.04

            – Jiří Doubravský
            Aug 21 '15 at 21:57





            its deprecated in 15.04

            – Jiří Doubravský
            Aug 21 '15 at 21:57













            works on fedora 21 too

            – Edward Torvalds
            Aug 31 '15 at 12:09





            works on fedora 21 too

            – Edward Torvalds
            Aug 31 '15 at 12:09













            @JiříDoubravský then what to do? other answers dont work

            – Edward Torvalds
            Aug 31 '15 at 12:09





            @JiříDoubravský then what to do? other answers dont work

            – Edward Torvalds
            Aug 31 '15 at 12:09




            1




            1





            reboot command doesn't like the -r option, anyway.

            – Jin Kwon
            Dec 31 '16 at 16:01





            reboot command doesn't like the -r option, anyway.

            – Jin Kwon
            Dec 31 '16 at 16:01











            14














            Set the graphics mode with GRUB_GFXPAYLOAD_LINUX



            First, install xrandr and run it:



            $ sudo apt-get install xrandr
            $ xrandr


            The available screen modes are listed.



            Now, edit /etc/default/grub:



            $ sudo nano /etc/default/grub


            Assuming a previously unedited file, make the following changes:



            The variable GRUB_CMDLINE_LINUX_DEFAULT should contain at least nomodeset, perhaps in addition to quiet and splash on desktop systems.



            GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"


            On server systems, uncomment GRUB_TERMINAL=console to see more messages passing during boot before entering in the graphics console.



            Leave this line as a comment:



            #GRUB_GFXMODE=640x480


            At the end of the file, add a line:



            GRUB_GFXPAYLOAD_LINUX=1280x1024x16


            or replace the value by any other (comma separated) mode(s) that is(are) supported by your hardware. The values text, keep, auto, vga and ask should also work.



            Finally, after saving the edited /etc/default/grub with Ctrl+O and exiting it with Ctrl+X, issue the following commands:



            $ sudo update-grub
            $ sudo reboot


            This answer will also work to decrease the resolution and/or refresh rate or frame buffer frequency on down-clocked systems. CRT monitors typically show flickering stripes when the refresh frequency is too high.






            share|improve this answer





















            • 1





              there is no hwinfo anymore

              – obayhan
              Feb 12 '16 at 10:05






            • 1





              @obayhan Well noted! You may use xrandr instead.

              – Serge Stroobandt
              Feb 13 '16 at 15:26






            • 1





              Works with 16.04.

              – Jin Kwon
              Dec 31 '16 at 16:22






            • 1





              THIS. This is the only thing that worked for me on 16.10.

              – Siguza
              Mar 7 '17 at 23:58
















            14














            Set the graphics mode with GRUB_GFXPAYLOAD_LINUX



            First, install xrandr and run it:



            $ sudo apt-get install xrandr
            $ xrandr


            The available screen modes are listed.



            Now, edit /etc/default/grub:



            $ sudo nano /etc/default/grub


            Assuming a previously unedited file, make the following changes:



            The variable GRUB_CMDLINE_LINUX_DEFAULT should contain at least nomodeset, perhaps in addition to quiet and splash on desktop systems.



            GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"


            On server systems, uncomment GRUB_TERMINAL=console to see more messages passing during boot before entering in the graphics console.



            Leave this line as a comment:



            #GRUB_GFXMODE=640x480


            At the end of the file, add a line:



            GRUB_GFXPAYLOAD_LINUX=1280x1024x16


            or replace the value by any other (comma separated) mode(s) that is(are) supported by your hardware. The values text, keep, auto, vga and ask should also work.



            Finally, after saving the edited /etc/default/grub with Ctrl+O and exiting it with Ctrl+X, issue the following commands:



            $ sudo update-grub
            $ sudo reboot


            This answer will also work to decrease the resolution and/or refresh rate or frame buffer frequency on down-clocked systems. CRT monitors typically show flickering stripes when the refresh frequency is too high.






            share|improve this answer





















            • 1





              there is no hwinfo anymore

              – obayhan
              Feb 12 '16 at 10:05






            • 1





              @obayhan Well noted! You may use xrandr instead.

              – Serge Stroobandt
              Feb 13 '16 at 15:26






            • 1





              Works with 16.04.

              – Jin Kwon
              Dec 31 '16 at 16:22






            • 1





              THIS. This is the only thing that worked for me on 16.10.

              – Siguza
              Mar 7 '17 at 23:58














            14












            14








            14







            Set the graphics mode with GRUB_GFXPAYLOAD_LINUX



            First, install xrandr and run it:



            $ sudo apt-get install xrandr
            $ xrandr


            The available screen modes are listed.



            Now, edit /etc/default/grub:



            $ sudo nano /etc/default/grub


            Assuming a previously unedited file, make the following changes:



            The variable GRUB_CMDLINE_LINUX_DEFAULT should contain at least nomodeset, perhaps in addition to quiet and splash on desktop systems.



            GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"


            On server systems, uncomment GRUB_TERMINAL=console to see more messages passing during boot before entering in the graphics console.



            Leave this line as a comment:



            #GRUB_GFXMODE=640x480


            At the end of the file, add a line:



            GRUB_GFXPAYLOAD_LINUX=1280x1024x16


            or replace the value by any other (comma separated) mode(s) that is(are) supported by your hardware. The values text, keep, auto, vga and ask should also work.



            Finally, after saving the edited /etc/default/grub with Ctrl+O and exiting it with Ctrl+X, issue the following commands:



            $ sudo update-grub
            $ sudo reboot


            This answer will also work to decrease the resolution and/or refresh rate or frame buffer frequency on down-clocked systems. CRT monitors typically show flickering stripes when the refresh frequency is too high.






            share|improve this answer















            Set the graphics mode with GRUB_GFXPAYLOAD_LINUX



            First, install xrandr and run it:



            $ sudo apt-get install xrandr
            $ xrandr


            The available screen modes are listed.



            Now, edit /etc/default/grub:



            $ sudo nano /etc/default/grub


            Assuming a previously unedited file, make the following changes:



            The variable GRUB_CMDLINE_LINUX_DEFAULT should contain at least nomodeset, perhaps in addition to quiet and splash on desktop systems.



            GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"


            On server systems, uncomment GRUB_TERMINAL=console to see more messages passing during boot before entering in the graphics console.



            Leave this line as a comment:



            #GRUB_GFXMODE=640x480


            At the end of the file, add a line:



            GRUB_GFXPAYLOAD_LINUX=1280x1024x16


            or replace the value by any other (comma separated) mode(s) that is(are) supported by your hardware. The values text, keep, auto, vga and ask should also work.



            Finally, after saving the edited /etc/default/grub with Ctrl+O and exiting it with Ctrl+X, issue the following commands:



            $ sudo update-grub
            $ sudo reboot


            This answer will also work to decrease the resolution and/or refresh rate or frame buffer frequency on down-clocked systems. CRT monitors typically show flickering stripes when the refresh frequency is too high.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 12 '17 at 14:45

























            answered Jun 23 '14 at 12:31









            Serge StroobandtSerge Stroobandt

            2,2312034




            2,2312034








            • 1





              there is no hwinfo anymore

              – obayhan
              Feb 12 '16 at 10:05






            • 1





              @obayhan Well noted! You may use xrandr instead.

              – Serge Stroobandt
              Feb 13 '16 at 15:26






            • 1





              Works with 16.04.

              – Jin Kwon
              Dec 31 '16 at 16:22






            • 1





              THIS. This is the only thing that worked for me on 16.10.

              – Siguza
              Mar 7 '17 at 23:58














            • 1





              there is no hwinfo anymore

              – obayhan
              Feb 12 '16 at 10:05






            • 1





              @obayhan Well noted! You may use xrandr instead.

              – Serge Stroobandt
              Feb 13 '16 at 15:26






            • 1





              Works with 16.04.

              – Jin Kwon
              Dec 31 '16 at 16:22






            • 1





              THIS. This is the only thing that worked for me on 16.10.

              – Siguza
              Mar 7 '17 at 23:58








            1




            1





            there is no hwinfo anymore

            – obayhan
            Feb 12 '16 at 10:05





            there is no hwinfo anymore

            – obayhan
            Feb 12 '16 at 10:05




            1




            1





            @obayhan Well noted! You may use xrandr instead.

            – Serge Stroobandt
            Feb 13 '16 at 15:26





            @obayhan Well noted! You may use xrandr instead.

            – Serge Stroobandt
            Feb 13 '16 at 15:26




            1




            1





            Works with 16.04.

            – Jin Kwon
            Dec 31 '16 at 16:22





            Works with 16.04.

            – Jin Kwon
            Dec 31 '16 at 16:22




            1




            1





            THIS. This is the only thing that worked for me on 16.10.

            – Siguza
            Mar 7 '17 at 23:58





            THIS. This is the only thing that worked for me on 16.10.

            – Siguza
            Mar 7 '17 at 23:58











            14















            1. Start in the GRUB menu

            2. Press C to go to the GRUB command line

            3. Run vbeinfo and make a decision (e.g. 1920x1200x32).

            4. Start your system again

            5. sudo nano /etc/default/grub

            6. Change GRUB_GFXMODE= (e.g. GRUB_GFXMODE=1920x1200x32)

            7. Set GRUB_GFXPAYLOAD_LINUX to GRUB_GFXPAYLOAD_LINUX=keep

            8. sudo update-grub

            9. reboot your system






            share|improve this answer


























            • among all the answers on this question, this is the one that worked for me with Ubuntu 16.04 server (and it's the simplest one)

              – Seb - SonarSource Team
              Aug 9 '16 at 7:57











            • Wrt step 2 above: I find one should press 'c' for a command-line (not 'E')

              – kaiwan
              Oct 12 '16 at 7:57











            • Doesn't work on VMware Workstation Player with Ubuntu 16.10

              – Sebi2020
              Nov 2 '16 at 23:33











            • @Sebi2020 Now which one? VMware Player or VMware Workstation? Works for me on VMware Workstation 14.0 with Ubuntu 16.04.

              – 0xC0000022L
              Dec 5 '17 at 14:31






            • 1





              @0xC0000022L VMWare Workstation 10

              – Sebi2020
              Dec 8 '17 at 11:22
















            14















            1. Start in the GRUB menu

            2. Press C to go to the GRUB command line

            3. Run vbeinfo and make a decision (e.g. 1920x1200x32).

            4. Start your system again

            5. sudo nano /etc/default/grub

            6. Change GRUB_GFXMODE= (e.g. GRUB_GFXMODE=1920x1200x32)

            7. Set GRUB_GFXPAYLOAD_LINUX to GRUB_GFXPAYLOAD_LINUX=keep

            8. sudo update-grub

            9. reboot your system






            share|improve this answer


























            • among all the answers on this question, this is the one that worked for me with Ubuntu 16.04 server (and it's the simplest one)

              – Seb - SonarSource Team
              Aug 9 '16 at 7:57











            • Wrt step 2 above: I find one should press 'c' for a command-line (not 'E')

              – kaiwan
              Oct 12 '16 at 7:57











            • Doesn't work on VMware Workstation Player with Ubuntu 16.10

              – Sebi2020
              Nov 2 '16 at 23:33











            • @Sebi2020 Now which one? VMware Player or VMware Workstation? Works for me on VMware Workstation 14.0 with Ubuntu 16.04.

              – 0xC0000022L
              Dec 5 '17 at 14:31






            • 1





              @0xC0000022L VMWare Workstation 10

              – Sebi2020
              Dec 8 '17 at 11:22














            14












            14








            14








            1. Start in the GRUB menu

            2. Press C to go to the GRUB command line

            3. Run vbeinfo and make a decision (e.g. 1920x1200x32).

            4. Start your system again

            5. sudo nano /etc/default/grub

            6. Change GRUB_GFXMODE= (e.g. GRUB_GFXMODE=1920x1200x32)

            7. Set GRUB_GFXPAYLOAD_LINUX to GRUB_GFXPAYLOAD_LINUX=keep

            8. sudo update-grub

            9. reboot your system






            share|improve this answer
















            1. Start in the GRUB menu

            2. Press C to go to the GRUB command line

            3. Run vbeinfo and make a decision (e.g. 1920x1200x32).

            4. Start your system again

            5. sudo nano /etc/default/grub

            6. Change GRUB_GFXMODE= (e.g. GRUB_GFXMODE=1920x1200x32)

            7. Set GRUB_GFXPAYLOAD_LINUX to GRUB_GFXPAYLOAD_LINUX=keep

            8. sudo update-grub

            9. reboot your system







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 29 '17 at 13:59









            Foad

            31126




            31126










            answered Apr 15 '15 at 9:33









            A.B.A.B.

            69.8k12172266




            69.8k12172266













            • among all the answers on this question, this is the one that worked for me with Ubuntu 16.04 server (and it's the simplest one)

              – Seb - SonarSource Team
              Aug 9 '16 at 7:57











            • Wrt step 2 above: I find one should press 'c' for a command-line (not 'E')

              – kaiwan
              Oct 12 '16 at 7:57











            • Doesn't work on VMware Workstation Player with Ubuntu 16.10

              – Sebi2020
              Nov 2 '16 at 23:33











            • @Sebi2020 Now which one? VMware Player or VMware Workstation? Works for me on VMware Workstation 14.0 with Ubuntu 16.04.

              – 0xC0000022L
              Dec 5 '17 at 14:31






            • 1





              @0xC0000022L VMWare Workstation 10

              – Sebi2020
              Dec 8 '17 at 11:22



















            • among all the answers on this question, this is the one that worked for me with Ubuntu 16.04 server (and it's the simplest one)

              – Seb - SonarSource Team
              Aug 9 '16 at 7:57











            • Wrt step 2 above: I find one should press 'c' for a command-line (not 'E')

              – kaiwan
              Oct 12 '16 at 7:57











            • Doesn't work on VMware Workstation Player with Ubuntu 16.10

              – Sebi2020
              Nov 2 '16 at 23:33











            • @Sebi2020 Now which one? VMware Player or VMware Workstation? Works for me on VMware Workstation 14.0 with Ubuntu 16.04.

              – 0xC0000022L
              Dec 5 '17 at 14:31






            • 1





              @0xC0000022L VMWare Workstation 10

              – Sebi2020
              Dec 8 '17 at 11:22

















            among all the answers on this question, this is the one that worked for me with Ubuntu 16.04 server (and it's the simplest one)

            – Seb - SonarSource Team
            Aug 9 '16 at 7:57





            among all the answers on this question, this is the one that worked for me with Ubuntu 16.04 server (and it's the simplest one)

            – Seb - SonarSource Team
            Aug 9 '16 at 7:57













            Wrt step 2 above: I find one should press 'c' for a command-line (not 'E')

            – kaiwan
            Oct 12 '16 at 7:57





            Wrt step 2 above: I find one should press 'c' for a command-line (not 'E')

            – kaiwan
            Oct 12 '16 at 7:57













            Doesn't work on VMware Workstation Player with Ubuntu 16.10

            – Sebi2020
            Nov 2 '16 at 23:33





            Doesn't work on VMware Workstation Player with Ubuntu 16.10

            – Sebi2020
            Nov 2 '16 at 23:33













            @Sebi2020 Now which one? VMware Player or VMware Workstation? Works for me on VMware Workstation 14.0 with Ubuntu 16.04.

            – 0xC0000022L
            Dec 5 '17 at 14:31





            @Sebi2020 Now which one? VMware Player or VMware Workstation? Works for me on VMware Workstation 14.0 with Ubuntu 16.04.

            – 0xC0000022L
            Dec 5 '17 at 14:31




            1




            1





            @0xC0000022L VMWare Workstation 10

            – Sebi2020
            Dec 8 '17 at 11:22





            @0xC0000022L VMWare Workstation 10

            – Sebi2020
            Dec 8 '17 at 11:22











            4














            Just some personal background: in my other computer I have no problem with that fancy mode (it's 160 cols x 60 rows, but it has a 4:3 CRT monitor). It's equipped with a TNT2 (yes, I swear), and that mode was promptly displayed on first boot. Problem is, it does this by loading the nouveau driver, and this guy is still a bit faulty (in my case, it hangs the whole system when trying to move windows). So, to have an usable system, I had to downgrade to the old and stable nv driver, and also disabling mode-setting ('cause the kernel would always load nouveau when enabled). Note that I'm not using nVidia proprietary drivers, but like you, I was switched back to 80x25 in console mode.



            This is because the nv driver doesn't use kernel mode-setting. Now, I don't know about the proprietary drivers, but I'm guessing they might have changed your configuration in order to be usable, and possibly that's why you're seeing that "big" mode. Possibly they disabled mode-setting when installed. That's why you see the "small" text mode when booting from the Live CD.



            You could try booting up with a different VESA mode, but that depends a lot on your hardware. For that, please check http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers. For example, if you'd like to try booting your text mode on 1024x640, you'll find that the mode ID is 877.



            So, when booting, hold the SHIFT key (in case you don't have a GRUB timeout) to bring up GRUB's menu. Select the mode which you wish to boot and press 'e' (to edit the commands). At the end of the "kernel" command, add vga=877. The number is the mode ID, if you want to try other modes, replace it with the desired number.



            Also, at that same Wikipedia page, you could also try the helpful "Universal format" right below the modes table. That hwinfo command is quite useful.






            share|improve this answer



















            • 1





              I use grub2, not grub. I didn't know that grub was responsible for the console, so I didn't mention that in my question. Sorry. I've found a solution with grub2. Regards!

              – egarcia
              Dec 22 '10 at 4:55











            • To be true, the solution you found also seem simpler. Glad you sorted it out, and thanks for sharing!

              – Charles Roberto Canato
              Dec 22 '10 at 7:03
















            4














            Just some personal background: in my other computer I have no problem with that fancy mode (it's 160 cols x 60 rows, but it has a 4:3 CRT monitor). It's equipped with a TNT2 (yes, I swear), and that mode was promptly displayed on first boot. Problem is, it does this by loading the nouveau driver, and this guy is still a bit faulty (in my case, it hangs the whole system when trying to move windows). So, to have an usable system, I had to downgrade to the old and stable nv driver, and also disabling mode-setting ('cause the kernel would always load nouveau when enabled). Note that I'm not using nVidia proprietary drivers, but like you, I was switched back to 80x25 in console mode.



            This is because the nv driver doesn't use kernel mode-setting. Now, I don't know about the proprietary drivers, but I'm guessing they might have changed your configuration in order to be usable, and possibly that's why you're seeing that "big" mode. Possibly they disabled mode-setting when installed. That's why you see the "small" text mode when booting from the Live CD.



            You could try booting up with a different VESA mode, but that depends a lot on your hardware. For that, please check http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers. For example, if you'd like to try booting your text mode on 1024x640, you'll find that the mode ID is 877.



            So, when booting, hold the SHIFT key (in case you don't have a GRUB timeout) to bring up GRUB's menu. Select the mode which you wish to boot and press 'e' (to edit the commands). At the end of the "kernel" command, add vga=877. The number is the mode ID, if you want to try other modes, replace it with the desired number.



            Also, at that same Wikipedia page, you could also try the helpful "Universal format" right below the modes table. That hwinfo command is quite useful.






            share|improve this answer



















            • 1





              I use grub2, not grub. I didn't know that grub was responsible for the console, so I didn't mention that in my question. Sorry. I've found a solution with grub2. Regards!

              – egarcia
              Dec 22 '10 at 4:55











            • To be true, the solution you found also seem simpler. Glad you sorted it out, and thanks for sharing!

              – Charles Roberto Canato
              Dec 22 '10 at 7:03














            4












            4








            4







            Just some personal background: in my other computer I have no problem with that fancy mode (it's 160 cols x 60 rows, but it has a 4:3 CRT monitor). It's equipped with a TNT2 (yes, I swear), and that mode was promptly displayed on first boot. Problem is, it does this by loading the nouveau driver, and this guy is still a bit faulty (in my case, it hangs the whole system when trying to move windows). So, to have an usable system, I had to downgrade to the old and stable nv driver, and also disabling mode-setting ('cause the kernel would always load nouveau when enabled). Note that I'm not using nVidia proprietary drivers, but like you, I was switched back to 80x25 in console mode.



            This is because the nv driver doesn't use kernel mode-setting. Now, I don't know about the proprietary drivers, but I'm guessing they might have changed your configuration in order to be usable, and possibly that's why you're seeing that "big" mode. Possibly they disabled mode-setting when installed. That's why you see the "small" text mode when booting from the Live CD.



            You could try booting up with a different VESA mode, but that depends a lot on your hardware. For that, please check http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers. For example, if you'd like to try booting your text mode on 1024x640, you'll find that the mode ID is 877.



            So, when booting, hold the SHIFT key (in case you don't have a GRUB timeout) to bring up GRUB's menu. Select the mode which you wish to boot and press 'e' (to edit the commands). At the end of the "kernel" command, add vga=877. The number is the mode ID, if you want to try other modes, replace it with the desired number.



            Also, at that same Wikipedia page, you could also try the helpful "Universal format" right below the modes table. That hwinfo command is quite useful.






            share|improve this answer













            Just some personal background: in my other computer I have no problem with that fancy mode (it's 160 cols x 60 rows, but it has a 4:3 CRT monitor). It's equipped with a TNT2 (yes, I swear), and that mode was promptly displayed on first boot. Problem is, it does this by loading the nouveau driver, and this guy is still a bit faulty (in my case, it hangs the whole system when trying to move windows). So, to have an usable system, I had to downgrade to the old and stable nv driver, and also disabling mode-setting ('cause the kernel would always load nouveau when enabled). Note that I'm not using nVidia proprietary drivers, but like you, I was switched back to 80x25 in console mode.



            This is because the nv driver doesn't use kernel mode-setting. Now, I don't know about the proprietary drivers, but I'm guessing they might have changed your configuration in order to be usable, and possibly that's why you're seeing that "big" mode. Possibly they disabled mode-setting when installed. That's why you see the "small" text mode when booting from the Live CD.



            You could try booting up with a different VESA mode, but that depends a lot on your hardware. For that, please check http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers. For example, if you'd like to try booting your text mode on 1024x640, you'll find that the mode ID is 877.



            So, when booting, hold the SHIFT key (in case you don't have a GRUB timeout) to bring up GRUB's menu. Select the mode which you wish to boot and press 'e' (to edit the commands). At the end of the "kernel" command, add vga=877. The number is the mode ID, if you want to try other modes, replace it with the desired number.



            Also, at that same Wikipedia page, you could also try the helpful "Universal format" right below the modes table. That hwinfo command is quite useful.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Dec 22 '10 at 4:11









            Charles Roberto CanatoCharles Roberto Canato

            35918




            35918








            • 1





              I use grub2, not grub. I didn't know that grub was responsible for the console, so I didn't mention that in my question. Sorry. I've found a solution with grub2. Regards!

              – egarcia
              Dec 22 '10 at 4:55











            • To be true, the solution you found also seem simpler. Glad you sorted it out, and thanks for sharing!

              – Charles Roberto Canato
              Dec 22 '10 at 7:03














            • 1





              I use grub2, not grub. I didn't know that grub was responsible for the console, so I didn't mention that in my question. Sorry. I've found a solution with grub2. Regards!

              – egarcia
              Dec 22 '10 at 4:55











            • To be true, the solution you found also seem simpler. Glad you sorted it out, and thanks for sharing!

              – Charles Roberto Canato
              Dec 22 '10 at 7:03








            1




            1





            I use grub2, not grub. I didn't know that grub was responsible for the console, so I didn't mention that in my question. Sorry. I've found a solution with grub2. Regards!

            – egarcia
            Dec 22 '10 at 4:55





            I use grub2, not grub. I didn't know that grub was responsible for the console, so I didn't mention that in my question. Sorry. I've found a solution with grub2. Regards!

            – egarcia
            Dec 22 '10 at 4:55













            To be true, the solution you found also seem simpler. Glad you sorted it out, and thanks for sharing!

            – Charles Roberto Canato
            Dec 22 '10 at 7:03





            To be true, the solution you found also seem simpler. Glad you sorted it out, and thanks for sharing!

            – Charles Roberto Canato
            Dec 22 '10 at 7:03











            3














            Why i answer this threat even if it's very old? The answer is pretty easy, because so many other threat refer to it.



            If vbeinfo or hwinfo --framebuffer doesn't show the native resolution of your display, then disable vesa, to do so remove vga= options in:



            sudo nano /etc/default/grub


            Search for GRUB_CMDLINE_LINUX_DEFAULT= and remove vga= if you find it.



            If you have remove the option don't forget to generate a new grub.cfg:



            sudo update-grub


            If you don't know you did it well, then just reboot and open a terminal:



            grep vga /proc/cmdline
            grep -ir vga /etc/modprobe.d/


            If grep doesn't show anything, then you removed the vga= option.



            Now install uvesafb:



            sudo apt-get install v86d


            Make sure the uvesafb module is included into your initrd. Add it to the end of /etc/initramfs-tools/modules:



            sudo sh -c "echo uvesafb >> /etc/initramfs-tools/modules"


            To see what modes are available:



            sudo modprobe uvesafb
            cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes


            Now configure uvesafb mode_option=YOURxResoultion-BitColorMode e.g. 1280x1024-32:



            sudo sh -c "echo options uvesafb mode_option=1280x1024-32 scroll=ywrap > /etc/modprobe.d/uvesafb.conf"


            Don't forget to rebuild your initrd:



            sudo update-initramfs -k all -u


            Now you can reboot!



            See this for more details.
            It is for debian, but it also works for ubuntu.
            I hope it helped you and it should be more generic than using grub2.






            share|improve this answer


























            • +1 no need to change the grub config and uvesafb works for me on Ubuntu 16.04 with a proprietary nvidia driver (recommended in other places KMS is unsupported in this case)

              – jfs
              Sep 14 '16 at 13:31
















            3














            Why i answer this threat even if it's very old? The answer is pretty easy, because so many other threat refer to it.



            If vbeinfo or hwinfo --framebuffer doesn't show the native resolution of your display, then disable vesa, to do so remove vga= options in:



            sudo nano /etc/default/grub


            Search for GRUB_CMDLINE_LINUX_DEFAULT= and remove vga= if you find it.



            If you have remove the option don't forget to generate a new grub.cfg:



            sudo update-grub


            If you don't know you did it well, then just reboot and open a terminal:



            grep vga /proc/cmdline
            grep -ir vga /etc/modprobe.d/


            If grep doesn't show anything, then you removed the vga= option.



            Now install uvesafb:



            sudo apt-get install v86d


            Make sure the uvesafb module is included into your initrd. Add it to the end of /etc/initramfs-tools/modules:



            sudo sh -c "echo uvesafb >> /etc/initramfs-tools/modules"


            To see what modes are available:



            sudo modprobe uvesafb
            cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes


            Now configure uvesafb mode_option=YOURxResoultion-BitColorMode e.g. 1280x1024-32:



            sudo sh -c "echo options uvesafb mode_option=1280x1024-32 scroll=ywrap > /etc/modprobe.d/uvesafb.conf"


            Don't forget to rebuild your initrd:



            sudo update-initramfs -k all -u


            Now you can reboot!



            See this for more details.
            It is for debian, but it also works for ubuntu.
            I hope it helped you and it should be more generic than using grub2.






            share|improve this answer


























            • +1 no need to change the grub config and uvesafb works for me on Ubuntu 16.04 with a proprietary nvidia driver (recommended in other places KMS is unsupported in this case)

              – jfs
              Sep 14 '16 at 13:31














            3












            3








            3







            Why i answer this threat even if it's very old? The answer is pretty easy, because so many other threat refer to it.



            If vbeinfo or hwinfo --framebuffer doesn't show the native resolution of your display, then disable vesa, to do so remove vga= options in:



            sudo nano /etc/default/grub


            Search for GRUB_CMDLINE_LINUX_DEFAULT= and remove vga= if you find it.



            If you have remove the option don't forget to generate a new grub.cfg:



            sudo update-grub


            If you don't know you did it well, then just reboot and open a terminal:



            grep vga /proc/cmdline
            grep -ir vga /etc/modprobe.d/


            If grep doesn't show anything, then you removed the vga= option.



            Now install uvesafb:



            sudo apt-get install v86d


            Make sure the uvesafb module is included into your initrd. Add it to the end of /etc/initramfs-tools/modules:



            sudo sh -c "echo uvesafb >> /etc/initramfs-tools/modules"


            To see what modes are available:



            sudo modprobe uvesafb
            cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes


            Now configure uvesafb mode_option=YOURxResoultion-BitColorMode e.g. 1280x1024-32:



            sudo sh -c "echo options uvesafb mode_option=1280x1024-32 scroll=ywrap > /etc/modprobe.d/uvesafb.conf"


            Don't forget to rebuild your initrd:



            sudo update-initramfs -k all -u


            Now you can reboot!



            See this for more details.
            It is for debian, but it also works for ubuntu.
            I hope it helped you and it should be more generic than using grub2.






            share|improve this answer















            Why i answer this threat even if it's very old? The answer is pretty easy, because so many other threat refer to it.



            If vbeinfo or hwinfo --framebuffer doesn't show the native resolution of your display, then disable vesa, to do so remove vga= options in:



            sudo nano /etc/default/grub


            Search for GRUB_CMDLINE_LINUX_DEFAULT= and remove vga= if you find it.



            If you have remove the option don't forget to generate a new grub.cfg:



            sudo update-grub


            If you don't know you did it well, then just reboot and open a terminal:



            grep vga /proc/cmdline
            grep -ir vga /etc/modprobe.d/


            If grep doesn't show anything, then you removed the vga= option.



            Now install uvesafb:



            sudo apt-get install v86d


            Make sure the uvesafb module is included into your initrd. Add it to the end of /etc/initramfs-tools/modules:



            sudo sh -c "echo uvesafb >> /etc/initramfs-tools/modules"


            To see what modes are available:



            sudo modprobe uvesafb
            cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes


            Now configure uvesafb mode_option=YOURxResoultion-BitColorMode e.g. 1280x1024-32:



            sudo sh -c "echo options uvesafb mode_option=1280x1024-32 scroll=ywrap > /etc/modprobe.d/uvesafb.conf"


            Don't forget to rebuild your initrd:



            sudo update-initramfs -k all -u


            Now you can reboot!



            See this for more details.
            It is for debian, but it also works for ubuntu.
            I hope it helped you and it should be more generic than using grub2.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Sep 6 '15 at 14:17









            muru

            1




            1










            answered Sep 5 '15 at 14:00









            Arch UserArch User

            494




            494













            • +1 no need to change the grub config and uvesafb works for me on Ubuntu 16.04 with a proprietary nvidia driver (recommended in other places KMS is unsupported in this case)

              – jfs
              Sep 14 '16 at 13:31



















            • +1 no need to change the grub config and uvesafb works for me on Ubuntu 16.04 with a proprietary nvidia driver (recommended in other places KMS is unsupported in this case)

              – jfs
              Sep 14 '16 at 13:31

















            +1 no need to change the grub config and uvesafb works for me on Ubuntu 16.04 with a proprietary nvidia driver (recommended in other places KMS is unsupported in this case)

            – jfs
            Sep 14 '16 at 13:31





            +1 no need to change the grub config and uvesafb works for me on Ubuntu 16.04 with a proprietary nvidia driver (recommended in other places KMS is unsupported in this case)

            – jfs
            Sep 14 '16 at 13:31











            1














            Ubuntu 18 console mode:



            Edit



            GRUB_CMDLINE_LINUX_DEFAULT="splash quite"


            in



            /etc/default/grub


            so new line looks like:



            GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=XXX nomodeset"


            where XXX comes from



            https://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/



            then reload grub config and reboot



            update-grub2
            reboot





            share|improve this answer
























            • It seems like this question has already a many similar answers. Perhaps you could clarify what motivated you to add your answer (i.e. what information was missing from previously posted answers).

              – cauon
              Mar 24 at 11:34











            • It's just simple. And suitable for newest Ubuntu 18

              – Paul Paku
              Mar 24 at 14:21


















            1














            Ubuntu 18 console mode:



            Edit



            GRUB_CMDLINE_LINUX_DEFAULT="splash quite"


            in



            /etc/default/grub


            so new line looks like:



            GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=XXX nomodeset"


            where XXX comes from



            https://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/



            then reload grub config and reboot



            update-grub2
            reboot





            share|improve this answer
























            • It seems like this question has already a many similar answers. Perhaps you could clarify what motivated you to add your answer (i.e. what information was missing from previously posted answers).

              – cauon
              Mar 24 at 11:34











            • It's just simple. And suitable for newest Ubuntu 18

              – Paul Paku
              Mar 24 at 14:21
















            1












            1








            1







            Ubuntu 18 console mode:



            Edit



            GRUB_CMDLINE_LINUX_DEFAULT="splash quite"


            in



            /etc/default/grub


            so new line looks like:



            GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=XXX nomodeset"


            where XXX comes from



            https://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/



            then reload grub config and reboot



            update-grub2
            reboot





            share|improve this answer













            Ubuntu 18 console mode:



            Edit



            GRUB_CMDLINE_LINUX_DEFAULT="splash quite"


            in



            /etc/default/grub


            so new line looks like:



            GRUB_CMDLINE_LINUX_DEFAULT="splash quiet vga=XXX nomodeset"


            where XXX comes from



            https://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/



            then reload grub config and reboot



            update-grub2
            reboot






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 24 at 10:39









            Paul PakuPaul Paku

            111




            111













            • It seems like this question has already a many similar answers. Perhaps you could clarify what motivated you to add your answer (i.e. what information was missing from previously posted answers).

              – cauon
              Mar 24 at 11:34











            • It's just simple. And suitable for newest Ubuntu 18

              – Paul Paku
              Mar 24 at 14:21





















            • It seems like this question has already a many similar answers. Perhaps you could clarify what motivated you to add your answer (i.e. what information was missing from previously posted answers).

              – cauon
              Mar 24 at 11:34











            • It's just simple. And suitable for newest Ubuntu 18

              – Paul Paku
              Mar 24 at 14:21



















            It seems like this question has already a many similar answers. Perhaps you could clarify what motivated you to add your answer (i.e. what information was missing from previously posted answers).

            – cauon
            Mar 24 at 11:34





            It seems like this question has already a many similar answers. Perhaps you could clarify what motivated you to add your answer (i.e. what information was missing from previously posted answers).

            – cauon
            Mar 24 at 11:34













            It's just simple. And suitable for newest Ubuntu 18

            – Paul Paku
            Mar 24 at 14:21







            It's just simple. And suitable for newest Ubuntu 18

            – Paul Paku
            Mar 24 at 14:21













            0














            This will not change the font on boot, but for the console on Ctrl+Alt+F[1-6]



            Install the custom Ubuntu fonts for your console:



            sudo apt-get install fonts-ubuntu-font-family-console


            And create a script /usr/local/bin/fontset with this command:



            #!/bin/sh
            setfont /usr/share/consolefonts/Uni3-TerminusBold32x16.psf.gz


            (choose the desired fon out of the folder /usr/share/consolefonts/)



            You can either call fontset each time on your console after using Ctrl+Alt+F1



            or add this line to your /root/.profile



            [ ! -t 0 ] && sleep 1 & /usr/local/bin/fontset


            (don't add this to your users .profile or you get an error on a graphical boot)



            source: Resize font on boot message screen and console






            share|improve this answer






























              0














              This will not change the font on boot, but for the console on Ctrl+Alt+F[1-6]



              Install the custom Ubuntu fonts for your console:



              sudo apt-get install fonts-ubuntu-font-family-console


              And create a script /usr/local/bin/fontset with this command:



              #!/bin/sh
              setfont /usr/share/consolefonts/Uni3-TerminusBold32x16.psf.gz


              (choose the desired fon out of the folder /usr/share/consolefonts/)



              You can either call fontset each time on your console after using Ctrl+Alt+F1



              or add this line to your /root/.profile



              [ ! -t 0 ] && sleep 1 & /usr/local/bin/fontset


              (don't add this to your users .profile or you get an error on a graphical boot)



              source: Resize font on boot message screen and console






              share|improve this answer




























                0












                0








                0







                This will not change the font on boot, but for the console on Ctrl+Alt+F[1-6]



                Install the custom Ubuntu fonts for your console:



                sudo apt-get install fonts-ubuntu-font-family-console


                And create a script /usr/local/bin/fontset with this command:



                #!/bin/sh
                setfont /usr/share/consolefonts/Uni3-TerminusBold32x16.psf.gz


                (choose the desired fon out of the folder /usr/share/consolefonts/)



                You can either call fontset each time on your console after using Ctrl+Alt+F1



                or add this line to your /root/.profile



                [ ! -t 0 ] && sleep 1 & /usr/local/bin/fontset


                (don't add this to your users .profile or you get an error on a graphical boot)



                source: Resize font on boot message screen and console






                share|improve this answer















                This will not change the font on boot, but for the console on Ctrl+Alt+F[1-6]



                Install the custom Ubuntu fonts for your console:



                sudo apt-get install fonts-ubuntu-font-family-console


                And create a script /usr/local/bin/fontset with this command:



                #!/bin/sh
                setfont /usr/share/consolefonts/Uni3-TerminusBold32x16.psf.gz


                (choose the desired fon out of the folder /usr/share/consolefonts/)



                You can either call fontset each time on your console after using Ctrl+Alt+F1



                or add this line to your /root/.profile



                [ ! -t 0 ] && sleep 1 & /usr/local/bin/fontset


                (don't add this to your users .profile or you get an error on a graphical boot)



                source: Resize font on boot message screen and console







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Apr 13 '17 at 12:24









                Community

                1




                1










                answered Sep 1 '15 at 6:26









                rubo77rubo77

                15.4k31100205




                15.4k31100205























                    0














                    The following worked for me on Debian Stretch 4.9.51-1.

                    No GUI, only console mode:



                    Edit /etc/default/grub and add the following line



                    GRUB_CMDLINE_LINUX_DEFAULT="splash vga=795 nomodeset"


                    For a list of vga= codes see http://pierre.baudu.in/other/grub.vga.modes.html



                    The nomodeset prevents the resolution from changing again after grub initializes [thanks How do I increase console-mode resolution? ]



                    EDIT:
                    As mentioned by @Videonauth :
                    Afterwards do:

                    sudo update-grub






                    share|improve this answer


























                    • To make changes in /etc/default/grub is not enough, you as well need to run afterwards sudo update-grub to make it happen

                      – Videonauth
                      Oct 26 '17 at 15:51
















                    0














                    The following worked for me on Debian Stretch 4.9.51-1.

                    No GUI, only console mode:



                    Edit /etc/default/grub and add the following line



                    GRUB_CMDLINE_LINUX_DEFAULT="splash vga=795 nomodeset"


                    For a list of vga= codes see http://pierre.baudu.in/other/grub.vga.modes.html



                    The nomodeset prevents the resolution from changing again after grub initializes [thanks How do I increase console-mode resolution? ]



                    EDIT:
                    As mentioned by @Videonauth :
                    Afterwards do:

                    sudo update-grub






                    share|improve this answer


























                    • To make changes in /etc/default/grub is not enough, you as well need to run afterwards sudo update-grub to make it happen

                      – Videonauth
                      Oct 26 '17 at 15:51














                    0












                    0








                    0







                    The following worked for me on Debian Stretch 4.9.51-1.

                    No GUI, only console mode:



                    Edit /etc/default/grub and add the following line



                    GRUB_CMDLINE_LINUX_DEFAULT="splash vga=795 nomodeset"


                    For a list of vga= codes see http://pierre.baudu.in/other/grub.vga.modes.html



                    The nomodeset prevents the resolution from changing again after grub initializes [thanks How do I increase console-mode resolution? ]



                    EDIT:
                    As mentioned by @Videonauth :
                    Afterwards do:

                    sudo update-grub






                    share|improve this answer















                    The following worked for me on Debian Stretch 4.9.51-1.

                    No GUI, only console mode:



                    Edit /etc/default/grub and add the following line



                    GRUB_CMDLINE_LINUX_DEFAULT="splash vga=795 nomodeset"


                    For a list of vga= codes see http://pierre.baudu.in/other/grub.vga.modes.html



                    The nomodeset prevents the resolution from changing again after grub initializes [thanks How do I increase console-mode resolution? ]



                    EDIT:
                    As mentioned by @Videonauth :
                    Afterwards do:

                    sudo update-grub







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Oct 27 '17 at 19:23

























                    answered Oct 26 '17 at 15:11









                    OttiOtti

                    11




                    11













                    • To make changes in /etc/default/grub is not enough, you as well need to run afterwards sudo update-grub to make it happen

                      – Videonauth
                      Oct 26 '17 at 15:51



















                    • To make changes in /etc/default/grub is not enough, you as well need to run afterwards sudo update-grub to make it happen

                      – Videonauth
                      Oct 26 '17 at 15:51

















                    To make changes in /etc/default/grub is not enough, you as well need to run afterwards sudo update-grub to make it happen

                    – Videonauth
                    Oct 26 '17 at 15:51





                    To make changes in /etc/default/grub is not enough, you as well need to run afterwards sudo update-grub to make it happen

                    – Videonauth
                    Oct 26 '17 at 15:51


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f18444%2fhow-do-i-increase-console-mode-resolution%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

                    數位音樂下載

                    When can things happen in Etherscan, such as the picture below?

                    格利澤436b