All Activity

May this tell you something? Edit: In my case, on the SD card the /boot folder is empty. So I don't know how to use DTS files. Also, a flash drive was plugged: sda1 device. I can see Armbian sees the internal memory of my device (mmcblk1p1...p2...) lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 57,7G 0 disk └─sda1 8:1 1 57,7G 0 part /media/chad/New Volume mmcblk1 179:0 0 14,7G 0 disk ├─mmcblk1p1 179:1 0 4M 0 part ├─mmcblk1p2 179:2 0 4M 0 part ├─mmcblk1p3 179:3 0 4M 0 part ├─mmcblk1p4 179:4 0 4M 0 part ├─mmcblk1p5 179:5 0 4M 0 part ├─mmcblk1p6 179:6 0 1M 0 part ├─mmcblk1p7 179:7 0 64M 0 part ├─mmcblk1p8 179:8 0 96M 0 part ├─mmcblk1p9 179:9 0 384M 0 part ├─mmcblk1p10 179:10 0 384M 0 part ├─mmcblk1p11 179:11 0 16M 0 part ├─mmcblk1p12 179:12 0 1M 0 part ├─mmcblk1p13 179:13 0 4G 0 part └─mmcblk1p14 179:14 0 9,7G 0 part mmcblk1boot0 179:32 0 4M 1 disk mmcblk1boot1 179:64 0 4M 1 disk mmcblk0 179:96 0 29G 0 disk ├─mmcblk0p1 179:97 0 256M 0 part /boot └─mmcblk0p2 179:98 0 28,4G 0 part /var/log.hdd / zram0 254:0 0 989,3M 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log df -h Filesystem Size Used Avail Use% Mounted on tmpfs 198M 6,3M 192M 4% /run /dev/mmcblk0p2 28G 4,7G 23G 17% / tmpfs 990M 0 990M 0% /dev/shm tmpfs 5,0M 0 5,0M 0% /run/lock tmpfs 990M 12K 990M 1% /tmp /dev/mmcblk0p1 224M 122M 92M 58% /boot /dev/zram1 47M 1,6M 42M 4% /var/log tmpfs 198M 104K 198M 1% /run/user/1000 /dev/sda1 58G 28G 31G 48% /media/chad/New Volume blkid /dev/mmcblk0p1: LABEL="armbi_boot" UUID="b7da92dc-e8d6-4f98-bc78-2c2d26cb0e58" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="bootfs" PARTUUID="5ebaa50c-e6a2-ef4b-bdc0-42959c284dac" /dev/mmcblk0p2: LABEL="armbi_root" UUID="15ad00eb-944a-4829-8ff0-a0d0b211226c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a6783103-918f-fc44-b9ba-b8c9fc8915e4" /dev/mmcblk1p11: UUID="c6ed55dd-55ba-4fb3-81ed-e341a836e379" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="metadata" PARTUUID="015f0000-0000-4131-8000-2af900001415" /dev/mmcblk1p14: UUID="4548798e-a22e-48de-8b75-9fcbd508481a" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="userdata" PARTUUID="216e0000-0000-471b-8000-1139000006f0" /dev/mmcblk1p10: UUID="d90fb683-12be-438a-a851-85bb4899d594" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="cache" PARTUUID="a1470000-0000-4b4a-8000-335e00002f47" /dev/zram0: UUID="f4ddf41e-a476-410c-927e-7d1ad4814472" TYPE="swap" /dev/zram1: LABEL="log2ram" UUID="e37fe586-baaf-498e-980e-cdd667b954c2" BLOCK_SIZE="4096" TYPE="ext4" /dev/mmcblk1p3: PARTLABEL="trust" PARTUUID="d1630000-0000-4261-8000-78e300006a8d" /dev/mmcblk1p13: PARTLABEL="super" PARTUUID="78170000-0000-462e-8000-351f00003b21" /dev/mmcblk1p1: PARTLABEL="security" PARTUUID="72340000-0000-4939-8000-1a3d00005715" /dev/mmcblk1p8: PARTLABEL="recovery" PARTUUID="b2460000-0000-455b-8000-592d000036b6" /dev/mmcblk1p6: PARTLABEL="vbmeta" PARTUUID="4e6c0000-0000-4d7e-8000-1fcf000040fc" /dev/mmcblk1p4: PARTLABEL="misc" PARTUUID="357e0000-0000-4575-8000-0005000045d9" /dev/mmcblk1p2: PARTLABEL="uboot" PARTUUID="28010000-0000-4b3f-8000-3b8d00007f0e" /dev/mmcblk1p12: PARTLABEL="baseparameter" PARTUUID="5b6c0000-0000-424a-8000-6fa2000072f0" /dev/mmcblk1p9: PARTLABEL="backup" PARTUUID="74600000-0000-4a1e-8000-3b0700007340" /dev/mmcblk1p7: PARTLABEL="boot" PARTUUID="927d0000-0000-4354-8000-060700007162" /dev/mmcblk1p5: PARTLABEL="dtbo" PARTUUID="1c5d0000-0000-4b75-8000-66bb0000653c" /dev/sda1: LABEL="New Volume" BLOCK_SIZE="512" UUID="2070DF2870DF0406" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="17cffda1-bd82-44b9-8fc4-6e7175882b3a"

Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] Documentation summary for feature / change Please delete this section if entry to main documentation is not needed. If documentation entry is predicted, please provide key elements for further implementation into main documentation and set label to "Needs Documentation". You are welcome to open a PR to documentation or you can leave following information for technical writer: [ ] short description (copy / paste of PR title) [ ] summary (description relevant for end users) [ ] example of usage (how to see this in function) How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ ] Test A [ ] Test B Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

I'm trying to do this but my /boot folder is empty. I used the exact same version you mentioned: Armbian_community_24.5.0-trunk.367_Hinlink-ht2_jammy_legacy_5.10.160_gnome_desktop Was it moved to another folder?

So I managed to extract .dtb files from uboot.img using this extract-dtb tool. Later on, on a PC running Ubuntu 22.04 LTS I used "device tree compile" to decompile thos dtb files into dts files. I followed this article trying to use those DTS files to get the correct hardware informatin and/or drivers, but the /boot folder in the flashed SD card is empty. Probably, as the article says, dtb overlay is not activated in this image.

I tried the uboot with the same image you mentioned. Something is definitely happening, I see red and green lights flashing however there is nothing on my hdmi output, no shell or nothing else. Am I missing something?

@OttawaHacker you could try the images from here: https://www.armbian.com/orange-pi-zero-3/ and to patch the u-boot into the image from here https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3/tree/main

I have this Rupa X88 13 TV BOX with also uses RK3528, I dumped many parts of firmware using a tool called rkdumper and managed to extract .dtb files using a tool called dtb-extract Maybe this can help you. I don't know how to use those files yet, but reading your post I think I have a hint now

When I try to enable iptables (last step), I get the folowing error: Failed to enable unit: Refusing to operate on alias name or linked unit file: iptables.service

@ag123 @OttawaHacker I submitted a pull request in order to add DRAM patch to community builds. Let's see how it goes...

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.