-
Volunteering positions
-
Single board computer maintainer
Position: Board maintainerNumber of places: 64Applicants: 74
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
Activity Stream
-
2
Enabling ROCKCHIP_DW_DP on RK3588 based devices to have working HDMI0 (next to HeadphoneJack one on a Rock 5 ITX)
Works just fine on last version. Looks like need to Login on Wayland/X11 first, not sure. Thanks a lot !!! <pre> $ zcat /proc/config.gz | grep DP| grep ROCK CONFIG_ROCKCHIP_ANALOGIX_DP=y CONFIG_ROCKCHIP_CDN_DP=y CONFIG_ROCKCHIP_DW_DP=y CONFIG_PHY_ROCKCHIP_DP=y CONFIG_PHY_ROCKCHIP_DPHY_RX0=m CONFIG_PHY_ROCKCHIP_INNO_CSIDPHY=m CONFIG_PHY_ROCKCHIP_INNO_DSIDPHY=m CONFIG_PHY_ROCKCHIP_SAMSUNG_HDPTX=m CONFIG_PHY_ROCKCHIP_USBDP=m CONFIG_PHY_ROCKCHIP_DP=y </pre> -
97
Armbian doesnt seem to see sata harddrives.
SCSI works fine with linux Mainline at least (6.16, 6.17 & 6.18) since few month now. -
2
Armbian_25.11.1_Odroidn2_noble_current_6.12.58_xfce_desktop, missing internet browsers and other problems
I wish it was that simple! I am on a different computer here...on the exact same network.. and yes I can download that file from here, different machine, different distro. However from the Odroid N2+ it is a different story. I have with a few experiments found that WAN pings would not work from the Odroid N2+ machine with the "noble" distro. But that problem is NOT present with the "bookworm" distro. I thought it was the initial installation, but the problem is persistent in "noble" and never an issue with "bookworm". Thanks for your reply, and any other ideas? -
45
RK3566 and Armbian
my Rupa 88 Pro 20, wifi/bt chip is cdtech 208821c (rtl8821cs), with real 4g32 had no bluetooth with mmie4jbcu's dtb or the included box-demo.dtb. with a lil help from claude.ai, i mix mmie4jbcu's dtb with x96x6.dtb from another thread here. et voilá bluetooth is working after apt install armbian-firmware-full rk3566-box-X88PRO20.dtb -
9
Build armbian kernel config
So, here's what I had to do to successfully build the image. First, I corrected my board file in the config/board/orangepizero3.csc directory. The processor value was incorrect, it was 616, so I set it to 618. Menuconf suggested selecting a board with a 618 chip, but in the board file it was listed as family 616. Later, I copied my board file to the userpatches directory and added the value CONFIG_DRM_PANEL_MIPI_DBI=m. Then I ran the image build script with the menuconf viewer. I was surprised that the CONFIG_DRM_PANEL_MIPI_DBI parameter already had the value "m"; previously, it was empty. After all these manipulations, the build went smoothly. Thank you so much for your support.
-
-
Member Statistics
