<marex>
shyeline: there is about 50 different errors in that paste, which one of them ?
Leopold has quit [Ping timeout: 255 seconds]
Leopold has joined #u-boot
mncheck has quit [Ping timeout: 260 seconds]
mmu_man has quit [Ping timeout: 256 seconds]
Leopold has quit [Ping timeout: 255 seconds]
<shyeline>
Oh i haven't noticed any other than 8 of the "
<shyeline>
No FDT memory address configured"
<marex>
shyeline: oh that one ... is /boot/boot.scr content available somewhere too ?
<marex>
"Loading Environment from FAT... Unable to use mmc 0:1..." ... could it be that your SD/eMMC content is corrupted in some way ?
<marex>
"Failed to load '/boot/uImage'" same here ... is uImage on your boot media and is it even valid ?
<shyeline>
From the posts that I've read i think i have made the terrible mistake of updating the software via command. It was kinda slow so I did reboot command and the board since than won't start.
<marex>
well OK, is the board booting from SD card which you can remove and rewrite, or from eMMC ?
<shyeline>
I was running armbian jammy edge and ran apt upgrade. It is booting from sd card but i cannot rewrite it without somehow copying my pterodactyl panel data
Leopold has joined #u-boot
<marex>
shyeline: can you break into the u-boot shell ? (press space on boot a few times, you'll get a command prompt)
<marex>
then do some ... => mmc dev 0 ; mmc info ; ls mmc 0:1 ; ls mmc 0:1 /boot/ and let's see what's in there
<shyeline>
Mmc dev 0 with or without ;
<marex>
=> mmc dev 0 ; mmc info ; ls mmc 0:1 ; ls mmc 0:1 /boot/
<marex>
without the => , that's shell prompt prefix
<marex>
the ; behaves same as bourne shell, it runs the commands in sequence and ignores their return value
<shyeline>
do i pastebin or just paste the output
<marex>
pastebin please , or paste.debian.net which seems to be collecting less stuff on you
<shyeline>
when i was trying things on my own i checked the files listen in 'bash session' but the file naming system doesn't exist anymore but i found simmilar files
<shyeline>
all the names had something like 20.08.y but one was 20.10 and i think it is the one that fucked it up
<shyeline>
but i am sure your idea is better, do i paste all outputs?
<marex>
it is well possible the /boot contains some incompatible stuff, sure
<marex>
it's really up to you whether you want to debug this, or whether you want to just reinstall the system
<marex>
I suspect if you proceed through the boot script, you would be able to load the kernel image, ramdisk, fdt into memory and start the system by hand, and once in Linux, you can fix the /boot content with apt install or whatever
<shyeline>
well iam at line 11
<marex>
shyeline: proceed until line 46 as per above, that should be simple enough
<shyeline>
iam ignoring the comments like "# Print boot source" right?
<marex>
sure
<marex>
after the 'fdt resize', skip all the way to line 73 , then stop at line 76 and please share output
<shyeline>
line 24 Failed to load 'armbianEnv.txt'
<marex>
ah
<marex>
=> setenv prefix /boot/
<marex>
then re-run line 24
<marex>
works ?
<shyeline>
yup
<shyeline>
do i run 38
<shyeline>
line 38*
<marex>
yes
<marex>
=> if test "${devtype}" = "mmc"; then part uuid mmc 0:1 partuuid; fi
<marex>
the USB serial adapter is too fast and may overflow the receiving UART (on the orangepi) FIFO, so you would in fact get corrupted paste into the console
<marex>
there are now ways to partly mitigate that, there is a chance your board has that enabled, so ... you can try it and see what happens
<shyeline>
Well i was using putty so yeah it was kinda slow when i tried to type the commands u gave me, had to paste em. Gonna try tommorow if it brake while rebooting
<shyeline>
Hey really last question, can i kill a board while using u-boot?
<marex>
yes
<marex>
but I think that's not really the right question here
<marex>
basically U-Boot gives you full unlimited access to the hardware from software perspective
<marex>
you can write any register without any restrictions
<marex>
that includes something which may permanently damage the hardware
<marex>
I think what you want to ask is ... can you do some permanent damage to this particular board while using U-Boot without too much deliberate effort
<marex>
no
<shyeline>
Yeah that's a relief, thanks
<shyeline>
So if the board on any kernel newer than 5.4.y has wifi not working is it linux or uboot fixable?
<marex>
most likely linux issue, see if $ dmesg | grep -i firmware prints anything
<macromorgan>
anyone else have an issue with Arm Trusted Firmware for Rockchip after the binman changes? I can see it in my fit but it didn't get called.