All Activity

I have the same Android TV, and I've been trying to boot Armbian but I don't seem to successfully accomplish it. I believe we are all alone with this, and nobody will ever help us. Maybe RK3399 SoC is still problematic after 9 years.

@tofamus30 You said box Is 322x You said wifi Is 6330 But then you tried dtbo from 3318 board Not sure if is gonna work

Are u kidding me? This is freaking awesome Thanks guys, I will be patiently waiting..

R76S will be supported, but its too early at this stage. We setup download page https://www.armbian.com/nanopi-r76s/ but no images yet.

Thank you for the advice @MattWestB, But I already tried all available LED-config options, booting fine, but none working

Oh right, I forgot about that. Luckily the rk3576 is already maturing in the Linux kernel. In that case we will just hope for the best. Thank you for your time. edit: Could this topic be moved to https://forum.armbian.com/forum/176-other-families/

Try different LED-config then its also changing the hardware for the SD-Card interfaces = WiFi module but prepare that it can ending with not booteball system.

Probably marking on the board is the only what really matters.

Armbian does not accept new boards for official support unless there is funding involved. However anyone from the community can step up and add it as community-supported.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Hi guys, I would like to make a support request for the: NanoPi-R76S ($49): https://www.friendlyelec.com/index.php?route=product/product&product_id=308 Thank you for considering. Dantes

Finally there is a proper tor-browser available for arm64/aarch64: 1. Goto https://nightlies.tbb.torproject.org/nightly-builds/tor-browser-builds/ 2. Navigate into: tbb-nightly.<date>/nightly-linux-aarch64/ 3. Download tor-browser-linux-aarch64-tbb-nightly.<date>.tar.xz 4. Unpack with tar -Jxvf and run tor-browser/start-tor-browser.desktop Yay! (I'm sure you can compile it too from their github page)

Hey, has anyone tried using the BPI-3C1-27? Just wondering about price and if it’s really in stock.

I made a configuration via armbian-config, but the camera does not work, here are the messages /sys/bus/i2c/drivers/ov13855 3-0036 bind uevent unbind sudo i2cdetect -y 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- UU -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- 58 -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- dmesg | grep ov13855 [ 14.074752] platform csi2-dphy0: Fixed dependency cycle(s) with /i2c@feab0000/ov13855-1@36 [ 14.338234] ov13855 3-0036: driver version: 00.01.04 [ 14.338301] ov13855 3-0036: Failed to get power-gpios, maybe no use [ 14.338330] ov13855 3-0036: Looking up avdd-supply from device tree [ 14.338336] ov13855 3-0036: Looking up avdd-supply property in node /i2c@feab0000/ov13855-1@36 failed [ 14.338365] ov13855 3-0036: supply avdd not found, using dummy regulator [ 14.338418] ov13855 3-0036: Looking up dovdd-supply from device tree [ 14.338424] ov13855 3-0036: Looking up dovdd-supply property in node /i2c@feab0000/ov13855-1@36 failed [ 14.338434] ov13855 3-0036: supply dovdd not found, using dummy regulator [ 14.338454] ov13855 3-0036: Looking up dvdd-supply from device tree [ 14.338459] ov13855 3-0036: Looking up dvdd-supply property in node /i2c@feab0000/ov13855-1@36 failed [ 14.338468] ov13855 3-0036: supply dvdd not found, using dummy regulator [ 14.338484] ov13855 3-0036: could not get default pinstate [ 14.338487] ov13855 3-0036: could not get sleep pinstate [ 14.348869] ov13855 3-0036: Detected OV00d855 sensor, REVISION 0xb0 [ 14.863602] ov13855 3-0036: Consider updating driver ov13855 to match on endpoints [ 14.863609] rockchip-csi2-dphy csi2-dphy0: dphy0 matches m00_b_ov13855 3-0036:bus type 5 with the original distribution the camera works

I checked armbianEnv.txt and it says rockchip5, to triple check, I checked the site I bought it from, also says 5. So I believe I mislabeled the post as 5b, but it is a 5.

Search my threads with keyword "ili9341". Post a photo of your wiring, a schematic, and what did you try within armbian... in this thread.

This is similar to physical damage to the SD card

Those are standard kernel patches. Do you mean Armbian build system does not support multiple patches in a single file? If so, you can download each of the 14 patches individually and then apply them. Or you can try reformatting the combined patch file as a single patch.

I gave this a try but no success. The structure of original source code doesn't match the one for armbian. It would be great if you could make a patch as in this link

@dale I'm happy that it's now working! I'll add the x98h dtso to my devices library when I'll have some time (using the latest dt-bindings syntax). You can download the patch of the latest tm16xx version here: https://github.com/torvalds/linux/compare/master...jefflessard:linux:tm16xx.patch Let me know if the latest version works well for you and the updated x98h dtso (if you happen to do it before I have some time). I'll be glad to add you with Tested-by tag when submitting.

Can you make a patch for armbian? It will be easy for us to try.

Hi, I finally got my display to work with below DT overlay source. My device is x98h. Thank you! /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = <&pio 2 7 GPIO_ACTIVE_HIGH>; mosi-gpios = <&pio 2 2 GPIO_ACTIVE_HIGH>; cs-gpios = <&pio 2 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0x0>; spi-3wire; spi-lsb-first; spi-rx-delay-us = <1>; spi-max-frequency = <500000>; tm16xx,transposed; tm16xx,digits = [00 01 02 03]; tm16xx,segment-mapping = [00 01 02 03 04 05 06]; #address-cells = <2>; #size-cells = <0>; led@4,0 { reg = <4 0>; function = LED_FUNCTION_USB; }; led@4,1 { reg = <4 1>; function = LED_FUNCTION_SD; }; led@4,2 { reg = <4 2>; function = "hi-wifi"; }; led@4,3 { reg = <4 3>; function = "low-wifi"; }; led@4,4 { reg = <4 4>; function = "colon"; }; led@4,5 { reg = <4 5>; function = "apps"; }; led@4,6 { reg = <4 6>; function = LED_FUNCTION_LAN; }; }; }; };

Very good. First make sure you are actually having the 5B and not the 5 model. The reason I'm asking is in the logs is always model 5 and not 5B as supposed to. Did you adjust the dtb to use 5b one just like mentioned at the download page?

Dear Community, I currently want to reduce the transmission power of the NanoPi Neo Air. This means that I simply want to be able to set the Wifi transmission power in 10% steps, for example. What I have already tried: Instructions according to Wiki: OpenWrt image is not flashed. No access via browser. But it doesn't matter: max. transmission power is used in AP mode. Setting as in the Wiki image "TransmitPower:auto" probably does not apply here anyway. Network Manager TUI via "sudo nmtui" has no such settings. Adjust the NVRAM files in "/lib/firmware/brcm" or "/lib/firmware/ap6212" step by step. All changes are saved in the txt file but not written to the host driver. The tests do not recognise any changes. No matter how I adjust the values. (Many different attempts) Firmware patch ("brcmfmac43430a1-sdio.bin") with HxD: The place where "Maxp2ga0" is set is found & edited in binary file. --> 07 60 3F 60 6D 61 78 70 32 67 61 30 = `?`maxp2ga0 Bytes for maxp2ga0: 07 60Bytes for maxp2ga1: 3F 60 3F 60 → 0x603F or 0x3F60 → similar, typically 0x60 = 96 → 20 dBm (Both antenna values have been set) Unfortunately, this change is not loaded into the host driver on the chip either... Continue working on existing "locked" firmware with Seemoo Lab? (unlikely) Throttling Tx-Power via command "sudo iw dev wlan0 set txpower fixed 1500" Change is displayed under "iwconfig wlan0", but it is either overwritten directly or not taken into account at all. No change is noticeable in the tests, no matter how low the value is set. Other firmware & NVRAM tested: Wifi does not start at all (IP rebount reconnect try xx) or the W-Lan is not visible. Maybe you can start here again and find a working firmware that is not "locked"? Which software to use? I test with Putty via the wifi connection. I use the following command: for i in $(seq 1 30); do iw dev wlan0 station dump | awk '/signal/ {print $2}'; sleep 1; done \ | awk '{x[NR]=$1; s+=$1} END{ if (NR>0) {mean=s/NR; for(i=1;i<=NR;i++) v+=(x[i]-mean)^2; sd=sqrt(v/NR); print 'N="NR, "mean="mean, "sd="sd} }' This measures the connection strength in dBm every second, 30 times, and only outputs the mean value. I always have the same 3 measurement positions with the exact same antenna alignment. (In a corridor: 3m, 12m, 25m) Interesting stuff: sudo iw phy phy0 info dmesg | tail -n 50 | grep -i brcmfmac File paths: /lib/firmware/brcm & /lib/firmware/AP6212 CC code (country) is not set by default: "sudo iw reg get" & "sudo iw reg set DE" Are there any other approaches or have I overlooked something? Thank you very much for your help!

Thanks, very helpful. Maybe someone will be able to bring some light on how second partition could appear (uboot update script transition bug?), while being not a part of Armbian's functionality.