• Content Count

  • Joined

  • Last visited

Everything posted by eminguez

  1. Nice!!!! Do you happen to have a link to download the latest nightly? https://minio.k-space.ee/armbian/dl/pine64/nightly/Armbian_21.02.0-trunk.7_Pine64_buster_current_5.9.11.img.xz seems to fail for me. Thanks.
  2. armbian-firmware_20.08.14_all.deb 20-Oct-2020 22:04 6917020 armbian-firmware_20.08.15_all.deb 24-Oct-2020 21:01 1120 armbian-firmware_20.08.16_all.deb 24-Oct-2020 22:12 1120 https://armbian.systemonachip.net/apt/pool/main/a/armbian-firmware/ $ sudo dpkg -L armbian-firmware-full /. /lib /lib/firmware /lib/firmware/3com /lib/firmware/RTL8192E /lib/firmware/RTL8192SU /lib/firmware/acenic /lib/firmware/adaptec /lib/firmware/advansys /lib/firmware/amd /lib/firmware/ap6210 /lib/firmware/ap6212 /lib/firmware/ar3k /lib/firmware/ar3k/1020200 /lib/firmware/ar3k/1020201 /lib/firmware/ar3k/1
  3. After a fresh armbian installation + armbian-firmware-full package, the pine64 bluetooth doesn't work because the rtl8723bs_config-pine64.bin file is missing. I've downloaded the file from https://github.com/anarsoul/rtl8723bt-firmware/tree/master/rtl_bt into /lib/firmware/rtl_bt and it works so I've created a PR here https://github.com/armbian/firmware/pull/14 to add it to the firmware package so it can work out of the box. Let me know if I need to do something else for the PR to be merged. Thanks.
  4. Meanwhile, is there anything else that I can test/validate? Thanks!
  5. I tried but still black screen: root@pinebook-a64:/home/edu# uname -a Linux pinebook-a64 5.4.23-sunxi64 #trunk SMP Thu Mar 5 13:43:50 UTC 2020 aarch64 GNU/Linux root@pinebook-a64:/home/edu# zgrep "CONFIG_DRM_ANALOGIX_ANX6345" /proc/config.gz CONFIG_DRM_ANALOGIX_ANX6345=y
  6. I've created an armbian minimal image for my pinebook with luks encryption. It works fine but I cannot see the password prompt on screen... the boot process is: * The armbian uboot is displayed * Then a black screen... After a few seconds I'm assuming it is time to put my luks password, so I do it * Then the screen starts to show the boot text Is this expected? Am I doing something wrong? I don't want to install plymouth, just the usual LUKS password prompt. Thanks!
  7. I just want to confirm that using Armbian 19.11.6 on my pine64 (Linux pine64 5.4.7-sunxi64 #19.11.6 SMP Sat Jan 4 19:40:10 CET 2020 aarch64 GNU/Linux) for a couple of weeks with some workloads (single k3s cluster with some pods running) and 0 issues so far related to the clock. Thanks!
  8. I can confirm it's been >24h without the issue \o/ Also I've seen linux-image-dev-sunxi64/buster contains the fix, so I'm upgrading to that package version instead my custom compiled one. Thanks!
  9. That worked, the patch is applied, let's see if it works Thanks!
  10. I've tried to build the kernel with the current sources but it seems to fail to apply the patch. From the log file: Processing file /root/build/patch/kernel/sunxi-dev/fix-a64-timejump.patch 1 out of 1 hunk FAILED -- saving rejects to file drivers/clocksource/arm_arch_timer.c.rej It is just a clean git clone from the armbian/build repository and the following build flags: /compile.sh BOARD=pine64 BRANCH=dev KERNEL_ONLY=yes KERNEL_CONFIGURE=no The rej file: # find ~/build/cache/sources -type f -iname "*arm_arch_timer.c.rej*" /root/build/cache/sources/linux-mainline/orange-pi-5.
  11. I've updated to the latest one ( and I can confirm the fix is not yet there (probably by looking at the commit time and the build time it didn't entered in the build). In order to do that, I've downloaded the sources (https://apt.armbian.com/pool/main/l/linux-source-5.4.2-dev-sunxi64/linux-source-dev-sunxi64_19.11.3.346_all.deb) and the patch doesn't seem to be there (it would be nice if the debs have a changelog or if they can be shown somewhere) I'll wait for the next build Thanks!!!
  12. Thanks!!! How can I update the kernel to the latest build? Is there a nightly builds kernel repo? Is there a way to check if the patch is there as a 'regular user'? Thanks again!
  13. I've just installed latest armbian buster today, updated, switched to the latest 5.4.2 kernel via armbian-config and installed k3s (minimal k8s distro) on it and after a few minutes, 2113! I will try the attached patch but just in case, to me it is still unresolved in 5.4.2.
  14. Is this patch going to be added in future releases? Thanks!