Announcement

Collapse
No announcement yet.

Intel SNA vs. Modesetting GLAMOR - DDX Benchmarks

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    xorg.0.log most likely.

    Comment


    • #22
      What about Ivy Bridge?
      Anyone has tried modesetting? Is it even available?

      Comment


      • #23
        Originally posted by TeoLinuX View Post
        What about Ivy Bridge?
        Anyone has tried modesetting? Is it even available?
        Your distribution has to package and ship it. ON Debian, for example, it is bundled in the xserver-xorg-core package.

        To verify, your Xorg log should look like:

        Code:
        [    45.641] (==) Matched intel as autoconfigured driver 0
        [    45.641] (==) Matched intel as autoconfigured driver 1
        [    45.641] (==) Matched modesetting as autoconfigured driver 2
        [    45.641] (==) Matched fbdev as autoconfigured driver 3
        [    45.641] (==) Matched vesa as autoconfigured driver 4
        [    45.641] (==) Assigned the driver to the xf86ConfigLayout
        [    45.641] (II) LoadModule: "intel"
        [    45.641] (WW) Warning, couldn't open module intel
        [    45.641] (II) UnloadModule: "intel"
        [    45.641] (II) Unloading intel
        [    45.641] (EE) Failed to load module "intel" (module does not exist, 0)
        [    45.641] (II) LoadModule: "modesetting"
        [    45.641] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
        [    45.641] (II) Module modesetting: vendor="X.Org Foundation"
        [    45.641]    compiled for 1.18.3, module version = 1.18.3
        [    45.641]    Module class: X.Org Video Driver
        [    45.641]    ABI class: X.Org Video Driver, version 20.0
        [    45.641] (II) LoadModule: "fbdev"
        [    45.641] (WW) Warning, couldn't open module fbdev
        [    45.641] (II) UnloadModule: "fbdev"
        [    45.641] (II) Unloading fbdev
        [    45.641] (EE) Failed to load module "fbdev" (module does not exist, 0)
        [    45.641] (II) LoadModule: "vesa"
        [    45.641] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
        [    45.641] (II) Module vesa: vendor="X.Org Foundation"
        [    45.641]    compiled for 1.18.0, module version = 2.3.4
        [    45.641]    Module class: X.Org Video Driver
        [    45.641]    ABI class: X.Org Video Driver, version 20.0
        [    45.641] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
        [    45.641] (II) VESA: driver for VESA chipsets: vesa
        [    45.641] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
        [    45.641] (II) modeset(0): using drv /dev/dri/card0
        [    45.641] (WW) Falling back to old probe method for vesa
        [    45.641] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
        [    45.641] (II) modeset(0): Creating default Display subsection in Screen section
                "Default Screen Section" for depth/fbbpp 24/32
        [    45.641] (==) modeset(0): Depth 24, (==) framebuffer bpp 32

        IIRC, the biggest benefit with modesetting driver is the following:

        Code:
        [email protected]:~$ ps aux | grep Xorg
        rrs       3165  0.3  1.4 420616 117212 tty2    S+   Jun17  14:56 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
        rrs      30444  0.0  0.0  12752  2168 pts/3    S+   18:37   0:00 grep --color=auto Xorg
        2016-06-20 / 18:37:37 ♒♒♒  ☺

        Comment

        Working...
        X