aosos Posted June 24 Share Posted June 24 I tried installing the OS using SD card and EMMC, but both failed. Orange Pi OS (Arch) on the official website ran normally. However, I installed focal_desktop_xfce or jammy_desktop_gnome from Ubuntu Image, but they all failed. After inserting the image into the SD card, the symptom is a black screen and no booting. Does it only support SSD? Because it is entered through a translator, there may be unnatural sentences. If you reply about that, I will get back to you. 0 Quote Link to comment Share on other sites More sharing options...
Solution Igor Posted June 24 Solution Share Posted June 24 1 hour ago, aosos said: Orange Pi OS (Arch) on the official website ran normally. Orangepi OS (Arch) is custom / re-branded Manjaro and Manjaro is not doing much else then shipping (selling) their Arch derived OS while taking our and community work on kernel maintainace. This is the story how Orangepi "supports" open source - by primarily supporting code dealers that already mainly have negative contribution to open source development. But who cares other then small group of people called "developers"? In general, HW vendors have interest to block or at least control other OS providers and it is possible they purposefully compiled SPI boot-loader to not load anything else then their OS. This would explain why you can't load our OS. Manjaro already provided (or tried to) this "solution" to Pine64, so average users would have troubles changing OS. Details: https://blog.brixit.nl/why-i-left-pine64/ For us, this is easy to work-around, but bulk of people might still need to stick to their official promo/spy/pirate-ware. Solution? Debian based OS: sudo apt update sudo apt install mtd-utils sudo flash_eraseall /dev/mtd0 Arch based OS: sudo pacman -Syy sudo pacman -S mtd-utils sudo flash_erase /dev/mtd0 Then boot armbian from SD card and run: sudo armbian-install And choose "update MTD boot-loader" or "Install it to NVME", which will also update boot-loader and transfer image to SSD. Tested right now with Opi5 lying on my desk. 2 Quote Link to comment Share on other sites More sharing options...
Trinom Posted September 2 Share Posted September 2 I just tried the suggested steps on my new Orange Pi 5 Max (the newest board with RK3588) and unfortunatelly, it doesn't work. I followed every single step (using Debian), erased mtd0, but the Raspbian never booted when I swapped the SD cards. Indicator has solid cyan color (the same color as if no card is present). Apparently it's looking for something extra on the SD card, which it can't find, so it doesn't boot at all. 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted September 3 Share Posted September 3 9 hours ago, Trinom said: Raspbian I doubt that Raspian supports this board. 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted September 3 Share Posted September 3 9 hours ago, Trinom said: Orange Pi 5 Max For all those boards you need a dedicated image in order to boot it. This is not a PC or Raspberry Pi. If image is not here https://www.armbian.com/download/?device_support=Standard support&tx_maker=xunlong you will need to stick to terrible OS provided by Orangepi until someone will adopt this hardware https://docs.armbian.com/Developer-Guide_Adding-Board-Family/ 0 Quote Link to comment Share on other sites More sharing options...
Trinom Posted September 5 Share Posted September 5 Technically, 5Max is a combination of 5Plus and 5B (RK3588 CPU and 5B peripherals). So if 5B and 5Plus is supported, 5Max should be supported as well, right? Or do they do something stupid with a bootloader? I don't think so, as their images work between different 5-series boards just fine. I will probably further investigate their SW tools they provide for burning the image onto SD/EMMC/SSD. 0 Quote Link to comment Share on other sites More sharing options...
SteeMan Posted September 5 Share Posted September 5 2 hours ago, Trinom said: So if 5B and 5Plus is supported, 5Max should be supported as well, right? Not right at all. Every SBC that has different hardware configuration requires a different dtb file that describes the hardware to the Linux kernel. So every SBC needs it's own build ( sometimes dtb overlays can be used to shortcut this). And similar issues can exist at the uboot level too. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.