{
    "mode": "man",
    "parameter": "modesetting",
    "section": "4",
    "url": "https://www.chedong.com/phpMan.php/man/modesetting/4/json",
    "generated": "2026-10-05T16:30:56Z",
    "synopsis": "",
    "sections": {
        "NAME": {
            "content": "modesetting - video driver for framebuffer device\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "",
            "subsections": [
                {
                    "name": "Section \"Device\"",
                    "content": "Identifier \"devname\"\nDriver \"modesetting\"\nBusID  \"pci:bus:dev:func\"\n..."
                },
                {
                    "name": "EndSection",
                    "content": ""
                }
            ]
        },
        "DESCRIPTION": {
            "content": "modesetting  is  an  Xorg  driver for KMS devices.  This driver supports TrueColor visuals at\nframebuffer depths of 15, 16, 24, and 30. RandR 1.2 is supported  for  multi-head  configura‐\ntions. Acceleration is available through glamor for devices supporting at least OpenGL ES 2.0\nor OpenGL 2.1.  If glamor is not enabled, a shadow framebuffer is configured based on the KMS\ndrivers'  preference  (unless  the framebuffer is 24 bits per pixel, in which case the shadow\nframebuffer is always used).\n",
            "subsections": []
        },
        "SUPPORTED HARDWARE": {
            "content": "The modesetting driver supports all hardware where a KMS driver  is  available.   modesetting\nuses the Linux DRM KMS ioctls and dumb object create/map.\n",
            "subsections": []
        },
        "CONFIGURATION DETAILS": {
            "content": "Please  refer  to  xorg.conf(5)  for general configuration details.  This section only covers\nconfiguration details specific to this driver.\n\nFor this driver it is not required to specify modes in the screen section of the config file.\nThe modesetting driver can pick up the currently used video mode from the kernel  driver  and\nwill use it if there are no video modes configured.\n\nFor  PCI  boards  you  might have to add a BusID line to the Device section.  See above for a\nsample line.\n\nThe following driver Options are supported:\n\nOption \"SWcursor\" \"boolean\"\nSelects software cursor.  The default is off.\n\nOption \"kmsdev\" \"string\"\nThe framebuffer device to use. Default: /dev/dri/card0.\n\nOption \"ShadowFB\" \"boolean\"\nEnable or disable use of the shadow framebuffer layer.  Default: on.\n\nOption \"DoubleShadow\" \"boolean\"\nDouble-buffer shadow updates. When enabled, the driver will keep  two  copies  of  the\nshadow  framebuffer.  When the shadow framebuffer is flushed, the old and new versions\nof the shadow are compared, and only tiles that have actually changed are uploaded  to\nthe  device. This is an optimization for server-class GPUs with a remote display func‐\ntion (typically VNC), where remote updates are triggered by any framebuffer write,  so\nminimizing  the  amount of data uploaded is crucial.  This defaults to enabled for AS‐\nPEED and Matrox G200 devices, and disabled otherwise.\n\nOption \"AccelMethod\" \"string\"\nOne of \"glamor\" or \"none\".  Default: glamor.\n\nOption \"PageFlip\" \"boolean\"\nEnable DRI3 page flipping.  The default is on.\n\nOption \"VariableRefresh\" \"boolean\"\nEnables support for enabling variable refresh on the Screen's CRTCs when  an  suitable\napplication is flipping via the Present extension.\nThe default is off.\n\nOption \"AsyncFlipSecondaries\" \"boolean\"\nUse  async  flips for secondary video outputs on multi-display setups. If a screen has\nmultiple displays attached and DRI3 page flipping is used, then only one of  the  dis‐\nplays  will have its page flip synchronized to vblank for tear-free presentation. This\nis the display that is used for presentation timing and timestamping, usually the  one\ncovering  the  biggest  pixel  area of the screen.  All other displays (\"Secondaries\")\nwill not synchronize their flips. This may cause some tearing on these  displays,  but\nit prevents a permanent or periodic slowdown or irritating judder of animations if not\nall  video  outputs are running synchronized with each other and with the same refresh\nrate. There is no perfect solution apart from perfectly synchronized outputs, but this\noption may give preferrable results if the displays in a multi-display setup mirror or\nclone each other.  The default is off.\n\nOption \"ZaphodHeads\" \"string\"\nSpecify the RandR output(s) to use with zaphod mode for a particular driver  instance.\nIf you use this option you must use this option for all instances of the driver.\nFor  example:  Option  \"ZaphodHeads\"  \"LVDS,VGA-0\" will assign xrandr outputs LVDS and\nVGA-0 to this instance of the driver.\n\nOption \"UseGammaLUT\" \"boolean\"\nEnable or disable use of the GAMMALUT property, when available.  When  enabled,  this\noption  allows  the  driver  to use gamma ramps with more entries, if supported by the\nkernel. By default, GAMMALUT will be used for kms drivers which are known to be  safe\nfor use of GAMMALUT.\n\nSEE ALSO\nXorg(1), xorg.conf(5), Xserver(1), X(7)\n",
            "subsections": []
        },
        "AUTHORS": {
            "content": "Authors include: Dave Airlie\n\nX Version 11                             xorg-server 21.1.11                          MODESETTING(4)",
            "subsections": []
        }
    },
    "summary": "modesetting - video driver for framebuffer device",
    "flags": [],
    "examples": [],
    "see_also": []
}