denni_isl

  • Posts

    113
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

denni_isl's Achievements

  1. To turn off the annoying heartbeat blue light.
  2. One has to freeze kernel and u-boot upgrades because generation of new uInitr does disable linux kernel hdmi. Disabling of hdmi in u-boot has to be implemented into armbian nanopi-m4v2 u-boot.
  3. Did try few resent images as of beginning of feb 21 for nanopi-m4v2 and compiled my own using the armbian build and tried to move u-boot support for hdmi - bud did have to plug the hdmi cable after starting kernel .... This pilter75 image does bypass u-boot hdmi and therefore allows the kernel control of hdmi https://users.armbian.com/piter75/Armbian_21.05.0-trunk_Nanopim4v2_buster_current_5.10.18_minimal-stability-fix.img.xz There is one problem - USB 3 do flicker. It is not possible to restore with rsync. Might be because I did install full firmware or overclocking. Edit: It is either - USB is working okay without full firmware and overclocking.
  4. Is it the new u-boot hdmi bug (conflict) u-boot hdmi - kernel hdmi https://github.com/armbian/build/pull/2016/files ?
  5. Related; A guide https://zuckerbude.org/armbian-using-create-patches/ to use armbian build script to patch u-boot and kernel and make adjustment to boards device tree blob - dtb.
  6. And the legacy kernel that does always boot up - mbian 21.02.1 Bullseye with Linux 4.4.213-rk3399.
  7. Some progress, rk3399-nanopi-m4.dtb does bring everyting up exept hdmi - the others on the list did just end at Starting kernel ..... rk3399-orangepi-4.dtb does also bring up the board. But no hdmi connection - just UART apt update - apt upgrade and the new image boots up
  8. Trying to boot legacy Armbian_20.11.10_Firefly-rk3399_bionic_legacy_4.4.213_desktop
  9. Vondering if this has something to do with AppArmor or the hardware partitions grep APPARMOR /boot/config-* CONFIG_SECURITY_APPARMOR=y CONFIG_SECURITY_APPARMOR_HASH=y CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y # CONFIG_SECURITY_APPARMOR_DEBUG is not set CONFIG_DEFAULT_SECURITY_APPARMOR=y This is from successful Armbian 21.02.1 Focal with Linux 5.10.12-rockchip64 emmc boot
  10. ArmbianEnv.txt mainline focal 5.10.y from https://www.armbian.com/firefly-rk3399/ sd card boot up does not get any further than - starting kernel....... UART:
  11. Now it boots Armbian 21.02.1 Focal with Linux 5.10.12-rockchip64 successfully every time from emmc.
  12. Now it boots Armbian 21.02.1 Focal with Linux 5.10.12-rockchip64 successfully every time from emmc. To those of consern about /dev/mmcblk2boot0 and /dev/mmcblk2boot1 and RPMB partitiones. This is http://trac.gateworks.com/wiki/MMC some info about hardware partitions on some emmc. "man mmc-utils" and "sudo dpkg -L mtd-utils" and man mmc UART
  13. This is strange - "and totally easy going ". After starting the board with bullseye 4.4.213 SD card and then right away starting with fresh 5.4.43-rockchip64 SD card then it all of a sudden did boot up. Then armbian-config - sytem - boot and flash to emmc - but 5.4.43 does not boot now from emmc- same UART messages as from the SD card. Edit: Did boot from 4.4.213 sd card, shut down, remove sd card, reset button, stop u-boot - run bootcmd_mmc1, and 5.4.43 did boot up from emmc. apt update; apt upgrde and reboot now and reboots so it is working. ------------------------------------------- There are always 3 small boot partitions on the mmc and some u-boot there - Boot1: 2019-03-14, version: 1.19 Is it possible to wipe those partitions clean without bricking the firefly-rk3399 board?