Plymouth and terminal with nvidia proprietary driver

Seninha · 2012-04-05 23:27:18

I installed arch linux recently and until now had some problems ....

Just what I like to play some logos, so I must have installed the nvidia proprietary driver.

Only after I installed the nvidia driver, both Plymouth (boot splash) on Linux terminals with different size were normal.

I use a widescreen and plymouth and the terminal appear with a reduced size.

How do they get the normal size?

The problem is not the image resolution. The resolution is great.
What happens is that the Plymouth, the terminal (tty) and burg are reduced in size (see picture):

Grub
TTY
TTY

For solve this problem I just edit this line in /etc/mkinitcpio.conf:

MODULES="nouveau"

And run the following command, to update the initramfs:

mkinitcpio -p linux

It solves the problem, both the tty and the plymouth gets to my screen's normal size
But when I do it. It runs the nouveau driver instead the nvidia driver. So I cannot play my games without the proprietary nvidia driver.

Vou copiar aqui o meu /etc/mkinitcpio.conf e o meu burg.cfg

Here is my /etc/mkinitcpio.conf and my burg.cfg

/etc/mkinitcpio.conf:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
#    FILES="/etc/modprobe.d/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect pata scsi sata filesystems"
#
##   This is identical to the above, except the old ide subsystem is
##   used for IDE devices instead of the new pata subsystem.
#    HOOKS="base udev autodetect ide scsi sata filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev pata scsi sata usb filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev pata mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev usb lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck v86d plymouth"

# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

burg.cfg:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /sbin/burg-mkconfig using templates
# from /etc/burg.d and settings from /etc/default/burg
#

### BEGIN /etc/burg.d/00_header ###
set theme_name=burg
set gfxmode=640x480
if [ -s $prefix/burgenv ]; then
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
  fi
}
function select_menu {
  if menu_popup -t template_popup theme_menu ; then
    free_config template_popup template_subitem menu class screen
    load_config ${prefix}/themes/${theme_name}/theme ${prefix}/themes/custom/theme_${theme_name}
    save_env theme_name
    menu_refresh
  fi
}
function toggle_fold {
  if test -z $theme_fold ; then
    set theme_fold=1
  else
    set theme_fold=
  fi
  save_env theme_fold
  menu_refresh
}
function select_resolution {
  if menu_popup -t template_popup resolution_menu ; then
    menu_reload_mode
    save_env gfxmode
  fi
}
if test -f ${prefix}/themes/${theme_name}/theme ; then
  insmod coreui
  menu_region.text
  load_string '+theme_menu { -arabic_and_freedom { command="set theme_name=arabic_and_freedom" }}'
  load_string '+theme_menu { -Autumn-Refined { command="set theme_name=Autumn-Refined" }}'
  load_string '+theme_menu { -black_and_white { command="set theme_name=black_and_white" }}'
  load_string '+theme_menu { -burg { command="set theme_name=burg" }}'
  load_string '+theme_menu { -chiva { command="set theme_name=chiva" }}'
  load_string '+theme_menu { -coffee { command="set theme_name=coffee" }}'
  load_string '+theme_menu { -fortune { command="set theme_name=fortune" }}'
  load_string '+theme_menu { -minimal { command="set theme_name=minimal" }}'
  load_string '+theme_menu { -minimum { command="set theme_name=minimum" }}'
  load_string '+theme_menu { -proto { command="set theme_name=proto" }}'
  load_string '+theme_menu { -radiance { command="set theme_name=radiance" }}'
  load_string '+theme_menu { -radianceblack { command="set theme_name=radianceblack" }}'
  load_string '+theme_menu { -radiancetext { command="set theme_name=radiancetext" }}'
  load_string '+theme_menu { -refit { command="set theme_name=refit" }}'
  load_string '+theme_menu { -sora { command="set theme_name=sora" }}'
  load_string '+theme_menu { -sora_clean { command="set theme_name=sora_clean" }}'
  load_string '+theme_menu { -sora_extended { command="set theme_name=sora_extended" }}'
  load_string '+theme_menu { -ubuntu { command="set theme_name=ubuntu" }}'
  load_string '+theme_menu { -ubuntu2 { command="set theme_name=ubuntu2" }}'
  load_string '+theme_menu { -vitruvio { command="set theme_name=vitruvio" }}'
  load_string '+theme_menu { -winter { command="set theme_name=winter" }}'
  load_config ${prefix}/themes/conf.d/10_hotkey
  load_config ${prefix}/themes/${theme_name}/theme ${prefix}/themes/custom/theme_${theme_name}
  insmod vbe
  insmod png
  insmod jpeg
  set gfxfont="Unifont Regular 16"
  menu_region.gfx
  vmenu resolution_menu
  controller.ext
fi
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set ab0d2af5-7f13-43e1-a6c3-750a7eb3c172
set locale_dir=($root)/boot/burg/locale
set lang=pt
insmod gettext
set timeout=5
### END /etc/burg.d/00_header ###

### BEGIN /etc/burg.d/10_custom ###
set root='(hd0,2)'
menuentry 'archlinux GNU/Linux' --class archlinux {
	linux	/boot/vmlinuz-linux root=UUID=ab0d2af5-7f13-43e1-a6c3-750a7eb3c172 ro quiet splash
	initrd	/boot/initramfs-linux.img
}

menuentry 'archlinux GNU/Linux (modo de recuperação)'{
	linux	/boot/vmlinuz-linux root=UUID=ab0d2af5-7f13-43e1-a6c3-750a7eb3c172 ro single 
	initrd	/boot/initramfs-linux-fallback.img
}
### END /etc/burg.d/10_custom ###

Seninha · 2012-04-06 23:42:48

I discovered that both VGA and Uvesa don't accept the resolution of my screen 1920x1080 (that is a widescreen resolutin, proportion 16:9)
And the maximum that they accept is 1280x720 (proportion 16:9 either)

Basically the following happens:
My screen resolution: 1920x1080 (16:9)
The maximum resolution of uvesa/vga: 1280x720 (16:9)

So the quality of the image is great, beacause both resolution have same proportion. But it size is not good, because my screen resolution is bigger than the supported, instead of being proportional

I discovered too that I can configure in my BIOS the resolution of VGA. I'll try to do it.

Thanks

DSpider · 2012-04-12 13:40:09

I think it's because the monitor is centring it. You feed it a 1280x720 signal and it tries its best to centre it. Some displays have the option, I believe it's called "1:1 pixel mapping". Look through your monitor's settings. Of course, some older games that use 640x480 (Diablo II, Starcraft, Red Alert 2) will look like shit, all stretched out instead of using black borders on either sides of the screen.

The high resolution you get with Nouveau is because it uses KMS. The proprietary Nvidia drivers don't. And while Nouveau can have some 3D support using the nouveau-dri package, if you're gonna play games you're probably better off dual booting with Windows.

Arch Linux

#1 2012-04-05 23:27:18

Plymouth and terminal with nvidia proprietary driver

#2 2012-04-06 23:42:48

Re: Plymouth and terminal with nvidia proprietary driver

#3 2012-04-12 13:40:09

Re: Plymouth and terminal with nvidia proprietary driver

Board footer