lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<Armbian-Discord> <M​icroLinux (Salva)> for the record, tried to boot amrbian debian sid 5.19 gnome on T4 and didnt boot correctly.
<Armbian-Discord> <M​icroLinux (Salva)> @balbes150
<Armbian-Discord> <M​icroLinux (Salva)> going to test 5.18 jammy
<Armbian-Discord> <M​icroLinux (Salva)> okay, Installed jammy 5.18 and boots correctly, everything working fine from sd. but after installing to the emmc from armbian-config uboot enters a loop in which doesnt boot from emmc
<Armbian-Discord> <l​anefu> is that on the record too?
<Armbian-Discord> <M​icroLinux (Salva)> Well, the boot proccess failure was related to my usb hub connected to the usb 3.0 interface
<Armbian-Discord> <M​icroLinux (Salva)> That produce the loop, so, uboot bug I guess.
<Armbian-Discord> <M​icroLinux (Salva)> But yeah, 5.19 isn't working from the releases available at armbian T4 homepage
<Armbian-Discord> <M​icroLinux (Salva)> Also tried the manjaro inages for T4 and they also do not boot at all, but due to other problem it seems.
<Armbian-Discord> <M​icroLinux (Salva)> Not a great day for the T4
<Armbian-Discord> <I​gorPec> software has to be maintained in order to work ... i know this sounds boring and is cliche 🙂
<Armbian-Discord> <M​icroLinux (Salva)> absolutely
<Armbian-Discord> <M​icroLinux (Salva)> I will retest the efi image of balbes
<Armbian-Discord> <I​gorPec> balbes can't test those images anymore since his board died
<Armbian-Discord> <M​icroLinux (Salva)> Yes