• Home
  • Categories
  • WIKI
  • LANGUAGE: en
    • I have a problem installing my graphics card
    Community Discussion 1327 views · 3 replies ·
    Tofloor
    poster avatar
    emma
    deepin
    2018-04-11 14:08
    Author
    hi guys
    I installed deepin today,but i can't fix intel graphics card!
    i download "intel-gpu-tools-1.21" From https://01.org/linuxgraphics/ site and Extract file in Desktop


    But I don't know how to install it...

    README  File:
    1. Intel GPU Tools
    2. ===============

    4. Description
    5. -----------

    7. Intel GPU Tools is a collection of tools for development and testing of the
    8. Intel DRM driver. There are many macro-level test suites that get used against
    9. the driver, including xtest, rendercheck, piglit, and oglconform, but failures
    10. from those can be difficult to track down to kernel changes, and many require
    11. complicated build procedures or specific testing environments to get useful
    12. results. Therefore, Intel GPU Tools includes low-level tools and tests
    13. specifically for development and testing of the Intel DRM Driver.

    15. Intel GPU Tools is split into several sections:

    17. benchmarks/
    18.         This is a collection of useful microbenchmarks that can be used to tune
    19.         DRM code in relevant ways.

    21.         The benchmarks require KMS to be enabled.  When run with an X Server
    22.         running, they must be run as root to avoid the authentication
    23.         requirement.

    25.         Note that a few other microbenchmarks are in tests (like gem_gtt_speed).

    27. tests/
    28.         This is a set of automated tests to run against the DRM to validate
    29.         changes. Many of the tests have subtests, which can be listed by using
    30.         the --list-subtests command line option and then run using the
    31.         --run-subtest option. If --run-subtest is not used, all subtests will
    32.         be run. Some tests have futher options and these are detailed by using
    33.         the --help option.

    35.         The test suite can be run using the run-tests.sh script available in
    36.         the scripts directory. Piglit is used to run the tests and can either
    37.         be installed from your distribution (if available), or can be
    38.         downloaded locally for use with the script by running:

    40.         ./scripts/run-tests.sh -d

    42.         run-tests.sh has options for filtering and excluding tests from test
    43.         runs:

    45.           -t       only include tests that match the regular expression
    46.           -x       exclude tests that match the regular expression

    48.         Useful patterns for test filtering are described in the API
    49.         documentation and the full list of tests and subtests can be produced
    50.         by passing -l to the run-tests.sh script.

    52.         Results are written to a JSON file and an HTML summary can also be
    53.         created by passing -s to the run-tests.sh script. Further options are
    54.         are detailed by using the -h option.


    57.         If not using the script, piglit can be obtained from:

    59.         git://anongit.freedesktop.org/piglit

    61.         There is no need to build and install piglit if it is only going to be
    62.         used for running i-g-t tests.

    64.         Set the IGT_TEST_ROOT environment variable to point to the tests
    65.         directory, or set the path key in the "igt" section of piglit.conf to
    66.         the intel-gpu-tools root directory.

    68.         The tests in the i-g-t sources need to have been built already. Then we
    69.         can run the testcases with (as usual as root, no other drm clients
    70.         running):

    72.         piglit-sources # ./piglit run igt

    74.         The testlist is built at runtime, so no need to update anything in
    75.         piglit when adding new tests. See

    77.         piglit-sources $ ./piglit run -h

    79.         for some useful options.

    81.         Piglit only runs a default set of tests and is useful for regression
    82.         testing. Other tests not run are:
    83.         - tests that might hang the gpu, see HANG in Makefile.am
    84.         - gem_stress, a stress test suite. Look at the source for all the
    85.           various options.
    86.         - testdisplay is only run in the default mode. testdisplay has tons of
    87.           options to test different kms functionality, again read the source for
    88.           the details.

    90. lib/
    91.         Common helper functions and headers used by the other tools.

    93. man/
    94.         Manpages, unfortunately rather incomplete.

    96. tools/
    97.         This is a collection of debugging tools that had previously been
    98.         built with the 2D driver but not shipped.  Some distros were hacking
    99.         up the 2D build to ship them.  Instead, here's a separate package for
    100.         people debugging the driver.

    102.         These tools generally must be run as root, safe for the ones that just
    103.         decode dumps.

    105. debugger/
    106.         This tool is to be used to do shader debugging. It acts like a
    107.         debug server accepting connections from debug clients such as
    108.         mesa. The connections is made with unix domain sockets, and at some
    109.         point it would be nice if this directory contained a library for
    110.         initiating connections with debug clients..

    112.         The debugger must be run as root: "sudo debugger/eudb"

    114. docs/
    115.         Contains the automatically generated intel-gpu-tools libraries
    116.         reference documentation in docs/reference/. You need to have the
    117.         gtk-doc tools installed and use the "--enable-gtk-doc" configure flag
    118.         to generate this API documentation.

    120.         To regenerate the html files when updating documentation, use:

    122.         $ make clean -C docs && make -C docs

    124.         If you've added/changed/removed a symbol or anything else that changes
    125.         the overall structure or indexes, this needs to be reflected in
    126.         intel-gpu-tools-sections.txt. Entirely new sections will also need to be
    127.         added to intel-gpu-tools-docs.xml in the appropriate place.

    129. include/drm-uapi
    130.         Imported DRM uapi headers from airlied's drm-next branch.
    131.         These should be updated all together by executing "make
    132.         headers_install" from that branch of the kernel and then
    133.         copying the resulting ./usr/include/drm/*.h in and committing
    134.         with a note of which commit on airlied's branch was used to
    135.         generate them.


    138. Requirements
    139. ------------

    141. This is a non-exhaustive list of package dependencies required for building
    142. the default configuration (package names may vary):

    144.         gtk-doc-tools
    145.         libcairo2-dev
    146.         libdrm-dev
    147.         libkmod-dev
    148.         libpciaccess-dev
    149.         libprocps-dev
    150.         libunwind-dev
    151.         python-docutils
    152.         x11proto-dri2-dev
    153.         xutils-dev

    155. The following dependencies are required for building chamelium support
    156. (package names may vary):

    158.         libxmlrpc-core-c3-dev
    159.         libpixman-1-dev
    160.         libudev-dev
    161.         libglib2.0-dev
    162.         libgsl-dev

    164. The following dependencies are requires for building audio support
    165. (package names may vary):

    167.         libasound2-dev
    168.         libgsl-dev

    170. Meson build system support
    171. --------------------------

    173. Currently we support both meson and automake as build systems, but meson is the
    174. recommended choice. Oneliner to get started:

    176. $ mkdir build && meson build && cd build && ninja

    178. Note that meson insist on separate build directories from the source tree.

    180. Running testcases is done with

    182. $ cd build && ninja test

    184. Documentation is built using

    186. $ cd build && ninja && ninja intel-gpu-tools-doc

    188. Note that there's a setup script similar to ./autogen.sh which creates a
    189. compatibility Makefile with a few useful default targets:

    191. $ ./meson.sh [make-arguments]

    193. Releases for maintainers
    194. ------------------------

    196. (1.14)

    198. http://www.x.org/wiki/Development/Documentation/ReleaseHOWTO/
    Copy the Code

    Reply Favorite View the author
    All Replies
    oscararg
    deepin
    2018-04-11 15:11
    #1
    My doubt here is why you want to install that, as Intel processors' integrated cards are supported by Deepin without installing any extra package. And, as an advice, Intel is leaving all their apps for linux, not bad news anyways, because kernels comes with good support of Intel products, thats why Intel guys are leaving those apps who not too much people use and can be replaced with kernel updates.
    Reply View the author
    emma
    deepin
    2018-04-11 17:40
    #2
    https://bbs.deepin.org/post/155216
    My doubt here is why you want to install that, as Intel processors' integrated cards are supported b ...

    Thank you for answering
    There is a problem scrolling the image and browser and watch movies
    How to know if the graphics card is installed?
    Reply View the author
    oscararg
    deepin
    2018-04-12 14:39
    #3
    https://bbs.deepin.org/post/155216
    Thank you for answering
    There is a problem scrolling the image and browser and watch movies
    How to ...

    sudo apt update && sudo apt install i-nex, with this app you must see all of your pc's devices, even graphics card. There is a "Deepin Graphics Drivers Utility" in Deepin Store too. It must show to you the best graphic driver available, but if you use only Intel's integrated one, it doesn't need any extra drivers, so the problem must radicate in the browser, try using (only for testing) another one, a light one, like Min or Midori, to check if the problem is on all browsers or (I suppose you're using Chrome), Chrome based (this can be a flash problem).
    Reply View the author