Lines Matching +full:boot +full:- +full:mode
7 The idea is simple: Turn on graphics mode at boot time with the help
11 This means we decide at boot time whenever we want to run in text or
12 graphics mode. Switching mode later on (in protected mode) is
13 impossible; BIOS calls work in real mode only. VESA BIOS Extensions
20 * You can run XF68_FBDev on top of /dev/fb0 (=> non-accelerated X11
22 * Most important: boot logo :-)
26 * graphic mode is slower than text mode...
32 Switching modes is done using the vga=... boot parameter. Read
33 Documentation/admin-guide/svga.rst for details.
35 You should compile in both vgacon (for text mode) and vesafb (for
36 graphics mode). Which of them takes over the console depends on
37 whenever the specified mode is text or graphics.
39 The graphic modes are NOT in the list which you get if you boot with
40 vga=ask and hit return. The mode you wish to use is derived from the
41 VESA mode number. Here are those VESA mode numbers:
53 The video mode number of the Linux kernel is the VESA mode number plus
58 So the table for the Kernel mode numbers are:
71 mode at the "vga=ask" prompt. For example if you like to use
75 linear framebuffers or because it does not support this mode at all.
78 "bad mode number" message if something goes wrong.
81 "vga=mode-number" you have to transform the numbers to decimal.
88 XF68_FBDev should work just fine, but it is non-accelerated. Running
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
90 It depends on X-Server and graphics board.
92 The X-Server must restore the video mode correctly, else you end up
99 There is no way to change the vesafb video mode and/or timings after
103 * configure and load the DOS-Tools for the graphics board (if
104 available) and boot linux with loadlin.
114 The VESA BIOS provides protected mode interface for changing
129 ypan enable display panning using the VESA protected mode
142 ugly flicker effects (boot logo flickers for
145 ywrap Same as ypan, but assumes your gfx board can wrap-around
155 pmipal Use the protected mode interface for palette changes.
160 - 0 - disabled (equivalent to nomtrr) (default)
161 - 1 - uncachable
162 - 2 - write-back
163 - 3 - write-combining
164 - 4 - write-through
169 mtrr: type mismatch for e0000000,8000000 old: write-back new:
170 write-combining
177 according to video mode. (2.5.66 patch/idea by Antonino Daplas
187 Gerd Knorr <kraxel@goldbach.in-berlin.de>
190 by Nico Schmoigl <schmoigl@rumms.uni-mannheim.de>