Jump to content

ebin-dev

Members
  • Posts

    436
  • Joined

  • Last visited

Everything posted by ebin-dev

  1. 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
  2. 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.
  3. 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.
  4. @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.
  5. @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 .
  6. @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
  7. @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.
  8. @prahal Thanks for fixing this bug ! You mentioned, that you are investigating the emmc hs400 issue. Once you (or someone else) found a solution to it, please let us know. We could then try to test newer versions of the linux kernel and see what remains to be done.
  9. 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
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines