Tony3

I feel stupid now. I think the SD card was not inserted properly! (when there is no SD card, you see an "Orange PI screen")

I received my new orange pi 5 plus. I installed the official Orange PI 5 Plus Ubuntu on a SD card and it worked great. Then I installed the "Armbian_23.8.1_Orangepi5-plus_jammy_legacy_5.10.160_gnome_desktop" on SD card (Yes I took the image from the page with the "archive for orange Pi 5 plus"), and it get stuck on a screen displaying "Orange PI" (I do not see any armbian logo) , and nothing else happens (the blue light on the board does not blink). Why is that? How can I see what is happening? I installed in the past Armbian on an Orange Pi 5 with no issue, so I am really wondering what is going on there. Your view/ideas will be appreciated, thanks in advance,

I will receive soon a Orange Pi 5 Plus. I have setup completely an Orange PI5 with Armbian. I had to recompile kernel, compile drivers ...... it took some time. If I run the Orange PI5 plus with the same SD card as the Orange Pi 5, would it work? If not, is there an easy thing to do to make it work? I think there is a device tree file hardware specific , but is it read when compiling the kernel or dynamically? I am asking because processors are very similar, and it would make my life easier! Your view will be appreciated. Thanks.

Ok, good then

Just wondering, does the GPU acceleration works?

And if not in kernel, simply compile one as a module

I extracted a wifi module from an old skybox that I found in the street on the pavement, compiled the ath6 driver, and it works great! (ok not really out of the box......only out of a sky box!)

May I know why using suspend? It creates so many issues when you have devices attached.......better to boot!

yes of course, update /etc/fstab, now working, thanks Royk. To Tom1238732, I did the copy with dd, but not for the whole disk, only the partitions /boot and /

I thought it would be easy, but I am now turning in circles, so I am asking here. I have a working system booting on NVME (when no SD card inserted), with two partitions nvme0p1 (256Mb) and nvmeop2 (40Gb) I would like to clone my working system on a SD card. How shall I proceed? I am not asking details instruction, only the rough path I should follow (e.g. dd partitions, tune2fs ......). PS: I thought it would be easy, but whatever I do, the system keep taking /boot on the nvmeop1, so I really struggle to boot on the /boot of the SD card

How can I check the version of the firmware for Orange my Pi5? How can I see the latest version available firmware? How to update firmware? Is it risky to update it? Four firmware related questions!!!

Cover it with a piece of plastic? Lol

By the way you can also compile on the pi 5, this is what I did.

You have to install python to be able to compile. See error message above

This seems to have fixed my issue. sudo apt update sudo apt dist-upgrade sudo apt install mali-g610-firmware rockchip-multimedia-config Strange because the ppa's were pin.

I have setup the hardware acceleration as explained in the posts, but within Kodi, every now and then I can see the image with "pixelising", and looking in the syslog when this just happened, I can read: Feb 15 16:54:17 orangepi5 kernel: [ 1267.908544] mpp_rkvdec2 fdc48100.rkvdec-core: reset done Feb 15 16:54:17 orangepi5 kernel: [ 1267.908549] mpp_rkvdec2 fdc38100.rkvdec-core: resetting... Feb 15 16:54:17 orangepi5 kernel: [ 1267.908670] mpp_rkvdec2 fdc38100.rkvdec-core: reset done Feb 15 16:54:17 orangepi5 kernel: [ 1268.316705] mpp_rkvdec2 fdc48100.rkvdec-core: resetting... Feb 15 16:54:17 orangepi5 kernel: [ 1268.316855] mpp_rkvdec2 fdc48100.rkvdec-core: reset done Feb 15 16:54:17 orangepi5 kernel: [ 1268.316860] mpp_rkvdec2 fdc38100.rkvdec-core: resetting... Feb 15 16:54:17 orangepi5 kernel: [ 1268.316930] mpp_rkvdec2 fdc38100.rkvdec-core: reset done Any idea what could be wrong? Thanks.

Only sharing what I managed to make working on the Orange Pi5: a Tvheadend server with satellite cards TBS 5527 and TBS 5520se. The rough path I followed: - recompiled the kernel in order to have "Linux tv" as a module (CCONFIG_DVB_CORE=m). This will be replaced by the tbs driver in next steps. - installed TVheadend from the armbian-config - compiled tbs drivers by following standards instructions....but: - had to add a CFGLAGS += -w to avoid some warning stopping the build (Makefile in the v4l directory) - had to disable the creation of the mc.ko (MEDIA_CONTROL) to avoid conflict with kernel built-in module (not sure why, but trying to rebuild the kernel with "Media support" as a module was causing some compilation errors dealing with a samsung chip in the RK5588s). That is it, hope it will helps the ones wondering like myself whether it would work or not.

yes saw it. You have to pin the drivers so that they do not get overwritten by the upgrade (there is a post on site on how to do that)

You have to wipe all partitions of the spi memory, reinstall the boot loader on the spi with orangepiconfig

I successfully installed the new kernel and now Rebuild my wireless atheros module Thanks a lot for helping on that one.

Have you created the NVME image from this SD card? If yes, NVME and SD have the same UUID and this creates some confusion during the boot. I suggest you create a blank new SD card from the Orange web site, to get another UUID.

Indeed it was a problem with the 8852bu.c, but not only, to compile successfully I had to deselect all the realtek wifi drivers, in particular the rtl8188eu. I finally got my kernel generated...yeaahhhhh! However, I can see the generated files in the output/debs directory, but not sure what to do with them? I only want to install my new kernel, not u-boot, not the full image, how shall I proceed? I read lots of things on the net: run armbian-pdate run dpkg -i *.debs run dpkg -i newkernel.deb ...... How shall I proceed? How will the modules be updated? With the dpkg -i and only one deb file? I have not found the official documentation from armbian.doc about what to do after the build finished, did I miss something? Thanks again.

I am trying to compile the Kernel on my PC with the Ubuntu recommended version. I get the error below: arch/arm/dts/rk3128-evb.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /syscon@20008000/usb2-phy@17c arch/arm/dts/rk3128-evb.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /syscon@20008000/usb2-phy@17c FATAL ERROR: Couldn't open "./u-boot.dtb": No such file or directory ./tools/mkimage: Can't read u-boot.itb.tmp: Invalid argument make: *** [Makefile:1053: u-boot.itb] Error 255 Any idea what this could be? It is the first time I am running ./.compile.sh potential-paths.log Thank you. == u-boot make orangepi_5_defconfig == arch/../configs/orangepi_5_defconfig:245:warning: override: reassigning to symbol CMD_SETEXPR == u-boot make BL31=/home/eric/installed/build/cache/sources/rkbin-tools/rk35/rk3588_bl31_v1.28.elf tpl/u-boot-tpl.bin spl/u-boot-spl.bin u-boot.itb BL31=/home/eric/installed/build/cache/sources/rkbin-tools/rk35/rk3588_bl31_v1.28.elf spl/u-boot-spl.bin u-boot.dtb u-boot.itb == .config:1667:warning: override: reassigning to symbol BOOTDELAY tools/rockchip/boot_merger.c: In function ‘mergeBoot’: tools/rockchip/boot_merger.c:700:43: warning: ‘%s’ directive output may be truncated writing up to 813 bytes into a region of size 5 [-Wformat-truncation=] 700 | snprintf(buffer, sizeof(buffer), "%s", chip); | ^~ ...... 742 | chipType = convertChipType(chip + 2); | ~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /usr/include/stdio.h:894, from ././include/compiler.h:25, from <command-line>: /usr/include/x86_64-linux-gnu/bits/stdio2.h:71:10: note: ‘__builtin_snprintf’ output between 1 and 814 bytes into a destination of size 5 71 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 72 | __glibc_objsize (__s), __fmt, | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 73 | __va_arg_pack ()); | ~~~~~~~~~~~~~~~~~ tools/rockchip/boot_merger.c: In function ‘main’: tools/rockchip/boot_merger.c:895:18: warning: array subscript 20 is outside array bounds of ‘char[20]’ [-Warray-bounds] 895 | str[len] = 0; | ~~~~~~~~~^~~ tools/rockchip/boot_merger.c:933:14: note: while referencing ‘name’ 933 | char name[MAX_NAME_LEN]; | ^~~~ tools/rockchip/bmp2gray16.c: In function ‘usage’: tools/rockchip/bmp2gray16.c:121:25: warning: ‘%s’ directive argument is not a nul-terminated string [-Wformat-overflow=] 121 | printf("Version %s (zwp@rock-chips.com)\n", version); | ^~ ~~~~~~~ tools/rockchip/bmp2gray16.c:109:19: note: referenced argument declared here 109 | static const char version[4] = "1.00"; | ^~~~~~~ arch/arm/dts/rk3126-evb.dtb: Warning (reg_format): "reg" property in /syscon@20008000/usb2-phy@17c has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) arch/arm/dts/rk3126-evb.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /syscon@20008000/usb2-phy@17c arch/arm/dts/rk3126-evb.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /syscon@20008000/usb2-phy@17c arch/arm/dts/rk3128-evb.dtb: Warning (reg_format): "reg" property in /syscon@20008000/usb2-phy@17c has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) arch/arm/dts/rk3128-evb.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /syscon@20008000/usb2-phy@17c arch/arm/dts/rk3128-evb.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /syscon@20008000/usb2-phy@17c FATAL ERROR: Couldn't open "./u-boot.dtb": No such file or directory ./tools/mkimage: Can't read u-boot.itb.tmp: Invalid argument make: *** [Makefile:1053: u-boot.itb] Error 255 make: *** Waiting for unfinished jobs....

I keep getting this error LD [M] drivers/net/wireless/rockchip_wlan/rtl8852bu/8852bu.o scripts/extract-cert.c: In function ‘display_openssl_errors’: scripts/extract-cert.c:46:9: warning: ‘ERR_get_error_line’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 46 | while ((e = ERR_get_error_line(&file, &line))) { IS there a way to disable the warning becoming errors? I tried CONFIG_WERROR=no but it has no effect.

I am trying to build the kernel with the standards scripts, but directly on my orange pi 5. The build is stopping at some point because of a Warning issued by the compiler (this is the default behaviour for the compiler who does not tolerate any warning by default). (Some functions in the C code are depreciated, thus a warning is issue) How can I set the CFLAGS so that the kernel build takes it into account during compilation? Thanks.