All Activity

Made some progress today. For debugging, I built my own image with the Edge kernel (6.18). However, this time, the board did not even boot up and there was also no signal on HDMI. The last idea I had was to downgrade the kernel using armbian-config. But since the Ethernet is not working, I was trying to setup WiFi because armbian-config was trying to load apt cache but without internet, I cannot load anything. After multiple reboots, I slowly cached the apt. Then the armbian-config loaded. I downgraded the kernel from 6.12.60 to 6.6.63 and then the Ethernet started working fine! ☺️ Current version: $ uname -a Linux rockpi.dev.com 6.6.63-current-rockchip64 #2 SMP PREEMPT Fri Nov 22 14:38:37 UTC 2024 aarch64 GNU/Linux $ lsb_release -a Distributor ID: Debian Description: Armbian_community 26.2.0-trunk.44 trixie Release: 13 Codename: trixie I am now confident that somewhere after Kernel 6.6, the Ethernet is broken in Rockpi 4B.

That's not really possible either. The only thing that is possible is using my kernel build in Armbian environment to see how it is performing for you. With my jumpstart image, this is actually quite easy to implement. For this, both root filesystems just need to be mounted and extlinux/prepare-jump-start ${target-rootfs-mount-point} needs to be executed in the jumpstart rootfs. If the target system is now being booted with firmware that uses mainline U-Boot as the payload, nothing stands in the way of booting with my kernel. And don't worry, prepare-jump-start only adds files to the target rootfs. Nothing will be overwritten or deleted. If you want to give it a whirl, speak up and I will upload a current image. But you will be disappointed, because the stock kernel only provides the functionalities available with the officially released kernel. Both Armbian and my kernel build have already applied patches that may appear in a future official release. I doubt that you will succeed, because even the fedora organization only does a full rebuild once per release cycle. There is no advantage in rebuilding a component unmodified that leads to the same result as the package already provided. It only makes sense to do this when branching off the release version in order to create a synchronized basis for further development. Only modified packages will be replaced or upgraded. My weekly upgrade gives me several gigabytes of new packages each time because I'm on Rawhide. Somehow, I can no longer manage to stick to any official release versions.

Maybe a handful, I have most SBC's equipped with one permanently. And needed for Arduinos etc, you can even power tiny old things like RPI0/1 with it (if you connect red wire to 5V pin as well). In the meantime, you might think about some previous U-Boot and previous kernel. For quite some SBCs, there is trouble when U-Boot is new/mainline/releasecandidate and kernel vendor. I am currently also doing some tests on my NanoPi-R6C (RK3588s) because HDMI is not initialized fast enough (by U-Boot). And with 6.1.115 vendor kernel really choppy mouse updates and green tint, not complete flat green luckily, I can still see icons and mouse.

Hey @Sergey Lepeshkin, thanks for the fast reply. I will check what you mentioned. I was thinking, could i modify the recovery.zip from the recovery partition so when it reflashes it gives the box "su" rights? that would be via software and no need to connect wires. If my idea is not possible, i will keep trying with the UART. Thanks for the advice.

Nothing is working and the device did not boot sun50i-h313-tanix-tx1.dtb sun50i-h313-x96q.dtb sun50i-h313-x96-q.dtb sun50i-h313-x96-q-lpddr3.dtb sun50i-h313-x96-q-v5.1.dtb

I managed to run Armbian, everything seems to work except the WiFi, which is module KM3306005. Any idea how to fix it?

I'll have to order a USB serial cable based on CH340. Give me a few days and I'll have those logs for you.

Thank you for the kind words.

I find this forum very interesting. There's a lot of useful information here.

https://docs.radxa.com/en/rock4/rock4c+/low-level-dev/serial and set loglevel to 7 in armbianEnv.txt

Hello fellow geeks/nerds, Here still using a Rock Pi 4c on 26.2.0-trunk.44. After upgrading to 26.2.0-trunk.62 the Rockpi just does not come back. No display no network. Wish I could provide more details beside the versions. I've went ahead and froze the kernel updates. If there's a way to maybe pull a log of sorts please let me know and I'll post it.

@Jerry Falken well this forum is more oriented on hardware and compiling stuffs rather than generic linux info that you can find every where on the net so I won't answer on this, google it You can remain also on old distros such as debian 9 stretch minimal without gui but with ssh support to run headless ngix apps. I don't think you need newer distros to run such easy apps , the important is improve a good firewall and also a fail2ban app to protect your system but, again, those are more generic linux questions rather than support on tvboxes socs

Thank you! Unfortunately, this didn't help. The device won't boot at all and immediately goes into MASKROM after rebooting. I just built Ubuntu 24.04.3 from here - https://github.com/markbirss/rk3506-ubuntu and it booted perfectly without any problems. I'm testing it now.

Have just tested Forky (Debian) release on both the 2A and the 2F, and in both cases the wireless driver survived an upgrade. I also tested the Plucky release on the 2A, and the wireless driver did not survive the stock upgrade. I have not tested the Plucky version on the 2F yet. Also it should be noted that the cron implementation in the Forky version for the 2A is fouled up. Any ordinary user's crontab has to be edited by root. Bad permissions on a number of files. Nice to know that at least the wireless adapter problem has attracted someone's interest.

Thanks! I think it will be a little bit of work, but I agree that it would be the best way forward. So I'll attempt to start again with a fresh install. Really appreciate your help!

So I have tried all the different images for the Opiz3 from the Orange pi website with the dts, I have tried 2 of the desktop images for the opiz3 from armbian. All of them result in the desktop environment not booting correctly. with Armbian I even got to the point where there are no errors in the lightdm logs, yet still a black screen. However with all those different images, a simple manual restart of lightdm (systemctl restart lightdm.service, will fix it and make the desktop show up.

If you have X11 installed, then boot with only the LCD and try: sudo systemctl stop lightdm (the greeter, which requires X11) sudo startx Show me what errors you see If you have Trixie, boot with only the LCD and: sudo apt install labwc labwc (as a regular user) Large language models are just google on steroids. They can only give good answers, if hundreds of people have typed and published solution similar to your problem.

Does this happen if you are running from an SD card also? Or is it specific to running off of emmc?

sun50iw9p1.dtsi

Extract the 7z file in the same folder as Armbian-unofficial_26.02.0-trunk_Luckfox-lyra-ultra-w_trixie_vendor_6.1.115_minimal.img Then do: dd if=uboot.img of=Armbian-unofficial_26.02.0-trunk_Luckfox-lyra-ultra-w_trixie_vendor_6.1.115_minimal.img bs=32k seek=1 conv=notrunc Then you have an old Rockchip 2017.09 u-boot, my guess it that that shall work with 6.1.115 But you are the first one, the tester of it. Also, I did a 32-bit rockchip edge kernel test build and I see no DTB file for Luckfox-lyra-ultra-w That means it is not supported for mainline. At least it seems correct that one cannot build a working image now as legacy u-boot is not available anymore. In theory, the 2025.10-rc4 u-boot might be such that you can get a mainlne edge rockchip kernel running, EFI booted maybe, but expect same strange errors or freezes.

At this point I've tried with and without adafruit,yx240qv29. I also have tried with X11 and Wayland. I am at the point where I am using Gemini to figure out what is wrong but not making much progress. I have found people with similar issues but no solutions.

I've already tried both sudo apt update && sudo apt upgrade. I can't update because it says that the website linked "apt.armbian,com bionic release" doesn't have a release file. What commands would i specifically need to run to do what you said (Blacklisting kernel, seguenti (?)) Server, something i can ssh into to run some basic websites on nginx

@Jerry Falken Unfortunately you must remain on kernel 4.4.xxx because as many times said newer kernels doesn t support NAND. About upgrading to newer distros, blacklist kernel update in apt and try doing seguential apt dist upgrades changing repository and starting by a well working distro I have up to Debian bookworm ( Debian 12 ) but only cli, no desktop May I ask what the purpose are you using for your tv box ?

Jeffrey, Is your DTS using this in the "compatible" line: adafruit,yx240qv29 ? Are you trying to use an X11 or Wayland greeter and desktop? (I can't remember what commands to use to check that right now). I didn't know about X11 problems with adafruit,yx240qv29 (only with the other driver panel-mipi-dbi) There's no available image to download with all the required parts.

Yes, that is the correct sequence of actions: 1. Build armbian minimal with panel-mipi-dbi kernel module 2. Use DTS so that the kernel links the GPIO, SPI to the panel-mipi-dbi kernel module 3. Use the bin file (originally provided by Kungfu pancake) <-mandatory, not optional 4. If you see console text successfully in the LCD during boot, you have successfully installed your LCD 5. Tell us here, for the next step in GUI installation The "greeter" is the graphical login screen. Labwc is the wayland-based compositor and window manager (I think).