04-05-2020, 11:19 AM
(04-05-2020, 08:53 AM)moonwalkers Wrote: You should first try to use apt, reboot, and run `uname -a`. It's easy, it's quick, and it typically carries no more risk than manually copying the bootloader, firmware, etc., from GitHub. If after you've covered the basics the results are not what you expect - by all means, please ask this question again.
Speaking of U-boot (bootloader and firmware) - it is independent from kernel (and vice versa, kernel is independent from U-boot). There is a package that claims to support rk3399 SoC in Debian repos, but this installer currently uses the binary blob from mrfixit2001's repo. If you have installed your system before danielt@ updated the installer to use v2.0 of mrfixit2001's blob then you should update your bootloader manually - v2.0 has, among other things, a fix that allows to drop the 'maxcpus' workaround from kernel cmdline.
Actually, I've done apt and have the 5.5 kernel now.
My question regarding the rk3399-pinebook-pro.dtb and the firmware blobs. How far as I understand, they were copied by the installer from the GitHub .
Now they are updated there, but not in my system.
In Debian's repos I see u-boot-rockchip, should I install it?
PBP ISO / Debian Bullseye (unofficial installer)