jimt

  • Posts

    7
  • Joined

  • Last visited

Profile Information

  • Location
    Ito, Shizuoka, JAPAN
  • Interests
    7J1AJH / ZL2IA / AI8A

Contact Methods

  • Matrix
    jimt@matrix.org
  • Mastodon
    @jimt@mastodon.OERu.org
  • IRC
    jimt on Freenode
  • Github
    jimt

jimt's Achievements

  1. 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.
  2. 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?
  3. Mine rebooted successfully after update, but the Ethernet is still broken... so I am using a USB Ethernet adapter.
  4. 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.
  5. jimt

    jimt

  6. 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).
  7. 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)
  8. 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.)