02:02 <Armbian-Discord> <T​onymac32> Insulted? Haha

02:28 <stipa> life will be hard without archetech

16:09 <abws> if I disable the 2 big cpus in the rk3399 on helios64 the board boot, if I enable 5 cpus (with nr_cpus=5) it crashes in various ways

16:23 <[TheBug]> okay?

17:07 <abws> sorry, then I noticed with with cpufreq.off=1 a boot arg all is fine

17:09 <abws> helios64 has the max-buck-steps-per-change which fix overshoot ... but for cpu_l not cpu_b

17:52 <nekomancer[m]> abws first of all helios64 now can't be build because it need patches to u-boot, or rollback u-boot to working version

18:01 <Armbian-Discord> <p​sztoch> I have problem with fdtoverlays /dtbo/rockchip-enms1.dtbo in extlinux.conf.

18:01 <Armbian-Discord> <p​sztoch> There is error: Invalid fdtoverlay_addr_r for loading overlays:```

18:01 <Armbian-Discord> <p​sztoch> Scanning nvme 0:1...

18:01 <Armbian-Discord> <p​sztoch> Found /extlinux/extlinux.conf

18:01 <Armbian-Discord> <p​sztoch> Retrieving file: /extlinux/extlinux.conf

18:01 <Armbian-Discord> <p​sztoch> U-Boot menu

18:01 <Armbian-Discord> <p​sztoch> 1: EtherMatic Linux 2021 5.15.77-rockchip64

18:01 <Armbian-Discord> <p​sztoch> 2: EtherMatic Linux 2021 5.15.77-rockchip64 (rescue target)

18:01 <Armbian-Discord> <p​sztoch> Enter choice: 1: EtherMatic Linux 2021 5.15.77-rockchip64

18:01 <Armbian-Discord> <p​sztoch> Retrieving file: /initrd.img-5.15.77-rockchip64

18:01 <Armbian-Discord> <p​sztoch> Retrieving file: /vmlinuz-5.15.77-rockchip64

18:01 <Armbian-Discord> <p​sztoch> append: root=UUID=6b198f5a-aa3d-4f1b-a12f-298036d7f8e0 console=ttyS2,1500000 ro no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 Retrieving file: /dtbs/5.15.77-rockchip64/rockchip/rk3399-rock-pi-4a.dtb

18:01 <Armbian-Discord> <p​sztoch> Invalid fdtoverlay_addr_r for loading overlays

18:02 <Armbian-Discord> <p​sztoch> Moving Image from 0x2080000 to 0x2200000, end=3fd0000

18:02 <Armbian-Discord> <p​sztoch> ## Flattened Device Tree blob at 01f00000

18:02 <Armbian-Discord> <p​sztoch> ```

18:07 <abws> nekomancer[m]: the dvfs issue looks way more critical than the u-boot lagging behind for a year or two

18:08 <abws> the only way to have a usable system with what I run on this helios64 is cpufreq.off=1 a boot arg

18:09 <abws> I plan to get a shot at doing the u-boot upgrade

18:09 <abws> I hope it is in my league. But this cpu_b issue I need help (clues I mean)

18:14 <abws> in fact I sepnd a lot of toime on the emmc issue (hs400es being broken on most - all? - rk339 boards to end up findind that the issue I nailed the bug to was fixed in linux 6.1

18:16 <abws> but for two years clues about the dvfs issue have been about vdd_log and cpu_l . Though today I tried to only start a subset of the cpu and it turns out that if I only starts 4 of them, only the little cpu are started and all is fine

18:17 <abws> so it seems the cause has never been worked on. cpu_b ...

18:18 <abws> Can I phase out a faulty IC ?

18:21 <abws> and by sheer luck I have an easy reproducer of the dvfs issue (at times it took 14 days to reproduce, here I have a crash at each boot with a cpu_b at ondemand cpufreq)

18:22 <abws> nekomancer[m]: sorry I read anew what you wrote. I did not upgrade u-boot (the borken one as far as I understood does not even build)

18:54 <Armbian-Discord> <p​sztoch> Why fdtoverlay_addr_r is invalid, if it is present in u-boot/v2022.07/include/configs/rk3399_common.h?

18:56 <nekomancer[m]> somewhere around 6.1 should be a crypto and rng hardware sypport for rk3[23]xx

19:01 <Armbian-Discord> <p​sztoch> There was Loading Environment from SPIFlash...... And after env default -a, env save problem is gone.

19:22 <nekomancer[m]> 🛴

19:23 <nekomancer[m]> https://github.com/montjoie/linux/commits/cryptorockchipv4b

19:34 <montjoie> it is merged since 2/3 weeks

19:34 <montjoie> so will land in next release

19:35 <montjoie> probably 6.2 ?

19:36 <montjoie> but my serie is only fixing crypto and not rng

20:58 <Armbian-Discord> <d​ave> Is that 100% in sync with the rsync.armbian.com endpoint?