Jump to content

Search the Community

Showing results for tags 'odroidhc4'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

Categories

  • Official giveaways
  • Community giveaways

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. I recently installed the latest precompiled Bullseye image on my Odroid HC4 and plugged in two Samsung 870 QVO 8TB SSDs. After configuring the system I noticed that they were not present, checking output from `/var/log/syslog` I can see the "SATA Llink down" messages for both channels. After several reboots I tried seating them after booting, both drives cause some messages about a soft reset failing, then eventually within 30-60 seconds are recognised until I reboot. I then one Crucial MX500 4TB SSDs which was recognised at first, after some reboots it would no longer be present, or strangely, be present with a much lower capacity (1TB). When seating the drive after boot, it instantly becomes available/recognised. I went back to trying an old 250GB Kingston SSD (SA400S37240G) which is detected every single boot, just fine. The same is also true for some old Seagate/Western Digital HDDs. I eventually tried some other distros, namely DietPI which behaves exactly the same. I eventually tried all available precompiled Armbian 5.x and 4.x images but they all behaved the same way. Finally I tried the Hardkernel Odroid Ubuntu image, and this seems to work fine, for all of the drives listed above. Noting it's a 4.9 kernel, I assumed I might get the same functionality from Armbian if I compiled it myself, however the build system seems specifically geared toward current/edge, judging by the configs, this is usually 6.x and 5.x. After some fiddling I was able to start the process of building a 4.9 image, but due to other expectations the compilation fails much later on. I've seen posts here and elsewhere online about faulty NCQ for the Samsung drives, apparently fixed with my firmware version and also blacklisted by the driver anyway. I've seen posts about the Crucial MX500 and other drives appearing and disappearing between boots. Those people had access to even earlier kernels and managed to downgrade to keep things working, but they are no longer available. So I'm at a loss. Any advice would be appreciated. armbianmonitor: https://paste.armbian.com/gexecuzuja
  2. After last system upgrade I got, Package armbian-bsp-cli-odroidhc4-current is kept back because a related package is kept back or due to local apt_preferences(5). and (translate from french) sudo apt install --only-upgrade armbian-bsp-cli-odroidhc4-current ... The following packages contain unmet dependencies: armbian-bsp-cli-odroidhc4-current : Dépend: base-files (>= 23.11.1) E: Unable to fix problems, bad packets are in "keep as is" mode. How to fix this issue? uname -a Linux xxxxx.xx 6.1.63-current-meson64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 GNU/Linux apt-cache show base-files Package: base-files Essential: yes Priority: required Section: admin Installed-Size: 271 Maintainer: Armbian Linux <info@armbian.com> Architecture: arm64 Version: 23.8.1-bullseye Replaces: base, dpkg (<= 1.15.0), miscutils ... Package: base-files Version: 11.1+deb11u8
  3. Running a home NAS using Armbian/meson bullseye and openmediavault. After apt upgrade today, my SATA disks are no longer spinning up or showing up in "fdisk -l". The system is on an SD card and still boots fine. This is what I'm seeing: [ 2.270633] scsi host0: ahci [ 2.272861] scsi host1: ahci [ 2.273074] ata1: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700100 irq 27 [ 2.273090] ata2: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700180 irq 27 ... [ 2.584971] ata1: SATA link down (SStatus 0 SControl 300) [ 2.896948] ata2: SATA link down (SStatus 0 SControl 300) Both disks work fine in another system. I have tried to upgrade the firmware, no change. Moved to nightly and booted into linux-image-edge-meson64 (6.1.0), same issue. Next, I tried booting into kernel 5.19.17-meson64, but the problem persists. I wonder what has happened here? Could it be a userspace problem (since I didn't downgrade userspace here, only the kernel)? Any hints very much welcome!
  4. Hi! I have been using Armbian for long, but I am new to the Development/build system. I have however set the environment and I can build images. Now, I want to create a custom Armbian image with the following customization: - Separate ext2 partition for boot - second partition for LVM - Root Filesystem in Logical Volume and fixed size. - Cloud Init, with an extra partition for NoCloud Datasource. I see in the documentation how to install new packages, but not how to partition the SD card. How can I change the partitioning? On the other hand. Can I just build an image without compiling the Kernel? I have no interest in kernel customization in this case, I would rather install the distribution's default without compiling. Is it possible?
  5. Hi, recently downloaded image for may odroid hc4. There was big sign with 23.5 version so i used this. Everything went fine. Set up lamp nextcloud server but then i wanted to set firewall with geoblock(xt_geoip) but can't go through basic steps. On my old version it workerd. With some addition steps but did. Problem is with linux headers. I found out there is some weird "desync" with packages versioning? I downloaded image for 23.5 and repo seems to be on 23.2. Linux kernel on fresh image is 6.1.30 and in repo is 6.1.11. Even armbian-config is installing headers for 6.1.11 and can't compile my stuffs. I just wanted to downgrade kernel to 6.1.11, but i think it may be worth to ask here first if there is no some better solution. Maybe i just did broke something? But I am not sure if there was an option to do so. Just checked hostnamectl and it shows 23.08.0... Static hostname: odroidhc4 Icon name: computer Machine ID: bb96d7c6a69c4d53802181498c890c56 Boot ID: c6223f2f9d8b49238cbf77cbb183c538 Operating System: Armbian 23.08.0-trunk bookworm Kernel: Linux 6.1.30-meson64 Architecture: arm64 # cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=odroidhc4 BOARD_NAME="Odroid HC4" BOARDFAMILY=meson-sm1 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=508a701 VERSION=23.05.1 LINUXFAMILY=meson64 ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image FORCE_BOOTSCRIPT_UPDATE= VENDOR=Armbian REVISION=23.05.1 BOOTSCRIPT_FORCE_UPDATE="no" BOOTSCRIPT_DST="boot.cmd" BRANCH=current # cat /etc/armbian-image-release # PLEASE DO NOT EDIT THIS FILE BOARD=odroidhc4 BOARD_NAME="Odroid HC4" BOARDFAMILY=meson-sm1 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=508a701 VERSION=23.05.1 LINUXFAMILY=meson64 ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image FORCE_BOOTSCRIPT_UPDATE= VENDOR=Armbian REVISION=23.05.1 BOOTSCRIPT_FORCE_UPDATE="no" BOOTSCRIPT_DST="boot.cmd" IMAGE_UUID=114fd58e-d496-4ae9-9fb5-9342d4c75b31 Have no idea what is going on here. On one hand i have 23.05 and on the other whole repository is for 23.02. Is this 23.05 suitable at all? Sorry if i cam deeply wrong. I am not familiarly with debian based distros.
  6. Hi I am looking for the bullseye image for odroid hc4. Is there an archived version? It's needed for OMV as it is incompatible with newer versions: https://wiki.omv-extras.org/doku.php?id=omv6:armbian_bullseye_install Appreciate any help Alex
  7. Been having an issue where my idle temps are >60C The fan will spin for maybe a second or two and then turn off for 10-20 seconds Checking /sys/class/hwmon/hwmon2/pwm1 and it is set to 0 even though my MINPWM is set to 90 Even if I manually tee 90 to pwm1 it will eventually reset to 0 even with fancontrol turned off So something resetting without my input... fan1_input does read fan speed & pwm1_enabled is set to 1 lsof & auditd do not have any info as to what is overwriting the file Only way I can get the fan to stay on is to loop the tee command for a few seconds and then it is on that one speed Turning fancontrol back on works for a while and changes speed as expected but eventually pwm1 goes back to 0 I found that when pwm1 is between 90-125 it does runs fine but once higher than 125 it resets Then tried 125 as minimum and the working range becomes 125-160 before reset Then tried 170 as minimum and the working range becomes 175-220 before reset Could the fan be dying and the voltage/load send a signal to the kernel to say "shut down fan"? fancontrol INTERVAL= 10 DEVPATH= hwmon0=devices/virtual/thermal/thermal_zone0 hwmon2=devices/platform/pwm-fan DEVNAME= hwmon0=cpu_thermal hwmon2=pwmfan FCTEMPS=hwmon2/pwm1=hwmon0/temp1_input FCFANS=hwmon2/pwm1=hwmon2/fan1_input MINTEMP=hwmon2/pwm1=54 MAXTEMP=hwmon2/pwm1=65 MINSTART=hwmon2/pwm1=90 MINSTOP=hwmon2/pwm1=110 MINPWM=hwmon2/pwm1=90 MAXPWM=hwmon2/pwm1=240 tee command to force fan spin (only way to avoid resetting to zero), ctrl+c after a few seconds while true; do echo 90 | sudo tee /sys/class/hwmon/hwmon2/pwm1; done
  8. This isn't a question but more of a tutorial. I wanted to install Debian Bookworm with latest kernel to my odroid. I'm documenting my steps and experience here in case you stumble across it and find it useful. At the time of writing, the link on the Odroid HC4 site to download Bookworm is broken. No worries, I thought, I'll just build it myself, doesn't seem too hard. My host system is Windows 10 where I'm building in a WSL 2 Ubuntu. It has GCC 9.3.0 installed. Follow the usual instructions here. My compilation command is: ./compile.sh KERNEL_CONFIGURE= BUILD_MINIMAL=no BUILD_DESKTOP=no EXTERNAL_NEW=prebuilt BOARD=odroidhc4 BRANCH=edge RELEASE=bookworm SYNC_CLOCK=no EXTRAWIFI=no KERNEL_CONFIGURE=yes BUILD_KSRC=no I ran into several problems, and fixed them as follows: Certificates outdated. I hadn't used the WSL2 in a while so the certs for github had expired. I found these commands on stackoverflow: sudo apt-get install ca-certificates sudo mkdir /usr/local/share/ca-certificates/cacert.org sudo wget -P /usr/local/share/ca-certificates/cacert.org http://www.cacert.org/certs/root.crt http://www.cacert.org/certs/class3.crt sudo update-ca-certificates Some error while applying the patch for rtw88 - something to do with Realtek WIFI drivers. Not exactly sure why, and I won't be using one of those anyway, so I just made the patch zero size (deleting it causes it to get redownloaded I think). The compile script will complain about an invalid patch but you can ignore it. truncate -s 0 patch/misc/rtw88/6.4/001-rtw88-linux-next.patch Another Realtek wifi driver issue - this time something in the rtl88x2bu driver that wouldn't compile due to a missing define. Again truncate the patch, or just edit the kernel config to not build Realtek drivers. patch/misc/wireless-rtl88x2bu-wireless-ignore-stale-kickoff-removal.patch Now we can follow along with the normal setup guide. I'm just using HDMI monitor and USB keyboard for now. It boots up and we can do the initial setup just fine. Regarding fancontrol: The main HC4 page says to set it up manually. However, it seems to be automatically working for me since the fan is off at idle. The /etc/fancontrol also seems to contain some content already. For me, it was prefilled with: root@odroidhc4:~# cat /etc/fancontrol # Default config for the droid HC4 -- adjust to your needs (MINTEMP=40) INTERVAL=10 DEVPATH=hwmon0=devices/virtual/thermal/thermal_zone0 hwmon2=devices/platform/pwm-fan DEVNAME=hwmon0=cpu_thermal hwmon2=pwmfan FCTEMPS=hwmon2/pwm1=hwmon0/temp1_input FCFANS= hwmon2/pwm1=hwmon2/fan1_input MINTEMP=hwmon2/pwm1=40 MAXTEMP=hwmon2/pwm1=60 MINSTART=hwmon2/pwm1=150 MINSTOP=hwmon2/pwm1=30 MAXPWM=hwmon2/pwm1=180 I guess this is fine for now. Let me know if this helps you or if you have a related question!
  9. I've just install Armbian_23.02.2_Odroidhc4_jammy_current_6.1.11.img to my new odroid hc4 but after copy sd to sata by using nand-sata-install the system stuck dureing boot on an "emergency mode error".
  10. Dear All, I got a zfs upgrade today, I updated the packages but then it failed to build the module, thus I tried to update kernel and firmware but it failed the same: hecking whether CONFIG_MODULES is defined... no configure: error: *** This kernel does not include the required loadable module *** support! *** *** To build OpenZFS as a loadable Linux kernel module *** enable loadable module support by setting *** `CONFIG_MODULES=y` in the kernel configuration and run *** `make modules_prepare` in the Linux source tree. *** *** If you don't intend to enable loadable kernel module *** support, please compile OpenZFS as a Linux kernel built-in. *** *** Prepare the Linux source tree by running `make prepare`, *** use the OpenZFS `--enable-linux-builtin` configure option, *** copy the OpenZFS sources into the Linux source tree using *** `./copy-builtin <linux source directory>`, *** set `CONFIG_ZFS=y` in the kernel configuration and compile *** kernel as usual. Building for 6.2.0-rc3-meson64 Building initial module for 6.2.0-rc3-meson64 Error! Bad return status for module build on kernel: 6.2.0-rc3-meson64 (aarch64) Consult /var/lib/dkms/zfs/2.1.9/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for initramfs-tools (0.140ubuntu13.1) ... update-initramfs: Generating /boot/initrd.img-6.2.0-rc3-meson64 update-initramfs: Converting to u-boot format Errors were encountered while processing: zfs-dkms uname -a Linux odroidhc4 6.2.0-rc3-meson64 #23.02.2 SMP PREEMPT Fri Feb 17 23:06:22 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux Any idea for fixing this issue? Thanks, 🙏 Freezr
  11. I'm trying to complete the installation of Armbian onto the HC4 (HC4-P if that changes anything). With a fresh SD card I run sudo dd if=Armbian_22.11.1_Odroidhc4_bullseye_current_5.19.17.img of=/dev/sdb status=progress plug in the card to the board, plug in the ethernet cable, hold down the boot switch, and plug it into power. It all seems to run correctly: I can SSH into the board and I complete the initial steps to set-up the installation (root pass, default shell, username, real name, and locale). However it does not seem as I can access the SPI FLASH device. Running the following commands from the HC4 page do not work as there are no mtd devices. root@odroidhc4:~# ls -ltr /dev/mtd* ls: cannot access '/dev/mtd*': No such file or directory Here's a paste of the files available under /dev: https://paste.tildeverse.org/?aa94ecb514ce9e50#E5qD2kbTFiQzaHRrgnBLfMw8PMfspfVsCFrxhPATYDyi
  12. Hi, I'm trying to use an external RTC clock (https://www.hardkernel.com/shop/rtc-shield/, battery is good) connected over I2C to wakeup the Odroid HC4 from poweroff (or if not possible from disk-suspend). To my surprise the rtc was already recognised (and also the device tree seems good) and I'm able to communicate with it, read it and set alarms for it. However, whenever I poweroff the device and try to turn on again it does not power on by itself (neither from poweroff, nor from disk suspend). Output from /proc/driver/rtc: rtc_time : 19:16:28 rtc_date : 2023-03-29 alrm_time : 19:07:00 alrm_date : 2023-04-29 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1 max user IRQ frequency : 64 24hr : yes When setting an alarm using (same result using rtcwake) echo `date '+%s' -d '+ 5 minutes'` | sudo tee /sys/class/rtc/rtc0/wakealarm which sets the RTC to the following: rtc_time : 19:18:17 rtc_date : 2023-03-29 alrm_time : 19:23:00 alrm_date : 2023-03-29 alarm_IRQ : yes alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1 max user IRQ frequency : 64 24hr : yes However, after power off (or suspend to disk), the Odroid HC4 does not turn on again.. After powercycling and the following boot, this is what /proc/driver/rtc looks like: rtc_time : 19:24:49 rtc_date : 2023-03-29 alrm_time : 19:23:00 alrm_date : 2023-04-29 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1 max user IRQ frequency : 64 24hr : yes which somehow has a wrong alarm date and the alarm_IRQ is no, and no alarm is pending. The OS I'm using is the following: Linux odroidhc4two 6.1.11-meson64 #23.02.2 SMP PREEMPT Sat Feb 18 00:07:55 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux Armbian 23.02.2 Jammy with Linux 6.1.11-meson64 Would be nice if someone could help me.. Best, trembel
  13. Hello, I’m in a pickle. I bought an Odroid HC4 a few months ago, setup a RAID-1 array and installed Nextcloud on it. At the time, I used `nand-sata-install` to move the system from the SD‑card to a partition of one of the HDD (/dev/sda1), out of RAID (/dev/md0), and leave the bootloader on the SD-card. I did not make a backup of this SD-card and, after rebooting today, I realised the SD-card was not functioning any more. No device I use (Sansa audio player with Rockbox, phone with Ubuntu Touch, Laptop with Ubuntu) would even detect it. I was thinking of using `nand-sata-install` again to only update the bootloader on the SD‑card but I’m afraid it will overwrite what is already on /dev/sda1 instead of only pointing to it. So here are my questions: 1. Would you know if `nand-sata-install` can be used safely to recreate the bootloader on the SD‑card without touching anything else? 2. Is there a manual for this tool, or are you able to explain how this would work? 3. Otherwise, is it possible to only copy a few files manually to the SD‑card to get the same result, and maybe update a few variables in some files? Thanks for any solution or pointer, I’ve searched on this forum and in other places without success so far.
  14. Hello, I'm looking to replace my x86 micro tower with a SBC, to mainly use it as a NAS and media player. On the hardware side, I would like to have a native SATA port (for the NAS hard disk), HDMI output and H.265 decoding (media player), at least 4GB of RAM (to be somewhat future-proof). Bluetooth is a plus to play some retro games Not sure about the OS storage: SD card, eMMC, an hard disk on another SATA port? At the moment I found two boards: the Radxa Rock 3A (with its DIY SATA over USB cable) and Odroid HC4. Both are supported by Armbian, but maybe there is a more recent board that I didn't find? Thanks.
  15. As the original thread, which was closed by moderator for obvious reason, did attract attention of few peoples having the same problem as me, it would be a waste not to follow up on this, I think. Let me sum up: I have two HC4, one bought in 8.2021 and other one 11.2022, both have two SSDs each. The older one after a kernel upgrade didn't see a second disk any more. I've just tried few kernels I could find with the following results: OK: Linux odroidhc4 5.12.10-meson64 #21.05.4 SMP PREEMPT Wed Jun 16 08:19:35 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux OK: Linux odroidhc4 5.13.12-meson64 #21.08.1 SMP PREEMPT Wed Aug 25 19:35:13 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Not OK:Linux odroidhc4 5.15.4-meson64 #21.08.6 SMP PREEMPT Mon Nov 22 11:46:10 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Couldn't find any kernel between 5.13.12 and 5.15.4, so it's not clear which is exact the version where the problem started. Here is what I found in /var/log/syslog: Nov 22 14:40:46 odroidhc4 kernel: [ 2.355049] ata1: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700100 irq 38 Nov 22 14:40:46 odroidhc4 kernel: [ 2.355060] ata2: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700180 irq 38 Nov 22 14:40:46 odroidhc4 kernel: [ 2.358363] libphy: mdio_mux: probed Nov 22 14:40:46 odroidhc4 kernel: [ 2.564017] libphy: mdio_mux: probed Nov 22 14:40:46 odroidhc4 kernel: [ 2.830521] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 22 14:40:46 odroidhc4 kernel: [ 2.830799] ata1.00: FORCE: horkage modified (noncq) Nov 22 14:40:46 odroidhc4 kernel: [ 2.830854] ata1.00: supports DRM functions and may not be fully accessible Nov 22 14:40:46 odroidhc4 kernel: [ 2.830860] ata1.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, max UDMA/133 Nov 22 14:40:46 odroidhc4 kernel: [ 2.830865] ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (not used) Nov 22 14:40:46 odroidhc4 kernel: [ 2.832778] ata1.00: Features: Trust Dev-Sleep Nov 22 14:40:46 odroidhc4 kernel: [ 2.833128] ata1.00: supports DRM functions and may not be fully accessible Nov 22 14:40:46 odroidhc4 kernel: [ 2.835140] ata1.00: configured for UDMA/133 Nov 22 14:40:46 odroidhc4 kernel: [ 2.835408] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 870 2B6Q PQ: 0 ANSI: 5 Nov 22 14:40:46 odroidhc4 kernel: [ 2.835890] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.836066] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Nov 22 14:40:46 odroidhc4 kernel: [ 2.836102] sd 0:0:0:0: [sda] Write Protect is off Nov 22 14:40:46 odroidhc4 kernel: [ 2.836108] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Nov 22 14:40:46 odroidhc4 kernel: [ 2.836159] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 22 14:40:46 odroidhc4 kernel: [ 2.850916] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.872432] sda: sda1 sda9 Nov 22 14:40:46 odroidhc4 kernel: [ 2.872842] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.886688] sd 0:0:0:0: [sda] Attached SCSI disk Nov 22 14:40:46 odroidhc4 kernel: [ 3.148738] ata2: SATA link down (SStatus 0 SControl 300) The newer HC4 doesn't show this problem which leads me to the conclusion: their hardware (firmware?) must differ. Asked about it on the HardKernel Forum, didn't get a clear answer (yet?). I don't know how to proceed i.e. where to look for further help. Any idea anyone? I'm to old for an advanced GIT class 😉 Thanks for your time. Chris
  16. Hey, I have a very similar problem here to this and this thread. I rebooted as the HC4 was already bugging me for a while to reboot on the motd (unattended-upgrades). Since the reboot, /dev/sdb is gone. It's a new Samsung SSD 870 EVO as well as in the other thread. The other (still running) one is a new Crucial MX500. I tried several Armbian kernels but no change. I went back to 5.10.57-meson64. There are no obviously burnt components on the device. There seem quite a few people with this problem. Any ideas? Thanks a lot! P.S. TP10 and TP11 are at 12V.
  17. The zfs-dkms included in Armbian_22.11.1_Odroidhc4_jammy in version 2.1.4 is to old for 5.19.17 kernel. It should be 2.1.6 like in Armbian_22.08.7. Loading new zfs-2.1.4 DKMS files... Building for 5.19.17-meson64 Building initial module for 5.19.17-meson64 configure: error: *** None of the expected "blk_queue_discard" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 http://paste.debian.net/1267188/
  18. Hi everyone! For about a week now, I have been using armbian 22.11.1 on my new Odroid HC4, which is my Nextcloud server. As alway, armbian is rock solid 😉 I have just a little question: Can one modify the information presented in htop? I'd like to have "CPU temperature" and "TX today" (meaning sent bytes) showing. The welcome screen already shows "CPU temperature" and "RX today". I know that the CPU temperature can be read here /etc/armbianmonitor/datasources/soctemp and but I can't find it in the htop-configuration under "available meters".
  19. Hi there, I have new HC4 (like 6 moths old) and since beginning I am struggling with reboot. I have latest Armbian Bullseye, and every time I make reboot, I need to power cycle to get it up. Is there any solution to that problem? I tried HK images, and they are rebooting but they are old so I want to be a bit modern but that is really annoying issue. Any help please? And Merry Christmas guys, thanks for the awesome distro even with that stupid problem.
  20. Some time ago a I was desperate to have ZFS on an Odroid HC4 and after some trying found Armbian 21.05.8 Buster with Linux 5.10.57-meson64 on which I could compile ZFS module. Then I moved everything from the SD card to filesystems in a ZFS pool. It boots from SD card, though. And has been working fine for several months. Recently I bought another HC4 and took the current Armbian image for it: Armbian 22.08.8 Jammy with Linux 5.19.17-meson64 Everything works fine. Tried this image on the older HC4 and it doesn't see the second SSD. In the syslog I found this message: ata1: SATA link down (SStatus 0 SControl 300) Is it a firmware problem? Googling hasn't help. Any idea anyone? Thanks for your time. Chris BTW Does anybody know how to disable the "Clear Screen" after the "Starting kernel" message? I would like to see what u-boot has to tell me, especially if I have some problems.
  21. Hi, i have armbian bullseye (headless) installed on my odroid-hc4. petitboot is disabled. The boot-partition lies on a sd-card while the root-partion is on a ssd. this configuration worked fine. After upgrading to armbian bullseye 22.11 the boot process stucks in initramfs cause the root file-system is not found anymore (ALERT! UUID=xxx does not exist. Dropping to a shell. The sd-card with the boot partition as well as the ssd with the root-partition can be mounted on another PC and seem to be flawless. the UUID shown in fstab and initramfs are identical. In initramfs ls /dev/sd* shows no devices while ls /dev/mm* shows the sdcard (mmcblk01...). I don't really know how the boot process works on an arm-system. What steps can I do to narrow down the problem. Thanks in advance. Hardware: odroid-hc4, samsung 870 EVO 1TB (sda), WD60EFZX (sdb), BS: armbian-bullseye with OMV 6.0.46-5 fs: ext4 no raid
  22. Hello, Bluetooth stopped working in kernel 5.19.17-meson64 #22.11.1 root@nextcloudpi:~# hciconfig hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:14 acl:0 sco:0 events:1 errors:0 TX bytes:3 acl:0 sco:0 commands:3 errors:2 root@nextcloudpi:~# hcitool dev Devices: root@nextcloudpi:~# dmesg | grep Bluetooth [ 10.005353] Bluetooth: Core ver 2.22 [ 10.010561] Bluetooth: HCI device and connection manager initialized [ 10.010582] Bluetooth: HCI socket layer initialized [ 10.010589] Bluetooth: L2CAP socket layer initialized [ 10.010621] Bluetooth: SCO socket layer initialized [ 10.273422] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [ 11.647454] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.647474] Bluetooth: BNEP filters: protocol multicast [ 11.647489] Bluetooth: BNEP socket layer initialized [ 15.326913] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [ 15.327136] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [ 15.327149] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [ 15.327153] Bluetooth: hci0: HCI Set Event Filter command not supported. [ 17.341929] Bluetooth: hci0: Opcode 0x c03 failed: -110 [42900.593231] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [42900.922097] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [42900.923021] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [42900.923040] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [42900.923044] Bluetooth: hci0: HCI Set Event Filter command not supported. [42902.934227] Bluetooth: hci0: Opcode 0x c03 failed: -110 [42905.073243] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [42905.661928] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround [42905.662099] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. [42905.662108] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported. [42905.662112] Bluetooth: hci0: HCI Set Event Filter command not supported.
  23. Hi, I'm trying to use ZFS but the kernel I'd like to use doesn't support loadable modules. The version is 22.08.4 at the moment (5.10.147) Can I use zfs-dkms on linux-image-current-meson64? And I'm curious why loadable modules are not supported by default for linux-image-current-meson64, is it same with every model? or probably Odroid-HC4 is one of the models in which loadable modules are not build by default? System diagnosis information: https://paste.armbian.com/ezisijedob Thank you, Gunwoo Gim
  24. Long story short: I used for about one year an odroid HC4 as NFS server and worked fine. Now I would add a player service for it. It mounts an HDMI port, so I tried to plug in the cable and it worked. I were able to see the video output but with no sound. I found there is no detected hdmi card: # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: ODROIDHC4 [ODROID-HC4], device 0: fe.dai-link-0 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: ODROIDHC4 [ODROID-HC4], device 1: fe.dai-link-1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: ODROIDHC4 [ODROID-HC4], device 2: fe.dai-link-2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 tried again after # alsactl init alsa-lib main.c:1541:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "axg-sound-card" "" "" "" "" Hardware is initialized using a generic method (alsactl -U init provides no error) The modules side looks fine to me (it was the same on 5.10.144, I tried moving to 5.19.10 with no result): # lsmod | grep snd snd_soc_hdmi_codec 24576 1 snd_soc_meson_axg_sound_card 16384 0 snd_soc_meson_card_utils 16384 1 snd_soc_meson_axg_sound_card snd_soc_meson_g12a_tohdmitx 20480 1 snd_soc_meson_codec_glue 16384 1 snd_soc_meson_g12a_tohdmitx snd_soc_meson_axg_tdmout 24576 1 snd_soc_meson_axg_frddr 36864 3 snd_soc_meson_axg_fifo 20480 1 snd_soc_meson_axg_frddr snd_soc_meson_axg_tdm_interface 16384 2 snd_soc_meson_axg_sound_card snd_soc_meson_axg_tdm_formatter 16384 2 snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_tdmout snd_soc_core 245760 10 snd_soc_meson_axg_tdm_formatter,snd_soc_meson_axg_sound_card,snd_soc_hdmi_codec,snd_soc_meson_g12a_tohdmitx,snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_fifo,snd_soc_meson_axg_tdmout,snd_soc_meson_axg_frddr,snd_soc_meson_card_utils,snd_soc_meson_codec_glue snd_compress 24576 1 snd_soc_core ac97_bus 16384 1 snd_soc_core snd_pcm_dmaengine 20480 1 snd_soc_core snd_pcm 131072 7 snd_soc_hdmi_codec,snd_compress,snd_soc_meson_axg_tdm_interface,snd_soc_core,snd_soc_meson_axg_fifo,snd_soc_meson_codec_glue,snd_pcm_dmaengine snd_timer 40960 1 snd_pcm snd 90112 5 snd_soc_hdmi_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm soundcore 16384 1 snd I tried digging in dmesg and the only related issue that came out is:p panfrost ffe40000.gpu: error -ENODEV: dev_pm_opp_set_regulators: no regulator (mali) found but I wouldn't say that to be the source of the sound problem. There are errors but I don't feel the solution behind any of them. Do you? Kernel, modules, drive, dtb... where else could the lack of sound come from? Any suggestion?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines