All Activity

Crashed.

https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus

moved

Hi, I'm doing some tests on my BTVe10 Box TV. I tried the image "Armbian_23.02.2_Aml-s9xx-box_jammy_current_6.1.11.img" with the dtb "meson-g12a-sei510.dtb" and it booted but the wifi didn't work. I used the command iwconfig and got the error "no wireless extensions". How can I make the wifi work?

Each code change represent danger that some feature out of tens of thousands will stop working. One bug is fixed, something else can and do break down ... Nobody knows when this happens as nobody can't test all features. Testing is expensive and we run this - for public good service - mainly with our private money. Since information does not exists, we will not be keeping list of working / not working features for you. Especially not if this require additional expensive manual work. I told you to verify with latest image from development as this might just work. You didn't and there is little we can do from here. If you didn't know, we provide users results of automated testing, which is sadly primitive and can't test complex functions as in this case, but it will stay that way as we have not enough support/interest from anyone (but everyone would like to have this info) If you need better info that this https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results apply here: and start working for us as a full time volunteer. I know you will not, but this request is on same level as yours. So far, in one year, we didn't get anyone.

I am not your personal assistance. Orangepi (mainly as they are chepest) customers are demanding thousands of fixes, changes and improvements. Personally I can't answer to this and other thousands of issues that are found in code / text. I would love to but its impossible even as a team and I have to run the project and sometimes I chat on forums. Mainly for fun and providing hints. I can't be your partner in resolving your (clearly business) problem. I would love to, but Orangepi treat as not good and we treat their clients accordingly. Use other board and you will get help. Isn't that stupid? Yes, but this is one of ways we fight abuse that is targeted toward open source developers. In this segment of open source, there are things you might never experienced with your work in open source. Isn't it better to be open for other perspectives? I believe in yours. Perhaps this will give you a picture on resources you are addressing? You are not the only one that is requesting support. Our resources are 1/1000 of needed. We are developers, we maintain serious and complex system and we don't have much time for individual problems. Regardless if you think we should be more attractive. We can be, but then we have to kill R&D. Which is source of sorrow, frustration and costs. Why do you even try to be accepted over the line? And why you think this problem is important enough to be even discussed? Why don't you resolve a problem you find? And on and on. I told you already that we only loose if we fix a bug. We have competitors, that invest nothing, while they can provide the same. In order to catch them, we have to invest less and less. And be more attractive at the same time, agree with that. This means we should invest into sales a lot more, where again you know what has to suffer. Absolutely. We love that, me included. But I have to run this development on totally different level. If you would set our priorities, we would already be long dead. Imagine users, who in big majority have no clue about how much time some problem is needed, they don't care how many problems are already been worked on, what is team capacity, and on and on. Remember also that, at the end, support goes under "best effort" principle. If serious and life important problems are not done, your will wait. A week, month, year ... never. This is how it goes and this won't be changed. Not sure what you mean by that, but open source is like freedom.

Writing one sentence “our image is intended only for installation from SD” is not “more and more”. This doesn't require a second or third job, or month or years. Besides, being an open-source developer is your conscious choice, so why have you already repeated a hundred times that you have nothing to gain from it? If human impact is so important to you, do something that will bring it, instead of blaming me for something. Open source is a calling, not an excuse.

If you care so much about people not wasting time, documentation is open source, invest your time https://github.com/armbian/documentation and stop wasting my time. Our project is saving all of you years, not just months. And you still don't get it and want more and more. Remember that not you, not the one that generates problem contributes virtually nothing. Buy a PC, which works well with our product.

My set-top box has an FX-618-D4_V10 board. The WI-FI chip is HK6334Q. WIFI started working when using the brcmfmac4334-sdio.bin driver and file brcmfmac4334-sdio.txt from the website https://github.com/LibreELEC/brcmfmac_sdio-firmware/blob/master/brcmfmac4334-sdio.bin .

You don't understand what I'm talking about. I understand perfectly well what open source is, I have been dealing with it for 14 years. Including, sometimes I do something of my own. But if my product is not intended to be used according to the instructions for what it is based on, I write about it in big red letters so that people do not waste time on actions that are not designed for results. Is Orange Pi shamelessly stealing from Armbian? Apparently, they still came up with the phrase “the flashing manual is intended only for our images”, which helps save time without making unnecessary mistakes. And they have (not so fancy but) manual, by the way. What I am asking from you is not some kind of feat, or a "fancy manual", or something for which you need to involve PR. We are talking about the basic required minimum: if you want to attract people to your project, it must be attractive. At a minimum, attract by accessibility of use. It should at least run. If it not designed to be run using certain methods, (RkDevTool for example) just write one sentence about it right above the download link. If you suddenly have some kind of documentation, attach a link to it there. There's nothing complicated about it, no one forces you to write archwiki for each image. You can’t just do it "somehow", post it without the simplest explanation and justify it by saying that it’s open source. All Linux is open-source, and 99% of them either just work, or without a forum it’s clear how to make them work. Because it's just minimum.

I tried to make of file with command: dtc -O dtb -o sun50i-h616-w1-gpio.dtbo sun50i-h616-w1-gpio.dts but result is with warring so we can not use example from Orange Pi Zero 2 to create dtbo file for OZPI v3 ? Warning (unit_address_vs_reg): /__local_fixups__/fragment@1/__overlay__/onewire@0: node has a unit name, but no reg or ranges property sun50i-h616-w1-gpio.dts:27.33-69: Warning (gpios_property): /fragment@1/__overlay__/onewire@0:gpios: cell 1 is not a phandle reference sun50i-h616-w1-gpio.dts:27.33-69: Warning (gpios_property): /fragment@1/__overlay__/onewire@0:gpios: Could not get phandle node for (cell 1)

@SUPA Thank you for testing the patch. I assume it worked and that you are working with an orangepisero3. If you want to build you own images follow the directions in the Armbian build manual: https://docs.armbian.com/Developer-Guide_Build-Preparation/ and clone my repository. Unfortunately I have limited space on my google drive. git clone https://github.com/stephengraf/armbian_build_sg.git

You are using a lot of our work also if you use images for Orangepi 5 with different name, from different DJs and / or even official ones. Official Debian and Ubuntu images are shameless copy of Armbian, assembled with old tools and slightly different - some features will work better, some not. As they are never upgraded, they never breaks. We work together with Joshua-Riek on kernel and other things. Images should behave more or less the same, but as they were not released at the same time, diff exists. If your problem is fixed in our images, nobody will check this for you because this is not a commercial product and you are not a customer - there are daily automated builds at the download page. Try them. We can't spoil you with writing fancy manual and make better support as we will gain nothing. Competitors (Orangepi and copycats) are not copy pasting code we made (remember this is open source world), they also copy pasting instructions we make. Ask Orangepi to cover those costs (they will ofc not) or you cover them. Problem is that for 99% of projects costs we have to find elsewhere (most people have jobs somewhere) or do it for free (slave work when abuse is used. And this exists in large scale). Donations only cover 0.5% ... Asking for more, from end user perspective, is rude. Mitigating your debt first? Every donation counts. Complex software without active maintaining will start to fall apart, but people that made money with you will be long gone by then. Regressions will happen and again we will be the one behind ...

@BOFFBOY, @eddie, @ghosty could you try to run sudo memtester 30G (or 20G if you don't have enough free memory) ?

Hi all, @royk, I tried to replace rk3588-orangepi-5-plus.dtb file but it doesn't boot at all. Something really strange is happening. Yesterday I tried the following official Orange Pi images on eMMC: Orangepi5plus_1.0.8_ubuntu_jammy_server_linux6.1.43 Orangepi5plus_1.0.8_debian_bookworm_server_linux6.1.43 Orangepi5plus_1.0.8_debian_bookworm_server_linux5.10.160 They seemed to work well, at least did not crash after starting of memtester. Today I tried Joshua Riek's image loaded from SD card, it crashes also, tried 3 times. After that I flashed the same image to eMMC and it seems to work. And after flashing it to eMMC the image booted from SD card started working again I'm still trying to figure out the condition when it crashes and when it doesn't.

Description This is to fix wrong DRAM size detection in Orange Pi Zero 3 board with 1.5GB DRAM. Currently they are not able to boot as they detect 2GB DRAM, so after applying this patch they will boot normally. Other boards with 1GB/2GB/4GB DRAM will continue working the same way with this patch. This patch would only be applied to u-boot v2024.01 release. I will provide other patch for u-boot v2024.04 and newer. How Has This Been Tested? [X] Build image for Orange Pi Zero 3 board, flash devices with 1/1.5/2/4GB DRAM and power on with serial cable: logs will show the right memory size [X] Build image for Orange Pi Zero 3 board, flash devices with 1/1.5/2/4GB DRAM and power on: boards will boot normally Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] I have commented my code, particularly in hard-to-understand areas [X] My changes generate no new warnings View the full article

@OttawaHacker I already did it, you can find it attached here: This is what I am trying to avoid.

This is awesome. Would you be able to share the uboot bin file to start? Also PR to the community build would be super useful but I suspect there is a bit more to figure out. I did some digging around the builds and was not able to figure out where the u-boot thing was happening. Would the OPI Zero 3 1.5G be a separate configuration? Sounds like it needs to be a separate build and configuration (until more uboot magic can be figured out). Also this doesn't look like a regular patch if a u-boot bin needs to be applied.

@SteeMan This is what I am trying to do, but I should submit at least two patches, one for u-boot release v2024.01 and other one for v2024.04 and newer. After doing some tests, adding patch to patch/u-boot/u-boot-sunxi folder, it is applied during build, but for any u-boot release. I tried to add it to patch/u-boot/v2024.01 folder, but it does not work. I did not find any document explaining how to do it. Any help is welcome.

Because some features on website still has to be done manually. For which we don't have sufficient man power, org resources or coding resources to complete automation. If you are PHP / Python coder and want to contribute resolving this problem, PM.

So, with the image of Joshua-Riek from here https://github.com/Joshua-Riek/ubuntu-rockchip/releases, flashed according to the same OPi user manual for RkDevTool, it's just work. We can assume that the problem has been solved.

Hey @jock I need to install the kernel headers on Armbian. So I've tried to build the legacy kernel with flag "INSTALL_HEADERS=yes" I builded it like this: cd /opt git clone -b history-rk322x-family https://github.com/paolosabatino/armbian-build.git build cd build ./compile.sh docker-shell ./compile.sh BOARD=rk322x-box BRANCH=legacy RELEASE=focal BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=yes INSTALL_HEADERS=yes KERNEL_KEEP_CONFIG=yes But the results were these: |🔨] Get:30 http://ports.ubuntu.com focal-updates/multiverse Translation-en [7,880 B] [🐳|🔨] Get:31 http://ports.ubuntu.com focal-backports/main armhf Packages [45.3 kB] [🐳|🔨] Get:32 http://ports.ubuntu.com focal-backports/main Translation-en [16.3 kB] [🐳|🔨] Get:33 http://ports.ubuntu.com focal-backports/universe armhf Packages [24.2 kB] [🐳|🔨] Get:34 http://ports.ubuntu.com focal-backports/universe Translation-en [16.3 kB] [🐳|🔨] Reading package lists... [🐳|🔨] E: The repository 'http://apt.armbian.com focal Release' does not have a Release file. [🐳|🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_update ] [🐳|🔨] Hit:2 http://ports.ubuntu.com focal InRelease [🐳|🔨] Hit:3 http://ports.ubuntu.com focal-security InRelease [🐳|🔨] Hit:4 http://ports.ubuntu.com focal-updates InRelease [🐳|🔨] Ign:1 http://armbian.tnahosting.net/apt focal InRelease [🐳|🔨] Hit:6 http://ports.ubuntu.com focal-backports InRelease [🐳|🔨] Err:5 http://xogium.performanceservers.nl/apt focal Release [🐳|🔨] 404 Not Found [IP: 198.140.141.60 80] [🐳|🔨] Reading package lists... [🐳|🔨] E: The repository 'http://apt.armbian.com focal Release' does not have a Release file. [🐳|🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_update ] [🐳|🔨] Hit:2 http://ports.ubuntu.com focal InRelease [🐳|🔨] Hit:3 http://ports.ubuntu.com focal-security InRelease [🐳|🔨] Hit:4 http://ports.ubuntu.com focal-updates InRelease [🐳|🔨] Ign:1 http://armbian.tnahosting.net/apt focal InRelease [🐳|🔨] Hit:5 http://ports.ubuntu.com focal-backports InRelease [🐳|🔨] Err:6 http://mirrors.jevincanders.net/armbian/apt focal Release [🐳|🔨] 404 Not Found [IP: 172.93.158.60 80] [🐳|🔨] Reading package lists... [🐳|🔨] E: The repository 'http://apt.armbian.com focal Release' does not have a Release file. [🐳|🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_update ] [🐳|🚸] Command failed 3 times, giving up [ chroot_sdcard_apt_get_update ] [🐳|💥] Error 1 occurred in main shell [ at /armbian/lib/functions/rootfs/rootfs-create.sh:164 create_new_rootfs_cache_via_debootstrap() --> lib/functions/rootfs/rootfs-create.sh:164 create_new_rootfs_cache() --> lib/functions/rootfs/create-cache.sh:69 do_with_logging() --> lib/functions/logging/section-logging.sh:81 artifact_rootfs_build_from_sources() --> lib/functions/artifacts/artifact-rootfs.sh:80 artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34 obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280 build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:392 get_or_create_rootfs_cache_chroot_sdcard() --> lib/functions/rootfs/create-cache.sh:83 build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:14 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> ./compile.sh:50 ] [🐳|💥] Cleaning up [ please wait for cleanups to finish ] [🐳|🌿] Unmounting recursively [ SDCARD - be patient ] [🐳|🌱] Unmounted OK after 2 attempt(s) [ SDCARD ] [🐳|🌿] Unmounting recursively [ MOUNT - be patient ] [🐳|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-f4961847-8e5a-40a8-a7cd-ecb4e58220c3.log.ans ] [🐳|🌿] Share log manually (or SHARE_LOG=yes): [ curl] Am I doing something wrong?

https://github.com/armbian/os#latest-smoke-tests-results still shows "community." It's a mystery as to why the download page has it categorized as Standard Support.