Search the Community

Hello I use armbian on my odroidc2 on the devic is lamp, for a mysql and php server. Now i tried to install composer. The installation works great, but i can't use any scripts from vendor folder. The directory of my php file: /var/www/html/terminal/includes/helpers/my_php_file.php the code in my php file require_once(__DIR__ . '/vendor/autoload.php'); The code means the vendor directory has this path: /var/www/html/terminal/includes/helpers/vendor/autoload.php But thats not correct. I searched and found the correct path of composer it's: /home/user/vendor/ So i tried to make a folder-shortcut in my www/html/ folder, but i can't use it because permission denied. Next idea: i fix the code in my php file include '../../../../../../home/odroid/vendor/autoload.php'; now it would be found, but i get the same error: Warning: include(../../../../../../home/odroid/vendor/autoload.php): Failed to open stream: Permission denied in /var/www/html/terminal/includes/helpers/backup_DB.php on line 26 what's the correct way to youe composer with autoload.php and something more?

Added more details for original post odroidc2 with Armbian 23.02 Jammy XFCE (Armbian_23.02.1_Odroidc2_jammy_current_6.1.14_xfce_desktop.img) I have an odroidc2 connected to: 1)monitor with built-in speakers via hdmi cable. 2)usb audio adapter (https://ameridroid.com/products/usb-audio-adapter) 3)ethernet cable 4)wireless keyboard dongle I have issue outputting audio to monitor speaker. dmesg and syslog output related to hdmi is as follows. Any help is greatly appreciated. Thanks $ dmesg|grep hdmi [ 0.035220] platform c883a000.hdmi-tx: Fixing up cyclic dependency with d0100000.vpu [ 0.037586] platform hdmi-connector: Fixing up cyclic dependency with c883a000.hdmi-tx [ 1.614016] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy) [ 1.614532] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver [ 1.614805] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops) $ sudo cat /var/log/syslog |grep -i hdmi Apr 25 00:44:37 odroidc2 kernel: [ 0.035292] platform c883a000.hdmi-tx: Fixing up cyclic dependency with d0100000.vpu Apr 25 00:44:37 odroidc2 kernel: [ 0.037662] platform hdmi-connector: Fixing up cyclic dependency with c883a000.hdmi-tx Apr 25 00:44:37 odroidc2 kernel: [ 1.614019] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy) Apr 25 00:44:37 odroidc2 kernel: [ 1.614545] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver Apr 25 00:44:37 odroidc2 kernel: [ 1.614825] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops) Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:5 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:5 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:9 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:9 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:13 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:13 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:16 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:16 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:20 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:20 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:23 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:23 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:26 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:26 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:34 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:39 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:39 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:47 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:47 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:51 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:51 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:55 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:55 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:59 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:59 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:64 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:64 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:68 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:68 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:71 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:71 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:71 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:75 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:75 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:78 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:78 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:81 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:81 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:87 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:87 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:87 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:90 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:90 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:95 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:95 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:104 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:108 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:113 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. <repeated similar lines> Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:409 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:409 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 00:57:50 odroidc2 kernel: [ 0.035295] platform c883a000.hdmi-tx: Fixing up cyclic dependency with d0100000.vpu Apr 25 00:57:50 odroidc2 kernel: [ 0.037650] platform hdmi-connector: Fixing up cyclic dependency with c883a000.hdmi-tx Apr 25 00:57:50 odroidc2 kernel: [ 1.613986] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy) Apr 25 00:57:50 odroidc2 kernel: [ 1.614507] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver Apr 25 00:57:50 odroidc2 kernel: [ 1.614777] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops) Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:5 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:5 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:9 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:9 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:13 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:13 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:16 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:16 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:20 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:20 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:23 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:23 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:26 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:26 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:34 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:39 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:39 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:47 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:47 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:51 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:51 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:55 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:55 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:59 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:59 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:64 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:64 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. <repeated similar lines> Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 kernel: [ 0.035220] platform c883a000.hdmi-tx: Fixing up cyclic dependency with d0100000.vpu Apr 25 01:50:25 odroidc2 kernel: [ 0.037586] platform hdmi-connector: Fixing up cyclic dependency with c883a000.hdmi-tx Apr 25 01:50:25 odroidc2 kernel: [ 1.614016] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy) Apr 25 01:50:25 odroidc2 kernel: [ 1.614532] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver Apr 25 01:50:25 odroidc2 kernel: [ 1.614805] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops) Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:95 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:95 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.] Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:104 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:108 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='. <repeated similar lines> Apr 25 01:50:26 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:409 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.

Hello I want to get cpu and ram infos via bash command. So i use this for temperature: For the cpu usage i needed a long time to find a solution. now i found this: echo $[100-$(vmstat 1 2|tail -1|awk '{print $15}')] For the free ram usage, i will use free --mega My question Are this command correct? the cpu command line is really new for me... does it takes a lot of ressources, if i use this commands every 2 seconds to get a real time listening? i need to write it in a database to get a graphical solution. Thank you for your help

I have an odroid-c2 with eMMC module flashed with Armbian_23.02.1_Odroidc2_jammy_current_6.1.14_xfce_desktop When viewing youtube containing word composed of non-latin characters, it shows a funny symbol for each character. How do I install the proper language for this?

I have an odroid-c2 with eMMC module flashed with Armbian_23.02.1_Odroidc2_jammy_current_6.1.14_xfce_desktop I have the following connected to the USB ports. 1) USB to audio headphone/microphone jacks 2) Wifi keyboard dongle The odroid-c2 is connected to an HDMI monitor with speakers I've been manipulating the settings for Pulseaudio and I could not get the audio to output to the monitor speakers. I could hear audio from the USB to audio jack connected to headphones

I tested the latest available Armbian image (minimal installation) on my odroid C2 via SD card. have available an 16gb hardkernel emmc card on which I had ubuntu 20.04 installed and running. But by burning the image with etcher (the same procedure as with the SD image) the odroid is unable to boot. Black screen, solid red led, and nothing else. I waited more than 30 seconds, I tried to disconnect keyboard....I waited more than 30 seconds, I tried to disconnect keyboard I have repeated the procedure through the SD and it works correctly. When I do it through the emmc, the system does not boot. When I use the SD card, the Emmc card is obviously disconnected, and when I use the emmc, the sd card is disconnected. I think u-boot has something to do with it https://redirect.armbian.com/region/EU/odroidc2/Jammy_current_minimal I apologize to the people mentioned above. I've read the forum a lot and thought they were the right people to respond to. @Igor

Dear members My odroid c2 don't restart. I found this command in the forum: apt install linux-image-edge-meson64 linux-dtb-edge-meson64 linux-u-boot-odroidc2-edge Can i use it for odroid c2? What will be installed?

Hello I'm a newbie and want to start my tour with my odroid c2 for the beginn i want to install a vnc server. So i tried to setup the port 5901 tcp (opoen/free) if i try ufw allow 5901/tcp i get ufw not found if i try iptables -a ........ dport 5901 i get dport not found So my question, is there any firwall on the default system? Thank you a lot

Hello, i tried to set up a little samba server with armbian on a odroid c2. If i use only the sd card, without any external storage, the system works fine, but if i connect any usb storage to the odroid c2, the system is booting into a bootloop or stops booting If i connect the usb storage after the first bios display, the system boot is fine. I think, the bootloader is trying to boot from the usp storage after detecting this, so is there an option to modify the bootloader, so it is only trying to boot from the pluged in sd card?

Hello all! I have an ODROID-C2 that I am trying to use with a GPS connected over UART for timing purposes, which requires the use of pps. Based on my searching and reading in this forum, I have determined that for my OS and kernel (Focal, 5.9.14) I should be able to do so by adding overlay=pps-gpio to armbianEnv.txt. What is not clear to me, however, is how to specify which pin to use! In this thread I see windysea said: But I don't know how to use this information! I have found no documentation on param_pps_*, and my attempts at guessing based on information from other threads and resources have failed to work so far. I have been fiddling with this for a few days to no avail now, so any assistance would be greatly appreciated. Regards, John

I’m running an Odroid C2 and trying to drive a 14.9" 1280x390 60hz LCD marquis display. On a Pi I can change the boot config files to the following and the display works like a champ. [HDMI:1] hdmi_group=2 hdmi_mode=87 hdmi_timings=1280 0 8 128 64 390 0 1 3 24 0 0 0 67 0 42009500 8 On the Odroid running Armbian 22.11 Jammy XFCE I tried changing: /boot/armbianEnv.txt adding display_autodetect=false hdmimode=1280x390p60hz I had no joy with this change, it did not modify the display output. I love how fast and light Odroid is with Armbian, it is really snappy, but I need some help stretching out this display. Any help pointing me in the right direction would be greatly appreciated, I already threw you $5 to take a look @Igor https://paypal.com/donate/?hosted_button_id=A2AM5NWLVENF2&source=url

boa noite gostaria de pedir ajuda estou tentando instalar o armbian em placa amlogic s805 e gostaria do arquivo u-boot já pesquisei no forum no site desde já agradeço não obteve sucesso

I have a Waveshare 3.5inch RPi LCD (A): https://www.waveshare.com/wiki/3.5inch_RPi_LCD_(A) Does somebody have this kind of LCD running on a Odroid C2? Is there a step by step? Because the Waveshare or Odroid Wiki is over my head 😟

Hi. I want to use CAN interface on ODROID C2 board. I use external CAN-bus controller like MCP2515 via SPI interface. So, i need to enable SPI and CAN-bus peripherals and in kernel. So, could someone explain me how to do that? I know about device tree, but don`t know what to do. Just give me some guide links about device tree management, any examples, etc.

Hello Guys, i am running an Odroid C2 with the latest Armbian based on debian Bullseye. As disk i am using an 8GB emmc flash drive. For longlive reasons i am thinking about to reduce the read or more important the write access to that drive. I know, that every SD card and also every EMMC flash drive got a certain amount of write access and then its dead... So i am ask you what can i do to reduce read/write: - move logs to external usb? - activate ZRAM? - disable cache...? - tmpfs? I am just at the beginning of this, so kindly let me know if you guys have some well know hints. Thanks JM

I have just downloaded desktop Armbian 22.08 Jammy XFCE on my Odroid-C2 and it works fine on a 1080p monitor. I need it to work on a different monitor though so I have added the following lines to /boot/armbianEnv.txt display_autodetect=false hdmimode=1680x1050p60hz and added hdmitx=forcergb in the bootargs (which I copy/pasted from /boot/boot.cmd) but it has no effect. My monitor works with these parameters on Hardkernels Ubuntu 18.04 image. What else do I need to do?

I use DietPi on my Odroid C2. I post here because the developer mentioned that the DietPi image is based on the Armbian kernel and he suggested posting here. When I attach the R5 to a USB port of my Odroid C2 it is not recognized. lsusb and dmesg do not show it. On my Ubuntu 22.04 PC it does show up. Looked around and finally found an old post on this forum that mentions a bug with the C2 in recognizing USB devices. The mentioned workaround is to add a second USB device and reboot the device. I added an USB drive and both are now recognized, initialized and working after a reboot. (When removing one of the devices it again doesn’t stick after a reboot.) I can not find more information on this. It seems this problem isn't solved? Regards, Joost

Hi there, I've an odroid C2 device used for home automation and running armbian (uname -a) : Linux odroidc2 4.19.69-meson64 which is running stable with no problem. Yesterday, I've downloaded a fresh image of latest armbian for odroid C2, named Armbian_21.02.1_Odroidc2_buster_current_5.10.12.img.xz. Put it on a new SD card and booted. It booted correctly but I've NO network. The LAN chip doesnt work at all, altough it appear in the device list I've theses entries in dmesg: [ 2.217600] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found [ 2.217611] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found [ 2.217694] meson8b-dwmac c9410000.ethernet: PTP uses main clock [ 2.218292] random: fast init done [ 2.218418] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37 [ 2.218426] meson8b-dwmac c9410000.ethernet: DWMAC1000 [ 2.218431] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported [ 2.218435] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported [ 2.218439] meson8b-dwmac c9410000.ethernet: COE Type 2 [ 2.218443] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported [ 2.218446] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported [ 2.218538] meson8b-dwmac c9410000.ethernet: Normal descriptors [ 2.218543] meson8b-dwmac c9410000.ethernet: Ring mode enabled [ 2.218547] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer ... [ 10.568311] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.568329] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.615619] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.615634] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.716190] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.716207] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 10.735509] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1 [ 10.735535] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) the first message I see when I boot (while plug in the power) is: Net: Could not get PHY for ethernet@c9410000: addr -1 No ethernet found The device is working with older armbian version but not the latest ? Could anyone look at it because the image available for download seem's broken and should not be distributed like this. I've reverted back to my old image (that's why I don't have the full log) and lost my week end on it, trying to sort it out without success. Could this be related to the .dtb ?? Thanks you

I would like to permanently change at start up the UART permissions of /dev/ttyAML0 to give user, read write permissions always. I can do this with the usual "chmod" command but this gets reset after every boot and sometimes also during normal operations. Can somebody direct me to how this can be done please? xuraax

I have an C2 and an old VU7 (800x480p60hz) https://wiki.odroid.com/accessory/display/vu_series/vu7/vu7#tab__odroid-c2 that I was hoping to use for a mini kiosk. Was able to run the older Hard Kernel supplied images with the uboot boot.ini updates suggested above to change disable auto detect, fix the resolution, and set to DVI rather than HDMI mode. When I loaded the latest Focal image from Armbian when I have the screen switched on then the kernel faults and reboots. ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7b06a000, end 7bf49d63 ... OK Loading Device Tree to 000000007aff8000, end 000000007b069fff ... OK Starting kernel ... GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0; TE: 59543 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton I assume all I should need to do is update the /boot/boot.cmd, run `mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr` and the boot.scr should be updated. Also set: setenv disable_vu7 "false" But that variable isn't being used anywhere in the boot.cmd so I don't think it is being applied.

This week we discontinued the default 3.x kernel for the Odroid C2, and are working on the 4.18/4.19 kernels. A few odds and ends have come up, the biggest one appears to be the gpio-hog in the C2 device tree somehow not working, causing the USB hub on the board to never be powered on. root@odroidc2:/sys/class/gpio# cat /sys/kernel/debug/gpio gpiochip1: GPIOs 378-496, parent: platform/c8834000.periphs:pinctrl@4b0, periphs-banks: gpio-392 ( |mdio-reset ) out hi gpio-407 ( |reset ) out hi gpio-422 ( |cd ) in lo gpio-465 ( |TFLASH_VDD ) out hi gpiochip0: GPIOs 497-511, parent: platform/c8100000.bus:pinctrl@14, aobus-banks: gpio-500 ( |TF_IO ) out lo gpio-501 ( |usb-hub-reset ) out hi gpio-502 ( |USB_OTG_PWR ) out hi gpio-510 ( |c2:blue:alive ) out lo The hog claims it is there, but I get no power to the port. The other is the HDMI output becoming extremely fussy about the sort of monitor it's been given. [update] On the NanoPi K2 I actually get a crash on boot with my HDMI --> DVI adapter monitor. With both monitors, if plugged in after boot, desktop displays (on C2 only the pure HDMI monitor will display at all), but a fault occurs: FYI @Neil Armstrong

according to here 5.13 is latest kernel https://www.armbian.com/odroid-c2/ but when I issue: sudo apt-get update && sudo apt-get dist-upgrade -y I'm still on 5.10....

Hi , i buiild a SPDIF connector like shown here: https://forum.odroid.com/viewtopic.php?t=21477 it uses the J7 SPDIF output which is connected to HDMI. On coreelec i can clearly see a HDMI soundcard output with aplay -L , i dont see that on armbian.... Is odroid c2 spdif output on armbian working ? why do i not see this soundcard that f.e. libreelec is showing ( i have 2 odroid c2s , one is running coreelec in my living room with HDMI connector working) im using a little older armbian distro since the latest has ethernet issues on C2 (im using 20.11 , kernel 5.9.10 debian edition ) regards, Simon

as described in: https://gitlab.freedesktop.org/mesa/mesa/issues/2377 it's possible to use meson HW video codec now, but in the URL, not very clear, does any one know how to use it?

Hi, I'm getting a random packet loss on the ethernet connection. When pinging, about 6-8% pings are lost, the ssh connection sometimes freezes for a moment. Things I've tried so far: Disabled NetworkManager, added eth0 in /etc/network/interfaces with a static ip4 address Disabled EEE for eth0 Replaced ethernet cable Plugged into different switch None of them made something better. My C1 & C4 with the same Armbian Buster version/release don't have this issue. How to investigate deeper in this issue?