Jump to content

jimt

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by jimt

  1. I notice my VIM3 Pro negotiated 12V power when running the originally supplied Android image or the Rescue image, but when using Armbian 23.02.2 Jammy with Linux 6.1.11-meson64 it stays at 5V.
  2. I tried setting SKIP_BOOTSPLASH=yes from Hidden options for advanced users of the Build Options page, but the Armbian splash screen still appears. Since I have to ask here, I am obviously not an advanced user. 🙃 How do I eliminate the boot splash screen as I am building/testing images? ./compile.sh \ BOARD=visionfive2 \ BRANCH=edge \ RELEASE=lunar \ BUILD_MINIMAL=no \ BUILD_DESKTOP=no \ KERNEL_CONFIGURE=no \ SKIP_BOOTSPLASH=yes \ CARD_DEVICE="/dev/sdb"
  3. On Armbian_23.5.0-trunk.140_Visionfive2_lunar_edge_5.15.0.img.xz chrony fails to start: May 02 23:24:48 visionfive2 systemd[1]: Starting chrony.service - chrony, an NTP client/server... May 02 23:24:48 visionfive2 chronyd[1874]: chronyd version 4.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGN> May 02 23:24:48 visionfive2 chronyd[1874]: Using right/UTC timezone to obtain leap second data May 02 23:24:48 visionfive2 chronyd[1874]: Fatal error : Failed to load seccomp rules May 02 23:24:48 visionfive2 chronyd-starter.sh[1872]: Failed to load seccomp rules May 02 23:24:48 visionfive2 systemd[1]: chrony.service: Control process exited, code=exited, status=1/FAILURE May 02 23:24:48 visionfive2 systemd[1]: chrony.service: Failed with result 'exit-code'. May 02 23:24:48 visionfive2 systemd[1]: Failed to start chrony.service - chrony, an NTP client/server. So I am using ntpdate (from ntpsec-ntpdate) at boot.
  4. When using the "boot from SD install to NVMe" option of armbian-config it offered the option to format the NVMe drive with btrfs. When I selected that option, it briefly flashed an error about the partition being too small (even though I had created a 120GB partition). The actual problem appears to have been that btrfs-progs was not installed. After installing that package and rerunning armbian-config it was possible to btrfs format and install successfully. I suggest the error message could be improved. Armbian_22.11.1_Rockpi-4cplus_jammy_current_5.15.80_minimal.img.xz
  5. Great, thanks. (FWIW, it seems to be working on mine (including NVMe) in a day's casual use. The only missing feature I've noticed so far is support for the optional SPI for booting.)
  6. The link to nightly builds for the Rockpi 4C+ WIP on https://www.armbian.com/rockpi4/ is broken. (Perhaps it should link directly to https://github.com/armbian/community ?)
  7. jimt

    Odroid C4

    I moved to the Manjaro ARM distribution for my C4s. Obviously, a different package manager/ecosystem and it has only been a week... but so far so good.
  8. jimt

    Odroid C4

    I ended up doing a backup and installing the Armbian Focal mainline kernel 5.9.y image and the onboard Ethernet is working again. The versions of the linux-* and armbian-config packages claim to be the same. Something else apparently hadn't survived one of the updates about 1.5 months ago. As Arpel mentioned, it seems the C4 always wants to boot from the eMMC, even if there is a bootable SD card is present. Is there a way to change that boot order?
  9. jimt

    Odroid C4

    Mine rebooted successfully after update, but the Ethernet is still broken... so I am using a USB Ethernet adapter.
  10. After updating to 5.7.15-rockchip64 #20.08 I needed to add "/sys/devices/platform/pwm-fan/hwmon/hwmon3/pwm1" to the PWM_CTL array in /etc/ats.conf.
  11. jimt

    jimt

  12. jimt

    Odroid C4

    Oh. I hadn't done the switched to nightly images step. I had been expecting the updates to magically appear in the standard package pool so that apt update was sufficient. Sorry for the misunderstanding. I just reflashed, created user account, rebooted, used armbian-config to switch to nightly... and have successfully rebooted. Thanks for your help (and patience).
  13. jimt

    Odroid C4

    Yes, I had done: apt update && apt -y dist-upgrade I've just (2020-05-11T02:28:00Z) tried again: reflashed 32GB eMMC with Armbian_20.02.14_Odroidc4_focal_current_5.4.39.img did initial boot, created user account successfully rebooted logged in as newly created user and did apt update && apt -y dist-upgrade reboot... board never returns Start-Date: 2020-05-11 02:22:39 Commandline: apt -y dist-upgrade Requested-By: jim (1000) Upgrade: linux-image-current-meson64:arm64 (20.02.14, 20.02.15), linux-libc-dev:arm64 (5.4.0 -26.30, 5.4.0-29.33), libldap-2.4-2:arm64 (2.4.49+dfsg-2ubuntu1, 2.4.49+dfsg-2ubuntu1.2), li bpython3.8-minimal:arm64 (3.8.2-1ubuntu1, 3.8.2-1ubuntu1.1), libpython3.8:arm64 (3.8.2-1ubun tu1, 3.8.2-1ubuntu1.1), python3.8:arm64 (3.8.2-1ubuntu1, 3.8.2-1ubuntu1.1), linux-dtb-curren t-meson64:arm64 (20.02.14, 20.05.0-trunk), armbian-firmware:arm64 (20.02.14, 20.05.0-trunk), python3.8-minimal:arm64 (3.8.2-1ubuntu1, 3.8.2-1ubuntu1.1), libldap-common:arm64 (2.4.49+df sg-2ubuntu1, 2.4.49+dfsg-2ubuntu1.2), distro-info-data:arm64 (0.43ubuntu1, 0.43ubuntu1.1), a rmbian-config:arm64 (20.02.14, 20.05.0-trunk), linux-u-boot-odroidc4-current:arm64 (20.02.14 , 20.05.0-trunk), libpython3.8-stdlib:arm64 (3.8.2-1ubuntu1, 3.8.2-1ubuntu1.1)
  14. jimt

    Odroid C4

    Thanks. I just ran into the same thing with the upgrade to the Focal image. (Perhaps Igor's fix for the updating problem mentioned later in this thread hasn't trickled out to whatever mirror I had updated from.)
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines