Mir-kiosk on raspberry pi 3 in Jan 2018

1

I have been trying to get the mir-kiosk snap to run on a raspberry pi 3.
I’ve not had any success.

Here are the logs from journalctl -b

Jan 11 02:48:15 localhost.localdomain systemd[1]: Started User Manager for UID 1000.
Jan 11 02:48:15 localhost.localdomain mir-kiosk.mir-kiosk[1181]: [2018-01-11 02:48:15.651750] mirplatform: Found graphics driver: mir:mesa-kms (ver
Jan 11 02:48:15 localhost.localdomain mir-kiosk.mir-kiosk[1181]: [2018-01-11 02:48:15.742867] mirplatform: Found graphics driver: mir:mesa-x11 (ver
Jan 11 02:48:15 localhost.localdomain mir-kiosk.mir-kiosk[1181]: Unknown command line options: --vt 1
Jan 11 02:48:15 localhost.localdomain systemd[1]: snap.mir-kiosk.mir-kiosk.service: Main process exited, code=exited, status=1/FAILURE
Jan 11 02:48:15 localhost.localdomain systemd[1]: snap.mir-kiosk.mir-kiosk.service: Unit entered failed state.
Jan 11 02:48:15 localhost.localdomain systemd[1]: snap.mir-kiosk.mir-kiosk.service: Failed with result ‘exit-code’.

Is it possible that the error report that: Unknown command line options: --vt 1
is related to that fact that /dev/dri does not exist on my system.

These are the kernel modules. Here is the output from lsmod
Module Size Used by
nls_ascii 16384 1
hid_generic 16384 0
hid_apple 16384 0
usbhid 57344 0
hid 114688 3 hid_generic,usbhid,hid_apple
brcmfmac 282624 0
brcmutil 20480 1 brcmfmac
cfg80211 557056 1 brcmfmac
i2c_bcm2708 16384 0
bcm2835_gpiomem 16384 0
bcm2835_wdt 16384 0
uio_pdrv_genirq 16384 0
uio 20480 1 uio_pdrv_genirq

I thought that the vc4 kernel module was used on raspberry pi. In any case there is nothing located at /dev/dri

I have tried “modprobe vc4”, and then
snap disable mir-kiosk
snap enable mir-kiosk
but to no effect.

I have updated to edge on all my snaps.
Name Version Rev Developer Notes
classic 16.04 26 canonical devmode
core 16-2.30+git477.ccba80a 3852 canonical core
mir-kiosk 0.29.0 49 canonical devmode
pi2-kernel 4.4.0-1082.90 49 canonical kernel
pi3 16.04-0.5 22 canonical gadget

I am trying to figure out the kiosk mode for embedded IoT device.

Wendell Duncan

1 Like
2

does that mean that your image was originally not edge based ?

note that the bootloader binary bits and configs do not get updated if you update the gadget, so if you started from an image from the stable channel, the right dtb overlays and config settings for supporting vc4 will be missing. i’d suggest to try it on a clean edge image i.e. from http://cdimage.ubuntu.com/ubuntu-core/16/edge/current/

3

The results I posted were from an image that was not originally edge based.

I cannot get the current edge image from 3 Jan 2018 to boot. With the 2018-1-3 edge image, the bootloader starts and prints out some stuff. The last line printed is “Starting kernel …” and then my screen goes black. I am connected to the hdmi output.

I do have an qemu/kvm based virtual machine using the amd64 image. In my VM, everything is working.

4

I’ve narrowed down the problem a lot.

I have been attaching my raspberry pi to a DELL 4k monitor.
With the “stable” version of the ubuntu core image, it is able to drive that monitor.
The “edge” version of ubuntu core image does not seem to work with that monitor.

When I use a different monitor, I had success installing an ubuntu core “edge” image – and then was also able to get the mir-kiosk and mir-kiosk-apps working.