Truenox

@ValdikSS I believe @brentr updated the image with u-boot updated to the latest version: https://www.armbian.com/rockpi-s/ (v24.11.4 with kernel 6.12.11) If you download older versions, they will come with the old u-boot and you will have to flash it manually as brent recommended. (because the u-boot not update with other way... i think...) Regarding what you say about consumption, I haven't investigated it, but you can configure your options with alsamixer for example, enabling what interests you. (For example, VRef BIAS), Audio Always-On Enable is not present on this board, or at least I am not aware of it. At the moment I'm still working on my updated image, with kernel 6.12 and the audio working perfectly.

Hello @brentr, Indeed, it was the outdated U-boot. I have followed your steps exactly as you say and it now boots perfectly with u-boot v2024.04, this time it does not give an error in the Device Tree and loads everything correctly. Armbian 24.11.3 image running with Kernel 6.12.9 with the audio perfectly available and working too, just what I wanted. (I was even able to recover my old image with all the relevant settings too, amazing) 🤯 They should release an updated image with this version of U-Boot so that it does not happen again and be aware of this, apart from the fact that it makes the installation easier for more novice people who may be lost and not have as much control and mastery of the system or at least, have a tutorial on the matter. These have been intense days, but fruitful with this help, thank you very much to everyone. If I have any other problem again I will report the bugs and comment on this forum. Thanks for all. 🙏 Best Regards.

@brentr But then you are saying that my USB serial is not working properly? I copied exactly the entire serial console log after applying the reboot of the rock pi s, and it wasn't just one time that I got the same results, I've been doing tests all day.

Everything is exactly as described, without any apparent modifications and flashed directly to the SD with the . img from the official website as I mentioned. The Rock Pi S is brand new, unless it has been damaged for some unknown reason, that shouldn't be the problem, it was working perfectly before doing the apt upgrade. The USB serial is a FTDI FT232RL with TTL 3.3v or 5v control, in this case I think I set it to 3.3v (if not, the Rock Pi S could burn), only Tx/Rx and GND as stated on the Radxa website. I tried to connect an RS232 previously, but without connecting power, only Tx/Rx and GND as stated on the Radxa website. https://wiki.radxa.com/RockpiS/dev/serial-console As I said, I am completely unaware of why the apt upgrade does not apply correctly... (Paranormal events here.) Any suggestions on what this could be or what I could do? Thanks.

Hi @brentr, I got a serial USB today to provide more information on this. I've been testing, doing exactly the same steps as you, and I still can't get the Rock Pi S to boot after rebooting, but I think the serial console info is pretty good. I'll paste the console information for you: After reboot, serial console: It has come to my attention that my version of U-Boot is more outdated than yours, I don't know if I have to update this manually or what... but I have been unable to find this information. On the other hand, it seems that it fails to detect the Device Tree... Any understanding of what else could be going on is beyond me. I hope you can help me with all this. Thanks again.

As a revealing fact, the packages that it updates are the following: The following NEW packages will be installed: libtext-iconv-perl The following packages will be upgraded: armbian-config armbian-firmware base-files bsdextrautils bsdutils fdisk libblkid1 libfdisk1 libglib2.0-0 libmount1 libpam-systemd libpython3.11-minimal libpython3.11-stdlib libsmartcols1 libsystemd-shared libsystemd0 libudev1 libuuid1 linux-dtb-current-rockchip64 linux-image-current-rockchip64 mount openssh-client openssh-server openssh-sftp-server python3-pkg-resources python3.11 python3.11-minimal rsync systemd systemd-resolved systemd-sysv systemd-timesyncd tzdata ucf udev util-linux util-linux-extra 37 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.

Hello @brentr, Exactly, the steps are as follows: 1. Flash https://dl.armbian.com/rockpi-s/Noble_current_server or https://dl.armbian.com/rockpi-s/Bookworm_current_minimal (Fails in both) to an SDcard. 2. Then, run 3. apt update 4. apt upgrade 5. and, subsequent reboot will fail. My board is v1.3 with the rockchip RK3308B (Recently purchased). What I told you about Kernel 6.6.63 is all written in this forum post: You mentioned a kernel fix for audio since if you install kernel 6.6.62 it does not detect any audio card. Thanks.

Hello brentr, I downloaded the image from the official website, right from Rock Pi S: https://www.armbian.com/rockpi-s/ Initially and in the most stable version possible I had the noble server CLI version installed, but as it failed and I couldn't get it to boot again, I performed clean installations of both systems, both Debian Bookworm and Ubuntu Noble and in both cases the same failure occurs, after performing an apt upgrade from a clean installation and executing a reboot, it bricks and doesn't boot. From the desperation of these days... I even tried Trixie and Oracular thinking that a more recent version could solve the problem, and directly these images don't work, they didn't boot either. Thinking it might be a problem with the recent u-boot tool updates, I repeated this whole process, installing it on the eMMC, with the same result. The feeling is that some base package has been touched, corrupting the installation. I'd like to provide the logs for further help, but as I mentioned, I don't have a TTL serial cable handy to debug, so I'll have to have one. So I found myself in a loop with no way out, so I appreciate the quick response to solve this problem. Thanks.

Hi everyone, I've been working with Armbian for a while on my Rock Pi S, I got to a stable situation on version 24.11.1 with kernel 6.6.63 where everything worked perfectly... but recently this last week I applied an apt upgrade, which applied strong base modifications (linux-current-rockchip64 and dtbo going from 24.11.1 to 24.11.3), after applying this update and rebooting, I can't get it to boot again, either from the Micro SD or from the eMMC installation. I wanted to report this bug, but I don't have a TTL cable at hand to be able to do the corresponding debugging... I've tried to flash older versions, or even flash the 24.11.1 version again but I need the audio fix for kernel 6.6.63, which doesn't apply after the last upgrade coincidentally. For work reasons I need to get this SBC up and running... Any solution for this? Thanks for all.