All Activity

The defconfigs are also just one piece of the problem here. There are patches getting applied to Sunxi for the Rockchip platform, why? Patches for the Pinephone, why? Last I checked that's not supported in either standard or community. Allwinner on Armbian has also been plagued with Bluetooth issues for years. I would venture to guess this is related to unchecked and unverified patching along with a defconfig that looks like a 5 year old went through and just ticked everything on. You tell me. Who wants to deal with this? Who wants to help fix it? and whom would want to do any work in this muddled up environment.

Could do that. Or you could do a PR and turn back on what is now missing from the defconfiigs that is required for your use case. Probably more productive than endlessly complaining. Nothing got intentionally disabled or turned off. They are two new defconfigs that are getting re-worked so everyone with in the community can profit. Not just the OPi crew.

The commit 2a38243de9ff01e079b6ec0c930c00f892e163aa brought lots of unnecessary config changes, DISABLED hundreds lines and at least made owserver failed. You say you just want pwserq and bluetooth work , why did you modified so many TCP/IP network config? Maybe we should rollback to commit d502356d0271f0d5748b67e4b4d998b51e588c6a (tag: v25.8.0-trunk.293) and remove all patches from pyavitz@gmail.com, It is so terriable.

Has anybody had success with Armbian Trixie? I repeated the steps I did for Bookworm, to have HW accelerated H264 1080p in XFCE, X11, with Linux 6.15.4... and I get "Unsupported hwdec: drm" in Trixie: ffmpeg 7.1.1, mpv 0.4.0 mpv log in trixie (with double verbose): For reference, mpv log in Bookworm: I inspected ffmpeg build configuration, and I see that ffmpeg 7.1.1 doesn't have "--enable-libv4l2", while ffmpeg 5.1.6 has that option. I checked with "ffmpeg -codecs|grep h264" In bookworm: In trixie Although, here the ffmpeg manual reads that this is option is only for webcams and videocapture https://www.ffmpeg.org/ffmpeg-devices.html#video4linux2_002c-v4l2

Thanks for your answer 🙂 And Sorry for my Stupidness .... and stupid questions in advance 🙂 with "firmware" you mean the "uboot - loader" mainly right ? at least It should be part of it ? The one I'm used is from the Armbian 25.5.1 image, thats what im copied with the arm-install to the /dev/mtdblock0 So I need a new uboot version for the orange pi 5 (that the chip gets configured properly) with support for my boot device I think this uboot version is lacking at least on nvme support, right ? Usually my plan was not to boot from nvme, but from the extra emmc .... but this had the same result. I have red somewhere that the actual released git branch of uboot has support for the orange pi 5 plus so building a uboot from git would help here ?

OK, PPS has back. good job. But another issue: the 1-Wire device maybe broken , Python3 package w1thermsensor works, but owserver failed . w1thermsensor all Got temperatures of 2 sensors: Sensor 1 (0000051a7f7c) measured temperature: 32.44 celsius Sensor 2 (04146945e5ff) measured temperature: 33.06 celsius owserver: journalctl -xeu owserver 7月 22 14:05:24 opip3 systemd[1]: owserver.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit owserver.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. 7月 22 14:05:24 opip3 systemd[1]: owserver.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit owserver.service has entered the 'failed' state with result 'exit-code'. 7月 22 14:05:25 opip3 systemd[1]: Failed to start owserver.service - Backend server for 1-wire control. ░░ Subject: owserver.service 单元已失败 ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ owserver.service 单元已失败。 ░░ ░░ 结果为“failed”。 7月 22 14:05:25 opip3 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5. ░░ Subject: Automatic restarting of a unit has been scheduled ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ Automatic restarting of the unit owserver.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. 7月 22 14:05:25 opip3 systemd[1]: owserver.service: Start request repeated too quickly. 7月 22 14:05:25 opip3 systemd[1]: owserver.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit owserver.service has entered the 'failed' state with result 'exit-code'. 7月 22 14:05:25 opip3 systemd[1]: Failed to start owserver.service - Backend server for 1-wire control. ░░ Subject: owserver.service 单元已失败 ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ owserver.service 单元已失败。 ░░ ░░ 结果为“failed”。

I have an old oDroid M1 that used to have Ubuntu 20 LTS installed on, but after it bricked itself during the install of Ubuntu 22 LTS, I decided to go looking for an alternative OS (it was also really sluggish). I got pointed to Armbian, and since it officially supports the M1, I gave it a go. Unfortunately, the instructions leave much to be desired. This part just doesn't seem to actually work: > Once booted, use armbian-install to write u-boot to MTD (SPI flash). This completely and irrevocably removes Petitboot, replacing it with mainline u-boot. All of the options that appear to be what it means by "write u-boot to MTD (SPI Flash)" don't seem to actually do that, as every time I try, rebooting the oDroid just leads back to this Petiboot screen: I can't seem to do anything from there, and it seems to be the old bootloader that the installation instructions said would be "irrevocably removed", but apparently isn't. I can boot into Armbian if I hold the RCY button while booting up the oDroid, but I believe that's booting in the Armbian that's installed on my SD card (I did the initial setup once). I want to install the system onto the oDroid's storage directly (the eMMC, I think?), so I don't have to hold that button every time I boot. I'm no linux expert (I use PC at home and a Mac at work), so I'm completely at a loss, here. Any help would be greatly appreciated. Here's the options I'm given from armbian-install. I've tried 2, 5, and 6, and none have worked. I don't have a SATA, USB, or NVMe to try the other options with.

Hello! I installed the latest Gnome Noble image from the very top of the Orange Pi 5 page, it has Wayland and generally is working really well - it even is doing higher refresh rate for my monitor and is smooth! HOWEVER the one big thing I noticed right away - my screen never turns off anymore And my Power options are missing such settings? It only gives the option to blank, which still is running my monitor at 100% brightness and a horrible solution Where is the setting to turn my screen off after 5 minutes? NOT blank, but into standby mode Worked on the previous Cinnamon version but that version lacked higher refresh rates and I think was not wayland Thank you!

Maybe you don't need some function, but please don't break it.

Device: Opi5-Plus Armbian Image: Armbian_25.5.1_Orangepi5-plus_noble_vendor_6.1.115_kde-neon_desktop.img.xz Upgraded successfully and reboot up with no issue on Wayland session. Operating System: Ubuntu 24.04 KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Kernel Version: 6.1.115-vendor-rk35xx (64-bit) Graphics Platform: Wayland Processors: 4 × ARM Cortex-A55, 4 × ARM Cortex-A76 Memory: 15.6 GiB of usable RAM Graphics Processor 1: Mali-G610 Graphics Processor 2: Mali-G610 Graphics Processor 3: llvmpipe Product Name: Orange Pi 5 Plus

If it is NAND then you are out of luck as mainline Linux has no support for NAND. If it is eMMC then your dtb would likely need to be modified to support your hardware if it isn't showing up. My guess is that you have NAND.

Do you see all the needed files in the initramfs? Use lsinitramfs -l /boot/initrd... What guide did you use?

Hello, I have a T95 Super with H2+/H3 processor. I've been successful running Armbian in the past on it and even writing to eMMC but am looking for the most updated build I can to burn to the eMMC. I have H3droid running on it after a VERY long install process and many board reburns to fix it. I noticed H3droid has an "Armbian" option in it's rescue menu but there don't seem to be any instructions on how to install with the menu/use it. What is the best new build for this setup? Thank you!

Hello, My pet labubu and I got the most recent onecloud/odroid c1 versions fully working on my horrid former Oriental TV box, the TVPad 4 (previously brought up by user @daniyo). Everything works perfectly, except I want to finish my building by installing to eMMC. None of the recent builds I can find come with an install.sh script, and I cannot see the eMMC (or NAND if it's NAND) in lsblk or any of the installers. Does anyone have any clues or suggestions that can help the poor long suffering Labubu fix this issue? He just wants to watch IPTV and play little games

I was extremely excited to read this. My issue currently is that I'm dealing with S805 and H3 builds which had builds dominated by the megalomaniacal user whose name starts with "B" (really not a fan of their behavior but extremely impressive work). For some reason, these builds never come with the install.sh scripts that Amlogic builds normally come with, and I can only write S805 builds to eMMC using builds with the 5.7/3.10 kernel to eMMC because they come with an install.sh. I really want to "finish" the builds by writing them. I'm hoping to use dd to write to the eMMC but it doesn't come up with lsblk at all (except with the 3.10 kernel). Does anyone have any suggestions about how to get around this?

I agree, it would be a small adjustment that is hopefully easy. I don't know how to do it myself but the inbuilt eMMC is definitely not big enough for the kind of files I want to serve from the board. And I apologize, I didn't realize that random people can upload builds like that; I meant that it appeared to be a listed frequently updated board.

Are you twwn on github, @tast ky? As mentioned in the bug tracker, you need to try a different image. Please keep the discussion of run-time issues in the forum. This is where run-time bug triage happens. Until the time one can essentially make a PR with a clear code fix, the forum is where we discuss run-time problems.

Not a problem. Just please do not give up I have 5 units of those waiting for a newer kernel LoL

I'd say try flashing again with a different image, possibly one that worked in one of your other boards. Verify the download and the flash process with checksums.

Yes, your list of questions is a bit long (understatement) and as such comes off demanding. I would say armbian or an SBC is not for you if you require a great amount of handholding and that's the vibe I am getting from your laundry list of questions for everything under the sun. I guess you want to be thorough before taking the plunge, but you need to take armbian with a different attitude, I guess; be happy when it runs, get down to help fixing it when it doesn't. We are NOT selling you a product.

Hi @salas, Unfortunately, no. In my free time, I've only had time for small patches and bug fixes. I've been trying to get it working on newer u-boot versions (v2025.07), but without any luck so far, I'll be busy this week, but I can probably release a new update next month (August). I've tried it with and without an M.2 drive using the SD card as boot and root, but I can't reproduce it.

You are running with a broken firmware: Your version is also quite outdated: A current firmware log looks like this:

please provide the output of "apt policy armbian-bsp-cli-rock-5b" and "sudo cat /etc/apt/preferences.d/*"

Chromium is not the best for playing videos. Try mplayer or mpv or something alike. I doubt you'll get great performance beyond 720p though. Might not even get it in some cases with 720p? If I wanna use an SBC as a media player, I either use LibreELEC or CoreELEC and don't use Alllwinner, but Amlogic. Good luck.

If you can still return the item for a refund, go ahead and do so. If you can still leave a bad review for this bad seller, go ahead and do so. This person has quite the gall to take your money but send you to us for the costly support. Buy cheap, buy twice.