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
55 1. Driver and fbcon are compiled statically
57 Usually, fbcon will automatically take over your console. The notable
61 2. Driver is compiled statically, fbcon is compiled as a module
65 do a 'modprobe fbcon'.
67 3. Driver is compiled as a module, fbcon is compiled statically
70 'modprobe xxxfb', fbcon automatically takes over the console with
71 the possible exception of using the fbcon=map:n option. See below.
73 4. Driver and fbcon are compiled as a module.
75 You can load them in any order. Once both are loaded, fbcon will take
84 1. fbcon=font:<name>
94 2. fbcon=map:<0123>
109 available, fb0, adding fbcon=map:1 tells fbcon not to take over the
115 3. fbcon=vc:<n1>-<n2>
117 This option tells fbcon to take over only a range of consoles as
127 4. fbcon=rotate:<n>
139 /sys/class/graphics/fbcon:
153 5. fbcon=margin:<color>
160 6. fbcon=nodefer
162 If the kernel is compiled with deferred fbcon takeover support, normally
165 This option causes fbcon to bind immediately to the fbdev device.
167 7. fbcon=logo-pos:<location>
175 8. fbcon=logo-count:<n>
196 This is more complicated in the case of the framebuffer console (fbcon),
197 because fbcon is an intermediate layer between the console and the drivers::
199 console ---> fbcon ---> fbdev drivers ---> hardware
201 The fbdev drivers cannot be unloaded if bound to fbcon, and fbcon cannot
204 So to unload the fbdev drivers, one must first unbind fbcon from the console,
205 then unbind the fbdev drivers from fbcon. Fortunately, unbinding fbcon from
207 fbcon. Thus, there is no need to explicitly unbind the fbdev drivers from
208 fbcon.
210 So, how do we unbind fbcon from the console? Part of the answer is in
214 driver. So assuming vtcon1 represents fbcon, then::
221 If fbcon is detached from the console layer, your boot console driver (which is
223 restore VGA text mode for you. With the rest, before detaching fbcon, you
241 4. If fbcon is compiled as a module, load fbcon by doing::
243 modprobe fbcon
245 5. Now to detach fbcon::
250 6. That's it, you're back to VGA mode. And if you compiled fbcon as a module,
251 you can unload it by 'rmmod fbcon'.
253 7. To reattach fbcon::
257 8. Once fbcon is unbound, all drivers registered to the system will also
258 become unbound. This means that fbcon and individual framebuffer drivers
259 can be unloaded or reloaded at will. Reloading the drivers or fbcon will
260 automatically bind the console, fbcon and the drivers together. Unloading
261 all the drivers without unloading fbcon will make it impossible for the
262 console to bind fbcon.
270 won't get any display after detaching fbcon. Your machine is still alive, so
276 a. Before detaching fbcon, do::
281 b. Detach fbcon as in step 5.
283 c. Attach fbcon::
290 a. Before detaching fbcon, do::
298 b. Detach fbcon as in step 5.
300 c. Attach fbcon::
312 # Unbind fbcon
341 # Bind fbcon