ebin-dev

Linux 6.1.36 is not affected by the dwc3 usb issue. The braking changes made it into the kernel after that. Thank you for confirming that you had no issues accessing emmc with that kernel - your system is even running from there. Your linux kernel uses the linux-tree version of the realtek driver r8152. It is based on an old version of the manufacturer and we have to test if it is reliable when used to drive the 2.5G interface. Once the dwc3 usb issue is resolved (upstream), I intend to build several versions of the linux kernel with different rtl8152 drivers so that performance and reliability can be compared.

@alchemist Thank you for the hint ! The dwc3 usb issue remains even if I compile a more recent realtek-r8152-linux driver into kernel 6.1.52. So the realtek driver does not seem to be the (only) reason for the issue. While compiling the kernel I was informed by the build system that 74 patches need to be rebased and that the rk3399-enable-dwc3-xhci-usb-trb-quirk.patch could not be applied - something has changed. This is how a system looks like that was not maintained for years ... P.S.: I will therefore currently not upgrade Helios64 (hosting all my data) to Armbian bookworm 23.05.4-6.1.36. It uses the linux-tree rtl8152 driver and needs proper testing first, in particular network performance (1Gbit/s and 2.5Gbit/s interfaces), reliability of accessing emmc and stability.

It does not matter if you refer to the current Armbian version as 23.8 as indicated on the helios64 download page or to 23.08 as indicated on the welcome screen. And it does not matter if it is 23.8.1. The important bit is that any current linux kernel or image (fully automatically) built by the Armbian build system does not provide any USB support for your Helios64 for linux kernel versions higher than 5.12. You could verify that yourself by upgrading your backup sd to the current kernel versions. Unless you have access to the original linux kernel debs you would have to reinstall your system entirely from scratch. You should therefore not upgrade your system to any current linux kernel produced by the Armbian build system until the linux rtl8152 driver is replaced for kernel versions higher than 5.12 (in this code). For the time being you could disable Armbian updates entirely (and still receive debian updates): cat /etc/apt/sources.list.d/armbian.list # deb http://apt.armbian.com bookworm main bookworm-utils bookworm-desktop

For linux versions higher than 5.12, the Armbian build system does not replace the realtek driver r8152 but it uses an aged realtek driver from the linux source tree. So if someone intends to build from sources at home, the realtek r8152 driver in the linux source tree must be replaced by a newer version, otherwise USB devices will not be accessible to helios64. It follows that all fully automated builds with the current Armbian build system building linux kernel versions higher than 5.12 will not support USB devices on helios64 anymore (until that is fixed). The good news is that there is an image available for download were the USB issue was fixed: Armbian_23.5.4_Helios64_bookworm_current_6.1.36.img (here)

A stable Armbian Bookworm configuration for your Helios64 is provided here (solved). ************************************************************************* Recently a new Armbian 23.08.1 Bookworm image with linux-6.1.50 was made available for Helios64 on its download page (see here) - which is as such great 😀. Everything starts up nicely, but unlike the previous Bookworm 23.05 image, the current one has an issue with accessing USB devices. In the boot process the following error occurs: # cat /var/log/syslog | grep error 2023-09-07T12:31:05.671598+02:00 helios64 kernel: [ 2.537009] dwc3 fe900000.usb: error -ETIMEDOUT: failed to initialize core 2023-09-07T12:31:05.671602+02:00 helios64 kernel: [ 2.537107] dwc3: probe of fe900000.usb failed with error -110 No USB device could be accessed. As this seems to be related to the realtek driver r8152, I compiled and installed the current version of that driver (see below) and after that the USB devices were accessible. # compile and install the current realtek driver git clone https://github.com/wget/realtek-r8152-linux.git cd realtek-r8152-linux... make sudo make install

That`s right - I am running bookworm off SD, since my bullseye system is still present on emmc. The effect of omitting the "BUILD_ONLY" option in the compile instruction is simply that everything is being compiled from sources such that the bookworm image is compiled too. And 'current' was used, since bookworm was designed to operate with that version of linux. A short test using 'hdparm -tT /dev/mmcblk1' #emmc indicates that emmc access speed with linux 6.1.45 is around 120MB/s (hs200), about half of what it used to be with linux 5.10.43 (220 MB/s = hs400). I can live with that, but before I copy the bookworm system from sd to emmc, could you please confirm that linux 6.1.xx can safely be used to read and write emmc using the slower hs200 mode ? P.S.: Regarding u-boot: before I became aware of your warning I already flashed the u-boot binaries to emmc using the blobs that came with the fresh bookworm image. emmc was still bootable and I did not oberve any issues. To be on the safe side, I reverted back to the original blobs present in my original bullseye image.

How to switch from network-manager to systemd-networkd is explained i.e here. Bookworm is up and running from SD for a few days now, but it would appear that emmc is still being accessed with hs200 speed.

@mrjpaxton Dist-upgrade(ing) from bullseye to bookworm did finally complete successfully. However, one should consider that device names have changed (otherwise your system may end up offline 🙂) the new interface names are: # interface names (bookworm) sd: /dev/mmcblk0 emmc: /dev/mmcblk1 eth0: end0 (1GBase-T ethernet) eth1: end1 (2.5GBase-T ethernet) P.S.: I am currently setting up bookworm from scratch starting from the fresh image to get rid of the stuff that accumulated during the last years.

@mrjpaxton I am about to upgrade linux from 5.10 to 6.1 now and if that works to dist-upgrade bullseye to bookworm. Just to prevent someone from telling us that this is not supported by Armbian - we already know that. Just in case you would like to try, here is a link to the most recent Armbian 23.08.0 - 6.1.45 bookworm image including all the linux-6.1.45 deb packages. You could also start with the fresh bookworm image, in case dist-upgrade to bookworm does not complete successfully with your installation. Armbian 23.08.0 - 6.1.45 bookworm image was compiled for Helios64 using the Armbian build system as mentioned in the parallel thread .

@prahal@balbes150 I just gave it a try and built a complete bookworm image (Armbian_23.08.0-trunk_Helios64_bookworm_current_6.1.49.img and corresponding linux 6.1.49 deb packages). The bookworm image boots without any issues. Thank you very much for your contributions! Now there should be an upgrade path from Debian bullseye to bookworm once linux is upgraded to 6.1.49. If that does not complete successfully I will set up the whole system starting from the fresh bookworm image. git clone https://github.com/armbian/build.git cd build ./compile.sh BOARD=helios64 BRANCH=current RELEASE=bookworm KERNEL_CONFIGURE=no P.S.: There is a more recent update on armbian.com/helios64

@privilegejunkie I am still on Linux 5.10.43-rockchip64 #21.05.4 SMP PREEMPT Wed Jun 16 08:02:12 UTC 2021 aarch64 GNU/Linux / debian bullseye 11.7. Would you provide a download link to the kernel you are using ? I could easily test it with debian bullseye. However, debian bookworm is about to be released and it comes with linux 6.1 LTS. So it would make some sense to test 6.1 kernels too for the ones who intend to upgrade.

Upgrading Helios64 from Armbian Buster to Bullseye (see below) works as expected on my system. However, I am using systemd-networkd and just a few services (nextcloud, netatalk, etc. and not ZFS) EDIT: Upgrading Buster installations to Bullseye also works fine if you use network-manager, even if you have a bridge configured (using bridge-slave; binutils-bridge). # cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 21.08.1 Bullseye with Linux 5.10.43-rockchip64 System load: 2% Up time: 12:29 Memory usage: 19% of 3.77G IP: xx.xx.xx.xx CPU temp: 42°C Usage of /: 41% of 15G storage/: 57% of 3.6T Edit: Attention - if you upgrade your Buster or Bullseye installation on emmc to Armbian 21.08.1 it will not be writable anymore. You will then have to downgrade linux on emmc from 5.10.60 to 5.10.43 as described in this thread. Edit: There is a temporary fix for the problem. See this message from @piter75 To upgrade Armbian Buster to Bullseye, first disable Armbian updates in /etc/apt/sources.list.d/Armbian.list for the time being. Then fully upgrade Buster (sudo apt update && sudo apt upgrade -y) , then change the apt sources (see below) followed by 'sudo apt update && sudo apt full-upgrade'. I kept all the configuration files by confirming 'N' in the following dialogue. # cat /etc/apt/sources.list deb http://deb.debian.org/debian/ bullseye main deb-src http://deb.debian.org/debian/ bullseye-updates main deb http://security.debian.org/debian-security bullseye-security main deb-src http://security.debian.org/debian-security bullseye-security main deb http://ftp.debian.org/debian bullseye-backports main