All Activity

I wonder if it'd be worth having a look instead at the Odroid stock kernel image and the vanilla kernel of the base same version; see what quirks are needed. I will have a look and see if that diff is less overwhelming than the massive gap you're seeing.

Hi pcduino2user, glad you are finding it useful. Maybe CMA Buffer size needs to be lowered during the kernel, which actually appears to get ignore anyway once the board has fully booted and replaced with 96mb based on the reserve memory node within the A10 DTSI. This is definitely needed if trying to run a desktop although I wouldn't recommend running a desktop on the Pcduino2. There are still some minor issues that I would like to address in future but I don't have as much time as I used to. For example the pcduino2 is actually booting from the Pcduino1 DTS although this problem is more cosmetic than functional. Both the Pcduino1 and Pcduino2 share the same uboot defconfig file but the Pcduino2 has a USB2 VBUS pin defined within its DTS and physically connected on the PCB. This is normally pulled high by a resistor so does not cause any problems with USB power being enabled. The build framework allows us to configure the kernel but there must be a way to customize uboot more dynamically as well? Now certain Armbian board configuration files appear to contain configuration data for adjusting the dram speed as can be found in the cubieboard.csc so I wonder if a similar setup in the pcduino2 configuration file to override the default device tree property to use sun4i-a10-pcduino2.dts instead of sun4i-pcduino.dts. Given the closeness of hardware it does not seem worth creating a separate defconfig file. Ryzer

Hi @Nick A, the armbian in afiftyp board just see 2GB to, at least it was this way in 2024 when he sent me his boot log. My board is very similar to afiftyp board, except of a number near the QC sticker, that looks like a version number. afiftyp number is 2336 and the mine is 2333. The amout of memory chips is identical to (8 chips), but tha labels is a litle different, but I cant found the label meaning. I use your image since very old one, so I don't think it is about u-boot update, but I could try an older one. About Secure Boot, A patch that you give me solved it and it isn't a problem any more (thanks again for it). @afiftyp, if I'm wrong and you already solve your rom amount in armbian, please let us know and if you could, explain us what you did to solve it, thanks.

Hi Ryzer, hi Igor, I was out of town for a while, but recently I could try out the new Armbian release v25.8.1, which incorporates the changes made by Ryzer. I chose kernel version 6.15 and did get an HDMI output on a Dell 21,5" monitor. So I managed to configure the pcduino2 for its purpose and I am using it again after many years. Excellent! Thank you so much for all your efforts! Great to be back as an Armbian user. Just as a side note: I was first trying with my Dell UltraSharp 34" monitor and there the HDMI output still does not work. I does work with the old Armbian 5.38 version for pcduino2 from the archives and also with Raspberry Pi 3 using a recent version of Raspberry Pi OS. Anyway, this is just for information. I do not think it is worth investigating this issue.

Something like git clone https://github.com/armbian/build.git -b main cd build git remote add -f imx8mp-build https://github.com/OLIMEX/imx8mp-build.git git remote update git fetch origin git fetch imx8mp-build git checkout main git rebase imx8mp-build/bookworm # fix conflict vi VERSION git add VERSION git rebase --continue # fix conflict vi .github/dependabot.yml git add .github/dependabot.yml git rebase --continue git log

They certainly did fork armbian, apparently at tag v24.11.1 AKA dd379da888f7d114f9f954d94a7ebcf261d179e5 $ git merge-base dd379da888f7d114f9f954d94a7ebcf261d179e5 main 017549347bb8c278a067d1be14c2f1b3538690c2 Add the Olimex repo as a remote and then rebase the latest armbian/build HEAD to their HEAD.

Following is the output of "mount|grep ro" root@rock-5-itx:~# mount|grep ro proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) /dev/sda2 on / type ext4 (ro,relatime) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=19056) ramfs on /run/credentials/systemd-resolved.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) ramfs on /run/credentials/systemd-networkd.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) ramfs on /run/credentials/systemd-journald.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) ramfs on /run/credentials/getty@tty1.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) ramfs on /run/credentials/serial-getty@ttyFIQ0.service type ramfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,mode=700) Following is the output of "lsblk" root@rock-5-itx:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 7.5G 0 disk ├─sda1 8:1 1 256M 0 part /boot/efi ├─sda2 8:2 1 7.2G 0 part / └─sda3 8:3 1 8M 0 part sdb 8:16 0 465.8G 0 disk ├─sdb1 8:17 0 1M 0 part ├─sdb2 8:18 0 512M 0 part ├─sdb3 8:19 0 16G 0 part └─sdb4 8:20 0 449.3G 0 part mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 29.1G 0 disk mmcblk0boot0 179:32 0 4M 1 disk mmcblk0boot1 179:64 0 4M 1 disk zram0 253:0 0 11.6G 0 disk [SWAP] zram1 253:1 0 50M 0 disk zram2 253:2 0 0B 0 disk nvme0n1 259:0 0 1.9T 0 disk ├─nvme0n1p1 259:1 0 1G 0 part └─nvme0n1p2 259:2 0 1.9T 0 part

I uploaded an updated version of the package bundle, with MPV and a few other updates that I found laying around: https://mega.nz/file/ZmwDBL6b#pGgXVRnoC0jU6dwFJebBcLDXyTNqdkmw3qvsOLz5qUI

@Dann https://dl.armbian.com/rock-5b-plus/Noble_vendor_gnome verifies fine for me. Try https://netcup-03.armbian.com/dl/rock-5b-plus/archive/Armbian_25.5.1_Rock-5b-plus_noble_vendor_6.1.115_gnome_desktop.img.xz and https://netcup-03.armbian.com/dl/rock-5b-plus/archive/Armbian_25.5.1_Rock-5b-plus_noble_vendor_6.1.115_gnome_desktop.img.xz.sha

An update. I suspect that the issue (or at least 1 issue) is a regression in the handling of MMC (SD card driver in the kernel). I suspect this is a regression as this issue did not hit me on earlier builds. I set up a netconsole, and received the following stack trace: [ 216.236507] I/O error, dev mmcblk0, sector 849688 op 0x0:(READ) flags 0x84700 phys_seg 1 prio class 2 [ 216.524566] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:353: I/O error 10 writing to inode 131108 starting block 323201) [ 216.534718] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:353: I/O error 10 writing to inode 131109 starting block 323202) [ 216.544920] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:353: I/O error 10 writing to inode 131110 starting block 323203) [ 216.560591] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:353: I/O error 10 writing to inode 131111 starting block 323204) [ 216.575914] EXT4-fs (mmcblk0p2): failed to convert unwritten extents to written extents -- potential data loss! (inode 131108, error -5) [ 216.587187] Buffer I/O error on device mmcblk0p2, logical block 270977 [ 216.601434] EXT4-fs (mmcblk0p2): failed to convert unwritten extents to written extents -- potential data loss! (inode 131109, error -5) [ 216.601564] ------------[ cut here ]------------ [ 216.608348] Buffer I/O error on device mmcblk0p2, logical block 270978 [ 216.608383] WARNING: CPU: 0 PID: 129 at drivers/mmc/host/meson-mx-sdio.c:446 meson_mx_mmc_irq_thread+0x168/0x174 [ 216.608467] EXT4-fs (mmcblk0p2): failed to convert unwritten extents to written extents -- potential data loss! (inode 131110, error -5) [ 216.608485] Buffer I/O error on device mmcblk0p2, logical block 270979 [ 216.612894] Modules linked in: rpcsec_gss_krb5 [ 216.619667] EXT4-fs (mmcblk0p2): failed to convert unwritten extents to written extents -- potential data loss! (inode 131111, error -5) [ 216.629626] auth_rpcgss [ 216.629674] Buffer I/O error on device mmcblk0p2, logical block 270980 [ 216.629700] zram [ 216.632164] Aborting journal on device mmcblk0p2-8. [ 216.641941] zsmalloc [ 216.642033] JBD2: I/O error when updating journal superblock for mmcblk0p2-8. [ 216.648457] binfmt_misc [ 216.676718] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1639: inode #598: comm dpkg-reconfigur: reading directory lblock 0 [ 216.680959] evdev [ 216.681075] EXT4-fs (mmcblk0p2): I/O error while writing superblock [ 216.683223] snd_soc_meson_aiu snd_soc_meson_gx_sound_card snd_soc_hdmi_codec snd_soc_meson_card_utils snd_soc_meson_codec_glue snd_soc_core snd_pcm meson_ir snd_timer rc_core [ 216.683268] EXT4-fs (mmcblk0p2): Remounting filesystem read-only [ 216.683278] thermal_generic_adc snd meson_saradc soundcore cfg80211 rfkill efi_pstore pstore netconsole [ 216.744185] CPU: 0 UID: 0 PID: 129 Comm: irq/35-c1108c20 Not tainted 6.12.47-current-meson #3 [ 216.744207] Hardware name: Amlogic Meson platform [ 216.744212] Call trace: [ 216.744225] unwind_backtrace from show_stack+0x10/0x14 [ 216.744259] show_stack from dump_stack_lvl+0x50/0x64 [ 216.744275] dump_stack_lvl from __warn+0x80/0x11c [ 216.744294] __warn from warn_slowpath_fmt+0x17c/0x188 [ 216.744311] warn_slowpath_fmt from meson_mx_mmc_irq_thread+0x168/0x174 [ 216.744337] meson_mx_mmc_irq_thread from irq_thread_fn+0x1c/0x7c [ 216.744364] irq_thread_fn from irq_thread+0x134/0x224 [ 216.744378] irq_thread from kthread+0xe0/0xfc [ 216.744396] kthread from ret_from_fork+0x14/0x28 [ 216.744411] Exception stack(0xf1075fb0 to 0xf1075ff8) [ 216.744420] 5fa0: 00000000 00000000 00000000 00000000 [ 216.744428] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 216.744435] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 216.744458] ---[ end trace 0000000000000000 ]--- [ 217.163204] mmc0: new high speed SDHC card at address 0002 [ 217.163907] mmcblk0: mmc0:0002 Which suggests the SD card was connected and disconnected. I have already ruled out faulty SD card (happens on any SD card I use, as well as a thorough stress test on the current card prior to use). Further research tells me "The Amlogic Meson8b (S805) SoC’s MMC controller has known quirks." I switched to USB rootfs (external HDD), and I still get the same failure, but as it is just the boot partition being unmounted and remounted the system remains up. Ideally I would propose a patch to fix this, but I am not a kernel developer, and the changes between 3.10 and 6.12 are huge (as to be expected) so identifying what is required and where is non-trivial for me. For now, I am sticking with rootfs on USB as my interim fix, but I am going to keep netconsole up and monitor over the next couple of weeks to see if we hit another issue (when I tested this in the past, I was also getting failures with rootfs on an external USB stick, so I am not convinced I am completely out of the woods yet).

show the output of "mount|grep ro"

AFBC support has been merged to PanVK and will be available in the Mesa 25.3 release! This new enablement reduces memory bandwidth and boosts performance. View the full article

Hi, I’m new to the forum and just wanted to take a moment to appreciate the incredible work Armbian has done for the community. I have been tinkering around with Radxa rock 5 ITX SBC and Armbian. I flashed UEFI EDK2 for Radxa rock 5 ITX  v1.1 from EDK2 porting to RK3588 initiative. While I can install ARM64 version of Ubuntu and Debian, none of them had support for H/W transcoding. So I decided to build an Armbian which used vendor kernel and had `uefi-edk2-3588` extension. Full build report is linked in this Armbian paste ./compile.sh \ BOARD=rock-5-itx \ RELEASE=trixie \ BRANCH=vendor \ BUILD_MINIMAL=yes \ BUILD_DESKTOP=no \ KERNEL_CONFIGURE=no \ NETWORKING_STACK=systemd-networkd \ EXPERT=yes \ CLEAN_LEVEL=extras \ ENABLE_EXTENSIONS=mesa-vpu,uefi-edk2-rk3588 \ KERNEL_BTF=yes \ SHARE_LOG=yes \ CONSOLE_AUTOLOGIN=no \ build I flashed the resulting image to a usb stick and booted system off it. This is when I had encountered problems. armbian-upgrade complained about a readonly system root@rock-5-itx:~# armbian-upgrade Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://security.debian.org trixie-security InRelease Hit:4 http://deb.debian.org/debian trixie-backports InRelease Hit:5 https://github.armbian.com/configng stable InRelease Ign:6 http://mirror.twds.com.tw/armbian-apt trixie InRelease Err:7 http://mirror.twds.com.tw/armbian-apt trixie Release Could not open file /var/lib/apt/lists/partial/apt.armbian.com_dists_trixie_Release - open (30: Read-only file system) [IP: 103.147.22.36 80] Warning: chown to _apt:root of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system) Warning: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system) Warning: chown to _apt:root of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system) Warning: chmod 0755 of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system) Warning: Not using locking for read only lock file /var/lib/apt/lists/lock Warning: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.foxhPQ - IsAccessibleBySandboxUser (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.ZQLLDs - IsAccessibleBySandboxUser (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.k64ifr - IsAccessibleBySandboxUser (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.kWgd4F - IsAccessibleBySandboxUser (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.pSkidL - IsAccessibleBySandboxUser (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/.apt-acquire-privs-test.PoF76X - IsAccessibleBySandboxUser (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_trixie_InRelease - PrepareFiles (30: Read-only file system) Warning: chown to _apt:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: chmod 0600 of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_trixie-updates_InRelease - PrepareFiles (30: Read-only file system) Warning: chown to root:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_InRelease failed - 201::URIDone (30: Read-only file system) Warning: chmod 0644 of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_InRelease failed - 201::URIDone (30: Read-only file system) Warning: chown to _apt:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: chmod 0600 of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/security.debian.org_dists_trixie-security_InRelease - PrepareFiles (30: Read-only file system) Warning: chown to root:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_InRelease failed - 201::URIDone (30: Read-only file system) Warning: chmod 0644 of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_InRelease failed - 201::URIDone (30: Read-only file system) Warning: chown to _apt:root of file /var/lib/apt/lists/security.debian.org_dists_trixie-security_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: chmod 0600 of file /var/lib/apt/lists/security.debian.org_dists_trixie-security_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: chown to root:root of file /var/lib/apt/lists/security.debian.org_dists_trixie-security_InRelease failed - 201::URIDone (30: Read-only file system) Warning: chmod 0644 of file /var/lib/apt/lists/security.debian.org_dists_trixie-security_InRelease failed - 201::URIDone (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_trixie-backports_InRelease - PrepareFiles (30: Read-only file system) Warning: chown to _apt:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-backports_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: chmod 0600 of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-backports_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/github.armbian.com_configng_dists_stable_InRelease - PrepareFiles (30: Read-only file system) Warning: chown to root:root of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-backports_InRelease failed - 201::URIDone (30: Read-only file system) Warning: chmod 0644 of file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-backports_InRelease failed - 201::URIDone (30: Read-only file system) Warning: chown to _apt:root of file /var/lib/apt/lists/github.armbian.com_configng_dists_stable_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: chmod 0600 of file /var/lib/apt/lists/github.armbian.com_configng_dists_stable_InRelease failed - Item::QueueURI (30: Read-only file system) Warning: chown to root:root of file /var/lib/apt/lists/github.armbian.com_configng_dists_stable_InRelease failed - 201::URIDone (30: Read-only file system) Warning: chmod 0644 of file /var/lib/apt/lists/github.armbian.com_configng_dists_stable_InRelease failed - 201::URIDone (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/apt.armbian.com_dists_trixie_InRelease - PrepareFiles (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/partial/apt.armbian.com_dists_trixie_Release - PrepareFiles (30: Read-only file system) Error: The repository 'http://apt.armbian.com trixie Release' no longer has a Release file. Notice: Updating from such a repository can't be done securely, and is therefore disabled by default. Notice: See apt-secure(8) manpage for repository creation and user configuration details. Warning: Problem unlinking the file /var/lib/apt/lists/github.armbian.com_configng_dists_stable_main_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_main_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_contrib_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_non-free_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie_non-free-firmware_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_contrib_binary-arm64_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_main_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_non-free-firmware_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_non-free_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_contrib_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_non-free_binary-arm64_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-updates_non-free-firmware_binary-arm64_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-backports_non-free_binary-arm64_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-backports_non-free-firmware_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-backports_non-free_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-backports_contrib_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/deb.debian.org_debian_dists_trixie-backports_main_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/security.debian.org_dists_trixie-security_non-free_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/security.debian.org_dists_trixie-security_main_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/security.debian.org_dists_trixie-security_non-free-firmware_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/security.debian.org_dists_trixie-security_contrib_binary-all_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/security.debian.org_dists_trixie-security_non-free-firmware_binary-arm64_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/security.debian.org_dists_trixie-security_non-free_binary-arm64_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Problem unlinking the file /var/lib/apt/lists/security.debian.org_dists_trixie-security_contrib_binary-arm64_Packages - TransItem::TransactionCommit (30: Read-only file system) Warning: Not using locking for read only lock file /var/lib/dpkg/lock-frontend Warning: Not using locking for read only lock file /var/lib/dpkg/lock Error: Archives directory /var/cache/apt/archives/partial is missing. - Acquire (2: No such file or directory) Warning: chown to _apt:root of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system) Warning: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system) Warning: chown to _apt:root of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system) Warning: chmod 0755 of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system) Warning: Not using locking for read only lock file /var/lib/apt/lists/lock Warning: Not using locking for read only lock file /var/lib/dpkg/lock-frontend Warning: Not using locking for read only lock file /var/lib/dpkg/lock Error: Archives directory /var/cache/apt/archives/partial is missing. - Acquire (2: No such file or directory) armbian-install only shows /dev/ but lsblk and blkid can see all drives. I am sorry for the long post.

perhaps someone who's more knowledgeable could update the script to work on newer versions than buster, like bookworm or trixie?

@remolaan "...Hey i have a SDMC DV8040 stb ,SoC-Amlogic S805X,CPU-Quad-core 1.2 GHz,GPU-ARM Mali-450,RAM-1GB,Storage-8GB it currently runs custom made android 9..." Please @remolaan, could you send me a working download link for the custom Android 9 system you made?

Hello. I have an old "Ott Amlogic S805 rlt8188 (wifi) 1GB/8GB" so Android 4.4.2 is fully outdated (It is no longer supported by Google, so it is unusable.) Is there an Armbian release that can be installed on "this fossil" 🙂 ?

You can add APA to your system and as one of the benefits get a managed GPG key so you should not run into this issue again in the future.

Armbian 25.8.1 Noble XFCE (mainline Kernel: 6.16.6-edge-rockchip64) + PanVk - mesa 23.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.7 (https://ryanfortner.github.io/box64-debs/) + wine-10.15-staging-tkg-ntsync-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.15) + DXVK-stripped v2.7.1 ~60fps@720p Hades

Hello @Ian Coelho, have you ever got any solution? I got the same issue

As long as you keep the discussion about this at their place... ophub is (ab)using the name Armbian without permission and they do not contribute to the core development process. Rather they trick users into thinking they get support here and therefore (ab)using our resources.

zero2w != zero2 moved

Hi All First post here. Have been using Rpi Zero 2W for a couple of years in various installations and other then speed been happy with it. So got an Orange Pi Zero 2 W in an attempt to use it as a plug in replacement for the Rpi. Installed Armbian and other than a booting issue, it all works. The first obstacle is the i2c, it is obvious that is nowhere near as easy as a Rpi to set up. I have read many posts and get more confused as the days go on. So, the question: Is there a step by step instruction on how to enable I2C. I am connecting 2 x ADS1115 A2D converters, one at &H48 and the 2nd at &H49. When I use i2cdetect -l i2c-0 i2c DesignWare HDMI i2c-1 i2c mv64xxx_i2c Adapter i2c-2 i2c ditto When I use i2cdetect -y 0 &h30 and &h50 show up When I use i2cdetect -y 1 I get UU on &h36 In software, I can do a fd = i2c_open("/dev/i2c-0") or use i2c-1 rc = i2cselect (fd,&h48,0) BUT, I cannot write or read to the device.(obviously because it does not exist according to i2cdetect ) My armbianEnv.txt has overlays=i2c3 changed from i2c0 after reading some posts. dtparam i2c_arm=on In armbian-config /system/kernel/booto001/ I have ticked i2c0-pi and for 2 and 3 as well. So after all that I have no idea how to proceed. Regards EDIT: kern.log has repeated entries as follows: mv64xxx_i2c 5002000 Error applying settings reverse things back

I have the tinkerboard rk3288, where do I find the mpv-legacy

Yeah, I wasn't asking for diagnostics, I realise that this issue could be for a myriad of reasons, just I was sure (before) that it was hardware related, now I'm not so sure. FWIW, it has just happened again less than an hour after boot, so I'm going to pull the card and chroot in to analyse. (I'm a software developer, so am well aware of the 'it don't go, what's wrong?' approach to tech support 😉) Interestingly, I was still logged in on an ssh shell, and I realised there was an issue when it was telling me that `cat` was an unknown command (clearly not!). I logged out, and now got the dreaded "Connection reset by 192.168.1.44 port 22". I also ran a full badblocks pass (4 real passes) on the SD card prior to imaging just to 100% make sure the card is fine. My main concern is that it will not have flushed logs to disk after the issue, so I suspect I will find nothing. ____ Edit: It looks like Armbian has rsync on a schedule to hold logs in RAM and perhaps periodically copy back to HDD. so unfortunately I have no useful info here. Going to look into the Armbian docs and see if I can get it to log directly to disk whilst I test. ______________ Another edit: I managed to disable ramlog, but unfortunately nothing of note has been written to the log files. I have tried connecting a monitor via HDMI, but am getting no output. I am sure this is fixable, but not sure how much I'm prepared to fiddle around with a box that just wants to lock up after some undetermined amount of time. I'm going to install the official Ubuntu 18.04 image (urrrgh) and leave it running for a long while. If that displays the same symptoms, then I can safely say this board is e-waste. If it does not, then I will come back to it and try to get myself an output.

@torz77 Without logs and diagnostic information it's hard to tell what is going on because what you're saying is the equivalent of "it doesn't work" Nonetheless I had the same symptoms when my SDcard was dying (bad sectors here and there). The kernel and network layer was loaded in to memory OK, so pings would work, but ssh calls upon extra binaries and files from the SD card and I was getting I/O errors, hence would result in SSH dying which is the connection refused the client sees. I had to connect mine to a display for the duration of a diagnostic session but thankfully it was easily reproducible so the error glared out. A replacement SD card got me there.