DRM driver - Fedora(pinephone)
-
Hi!
I'm trying to get unity-system-compositor running on fedora rawhide for the pinephone. But it can't find the graphics driver.
The output is as follows:
[2020-07-14 07:12:00.243498] < -warning- > mesa-kms: Failed to detect whether device /dev/dri/card0 supports KMS, continuing with lower confidence
[2020-07-14 07:12:01.176468] <information> mirserver: Found graphics driver: mir:mesa-kms (version 1.7.2) Support priority: 128
[2020-07-14 07:12:01.176649] <information> mirserver: Found graphics driver: mir:wayland (version 1.7.2) Support priority: 0
[2020-07-14 07:12:01.185971] <information> mirserver: Found graphics driver: mir:mesa-x11 (version 1.7.2) Support priority: 0
[2020-07-14 07:12:01.187255] <information> mirserver: Selected driver: mir:mesa-kms (version 1.7.2)
[2020-07-14 07:12:01.189450] < -warning- > mesa-kms: Failed to detect whether device /dev/dri/card0 supports KMS, but continuing anyway
[2020-07-14 07:12:01.189602] <information> mesa-kms: Using DRM device /dev/dri/card0
[2020-07-14 07:12:01.190084] < -warning- > mesa-kms: Failed to detect whether device /dev/dri/card1 supports KMS, but continuing anyway
[2020-07-14 07:12:01.190189] <information> mesa-kms: Using DRM device /dev/dri/card1
ERROR: ../src/platforms/common/server/kms-utils/drm_mode_resources.cpp(41): Throw in function mir::graphics::kms::DRMModeResUPtr {anonymous}::resources_for_drm_node(int)
Dynamic exception type: boost::wrapexceptstd::system_error
std::exception::what: Couldn't get DRM resources: Operation not supportedCompare to the UT version...
[2020-07-14 13:24:46.198721] < -warning- > mesa-kms: Failed to detect whether device /dev/dri/card1 supports KMS, checking using fallback method
[2020-07-14 13:24:46.199004] <information> mesa-kms: Using DRM device /dev/dri/card1
[2020-07-14 13:24:46.202459] < -warning- > mesa-kms: Failed to detect whether device /dev/dri/card0 supports KMS, checking using fallback method
[2020-07-14 13:24:46.205636] <information> mesa-kms: Ignoring non-KMS DRM device /dev/dri/card0
[2020-07-14 13:24:46.656012] < - debug - > mesa-kms: No EDID data available on connector 50
[2020-07-14 13:24:46.659572] < -warning- > mesa-kms: Unable to determine the current display mode.
[2020-07-14 13:24:46.676697] <information> mesa-kms: DRM device details:
[2020-07-14 13:24:46.676959] <information> mesa-kms: /dev/dri/card1: using driver sun4i-drm [Allwinner sun4i Display Engine] (version: 1.0.0 driver date: 20150629)
[2020-07-14 13:24:46.677164] <information> mesa-kms: Output: DSI-1 (connected)
[2020-07-14 13:24:46.677261] <information> mesa-kms: Mode: 720×1440@55.31
[2020-07-14 13:24:46.677672] < -warning- > mesa-kms: drmModeCrtcSetGamma failed: Invalid argument
[2020-07-14 13:24:46.699166] <information> mesa-kms: Detected single-GPU DisplayBuffer. Rendering will be sent directly to output
[2020-07-14 13:24:47.161588] <information> mirserver: Using hardware cursorany ideas?
Is there a difference in the driver between megi's kernel and UT version? Or is there a difference between Mir 1.8.0(Fedora) and Mir 1.8.0 (UT)?
And why is the UT version writing "checking using fallback method" while fedora is writing ", but continuing anyway"
-
@erlend said in DRM driver - Fedora(pinephone):
And why is the UT version writing "checking using fallback method" while fedora is writing ", but continuing anyway"
That's down to getting a different error from
drmCheckModesetSupported(), so likely a kernel difference. -
Thank you, but I'm not so sure...
The Ubports version is changed compared to standard version... Particularly when it come to this function's return value... So I'm hoping the ubports change is what I need.
So I'm now trying to compile ubports version of mir... And the try it (but it's a lot to compile and there are include files missing)... So it takes a while....
So I try that first, before venturing into the kernel.
