All Activity

@Nick A I'm using you latest build from pixeldrift on a Transpeed M98-8K TV box with a H618 and it works like a charm without any modifications! 👏🥳 Now I'm curious how these builds will go on, as the directory description talks about "experimental", "testing only", "are not intended for end users".... ? I will use the TV box as a small home server and do you know if this device (or the Transpeed 8k618-T) will become some more or less "official" cummunity build? Many thanks in advance!

That looks like a fork of Armbian. These forums for Armbian builds not forks of Armbian builds. Generally we would recommend you direct questions based on forks of Armbian to those working on those forks.

Hmmm I seem to be having problems following this guide using: - OS: Armbian (unnofical) Noble ~ Armbian (24.04.30-armsurvivors-138) aarch6 - Hardware: On my Lenovo x13s gen 1 ~ sc8280xp - Kernal: 6.9.0-rc7-sc8280xp-arm64 I think im hitting the same problem with arm-linux-gnueabihf depency issues - This is problematic as without the 32bit toolchain (or whatever its called) I cant compile box86 correctly - The depency failures are, libpng16-16:armhf, libncurses5:armhf I would imagine it is because I am attempting this on Ubuntu Noble 24 (Armbian port) instead off earlier versions. I am playing around with trying to get Debian 13 Trixie (The Ubuntu Noble 24 equivilant) on a raspberry pi 4 in 32bit mode but will keep my progress tracked here. I also was messing around with the schroot method but I feel like this is the better way

that did it, it works now and I don't have that green pricture anymore. Thanks a lot.

What build are you using? Where are you placing you custom dtb? What entry do you have in your extlinux.conf file for the dtb?

Thank you guys for putting the effort to port Armbian to H616/H618 android boxes. I have a 4GB/64GB T95H (exactly the same PCB: https://linux-sunxi.org/File:T95H_PCB_Top.jpg, https://linux-sunxi.org/File:T95H_PCB_Bottom.jpg, just with stock firmware T95H-H616-X24). By default the serial console did not work. After adding a shortcut to tx-path, and 1K resistor to the rx-path (between two pads of SOT-23), the boot process of stock fw became available, and communication with the FW became possible at 115200 baud rate. Downloading the latest available PRxxxx_20240415_db21e5f7d_Armbian-unofficial_24.5.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12.tar.xz and putting the extracted img to SD card, powering up the box with pressed uboot button does not give any console output (neither on 115200 nor on 1500000 baud rate). Did I make something wrong? Or is this box is not supported by the tested firmware at any level?

hello i'm having a issue with my old tx9 pro s912 3g 34gb the problem is the wifi sometime will stop work and when i do a apt upgrade i have to replaced the dtb file because it get delete, i using a dtb file that a user post on github, i wonder if any of you have this issue, it cant be the wifi controller is dying, or my dtb file is wrong

@peter.eismann I added patches to glibc: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/rockchip-multimedia/+sourcefiles/glibc/1:2.35-0ubuntu3.4+2widevine/glibc_2.35-0ubuntu3.4+2widevine.debian.tar.xz But it seems that this patch is no longer needed with newer glibc: https://aur.archlinux.org/packages/widevine

Current status on the support: mostly working, but having some issues. I am pushing my work on github: https://github.com/JohnTheCoolingFan/armbian-build/tree/btt-cb2-rebase It is based off of BigTreeTech's fork of armbian build framework here: https://github.com/bigtreetech/build/tree/CB2 Current important issues: WiFi hardware isn't being recognized, interface wlan0 doesn't show up in builds made from my branch Some builds are setting the board name to "BigTreeTech CB1" instead of "BigTreeTech CB2" I'm trying to find out what causes these issues, the first being of higher priority, of course. Any help is welcome. After these issues resolved, I would like to address the rest of BTT's changes, which include kernel module patches and a patch for a systemd service.

I tested the 6.6.30 kernel without changing anything. The assembly was done locally on the main branch. I noticed that the temperature for A64 A83T is calculated incorrectly. DMESG does not report errors. Device loading is a bit weird with freezes. U-boot has not checked yet. The first step is to re-release the patches. I've already done that for the core. I'll fix the temperature and make a pull request.

@amazingfateI finally made some progress. I've got a working 6.1.43 kernel with Ubuntu noble and the newest versions of Kodi and Inputstream adaptive. I have used the vendor-boogie-panthor configuration for armbian and added my IR Receiver settings. Unfortunately with Netflix the WivedineCDM lib does not work as the patches for glibc6 are missing. I know there is a patched version in your PPA, but since I use noble instead of jammy I was wondering what I need to do to build a patched libc6 myself. Do you remember how you built it? (glibc=1:2.35-0ubuntu3.4+2widevine)

Hey, Having issues with Firefox's multi-factor authentication (MFA)? Remain calm! Fortunately, there are also remedies for the common reasons why it could not be functioning. Let's begin with the fundamentals. Have you updated your Firefox browser recently? Older versions may not always work with some websites or multi-factor authentication. It might only take updating Firefox to the most recent version to resolve the problem. Think about your browser addons after that. Even though some of those add-ons can be quite helpful, others may interfere with MFA operations. To find out which one is causing the issue, try temporarily turning each one off one at a time. Lastly, the cache and cookies on your browser may be the problem. To make browsing more convenient, information is temporarily stored in these files. Thank You

@peter.eismannYou are using EGL as render method, which will only support NV12 format. You can try direct-to-plane.

@Devmfc Did you manage to run an Armbian system for the S905W2 processor with a graphical interface? I have a TV Box S905W2 with SV6256P and I would like to convert it to Armbian.

I would like to ask about the entry in armbiaEnv.txt in the ArmBian distribution for Orange Pi Zero 3 overlay_prefix=sun50i-h616 does it have anything to do with the file in the directory? /boot/dtb-6.6.30-current-sunxi64/allwinner/sun50i-h618-orangepi-zero3.dtb For OZPI version 3 there is a prefix sun50i-h618 and in armbianEnv.txt there is overlay_prefix=sun50i-h616 shouldn't it be sun50i-h618 ?? I'm asking about this because I have a problem with using overlay for w1-gpio for OZPI v3, so I am looking for the source of the problem in various places

I try to understand problem [ 4.997793] sun50i-h616-pinctrl 300b000.pinctrl: pin PC10 already requested by onewire@0; cannot claim for 300b000.pinctrl:74 and I see this message is generate by: https://github.com/torvalds/linux/blob/master/drivers/pinctrl/pinmux.c#L102 /** * pin_request() - request a single pin to be muxed in, typically for GPIO * @pctldev: the associated pin controller device * @pin: the pin number in the global pin space * @owner: a representation of the owner of this pin; typically the device * name that controls its mux function, or the requested GPIO name * @gpio_range: the range matching the GPIO pin if this is a request for a * single GPIO pin */ ...... if ((!gpio_range || ops->strict) && desc->mux_usecount && strcmp(desc->mux_owner, owner)) { dev_err(pctldev->dev, "pin %s already requested by %s; cannot claim for %s\n", desc->name, desc->mux_owner, owner); goto out; } if ((gpio_range || ops->strict) && desc->gpio_owner) { dev_err(pctldev->dev, "pin %s already requested by %s; cannot claim for %s\n", desc->name, desc->gpio_owner, owner); goto out; } .....

Testing ... 3588 vendor 6.1: Do we have a working? 3D hw support via panfork wiringpi support? npu? 4k youtube video playback under Chromium? 4k under MPV video player? https://github.com/armbian/os/blob/main/userpatches/targets-release-standard-support.yaml other rockchips. Enabling extensions? - v4l2loopback-dkms,mesa-oibaf What about amlogic, allwinnner? - v4l2loopback-dkms,mesa-oibaf Nice to have: rock-5-itx edge kernel Manually tested: - Bananapi M2PRO Gnome desktop with 4l2loopback-dkms and mesa-oibaf

Maybe I need a change in my w1-gpio.dts looking to https://elixir.bootlin.com/linux/v6.6.30/source/arch/arm64/boot/dts/allwinner compatible = "allwinner,sun50i-h616"; to model = "OrangePi Zero3"; compatible = "xunlong,orangepi-zero3", "allwinner,sun50i-h618"; and add #include "sun50i-h616-orangepi-zero.dtsi" like in https://elixir.bootlin.com/linux/v6.6.30/source/arch/arm64/boot/dts/allwinner/sun50i-h618-orangepi-zero3.dts

I don't know for sure but my guess is yes, you need the sd to hold the boot loader at least. NAND was supported only with stone-age 3.x kernels which have been abandoned years ago. Therefore this can no longer be used.

Good day, Is there a manual how to do that with the latest Armbian versions? Since my SBC have internal NAND and SSD installed, but still need a SD card to boot fom it?

Will try, I guess i'll revert back to bullseye.

I have the same problem on NanoPi V2 after upgrading to OMV6->7, getting 502 error on login and trying to fix with "omv-salt stage run deploy". Sad((((

@Joko Christian I am not sure that mixing versions of firmware and kernel versions is advisable. I took note from @ER Samson that when he removed cloudfare and replaced it with an equivalent package, the problems went away. I am not able to do much with your issue as cloudfare is not part of Armbian, nor of debian for that matter. I would recommend you try the most recent current Armbian package and the latest release of cloudfare. Try to run without making changes to the firmware unless you need extra drivers for hardware that is not supported by the Armbian system as built.