Jump to content

Search the Community

Showing results for tags 'odroidc4'.

  • 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)
    • News
    • Odroid M1
    • ROCK Pi 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

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


Discord


Location


Interests

Found 17 results

  1. Igor

    Odroid C4

    https://wiki.odroid.com/odroid-c4/hardware/hardware
  2. So far I can only get the C4 to boot from a EMMC card, not a SDHC card, is that true or an I doing something wrong? I install the image with "dd if=./armbian...img bs=8M of=/dev/sde; sync; sync". That makes a bootable EMMC card, but all attempts with the SDHC card it just seems to sit there.
  3. After the last "sudo apt upgrade" my odroid C4 (meson) doesn't reboot properly anymore. In the system out there are many lines like: "Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically done." and one : "mdadm: error opening /dev/md?*: No such file or directory mdadm: No arrays found in config file or automatically /scripts/local-block/mdadm: 58: /scripts/local-block/mdadm: rm: not found" at the end: "Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev)" it's stuck in initramfs with "ALERT! UUID=<myUUID> does not exist. Dropping to a shell!" When I type "exit" the boot process starts and finishes successfully. screen.pdf
  4. Hi there! I just got my hands on a brand new Odroid C4. I flashed Armbian Bullseye (tried Buster too as Bullseye is marked unstable) onto an SD card. The Issue I'm now facing is, after any sort of kernel update the board will not properly soft reboot anymore. I can restart the freshly installed system (which I generated the ix link with) as many times as I want using /sbin/reboot, but one apt upgrade later the board hangs in limbo when I issue a soft reboot. I can see the system itself shutting down, the blue light stopping to heartbeat, and then nothing happens anymore, until I replug power, then the board boots up fine. I have tried to run nand-sata-install as described on the C4's board page (If you face issues with rebooting run this as root) but it does not help, and I'm not even sure whether it even flashes a new U-Boot at all. Obviously, I have trouble using the board as a server like this, as I'd have to come home and replug it if I ever need to reboot so hopefully this can get fixed Should anyone require further data, I can always provide that.
  5. Hello, we contact you with Odroid booting issues. I've confirmed that the problem occurs from the next boot when the board is powered off while the armbian logo is displayed. (It happens with a high probability.) When booting, the following log is displayed and it does not boot. Loading, please wait... starting version 237 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block … done done. Gave up waiting for root device. Common problems: -Boot args (cat /proc/cmdline) -Check rootdelay= (did the system wait long enough?) -Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk1p1 does not exits. Dropping to a shell! BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs)_ After that, if you try to reboot about 5-6 times, one boot is possible. (This phenomenon does not disappear and continues.) The sd card is not physically damaged. This is because cloning the OS will reboot normally. Another feature is that the Armbian logo does not appear normally after booting problems. When there were no problems booting, the Armbian logo was always displayed. It appears that some file related to booting are crashed on an abnormal shutdown. This is because we found a file that is believed to be the cause. After a few tries I successfully booted from the sd card with this boot problem and checked the /boot/armbianEnv.txt file. And found that the file contents are broken. (The contents are different from normal files.) I got the armbianEnv.txt file from a general sd card that did not have the problem raised in this article, overwritten it, and then booted it, and it was confirmed that it boots normally without any problem. I think this happens if the file writes don't complete properly while boot.cmd is running. Is my guess correct? I've heard that armbianEnv.txt is giving incorrect kernel parameters for the root filesystem root=/dev/mmcblk1p1 if it is corrupted. On the other hand, the kernel recognizes the SD card as /dev/mmcblk0p1, so there is a problem when booting. Has this phenomenon ever been reported? I would like to know the exact cause of this phenomenon and how to fix it or prevent this problem? We are looking for a way to recover if this happens during boot up. For example running script that pass hard coded boot parameter to kernel each boot... Because the product must be used in an environment where it is difficult to restrict users, unexpected power off (whether booting or not) may occur. (However, the system must be restored and operational.) We are considering mass production, so I think this is a very important issue. Thanks in advance for the reply. ------------------------------------------------- Environment of use - board : odroid c4 - power : DC 9V, 0.5A - os : ubuntu 18.04 - sdcard : SanDisk Ultra micro 32GB
  6. Hi! Odroid&ARM newbie here! Trying to boot Armbian on HC4, no picture coming up. I guess my problem is my old LCD display that im connecting with hdmi-vga connector. Display and connector are working, i tried with Odroid ubuntu SD-card, but when i ordered i didnt realize its Ubuntu-minimal. (My internet comes from mobile wifi hotspot, and i have no idea how to install GUI in there. Also Odroid wifi-bluetooth dongle is a pita) In Ubuntu, to get the monitor working i changed lines in boot.ini and conf.ini, no idea which of those files is the right one. My working lines in those Odroid Ubuntu 20.04 files are: setenv display_autodetect "false" setenv hdmimode "1280x1024p60hz" setenv voutmode "dvi" (Also the Odroid wifi dongle needs to be disconnected at boot, otherwise picture is scrambled) The question is: how to make such settings on Armbian SD-card. What files need to be changed with what text?
  7. I'm running Armbian from a emmc 16GB card. When I use the web browser the mouse constantly flickers, is there any way to get this to stop? Is there a graphics driver I should have enabled? When I select Additional Hardware Drivers none show up, so maybe there isnt a GPU accelerated driver available. Also switching between desktops feels sluggish. Maybe Im expecting too much performance from a $50 SBC. Thanks for your help & time in making this distribution. Im just looking to make the best user experience possible.
  8. The latest apt-get upgrade on my board running Focal updated all but two (described below) of the following packages: armbian-firmware armbian-focal-desktop-xfce armbian-zsh bluez bluez-obexd libbluetooth3 libnss-myhostname libpam-systemd libsecret-1-0 libsecret-common libsmbclient libsystemd0 libudev1 libwbclient0 linux-dtb-current-meson64 linux-image-current-meson64 linux-libc-dev linux-u-boot-odroidc4-current python3-samba samba samba-common samba-common-bin samba-libs smbclient systemdsystemd-sysv udev This generated a new initramfs and uboot updates so I rebooted afterwards to make sure everything was ok. Now, the Light Display Manager has a "failed to start" message and it prompts to see "systemctl status lightdm.service'. The output from that command is reproduced here: http://ix.io/3qc2 . (It tries to start the service five times and then gives up and gives the command-line login only). When I try to run $ sudo apt-get update again, the output now shows that : armbian-config and linux-focal-root-current-odroidc4 have been kept back. Any suggestions on how to get that glorious desktop happening again? I'm trying to get more experience with C, systems programming, drivers, scripting, (also interested in the Berkeley Software Distributions, have a working Linux From Scratch built [but haven't delved into https://www.linuxfromscratch.org/blfs/ much yet], have compiled a couple kernels with Gentoo, and have done some hobbyist work w/ assembly programming). In short, I like this project and want to contribute after improving my skillset more and (also getting more freetime) -- but my system stubbed its toe on this latest update. should I revert (somehow) to an earlier version of a package? (I'm not sure which one or ones from that list of updates goofed the lightdm service up.) Thanks in advance for any assistance.
  9. The screen will display for a minute or two before the display will stop and the screen is blank. After 4 minutes the display is back ON. Armbian_21.02.3_Odroidc4_focal_current_5.10.21_xfce_desktop Last errors reported; Mar 11 20:00:00 odroidc4 systemd-udevd[1507]: card1: Worker [1535] failed Mar 11 20:00:00 odroidc4 systemd-udevd[1507]: Worker [1535] terminated by signal 9 (KILL) Mar 11 20:00:00 odroidc4 systemd-udevd[1507]: card1: Worker [1535] processing SEQNUM=2984 killed Mar 11 20:00:00 odroidc4 systemd-udevd[1535]: card1: Spawned process '/usr/local/bin/hdmi-hotplug' [4565] timed out after 2min 59s, killing Mar 11 19:59:14 odroidc4 systemd[1]: armbian-disable-autologin.service: Succeeded. Mar 11 19:59:13 odroidc4 systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbu> Mar 11 19:59:13 odroidc4 systemd[1]: Reloading. Mar 11 19:59:13 odroidc4 systemctl[5584]: Removed /etc/systemd/system/timers.target.wants/armbian-disable-autologin.timer. Mar 11 19:59:13 odroidc4 systemd[1]: Started Disable automated desktop login. Mar 11 19:58:04 odroidc4 systemd[4695]: tracker-store.service: Succeeded. Mar 11 19:58:04 odroidc4 tracker-store[4871]: OK Mar 11 19:58:00 odroidc4 systemd-udevd[1507]: card1: Worker [1535] processing SEQNUM=2984 is taking a long time Mar 11 19:58:00 odroidc4 systemd-udevd[1535]: card1: Spawned process '/usr/local/bin/hdmi-hotplug' [4565] is taking longer than 59s to complete
  10. I am using two Odroid N2 and a new Odroid C4. The N2 installation with OMV5 is using Kernel 4.9.236 actually and the C4 is using the kernel 5.8 used in the latest download image for debian buster. When I try to install newer kernels after the following linux kernel packages the installation gets broken and the odroids are not booting anymore. There is also no output on hdmi to see what problem could be exist. On Odroid N2 I hear the USB drives starting, stopping, starting and then nothing happens. All other updates are installing without problems in rebooting. The N2 are using on my test N2 a micro sd card and on my prod n2 a emmc card. The C4 is also using a emmc card. Can someone help to fix this or are there other persons using these odroids with same problems? Here are the actually installed packages without problems: ii linux-dtb-legacy-meson64 20.08.6 arm64 Linux DTB, version 4.9.236-meson64 ii linux-image-legacy-meson64 20.08.6 arm64 Linux kernel, version 4.9.236-meson64 And here is the output from installing the newer kernel which is actually available Reading package lists... Building dependency tree... Reading state information... Suggested packages: linux-firmware-image-legacy-meson64 The following packages will be upgraded: linux-dtb-legacy-meson64 linux-image-legacy-meson64 apt-listchanges: Reading changelogs... 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/21.9 MB of archives. After this operation, 2632 kB of additional disk space will be used. (Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 62535 files and directories currently installed.) Preparing to unpack .../linux-dtb-legacy-meson64_20.08.13_arm64.deb ... Unpacking linux-dtb-legacy-meson64 (20.08.13) over (20.08.10) ... dpkg: warning: unable to delete old directory '/boot/dtb-4.9.236-meson64': Directory not empty Preparing to unpack .../linux-image-legacy-meson64_20.08.13_arm64.deb ... update-initramfs: Deleting /boot/initrd.img-4.9.236-meson64 Removing obsolete file uInitrd-4.9.236-meson64 Unpacking linux-image-legacy-meson64 (20.08.13) over (20.08.10) ... Setting up linux-dtb-legacy-meson64 (20.08.13) ... Setting up linux-image-legacy-meson64 (20.08.13) ... update-initramfs: Generating /boot/initrd.img-4.9.238-meson64 update-initramfs: Converting to u-boot format Fertig ...
  11. I recently uploaded Armbian_20.11_Odroidc4_focal_current 5.9.12_desktop.img.xz onto a new Odroid-C4. Booting up and getting started hasn't been a problem, but I've been interested in driving some brushless motors using a PWM control signal and started looking through the device tree. The C4 is supposed to have a total of 6 PWM outputs, spread over 3 pwmchip devices, which (I believe) should be named pwmchip0, pwmchip4, and pwmchip8. However, upon navigating to /sys/class/pwm, I'm only seeing pwmchip0. This seems a little odd, because if PWM was entirely disabled in the device tree, I wouldn't have expected that any of the chips would have appeared. Not sure if this is a board-level problem, or something I'm missing in the kernel image I downloaded. I'm planning on comparing the stock Odroid image, but the spare uSD card I ordered is taking longer to arrive than expected. I can update when it comes in, but wanted to check either way if this was expected behavior for the Armbian image and if so, there is a simple fix, since I'd prefer sticking with vanilla Armbian over whatever fork the manufacturer puts out is. Thanks for your time, and please let me know if there's any add'l information I can provide to make this easier!
  12. Hey, I am not able to compile a .ko kernel module : below the error. I think it's fair to say that it may happen on many boards. I guess you supposed that before I had to get the linux-headers on. which required to tune the build config and include the headers during the build for that specific meson64 release at least. Saying that after rebuilding all I am stuck again on the vdso as i can't build a .ko easily. I think many people but i let the team taken the decision may be stuck at one point on linux-headers or to compile a .ko module. I would recommend to have DEFAULT parameter YES for the linux-headers as well as all that would be required to compile some .ko module. I remember in the past get stucked on some other boards for similar reasons. Let us know the decision and how to solve that from a initial build . I also would like to mention that your build is kool. thanks for that. just a few steps to make other customers happy ------------- ERROR in making .KO ------------------------------------------ /src/linux-headers-5.9.16-meson64' scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order' Makefile:1400: warning: ignoring old recipe for target 'modules.order' make[2]: *** No rule to make target 'arch/arm64/kernel/vdso/vdso.lds', needed by 'arch/arm64/kernel/vdso/vdso.so.dbg'. Stop. make[1]: *** [arch/arm64/Makefile:193: vdso_prepare] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.9.16-meson64' make: *** [Makefile:6: all] Error 2
  13. So as we know, the Hardkernel kernel did support powering the device on and off via a GPIO pin. This does not seem to work on Armbian with the mainline kernel. What does work is powering the device on and off with the remote control. So I wonder, what has to be done to enable power on and off vie the GPIO? My approach till now makes it possible to shutdown the device via GPIO interrupt. But then it will not come up again except if I reconnect the power cord or use the remote. I use this user device three overlay btw: /dts-v1/; /plugin/; /{ fragment@0 { target = <&ao_pinctrl>; __overlay__ { power_btn_port:power_btn_port { mux { groups = "GPIOAO_10"; function = "gpio_periphs"; bias-pull-up; output-high; }; }; }; }; fragment@1 { target-path = "/"; __overlay__ { gpio_keys:gpio_keys { compatible = "gpio-keys"; power_btn:power_btn { label = "POWER BUTTON"; linux,code = <116>; gpios = <&gpio_ao 10 0>; //GPIOAO_10 interrupt-parent = <&gpio_intc>; interrupts = <10 3>; wakeup-source; }; }; }; }; }; I've tried with the default pin as well (GPIOX_4) but with the same result. The hope was that the AO domain would do some magic like with the remote but no dice. Also the 'wakeup-source' seems to be ignored by the system as 'cat /sys/kernel/irq/*/wakeup' prints 'disabled' for all IRQ's. So, any ideas besides dissembling the remote and some solider works from the power button on the chassis to the IR IC to make it part of the final device? This would be very Frankenstein'ish just have a power button.
  14. Image used Armbian_20.11.10_Odroidc4_focal_current_5.9.14_desktop.img It works with micro SD (eMMc not inserted) Not booting with eMMc (SD not inserted), With SD & eMMC, system boot from SD .. . I tried nand-sata-install -> "Update bootloader" script same problem. see the attached output error from my monitor
  15. Hi, for the Odrioid C4 eMMC v0.4 modules are available. like Can I use these v0.4 modules in my Odroid C2, too? I didn't find any information about the compatibility. Thanks in advance! Matt
  16. 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 ]---
  17. 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.
×
×
  • Create New...