Lines Matching refs:fbcon
4 The framebuffer console (fbcon), as its name implies, is a text
13 What are the features of fbcon? The framebuffer console supports
24 module will be fbcon.
26 In order for fbcon to activate, at least one framebuffer driver is
50 1. Driver and fbcon are compiled statically
52 Usually, fbcon will automatically take over your console. The notable
56 2. Driver is compiled statically, fbcon is compiled as a module
60 do a 'modprobe fbcon'.
62 3. Driver is compiled as a module, fbcon is compiled statically
65 'modprobe xxxfb', fbcon automatically takes over the console with
66 the possible exception of using the fbcon=map:n option. See below.
68 4. Driver and fbcon are compiled as a module.
70 You can load them in any order. Once both are loaded, fbcon will take
78 1. fbcon=font:<name>
87 2. fbcon=scrollback:<value>[k]
95 3. fbcon=map:<0123>
110 available, fb0, adding fbcon=map:1 tells fbcon not to take over the
116 4. fbcon=vc:<n1>-<n2>
118 This option tells fbcon to take over only a range of consoles as
127 4. fbcon=rotate:<n>
139 /sys/class/graphics/fbcon:
152 5. fbcon=margin:<color>
159 6. fbcon=nodefer
161 If the kernel is compiled with deferred fbcon takeover support, normally
164 This option causes fbcon to bind immediately to the fbdev device.
181 This is more complicated in the case of the framebuffer console (fbcon),
182 because fbcon is an intermediate layer between the console and the drivers:
184 console ---> fbcon ---> fbdev drivers ---> hardware
186 The fbdev drivers cannot be unloaded if bound to fbcon, and fbcon cannot
189 So to unload the fbdev drivers, one must first unbind fbcon from the console,
190 then unbind the fbdev drivers from fbcon. Fortunately, unbinding fbcon from
192 fbcon. Thus, there is no need to explicitly unbind the fbdev drivers from
193 fbcon.
195 So, how do we unbind fbcon from the console? Part of the answer is in
199 driver. So assuming vtcon1 represents fbcon, then:
206 If fbcon is detached from the console layer, your boot console driver (which is
208 restore VGA text mode for you. With the rest, before detaching fbcon, you
226 4. If fbcon is compiled as a module, load fbcon by doing:
228 modprobe fbcon
230 5. Now to detach fbcon:
235 6. That's it, you're back to VGA mode. And if you compiled fbcon as a module,
236 you can unload it by 'rmmod fbcon'.
238 7. To reattach fbcon:
242 8. Once fbcon is unbound, all drivers registered to the system will also
243 become unbound. This means that fbcon and individual framebuffer drivers
244 can be unloaded or reloaded at will. Reloading the drivers or fbcon will
245 automatically bind the console, fbcon and the drivers together. Unloading
246 all the drivers without unloading fbcon will make it impossible for the
247 console to bind fbcon.
255 won't get any display after detaching fbcon. Your machine is still alive, so
261 a. Before detaching fbcon, do
266 b. Detach fbcon as in step 5.
268 c. Attach fbcon
275 a. Before detaching fbcon, do:
283 b. Detach fbcon as in step 5.
285 c. Attach fbcon:
298 # Unbind fbcon
324 # Bind fbcon