Jump to content

Search the Community

Showing results for tags 'odroidxu4'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. Hello, for quite some time I have noticed that it seems impossible to build just the kernel, an image is built every time. I am using the following command: ./compile.sh BOARD=odroidxu4 BRANCH=current RELEASE=bullseye BUILD_MINIMAL=yes BUILD_DESKTOP=no BUILD_ONLY="kernel" KERNEL_CONFIGURE=no USE_CCACHE=no KEEP_KERNEL_CONFIG=no DEB_COMPRESS=xz Additionally, output/debs seems not to be cleaned, despite documentation indicating this should happen with default CLEAN_LEVEL. Am I doing something wrong? Or does documentation need updating? Thanks!
  2. Hi, I have been recently working on a couple of extensions: lvm and cloud-init I forked off "v23.11.2" tag when creating my branches, since they are extensions, and wont alter the framework much. Today I noticed that OdroidUX4 is not building, but it was building last week. A patch seems to be failing. I guess it is a kernel/driver patch. Then my question is: is it possible that, on the same tag (v23.11.2), builds break? I am starting to think that the tag is only for the build process/patch set, but excludes, for example a reference to kernel code. I suppose then the situation is that a kernel update has "broken" a patch, would that be the case? If so, is it possible to also checkout a particular working kernel for the sake of a stable dev environment? How do you normally do? R.
  3. Hello, I use an Odroid XU with Armbian and Webmin as a NAS drive. I have 6 hard drives (GPT format) connected. Under an old Linux version I was able to put the hard drives into standby with /etc/ rc.local (hdparm -S). Since I started running the system with Armbian, standby no longer works. A query via hdparm says "Standby", but the disks are still spinning. Am I fundamentally doing something wrong? Thank you!
  4. I had to roll back and use apt hold on the 2 corresponding packages to remain on the "good" LTS kernel 5.4.253 that supports fstrim on extremely popular Crucial SSDs that support it. It's impossible to get the maintainer Joe to reply. Is there a triage way to have someone contact him and make him aware of this issue? I have zero complaints about his work, but SATA TRIM commands are a must have on SBCs that have drive bays. It dramatically increases lifetime of NAND based storage devices. Please tell me what to do. I found filing a simple bug report would be counter productive as I want to investigate why later Kernels are either compiled without support for it or what causes later Kernels to break. We are talking about a feature here that is available in every Desktop *NIX OS.
  5. I'm using Armbian bullseye on an Odroid HC2 with 2 GB of RAM with OpenMediaVault. Its memory usage used to be around 10% before starting any docker services, and a cool 50-60% while running things like Nextcloud, Vaultwarden etc. It used to jump to around 80% when some headless Chromium processes ran intermittently, but overall, it's been quite stable. I don't recall to make any significant changes to the system, yet suddenly the baseline memory usage jumped to around 50%, making my system extremely slow and unstable, with service and system restarts now occuring several times a day. I couldn't extract any useful clue about what's using all that RAM, with `systemd-cgtop -m` showing system.slice using half my memory, without any services therein apparently making up that amount. Unfortunately, I can't make comparisons of `/proc/meminfo`, output of `free` or any other method relative to the before-state, because I obviously haven't monitored these until it became an issue, and now I can't restore the normal state. How would I go about addressing this problem?
  6. I just installed latest Jammy on XU-4 and it was running fine off SD. Then I did nand-sata-install and you can see below what happened. This used to work fine with older versions. sudo hdparm -Tt /dev/sda /dev/sda: Timing cached reads: 2 MB in 5.54 seconds = 369.48 kB/sec Timing buffered disk reads: 2 MB in 10.33 seconds = 198.19 kB/sec
  7. I already posted the question in the Odroid forum. I decided to post it here too since it may be more inherent to the Armbian OS. I used both Armbian_23.02.3_Odroidxu4_bullseye_current_5.4.239.img from the odroidxu4 archive and Armbian-unofficial_23.11.0-trunk_Odroidxu4_bullseye_current_6.1.63 generated from the Armbian build script. (Base CLI Image). After flashing the former image and then installing OMV6, this is the output that OMV6 gives me when installing the openmediavault-wireguard plugin: Then, after rebooting, here is the output of minicom: And the ODROID doesn't go further. It stays stuck at "BOOTP broadcast 1". Next, I tried to repeat the same steps with the image generated from the Armbian build script. Here is the output of OMV6 when installing openmediavault-wireguard: And here is the output of minicom: What could be the issue? Thanks in advance for your help.
  8. On a fresh armbian bullseye debian install on an odroidhc2, the only change is I installed NCP through armbian softy and a reboot. My sudo account works, but if I try to sign into root it says account unavailable. How can I fix this?
  9. I am using an odroid HC2 as home NAS for some years now. Software is armbian/XU4 in debian flavour. At the moment I am running bookworm (which was updated from buster to bullseye and then to bookworm - I know its not supported but it worked fine. And the problem described here started only some month after the last update). Some days ago I wanted to reboot the unit but it was stuck in the boot process. Not available by ssh or any other services. I then found out that the boot stopped because my hard disk could not be mounted from ftsab (while the sd card as root file system could be mounted). After commenting out the line it boots normally. And when logged in by ssh I can mount the hard disk without any problem. As a workaround I put the "noauto" option in fstab and mount the drive after a sleep of some seconds from rc.local. That works fine but I am wondering what is causing the problem? Has something in armbian changed so that mounting on boot time doesnt work anymore? Maybe some problem with initializing the sata controller? Or is this a sign of degrading hardware? Any hints welcome. Juergen
  10. Hi guys, this is something that I would like to achieve if feasible. I remember that other OS like "RetroPie Arena" support GPU acceleration, thanks. Any documentation to read? Thanks! 🙏
  11. Hello, my Odroid HC2 was working flawlessly for years but since 1-2 weeks it keeps crashing/freezing and I don't know why. If I cut power and repower it, it works fine for a while but then trying to reach it via ssh, or accessing the harddrive via smb share, or opening a webinterface fails. I checked the microsd card with armbianmonitor -c "$HOME" and it showed it's fine. I can only provide the logs: https://paste.armbian.com/cibowaquyi and hope someone can check them and reply 🙏. I don't know what to look for in the logs that could be wrong... One last thing I noticed, after I ssh to it amongst other things I'm greeted with this: RX today: Error: Unable to read database "/var/lib/vnstat/veth1251466": No such file or directory. I never noticed that all the time before.
  12. Hello, I have been struggling with this for a while, found some replies on the other communities but I simply cannot get Wireguard up and running on my Odroid HC2 with Armbian. Running... echo "deb http://deb.debian.org/debian/ unstable main" > /etc/apt/sources.list.d/unstable-wireguard.list printf 'Package: *\nPin: release a=unstable\nPin-Priority: 90\n' > /etc/apt/preferences.d/limit-unstable apt update apt install -y linux-headers-odroidxu4 wireguard yields... Loading new wireguard-0.0.20181218 DKMS files... dpkg: warning: version '3.10.106-odroidxu4 4.19.14' has bad syntax: invalid character in revision number Building for 4.19.14-odroidxu4 Module build for kernel 4.19.14-odroidxu4 was skipped since the kernel headers for this kernel does not seem to be installed. Do I really need to compile Wireguard from source? :-(
  13. Hi guys, I'm running out of ideas... Following situation, I use since years Armbian Bullseye on the HC2 with a 3,5" HDD, with OMV and Syncthing. Now I replaced the HDD with a SDD, copied and work without issues with the old HC2 board. I have as well a HC1 board here, so ideal solution is, change SD and SSD to the HC1 and my expectation is, should work. For sure the MAC would change, but seems the network connection isn't working at all. At least my expectation is, there should be a new address received via DHCP (setting is DHCP). Did I miss some important Armbian specific settings? Maybe there is something set in first run? Both board run seamless with a new flashed Armbian SD card, but change the working SD cad from HC2 to HC1 does not work. Any ideas?
  14. Is there a repository with older Armbian images available? I'm looking to install OMV6 on my Odroid HC1 (XU4), when I get Armbian Bookworm installed OMV scripts says to use Buster or Bullseye, but I cannot find an Armbian Bullseye image anywhere. I'm not super proficient with Linux (I know enough to get myself in trouble) so compiling my own image is not something I think I can do. Any help would be greatly appreciated. Edit: Nevermind...I'm an idiot...didn't notice the GIANT button for Archived Images. Apologies. Thanks, Robert
  15. As bookworm is stable now I want to update my odroid HC2 from bullseye to bookworm? Any experiences welcome. I know this is not supported. But in principle it should work. I did the update from buster to bullseye and that worked perfectly (see link to threat below). I would just do the same for the new update. But maybe there is one special fact to remember that wasn't necessary for the last update. Jürgen
  16. Hi guys, which is the Armbian recommended way to jump to a newer Userspace version? A fresh install ? A regular system upgrade ? Thanks in advance, 🙏 F.
  17. Greetings, As the subject says... CEC not detected in kernel, cec-client throws errors, nothing I tried worked. root@odroidxu4:~# uname -a Linux odroidxu4 5.4.239-odroidxu4 #1 SMP PREEMPT Thu Mar 16 15:52:54 UTC 2023 armv7l GNU/Linux root@odroidxu4:~# cec-client -l libCEC version: 6.0.2, compiled on Linux-4.19.0-14-armmp-lpae ... , features: P8_USB, DRM, P8_detect, randr, Exynos, Linux, AOCEC Found devices: 1 device: 1 com port: Linux vendor id: 0000 product id: 0000 firmware version: 0 type: Linux root@odroidxu4:~# cec-client No device type given. Using 'recording device' CEC Parser created - libCEC version 6.0.2 no serial port given. trying autodetect: path: /dev/cec0 com port: Linux opening a connection to the CEC adapter... DEBUG: [ 468] Broadcast (F): osd name set to 'Broadcast' DEBUG: [ 468] CLinuxCECAdapterCommunication::Open - m_fd=3 bStartListening=1 DEBUG: [ 468] CLinuxCECAdapterCommunication::Open - ioctl CEC_ADAP_G_PHYS_ADDR - addr=ffff WARNING: [ 468] CLinuxCECAdapterCommunication::Open - physical address is invalid DEBUG: [ 468] CLinuxCECAdapterCommunication::Open - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0 DEBUG: [ 468] CLinuxCECAdapterCommunication::Open - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=1 NOTICE: [ 469] connection opened DEBUG: [ 469] << Broadcast (F) -> TV (0): POLL TRAFFIC: [ 469] << f0 ERROR: [ 469] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 TRAFFIC: [ 469] << f0 ERROR: [ 469] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 DEBUG: [ 469] >> POLL not sent DEBUG: [ 469] TV (0): device status changed into 'not present' DEBUG: [ 469] registering new CEC client - v6.0.2 DEBUG: [ 469] SetClientVersion - using client version '6.0.2' NOTICE: [ 469] setting HDMI port to 1 on device TV (0) DEBUG: [ 469] << Broadcast (F) -> TV (0): POLL TRAFFIC: [ 469] << f0 ERROR: [ 469] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 TRAFFIC: [ 469] << f0 ERROR: [ 469] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 DEBUG: [ 469] >> POLL not sent DEBUG: [ 469] SetConfiguration: double tap timeout = 200ms, repeat rate = 0ms, release delay = 500ms DEBUG: [ 469] detecting logical address for type 'recording device' DEBUG: [ 469] trying logical address 'Recorder 1' DEBUG: [ 469] << Recorder 1 (1) -> Recorder 1 (1): POLL DEBUG: [ 469] CLinuxCECAdapterCommunication::Process - CEC_DQEVENT - CEC_EVENT_STATE_CHANGE - log_addr_mask=0000 phys_addr=ffff TRAFFIC: [ 469] << 11 ERROR: [ 470] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 TRAFFIC: [ 470] << 11 ERROR: [ 470] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 DEBUG: [ 470] >> POLL not sent DEBUG: [ 470] using logical address 'Recorder 1' DEBUG: [ 470] Recorder 1 (1): device status changed into 'handled by libCEC' DEBUG: [ 470] Recorder 1 (1): power status changed from 'unknown' to 'on' DEBUG: [ 470] Recorder 1 (1): vendor = Pulse Eight (001582) DEBUG: [ 470] Recorder 1 (1): CEC version 1.4 DEBUG: [ 470] AllocateLogicalAddresses - device '0', type 'recording device', LA '1' DEBUG: [ 470] CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0 DEBUG: [ 470] CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=1 DEBUG: [ 470] Recorder 1 (1): osd name set to 'CECTester' DEBUG: [ 470] Recorder 1 (1): menu language set to 'eng' NOTICE: [ 470] setting HDMI port to 1 on device TV (0) DEBUG: [ 470] << Recorder 1 (1) -> TV (0): POLL TRAFFIC: [ 470] << 10 ERROR: [ 470] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 TRAFFIC: [ 470] << 10 ERROR: [ 470] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 DEBUG: [ 470] >> POLL not sent DEBUG: [ 470] Recorder 1 (1): physical address changed from ffff to 1000 DEBUG: [ 470] << Recorder 1 (1) -> broadcast (F): physical address 1000 TRAFFIC: [ 470] << 1f:84:10:00:01 ERROR: [ 470] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 TRAFFIC: [ 470] << 1f:84:10:00:01 ERROR: [ 470] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64 root@odroidxu4:~# lsmod Module Size Used by rfkill 24576 1 cpufreq_powersave 16384 0 cpufreq_userspace 16384 0 cpufreq_conservative 16384 0 zstd 16384 8 joydev 20480 0 input_leds 16384 0 exynos_gsc 32768 0 s5p_mfc 135168 0 s5p_jpeg 45056 0 v4l2_mem2mem 20480 2 s5p_jpeg,exynos_gsc videobuf2_dma_contig 20480 3 s5p_jpeg,s5p_mfc,exynos_gsc mali_kbase 364544 0 videobuf2_memops 16384 1 videobuf2_dma_contig videobuf2_v4l2 24576 4 s5p_jpeg,s5p_mfc,exynos_gsc,v4l2_mem2mem videobuf2_common 40960 5 s5p_jpeg,s5p_mfc,exynos_gsc,v4l2_mem2mem,videobuf2_v4l2 s5p_cec 16384 0 evdev 24576 4 exynos_gpiomem 16384 0 zram 28672 2 sunrpc 315392 1 ip_tables 24576 0 ipv6 462848 42 autofs4 36864 2 usbhid 49152 0 gpio_keys 20480 0 root@odroidxu4:~# zgrep CEC /proc/config.gz CONFIG_TABLET_USB_ACECAD=m CONFIG_CEC_CORE=y CONFIG_CEC_NOTIFIER=y CONFIG_MEDIA_CEC_SUPPORT=y # CONFIG_MEDIA_CEC_RC is not set # USB HDMI CEC adapters # CONFIG_USB_PULSE8_CEC is not set # CONFIG_USB_RAINSHADOW_CEC is not set # CONFIG_VIDEO_VIVID_CEC is not set CONFIG_CEC_PLATFORM_DRIVERS=y # CONFIG_VIDEO_CROS_EC_CEC is not set # CONFIG_CEC_GPIO is not set CONFIG_VIDEO_SAMSUNG_S5P_CEC=m # CONFIG_DRM_DP_CEC is not set Please help! Thanks in advance.
  18. Hi, I want to make adc pcm1804(simple adc clock + i2s) work with odroid, and manage it by alsa. As I understand, I should add a codec for pcm1804, driver to work with alsa, and device tree overlay. Please, tell me where can I get an example of this, or at least smth to use as a reference ?
  19. HC2 here. Two last 6.1 kernels broke alsa : hw not accessible anymore. Aplay -l lists audio outputs but none may be used. Looks like an omission on kernel flags.. Reverted to Armbian Bullseye : exact same config, but working.
  20. Hi, I have Armbian 23.05.0-trunk Bullseye with Linux 5.4.239-odroidxu4 on my XU4. I recently bought a USB Bluetooth adapter using RTL8761A. But the firmware is not present in rtl_bt. I want the Bluetooth adapter to work for Home Assistant. I am quite new to this stuff, so if you need any additional information i will provide. Thanks in Advance.
  21. Hi, I've several Odroid HC1 boards (forming a kubernetes cluster of 8 nodes) currently running Armbian Buster Minimal image. I would like to upgrade the cluster (node by node) to Armbian Bullseye Minimal but I faced the following issue when I tried to reinstall the 1st node: - Used image: https://mirrors.dotsrc.org/armbian-dl/odroidxu4/archive/Armbian_23.02.1_Odroidxu4_bullseye_current_5.4.232_minimal.img.xz - Image flashed on SD card using BalenaEtcher - SD card plugged into the board + power up --> the OS is not booting (and not answering to ping) Here are the different tries I did: - I've tried to flash the image several times even using different SD cards and boards --> same issue, unable to boot - I've tried a rollback and flash the previous version Armbian Buster minimal --> OK, able to boot (so I don't think the issue is at SD card or board level) - I've tried to flash the Armbian Bullseye non-minimal image (https://mirrors.dotsrc.org/armbian-dl/odroidxu4/archive/Armbian_23.02.1_Odroidxu4_bullseye_current_5.4.232.img.xz) --> with this image, I'm able to boot but after installing the OS on the SATA drive (using armbian-config : System / Install / Boot on SD, system on SATA), the OS is not booting anymore. Unfortunately, I don't have an USB UART adapter to provide logs. I'm suspecting an issue at image level as: After flashing the image on the SD card, I noticed that a file "qemu_fstype_20230226-211008_10215.core" is present at the root of the SD card ... maybe a sign showing that the image build failed or something like this !? Thank you for your support. I would be happy to provide additional information if needed. Adrien
  22. I STFW now for hours but didn't find a solution to this: When I login to my new installed OdroidXU4 image of armbian minimal it says: [ Kernel and firmware upgrades disabled: armbian-config ] # armbian-config gives: 'command not found' So I searched for a way, a hint, an instruction how to enable those 'Kernel and firmware upgrades' without having to install 'armbian-config' with no avail. How can I archive this? Thank you in advance; Gerry
  23. Hello, the new kernel versioning scheme consists of the latest git tag and several hashes: https://github.com/armbian/build/blob/main/lib/functions/artifacts/artifact-kernel.sh With boards like odroid-xu4 for which the upstream git is only updated occasionally, this leads to two problems: 1. the generated version is lower than what is currenty getting shipped: `5.4.228-S3043-De511-P0a53-C0750H6842-Bb436` vs `23.02.2` 2. it cannot be guaranteed that the versions go up reliably: 5.4.232 is `5.4.228-S3043-De511-Pc02c-C0750H6842-Bec1c` and 5.4.233 is `5.4.228-S3043-De511-P0a53-C0750H6842-Bb436` While I can understand using the kernel version than armbian version is better, this currently only works if every version is tagged. Is there a variable which I could use to get the old behaviour back? Thanks.
  24. Hi, Just yesterday I had to reinstall my server (odroid-xu4 based). I've been using Armbian a few years now. But this time, no matter if just after a fresh install or after firmware and packages update/upgrade, it fails to reboot I no long have the release number of the previous install I've used, but tryied this time with 22.11.1 and 23.01.1 and both fail the same way After a few debuging it turned out to be that the /etc/fstab entry for the microSD starts just with the UUID code, but adding the "UUID=" string to the line begin, solves the issue Don't know when the bug began or where to properly report the bug, so I started this thread, but I'll be glad to help if more info is needed Thanks in advance!
  25. Unable to start docker after update, due to apparmor I used armbian-config's "edit boot-enviroment", added "extraargs=apparmor=0" and after a reboot I still get: docker start portainer Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output: error: exec: "apparmor_parser": executable file not found in $PATH Error: failed to start containers: portainer armbianmonitor: https://paste.armbian.com/ebuburoxeh
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines