Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
International Rescue Committe

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 71 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       The  directfbrc  file  is a configuration file read by all
       DirectFB applications on startup.  There are two of these:
       a system-wide one stored in /etc/directfbrc and a per-user
       $HOME/.directfbrc which may override system settings.

       The same parameters that can be  used  in  the  directfbrc
       file  can  also  be passed to DirectFB applications on the
       command-line by prefixing them with --dfb:


       The directfbrc file contains one parameter per line.  Com­
       ments  are  introduced  by  a  hash sign (#), and continue
       until the end of the line.  Blank lines are ignored.

       Most parameters are switches that turn certain features on
       or  off.   These switches have a no- variant that disables
       the feature. This man-page describes the positive  variant
       and  will  also  note  which  setting  is  the compiled-in


       The following parameters may be specified in the  directf­
       brc file:

              Specifies  the  graphics system to use. The default
              is to use the Linux frame buffer  (fbdev)  but  you
              can  also  run  DirectFB applications on SDL (sdl).
              Other systems might be added in the future.

              Opens the given  frame  buffer  device  instead  of

              Sets  the default screen resolution. If unspecified
              DirectFB will use the first mode from /etc/fb.modes
              Some  frame  buffer  devices  (namely vesafb) don't
              support mode switches and can only be used  in  the
              resolution that is set on boot time.

              Sets the default pixel format. This is  similar  to
              the depth parameter described above but allows more
              fine-grained control. Possible values for pixelfor­
              mat  are LUT8, RGB332, RGB16, RGB24 and RGB32. Some
              drivers may also support the more exotic pixel for­
              mats A8, ARGB, ARGB1555, I420, UYVY, YUY2 and YV12.

       quiet  Suppresses console output from DirectFB. Only error
              messages will be displayed.

              Enables  the  output  of  the  DirectFB  banner  at
              startup. This is on by default.

              Enables debug output. This is on by default but you
              won't  see  any  debug  output  unless you compiled
              DirectFB with debugging support.

              Forces the primary surface to  be  a  window.  This
              allows  to run applications that were written to do
              full-screen access in a window.

              Turns hardware acceleration on. By default hardware
              acceleration is auto-detected. If you disable hard­
              ware acceleration, the  driver  for  your  graphics
              card  will still be loaded and used to access addi­
              tional display layers (if there are any),  but  all
              graphics  operations will be performed by the soft­
              ware renderer.

              Flushes  all  disk  buffers   before   initializing
              DirectFB.  This  can  be useful if you working with
              experimental device drivers and expect crashes. The
              default is not to sync.

              The no-mmx options allows to disable the use of MMX
              routines even if support for MMX was  detected.  By
              default MMX is used if is available and support for
              MMX was compiled in.
              DirectFB  engine  before  quitting the application.
              Use this option to enable/disable this feature.

              As described with the sighandler  option,  DirectFB
              installs  a signal handler for a number of signals.
              By using this option you may specify a list of sig­
              nals that shouldn't be handled this way.

              By  default  DirectFB checks if the application has
              released all allocated resources  on  exit.  If  it
              didn't,  it  will  clean  up after the application.
              This option allows to switch  this  feature  on  or

              This option activates blocking of all signals, use­
              ful for DirectFB daemons (a DirectFB master  appli­
              cation  that does nothing except being the master).

              By default DirectFB allocates a new virtual  termi­
              nal and switches to it.

              Allow    to    switch   virtual   terminals   using
              <Ctrl>+<Alt>+<F?>. This is an experimental  feature
              that is usually disabled; use at your own risk.

              Puts  the virtual terminal into graphics mode. This
              has the advantage that kernel messages  won't  show
              up on your screen while the DirectFB application is

              Usually DirectFB compresses  mouse  motion  events.
              This means that subsequent mouse motions are deliv­
              ered to the application as a  single  mouse  motion
              event.  This  leads  to  a more responsive but less
              exact mouse handling.

              three button mice.

              The  different  protocols  for  serial   mice   are
              described in more detail in mouse(4).

              Swaps  left  and  right  mouse  buttons. Useful for

              Map the CapsLock key to Meta. Useful for  users  of
              the  builtin  WM without a Meta key on the keyboard
              (e.g. Window key).

              By default DirectFB shows a mouse  cursor  when  an
              application  makes  use  of  windows.  This options
              allows to switch the cursor off. Note that applica­
              tions may nevertheless switch it on explicitly.

              Suppress loading of this module. The module name is
              the filename without the  libdirectfb_  prefix  and
              without  extension (for example keyboard to disable
              loading of the keyboard input module).

              Completely disables  background  handling.  Doesn't
              make  much sense since the mouse and moving windows
              will leave ugly traces on the background.

              Controls the color of the background. The color  is
              specified  in hexadecimal notation. The alpha value
              defaults to full opacity and may  be  omitted.  For
              example  to  choose  a  bright  magenta background,
              you'd use bg-color=FF00FF.

              Fills the background with the given image file. The
              image is stretched to fit to the screen dimensions.

              Like bg-image but tiles the image  to  fit  to  the

              Controls  the  signal  produced by the TV output of
              Matrox cards.

              Some older Matrox G400 cards have SGRAM and a  num­
              ber  of graphics operations are considerably faster
              on these cards if this feature  is  enabled.  Don't
              try to enable it if your card doesn't have SGRAM!

              If  you have a dual head G400/G450/G550 you can use
              this option to enable additional layers  using  the
              second head.

              If specified DirectFB will dump the screen contents
              in PPM format into this directory when the  <Print>
              key gets pressed.

              Allows to specify a second frame buffer device that
              is used to display how surface memory is  allocated
              on  the video card. This is highly experimental and
              only useful for debugging.

              Allows to control where window surfaces are stored.
              Supported values for <policy> are:

              auto  DirectFB  decides depending on hardware capa­
              bilities. This is the default.

              videohigh Swapping system/video with high priority.

              videolow Swapping system/video with low priority.

              systemonly  Window  surfaces  are  stored in system

              videoonly Window surfaces are stored in video  mem­

              Supported values for <mode> are:

              auto  DirectFB  decides depending on hardware capa­
              bilities. This is the default. DirectFB  chooses  a
              back  buffer  in  video memory if the hardware sup­
              ports simple blitting (copying from back  to  front
              buffer). If there's no acceleration at all the back
              buffer is allocated in  system  memory  since  that
              gives  much  better  performance  for alpha blended
              recomposition in software and avoids  reading  from
              the  video  memory when the result is copied to the
              front buffer.

              backsystem The back buffer is allocated  in  system
              memory.  This is the recommend choice if your hard­
              ware supports simple blitting but no alpha blending
              and  you  are going to have many alpha blended win­

              backvideo Front and back buffer  are  allocated  in
              video  memory.  It's  not required to set this mode
              explicitly because the 'auto' mode  chooses  it  if
              blits  are  accelerated.  Without accelerated blits
              this mode is not recommended.

              frontonly There is no back buffer. This is the best
              choice  if  you  are  using opaque windows only and
              don't use any color keying.

              Wait for the vertical retrace after  flipping.  The
              default is to wait before doing the flip.

              Disables polling for vertical retrace.


       Here  are  some examples that demonstrates how the parame­
       ters described above are passed to DirectFB application on
       the command-line.

       df_neo --dfb:no-hardware
              Starts df_neo without hardware acceleration.

       df_neo --dfb:help
              Lists  the  DirectFB  options that can be passed to
              system-wide DirectFB configuration file

              per-user DirectFB configuration file

              frame buffer modes file


       fb.modes(5), fbset(8), mouse(4), ppm(5)

Version 0.9.16             23 May 2002              DIRECTFBRC(5)
Help us cut cost by not downloading the whole site!
Use of automated download sofware ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and therefore is expressedly prohibited. For more details on this, take a look here



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can help in many different ways.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.07 Seconds