All Activity

Tried several /etc/asound.conf upmix settings, no luck. Made absolutely sure my audio jack isn't bridging anything by soldering straight to the board. No luck, I cannot separate the outputs. (no, the loose floating wire on the bottom is not the cause)

@madeofstown try out the orange pi zero 3 community images to see if it helps https://www.armbian.com/orange-pi-zero-3/ zero 2w don't have the motorcomm ethernet (requires an extension/expansion board accordingly), that's what I understand it to be. hopes that works still on zero 2w

In general you are going to need to find or fix a dtb file to correspond to the hardware you are running.

Hi, I'm using the image Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11.img on my Box TV Tigre 2 with Amlogic S905x processor and the dtb meson-gxl-s905x-p212.dtb and all the things I need are working, except the HDMI Audio output. Using the command "aplay -l" it shows no soundcards found but using the command lsmod | grep snd it shows different sound modules so I think it's a driver problem Also using armbian-config and going to system->hardware it shows an empty list. Any ideas on how to make it work?

https://forum.armbian.com/topic/29202-orange-pi-zero-3 @madeofstown If you care there was a discussion the last week on this topic in the above thread (the 2w and 3 are similar).

Why not use libgpiod? Or try to port mraa?

Works for me since ages. glmark2-wayland-nanopc-t4.logclinfo-fp-nanopc-t4.log

There are new Armbian 24.05 images available on the Helios64 download page: both images Bookworm minimal and Jammy Desktop are based on linux 6.6.30 (download them !). I will test the Bookworm image and see what needs to be modified (dtb, rtl_nic firmware, bootloader) and post a summary here.

I'll take your word for it @SteeMan, thank you. When I search for "orangepi 1.5GB" my post is the only one that comes up. Ill try different combinations but you already gave me my answer.

Do you have a USB to TTL/UART device? You would then be able to check what happens, you might even get a console through the serial connection if it starts up.

Collabora's engineers continue to be involved in the hardware enablement for a few different system-on-chips (SoCs) and platforms, and have also contributed significant improvements to kernel testing. View the full article

I used simple dts file as possible : /dts-v1/; /plugin/; / { model = "OrangePi Zero3"; compatible = "xunlong,orangepi-zero3", "allwinner,sun50i-h618"; fragment@0 { target-path = "/"; __overlay__ { w1: onewire@0 { compatible = "w1-gpio"; pinctrl-names = "default"; gpios = <&pio 2 7 0>; status = "okay"; }; }; }; }; compiled: armbian-add-overlay w1-gpio.dts and works 🙂 with armbianEnv.txt user_overlays=w1-gpio param_w1_pin=PC10 param_w1_pin_int_pullup=0 demsg show [ 5.015541] Driver for 1-wire Dallas network protocol. [ 5.019754] gpio-74 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 5.046831] w1_master_driver w1_bus_master1: Attaching one wire slave 28.03165129ecff crc 24 and cat /sys//bus/w1/devices/28-03165129ecff/w1_slave 76 01 4b 46 7f ff 0c 10 d3 : crc=d3 YES 76 01 4b 46 7f ff 0c 10 d3 t=23375 SBC DS18B20 VCC (3V3) Pin 1 ---------- VCC DS18B20 | R1 = 4k7 | GPIO74 Pin 26 --------- Data DS18B20 GND Pin 6 ---------- GND DS18B20

The issue is the 1.5gb memory. That particular memory configuration isn't currently working. Look back in the threads for the 2w and 3 and you can see a lot of discussion on this topic.

If you are using an ophub kernel you are not using Armbian. These forums are for Armbian ophub is a fork of Armbian. They use the Armbian name without permission. They do not contribute to Armbian development nor do they participate in these forums. You need to direct your question to their forums/support channels.

Hi team, This is not exactly Armbian related, however I hope to find some help here, also it can be useful for someone else in custom board development (my case). For testing I have Olimex RK3328-SOM-EVB and RK3318 TV box boards. They both behave the same way. As summary I'm trying to boot Linux using the Bootrom and USB OTG only, in other words without any external boot NVM attached. To archive this I build U-Boot SPL (u-boot-spl.bin), which support SDP protocol via USB OTG. For SDP file transfer I'm using imx_usb tool. The binaries used in the process are: rk3328_uboot_v1.19.250.bin - consists of u-boot-tpl.bin and u-boot-spl.bin created with boot_merger tool. u-boot.itb - FIT image (ATF, u-boot.bin and dtb), mainline U-Boot v2023.10 kernel.itb - FIT image (Image.gz and dtb), mainline kernel v6.1 I also prepared a proper sdcard image, from above binaries and wrote it to an SD card. My test setup consists of two booting paths, note the binaries in both are the same: With boot path 1, u-boot-tpl, u-boot-spl loaded via USB OTG: RK3328 in Mask ROM mode, SD card removed rkdeveloptool db rk3328_uboot_v1.19.250.bin insert SD card imx_usb - u-boot.itb boot kernel from U-boot prompt: setenv bootargs root=/dev/mmcblk1p2 console=ttyS2,1500000 earlycon ro rootwait; mmc dev 1; load mmc 1 0x800800 kernel.itb; bootm 0x800800 With boot path 2, u-boot-tpl, u-boot-spl loaded from SD card: insert SD card, power on (or reset) the board imx_usb - u-boot.itb boot kernel from U-boot prompt: setenv bootargs root=/dev/mmcblk1p2 console=ttyS2,1500000 earlycon ro rootwait; mmc dev 1; load mmc 1 0x800800 kernel.itb; bootm 0x800800 The overall description of two boot paths is as follow: boot path 1: rk3328_uboot_v1.19.250.bin (bootrom via OTG)-+ +- -> uboot.itb (imx_usb) -> kernel.itb (from SD card) boot path 2: rk3328_uboot_v1.19.250.bin (bootrom via SD) -+ The issues I have: When the SoC is booted through boot path 1 the kernel hangs soon after starting ... [ 0.016620] smp: Bringing up secondary CPUs ... If boot path 2 is used - The kernel boots and everything works as expected. The Bootrom in RK3318/28 first tries eMMC, SPI NOR, SPI NAND and SD card, if those boot devices failed then USB OTG is used for booting. Since the only difference between two boot paths is the way the TPL/SPL is loaded from the Bootrom - USB OTG or SD card, the only logical explanation I can think of is that there is some "leftover" in SoC state after OTG boot, which causes the kernel to hang. Does anyone have any idea how I can narrow down and eventually find the cause for this issue?

Forgive me if I am missing something. I have a 1.5GB oPiZ2W and I cannot get it to boot with the community builds or the unofficial builds. No green activity light, just the red power light. No output from HDMI. I've let it sit like this for 15 minutes and still nothing. Is there something else I need to do to get this to boot? I've had no issues with the Debian/Ubuntu images provided by OrangePi.

[ 11.309397] panfrost ff9a0000.gpu: clock rate = 500000000 [ 11.316882] panfrost ff9a0000.gpu: EM: OPP:200000 is inefficient [ 11.317248] panfrost ff9a0000.gpu: EM: created perf domain [ 11.320588] panfrost ff9a0000.gpu: mali-t860 id 0x860 major 0x2 minor 0x0 status 0x0 [ 11.321594] panfrost ff9a0000.gpu: features: 00000000,00000407, issues: 00000000,24040400 [ 11.322812] panfrost ff9a0000.gpu: Features: L2:0x07120206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002830 AS:0xff JS:0x7 [ 11.324483] panfrost ff9a0000.gpu: shader_present=0xf l2_present=0x1 [ 11.357056] [drm] Initialized panfrost 1.2.0 20180908 for ff9a0000.gpu on minor 1 It seems Panfrost driver was loaded, but the GPU doesn't produce any interrupts: 83: 0 0 0 0 0 0 GICv3 51 Level panfrost-gpu 84: 0 0 0 0 0 0 GICv3 53 Level panfrost-mmu 85: 0 0 0 0 0 0 GICv3 52 Level panfrost-job I tried build and install the latest version of `mesa`, which just not work. And `glxinfo -B` still shows that GPU is a virtual GPU. display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa/X.org (0xffffffff) Device: llvmpipe (LLVM 15.0.6, 128 bits) (0xffffffff) Version: 24.0.6 Accelerated: no Video memory: 3792MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 4.5 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Mesa/X.org OpenGL renderer string: llvmpipe (LLVM 15.0.6, 128 bits) OpenGL core profile version string: 4.5 (Core Profile) Mesa 24.0.6 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.5 (Compatibility Profile) Mesa 24.0.6 OpenGL shading language version string: 4.50 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.0.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 I am wondering if I can use the GPU on kernel 6.x, because I found that the case in this forum that can enable GPU for rk3399 all use the legacy version kernel, like 4.X. By the way, I am using the kernel from https://github.com/ophub/amlogic-s9xxx-armbian. Anyone can give me some tips or interpretation? Thanks in advanced!!!!

Both of these problems got resolved today... And I'm a bit ashamed to tell how they were resolved, but I should document this: WiFi starts working after a reboot, confirmed on the btt-cb2-rebase branch. The board name is correct (the one in /etc/armbian-release and in motd) if debs and packages-hashed dirs in the output dir are cleaned (rm -r).

Tested Debian Bookworm on Radxa Rockpi-E - RK3328: Systems boots HDMI N/A eMMC N/A sdcard ok USB 3.0 ok Gigabit Ethernet ok, throughput ok (> 900mbps) Fast Ethernet ok, throughput ok (> 90mbps) Wireless ok (rtl8821), throughtput satisfying but not at best (~30 mbps on 2.4ghz 802.11n network) Bluetooth untested Analog audio codec ok dmesg is clean

Goodday I had the same issue with a NanoPi Neo, your steps worked for me, with version Armbian_21.02.1_Nanopineo_bionic_current_5.10.12. It do not work with version Armbian_23.8.1_Nanopineo_bookworm_current_6.1.47

Hi I've got both left and right channels working of my analog audio jack. The quality is quite good as long as Master audio isn't set above volume 15 - 20 or so. Toggling DAC or DAC-Reversed in Alsamixer will enable or disable the physical left and right physical speakers of ear buds. However! On both channels, the left and right software signals are mixed. So if I use "aplay stereo-file.wav", I hear left+right mixed through my separate left ear. Listening to my right earbud, same story: I hear left+right audio mixed. Please help, I can't even find any snd_ module flags to mess with. I've no pulseaudio installed on this latest stable server edition of Armbian (Armbian_23.8.3_Orangepi3-lts_jammy_current_6.1.53_minimal.img). Armbianmonitor txt/gzip output is attached. root@oranger:/etc/modprobe.d# lsmod | grep -i snd snd_soc_hdmi_codec 20480 1 snd_soc_ac200 32768 1 snd_soc_simple_card 20480 0 snd_soc_simple_card_utils 24576 1 snd_soc_simple_card root@oranger:/etc/modprobe.d# modinfo snd_soc_ac200 filename: /lib/modules/6.6.16-current-sunxi64/kernel/sound/soc/codecs/snd-soc-ac200.ko license: GPL author: Jernej Skrabec <jernej.skrabec@gmail.com> description: X-Powers AC200 Codec Driver alias: of:N*T*Cx-powers,ac200-codecC* alias: of:N*T*Cx-powers,ac200-codec depends: intree: Y name: snd_soc_ac200 vermagic: 6.6.16-current-sunxi64 SMP mod_unload aarch64 root@oranger:/etc/modprobe.d# uname -a Linux oranger 6.6.16-current-sunxi64 #2 SMP Fri Feb 23 08:25:28 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux armbianmonitor-output.txt.gz

No idea what this version is. Take out microsd and shove it into your laptop/PC (running Linux) and mount it. Then check whats wrong.

moved to offtopic

Description station-m2: move to rk35xx family Add legacy-5.10 and vendor-6.1 kernel for station-m2 This PR is depend on https://github.com/armbian/linux-rockchip/pull/187 and https://github.com/armbian/linux-rockchip/pull/186 How Has This Been Tested? [x] Almost all hardware functions(HDMI, WiFi, BT, GbE, USB...). [x] System startup. 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

@Nick A thank you for your information 😀 Would it be possible to get your already patched sources for building the images you posted on pixeldrift? Can I download them on your github page? Any other way that I don't have to invent the wheel anew to create the same image myself? Thanks!!!