Mir can't start if KMS is disabled (nomodeset kernel parameter)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Triaged
|
Medium
|
Unassigned | ||
mir (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Mir can't start if KMS is disabled (nomodeset kernel parameter).
The nomodeset option is used to diagnose kernel graphics problems and gives you a simple framebuffer instead. Xorg can deal with this and still works in low resolution, but Mir cannot even start under such conditions yet:
$ sudo mir_demo_server
[2016-08-15 11:48:43.120823] mirplatform: Found graphics driver: mir:mesa-kms (version 0.23.5)
[2016-08-15 11:48:43.120874] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.23.5)
[2016-08-15 11:48:43.121189] mirserver: Starting
[2016-08-15 11:48:43.121274] mircommon: Loading modules from: /usr/lib/
[2016-08-15 11:48:43.121302] mircommon: Loading module: /usr/lib/
[2016-08-15 11:48:43.121459] mircommon: Loading module: /usr/lib/
[2016-08-15 11:48:43.121714] mircommon: Loading module: /usr/lib/
[2016-08-15 11:48:43.122199] mirplatform: Found graphics driver: mir:mesa-kms (version 0.23.5)
[2016-08-15 11:48:43.122228] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.23.5)
ERROR: /build/
Dynamic exception type: boost::
std::exception:
ERROR: /build/
Dynamic exception type: boost::
std::exception:
Related: https:/
Changed in mir: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Syncing task from Mir.