Build Ubuntu For i.MX8 Series Platform

Document created by Gnar Fang

on Jul 19, 2019•Last modified by Gnar Fang

on Aug 27, 2019

Version 3Show Document

Like • Show 3 Likes3
Comment • 19
View in full screen mode

The Guide is how to use Ubuntu filesystem with i.MX8 series platform.At present, I had try it on i.MX8QXP with 4.14.98 kernel with ubuntu16.04.

The Document will be continuously updated with enable VPU, ubuntu18.04. The desktop we can chose Gnome or weston. Because driver

support issue, gc7000 series gpu not support render Gnome destop but it can render weston destop.

Update 2019/7/31:

Ubuntu-i.MX8-weston.pdf

Feature:

weston + ubuntu18.04 + 4.14.98 kernel
VPU (enable with gplay or gst-play)
GPU (could render desktop and run GPU demo under root privileges)

I also try ubuntu with gnome desktop, ubuntu18.04 can not run gnome, need use ubuntu19.04. But Gnome's mutter need libgbm.so is

not match imx-gpu-viv libgbm. so can not run GPU at present.

3 people found this helpful

Attachments

Ubuntu-i.MX8.pdf201.8 KB
Ubuntu-i.MX8-weston.pdf177.1 KB

Outcomes

19 Comments

Amrit Soni Aug 16, 2019 7:00 AM
Hello Gnar,

Thank you for posting this detailed document. I was trying to follow it for nxp imx8m-mini evk. I have been able to build yocto for this board and that seems to work fine but now want to try ubuntu with weston on this evk. I have these questions for you in your Ubuntu-i.MX8-weston.pdf document.
In section 9 you write:
2)copy libdrm,wayland vpu-firmware from yocto
$sudo cp -Pra libdrm/2.4.91.imx-r0/image/* ubuntu18.04/
$sudo cp -Pra imx-gpu-viv/1_6.2.4.p4.0-aarch64-r0/image/* ubuntu18.04/
$sudo cp -Pra imx-dpu-g2d-1.7.0/imx-dpu-g2d/1.7.0-r0/image/* ubuntu18.04/
$sudo cp -r all-poky-linux/firmware-imx/1_8.1-r0/image/* ubuntu18.04/

Could you tell me from which folder (cd ~/????) you are running these commands? Also this folder ubuntu 18.04 does not exist anywhere, where does it get used later? I do not see any other reference to "ubuntu 18.04" folder in this document.

Is imx-dpu-g2d a typo, should it be imx-gpu-g2d ?

Also you say:
2.Compile the kernel separately to replace yocto kernel
Do you mean bitbake linux-imx after I have built yocto? Currently in the yocto build I do see that a kernel Image that has been built.

Thanks,
Amrit
Like • Show 0 Likes0
Actions
- Gnar Fang @ Amrit Soni on Aug 19, 2019 4:03 AM
  Hi, Amrit
  1.which folder (cd ~/????)
  The command run Host PC side. To build a ubuntu rootfs, decompression rootfs first such as tar -xvf ubuntu-base-18.04.2-base-arm64.tar.gz -C ubuntu-rootfs, in my case modify ubuntu-rootfs to ubuntu 18.04, May cause you misunderstand and I will uniform naming. This command purpose
  is copy libraries related GPU to ubuntu-rootfs.
  2.Compile the kernel separately
  Because the GPU dirver be builded as galcore.ko by yocto default. So compile the kernel separately to make Image include gpu dirver. In kernel source code(I download form linux-imx - i.MX Linux kernel , not use the yocto code), after command $ make menuconfig, you can see the .config
  CONFIG_MXC_GPU_VIV=y.
  
  BR
  Gnar
  Like • Show 0 Likes0
  Actions
Kyle_Fox Aug 26, 2019 2:56 PM
Hi Gnar,

i was curious whether you have tested a webcam with ubuntu and seen if it works? i'm struggling to get a simple logitech webcam to work. It looks like i'm getting a dmesg alert that "VPU_firmware_download Failed"... so i assume the VPU firmware is messed up.

maybe i copied in the wrong file at some point...

k
Like • Show 0 Likes0
Actions
- Gnar Fang @ Kyle_Fox on Aug 26, 2019 6:30 PM
  Hi, Kyle
  I am not test webcam but other one test it ok. I am not sure he do other config for it. If you webcam is usb camera, may should enable UVC driver in kernel. About VPU firmware, are you copy it under /lib/firmware ? You also can copy unit_test file form yocto, use v4l2 to open camera.
  
  BR
  Gnar
  Like • Show 0 Likes0
  Actions
  - Kyle_Fox @ Gnar Fang on Aug 27, 2019 8:12 AM
    Hi Gnar,
    
    I think i've gotten a bit confused on what specifically to copy. From your awesome manual (Ubuntu-imx8-weston.pdf)
    there are several commands here:
    2) copy libdrm, wayland, vpu-firmware from yocto
    $sudo cp -Pra libdrm/2.4.91.imx-r0/image/* ubuntu18.04/
    $sudo cp -Pra imx-gpu-viv/1_6.2.4.p4.0-aarch64-r0/image/* ubuntu18.04/
    $sudo cp -Pra imx-dpu-g2d-1.7.0/imx-dpu-g2d/1.7.0-ro/image/* ubuntu 18.04/
    $sudo cp -r all-poky-linux/firmware-imx/1_8.1-r0/image/* ubuntu18.04/
    
    What would help me is to understand the actual folder paths for each of them.
    My assumption is that you are copying from the Yocto build... could you give me the full paths to /libdrm/2.4.91.imx-ro/image/, /imx-gpu-viv/1_6.2.4.p4.0-aarch64-ro/image/, /imx-dpu-g2d-1.7.0/imx-dpu-g2d/1.7.0-ro/image/* and all-poky-linux/firmware-imx/1_8.1-r0/image/*
    
    2nd, when you point out the destination folder of 'ubuntu18.04/' do i assume that /ubuntu18.04/ is the base of the ubuntu rootfs?
    
    thanks
    
    kylef
    Like • Show 0 Likes0
    Actions
Amrit Soni Aug 27, 2019 8:51 AM
Hello Gnar and Kyle,

I am glad to see that more than one person is working on this project. First of all thank you Gnar for creating the documents and outlining the essential steps.

Kyle,
I also went through and located all folder that need to be copied from yocto build folders to ~/rootfs/ubuntu-rootfs (or ~/rootfs/ubuntu18.04). Here are the the source folder names in each case:

cd ~/imx-yocto-bsp/build/tmp/work/aarch64-mx8mm-poky-linux
sudo cp -Pra libdrm/2.4.91.imx-r0/image/* ~/rootfs/ubuntu-rootfs
sudo cp -Pra imx-gpu-viv/1_6.2.4.p4.0-aarch64-r0/image/* ~/rootfs/ubuntu-rootfs
sudo cp -Pra ~/imx-yocto-bsp/build/tmp/work/aarch64-mx8mm-poky-linux/imx-gpu-g2d/6.2.4.p4.0-r0/image/* ~/rootfs/ubuntu-rootfs

cd ~/imx-yocto-bsp/build/tmp/work
sudo cp -r all-poky-linux/firmware-imx/1_8.1-r0/image/* ~/rootfs/ubuntu-rootfs

In my case rootfs folder is ~/rootfs/ubuntu-rootfs.

Gnar,

I am able to run ubuntu18.04 in basic form with Gnome or xfce4 but still in the process of trying to put all the components in my rootfs. I noticed a weird error in step 3) for weston-imx.
Here is the error log, when I run autogen for weston-imx:

root@UB160401:~/weston/weston-imx# ./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking --enable-setuid-install --disable-rdp-compositor --enable-clients --enable-simple- clients --enable-demo-clients-install --disable-colord --enable-egl --enable- simple-egl-clients --enable-fbdev-compositor --disable-headless-compositor -- enable-drm-compositor --enable-weston-launch --disable-lcms --disable-libunwind --with-pam --disable-vaapi-recorder --enable-wayland-compositor --without-webp --disable-x11-compositor --disable-xwayland

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:35: installing 'build-aux/compile'
configure.ac:43: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
autoreconf: Leaving directory `.'
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: unrecognized options: --enable-simple-, --enable-
checking for clients-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether sys/types.h defines makedev... no
checking sys/mkdev.h usability... no
checking sys/mkdev.h presence... no
checking for sys/mkdev.h... no
checking sys/sysmacros.h usability... yes
checking sys/sysmacros.h presence... yes
checking for sys/sysmacros.h... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking whether make supports nested variables... yes
checking dependency style of gcc... none
checking whether make supports nested variables... (cached) yes
checking for clients-gcc... gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking for a sed that does not truncate output... /bin/sed
checking build system type... Invalid configuration `clients': machine `clients' not recognized
configure: error: /bin/bash build-aux/config.sub clients failed

Any clue what I may be missing?

BTW: I am using imx8m mini evk - yocto, but that should not make difference as far as these steps are concerned.

Thank you both.
Amrit
Like • Show 0 Likes0
Actions
- Gnar Fang @ Amrit Soni on Aug 27, 2019 10:33 PM
  Hi Amrit
  1. I am install gnome base ubuntu18.04 meet error on 8QXP but sucessful with ubuntu19.04. At present, gnome not support GPU and use the CPU to render the desktop,
  the performance is not very optimistic. so i am try debug GNOME to support GPU but it need some time.
  2. When you build weston-imx meet error. If you had install gnome or xfce4(BTW: it base on X11, 8 series GPU is only support wayland, but if use CPU to render desktop,
  xfce4 is better than gnome because gnome is more complex), please build weston-imx without it because some component of GNOME of xfce4 effect weston-imx build.
  if not,try use the command:
  #./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking --enable-setuid-install --disable-rdp-compositor --enable-clients --enable-simple-clients --enable-demo-clients-install --disable-colord --enable-egl --enable-simple-egl-clients --enable-fbdev-compositor --disable-headless-compositor --enable-drm-compositor --enable-weston-launch --disable-lcms --disable-libunwind --with-pam --disable-vaapi-recorder --enable-wayland-compositor --without-webp --disable-x11-compositor --enable-xwayland --enable-imxg2d --enable-imxgpu --enable-drm-compositor --enable-opengl
  3. I had not meet the err, you can reference :cross compiling - What's the difference of "./configure" option "--build", "--host" and "--target"? - Stack Overflow .
  BR
  Gnar
  Like • Show 0 Likes0
  Actions
  - Daniel Toussaint @ Gnar Fang on Sep 30, 2019 10:46 PM
    Hi Gnar Fang : The GPU can't render gnome because of limitations in the OpenGL library or is there another reason?
    Like • Show 0 Likes0
    Actions
    - Gnar Fang @ Daniel Toussaint on Oct 7, 2019 6:52 PM
      Yes, may GPU dirver not fit.
      Like • Show 0 Likes0
      Actions
Amrit Soni Aug 29, 2019 8:16 AM
Hello Gnar,

Thank you for your reply. I think I am now very close to building ubuntu after following your document.

I now have these remaining items.
1. I do not see anything called imx-dpu-2d in my yocto build folder. So I am not able to run this step in your document:
sudo cp -Pra imx-dpu-g2d-1.7.0/imx-dpu-g2d/1.7.0-r0/image/* ubuntu18.04/
My DISTRO is fsl-imx-xwayland and MACHINE is imx8mmevk

2.. I tried the new autogen step as you mentioned in your last post for weston-imx but it still does not build. I now get different errors during autogen step. Here is my log:
.........................
root@UB160401:~/weston/weston-imx# ./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking --enable-setuid-install --disable-rdp-compositor --enable-clients --enable-simple-clients --enable-demo-clients-install --disable-colord --enable-egl --enable-simple-egl-clients --enable-fbdev-compositor --disable-headless-compositor --enable-drm-compositor --enable-weston-launch --disable-lcms --disable-libunwind --with-pam --disable-vaapi-recorder --enable-wayland-compositor --without-webp --disable-x11-compositor --enable-xwayland --enable-imxg2d --enable-imxgpu --enable-drm-compositor --enable-opengl....
..................
.................

checking for OPENGL... yes
checking for GL_RENDERER... yes
checking for XKBCOMMON_COMPOSE... yes
checking for XWAYLAND... no
configure: error: Package requirements (xcb xcb-xfixes xcb-composite xcb-shape xcursor cairo-xcb) were not met:

No package 'xcb-xfixes' found
No package 'xcb-composite' found
No package 'xcb-shape' found
No package 'xcursor' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XWAYLAND_CFLAGS
and XWAYLAND_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

Any suggestions?

Thank you so much.
Amrit
Like • Show 0 Likes0
Actions
- Gnar Fang @ Amrit Soni on Sep 1, 2019 7:51 PM
  Hi,Anrit
  1. imx-dpu-2d path in yocto is /buildxwayland/tmp/work/aarch64-mx8mm-poky-linux/imx-gpu-g2d ,8MM have not DPU.
  2. back to first command:
  ./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking --enable-setuid-install --disable-rdp-compositor --enable-clients --enable-simple- clients --enable-demo-clients-install --disable-colord --enable-egl --enable- simple-egl-clients --enable-fbdev-compositor --disable-headless-compositor -- enable-drm-compositor --enable-weston-launch --disable-lcms --disable-libunwind --with-pam --disable-vaapi-recorder --enable-wayland-compositor --without-webp --disable-x11-compositor --disable-xwayland
  
  The error log is :
  1)configure: WARNING: you should use --build, --host, --target
  2)checking build system type... Invalid configuration `clients': machine `clients' not recognized
  
  Are you build in qemu enviroment ? I had not meet the error in my step and not set any enviroment variables. Try google how build weston, according to the log you need
  add the arguments about --build, --host, --target.
  The second command, try disable xwayland at first.
  
  The xwayland is not necessary.
  
  BR
  Gnar
  Like • Show 0 Likes0
  Actions
gao bo Sep 11, 2019 7:15 PM
First of all, thank you very much for your proposal。But i have a question that I hope you can help me with this。In Ubuntu-imx8.pdf setp 2 Compile the kernel separately to replace yocto kernel，Specifically which is kernel to replace yocto kernel?
thanks!
Like • Show 0 Likes0
Actions
- Gnar Fang @ gao bo on Sep 15, 2019 7:57 PM
  Hi, gao
  Because in default, GPU driver galcore is compiled as .ko file, so need compile the kernel separately to make galcore in kernel.
  
  BR
  Gnar
  Like • Show 0 Likes0
  Actions
  - gao bo @ Gnar Fang on Sep 15, 2019 11:07 PM
    thanks for your answer.Can you tell me how to compile the kernel separetely? I use fellowing methods make it ：
    bitbake -c compile -f -v linux-imx
    bitbake linux-imx -c compile_kernelmodules -f -v
    bitbake -c deploy -f -v linux-imx
    result：
    Compare with before：
    galcore used numbers different.and no have qca6174 driver.and a lot of drivers have been added。
    how to resolve it？
    Like • Show 0 Likes0
    Actions
    - Gnar Fang @ gao bo on Sep 19, 2019 6:29 PM
      Hi,
      
      A easy way is download linux-imx for linux-imx - i.MX Linux kernel , Then use command "$ make defconfig, $ make" to build Image .
      Use the Image replace your current Image.
      
      BR
      Gnar
      Like • Show 0 Likes0
      Actions
prashanth kumar Oct 15, 2019 7:06 AM
Hi,

I am also porting Ubuntu 18.04 to iMX8 Quad Max custom board with 4.14.98 BSP by referring https://community.nxp.com/servlet/JiveServlet/download/343939-3-454211/Ubuntu-i.MX8-weston.pdf Document.

Till section 9. copy imx-gpu-viv in mentioned document able to understand properly. But after section 10.build weston, its not saying that where need to build weston, wayland, gstreamer and gst-plugins? How to link/add above features with "ubuntu-rootfs" ?

Best Regards,
Prashanth Kumar K
Like • Show 0 Likes0
Actions
- Gnar Fang @ prashanth kumar on Oct 15, 2019 10:36 PM
  Hi
  Build weston in qemu enviroment.
  BR
  Gnar
  Like • Show 0 Likes0
  Actions
prashanth kumar Oct 17, 2019 10:07 PM
Hi Gnar,

During below make command execution I am getting following header file declaration error message for weston-imx.
From where we can get header files for weston?

#cd ~/weston
#git clone https://source.codeaurora.org/external/imx/weston-imx.git
#cd weston-imx
#git checkout fb563901657b296c7c7c86d26602a622429e334f
#./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking --enable-setuid-install --disable-rdp-compositor --enable-clients --enable-simple-clients --enable-demo-clients-install --disable-colord --enable-egl --enable-simple-egl-clients --enable-fbdev-compositor --disable-headless-compositor --enable-drm-compositor --enable-weston-launch --disable-lcms --disable-libunwind --with-pam--disable-vaapi-recorder --enable-wayland-compositor --without-webp --disable-x11-compositor --enable-xwayland --enable-imxg2d --enable-imxgpu --enable-drm-compositor --enable-opengl
#make
libweston/compositor-drm.c: In function ‘drm_fb_addfb’:
libweston/compositor-drm.c:962:23: error: ‘DRM_FORMAT_MOD_AMPHION_TILED’ undeclared (first use in this function); did you mean ‘DRM_FORMAT_MOD_VIVANTE_TILED’?
if (fb->modifier == DRM_FORMAT_MOD_AMPHION_TILED) {
DRM_FORMAT_MOD_VIVANTE_TILED
libweston/compositor-drm.c:962:23: note: each undeclared identifier is reported only once for each function it appears in
libweston/compositor-drm.c: In function ‘drm_clip_overlay_coordinate’:
libweston/compositor-drm.c:1518:36: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (state->dest_x + state->dest_w > output->base.current_mode->width){
^
libweston/compositor-drm.c:1526:36: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (state->dest_y + state->dest_h > output->base.current_mode->height){
^
libweston/compositor-drm.c: In function ‘drm_get_gbm_alignment’:
libweston/compositor-drm.c:2184:9: error: ‘DRM_FORMAT_MOD_VIVANTE_SUPER_TILED_FC’ undeclared (first use in this function); did you mean ‘DRM_FORMAT_MOD_VIVANTE_SUPER_TILED’?
case DRM_FORMAT_MOD_VIVANTE_SUPER_TILED_FC:
DRM_FORMAT_MOD_VIVANTE_SUPER_TILED
libweston/compositor-drm.c: In function ‘drm_output_apply_state_atomic’:
libweston/compositor-drm.c:2600:4: warning: implicit declaration of function ‘gbm_surface_set_sync_post’; did you mean ‘gbm_surface_destroy’? [-Wimplicit-function-declaration]
gbm_surface_set_sync_post(output->gbm_surface, 0);
gbm_surface_destroy
libweston/compositor-drm.c:2601:18: warning: implicit declaration of function ‘gbm_surface_get_in_fence_fd’; did you mean ‘wl_surface_send_enter’? [-Wimplicit-function-declaration]
in_fence_fd = gbm_surface_get_in_fence_fd(output->gbm_surface);
wl_surface_send_enter
libweston/compositor-drm.c: In function ‘drm_query_dmabuf_modifiers’:
libweston/compositor-drm.c:3291:49: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (p->formats[i].format != format)
libweston/compositor-drm.c: In function ‘drm_import_dmabuf’:
libweston/compositor-drm.c:3342:37: error: ‘DRM_FORMAT_P010’ undeclared (first use in this function); did you mean ‘DRM_FORMAT_R16’?
&& dmabuf->attributes.format == DRM_FORMAT_P010)
DRM_FORMAT_R16
libweston/compositor-drm.c: In function ‘drm_output_propose_state’:
libweston/compositor-drm.c:3752:38: error: ‘DRM_FORMAT_P010’ undeclared (first use in this function); did you mean ‘DRM_FORMAT_R16’?
|| dmabuf->attributes.format == DRM_FORMAT_P010
DRM_FORMAT_R16
libweston/compositor-drm.c: In function ‘hdr10_metadata_set_metadata’:
libweston/compositor-drm.c:7250:29: error: storage size of ‘hdr_metadata’ isn’t known
struct hdr_static_metadata hdr_metadata;

Best Regards,
Prashanth Kumar K
Like • Show 0 Likes0
Actions

Lorenzo Giraudi Oct 18, 2019 8:57 AM

Hi Gnar,

Thank you for sharing this procedure. I would like to ask you: what is the purpose of the commands "sudo mount -t proc /proc ${2}proc" and the others?
It bring us some problems on the host machines.

I also faced a problem about weston. I followed your procedure, but when i try to execute weston i get this:

sudo -E weston --tty=1
[sudo] password for user:
Date: 2019-10-18 UTC
[08:42:03.809] weston 5.0.0
               https://wayland.freedesktop.org
               Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
               Build: 5.0.0-33-gfb563901 MGS-4627 [#ccc] weston will turn off when panel-psotion=none and use gplay (2019-03-14 11:30:30 +0800)
[08:42:03.816] Command line: weston --tty=1
[08:42:03.816] OS: Linux, 4.14.98-imx_4.14.98_2.0.0_ga+g64ad07d, #1 SMP PREEMPT Tue Aug 13 13:06:25 UTC 2019, aarch64
[08:42:03.816] warning: XDG_RUNTIME_DIR "/run/user/1000" is not configured
correctly.  Unix access mode must be 0700 (current mode is 700),
and must be owned by the user (current owner is UID 1000).
Refer to your distribution on how to get it, or
http://www.freedesktop.org/wiki/Specifications/basedir-spec
on how to implement it.
[08:42:03.826] Starting with no config file.
[08:42:03.839] Output repaint window is 16 ms maximum.
[08:42:03.845] Loading module '/usr/lib/libweston-5/drm-backend.so'
[08:42:03.952] initializing drm backend
[08:42:03.955] using /dev/dri/card0
[08:42:03.955] DRM: supports universal planes
[08:42:03.955] DRM: supports atomic modesetting
[08:42:03.955] DRM: does not support picture aspect ratio
[08:42:03.960] Loading module '/usr/lib/libweston-5/gl-renderer.so'
[08:42:04.302] EGL client extensions: EGL_EXT_device_base
               EGL_EXT_device_enumeration EGL_EXT_device_query
               EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses
               EGL_EXT_client_extensions EGL_KHR_debug
               EGL_EXT_platform_wayland EGL_EXT_platform_x11
               EGL_MESA_platform_gbm EGL_MESA_platform_surfaceless
[08:42:04.304] failed to initialize display
[08:42:04.304] EGL error state: EGL_NOT_INITIALIZED (0x3001)
[08:42:04.304] failed to initialize egl
[08:42:04.341] fatal: failed to create compositor backend
Have you ever seen a similar error message? 
Thank you. 

Regards,
Lorenzo

Actions

Incoming Links

Re: imx8 with ubuntu ?

Build Ubuntu For i.MX8 Series Platform

Attachments

Outcomes

Related Content

Recommended Content

Incoming Links