All Activity

That should be resolved as of this PR https://github.com/armbian/build/pull/6580

I used python script with Orange pi zero 3 (Armbian_community_24.8.0-trunk.6_Orangepizero3_bookworm_current_6.6.31_minimal.img) Observation: 1) /dev/ttyS1 is actually Serial 2 as per pin diagram as per Orange Pi Zero 3 - Armbian web page 2) /dev/ttyS2 is actually Serial 5 as per pin diagram as per Orange Pi Zero 3 - Armbian web page 3) even if I set rtscts=True in crateing object ser in above script, there is no output on rts or cts pin. I am looking forward to have RTS pin remain high during transmission to easily integrate ic for RS485 communication. I was glad that Amrbian for Orange Pi Zero 3 has out of the box RTS CTS pin support which otherwise is a complicated matter for me. Please guide how to make the serial port work along with RTS pin to remain high during transmission of data. Regards

thank you very much, please tell me how to write this command in u-boot?

G'day Has anyone managed to get our fave OS booting on this device. ? Wyse 3040 (N10D) I've created UEFI boot media, with both Rufus and Etcher, but it dosne't see it as bootable. To prove settings are ok on the device, it boots the deb bookworm usb image I made. Unfortunatly, Deb won't install as this device only has 8GB of flash... hence why I returned again to Armbain Many thanks MarkA

Hmmm, what you describe seems a regression from latest u-boot upgrade to v2024.01, even though I did not notice any issue like that before; anyway you can easily trigger the boot from sdcard removing the bootloader from the emmc with dd if=/dev/zero of=/dev/mmcblk2 bs=32k seek=1 count=40 Once you do that, the board will boot multitool from sdcard

Hi! I'm sorry for the delay. Here you go: interface=wlan0 driver=nl80211 country_code=XX hw_mode=g channel=7 ssid=wifiAP wpa=2 auth_algs=1 wpa_passphrase=12345678 wpa_key_mgmt=WPA-PSK rsn_pairwise=CCMP wpa_pairwise=CCMP wmm_enabled=1

I'm currently working on configuring the USB audio gadget (g_audio) on my Orange Pi 5B to ensure both the speaker and microphone are recognized by the host PC. However, I am facing an issue where only the speaker (playback) interface shows up on the host, while the microphone (capture) interface does not. Here are the steps I have followed so far: 1.Kernel Modules Loaded: sudo modprobe dwc3 sudo modprobe dwc3-gadget sudo modprobe libcomposite sudo modprobe g_audio 2.Unloaded and Reloaded g_audio Module with Parameters: sudo modprobe -r g_audio sudo modprobe g_audio p_chmask=0x3 c_chmask=0x3 p_srate=48000 c_srate=48000 3. Bind the Gadget to the USB Controller: echo "$(ls /sys/class/udc)" > /sys/kernel/config/usb_gadget/g1/UDC Despite these steps, the host PC only recognizes the playback interface. How can I configure the g_audio USB gadget on the Orange Pi 5B to ensure that both the speaker (playback) and microphone (capture) interfaces are recognized by the host PC? Are there any additional steps or configurations that I might be missing? Any help or guidance would be greatly appreciated! Thank you in advance.

I tested Armbian 24.5.1 Noble Gnome + trunk MESA/VPU Kernel: 6.6.31, Size: 1.3GB, Release date: May 25, 2024 on my PBP (sd card). What does not work: - Sound - HDMI Monitor on PB dock Thank you

Change to "vendor" kernel 6.1.y is recommended.

Kajen, I think that silver/gold chip on your board might be bluetooth/wifi. But I can't make out the number/letters written on it.

@lanefu Thanks a lot 🙂 ... The last open Question .. with the Edge Kernel, what is the right way to export the GPIO's cd /sys/class/gpio echo 157 > export does not work 🙂

You did a reboot after upgrading, right?

Using DNScrypt does reduce the instabilities with Linux 6.6.16-current-sunxians higher, though it still did have slowdowns/high CPU usage after 2-3 days. I had to move the back up instance to legacy kernel and so my network has a functioning DNS when the other conks up. Legacy has been rock stable.

...Got it working with Debian (not armbian) if I controlled the power-on and connection order carefully. But the easier fix was to grab a used i3 desktop machine and install Ubuntu Studio into that, reserving the SBC for future projects. It's amazing what SBCs can do... but if you don't need maximum compactness, minimum power draw, or direct hardware interfacing, sometimes using something better standardized/supported will be the winning choice. Oh well. Only a small detour, and a few bucks that it turned out I didn't need to spend right now; not a disaster. "No honest effort is ever wasted; it can always serve as a bad example."

I just upgraded to Arabian 24.5.1 using `apt-get upgrade` and now I cannot load ip_tables: # modprobe ip_tables modprobe: ERROR: could not insert 'ip_tables': Exec format error I’m not sure what to make of it.

So I figured out how to test uboot.bin's with the fel mode, but so far couldn't build my own uboot for the a83t. Also i dug around in the image and it seems like the banana pi m3 images doesn't have the uboot for the a83t (might be wrong there)

Hi! did you ever get this working? I had the touch working on a Arch with the radxa 5.10.110 kernel but had had trouble getting other pieces. Have everything working on Armbian except touch. Couldn't use the included display dtbo, but had to use my Arch working dtbo.

Kajen, For Ethernet you need these two patches in u-boot. https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/100-sunsi-add-h616-internal-eth-phy-support.patch https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/106-Add-int-phy-eth-H313-h616-with-AC300.patch Kernel patch. You need to edit your box's dts. https://github.com/NickAlilovic/build/blob/main/patch/kernel/archive/sunxi-6.7/patches.armbian/arm64-dts-allwinner-h618-Transpeed-8k618-T-Enable-Ethernet.patch Can you take a picture of your boards wifi chip?

it doesn't work even on a newest kernel: user@rockpro64:~$ uname -r 6.6.16-current-rockchip64 user@rockpro64:~$ sudo cat /etc/armbian-release |egrep -i "version|branch|board" BOARD=rockpro64 BOARD_NAME="RockPro 64" BOARDFAMILY=rockchip64 BOARD_TYPE=conf VERSION=24.2.1 BRANCH=current user@rockpro64:~$ sudo lspci -v -s 01:00.0 01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller (rev 11) (prog-if 01 [AHCI 1.0]) Subsystem: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller Flags: fast devsel, IRQ 59 Memory at fa040000 (32-bit, non-prefetchable) [size=2K] Expansion ROM at fa000000 [size=256K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [70] Express Legacy Endpoint, MSI 00 Capabilities: [e0] SATA HBA v0.0 Capabilities: [100] Advanced Error Reporting After initiating it appeared with the disks connected: user@rockpro64:~$ echo "0000:01:00.0" | sudo tee /sys/bus/pci/drivers/ahci/bind 0000:01:00.0 @rockpro64:~$ sudo lspci -v -s 01:00.0 01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller (rev 11) (prog-if 01 [AHCI 1.0]) Subsystem: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller Flags: bus master, fast devsel, latency 0, IRQ 95 Memory at fa040000 (32-bit, non-prefetchable) [size=2K] Expansion ROM at fa000000 [size=256K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Express Legacy Endpoint, MSI 00 Capabilities: [e0] SATA HBA v0.0 Capabilities: [100] Advanced Error Reporting Kernel driver in use: ahci Thus the workaround with udev rules still needs to be applied. https://forum.pine64.org/showthread.php?tid=7453 was helpful