Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #190413

Re: Setting a console resolution

From Brian <ad44@cityscape.co.uk>
Newsgroups linux.debian.user
Subject Re: Setting a console resolution
Date 2017-12-28 18:00 +0100
Message-ID <v1JHc-2PZ-11@gated-at.bofh.it> (permalink)
References <v1ERb-7Te-1@gated-at.bofh.it> <v1J4v-2Be-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu 28 Dec 2017 at 17:12:47 +0100, henrik i wrote:

> A small update. I did some more testing on the system with Intel 3600
> graphics, and at least one working solution was to blacklist the module:
> 
> In /etc/modprobe.d/whatever.conf
> blacklist gma500_gfx
> 
> This enabled me to use the following lines in /etc/default/grub
> GRUB_GFXMODE=1024x768@60
> GRUB_GFXPAYLOAD_LINUX=keep
> 
> Then run update-grub as always. For some reason, this works for resolution
> change for both grub and the console. I guess this is because vesafb is now
> in use. I wish it was possible to change the resolution with the 'native'
> modules, but have not found the right documentation on the video= syntax
> (if it works at all). As mentioned, it did not work with setting it in grub.

I have a machine with an nvidia card. 'video=800x600' added to the linux
line at boot time works satisfactorily. Can also be done via grub in
/etc/default.

-- 
Brian.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Setting a console resolution henrik i <whocarez1@gmail.com> - 2017-12-28 12:50 +0100
  Re: Setting a console resolution henrik i <whocarez1@gmail.com> - 2017-12-28 17:20 +0100
    Re: Setting a console resolution Brian <ad44@cityscape.co.uk> - 2017-12-28 18:00 +0100
      Re: Setting a console resolution Sven Joachim <svenjoac@gmx.de> - 2017-12-28 20:30 +0100

csiph-web