Heisath

Members
  • Posts

    280
  • Joined

  • Last visited

1 Follower

About Heisath

Profile Information

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

2755 profile views
  1. I will run mvebu tests tomorrow. Sorry for not being available for the meeting, turns out, building a house is a pretty major thing...
  2. No I do not think so. The hardware is nearly the same - base is just pro with removed devices.
  3. Yeah it is totally possible. Generally just follow official debian upgrade instructions. Which come down to making sure you have a clean install (apt update, upgrade, autoremove, clean), then upgrading the apt.source (replacing buster with bullseye) then upgrading via apt update, apt full-upgrade etc. Need to fix conflicts along the way. https://linuxize.com/post/how-to-upgrade-debian-10-to-debian-11/ Also adjust armbian apt sources if neccessary.
  4. Above seems like a general armbian problem, not ebin specific. @lanefu you did something https://armbian.atlassian.net/browse/AR-445 Maybe it is not enough?
  5. Newest please - don't want to keep the old stuff around.
  6. I think the uboot and atf should be built with aarch, the wtmi with gnueabi. See: https://gitlab.nic.cz/turris/mox-boot-builder
  7. Yeah but that is not espressobin specific I guess - so I'll leave my hands off it for the moment No idea why apt fails.
  8. @y52 first of all thanks for testing and replying with complete + helpful logs and analyzation! This is indeed a problem. But I don't think the uboot error is responsible: as it is visible in armbian and mainline uboot! If this this CZ.NIC firmware is needed, I will check how to add it. I think this is ebin v5 vs v7. I will look into how-to remove the mtdparts, the loglevel will stay (it is user adjustable via armbianEnv.txt), not sure what the part about timestamps is about, could you clarify? Network settings like this are user defined. Maybe someone wants DHCP on eth0. We don't know that. I'm hesitant to change anything here, please give more reason why. I will remove the MAC addresses. Not sure how we can "generate a valid one".
  9. I built an image today: https://drive.google.com/file/d/1uZ4Pn_APPs9cJEpjV6-Nn7b1Ib6Ykh8W/view?usp=sharing maybe you can use this. Otherwise best to use Virtual Box or Docker. Building on Arm is also possible, but I don't know details.
  10. Ok so building the packages works, but image build does not. I will see if I can fix this. @y52 what host system are you building on? Recommended is a virtual machine running Ubuntu Hirsute. You need atleast the OS version, which you're bootstrapping. So if you wanna produce bullseye need atleast bullseye or ubuntu equivalent (hirsute). https://docs.armbian.com/Developer-Guide_Build-Preparation/ EDIT: Image build on hirsute seems to work: [ o.k. ] Mount point [ o.k. ] Ending debootstrap process and preparing cache [ bullseye ] [ o.k. ] Unmounting [ /home/user/build/.tmp/rootfs-89867f8c-41b7-4ec1-aecf-5e1b88411dd8 ] bullseye-cli-arm64.ead...ad3.tar.lz4: 1008MiB [56.1MiB/s] [=========================================================================================================================================================================================================================] 106% [ o.k. ] Applying distribution specific tweaks for [ bullseye ] [ o.k. ] Applying common tweaks [ .... ] Cleaning [ package lists ] [ .... ] Updating [ package lists ] [ .... ] Temporarily disabling [ initramfs-tools hook for kernel ] [ .... ] Installing [ linux-u-boot-current-espressobin_22.02.0-trunk_arm64.deb ] [ .... ] Installing [ linux-image-current-mvebu64_22.02.0-trunk_arm64.deb ] [ .... ] Installing [ linux-dtb-current-mvebu64_22.02.0-trunk_arm64.deb ] [ .... ] Installing [ armbian-bsp-cli-espressobin_22.02.0-trunk_arm64.deb ] [ .... ] Installing [ armbian-firmware_22.02.0-trunk_all.deb ] [ .... ] Installing [ armbian-config_22.02.0-trunk_all.deb ] [ .... ] Installing [ armbian-zsh_22.02.0-trunk_all.deb ] [ .... ] Installing from repository [ wireguard-tools --no-install-recommends ] [ o.k. ] Enabling serial console [ ttyMV0 ] [ o.k. ] Building kernel splash logo [ bullseye ] [ .... ] Installing extras-buildpkgs [ hostapd htop ] [ o.k. ] Calling image customization script [ customize-image.sh ] [ o.k. ] No longer needed packages [ purge ] [ o.k. ] Unmounting [ /home/user/build/.tmp/rootfs-89867f8c-41b7-4ec1-aecf-5e1b88411dd8 ] [ o.k. ] Preparing image file for rootfs [ espressobin bullseye ] [ o.k. ] Current rootfs size [ 1360 MiB ] [ o.k. ] Creating blank image for rootfs [ 1708 MiB ] [ .... ] dd: 1.67GiB [ 124MiB/s] [=================================================================================================================================================================================================================================================>] 100% [ o.k. ] Creating partitions [ root: ext4 ] [ .... ] Creating rootfs [ ext4 on /dev/loop11p1 ] [ .... ] Copying files to [ / ] [ .... ] Copying files to [ /boot ] sent 26.63M bytes received 643 bytes 53.26M bytes/sec total size is 26.62M speedup is 1.00 [ .... ] Updating initramfs... [ update-initramfs -uv -k 5.15.26-mvebu64 ] [ o.k. ] Updated initramfs. [ for details see: /home/user/build/output/debug/install.log ] [ .... ] Re-enabling [ initramfs-tools hook for kernel ] [ o.k. ] Unmounting [ /home/user/build/.tmp/mount-89867f8c-41b7-4ec1-aecf-5e1b88411dd8/ ] [ o.k. ] Free SD cache [ 10% ] [ o.k. ] Mount point [ 88% ] [ o.k. ] Writing U-boot bootloader [ /dev/loop11 ] [ o.k. ] SHA256 calculating [ Armbian_22.02.0-trunk_Espressobin_bullseye_current_5.15.26.img ] [ warn ] GPG signing skipped - no GPG_PASS [ Armbian_22.02.0-trunk_Espressobin_bullseye_current_5.15.26.img ] [ o.k. ] Done building [ /home/user/build/.tmp/image-89867f8c-41b7-4ec1-aecf-5e1b88411dd8/Armbian_22.02.0-trunk_Espressobin_bullseye_current_5.15.26.img ] [ o.k. ] Runtime [ 29 min ] [ o.k. ] Repeat Build Options [ ./compile.sh BOARD=espressobin BRANCH=current RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img ] user@builder:~/build$
  11. I am not sure if this is your problem, but working on SD cards I realized they are quite sensitive to voltage, ripple, signal path/delay etc. So if you made this board on your own, definitely check if the routing and buffering (power) on the SD lines is good. Also uboot might be using slower SD speeds (thus frequency) and work.
  12. Seems weird or really kinda broken. Its been now 5days(?) since release, I ran those commands, no newer versions found: root@cfp-router:~# apt update Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://security.debian.org bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://deb.debian.org/debian bullseye-backports InRelease Hit:5 http://mirror.armbian.de/apt bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@cfp-router:~# apt list linux-image-current-mvebu Listing... Done linux-image-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] N: There are 5 additional versions. Please use the '-a' switch to see them. root@cfp-router:~# apt list linux-image-current-mvebu -a Listing... Done linux-image-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] linux-image-current-mvebu/bullseye 21.08.1 armhf linux-image-current-mvebu/bullseye 21.08 armhf linux-image-current-mvebu/bullseye 21.05.1 armhf linux-image-current-mvebu/bullseye 21.02.3 armhf linux-image-current-mvebu/bullseye 21.02.2 armhf If I check the mirror apt was using manually: http://mirror.armbian.de/apt/pool/main/l/linux-5.15.25-mvebu/ there clearly are current files 22.02.1 which should be used. Still calling apt with explicit version gives: root@cfp-router:~# apt install linux-image-current-mvebu=22.02.1 Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Version '22.02.1' for 'linux-image-current-mvebu' was not found
  13. http://armbian.hosthatch.com/apt/pool/main/l/linux-5.15.25-mvebu/ Checking there, it seems like the packages for 5.15 mvebu already exist. Maybe mirrors are still syncing.
  14. Helios4 is supported and I am the maintainer, thats correct. I tested bullseye on the device, it works as expected. On the issue on not existing packages I can't help unfortunately. I did confirm this issue though: root@cfp-router:~# apt update Get:1 http://security.debian.org bullseye-security InRelease [44.1 kB] Hit:2 http://deb.debian.org/debian bullseye InRelease Get:3 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB] Get:4 http://deb.debian.org/debian bullseye-backports InRelease [44.2 kB] Hit:5 http://armbian.12z.eu/apt bullseye InRelease Get:6 http://deb.debian.org/debian bullseye-backports/main armhf Packages.diff/Index [63.3 kB] Get:7 http://deb.debian.org/debian bullseye-backports/main all Contents (deb).diff/Index [63.6 kB] Get:8 http://deb.debian.org/debian bullseye-backports/main armhf Contents (deb).diff/Index [63.5 kB] Get:9 http://deb.debian.org/debian bullseye-backports/contrib armhf Packages.diff/Index [14.0 kB] Get:10 http://deb.debian.org/debian bullseye-backports/main armhf Packages T-2022-03-02-1402.19-F-2022-02-27-0802.11.pdiff [7,572 B] Get:11 http://deb.debian.org/debian bullseye-backports/main all Contents (deb) T-2022-03-02-1402.19-F-2022-02-27-1401.47.pdiff [1,125 B] Get:12 http://deb.debian.org/debian bullseye-backports/main armhf Contents (deb) T-2022-03-02-0201.01-F-2022-02-27-0802.11.pdiff [402 B] Get:10 http://deb.debian.org/debian bullseye-backports/main armhf Packages T-2022-03-02-1402.19-F-2022-02-27-0802.11.pdiff [7,572 B] Get:11 http://deb.debian.org/debian bullseye-backports/main all Contents (deb) T-2022-03-02-1402.19-F-2022-02-27-1401.47.pdiff [1,125 B] Get:12 http://deb.debian.org/debian bullseye-backports/main armhf Contents (deb) T-2022-03-02-0201.01-F-2022-02-27-0802.11.pdiff [402 B] Get:13 http://deb.debian.org/debian bullseye-backports/contrib armhf Packages T-2022-03-02-0201.01-F-2022-03-01-2001.26.pdiff [418 B] Get:13 http://deb.debian.org/debian bullseye-backports/contrib armhf Packages T-2022-03-02-0201.01-F-2022-03-01-2001.26.pdiff [418 B] Fetched 342 kB in 18s (18.6 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@cfp-router:~# apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@cfp-router:~# apt list --installed | grep linux WARNING: apt does not have a stable CLI interface. Use with caution in scripts. binutils-arm-linux-gnueabihf/stable,now 2.35.2-2 armhf [installed,automatic] console-setup-linux/stable,now 1.205 all [installed,automatic] libselinux1/stable,now 3.1-3 armhf [installed] linux-base/stable,now 4.6 all [installed] linux-dtb-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] linux-headers-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] linux-image-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] linux-libc-dev/now 21.11.0-trunk.2 armhf [installed,local] linux-u-boot-clearfogpro-current/bullseye,now 21.08.8 armhf [installed] util-linux/stable-security,now 2.36.1-8+deb11u1 armhf [installed] root@cfp-router:~# EDIT: It seems like Repo rebuild is still in progress: https://github.com/armbian/build/actions/runs/1927292054