Hi Mathieu, Sorry I don't work with QtWebEngine module. It's not available on my working version (Qt 5.6.3).
Type this commands before execute your application : export QT_LOGGING_RULES=*=true export QSG_INFO=1 export QT_QPA_EGLFS_DEBUG=1 export QT_DEBUG_PLUGINS=1 May be you'll have more informations for your problem. Good luck, Best regards, Rémi A. Le mercredi 19 juin 2019 14:40:53 UTC+2, [email protected] a écrit : > > Hi Everyone, > > I want to test whether 2D acceleration makes QtWebEngine (Chromium) > reactive enough on the BBB. > I tried Rémi's procedure, and I can run the OGLES2 demos and kmscube. > However, when I try to use a QWebEngineView in a Qt application, I get a > segmentation fault (other Qt apps are fine). > > I checked with ldd that my app is linked with libgbm2 and not libgbm1, so > that does not seem to be the problem. > > Has anyone tried QtWebEngine with this setup? Could it be that the debian > package for QtWebEngine is incompatible? > > Best regards, > Mathieu > > Le jeudi 2 mai 2019 15:05:28 UTC+2, [email protected] a écrit : >> >> Hi Bora, >> >> Thank you very much for your feedback. I am very happy to know that my >> article was able to help you! >> >> Best regards, >> Rémi >> >> Le mercredi 1 mai 2019 03:07:08 UTC+2, Bora a écrit : >>> >>> Hey Remi, >>> >>> I believe you solved this issue since you already posted this article in >>> the wiki: >>> >>> https://elinux.org/BeagleBoneBlack/SGX_%2B_Qt_EGLFS_%2B_Weston >>> >>> I used your article to enable EGLFS support for Qt on my BeagleBone >>> Black. Many thanks for the clear and detailed article! >>> >>> Best regards >>> Bora >>> >>> On Thursday, March 28, 2019 at 7:47:49 PM UTC+1, [email protected] >>> wrote: >>>> >>>> So kernel "overlays" are broken, upgrade your version of u-boot and >>>>> >>>>> add this define in /boot/uEnv.txt >>>>> >>>>> sudo /opt/scripts/tools/developers/update_bootloader.sh >>>>> >>>>> enable_uboot_overlays=1 >>>>> uboot_overlay_addr4=/lib/firmware/CAPE-LVDS-1024-00A0.dtbo >>>>> disable_uboot_overlay_video=1 >>>>> >>>>> Then reboot and run: >>>>> >>>>> sudo /opt/scripts/tools/version.sh >>>>> >>>>> to see if everything is happy.. >>>>> >>>>> >>>> Ok perfect, that work very fine! Thanks >>>> >>>> >>>> That is strange, i never had libgbm-dev installed and got kmscube to >>>>> work.. >>>> >>>> When I execute 'autogen.sh', the script notice me to get libgbm-dev: >>>> >>>> git clone git://git.ti.com/glsdk/kmscube.git >>>> >>>> cd kmscube/ >>>> >>>> ./autogen.sh >>>> ... >>>> checking for DRM... yes >>>> checking for GBM... no >>>> configure: error: Package requirements (gbm) were not met: >>>> >>>> No package 'gbm' 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 GBM_CFLAGS >>>> and GBM_LIBS to avoid the need to call pkg-config. >>>> See the pkg-config man page for more details. >>>> >>>> >>>> >>>> But it's very strange, because if I do just: apt remove libgbm1 --purge >>>> I can execute normaly kmscube but I have a black screen. >>>> root@beaglebone ~ # ll /usr/lib/libgb* >>>> lrwxrwxrwx 1 root root 15 Mar 26 18:40 /usr/lib/libgbm.so -> >>>> libgbm.so.2.0.0 >>>> lrwxrwxrwx 1 root root 15 Mar 26 18:40 /usr/lib/libgbm.so.2 -> >>>> libgbm.so.2.0.0 >>>> -rw-r--r-- 1 root root 9.5K Mar 26 18:40 /usr/lib/libgbm.so.2.0.0 >>>> root@beaglebone ~ # whereis kmscube >>>> kmscube: /usr/bin/kmscube >>>> root@beaglebone ~ # ldd /usr/bin/kmscube >>>> linux-vdso.so.1 (0xbeff6000) >>>> libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb6f27000) >>>> libdrm.so.2 => /usr/lib/arm-linux-gnueabihf/libdrm.so.2 >>>> (0xb6f0b000) >>>> libgbm.so.2 => /usr/lib/libgbm.so.2 (0xb6ef8000) >>>> libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6ee5000) >>>> libEGL.so.1 => /usr/lib/libEGL.so.1 (0xb6ed3000) >>>> libIMGegl.so.1 => /usr/lib/libIMGegl.so.1 (0xb6eae000) >>>> libdrm_omap.so.1 => >>>> /usr/lib/arm-linux-gnueabihf/libdrm_omap.so.1 (0xb6e9b000) >>>> libGLESv2.so.2 => /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 >>>> (0xb6e7d000) >>>> libsrv_um.so.1 => /usr/lib/libsrv_um.so.1 (0xb6e46000) >>>> libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6d58000) >>>> /lib/ld-linux-armhf.so.3 (0xb6fc3000) >>>> libudev.so.1 => /lib/arm-linux-gnueabihf/libudev.so.1 >>>> (0xb6d41000) >>>> libwayland-server.so.0 => >>>> /usr/lib/arm-linux-gnueabihf/libwayland-server.so.0 (0xb6d26000) >>>> libffi.so.6 => /usr/lib/arm-linux-gnueabihf/libffi.so.6 >>>> (0xb6d10000) >>>> libdbm.so.1 => /usr/lib/libdbm.so.1 (0xb6cfe000) >>>> libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 >>>> (0xb6cda000) >>>> libGLdispatch.so.0 => >>>> /usr/lib/arm-linux-gnueabihf/libGLdispatch.so.0 (0xb6c5c000) >>>> librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb6c46000) >>>> libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 >>>> (0xb6c1d000) >>>> After the command "apt autoremove", the kmscube is displayed correctly >>>> on the screen! >>>> >>>> >>>> >>>> Unfortunately, if we use we ti-sgx-common-ddk-um package's, we will >>>>> have conflicts with libegl1-mesa-dev and libgles2-mesa-dev packages and >>>>> the >>>>> libgbm1 package will be reinstall... >>>> >>>> Ah crap, so the reason i split those files into a 2nd common package >>>>> was to fix that possibility.. >>>>> >>>>> Fixed with: >>>>> https://github.com/rcn-ee/repos/commit/25a4d0892b99a0526adc683f0f34b767cb6b193e >>>>> >>>>> >>>> Ok I try this : >>>> root@beaglebone ~ # dpkg -l |grep ti-sgx >>>> ii ti-sgx-ti335x-modules-4.14.108-ti-r101 1stretch >>>> armhf >>>> ti-sgx modules >>>> ii ti-sgx-ti33x-ddk-um >>>> 1.14.3699939-git20171201.0-0*rcnee9*~stretch+20190328 armhf >>>> Userspace libraries for SGX >>>> ii ti-sgx-common-ddk-um >>>> 1.14.3699939-git20171201.0-0rcnee8~stretch+20190326 armhf >>>> Userspace libraries for SGX >>>> >>>> root@beaglebone ~ # apt install libqt5qml5 qml-module-qtquick-controls >>>> qt5-default qtdeclarative5-dev qtquickcontrols5-examples >>>> Reading package lists... Done >>>> Building dependency tree >>>> Reading state information... Done >>>> The following additional packages will be installed: >>>> libdrm-amdgpu1 libdrm-common libdrm-dev libdrm-etnaviv1 >>>> libdrm-exynos1 libdrm-freedreno1 libdrm-nouveau2 libdrm-omap1 >>>> libdrm-radeon1 libdrm-tegra0 libdrm2 libegl-mesa0 libegl1 libegl1-mesa >>>> *libegl1-mesa-dev* libevdev2 *libgbm1 *libgles2 *libgles2-mesa-dev* >>>> ... >>>> Errors were encountered while processing: >>>> >>>> >>>> /tmp/apt-dpkg-install-e1Iuir/076-libegl1-mesa-dev_18.1.9-1rcnee1~stretch+20190321_armhf.deb >>>> >>>> >>>> /tmp/apt-dpkg-install-e1Iuir/077-libgles2-mesa-dev_18.1.9-1rcnee1~stretch+20190321_armhf.deb >>>> E: Sub-process /usr/bin/dpkg returned an error code (1) >>>> >>>> So I remove manually: >>>> # dpkg -r ti-sgx-common-ddk-um >>>> # apt --fix-broken install >>>> >>>> Ok, there is no error now with apt command. >>>> I execute the Qt example: >>>> ./dashboard >>>> Could not initialize egl display >>>> Aborted >>>> Thin I really need the ti-sgx-common-ddk-um package and not >>>> libegl1-mesa-dev/libgles2-mesa-dev! >>>> This is not the way to go I guess. >>>> >>>> >>>> It's certainly a silly question but.. Why do not you update directly >>>> the libraries mesa-libgl1, mesa-libgles2 and libgbm? >>>> >>>> >>>> >>>> Le jeudi 28 mars 2019 16:33:51 UTC+1, RobertCNelson a écrit : >>>>> >>>>> On Thu, Mar 28, 2019 at 9:59 AM <[email protected]> wrote: >>>>> > >>>>> > Hi Robert, >>>>> > >>>>> > I test your script with kmscube, qt5 qml and with my custom cape >>>>> with dts file (available on attached file). >>>>> > I share with you all my results (sorry it's a long post...) >>>>> > >>>>> > Commands execute on start >>>>> > #uname -r >>>>> > 4.9.78-ti-r94 >>>>> > #apt update >>>>> > #cd /opt/scripts/tools/ >>>>> > #git pull >>>>> > #./update_kernel.sh --ti-channel --lts-4_14 --sgx >>>>> > ... >>>>> > The following NEW packages will be installed: >>>>> > linux-image-4.14.108-ti-r101 >>>>> > ... >>>>> > The following NEW packages will be installed: >>>>> > libpruio-modules-4.14.108-ti-r101 >>>>> > ... >>>>> > The following NEW packages will be installed: >>>>> > ti-sgx-ti335x-modules-4.14.108-ti-r101 >>>>> > ... >>>>> > The following NEW packages will be installed: >>>>> > ti-libgbm2 ti-sgx-ti33x-ddk-um >>>>> > ... >>>>> > #reboot >>>>> > #uname -r >>>>> > 4.14.108-ti-r101 >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > With HDMI and KMSCUBE >>>>> > root@beaglebone ~ #ls /sys/devices/platform/ocp/56000000.sgx >>>>> > ls: cannot access '/sys/devices/platform/ocp/56000000.sgx': No such >>>>> file or directory >>>>> > root@beaglebone ~ # /etc/init.d/ti-sgx-ti33x-ddk-um start >>>>> > [ ok ] Starting ti-sgx-ti33x-ddk-um (via systemctl): >>>>> ti-sgx-ti33x-ddk-um.service. >>>>> > root@beaglebone ~ # dmesg |grep -i pvr >>>>> > [ 317.740779] pvrsrvkm: loading out-of-tree module taints kernel. >>>>> > root@beaglebone ~ # service ti-sgx-ti33x-ddk-um status >>>>> > ● ti-sgx-ti33x-ddk-um.service - LSB: Start daemon at boot time >>>>> > Loaded: loaded (/etc/init.d/ti-sgx-ti33x-ddk-um; generated; >>>>> vendor preset: enabled) >>>>> > Active: active (exited) since Thu 2019-03-28 14:27:45 CET; 9min >>>>> ago >>>>> > Docs: man:systemd-sysv-generator(8) >>>>> > Process: 314 ExecStart=/etc/init.d/ti-sgx-ti33x-ddk-um start >>>>> (code=exited, status=0/SUCCESS) >>>>> > Tasks: 0 (limit: 4915) >>>>> > CGroup: /system.slice/ti-sgx-ti33x-ddk-um.service >>>>> > >>>>> > Mar 28 14:27:42 beaglebone systemd[1]: Starting LSB: Start daemon at >>>>> boot time... >>>>> > Mar 28 14:27:45 beaglebone systemd[1]: Started LSB: Start daemon at >>>>> boot time. >>>>> > >>>>> > >>>>> > hum I haven't access to sgx drivers. I check my uEnv.txt file, and I >>>>> comment "dtb=am335x-boneblack-overlay.dtb" line (why I have this line? >>>>> idk..) >>>>> > ls /sys/devices/platform/ocp/56000000.sgx >>>>> > driver driver_override drm modalias of_node power subsystem >>>>> uevent >>>>> > dmesg |grep -i pvr >>>>> > [ 12.544964] pvrsrvkm: loading out-of-tree module taints kernel. >>>>> > [ 12.754997] [drm] Initialized pvr 1.14.3699939 20110701 for >>>>> 56000000.sgx on minor 2 >>>>> > [ 12.939720] PVR_K: UM DDK-(3699939) and KM DDK-(3699939) match. [ >>>>> OK ] >>>>> > >>>>> > Ok good! Your /etc/init.d/ti-sgx-ti33x-ddk-um script work fine now. >>>>> > >>>>> > So to really test the SGX drivers, I run OGLES2Water from git:// >>>>> git.ti.com/graphics/img-pvr-sdk.git and it execute fine! Perfect! >>>>> > >>>>> > I did not find a package with kms++ or kmscube, so I took my package >>>>> directly. >>>>> > root@beaglebone /opt # wget >>>>> https://remi.avignon.me/bbb/kmsxx_1.0.0_armhf.deb >>>>> > root@beaglebone /opt # dpkg -i kmsxx_1.0.0_armhf.deb >>>>> > root@beaglebone /opt # kmscube >>>>> > drmModeGetResources failed: Invalid argument >>>>> > failed to initialize DRM >>>>> > >>>>> > root@beaglebone /opt # ls -alh /sys/class/drm/ >>>>> > total 0 >>>>> > drwxr-xr-x 2 root root 0 Mar 28 15:01 . >>>>> > drwxr-xr-x 63 root root 0 Mar 28 14:52 .. >>>>> > lrwxrwxrwx 1 root root 0 Mar 28 14:52 card0 -> >>>>> ../../devices/platform/vgem/drm/card0 >>>>> > lrwxrwxrwx 1 root root 0 Mar 28 14:52 card1 -> >>>>> ../../devices/platform/ocp/4830e000.lcdc/drm/card1 >>>>> > lrwxrwxrwx 1 root root 0 Mar 28 14:52 card1-HDMI-A-1 -> >>>>> ../../devices/platform/ocp/4830e000.lcdc/drm/card1/card1-HDMI-A-1 >>>>> > lrwxrwxrwx 1 root root 0 Mar 28 14:53 card2 -> >>>>> ../../devices/platform/ocp/56000000.sgx/drm/card2 >>>>> > lrwxrwxrwx 1 root root 0 Mar 28 14:53 renderD128 -> >>>>> ../../devices/platform/ocp/56000000.sgx/drm/renderD128 >>>>> > -r--r--r-- 1 root root 4.0K Mar 28 14:52 version >>>>> > >>>>> > root@beaglebone /opt # kmscube -d /dev/dri/card1 >>>>> > ### Display [0]: CRTC = 28, Connector = 30, format = 0x36314752 >>>>> > Mode chosen [1024x768] : Clock => 78750, Vertical refresh => >>>>> 75, Type => 64 >>>>> > Horizontal => 1024, 1040, 1136, 1312, 0 >>>>> > Vertical => 768, 769, 772, 800, 0 >>>>> > ### Primary display => ConnectorId = 30, Resolution = 1024x768 >>>>> > loaded module : gbm_pvr.so >>>>> > found valid GBM backend : gbm_pvr.so >>>>> > failed to initialize >>>>> > failed to initialize EGL >>>>> > >>>>> > root@beaglebone /opt # apt remove libgbm-dev libgbm1 >>>>> > Reading package lists... Done >>>>> > Building dependency tree >>>>> > Reading state information... Done >>>>> > Package 'libgbm-dev' is not installed, so not removed >>>>> > The following packages were automatically installed and are no >>>>> longer required: >>>>> > gconf-service gconf2 gconf2-common gksu keyboard-configuration >>>>> libdbus-glib-1-2 libdrm-armada2 libetnaviv libevde >>>>> > libgksu2-0 libgles2 libgles2-mesa libgnome-keyring-common >>>>> libgnome-keyring0 libgtop-2.0-10 libgtop2-common libinp >>>>> > libstartup-notification0 libutf8proc2 libwacom-bin libwacom-common >>>>> libwacom2 libxcb-icccm4 libxcb-image0 libxcb-k >>>>> > libxkbcommon-x11-0 lxmenu-data oxygen-icon-theme pcmanfm-qt-l10n >>>>> qterminal-l10n qtermwidget5-data xserver-xorg-le >>>>> > Use 'apt autoremove' to remove them. >>>>> > The following additional packages will be installed: >>>>> > libwayland-egl1 xserver-common >>>>> > The following packages will be REMOVED: >>>>> > libegl-mesa0 libegl1 libegl1-mesa libfm-qt3 libgbm1 libqt5gui5 >>>>> libqt5multimedia5 libqt5multimediawidgets5 libqt5o >>>>> > pcmanfm-qt qt5-gtk-platformtheme qterminal xserver-xorg >>>>> xserver-xorg-core xserver-xorg-input-all xserver-xorg-inp >>>>> > xserver-xorg-video-armada-etnaviv xserver-xorg-video-fbdev >>>>> xserver-xorg-video-omap >>>>> > The following NEW packages will be installed: >>>>> > libwayland-egl1 >>>>> > The following packages will be upgraded: >>>>> > xserver-common >>>>> > 1 upgraded, 1 newly installed, 28 to remove and 188 not upgraded. >>>>> > Need to get 2,067 kB of archives. >>>>> > After this operation, 21.2 MB disk space will be freed. >>>>> > Do you want to continue? [Y/n] y >>>>> > >>>>> > root@beaglebone /opt # kmscube -d /dev/dri/card1 >>>>> > ### Display [0]: CRTC = 28, Connector = 30, format = 0x36314752 >>>>> > Mode chosen [1024x768] : Clock => 78750, Vertical refresh => >>>>> 75, Type => 64 >>>>> > Horizontal => 1024, 1040, 1136, 1312, 0 >>>>> > Vertical => 768, 769, 772, 800, 0 >>>>> > ### Primary display => ConnectorId = 30, Resolution = 1024x768 >>>>> > loaded module : gbm_pvr.so >>>>> > found valid GBM backend : gbm_pvr.so >>>>> > Using display 0x1 with EGL version 1.4 >>>>> > EGL Version "1.4 build 1.14@3699939 (MAIN)" >>>>> > EGL Vendor "Imagination Technologies" >>>>> > EGL Extensions "EGL_IMG_client_api_ogl EGL_KHR_image >>>>> EGL_KHR_image_base EGL_KHR_gl_texture_2D_image >>>>> EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image >>>>> EGL_KHR_vg_parent_image EGL_IMG_cl_image EGL_KHR_fence_sync >>>>> EGL_IMG_context_priority EGL_IMG_hibernate_process >>>>> EGL_IMG_image_plane_attribs EGL_KHR_surfaceless_context EGL_KHR_wait_sync >>>>> EGL_KHR_create_context EGL_WL_bind_wayland_display >>>>> EGL_EXT_image_dma_buf_import" >>>>> > >>>>> > >>>>> > But on my HDMI monitor I don't see a 3D cube but just a verticals >>>>> blue lines!! It's strange... >>>>> > I recompile kmscube but I need libgbm-dev package ^^'... >>>>> >>>>> That is strange, i never had libgbm-dev installed and got kmscube to >>>>> work.. >>>>> >>>>> >>>>> > root@beaglebone /opt/kmscube # apt autoremove >>>>> > Reading package lists... Done >>>>> > Building dependency tree >>>>> > Reading state information... Done >>>>> > The following packages will be REMOVED: >>>>> > gconf-service gconf2 gconf2-common gksu keyboard-configuration >>>>> libdbus-glib-1-2 libdrm-armada2 libetnaviv >>>>> > libevdev2 libfm-data libfm-extra4 libfm-gtk-data libfm-gtk4 >>>>> libfm-modules libfm-qt-l10n libfm4 libgbm1 >>>>> > libgconf-2-4 libgksu2-0 libgles2 libgles2-mesa >>>>> libgnome-keyring-common libgnome-keyring0 libgtop-2.0-10 >>>>> > libgtop2-common libinput-bin libinput10 libmenu-cache-bin >>>>> libmenu-cache3 libmtdev1 libpciaccess0 libqt5dbus5 >>>>> > libqt5network5 libstartup-notification0 libutf8proc2 libwacom-bin >>>>> libwacom-common libwacom2 libxcb-icccm4 >>>>> > libxcb-image0 libxcb-keysyms1 libxcb-randr0 libxcb-render-util0 >>>>> libxcb-util0 libxcb-xinerama0 libxcb-xkb1 >>>>> > libxfont2 libxkbcommon-x11-0 lxmenu-data oxygen-icon-theme >>>>> pcmanfm-qt-l10n qterminal-l10n qtermwidget5-data >>>>> > xserver-xorg-legacy >>>>> > 0 upgraded, 0 newly installed, 54 to remove and 182 not upgraded. >>>>> > After this operation, 61.0 MB disk space will be freed. >>>>> > Do you want to continue? [Y/n] y >>>>> > ... >>>>> > >>>>> > root@beaglebone ~ # kmscube -d /dev/dri/card1 >>>>> > kmscube: error while loading shared libraries: libgbm.so.1: cannot >>>>> open shared object file: No such file or directory >>>>> > >>>>> > root@beaglebone ~ # ln -s /usr/lib/libgbm.so.2.0.0 >>>>> /usr/lib/libgbm.so.1 >>>>> >>>>> Wonder if i should just auto-create that symlink to... >>>>> >>>>> > >>>>> > root@beaglebone ~ # kmscube -d /dev/dri/card1 >>>>> > ### Display [0]: CRTC = 28, Connector = 30, format = 0x36314752 >>>>> > Mode chosen [1024x768] : Clock => 78750, Vertical refresh => >>>>> 75, Type => 64 >>>>> > Horizontal => 1024, 1040, 1136, 1312, 0 >>>>> > Vertical => 768, 769, 772, 800, 0 >>>>> > ### Primary display => ConnectorId = 30, Resolution = 1024x768 >>>>> > loaded module : gbm_pvr.so >>>>> > found valid GBM backend : gbm_pvr.so >>>>> > Using display 0x1 with EGL version 1.4 >>>>> > EGL Version "1.4 build 1.14@3699939 (MAIN)" >>>>> > EGL Vendor "Imagination Technologies" >>>>> > EGL Extensions "EGL_IMG_client_api_ogl EGL_KHR_image >>>>> EGL_KHR_image_base EGL_KHR_gl_texture_2D_image >>>>> EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image >>>>> EGL_KHR_vg_parent_image EGL_IMG_cl_image EGL_KHR_fence_sync >>>>> EGL_IMG_context_priority EGL_IMG_hibernate_process >>>>> EGL_IMG_image_plane_attribs EGL_KHR_surfaceless_context EGL_KHR_wait_sync >>>>> EGL_KHR_create_context EGL_WL_bind_wayland_display >>>>> EGL_EXT_image_dma_buf_import" >>>>> > ^CHandling signal number = 2 >>>>> > Cleanup of GL, GBM and DRM completed >>>>> > >>>>> > Yeah now I can see the 3D cube in rotation! >>>>> > >>>>> > >>>>> > >>>>> > With HMDI and Qt QML with EGLFS >>>>> > Unfortunately, if we use we ti-sgx-common-ddk-um package's, we will >>>>> have conflicts with libegl1-mesa-dev and libgles2-mesa-dev packages and >>>>> the >>>>> libgbm1 package will be reinstall... >>>>> > >>>>> > #apt install libqt5qml5 qml-module-qtquick-controls qt5-default >>>>> qtdeclarative5-dev qtquickcontrols5-examples >>>>> > ... >>>>> > dpkg: error processing archive >>>>> /tmp/apt-dpkg-install-CHuAeE/57-libegl1-mesa-dev_18.1.9-1rcnee1~stretch+20190321_armhf.deb >>>>> >>>>> (--unpack): >>>>> > trying to overwrite '/usr/include/EGL/egl.h', which is also in >>>>> package ti-sgx-common-ddk-um >>>>> 1.14.3699939-git20171201.0-0rcnee8~stretch+20190326 >>>>> > Selecting previously unselected package libgles2-mesa-dev:armhf. >>>>> > Preparing to unpack >>>>> .../58-libgles2-mesa-dev_18.1.9-1rcnee1~stretch+20190321_armhf.deb ... >>>>> > Unpacking libgles2-mesa-dev:armhf (18.1.9-1rcnee1~stretch+20190321) >>>>> ... >>>>> > dpkg: error processing archive >>>>> /tmp/apt-dpkg-install-CHuAeE/58-libgles2-mesa-dev_18.1.9-1rcnee1~stretch+20190321_armhf.deb >>>>> >>>>> (--unpack): >>>>> > trying to overwrite '/usr/include/GLES2/gl2.h', which is also in >>>>> package ti-sgx-common-ddk-um >>>>> 1.14.3699939-git20171201.0-0rcnee8~stretch+20190326 >>>>> > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) >>>>> >>>>> Ah crap, so the reason i split those files into a 2nd common package >>>>> was to fix that possibility.. >>>>> >>>>> Fixed with: >>>>> https://github.com/rcn-ee/repos/commit/25a4d0892b99a0526adc683f0f34b767cb6b193e >>>>> >>>>> >>>>> > ... >>>>> > You might want to run 'apt --fix-broken install' to correct these. >>>>> > The following packages have unmet dependencies: >>>>> > qtbase5-dev : Depends: libgles2-mesa-dev but it is not going to be >>>>> installed or >>>>> > libgles2-dev but it is not installable >>>>> > E: Unmet dependencies. Try 'apt --fix-broken install' with no >>>>> packages (or specify a solution). >>>>> > >>>>> > $sudo apt --fix-broken install >>>>> > Reading package lists... Done >>>>> > Building dependency tree >>>>> > Reading state information... Done >>>>> > Correcting dependencies... Done >>>>> > The following additional packages will be installed: >>>>> > libegl1-mesa-dev libgles2-mesa-dev >>>>> > The following NEW packages will be installed: >>>>> > libegl1-mesa-dev libgles2-mesa-dev >>>>> > 0 upgraded, 2 newly installed, 0 to remove and 175 not upgraded. >>>>> > 78 not fully installed or removed. >>>>> > Need to get 140 kB of archives. >>>>> > After this operation, 811 kB of additional disk space will be used. >>>>> > Do you want to continue? [Y/n] y >>>>> > Get:1 http://repos.rcn-ee.com/debian stretch/main armhf >>>>> libegl1-mesa-dev armhf 18.1.9-1rcnee1~stretch+20190321 [59.7 kB] >>>>> > Get:2 http://repos.rcn-ee.com/debian stretch/main armhf >>>>> libgles2-mesa-dev armhf 18.1.9-1rcnee1~stretch+20190321 [80.7 kB] >>>>> > Fetched 140 kB in 0s (174 kB/s) >>>>> > E: Sub-process /usr/bin/dpkg returned an error code (1) >>>>> > >>>>> > >>>>> > But it's not a problem to compile and execute a Qt program : >>>>> > cd >>>>> /usr/lib/arm-linux-gnueabihf/qt5/examples/quickcontrols/extras/dashboard >>>>> > qmake >>>>> > make >>>>> > export QT_QPA_PLATFORM=eglfs >>>>> > export QT_QPA_EGLFS_INTEGRATION=none >>>>> > ./dashboard >>>>> > >>>>> > Okay we can see the dashboard program on the monitor! >>>>> > >>>>> > >>>>> > LVDS with my custom cape >>>>> > >>>>> > My custom cape work fine on 4.9 kernel. I can compile my dts file to >>>>> dtbo on 4.14 but I have a "Unable to handle kernel NULL pointer >>>>> dereference >>>>> at virtual address" error on boot. >>>>> > $sudo dtc -O dtb -o /lib/firmware/CAPE-LVDS-1024-00A0.dtbo -b 0 -@ >>>>> CAPE-LVDS-1024-00A0.dts >>>>> > $sudo echo 'CAPE=CAPE-LVDS-1024' > /etc/default/capemgr >>>>> > $sudo reboot >>>>> >>>>> So kernel "overlays" are broken, upgrade your version of u-boot and >>>>> add this define in /boot/uEnv.txt >>>>> >>>>> sudo /opt/scripts/tools/developers/update_bootloader.sh >>>>> >>>>> enable_uboot_overlays=1 >>>>> uboot_overlay_addr4=/lib/firmware/CAPE-LVDS-1024-00A0.dtbo >>>>> disable_uboot_overlay_video=1 >>>>> >>>>> Then reboot and run: >>>>> >>>>> sudo /opt/scripts/tools/version.sh >>>>> >>>>> to see if everything is happy.. >>>>> >>>>> > My dts file dates from the old school, I created it for the first >>>>> debian version (3.8.13-bone50) and I adapted it for kernel 4.4 and 4.9. >>>>> > I think I have to use the new way for kernel 1.14. This problem has >>>>> nothing to do with SGX. >>>>> > >>>>> > I hope that my tests will be useful to you to continue the >>>>> integration of the libraries to use the graphic acceleration. >>>>> >>>>> Regards, >>>>> >>>>> -- >>>>> Robert Nelson >>>>> https://rcn-ee.com/ >>>>> >>>> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a501541a-4058-47b9-aa12-7eb76fe61fb7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
