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>
91 2. fbcon=map:<0123>
106 available, fb0, adding fbcon=map:1 tells fbcon not to take over the
112 3. fbcon=vc:<n1>-<n2>
114 This option tells fbcon to take over only a range of consoles as
123 4. fbcon=rotate:<n>
135 /sys/class/graphics/fbcon:
148 5. fbcon=margin:<color>
155 6. fbcon=nodefer
157 If the kernel is compiled with deferred fbcon takeover support, normally
160 This option causes fbcon to bind immediately to the fbdev device.
162 7. fbcon=logo-pos:<location>
170 8. fbcon=logo-count:<n>
190 This is more complicated in the case of the framebuffer console (fbcon),
191 because fbcon is an intermediate layer between the console and the drivers::
193 console ---> fbcon ---> fbdev drivers ---> hardware
195 The fbdev drivers cannot be unloaded if bound to fbcon, and fbcon cannot
198 So to unload the fbdev drivers, one must first unbind fbcon from the console,
199 then unbind the fbdev drivers from fbcon. Fortunately, unbinding fbcon from
201 fbcon. Thus, there is no need to explicitly unbind the fbdev drivers from
202 fbcon.
204 So, how do we unbind fbcon from the console? Part of the answer is in
208 driver. So assuming vtcon1 represents fbcon, then::
215 If fbcon is detached from the console layer, your boot console driver (which is
217 restore VGA text mode for you. With the rest, before detaching fbcon, you
235 4. If fbcon is compiled as a module, load fbcon by doing::
237 modprobe fbcon
239 5. Now to detach fbcon::
244 6. That's it, you're back to VGA mode. And if you compiled fbcon as a module,
245 you can unload it by 'rmmod fbcon'.
247 7. To reattach fbcon::
251 8. Once fbcon is unbound, all drivers registered to the system will also
252 become unbound. This means that fbcon and individual framebuffer drivers
253 can be unloaded or reloaded at will. Reloading the drivers or fbcon will
254 automatically bind the console, fbcon and the drivers together. Unloading
255 all the drivers without unloading fbcon will make it impossible for the
256 console to bind fbcon.
264 won't get any display after detaching fbcon. Your machine is still alive, so
270 a. Before detaching fbcon, do::
275 b. Detach fbcon as in step 5.
277 c. Attach fbcon::
284 a. Before detaching fbcon, do::
292 b. Detach fbcon as in step 5.
294 c. Attach fbcon::
306 # Unbind fbcon
335 # Bind fbcon