[kmscon-devel] kmscon giving a black screen, systemd thinks it's fine

[David Herrmann]

Hi

On Tue, May 6, 2014 at 5:58 PM, Timo Paulssen <timo at wakelift.de> wrote:
>>> failed to load module: /usr/lib64/gbm/gbm_gallium_drm.so: cannot
>>> open shared object file: no such file or directory ERROR:
>>> uterm_drm3d_video: cannot create gbm device for /dev/dri/card0
>>> (permission denied) (video_init() in src/uterm_drm3d_video.c:436)
>>> ERROR: video_drm2d: driver does not support dumb buffers
>>> (video_init() in src/uterm_drm2d_video.c:335)
>>
>> Please try using --no-hwaccel and --no-drm to make it work with the
>> proprietary nvidia driver.
>
> Until I try this, is there a way to detect that the screen is not properly
> being rendered and exit kmscon with a failure exit code, so that agetty can
> properly be run as a fallback by systemd?

Errors are often not reliable, so reacting to them might break
existing setups (given that we know _nothing_ about the nvidia binary
blob that we're interacting with). Thus, I'm not really happy with
aborting kmscon if something might be wrong. Moreover, most rendering
problems aren't detectable at all, so we cannot deal with them,
anyway.

Thanks
David