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
[TheBug] has joined #armbian-rockchip
montjoie has joined #armbian-rockchip
<[TheBug]> BTW this is discord bridge, you can either check whitelogger for history or join Discord if you like
<montjoie> hello, I tried rk3588 armbian image on rock5b, when I change something in uboot, via saveenv, it said "saving to nowhere", not sure if you can do something about it
<montjoie> argh no ethernet in uboot:(
<Armbian-Discord> <T​onymac32> It's missing a lot of things. Have you tried the vendor image U-boot?
Tenkawa has joined #armbian-rockchip
<Tenkawa> montjoie: I have my rk3588 running the vendor u-boot and Armbian 22.08.0 and I have both ethernet and 802.11AC running right now
<Armbian-Discord> <M​anoftheSea> While u-boot is running?
<Armbian-Discord> <M​anoftheSea> I interpreted the complaint as that u-boot itself couldn't make use of the ethernet, not that the system launched by u-boot was lacking
<Tenkawa> How do I get in there quickly and I'll go test it
<Tenkawa> (hven't got in the u-boot cli in a long time)
<Tenkawa> traditional u-boot and I are not on good terms..
<Tenkawa> brb though... 10 min.. just got called away
<Armbian-Discord> <M​anoftheSea> I dunno. On my ebin, I'd try running the tftpboot scripts, but if they fail, I have no idea how to do any further debugging.
<Armbian-Discord> <T​enkawa> ah
<Tenkawa> Let me go reboot it and see what I have access to... brb
<Tenkawa> It jumps to the boot on the nvme way too fast to even do anything even if I had any way to stop it
<Tenkawa> I boot the emmc to nvme immediately
<Armbian-Discord> <T​enkawa> The main thing I'm at a disadvantage right now is trying to get away from 5.10.66... this is just too old and minimal of a kernel (even recompiled and tuned)
Orac has joined #armbian-rockchip
Tenkawa has quit [Ping timeout: 240 seconds]
_whitelogger has quit [Ping timeout: 240 seconds]