# Cannot install voxl-utils Source: https://forum.modalai.com/topic/1243/cannot-install-voxl-utils Category: General Questions (https://forum.modalai.com/category/2/general-questions) Posted: 2022-08-25 08:38:50 UTC by tanguy sagere Replies: 4 · Views: 950 ## tanguy sagere · 2022-08-25 08:38:50 UTC Hello! Ive successfully installed the VOXL2 system image on my VOXL2 and am now trying to install the SDK. However, I get an error for the voxl-utils package, whereas the other packages installed without issue, which is particularly problematic as I need this package to install the overarching voxl-suite deb. Thank you for your help, error message below! ``` xxx@xxx:/mnt/persist/voxl-suite-offline-packages$ sudo dpkg -i voxl-utils_1.0.0_arm64.deb Selecting previously unselected package voxl-utils. (Reading database ... 88015 files and directories currently installed.) Preparing to unpack voxl-utils_1.0.0_arm64.deb ... Unpacking voxl-utils (1.0.0) ... Setting up voxl-utils (1.0.0) ... Job for voxl-wait-for-fs.service canceled. dpkg: error processing package voxl-utils (--install): installed voxl-utils package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.27-3ubuntu1.6) ... Errors were encountered while processing: voxl-utils ``` ## Reply by Guest · 2022-08-25 17:03:00 UTC Hi, We have releases for voxl2 that have the system image and SDK install paired together. I'd recommend downloading one of these from our [downloads](https://developer.modalai.com/asset/2) page, the latest is system image 1.3.1 with sdk 0.8 (which includes voxl-utils 1.1.4). ## Reply by tanguy sagere · 2022-08-29 09:57:32 UTC Hello! Thank you for your quick reply :) I've downloaded the latest SDK from the download page as you recommended and re-ran into the same issue. ``` xxx@xxx:/mnt/persist/voxl2_platform_1.3.1-0.8/voxl-sdk$ sudo dpkg -i voxl-utils_1.1.4_arm64.deb (Reading database ... 88040 files and directories currently installed.) Preparing to unpack voxl-utils_1.1.4_arm64.deb ... Unpacking voxl-utils (1.1.4) over (1.1.4) ... Setting up voxl-utils (1.1.4) ... A dependency job for voxl-wait-for-fs.service failed. See 'journalctl -xe' for details. dpkg: error processing package voxl-utils (--install): installed voxl-utils package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: voxl-utils ``` When running 'journalctl -xe' to see the details I get the following : ``` xxx@xxx:/mnt/persist/voxl2_platform_1.3.1-0.8/voxl-sdk$ journalctl -xe -- Unit firmware-mount.service has failed. -- -- The result is RESULT. Aug 29 09:50:33 xxx-1e7fa15e systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Aug 29 09:50:33 xxx-1e7fa15e systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Aug 29 09:50:33 xxx-1e7fa15e systemd[1]: Failed to start Load Kernel Modules. -- Subject: Unit systemd-modules-load.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-modules-load.service has failed. -- -- The result is RESULT. Aug 29 09:50:33 xxx-1e7fa15e systemd[1]: dsp-mount.service: Main process exited, code=exited, status=32/n/a Aug 29 09:50:33 xxx-1e7fa15e systemd[1]: dsp-mount.service: Failed with result 'exit-code'. Aug 29 09:50:33 xxx-1e7fa15e systemd[1]: Failed to start Mount dsp partition to /dsp mount point. -- Subject: Unit dsp-mount.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit dsp-mount.service has failed. -- -- The result is RESULT. Aug 29 09:50:33 xxx-1e7fa15e systemd[1]: Reloading. Aug 29 09:50:33 xxx-1e7fa15e update-alternatives-recovery[2842]: update-alternatives: warning: forcing reinstallation of alternative /opt/qcom/usr/lib Aug 29 09:50:33 xxx-1e7fa15e update-alternatives-recovery[2842]: update-alternatives: warning: forcing reinstallation of alternative /opt/qcom/usr/lib Aug 29 09:50:33 xxx-1e7fa15e update-alternatives-recovery[2842]: update-alternatives: warning: forcing reinstallation of alternative /opt/qcom/usr/lib Aug 29 09:50:34 xxx-1e7fa15e update-alternatives-recovery[2842]: update-alternatives: warning: forcing reinstallation of alternative /opt/qcom/usr/lib Aug 29 09:50:34 xxx-1e7fa15e systemd[1]: Reloading. Aug 29 09:50:35 xxx-1e7fa15e sudo[2068]: pam_unix(sudo:session): session closed for user root Aug 29 09:50:35 xxx-1e7fa15e update-alternatives-recovery[3169]: update-alternatives: warning: forcing reinstallation of alternative /opt/qcom/usr/lib Aug 29 09:50:35 xxx-1e7fa15e update-alternatives-recovery[3169]: update-alternatives: warning: forcing reinstallation of alternative /opt/qcom/usr/lib Aug 29 09:50:35 xxx-1e7fa15e update-alternatives-recovery[3169]: update-alternatives: warning: forcing reinstallation of alternative /opt/qcom/usr/lib Aug 29 09:50:36 xxx-1e7fa15e systemd[1]: Started update-alternatives recovery. -- Subject: Unit update-alternatives-recovery.service has finished start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit update-alternatives-recovery.service has finished starting up. -- -- The start-up result is RESULT. Aug 29 09:50:36 xxx-1e7fa15e systemd[2847]: emergency.service: Executable /bin/plymouth missing, skipping: No such file or directory -- Subject: Process /bin/plymouth could not be executed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The process /bin/plymouth could not be executed and failed. -- -- The error number returned by this process is 2. ``` ## Reply by Guest · 2022-08-29 17:14:54 UTC Hi, Just for clarity on the current system image that you're on, could you send the output of the following commands: ``` bash xxx@xxx:/$ voxl-version xxx@xxx:/$ cat /firmware/verinfo/ver_info.txt ``` It looks like you've downloaded our latest platform release ```voxl2_platform_1.3.1-0.8```. If you haven't already can you try flashing the 1.3.1 system image from that platform release and seeing if you still see this same issue. ## Reply by tanguy sagere · 2022-09-03 09:00:50 UTC (in reply to Guest) @Hector-Nevarez Problem solved, was hardware-related. Thank you for your help!