robnielsen

@Efe Çetin Thanks, I successfully migrated to rk35xx with the stable branch. Maybe you want to update the note in the first post in this thread?

I upgraded to 23.8.1, and it appears that rk35xx is available in the stable branch. Is it safe to migrate? Welcome to Armbian 23.8.1 Bookworm with Linux 5.10.110-rockchip-rk3588 System load: 1% Up time: 8 min Memory usage: 7% of 15.35G IP: 192.168.1.2 CPU temp: 38°C Usage of /: 19% of 236G Tip of the day: Submit your desktop wallpaper creation! https://forum.armbian.com/topic/29433-armbian-desktop-wallpaper-contest/ Last login: Mon Sep 4 08:40:53 2023 from 192.168.1.30 rob@orangepi5:~$ apt-cache search rk35xx linux-dtb-edge-rk35xx - Armbian Linux DTB, version 6.1.11-rk35xx edge linux-dtb-legacy-rk35xx - Armbian Linux legacy DTBs in /boot/dtb-5.10.160-legacy-rk35xx linux-headers-edge-rk35xx - Linux kernel headers for 6.1.11-rk35xx on arm64 edge linux-headers-legacy-rk35xx - Armbian Linux legacy headers 5.10.160-legacy-rk35xx linux-image-edge-rk35xx - Linux kernel, armbian version 6.1.11-rk35xx edge linux-image-legacy-rk35xx - Armbian Linux legacy kernel image 5.10.160-legacy-rk35xx linux-source-6.1.11-edge-rk35xx - This package provides the source code for the Linux kernel 6.1.11

Any update on this yet?

Do you know when apt repo's will be updated?

I was able to get my Orange Pi 5 to boot to NVMe. I used https://jamesachambers.com/orange-pi-5-ssd-boot-guide/ as an example. Deleted partition on NVMe gdisk /dev/nvme0n1 Copied SD card to NVMD cat /dev/mmcblk1 > /dev/nvme0n1 Powered off the Orange Pi 5, removed the SD card and then powered it back on and it booted from the NVMe. I then resized the filesystem /usr/lib/armbian/armbian-resize-filesystem start Now I have: $ df -H Filesystem Size Used Avail Use% Mounted on udev 8.3G 0 8.3G 0% /dev tmpfs 1.7G 10M 1.7G 1% /run /dev/nvme0n1p2 254G 5.7G 245G 3% / tmpfs 8.3G 0 8.3G 0% /dev/shm tmpfs 5.3M 4.1k 5.3M 1% /run/lock tmpfs 8.3G 0 8.3G 0% /tmp /dev/nvme0n1p1 269M 158M 111M 59% /boot /dev/zram1 51M 4.8M 43M 11% /var/log tmpfs 1.7G 0 1.7G 0% /run/user/1000 $ mount | grep /dev/n /dev/nvme0n1p2 on / type ext4 (rw,noatime,errors=remount-ro,commit=600) /dev/nvme0n1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=936,iocharset=utf8,shortname=mixed,errors=remount-ro) /dev/nvme0n1p2 on /var/log.hdd type ext4 (rw,noatime,errors=remount-ro,commit=600)

I'm struggling to get my Orange Pi 5 to boot to NVMe with Armbian 23.02 Bullseye CLI. With armbian-install I picked: 4 Boot from MTD Flash - system on SATA, USB or NVMe then install to /dev/nvme0n1p1, followed by updating the bootloader on mtdbblock0, and then powering off. When I remove the SD drive, and reboot. The console remains blank. When I insert the SD drive, and reboot again, the system comes up, and I can mount /dev/nvme0n1p1: $ df -h Filesystem Size Used Avail Use% Mounted on udev 7.7G 0 7.7G 0% /dev tmpfs 1.6G 9.6M 1.6G 1% /run /dev/mmcblk1p2 30G 2.0G 27G 7% / tmpfs 7.7G 0 7.7G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 7.7G 0 7.7G 0% /tmp /dev/mmcblk1p1 256M 150M 106M 59% /boot /dev/zram1 49M 4.1M 41M 10% /var/log tmpfs 1.6G 0 1.6G 0% /run/user/1000 /dev/nvme0n1p1 234G 1.7G 221G 1% /mnt /dev/nvme0n1p1 looks like it's a clone of / Any ideas/suggestions?

Just to follow up on this. I replaced the SD card and then checked out the card that gave me errors. After reformatting the SD card and running H2testw it came back with the following: Test finished without errors. You can now delete the test files *.h2w or verify them again. Writing speed: 32.2 MByte/s Reading speed: 69.4 MByte/s H2testw v1.4 So as I suspected, the SD card was not failing. Rob

I created a /forcefsck and rebooted to force a fsck of / and it completed with no errors. Running tune2fs even shows that the filesystem state is clean: $ sudo tune2fs -l /dev/mmcblk0p1 tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: <none> Last mounted on: / Filesystem UUID: 213dcf34-ef86-404d-953f-1c5ff176493f Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: journal_data_writeback user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 954720 Block count: 3811488 Reserved block count: 41349 Free blocks: 3388064 Free inodes: 892869 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 79 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8160 Inode blocks per group: 510 Flex block group size: 16 Filesystem created: Sun Feb 5 14:55:01 2017 Last mount time: Mon May 1 11:44:53 2017 Last write time: Wed Dec 31 18:00:05 1969 Mount count: 23 Maximum mount count: -1 Last checked: Sun Feb 5 14:55:01 2017 Check interval: 0 (<none>) Lifetime writes: 4046 MB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: b5982d4f-1ead-45ee-a7b1-848a58aca1e7 Journal backup: inode blocks

I was able to get the other packages updated, and the unneeded ones removed, so the SD card is definitely not bad. Now I'm just stuck with a half-installed linux-image-next-sunxi package. If try and update I get the below errors. Is there any way to uninstall the half installed package? $ sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed. Need to get 0 B/15.6 MB of archives. After this operation, 0 B of additional disk space will be used. dpkg: error processing package linux-image-next-sunxi (--configure): package linux-image-next-sunxi is not ready for configuration cannot configure (current status `half-installed') Errors were encountered while processing: linux-image-next-sunxi E: Sub-process /usr/bin/dpkg returned an error code (1)

None of the filesystems are mounted read only, and I can read/write files to / with no problems.

I'm getting the following errors when running "apt-get upgrade" by banana pi: $ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following package was automatically installed and is no longer required: python-dialog Use 'apt-get autoremove' to remove it. Done The following packages will be upgraded: certbot linux-image-next-sunxi python-acme python-certbot 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 15.9 MB/16.1 MB of archives. After this operation, 1,021 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://apt.armbian.com/ jessie/main linux-image-next-sunxi armhf 5.27.170427 [15.9 MB] Fetched 15.9 MB in 14s (1,102 kB/s) (Reading database ... 56352 files and directories currently installed.) Preparing to unpack .../linux-image-next-sunxi_5.27.170427_armhf.deb ... Removing obsolete file 4.9.12-sunxi Removing obsolete file uInitrd-4.9.12-sunxi Unpacking linux-image-next-sunxi (5.27.170427) over (5.26) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-next-sunxi_5.27.170427_armhf.deb (--unpack): unable to create `/lib/modules/4.10.12-sunxi/kernel/drivers/media/rc/keymaps/rc-cinergy-1400.ko.dpkg-new' (while processing `./lib/modules/4.10.12-sunxi/kernel/drivers/media/rc/keymaps/rc-cinergy-1400.ko'): Read-only file system dpkg: error while cleaning up: unable to remove newly-extracted version of `/lib/modules/4.10.12-sunxi/kernel/drivers/media/rc/keymaps/rc-cinergy-1400.ko': Read-only file system This is followed by a few thousand lines of cleanup errors, followed by: dpkg: error while cleaning up: unable to remove newly-extracted version of `/usr/lib/linux-image-next-sunxi/overlay/sun4i-a10-uart7.dtbo': Read-only file system dpkg: error while cleaning up: unable E: Sub-process /usr/bin/dpkg returned an error code (2) E: Failed to write temporary StateFile /var/lib/apt/extended_states.tmp If I reboot it recovers, but if I try to run the upgrade again I get: $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a $ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following package was automatically installed and is no longer required: python-dialog Use 'apt-get autoremove' to remove it. Done The following packages will be upgraded: certbot linux-image-next-sunxi python-acme python-certbot 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/16.1 MB of archives. After this operation, 1,021 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 56352 files and directories currently installed.) Preparing to unpack .../linux-image-next-sunxi_5.27.170427_armhf.deb ... Removing obsolete file 4.9.12-sunxi Removing obsolete file uInitrd-4.9.12-sunxi Unpacking linux-image-next-sunxi (5.27.170427) over (5.26) ... dpkg-deb (subprocess): cannot copy archive member from '/var/cache/apt/archives/linux-image-next-sunxi_5.27.170427_armhf.deb' to decompressor pipe: failed to read (Input/output error) dpkg-deb (subprocess): decompressing archive member: lzma error: unexpected end of input dpkg-deb: error: subprocess <decompress> returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/linux-image-next-sunxi_5.27.170427_armhf.deb (--unpack): cannot copy extracted data for './lib/modules/4.10.12-sunxi/kernel/drivers/net/usb/r8152.ko' to '/lib/modules/4.10.12-sunxi/kernel/drivers/net/usb/r8152.ko.dpkg-new': unexpected end of file or stream run-parts: failed to open directory /etc/kernel/postrm.d: Input/output error dpkg: error while cleaning up: subprocess new post-removal script returned error exit status 1 dpkg: error processing archive /var/cache/apt/archives/certbot_0.10.2-1~bpo8+1_all.deb (--unpack): unable to sync file '/var/lib/dpkg/tmp.ci//postinst': Input/output error dpkg: error processing archive /var/cache/apt/archives/python-certbot_0.10.2-1~bpo8+1_all.deb (--unpack): unable to sync file '/var/lib/dpkg/tmp.ci//postinst': Input/output error dpkg: error processing archive /var/cache/apt/archives/python-acme_0.10.2-1~bpo8+1_all.deb (--unpack): unable to sync file '/var/lib/dpkg/tmp.ci//postinst': Input/output error dpkg: error: unable to sync new file '/var/lib/dpkg/status-new': Input/output error E: Sub-process /usr/bin/dpkg returned an error code (2) How can I fix this? Thanks! Rob