Search the Community

Hi I installed Armbian_community_26.2.0-trunk.151_Odroidhc4_trixie_current_6.18.2_minimal.img Trying to build zfs-dkms I discovered that I was missing the linux-headers for this kernel version and there is no package containing it. At least apt-cache didn't find anything. Any idea where to find it? Thanks, Chris

Armbian recently merged and will be releasing (and backporting) a patched devicetree file for the Odroid C4 and HC4 that eliminates the second power-cycle "glitch" during boot. Hopefully this will fix at least one issue people have been reporting, where some HDDs (or other devices) do not react well to rapid power double-tap during boot. https://github.com/armbian/build/blob/main/patch/kernel/archive/meson64-6.19/board-odroid-sm1-regulators-boot-on.patch It will also be released (and likely backported) upstream in next Linux kernel release and/or fixes. Also, something else people have been reporting is the HC4 struggling to spin up two large HDDs at the same time. If you have an HDD with a "Power Up In Standby" (PUIS) setting, such as the Seagate IronWolf, then you can configure all non-system (non-boot) drives in this manner, and then mount and access them sequentially after the system has booted. Depending on how much power the HDDs use in regular operation, this might work to get both spun up and running. Theoretically, you could also access just one drive at a time and then place it back in standby before using the other drive. YMMV.

System Overview Hardware: ODROID HC4 OS: Armbian (current version) Kernel: 6.12.44-current-meson64 Use case: Production NAS with critical data Problem Description During apt upgrade, the following critical warnings appear: dpkg: warning: This system uses merged-usr-via-aliased-dirs, going behind dpkg's dpkg: warning: back, breaking its core assumptions. This can cause silent file dpkg: warning: overwrites and disappearances System state analysis reveals: /bin, /sbin, /lib are correct symlinks to /usr/* BUT: Files exist in duplicate (/bin/bash and /usr/bin/bash identical) DKMS cannot build kernel modules (missing headers) systemd cannot set journal flags (symlink to SD card) NAS Configuration (Critical Infrastructure) Storage Setup: RAID1 with mdadm (two HDDs) + LUKS encryption /var/log relocated to SD card Filesystem: /dev/mmcblk0p1: LABEL="armbi_root" TYPE="ext4" /dev/sda: TYPE="crypto_LUKS" /dev/sdb: TYPE="crypto_LUKS" /dev/mapper/sda_luks: TYPE="linux_raid_member" /dev/mapper/sdb_luks: TYPE="linux_raid_member" /dev/md0: TYPE="ext4" Reproduction $ ls -la /bin /sbin /lib lrwxrwxrwx 1 root root 7 Apr 22 2024 /bin -> usr/bin lrwxrwxrwx 1 root root 7 Apr 22 2024 /lib -> usr/lib lrwxrwxrwx 1 root root 8 Apr 22 2024 /sbin -> usr/sbin $ ls -la /usr/bin/bash /bin/bash -rwxr-xr-x 1 root root 1543048 Mar 31 2024 /bin/bash -rwxr-xr-x 1 root root 1543048 Mar 31 2024 /usr/bin/bash # DUPLICATE! Urgent Questions 1. Root Cause Analysis Has anyone experienced this specific issue with Armbian on ODROID HC4? Is this a known upgrade problem with a particular Armbian version? 2. Solution Paths Which approach do you recommend for a production NAS? A) System repair tool (is there an Armbian-specific one?) Manual cleanup - any experiences with this? C) Migration to new image - best method with LUKS+RAID? D) Install kernel headers first despite warnings? 3. Migration Strategy with LUKS How to safely migrate: LUKS configuration (keys, passphrases) mdadm RAID1 setup Samba/NFS shares and ACLs WireGuard configuration Risk Assessment Current risk: Silent data corruption possible Kernel updates may break filesystem modules System might not boot after next reboot Time pressure: NAS must remain available, but security is top priority. System Details # dpkg --version Debian 'dpkg' package management program version 1.22.6 (arm64). # uname -a Linux odroidhc4 6.12.44-current-meson64 #3 SMP PREEMPT Thu Aug 28 14:31:16 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux # cat /etc/armbian-image-release BOARD=odroidhc4 BOARD_NAME="Odroid HC4" VERSION=25.2.1 REVISION=25.2.1 IMAGE_UUID=54c1127b-9e70-4d3f-bedd-3faf1f5e58fa BUILD_REPOSITORY_COMMIT=1f6972065 Request for assistance with: Immediate actions to stabilize the system Proven migration method for Armbian+ODROID+LUKS Experiences with this specific bug

Hi, I currently have the issue of a non working usb port on my odroidhc4. dmesg output: [ 133.464610] usb usb1-port2: connect-debounce failed The port does not show up when lsusb is entered. uname -a: Linux odroidhc4 6.12.56-current-meson64 #1 SMP PREEMPT Wed Oct 29 13:09:02 UTC 2025 aarch64 GNU/Linux I solved this temporairly a while ago by booting an older kernel (linux-image-6.12.43+deb12-arm64) like mentioned here: Are there any progresses on how to fix this reliably? Because I think still running kernel 6.6.63 is not save. Thanks for your answer in advance, if you need more information I am happy to deliver.

Board: ODROID-HC4 Images tested: Armbian_25.5.1_Odroidhc4_bookworm_current_6.12.28_minimal.img Armbian_25.5.1_Odroidhc4_noble_current_6.12.28.img Kernel versions tested: multiple (6.6.x, 6.7.x, 6.12.x) through armbian-config Issues observed: 1. No USB keyboard at boot I have tested with three different USB keyboards (all working fine on Debian/Ubuntu official images). 2. SATA not initialized → NAS functionality is broken Always get: ata1: SATA max UDMA/133 ata1: SATA link down (SStatus 0 SControl 300) ata2: SATA max UDMA/133 ata2: SATA link down (SStatus 0 SControl 300) Disks are never detected. This makes Armbian unusable on HC4 as a NAS (which is the main purpose of the board). 3. Petitboot incompatibility and restore procedure Armbian does not boot correctly with Petitboot (the default bootloader shipped by Hardkernel). The Armbian documentation recommends removing Petitboot, which prevents using other distributions afterwards. The official Armbian forum threads redirect to Hardkernel forum. The tools to restore Petitboot are hosted on ppa.linuxfactory.or.kr, which has been offline for over a week !... This effectively leaves users stuck without a working bootloader or system. Expected behavior SATA disks should be detected and initialized (as with Hardkernel’s Debian/Ubuntu 5.15 LTS images). USB keyboards should work at boot. Armbian should either work with Petitboot, or provide a reliable documented way to restore it. At the moment, Armbian on ODROID-HC4 is unusable as a NAS due to SATA not working and Petitboot being broken. The only working setup is using Hardkernel’s old Debian/Ubuntu images with kernel 5.15. Could you please clarify: Is HC4 still officially supported by Armbian? Do you test your releases ? If yes, which kernel/branch should be used for stable SATA support?... Will there be fixes for USB keyboard and Petitboot compatibility? Thanks a lot !

I can not reiterate enough just how easy it is to "clone" your modified emmc, or microSD card OS, ... into an image file that you can easily restore with (balena)Ethcher afterwards, and all withiin Linux. 1:/ you'll need a USB-card-reader-adapter. 2:/ no matter how your USB-reader card reader sees your emmc, microSD card, ..., it'll most likely be mounted on a /dev/sda1 partition. 3:/ sudo dd bs=4M if=/dev/sda of=~/tmp/armbian_odroidc4_11_01_2025.img (you don't dd the partition, you dd the drive). 4:/ (optionally) sudo xz -v armbian_odroidc4_11_01_2025.img (this will take some time). ...and that's it, ... and you know the rest.

Everything works, but I don't know why (;-) I upgraded to a new kernel 6.12.34-current-meson64 and also to the current u-boot. If I take a look at a current armbian image, every image.. vmlinux.. etc. is available in the boot folder, but no uImage. In my boot folder, however, in addition to the these files in the current armbian image, in my boot folder is still is a uImage from 2022. uname -r -> 6.12.34-current-meson6 So the current kernel is loaded and everything works. But if I now delete the uImage from 2022, the computer no longer boots. How does a current armbian image manage to boot without uImage? Is a uImage created at the first start? Manually I have created a new uImage via mkimage -A arm -O linux -T kernel -C none -a 0x01080000 -e 0x01080000 -n "Linux" -d ./vmlinuz-* ./uImage and the computer boots again, without uImage and only with the vmlinuz files not. Long story - can I leave it like that, or is there a way to boot without uImage.

Hello I'm running debian bullseye on an Odroid C4 since quite some time now and decided it was a good time to upgrade to bookworm. When I first installed armbian on this board, I remember that I had to install the Odroid HC4 image. If I'm not mistaking, there were no C4 image at the time. After upgrading my current bullseye firmware with armbian-config ( and by passing the SSD issue described in this armbian forum post by hot plugging it ), I noticed that /boot/armbianEnv.txt had this line: fdtfile=amlogic/meson-sm1-odroid-hc4.dtb whereas the amlogic/meson-sm1-odroid-c4.dtb file exists in the /boot/dtb directory. Despite having read that HC4 and C4 were the same board with few differences, dtdiff shows a lot of settings differ between the dtb of the two boards. Similarly, I notice that a bunch of *odroidc4 packages are now present in the repository that I don't remember having seen when I first installed armbian. So before upgrading to bookworm, I was wondering if it would be a good or bad idea to modify the armbianEnv.txt in order to use the C4 dtb, and replace the *odroidhc4 packages by their *odroidc4 equivalents. Did someone already try these changes ? Does someone see any issue with applying this changes ? Will there be other changes to apply in order to fully migrate from the initial HC4 configuration to a possibly more appropriate C4 configuration ? Thanks for your time and answers.

(Sorry this tagged as C2 since C4 tag not available) - Not trying to ruffle any feathers mentioning dietpi. I have an Odroid C4 with petitboot on sd for booting os's. I have a couple usb3>sata cases with 120g ssd's installed. Blazing fast and about $25usd 🙂 I can then download images and write them to the drives. Dietpi 9.11 and using the netboot function builtin to petiboot a few different flavors of other os's including debian 12. I have Armbian on SD as well. My problem is that it is incredibly slow running from sd on my c4. It runs VERY WELL though and detects audio properly on my tv through hdmi (shows as unknown display). Where Debian 12 and Dietpi DONT. I get NO SOUND from them. I just shutdown, swap usb and each boots nicely from petitboot. Is there a way to make Armbian like dietpi where its disk format is recognized by petitiboot? Then you would no longer have to do any u-boot configuration. I searched the forums and saw a post about using armbian-config to install to usb and did that. But petitboot does not see the drive so will not boot from it. I booted from the armbian sd and it appears to be using the usb drive but upon upgrade (of 37 pkgs) from 12.9>12.10 It fails with many file size/hash sum mismatch. It mentions mirror-sync in progress so I will try again later. And now that I am using usb storage on Armbian there is NO SOUND. So it appears that my sound problem on the C4 is usb related. I unplugged the usb and thought it would launch Armbian from sd but apparently uboot was changed so that fails. I will start hunting for odroid usb/sata sound issues and see if i have any luck. Just wondered if you have any ideas on this? Thanks.

# uname -a Linux odroidc4 6.6.63-current-meson64 #1 SMP PREEMPT Fri Nov 22 14:38:37 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux Installed latest "Armbian_24.11.1_Odroidc4_noble_current_6.6.60-kisak.img" ...with latest sudo apt update; sudo apt upgrade, rebooted... Hardware: - Odroid-C4 - Sabrent USB 3.0 to 2.5-Inch SATA Adapter; Model: EC-SSHD with latest firmware patch, connected to a Kingston SSD: SA400S37480G # dmesg -l emerg,alert,crit,err [ 0.879290] meson-drm ff900000.vpu: DSI transceiver device is disabled [ 3.402246] systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables. [ 4.327154] panfrost ffe40000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found [ 4.871183] systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables. [ 5.093021] I/O error, dev sda, sector 2064 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [ 5.098203] I/O error, dev sda, sector 2088 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 [ 5.098226] I/O error, dev sda, sector 2120 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 2 [ 5.102570] Buffer I/O error on dev sda1, logical block 2, async page read [ 5.111428] Buffer I/O error on dev sda1, logical block 2, async page read I'm not worried about vpu, or panfrost errors, ..., since I don't care about gpu on this headless (non-desktop) cli mini-server. # dmesg | grep -i systemd-sysctl [ 3.331877] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables... [ 3.399999] systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE [ 3.400501] systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'. [ 3.402246] systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables. [ 4.822476] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables... [ 4.870046] systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE [ 4.870601] systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'. [ 4.871183] systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables. I checked /etc/sysctl.conf, and everything looks ok, afaik.? # cat /etc/sysctl.conf # # /etc/sysctl.conf - Configuration file for setting system variables # See /etc/sysctl.d/ for additional system variables. # See sysctl.conf (5) for information. # #kernel.domainname = example.com # Uncomment the following to stop low-level messages on console #kernel.printk = 3 4 1 3 ################################################################### # Functions previously found in netbase # # Uncomment the next two lines to enable Spoof protection (reverse-path filter) # Turn on Source Address Verification in all interfaces to # prevent some spoofing attacks #net.ipv4.conf.default.rp_filter=1 #net.ipv4.conf.all.rp_filter=1 # Uncomment the next line to enable TCP/IP SYN cookies # See http://lwn.net/Articles/277146/ # Note: This may impact IPv6 TCP sessions too #net.ipv4.tcp_syncookies=1 # Uncomment the next line to enable packet forwarding for IPv4 #net.ipv4.ip_forward=1 # Uncomment the next line to enable packet forwarding for IPv6 # Enabling this option disables Stateless Address Autoconfiguration # based on Router Advertisements for this host #net.ipv6.conf.all.forwarding=1 ################################################################### # Additional settings - these settings can improve the network # security of the host and prevent against some network attacks # including spoofing attacks and man in the middle attacks through # redirection. Some network environments, however, require that these # settings are disabled so review and enable them as needed. # # Do not accept ICMP redirects (prevent MITM attacks) #net.ipv4.conf.all.accept_redirects = 0 #net.ipv4.conf.default.accept_redirects = 0 # _or_ # Accept ICMP redirects only for gateways listed in our default # gateway list (enabled by default) # net.ipv4.conf.all.secure_redirects = 1 # # Do not send ICMP redirects (we are not a router) #net.ipv4.conf.all.send_redirects = 0 # # Log Martian Packets #net.ipv4.conf.all.log_martians = 1 # ################################################################### # Magic system request Key # 0=disable, 1=enable all, >1 bitmask of sysrq functions # See https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html # for what other values do #kernel.sysrq=438 Swappiness for zram, see swapon vm.swappiness=100 # Decrease swap usage to a more reasonable level #vm.swappiness=30 # # Improve cache management #vm.vfs_cache_pressure=50 # # Improve writing to external media like USB memory sticks #vm.dirty_bytes=335544320 #vm.dirty_background_bytes=167772160 # ------------------------------- For the sake of brevity, I'm only running "transmission-daemon" on this successfully -sort of, with everything else being the default Armbian server settings, ... see: with: # cat /etc/udev/rules.d/99-usb-drive.rules ENV{ID_FS_UUID}=="501ce172-bc60-40db-90b6-9e025d2748bb", ACTION=="add", RUN{program}+="/usr/bin/systemd-mount --type=ext4 --no-block --collect $devnode /media/USB01/" ...so as to mount my USB-SSD-drive upon boot. But that's for another topic, since the "Failed to start systemd-sysctl.service - Apply Kernel Variables." were there before, and nothing else was changed. Basically, are the errors in my "dmesg" output above anything to really worry about.?

I successfully flashed the "Armbian_24.11.1_Odroidc4_noble_current_6.6.60-kisak.img" on my emmc, and everything boots, runs, and updates fine... My 2TB USB3.0 seagate HD, /dev/sda, is seen fine in "dmesg", as well as "lsblk" and "blkid", but when I add my UUID, ..., in /etc/fstab it fails to mount at boot. see below line in /etc/fstab for above /dev/sda1 : UUID=<output-of-bklid-for-sda1> /media/USB01 ext4 defaults 0 1 To test the above /etc/fstab mount I ran: sudo findmnt --verify (which completes successfully) Also, if I run: sudo mount -a (it manually automounts /dev/sda1 -> /media/USB01 successfully). But, whenever i reboot, it does not come up mounted.? -this is driving me crazy. Do I also need udisks2 ?, or autofs>, and/or, manually edit udev*?, and/or "systemd-mount" to get this thing to mount on every boot. ?

Hi there, I have an overlay available for Odroid C4 (Kernel 6.6.51), which needs some testing in the field. It supports 12MHz operation max on the pins 19, 21, 23 and 24 on the GPIO header. In case you have a test case for that, let me know, and I can provide things to you. Michael

Hi, after a long time I started up my C4 and tried both the standard download kernel as well as a home compiled one. I need SPI on the C4, so I changed the device tree to meson-sm1-odroid-c4-spidev.dtb, and see spidev kernel modul loaded, but no driver, and I don't get any signals on the corresponding pins. Any help is appreciated - would be great to have SPI working again... See you, Michael

Is there some instructions on how to get opencl with gpu working on the C4 with armbian ? I found https://wiki.odroid.com/odroid-c4/os_images/ubuntu/minimal/20200526#opencl_configuration but the package mali-fbdev isn't available on armbian. Closest I've got is : $ curl -L http://deb.odroid.in/c4/pool/main/m/mali-midgard-driver/mali-fbdev_0.1-2ubuntu4_arm64.deb -o mali-fbdev_0.1-2ubuntu4_arm64.deb $ ar -xv mali-fbdev_* $ tar --use-compress-program=unzstd -xvf data.tar.zst $ sudo cp -r usr/* /usr/ $ mkdir -p /etc/OpenCL/vendors/ $ echo /usr/share/mali-odroid-c4/libmali.so | sudo tee /etc/OpenCL/vendors/mali.icd But then clinfo fails with : $ clinfo Number of platforms 1 Platform Name ARM Platform Platform Vendor ARM Platform Version OpenCL 2.0 git.c8adbf9.ad00b04c1b60847de257177231dc1a53 Platform Profile FULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_3d_image_writes cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp16 cl_khr_icd cl_khr_egl_image cl_khr_image2d_from_buffer cl_khr_depth_images cl_khr_create_command_queue cl_arm_core_id cl_arm_printf cl_arm_thread_limit_hint cl_arm_non_uniform_work_group_size cl_arm_import_memory cl_arm_shared_virtual_memory Platform Extensions function suffix ARM Platform Name ARM Platform Number of devices 1 Failed creating base context during opening of kernel driver. So, presumably, there is a kernel module to be installed as well. I also found https://developer.arm.com/downloads/-/mali-drivers/user-space ... but doesn't indicate support for the C4. Any hints to get further ? Thanks.

Please move this message to correct folder, if I used the wrong one. There is a grave bug in the ext4 FS, which was introduced in kernel around 6.1.55 and is fixed in kernel 6.1.66. The bug is causing data coruption and data loss, like new packages aren't installed properly. A fix was introduced today into kernel, in version 6.1.66 Armbian Bookworm 23.11.1 (Debian) comes with 6.1.63 and, according to my knowledge, is affected. When will new kernel packages from armbian be available? References: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 https://fulda.social/@Ganneff/111551628003050712

I try to profiler the system, but could not find vmlinux binary and kernel debug symbol. The board is Odroid C4, SD card Image is download from armbian website Ubuntu 22.04.3 kernel 6.1.50-current-meson64 Thank you for help

Hello. I am wondering if anyone here has Xenomai working for Amlogic platforms? I'm particularly interested in applying Xenomai to Le Potato/Sweat Potato. According to them, Xenomai is current and working for the Amlogic S905X3 (Odroid C4), though I have failed to find any source, patches, or images for that board. As far as I can tell, aside from some minor performance improvements here and there, the Odroid C4's SoC layout is very comparable to what the Potato boards have. So I only expect minor changes, if anything, to go from that SoC to the Potato's SoC. Xenomai's own guide to porting the dovetail interface is pretty good; I'll do that if I have too. I'm just not trying to reinvent 80% of the wheel if I don't have to either. Not trying to get out of doing work, just doing it twice would be silly. Constructive comments most appreciated! 😄 (FYI, I'm not new to GNU/Linux, the cli, gcc, make, compiling in general, etc. etc. In fact, I have had a build system for Armbian up and running for months now, and can build functional images with it. I've even marginally contributed to Armbian. TL;DR: I won't need much hand holding, just help over one or two obstacles.)

Hi, I have a broken Odroid C2 from a customer. I've never used Odroid so I was wondering if I bought a Odroid C4 and insert the card will it run ok ? Don't know any info about what's in the sd card. The customer bought from a supplier he no long intends to work with ever again. Can anyone help me in any way ?

Hi, I would like to run a 32 bits (armhf) Debian or Ubuntu image on an Odroid C4. Do you know if this is possible, and if it is, can you point me to the right image ? Cheers, jf

Hello, I have trouble activating i2c on odroid c4. There's a pcf8563 module connected to the board. Also, /dev/i2c-0 /dev/i2c-1 exist. But pcf8563 does not show up when I run i2cdetect. I can rule out hardware issue because both i2c and pcf8563 work well with Hardkernel's Ubuntu image. So far, I've tried the followings but they don't work: Adding overlay="i2cA i2cB" to /boot/armbianEnv.txt and reboot. Manually editing device tree by changing status under "i2c@1d000" to "okay" and reboot. Also, I remember that i2c used to work on older versions of Armbian, which come with older version of kernels. But since linux 5.19, i2c no longer works. So I suspect that some changes in kernel may break the i2c functionality. I've uploaded diagnose info to https://paste.armbian.com/pevijojiwa Please advise. Thank you.

As it just happened, na OK, a few hours earlier, rhe name of an networkcard was changed. Why? How? By doing nothing special a real time consumpting work i had to get out what to change now, changing all the scripts and hoping nothing ist lost. what did build all the link local addresses?

I'm running Armbian Cli 23.02.2 Jammy with Linux 6.1.11-meson64 on my OdroidC4, I'd like to be able to boot from a USB3.0 SSD, (I'm aware that this board doesn't have SPI flash memory, so you should sacrifice a micro SD to host the system boot) When I run armbian-config and go to the option to "boot from SD - systemd on SATA, USB or NVMe" the process seems to complete all the steps without difficulty, at the end the process asks to reboot, the problem starts here, at perform the reboot the system never boots, it stays in a loop, the SSD flashes led light as if it had activity, the same my odroid c4 flashes blue led light in a loop, but the system never appears by ssh. I hope someone can help me. Excuse my English, I'm using a translator.

Armbian Armbian 22.11.4 Jammy on Odroid C4 boot from SD card system on an ext4 SSD. First of all - everything I need works correctly... However, I have a question about the SD card. During the first installation on the SSD disk, the system hung on the first reboot and you could see from the console that the SD card with UUID=61748c7e-b234-40e8-b6b6-592f845c3699 was being waited for. After the timeout, the only way to fix the "error" was to log into the system via terminal. Long story - only after commenting out the SD card in the fstab on the SSD: UUID=61748c7e-b234-40e8-b6b6-592f845c3699 /media/mmcboot ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 0 /media/mmcboot/boot /boot none bind 0 0 the system booted from the SSD as requested. Since then, the SD card is not mounted and just shows up as: Disk /dev/mmcblk0: 30.61 MiB, 32096256 bytes, 62688 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes at fdisk -l. No UUID etc nothing... The SD-Card is 32G and is readable on other systems... Question now - is this normal? Can I live with that? Can it be fixed? A "curiosity" - after booting from the SSD and updating the kernel to 6.0.13, the update ended up on both the SSD and the unmounted SD card. How - is a mystery to me (;-)

I've installed Armbian on a Odroid C4 board (running with emmc storage & connected to the orginal power supply). After a few hours or days, the board crashes & throws an error unable to handle kernel paging request at virtual address 000000000002e82e2... See https://pasteboard.co/NjIo5L6UR0Px.jpg for the complete error message System diagnosis information is uploaded to https://paste.armbian.com/aqahepelav

Hi everyone! I've just got a new odroid c4 and am trying to hook it up to a small i2c oled display. I've wired it up to the I2C A SCA and SCL pins with 3.3V and GND as needed, and enabled both I2C A and B in armbian-config. However, when I run i2cdetect -y 0 I get the device grid with a 30 in position 30 and nothing else, both with the display hooked up or not, nothing changes. Is there anything obvious I might have missed to get I2C running? Thanks in advance for your help!