1
Using Mir on a PC {#using_mir_on_pc}
7
Make sure your hardware is supported. That means you're using a Mesa driver,
8
of which intel, radeon, and nouveau families are supported. If you're logged
9
in to X then run this command to verify an appropriate DRI driver is active:
11
sudo pmap `pidof X` | grep dri.so
17
Before you can use Mir you need to ensure you have the proper custom Mesa
18
build installed. If you are running Ubuntu 13.10 or later
19
(see \ref installing_prebuilt_on_pc), you should be good to go.
21
If you built Mir from source code (see \ref building_source_for_pc), you
22
need to ensure you are using the proper Mesa at runtime. You can do that by
23
installing the Mesa packages from Ubuntu 13.10 (or later) or by building the
24
custom Mesa yourself and ensuring it can be found by Mir, e.g., by using
27
### Getting some example client applications
29
You can get some example programs by installing the `mir-demos` package:
31
$ sudo apt-get install mir-demos
33
If you are building from source you can find client applications in the `bin/`
34
subdirectory of the build directory.
39
Mir can run run either natively on mesa-kms or as an X application.
43
To run Mir as an X client start it from an X terminal:
45
$ mir_demo_server --launch-client mir_demo_client_multiwin
47
You can start additional Mir clients, for example (in a new terminal):
49
$ mir_demo_egltriangle
55
Note: up to Mir 0.18 it is also necessary to specify `--platform-input-lib` when
57
- for Mir-0.17 add: `--platform-input-lib server-mesa-x11.so.6`
58
- for Mir-0.18 add: `--platform-input-lib server-mesa-x11.so.7`
60
### Running Mir natively
62
To run Mir natively on a PC/desktop/laptop:
64
$ sudo DISPLAY= mir_demo_server --vt 1 --arw-file
66
This will switch you to a Mir session on VT1. Switch back to your X-based
73
$ mir_demo_client_multiwin -m /tmp/mir_socket
79
Watch your friends be amazed!
85
In case you accidentally killed your X login and ended up with a failsafe
86
screen, you might find on subsequent reboots you can't log in to X at all any
87
more (it instantly and silently takes you back to the login screen). The fix
88
for this is to log in to a VT and:
91
$ sudo restart lightdm