I'd like to use the hardware character generator for the console instead of framebuffer.
I've tried booting with the nomodeset kernel option. This does the thing for the console. However it also affects Xorg. I don't want VESA for Xorg, just to switch off the framebuffer for the console. How can I achieve that?
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[Software] Kernel option to use VGA text mode or EFI Simple Text Output Protocol instead of framebuffer
- ruwolf
- Posts: 643
- Joined: 2008-02-18 05:04
- Location: Banovce nad Bebravou
- Has thanked: 41 times
- Been thanked: 30 times
Re: [Software] Kernel option to use VGA text mode or EFI Simple Text Output Protocol instead of framebuffer
Which X.org server/driver do you want to use?
E.g.:
E.g.:
wiki.ArchLinux.org: AMDGPU wrote:Make sure you do not have nomodeset or vga= as a kernel parameter, since amdgpu requires KMS.
wiki.ArchLinux.org: ATI wrote:Make sure you do not have nomodeset or vga= as a kernel parameter, since radeon requires KMS.
Re: [Software] Kernel option to use VGA text mode or EFI Simple Text Output Protocol instead of framebuffer
What I've tried now is adding the line FRAMEBUFFER=n into /etc/initramfs-tools/initramfs.conf and then running update-initramfs -u to regenerate initram-fs.
However, I am still getting a framebuffer console after reboot.
However, I am still getting a framebuffer console after reboot.
- ruwolf
- Posts: 643
- Joined: 2008-02-18 05:04
- Location: Banovce nad Bebravou
- Has thanked: 41 times
- Been thanked: 30 times
Re: [Software] Kernel option to use VGA text mode or EFI Simple Text Output Protocol instead of framebuffer
P.S.docs.Kernel.org: Console Drivers wrote:If any of the virtual consoles are in KD_GRAPHICS mode, then binding or unbinding will not succeed. An example of an application that sets the console to KD_GRAPHICS is X.
I have tried to add to /etc/default/grub:
Code: Select all
GRUB_TERMINAL=console
GRUB_GFXPAYLOAD_LINUX=text
P.P.S.
When I added nomodeset, Xorg is runing in:
Code: Select all
[ 7.459] (II) FBDEV(0): hardware: EFI VGA (video memory: 8100kB)
[ 7.459] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 7.459] (II) FBDEV(0): checking modes against framebuffer device...
[ 7.459] (II) FBDEV(0): checking modes against monitor...
[ 7.459] (II) FBDEV(0): Virtual size is 1920x1080 (pitch 1920)
[ 7.459] (**) FBDEV(0): Built-in mode "current": 207.4 MHz, 85.3 kHz, 77.2 Hz
[ 7.459] (II) FBDEV(0): Modeline "current"x0.0 207.38 1920 1952 2192 2432 1080 1084 1088 1104 -hsync -vsync -csync (85.3 kHz b)
[ 7.459] (==) FBDEV(0): DPI set to (96, 96)
[ 7.459] (II) Loading sub module "fb"
[ 7.459] (II) LoadModule: "fb"
[ 7.459] (II) Module "fb" already built-in
[ 7.459] (**) FBDEV(0): using shadow framebuffer
[ 7.459] (II) Loading sub module "shadow"
[ 7.459] (II) LoadModule: "shadow"
[ 7.459] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 7.459] (II) Module shadow: vendor="X.Org Foundation"
[ 7.459] compiled for 1.21.1.7, module version = 1.1.0
[ 7.459] ABI class: X.Org ANSI C Emulation, version 0.4
[ 7.460] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
[ 7.461] (==) FBDEV(0): Backing store enabled
[ 7.462] (==) FBDEV(0): DPMS enabled
[ 7.462] (II) Initializing extension Generic Event Extension
[ 7.462] (II) Initializing extension SHAPE
[ 7.462] (II) Initializing extension MIT-SHM
[ 7.462] (II) Initializing extension XInputExtension
[ 7.462] (II) Initializing extension XTEST
[ 7.462] (II) Initializing extension BIG-REQUESTS
[ 7.462] (II) Initializing extension SYNC
[ 7.463] (II) Initializing extension XKEYBOARD
[ 7.463] (II) Initializing extension XC-MISC
[ 7.463] (II) Initializing extension SECURITY
[ 7.463] (II) Initializing extension XFIXES
[ 7.463] (II) Initializing extension RENDER
[ 7.463] (II) Initializing extension RANDR
[ 7.463] (II) Initializing extension COMPOSITE
[ 7.463] (II) Initializing extension DAMAGE
[ 7.463] (II) Initializing extension MIT-SCREEN-SAVER
[ 7.463] (II) Initializing extension DOUBLE-BUFFER
[ 7.463] (II) Initializing extension RECORD
[ 7.463] (II) Initializing extension DPMS
[ 7.463] (II) Initializing extension Present
[ 7.463] (II) Initializing extension DRI3
[ 7.463] (II) Initializing extension X-Resource
[ 7.463] (II) Initializing extension XVideo
[ 7.463] (II) Initializing extension XVideo-MotionCompensation
[ 7.463] (II) Initializing extension SELinux
[ 7.463] (II) SELinux: Disabled on system
[ 7.463] (II) Initializing extension GLX
[ 7.463] (II) AIGLX: Screen 0 is not DRI2 capable
[ 7.963] (II) IGLX: Loaded and initialized swrast
[ 7.964] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 7.964] (II) Initializing extension XFree86-VidModeExtension
[ 7.964] (II) Initializing extension XFree86-DGA
[ 7.964] (II) Initializing extension XFree86-DRI
[ 7.964] (II) Initializing extension DRI2
Even /sys/class/backlight is empty.
- ruwolf
- Posts: 643
- Joined: 2008-02-18 05:04
- Location: Banovce nad Bebravou
- Has thanked: 41 times
- Been thanked: 30 times
Re: [Software] Kernel option to use VGA text mode or EFI Simple Text Output Protocol instead of framebuffer
I can disable framebuffer on the first six consoles by parameter:
but this does not show other consoles.
It is strange, because they work with nomodeset.
Code: Select all
fbcon=vc:7-8
It is strange, because they work with nomodeset.
Re: [Software] Kernel option to use VGA text mode or EFI Simple Text Output Protocol instead of framebuffer
To what end? IOW, why?
In Trixie at least I can fake BIOS 80x25 mode on vttys by using video=640x400 or video=640x480 grub linu line option here. I say fake, but can't actually recognize any difference from booting DOS to a C:\> prompt.