All Activity

Thanks for your experience, did you try to run rk322x-config again and let it enable the proper overlay? realtek bluetooth is a bit quirky, especially on newer kernels

Truncate 2 partitions image ``` sudo losetup --partscan /dev/loop13 disk_image.img sudo e2fsck -f /dev/loop13p1 sudo e2fsck -f /dev/loop13p2 ' sudo resize2fs /dev/loop13p1 -M sudo resize2fs /dev/loop13p2 -M ' ### RUN THE "DISC" software and resize partition using the gui fdisk -l disk_image.img sudo losetup --detach /dev/loop13 truncate -s $(INSERT THE (END*BLOCKSIZE) OF PARTITION2 HERE) disk_image.img sudo losetup --partscan /dev/loop13 disk_image.img mkdir /tmp/disk_image sudo mount /dev/loop13p1 /tmp/disk_image sudo fstrim -v /tmp/disk_image sudo umount /tmp/disk_image sudo losetup --detach /dev/loop13 ```

Hello Guys!, I just want to share my experience with my tv-box. I've succesfully managed to install armbian in my rk3229 tv box Manufacturer Specifications (FROM ALI) General OS Version: Android 4.4 CPU: Rockchip 3229 Quad Core Processor Speed (max): 1.5GHz RAM: 1GB Internal Memory: 8GB External Memory: Support up to 32GB Display Resolution(max): 4K (2880x2160P) Support Video Resolution(max): 4K x 2K Wi-Fi: 802.11 b/g/n Bluetooth 2.1 Google Play DLNA Miracast Airplay 3D Movie Kodi / XBMC 15.2 Adobe Flash: Support Adobe Flash 10.1 and above (Armbian_community_24.5.0-trunk.667_Rk322x-box_bookworm_current_6.6.31_minimal.img.xz) I've used multitool to first backup my nand, and secondly set armbian image to boot over usb. Of course usb data transfer was significantly lower. Wifi module (rlt8723cs) worked very well, without drops. But my main issue is bluetooth. I was not capable of activate my bt module (after installing several packages). Of course, having a BT dongle fixes the issue but I really wanted to solve it.

moved

Hello Armbian Team I have one banana pi r2 pro board(https://wiki.banana-pi.org/Banana_Pi_BPI-R2_Pro). I used Armbian_community_24.5.0-trunk.667_Bananapir2pro_bookworm_current_6.6.31_minimal.img(https://github.com/armbian/community/releases/download/24.5.0-trunk.667/Armbian_community_24.5.0-trunk.667_Bananapir2pro_bookworm_current_6.6.31_minimal.img.xz) . I want to use 4 serial port. But when I tried to "cat" command, it gives Input/output error. I tried to screen too but it terminated immediately. it can see there is 7 uart interface ,but only ttyS2 works, for terminal how can I use other uart interfaces. :~# ls -l /dev/ttyS* crw-rw---- 1 root dialout 4, 64 May 24 14:17 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 May 24 14:17 /dev/ttyS1 crw------- 1 root tty 4, 66 May 24 14:22 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 May 24 14:17 /dev/ttyS3 crw-rw---- 1 root dialout 4, 68 May 24 14:17 /dev/ttyS4 crw-rw---- 1 root dialout 4, 69 May 24 14:17 /dev/ttyS5 crw-rw---- 1 root dialout 4, 70 May 24 14:17 /dev/ttyS6 crw-rw---- 1 root dialout 4, 71 May 24 14:17 /dev/ttyS7 Thanks, Best regards

Hi there, I'm trying to set up AP + STA on wlan0 using Orange Pi Zero 2W and Orange Pi Zero 3 with the Armbian image. I managed to do this on a Raspberry Pi Zero W. I encountered a problem: when creating a virtual access point, the process hangs and cannot be killed. Any attempt to view the logs after starting the process also leads to a hang, and only a reboot helps. This problem does not occur on the Raspberry Pi. I use the command: sudo iw phy phy0 interface add ap0 type __ap. For testing, I added an external USB Wi-Fi module to the Orange Pi Zero 3 and managed to create a virtual access point on it without any problems or hangs, so this problem only occurs on wlan0. The issue occurs on both Orange Pi Zero 2W and Orange Pi Zero 3, and they behave the same. Also, attempting to delete wlan0 via 'sudo iw dev wlan0 del' causes the device to hang. Has anyone encountered this situation? Is there a solution to this problem, and is it possible to make AP and STA on one interface on OPi Zero 2W/3 ? Here is the output of 'iw list': Wiphy phy1 //wlan0 Orange Pi [...] Supported interface modes: * IBSS * managed * AP * P2P-client * P2P-GO * P2P-device software interface modes (can always be added): valid interface combinations: * #{ managed, AP } <= 1, #{ P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1, total <= 3, #channels <= 2 [...] Wiphy phy0 //USB Wi-Fi adapter [...] Supported interface modes: * managed * AP * AP/VLAN * monitor software interface modes (can always be added): * AP/VLAN * monitor software interface modes (can always be added): * AP/VLAN * monitor interface combinations are not supported [...] Here is the output of 'iw list' on the Raspberry Pi: Wiphy phy0 [...] Supported interface modes: * IBSS * managed * AP * P2P-client * P2P-GO * P2P-device software interface modes (can always be added): valid interface combinations: * #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1, total <= 3, #channels <= 2 * #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1, total <= 4, #channels <= 1 [...] As far as I understand, based on the "valid interface combinations", wlan0 on the Orange Pi cannot support both managed and AP simultaneously. Could this be the reason? For the Wi-Fi adapter, "interface combinations are not supported". Thanks in advance!

dear dave3, Have you encountered the problem that when recording Armiban to an SD card, the nano pi neo air does not appear on the PC as a com port? If I install the old version of Armbian 5.73 and connect it via USB to the PC, it sees it as a com port.

Hi everyone! I wonder if modifying the "fbdev" driver to use Mali GPU to improve gaming performance is possible. I enabled `gpu` dtb, but according to "glxinfo -B" it uses "Device: llvmpipe, Accelerated: no". I'm curious if this can be improved somehow. BTW I found this old commit for Odroid C2: link

Based on what my android recovery says, use the following dtb amlogic "meson-gxl-s905x-p212.dtb"

Update: I ended up using the Ubuntu image from orange pi website and the camera works fine! It may be that the armbian linux image may need some file update for the camera to work correctly on op5b. This issue is now closed.

There is no archive for 'current images'. As of 24.02 and going forward the only images produced are the community builds.

Check github releases page: https://github.com/armbian/community/releases/

From first post: Prebuilt images: Archived images - built by Armbian servers and GPG-signed: https://imola.armbian.com/dl/rk3318-box/archive/ Nightly stables - built from trunk by Armbian servers and GPG-signed: https://github.com/armbian/community Stables provided by me (unsigned): https://users.armbian.com/jock/rk3318/ but the Archive with current images for RK3318 is down (many types is missing on the homepage) but the RK3228 is there but its not helping for my RK3318 boxes. Do some have one mirror of the latest current / stable builds that can being shred ?

Here's a bunch of links related to your box and uboot. https://linux-sunxi.org/T95H https://linux-sunxi.org/BROM#eGON_Boot https://linux-sunxi.org/Bootable_SD_card#Bootloader https://linux-sunxi.org/U-Boot#Boot https://linux-sunxi.org/FEL#Through_a_special_SD_card_image https://docs.u-boot.org/en/latest/board/allwinner/sunxi.html https://linux-sunxi.org/H616 https://lore.kernel.org/lkml/?q=T95

Nice! Enable SDHCI + emmc1 + emmc2 + emmc3 on DTS and recompile Check if usb*_dphy it's OTG or HOST on DTS

Never mind, still broken, 23.8.1 worked.

134 views and no Idea? Should I reinstall the old image? Regards, Holm Ok.. forget about that above, it's simply the wrong xrandr output )false DISPLAY variable). I can switch to HDMI1-1 and get a picture, but the default generated config for the Xserver seems to be wrong after the update.. One Question left: How can I switch the Video Output to VGA or HDMI or LCD on Armbian? Originally this was possible with a u-boot kernel Variable..but the original u-boot can't write to a fat partition..since there is none..? Regards, Holm

That is O.K., but Armbian build framework does not accept HW related tickets. Forum is right place where you can bring this up and discuss what to do. Then open a PR if solution emerges ... Without this patch, PCI probing will randomly fail. Which is worse then 100% going up in 1x. This is my 2c. I understand that you would like to have a perfect functioning PCI system on this hardware platform and if you cover someone several weeks of R&D, this can probably be done. Since this will not happen, we have partial solution/workaround in place, this forum and we have each other.

Hi there, I have been using a nanopi m4v2 for openmediavault for 4 years. In that time my SD card has died once. Now I have ordered an emmc module to do a full clean install of my server. So my questions are, is it wise to boot from the SD card and have the system on the emmc because the sd card can die faster? And if I boot from the SD card and it needs to be replaced, can I just insert a new one and everything will work as before? (With a freshly installed Armbian) If I do a backup of the emmc with win32 disk imager, can I burn the backup to a new emmc with a different sd-card as boot? When I do an armbian install, does it copy the system files to the emmc each time? Thanks and Greetings!

Fixed it!

Pardon me for asking here. I need to re-install OPi PC 2 -which I use as a firewall/router- because the old Ubuntu from 2020 is EOL. - Is the kernel problem stated here still an issue? Latest DL is Armbian_community_24.5.0-trunk.667_Orangepipc2_jammy_current_6.6.31_gnome_desktop.img.xz - I also have Armbian_23.8.1_Orangepipc2_jammy_current_6.1.47_xfce_desktop.img.xz from the archives. Which one is to go? When I start, I'll probably lose my Internet connection...