All Activity

@usual user@Efe Çetin it seem to work with i burned an sd card with the new compiled Armbian-unofficial_24.8.0-trunk_Orangepi5-plus_bookworm_legacy.5.10.160 image . I boot from the sdcard It seems to work as i have no crash copying a 250GB file between a usb ssd and the mvne. I'm trying now memtester 31G. ... ... trying mlock ...Killed BUT not crash trying memtester 30G is working ... ... and it does not crash. @Efe Çetin Is it possible to make the official release working for the 32Gb version ?

Since a board with 16G RAM practically has a little less than 16 GiB RAM, probably mem=16G limits it a little too less to prevent the crash 100% reliably, while mem=15G would do. I don't know how exactly those limits are applied, and at which point exactly the power usage of the RAM raises above the critical point (in case really this is the reason for the crashes), so this is just a guess which can be tested.

Yes. Added it to other arguments, like this: extraargs=fsck.mode=force fsck.repair=yes mem=16G free -h shows 16G after this.

@Eddie as @MichaIng explain me did you add the next in the armbienEnv.txt ?

I can add that Orange Pi Zero 3 users have similar problems, i.e. after turning on the power or, for example, after reboot. This is not a cyclical phenomenon. So when it happens that you need to reboot remotely, it may turn out that Orange Pi Zero 3 requires physical intervention by turning the power on and off.

https://debug.armbian.de

https://debug.armbian.de

Hi, New builds (hosted by armbian AND self compiled) of armbian do not post / boot at all. Completely black screen on hdmi outpout. Ethernet link lights do not light up. It's like there is no bootable media inserted (it definitely is). I have tried many combinations of different kernels and ubuntu versions. None work. Board: nanopc t6 8gb ram They used to work, and archived copies from november 2023 work, booting perfectly. I also compiled one back then which also worked. But now this is not working any more. Does anyone have idea why it no longer posts? Thanks Luke

Hi, I do not konow, it this is the right place to raise the this ticket. But in stable releases of Armbian it works fine, but there is no video acceleration. I have tried Kodi on Armbian Noble Gnome + trunk MESA/VPU: Armbian_24.8.0-trunk.85_Rock-5b_noble_vendor_6.1.43_gnome-oibaf_desktop.img Kodi falling when I'm trying to install some of extensions. For example https://repo.sc2.zone/ Crash log in the attachment. System log: 2024-06-05T12:01:28.534687+02:00 rock-5b kodi.desktop[3739]: Fatal Python error: PyImport_AppendInittab: PyImport_AppendInittab() may not be called after Py_Initialize() 2024-06-05T12:01:28.535024+02:00 rock-5b kodi.desktop[3739]: Python runtime state: initialized 2024-06-05T12:01:28.535112+02:00 rock-5b kodi.desktop[3739]: Thread 0x0000ffff3afde0c0 (most recent call first): 2024-06-05T12:01:28.535191+02:00 rock-5b kodi.desktop[3739]: <no Python frame> 2024-06-05T12:01:28.612980+02:00 rock-5b kodi.desktop[3732]: Aborted 2024-06-05T12:01:28.640388+02:00 rock-5b kodi.desktop[3732]: Crash report available at /home/tomogo/kodi_crashlog-20240605_120128.log kodi_crashlog-20240605_115433.log

Hello @ALIGMSTEN, I want to use UART5, which is located on the TX-PH2 and RX-PH3 pins. As far as I understand, this UART is initially disabled. To enable it, I tried using the command armbian-config -> System -> Hardware, but I couldn't do it because nothing was displayed in the graphical interface (as shown in the screenshot above). After doing some research, I started experimenting with the /boot/armbianEnv.txt file. I added the line overlay_prefix=sun50i-h616. After rebooting the board, I tried using armbian-config -> System -> Hardware again, and now the interface displays the hardware peripherals along with the UART5 that I need. By enabling it, I can receive data through the TX-PH2 and RX-PH3 pins via /dev/ttyS1. So, I have essentially solved my problem, but I still have a few questions: Is there a simpler or recommended way to enable UART5 on this board without manually editing the /boot/armbianEnv.txt file? Are there any potential issues or pitfalls I should be aware of when using this method? Is it a bug that the interface in armbian-config -> System -> Hardware did not display initially on various versions of the system? Thank you.

Hi, I've installed Armbian_24.5.1_Rock-5b_bookworm_vendor_6.1.43_cinnamon_desktop.img on my Rock 5b and when I have tried to do apt update get error message with armbian.com url. (timeout error) I did all necessary and now it work fine. But for dev info, there is some problem probably with all Stable images.

Many thanks to all those who helped me launch the TV-box, I am very grateful to these people who help out newcomers with their advice. Thanks jock, I deleted brltty using the command: and oh, a miracle the board worked, the connection to the printer took place!

Hi, I have tried Rock 5b images with Kernel 6.8.10. Any of image I've tested will not start. No LED flashing, no HDMI signal.. nothing. The others with Kernel 6.1.43 starts fine.

Hello @Dmytro Lazor UART is enabled by default, you can use a usb to ttl converter at a baud rate 115200 to connect to a serial consel. Please be more specific what you are trying to achieve?

No matter which DTB I use, HDMI doesn't respond. What's going on？

Hello! Can't say if a step is missing, normally an sdcard with multitool on it is sufficient to let it boot from sdcard. I don't know if you have an ancient version installed without the sdcard boot or a very new installation with the missing feature in u-boot. You may take a look to this:

Then compile it by yourself?

I have armbian-firmware-full installed. By the way, the config you mentioned in github is linux-rk35xx-legacy(kernel 5.10), not the linux-rk35xx-vendor(kernel 6.1) used in Armbian 24.5.1 Stable. This topic has also mentioned about the lost rtl8852be driver: No WiFi on latest image - Orange Pi 5 Plus - Armbian Community Forums Thanks!

Odd. It is enabled in config:https://github.com/armbian/build/blob/aa2d4696cac76148d01977f63cc831e492c0f7a2/config/kernel/linux-rk35xx-legacy.config#L2945 Have you installed armbian-firmware-full? Maybe just the firmware is missing.

Do you have a TV with hdmi port? Maybe these links can help. https://forums.raspberrypi.com/viewtopic.php?t=353936&start=50 https://forums.raspberrypi.com/viewtopic.php?t=24679&start=225

Sorry, I haven't got time to tinker with it. I'm staying with vendor kernel and trying to get nextcloud running, so 6.8 is not a priority for me now. I don't think it's possible to just add this overlay at boot time. I wanted to recompile the kernel with modified dts and then include this overlay. Why I think it's necessery is because of the __symbols__ node in decompiled versions of dtb's. 6.1 dp0_in_vp1 = "/dp@fde50000/ports/port@0/endpoint@1"; dp0_in_vp2 = "/dp@fde50000/ports/port@0/endpoint@2"; dp0_out = "/dp@fde50000/ports/port@1/endpoint"; hdcp1 = "/hdcp@fde70000"; hdmi0 = "/hdmi@fde80000"; hdmi0_in = "/hdmi@fde80000/ports/port@0"; hdmi0_in_vp0 = "/hdmi@fde80000/ports/port@0/endpoint@0"; hdmi0_in_vp1 = "/hdmi@fde80000/ports/port@0/endpoint@1"; hdmi0_in_vp2 = "/hdmi@fde80000/ports/port@0/endpoint@2"; edp0 = "/edp@fdec0000"; edp0_in_vp0 = "/edp@fdec0000/ports/port@0/endpoint@0"; edp0_in_vp1 = "/edp@fdec0000/ports/port@0/endpoint@1"; edp0_in_vp2 = "/edp@fdec0000/ports/port@0/endpoint@2"; dp1 = "/dp@fde60000"; dp1_in_vp0 = "/dp@fde60000/ports/port@0/endpoint@0"; dp1_in_vp1 = "/dp@fde60000/ports/port@0/endpoint@1"; dp1_in_vp2 = "/dp@fde60000/ports/port@0/endpoint@2"; dp1_out = "/dp@fde60000/ports/port@1/endpoint"; hdmi1 = "/hdmi@fdea0000"; hdmi1_in = "/hdmi@fdea0000/ports/port@0"; hdmi1_in_vp0 = "/hdmi@fdea0000/ports/port@0/endpoint@0"; hdmi1_in_vp1 = "/hdmi@fdea0000/ports/port@0/endpoint@1"; hdmi1_in_vp2 = "/hdmi@fdea0000/ports/port@0/endpoint@2"; edp1 = "/edp@fded0000"; edp1_in_vp0 = "/edp@fded0000/ports/port@0/endpoint@0"; edp1_in_vp1 = "/edp@fded0000/ports/port@0/endpoint@1"; edp1_in_vp2 = "/edp@fded0000/ports/port@0/endpoint@2"; 6.8 sys_grf = "/syscon@fd58c000"; hdptxphy0_grf = "/syscon@fd5e0000"; hdmi0 = "/hdmi@fde80000"; hdmi0_in = "/hdmi@fde80000/ports/port@0"; hdmi0_in_vp0 = "/hdmi@fde80000/ports/port@0/endpoint"; hdmi0_out = "/hdmi@fde80000/ports/port@1"; hdmi0_out_con = "/hdmi@fde80000/ports/port@1/endpoint"; vop_grf = "/syscon@fd5a4000"; vo0_grf = "/syscon@fd5a6000"; vo1_grf = "/syscon@fd5a8000"; usb_grf = "/syscon@fd5ac000"; And overlay patches __fixups__ { hdmi0_in_vp0 = "/fragment@0:target:0"; hdmi0_in_vp1 = "/fragment@1:target:0"; hdmi1_in_vp0 = "/fragment@2:target:0"; hdmi1_in_vp1 = "/fragment@3:target:0"; }; 6.8 does not even have hdm1* nodes, so we either need to somehow change the overlay or modify dts and rebuild kernel

Unfortunately, "sudo modprobe rtw89" didn't work. It returned this with error: "modprobe: FATAL: Module rtw89 not found in directory /lib/modules/6.1.43-vendor-rk35xx" I think it may be lost 8852BE kernel module? In directory /lib/modules/6.1.43-vendor-rk35xx/kernel/drivers/net/wireless/realtek/rtw89, I find "rtw89_8852c.ko", "rtw89_8852ae.ko", "rtw89_8852ce.ko", just without "rtw89_8852be.ko".

Checking that note reveals: Note: at the current status, helios64 board patches have been disabled because the base device tree does not apply on kernel 6.9. So helios64 is cancelled as of linux 6.9.x until someone takes care of the issue. Thank you very much.

Perhaps this helps:

Crashed.