Hi again! After that install of the kernel I tried a reinstall via... # apt-get install --reinstall linux-image-4.18.0-2-arm64 Lendo as listas de paquetes... Feito Construindo a árbore de dependencias Lendo a información do estado... Feito 0 anovados, 0 instalados, 1 reinstalados, Vanse retirar 0 e deixar 51 sen anovar. Ten que recibir 0 B/36,5 MB de arquivos. Despois desta operación ocuparanse 0 B de disco adicionais. (A ler a base de datos ... 31785 files and directories currently installed.) Preparing to unpack .../linux-image-4.18.0-2-arm64_4.18.10-2_arm64.deb ... Unpacking linux-image-4.18.0-2-arm64 (4.18.10-2) over (4.18.10-2) ... A configurar linux-image-4.18.0-2-arm64 (4.18.10-2) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.18.0-2-arm64 raspi3-firmware: deferring update via initramfs-tools (hook will be called later by the kernel
What I saw there was that the propagation to /boot/firmware had been done by raspi3-firmware before the update-initramfs had built the new initrd and later the new initrd is not propagated to firmware, so I ended up with an older -2 initrd on the firmware dir. Regards. -- Manty/BestiaTester -> http://manty.net
