Lines Matching refs:fbcon
5 The framebuffer console (fbcon), as its name implies, is a text
14 What are the features of fbcon? The framebuffer console supports
26 module will be fbcon.
28 In order for fbcon to activate, at least one framebuffer driver is
53 1. Driver and fbcon are compiled statically
55 Usually, fbcon will automatically take over your console. The notable
59 2. Driver is compiled statically, fbcon is compiled as a module
63 do a 'modprobe fbcon'.
65 3. Driver is compiled as a module, fbcon is compiled statically
68 'modprobe xxxfb', fbcon automatically takes over the console with
69 the possible exception of using the fbcon=map:n option. See below.
71 4. Driver and fbcon are compiled as a module.
73 You can load them in any order. Once both are loaded, fbcon will take
81 1. fbcon=font:<name>
90 2. fbcon=scrollback:<value>[k]
98 3. fbcon=map:<0123>
113 available, fb0, adding fbcon=map:1 tells fbcon not to take over the
119 4. fbcon=vc:<n1>-<n2>
121 This option tells fbcon to take over only a range of consoles as
130 4. fbcon=rotate:<n>
142 /sys/class/graphics/fbcon:
155 5. fbcon=margin:<color>
162 6. fbcon=nodefer
164 If the kernel is compiled with deferred fbcon takeover support, normally
167 This option causes fbcon to bind immediately to the fbdev device.
169 7. fbcon=logo-pos:<location>
192 This is more complicated in the case of the framebuffer console (fbcon),
193 because fbcon is an intermediate layer between the console and the drivers::
195 console ---> fbcon ---> fbdev drivers ---> hardware
197 The fbdev drivers cannot be unloaded if bound to fbcon, and fbcon cannot
200 So to unload the fbdev drivers, one must first unbind fbcon from the console,
201 then unbind the fbdev drivers from fbcon. Fortunately, unbinding fbcon from
203 fbcon. Thus, there is no need to explicitly unbind the fbdev drivers from
204 fbcon.
206 So, how do we unbind fbcon from the console? Part of the answer is in
210 driver. So assuming vtcon1 represents fbcon, then::
217 If fbcon is detached from the console layer, your boot console driver (which is
219 restore VGA text mode for you. With the rest, before detaching fbcon, you
237 4. If fbcon is compiled as a module, load fbcon by doing::
239 modprobe fbcon
241 5. Now to detach fbcon::
246 6. That's it, you're back to VGA mode. And if you compiled fbcon as a module,
247 you can unload it by 'rmmod fbcon'.
249 7. To reattach fbcon::
253 8. Once fbcon is unbound, all drivers registered to the system will also
254 become unbound. This means that fbcon and individual framebuffer drivers
255 can be unloaded or reloaded at will. Reloading the drivers or fbcon will
256 automatically bind the console, fbcon and the drivers together. Unloading
257 all the drivers without unloading fbcon will make it impossible for the
258 console to bind fbcon.
266 won't get any display after detaching fbcon. Your machine is still alive, so
272 a. Before detaching fbcon, do::
277 b. Detach fbcon as in step 5.
279 c. Attach fbcon::
286 a. Before detaching fbcon, do::
294 b. Detach fbcon as in step 5.
296 c. Attach fbcon::
308 # Unbind fbcon
337 # Bind fbcon