Search the Community

Showing results for tags 'odroidhc4'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • Tech News
    • Khadas VIM4
    • Radxa Zero 2
    • Odroid M1
  • Supported boards
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unsupported (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Old bug tracker - read only
    • Old bug tracker - read only
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues

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


Skype


Github


Location


Interests

Found 12 results

  1. 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?
  2. First off, could someone please help. I did not seem to be able to create this topic without a tag and the only tag it would accept was "solved". Wondering if somebody could remove the "solved" tag and add in "odroidhc4"? I purchased a brand new odroid hc4 board with the intention of installing armbian and then subsequently OMV. My intention was/is to install Armbian on a MicroSD card. On the downloader page I read that in order to clean boot Armbian the incompatible Petit bootloader needs to be removed. I tried the bootloader bypass (preferred) method and that didn't seem to work for me. The board still seemed to go to the petitboot UI. I then tried the Petitboot Console method and ran the following commands as detailed on the download page: # flash_eraseall /dev/mtd0 # flash_eraseall /dev/mtd1 # flash_eraseall /dev/mtd2 # flash_eraseall /dev/mtd3 These all seemed to run/complete without issue. I then rebooted the board and now absolutely nothing happens. It doesn't boot to the Petitboot UI/Console and it doesn't boot to Armbian either.... Does anybody have any suggestions or wisdom that can help resolve this? Thanks 🙂
  3. From time to time, I notice that the HC4 looses its IP address. journalctl then tells me: dhcp4 (eth0): selecting lease failed: -131 But I don't know the reason for it. Sometimes it happens after a reboot. Pulling the ethernet cable off and plugging it in again seems to help and after a few tries, the HC4 is reachable again. I'd be happy to give more information, but I don't know yet how to debug it. I noticed that /var/log (zram) sometimes gets full but I don't know if this is related…
  4. My current HC4-setup consists of 1 SSD and 1 HDD. The SSD contains the most recent Armbian-image (Buster-based) (https://redirect.armbian.com/odroidhc4/Buster_current). Long story short: it won't boot from SSD, and Google tells me it is because Armbian is not compatible with Petiboot. Armbian suggests the following solution: "Important: To be able to boot clean Armbian mainline based u-boot / kernel experiences, you need to remove incompatible Petitboot loader that is shipped with the board. From the Petitboot, go for “Exit to shell” and these commands to remove the Petitboot:" # flash_eraseall /dev/mtd0 # flash_eraseall /dev/mtd1 # flash_eraseall /dev/mtd2 # flash_eraseall /dev/mtd3 "This will make your SPI flash memory empty and would start from SD on next boot." However, it doesn't mention whether this works for booting from an SSD. Does it? And if not, is there a possibility of booting Armbian from an SSD without using an SD-card? Thanks in advance! P.S. I found the following (unresolved) related question: https://www.reddit.com/r/ODroid/comments/moxxhl/uboot_from_sata_on_hc4/
  5. After upgrading to Focal on hc1 I countinously receive cron mails with the following content: /usr/lib/armbian/armbian-truncate-logs: 19: /etc/default/armbian-ramlog: Syntax error: "(" unexpected Similar problem is reported here: https://forum.yunohost.org/t/continuously-receiving-email-about-armbian-log/16549 After checking the code, the problem seams to be, that nowerdays /etc/default/armbian-ramlog contains something like # If USE_RSYNC is true, additional options may be specified for the rsync # commands used to synchronize logs to disk from RAM (XTRA_RSYNC_TO) or from # disk to RAM (XTRA_RSYNC_FROM). These are bash arrays to make specifying # multiple arguments easy even in the presence of whitespace. XTRA_RSYNC_TO=( ## If you use log rotation programs that datestamp their logs (e.g., runit's ## svlogd or daemontools' multilog), deleting log files while synchronizing is ## likely a good idea. # --delete ) When now /usr/lib/armbian/armbian-truncate-logs sources this file, this will always fail because the script is using `#!/bin/sh` which is actually (at least on my system) a link to dash. To fix the problem, in armbian-truncate-logs the first line should be replaced with `#!/bin/bash` and the error disappears. Would be great if this could be fixed. Cheers
  6. Hello, I'm facing a weird issue where a network connection doesn't work after my HC4 is started (after a power off), but then after calling a `reboot` network starts to work. I'm running a fresh install of the latest "Armbian Buster mainline kernel 5.10.y". More details in armbianmonitor's output: http://ix.io/2Rh8 http://ix.io/2Req I've tried playing with /etc/network/interfaces by putting stuff like the following there: allow-hotplug eth0 no-auto-down eth0 auto eth0 iface eth0 inet dhcp also tried static ip but nothing works. What exactly is happening? 1. When I power on my HC4 it awaits for network for a longer while (A start job is running for Raise network interfaces) and then finally boots with no network working. 2. ifconfig shows eth0 and lo interfaces. eth0 has no IP set. I cannot connect to the device from outside not reach network from it. 3. then I run `reboot` (need to connect a screen and a keyboard to the device :/) and the device boots quickly with network up and working Any ideas how to resolve that?
  7. Hi all How can I enable the rtc clock in the Odroid HC4? I know nothing about device tree and overlays, but the Hardkernel Ubuntu image has an overlay to enable: wiki. I didn't find anything similar in the armbian image. Could be related to this this PR for the N2 model? Thanks
  8. I recently upgraded from an Odroid HC2 to and Odroid HC4. I reinstalled the OS following the instructions on armbian.com, flashing onto a MicroSD. After migrating the apps (mostly dockers), I found that restic (backup tool) was generating out of memory errors and bringing the system to a halt in a way the HC2 didn't. This surprised me as it's overall higher specced, and the configuration was otherwise identical. After some troubleshooting, I realised there was no swap drive specified, and that creating a swap eliminated my out of memory errors. I'm not sure if the source of the "problem" is the swapfile here, but it at least stopped the problem occurring.
  9. Hi, is there a way, how to check that image in download section is ok? I have Odroid HC4 with good PSU, both old and new card, flashed by Etcher and Rufus, keyboard plugged in USB, no SATA disks at the moment. I'm able to boot Focal 4.9 kernel (however with some errors after the boot). I've removed Petitboot with flasherase first, I've checked SHA checksum. Edit: File I've downloaded is: Armbian_20.11.6_Odroidhc4_focal_current_5.9.14.img.xz SHA: 9930f984eca2a72b3c22953ee6381c95da528b2a355dd9f429da38d1409f7b1f *Armbian_2 Any ideas what is wrong? Thank you.
  10. Hi guys, I installed the latest Armbian (Buster) release for my Odroid HC4 and - after getting rid of Petitboot as that just wouldn't let me boot the image - it's working great so far. Only big problem I have is that it does not recognize any SATA devices, in neither of the two slots. I tried different HDDs / SSDs that I verified are recognized on a Windows PC and another Ubuntu PC. Did anyone get that working already? I assume the required Kernel drivers for the PCIe-Sata-chip are probably still missing. Many thanks and best regards Daniel
  11. I have a second usb network card (chip ax88179) conected to my C4. It randomly crashes and I have to rmmod/modprobe to make it work again : can't be done remotely without network... Looks like this kind of problem is kernel related : any idea ? uname -a Linux gwm 5.8.16-meson64 #20.08.14 SMP PREEMPT Tue Oct 20 22:50:41 CEST 2020 aarch64 GNU/Linux [34120.524606] ------------[ cut here ]------------ [34120.524659] NETDEV WATCHDOG: enx002427fe2bf8 (ax88179_178a): transmit queue 0 timed out [34120.525139] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:442 dev_watchdog+0x300/0x308 [34120.525160] Modules linked in: cpufreq_conservative cpufreq_powersave zstd bridge snd_soc_hdmi_codec dw_hdmi_i2s_audio ftdi_sio ax88179_178a usbnet meson_rng ir_nec_decoder meson_dw_hdmi dw_hdmi snd_soc_meson_g12a_tohdmitx reset_meson_audio_arb snd_soc_meson_codec_glue rc_odroid snd_soc_meson_axg_sound_card meson_saradc snd_soc_meson_card_utils meson_ir rc_core snd_soc_meson_axg_frddr snd_soc_meson_axg_fifo snd_soc_meson_axg_tdmout xt_TCPMSS xt_tcpudp meson_vdec(C) meson_drm v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 drm_kms_helper videobuf2_common cec videodev mc meson_canvas nft_counter snd_soc_meson_axg_tdm_interface snd_soc_meson_axg_tdm_formatter snd_soc_core ac97_bus display_connector snd_pcm_dmaengine snd_pcm drm snd_timer snd drm_panel_orientation_quirks soundcore ch341 usbserial nft_chain_nat zram xt_mark xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink ip_tables x_tables autofs4 spidev rtc_meson_vrtc meson_gxl [34120.525999] realtek dwmac_generic dwmac_meson8b [34120.526096] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 5.8.16-meson64 #20.08.14 [34120.526119] Hardware name: Hardkernel ODROID-C4 (DT) [34120.526165] pstate: 20400009 (nzCv daif +PAN -UAO BTYPE=--) [34120.526212] pc : dev_watchdog+0x300/0x308 [34120.526255] lr : dev_watchdog+0x300/0x308 [34120.526278] sp : ffff800010003d90 [34120.526304] x29: ffff800010003d90 x28: ffff0000f20b8680 [34120.526356] x27: 0000000000000004 x26: 0000000000000140 [34120.526406] x25: 00000000ffffffff x24: 0000000000000000 [34120.526455] x23: ffff0000f22883dc x22: ffff0000f2288000 [34120.526504] x21: ffff0000f2288480 x20: ffff8000126b7000 [34120.526551] x19: 0000000000000000 x18: 0000000000000000 [34120.526598] x17: 0000000000000000 x16: 0000000000000000 [34120.526646] x15: ffff8000126d5000 x14: 656d697420302065 [34120.526695] x13: 756575712074696d x12: 736e617274203a29 [34120.526743] x11: 613837315f393731 x10: 3838786128203866 [34120.526791] x9 : 6232656637323432 x8 : 0000000000000000 [34120.526836] x7 : 0000000000000003 x6 : 00000000000001cd [34120.526881] x5 : 0000000000000001 x4 : 0000000000000000 [34120.526925] x3 : 0000000000000001 x2 : ffff0000f479a1e8 [34120.526972] x1 : 64ee6f6fb4eeb400 x0 : 0000000000000000 [34120.527017] Call trace: [34120.527075] dev_watchdog+0x300/0x308 [34120.527134] call_timer_fn.isra.0+0x24/0x80 [34120.527186] run_timer_softirq+0x1a0/0x410 [34120.527229] efi_header_end+0x120/0x25c [34120.527273] irq_exit+0xc0/0xe0 [34120.527316] __handle_domain_irq+0x68/0xc0 [34120.527362] gic_handle_irq+0x54/0xa8 [34120.527401] el1_irq+0xb8/0x180 [34120.527446] arch_cpu_idle+0x14/0x20 [34120.527487] do_idle+0x210/0x288 [34120.527527] cpu_startup_entry+0x28/0x70 [34120.527570] rest_init+0xd8/0xe8 [34120.527619] arch_call_rest_init+0x10/0x1c [34120.527664] start_kernel+0x4f0/0x528 [34120.527692] ---[ end trace 1ba072349341d5ea ]---
  12. I flashed the image Armbian_20.08.1_Odroidc4_buster_current_5.8.5.img on my new odroid c4 without installing the latest updates (see my other post with no boot anymore after kernel update). After this I started via softy installation of omv5. During installation I wondered why my ssh connection was gone without any output. During installation there is a reboot of the os and the networking is not coming up anymore. I tried to find out and found: - armbian uses network manager for networking and the default config file is for dhcp - after omv5 installation network manager seems to be deinstalled and also there is a new empty config file under /etc/networking (which is not used from network manager) - so I have to repair this manually via direct access to the shell and after reboot network is ok I didn't see this behavior on my odroids n2 which I installed some month before. Should I also post this on openmediavault forum because this shouldn't happen. Seems that there is a mismatch in the salt config when using this armbian version and using installation skript via softy.